From: Gertjan van Wingerde <gwingerde@gmail.com>
To: Ingo Molnar <mingo@elte.hu>, Yinghai Lu <yinghai@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
erbrochendes@gmx.de, divinespear@gmail.com, andjelo@gmx.net
Subject: Rt2x00 problem traced back to x86 ACPI/PCI/e820 handling.
Date: Mon, 07 Dec 2009 23:28:06 +0100 [thread overview]
Message-ID: <4B1D8176.9040209@gmail.com> (raw)
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.
next reply other threads:[~2009-12-07 22:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-07 22:28 Gertjan van Wingerde [this message]
2009-12-07 22:52 ` Rt2x00 problem traced back to x86 ACPI/PCI/e820 handling Yinghai Lu
2009-12-09 6:43 ` Gertjan van Wingerde
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=4B1D8176.9040209@gmail.com \
--to=gwingerde@gmail.com \
--cc=andjelo@gmx.net \
--cc=divinespear@gmail.com \
--cc=erbrochendes@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=yinghai@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