From: David Balazic <david.balazic@uni-mb.si>
To: ak@muc.de, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Workaround for AMD762MPX "mouse" bug
Date: Sun, 29 Dec 2002 15:46:57 +0100 [thread overview]
Message-ID: <3E0F0AE1.EB2C5DAA@uni-mb.si> (raw)
Andi Kleen (ak@muc.de) wrote :
> AMD has published a new errata sheet for the AMD762, which describes
> the root cause of the infamous "AMD 762 unstable when no PS/2 mouse
> connected" bug. The reason is that without a PS/2 mouse the BIOS doesn't
> put a data page in front of the VGA buffer at 640K. When the kernel
> puts a page cache page there and does busmaster IO with it then the automatic
> PCI prefetch from the chipset can hit the VGA buffer and that may cause a hang.
>
>
> The workaround is to reserve the page directly before 640K if it wasn't
> already reserved by the BIOS.
>
>
> The bug only occurs in newer revisions (B0,B1)
>
>
> The workaround here is somewhat hackish. We can only reserve the page
> in early boot, but at that time there is no easy way to check for the
> AMD762's PCI-ID because the PCI subsystem hasn't been initialized yet.
>
>
> This patch checks later during the pci quirks pass instead
> and then tells the user to pass a kernel option - "vgaguard" - in
> case of instability. This is not ideal, but probably preferable than
> to connect PS/2 mouses to all boxes in a colocated rack. Another
> way would be to always reserve that page, but I didn't feel like
> punishing everybody just for a hardware bug in a single chipset.
>
>
> Patch for 2.5.53. Please consider applying.
Some suggestions :
- do not tell the user to use the "vgaguard" option if he is already
using it
- change to more informative text :
old :
I/O APIC: AMD762 Errata #56 may be present.
In case of instability boot with "vgaguard" or connect a PS/2 mouse.
new:
I/O APIC: AMD762 Errata #56 may be present.
In case of instability boot with the "vgaguard" kernel boot option or
connect a PS/2 mouse and reboot.
Just connecting a PS/2 mouse on a running system does not help, right ?
:-)
- maybe rename the option to "amd762vgaguard" ?
- also write some docs and put a link to it in the kernel message ?
For now this would be enough :
I/O APIC: AMD762 Errata #56 may be present.
In case of instability boot with the "vgaguard" kernel boot option or
connect a PS/2 mouse and reboot.
See http://www.uwsg.indiana.edu/hypermail/linux/kernel/0212.3/0043.html
Regards,
David Balazic
next reply other threads:[~2002-12-29 14:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-29 14:46 David Balazic [this message]
2002-12-30 0:50 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2002-12-24 16:25 Andi Kleen
2002-12-29 16:51 ` Eric Lammerts
2002-12-29 20:10 ` Benjamin LaHaise
2002-12-30 10:35 ` Henning P. Schmiedehausen
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=3E0F0AE1.EB2C5DAA@uni-mb.si \
--to=david.balazic@uni-mb.si \
--cc=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome