linux-kernel - Rt2x00 problem traced back to x86 ACPI/PCI/e820 handling.

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-next>] [day] [month] [year] [list]

Message-ID: <4B1D8176.9040209@gmail.com>
Date:	Mon, 07 Dec 2009 23:28:06 +0100
From:	Gertjan van Wingerde <gwingerde@...il.com>
To:	Ingo Molnar <mingo@...e.hu>, Yinghai Lu <yinghai@...nel.org>
CC:	LKML <linux-kernel@...r.kernel.org>, erbrochendes@....de,
	divinespear@...il.com, andjelo@....net
Subject: Rt2x00 problem traced back to x86 ACPI/PCI/e820 handling.

Hi Ingo, Yinghai,

For a while now we have seen reports of the rt2x00 driver not working correctly
where bogus information was read from the EEPROM. This resulted in a non-functional
driver.
It has been established that the problem has introduced itself sometimes in the 2.6.31
development cycle.

Lately the failures have been traced back to commit 5d423ccd7ba4285f1084e91b26805e1d0ae978ed
of a patch created by Yinghai and committed Ingo.

Reverting this patch seems to fix the problems with the rt2x00 driver.

Also, it has been established that another work-around is to supply the pci=use_crs boot parameter.

Do any of you have any idea as to what is going on here, and if this is something where the
rt2x00 driver is at fault, or where the x86 ACPI/PCI/e820 code is buggy?

So far I can establish that all the cases for which it is known what kind of HW it is that these
are all MSI laptops.

The related bug reports are:
	http://bugzilla.kernel.org/show_bug.cgi?id=14460
	https://bugs.launchpad.net/ubuntu/+source/linux/+bug/404596

---
Gertjan.
--
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/