From: Cesar Eduardo Barros <cesarb@nitnet.com.br>
To: Erik Mouw <erik@harddisk-recovery.com>
Cc: "Martin J. Bligh" <mbligh@aracnet.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Bug 1284] New: Asus P5AB broken BIOS reading ESCD
Date: Mon, 29 Sep 2003 14:59:09 -0300 [thread overview]
Message-ID: <20030929175908.GD27908@flower.home.cesarb.net> (raw)
In-Reply-To: <20030929174127.GD26491@bitwizard.nl>
On Mon, Sep 29, 2003 at 07:41:27PM +0200, Erik Mouw wrote:
> On Mon, Sep 29, 2003 at 08:50:44AM -0700, Martin J. Bligh wrote:
> > Summary: Asus P5AB broken BIOS reading ESCD
> > Kernel Version: 2.6.0-test6
> > Status: NEW
> > Severity: normal
> > Owner: mbligh@aracnet.com
> > Submitter: cesarb@nitnet.com.br
> >
> >
> > Distribution: Debian testing/unstable
> > Hardware Environment: Asus P5AB
> > Software Environment:
> > Problem Description:
> >
> > Trying to read /proc/bus/pnp/escd causes an oops. Looks like the PnPBIOS is
> > broken. However, it's not exploding_pnp_bios, since only reading the escd causes
> > it (the boot probe works fine).
> >
> > I think a new function should be added to the DMI blacklist to block trying to
> > read the ESCD.
>
> [...]
>
> > DMI:
> > # dmidecode 2.2
> > Legacy DMI 2.0 present.
> > 29 structures occupying 946 bytes.
> > Table at 0x000F545A.
> > Handle 0x0000
> > DMI type 0, 18 bytes.
> > BIOS Information
> > Vendor: Award Software, Inc.
> > Version: ASUS P5A-B ACPI BIOS Revision 1004 .............................
>
> FWIW: I used to have a similar board (Asus P5A, it actually died a week
> ago, so I can't check anything anymore). Never tried 2.6 on it, but I
> know it had a flakey PnPBIOS implementation: if you put in a Sound
> Blaster AWE64 Gold, you couldn't use the floppy drive anymore. The
> latest "Y2K compliant" BIOS (revision 1.005 IIRC) fixed that, it might
> also fix this particular bug.
Well, I do have a SoundBlaster AWE ISA on that board, and it didn't
break the floppy.
I have downloaded the latest BIOS and will test it later (I don't have
the latest one, the latest one is from 2002 and the one in the box is
from '98)
> (Asus website seems to be broken, I get a "runtime error" from their
> web server when I want to get a list of downloads, so I have no idea if
> you have the latest BIOS right now :-/ )
--
Cesar Eduardo Barros
cesarb@nitnet.com.br
cesarb@dcc.ufrj.br
next prev parent reply other threads:[~2003-09-29 18:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-29 15:50 Martin J. Bligh
2003-09-29 17:41 ` Erik Mouw
2003-09-29 17:59 ` Cesar Eduardo Barros [this message]
2003-09-29 22:22 ` Cesar Eduardo Barros
2003-09-30 9:18 ` Erik Mouw
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=20030929175908.GD27908@flower.home.cesarb.net \
--to=cesarb@nitnet.com.br \
--cc=erik@harddisk-recovery.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
/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®