From: Roy Hills <linux-kernel-l@nta-monitor.com>
To: vda <vda@port.imtp.ilyichevsk.odessa.ua>,
Roy Hills <linux-kernel-l@nta-monitor.com>,
Petri Kaukasoina <kaukasoi@elektroni.ee.tut.fi>,
linux-kernel@vger.kernel.org
Subject: Re: zImage not supported for 2.2.20?
Date: Mon, 31 Dec 2001 09:12:44 +0000 [thread overview]
Message-ID: <4.3.2.7.2.20011231090710.00ab7e30@192.168.124.1> (raw)
In-Reply-To: <01122909300800.01870@manta>
In-Reply-To: <4.3.2.7.2.20011228173505.00aa3da0@192.168.124.1> <4.3.2.7.2.20011228124704.00abba70@192.168.124.1> <4.3.2.7.2.20011228173505.00aa3da0@192.168.124.1>
At 09:30 29/12/01 -0200, vda wrote:
>Maybe it's better to fix a20 problem? I never heard about Tecra a20 bug,
>can you point me to the info?
>--
>vda
My understanding is that the problem is something to do with the
Toshiba Tecra laptops not flushing the cache properly when activating
the A20 line. This causes a problem for bzImage kernels because they
decompress into extended memory, whereas zImage kernels don't and
thus don't tickle the bug.
Unfortunately, I haven't seen a proper technical description of the problem
nor any workaround or patch.
Earlier versions of Debian Linux e.g. 2.1 (the distro that I use) used to
supply
special "Tecra" kernels because of this problem.
Alan Cox said in a previous message in this thread:
ac>If your tecra is one with the problem early intel PCI chipsets the
ac>documentation on the workaround is on the intel.com site if you feel
ac>creative 8)
ac>Basically the A20 handling for hardware caches on some of these early chips
ac>was broken. There were real hardware fixes for new boards and a software
ac>workaround for old ones is described in the errata docs for the chip.
This sounds about right, but I've not been able to locate the info on Intel's
website.
Roy Hills
--
Roy Hills Tel: +44 1634 721855
NTA Monitor Ltd FAX: +44 1634 721844
14 Ashford House, Beaufort Court,
Medway City Estate, Email: Roy.Hills@nta-monitor.com
Rochester, Kent ME2 4FA, UK WWW: http://www.nta-monitor.com/
next prev parent reply other threads:[~2001-12-31 9:14 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-28 10:18 Roy Hills
2001-12-28 12:12 ` Matthias Andree
2001-12-28 12:26 ` bug reports for CML2? rpjday
2001-12-28 12:39 ` André Dahlqvist
2001-12-28 17:44 ` zImage not supported for 2.2.20? Roy Hills
2001-12-28 18:19 ` Alan Cox
2001-12-28 20:36 ` Petri Kaukasoina
2001-12-29 2:25 ` H. Peter Anvin
2001-12-29 2:58 ` Alan Cox
2001-12-29 11:01 ` Petri Kaukasoina
2001-12-28 18:36 ` H. Peter Anvin
2001-12-28 19:04 ` Alan Cox
2001-12-28 18:42 ` H. Peter Anvin
2001-12-31 12:16 ` Roy Hills
2001-12-31 13:06 ` Petri Kaukasoina
2001-12-28 13:11 ` Roy Hills
2001-12-28 13:35 ` Matthias Andree
2001-12-28 14:32 ` Petri Kaukasoina
2001-12-28 20:13 ` Wolfgang Erig
2001-12-29 2:23 ` H. Peter Anvin
2002-01-01 15:16 ` Wolfgang Erig
2001-12-31 9:12 ` Roy Hills [this message]
2002-01-02 0:54 ` H. Peter Anvin
2001-12-28 21:06 Andries.Brouwer
2001-12-28 21:55 ` H. Peter Anvin
2001-12-28 23:57 ` Alan Cox
2001-12-29 0:01 Andries.Brouwer
2001-12-29 0:17 ` H. Peter Anvin
2001-12-29 0:20 ` H. Peter Anvin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4.3.2.7.2.20011231090710.00ab7e30@192.168.124.1 \
--to=linux-kernel-l@nta-monitor.com \
--cc=kaukasoi@elektroni.ee.tut.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®