On Mon, 06 Jul 2009 13:29:55 -0400 Dan Williams <dcbw@xxxxxxxxxx> wrote: > On Sun, 2009-07-05 at 12:59 +0400, Alexander Barinov wrote: > > On Sat, 04 Jul 2009 12:41:42 +0200 > > Johannes Berg <johannes@xxxxxxxxxxxxxxxx> wrote: > > > On Sat, 2009-07-04 at 13:03 +0400, Alexander Barinov wrote: > > > > The initial symptom of the bug was system lockup when executing > > > > 'ifdown eth0' with 'BUG: scheduling while atomic'. Trying to > > > > understand the cause of the bug and find a workaround I was > > > > able to find an easier way to reproduce it. By executing > > > > 'cat /proc/net/wireless' I get the same bug: > > > This should have been fixed by > > > 87057825824973f29cf2f37cff1e549170b2d7e6. For some reason > > > everybody seems to have assumed that get_wireless_stats can > > > sleep, which before that commit it could _not_. > > > > The patch you have mentioned was not directly applicable to 2.6.30 > > kernel so I pulled wireless-testing git tree and compiled it. This > > deteriorated the situation further - now after executing > > 'cat /proc/net/wireless' I get kernel lockup without any further > > messages. > > Can you get anything at all out of the kernel on that? 2.6.29.5 with > quite recent wireless-testing libertas driver works fine with sd8686 > on my machine (hp 2530p laptop with a Ricoh controller). Can you > post your backport of that patch too? The problem is I get no kernel messages at all, just a lockup. Wireless debug (CONFIG_MAC80211_*_DEBUG) and libertas debug (CONFIG_LIBERTAS_DEBUG) are on, no "quiet" option on boot. Is there any other way I can increase level of debug output to be able to give you some meaningful information with regards to my problem? BTW, my case is sd8686 on some SDHCI PCI controller, I am not sure how to find the vendor. I am not sure which backport you are talking about, as I am using wireless-testing pulled from git, it should be something around 2.6.31-rc1. Regards, Alexander -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
