linux-kernel - Reporting ThinkPad BIOS bugs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 21 Mar 2008 09:51:35 -0300
From:	Henrique de Moraes Holschuh <hmh@....eng.br>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	"Peter F. Patel-Schneider" <pfps@...izon.net>,
	Tejun Heo <htejun@...il.com>, linux-kernel@...r.kernel.org,
	"Peter F. Patel-Schneider" <pfps@...earch.bell-labs.com>,
	Thomas Renninger <trenn@...e.de>
Subject: Reporting ThinkPad BIOS bugs

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/