From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "Peter F. Patel-Schneider" <pfps@verizon.net>,
Tejun Heo <htejun@gmail.com>,
linux-kernel@vger.kernel.org,
"Peter F. Patel-Schneider" <pfps@research.bell-labs.com>,
Thomas Renninger <trenn@suse.de>
Subject: Reporting ThinkPad BIOS bugs
Date: Fri, 21 Mar 2008 09:51:35 -0300 [thread overview]
Message-ID: <20080321125135.GF5586@khazad-dum.debian.net> (raw)
In-Reply-To: <20080321111313.24567b9f@core>
On Fri, 21 Mar 2008, Alan Cox wrote:
> > How can I check to see if this is the case? How would this explain that
>
> As I said before, take a CF card/adapter combination you know fails
> on a T60p/T61p and test it on a Linux box that isn't one of those types
> (and preferably not a Lenovo at all)
>
> > the adapter and card sometimes work when they are in when the system boots?
>
> Ask the BIOS authors. Trying to fathom what they have done is frequently
I can actually try to do just that. So can Thomas Renninger, added to cc.
Please someone send either of us a *detailed*, ready for "upstream
submission" bug report of the thinkpad BIOS IRQ routing issues, and we might
be able to get it to someone who can fix it for good.
Be clear, concise, and remember that whomever will read it has no obligation
to know much about Linux kernel internals, so explain things from a
*hardware* and ACPI model (as in what is in the ACPI spec, not what ACPICA
code does) point of view.
Do attach the trimmed kernel logs showing the bugs and ACPI/IOAPIC init.
Even if the person reading the report doesn't know Linux well, they can be
helpful. And if he does know Linux well...
The report should be done with the latest available BIOS when possible, and
include the dmidecode BIOS information (version, date), as well as the
dmidecode System Information/Product Name (i.e. the numeric model number).
Reports about non-Lenovo ThinkPad BIOSes are unlikely to be acted upon. I
have made a bunch of those, but they couldn't do much about it.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
next prev parent reply other threads:[~2008-03-21 12:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-05 18:08 2.6.23-rc9-git4: pata_pcmcia, disabling IRQ #9 Manuel Lauss
2008-03-21 0:26 ` 2.6.23-rc9-git4: pata_pcmcia, disabling IRQ #9 and Re: libata and legacy ide pcmcia failure Peter F. Patel-Schneider
2008-03-21 1:12 ` Alan Cox
2008-03-21 1:38 ` Tejun Heo
2008-03-21 10:40 ` Alan Cox
2008-03-21 11:17 ` Peter F. Patel-Schneider
2008-03-21 11:13 ` Alan Cox
2008-03-21 11:29 ` Peter F. Patel-Schneider
2008-03-21 12:51 ` Henrique de Moraes Holschuh [this message]
2008-03-21 13:40 ` Reporting ThinkPad BIOS bugs Peter F. Patel-Schneider
2008-03-21 11:31 ` 2.6.23-rc9-git4: pata_pcmcia, disabling IRQ #9 and Re: libata and legacy ide pcmcia failure Peter F. Patel-Schneider
2008-03-21 11:27 ` Alan Cox
2008-03-21 2:23 ` Peter F. Patel-Schneider
2008-03-21 10:41 ` Alan Cox
2008-03-26 14:13 ` Peter F. Patel-Schneider
2008-03-26 14:44 ` Tejun Heo
2008-03-26 15:28 ` Peter F. Patel-Schneider
2008-03-29 4:40 ` Tejun Heo
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=20080321125135.GF5586@khazad-dum.debian.net \
--to=hmh@hmh.eng.br \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=htejun@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pfps@research.bell-labs.com \
--cc=pfps@verizon.net \
--cc=trenn@suse.de \
/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®