Bug 26802
| Summary: | b43: Suspend failed | ||
|---|---|---|---|
| Product: | Drivers | Reporter: | Patrick Matthäi (patrick) |
| Component: | network-wireless | Assignee: | drivers_network-wireless (drivers_network-wireless) |
| Status: | CLOSED OBSOLETE | ||
| Severity: | normal | CC: | alan, andrew, cool_sch.alex, florian, Larry.Finger, linville, maciej.rutecki, rjw, zajec5 |
| Priority: | P1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Kernel Version: | 2.6.37 | Subsystem: | |
| Regression: | Yes | Bisected commit-id: | |
| Bug Depends on: | |||
| Bug Blocks: | 7216, 21782 | ||
|
Description
Patrick Matthäi
2011-01-15 18:56:47 UTC
I do not know what caused the issue; however, using modprobe to unload and reload b43 should fix the problem without needing to reboot. Did 2.6.36 work OK for you, or did you switch to 2.6.37 from some older kernel? 2.6.{30,31,32,33,34,35,36} do not have this issue (or I never triggered it, no idea how to retrigger it..).
But you are right, readding the module may be an idea, I will try it out, if it occurs again. Maybe some other logs etc needed, if it occurs again?
If you do not already have them on, please enable 1) Broadcom 43xx debugging in Drivers => Network device support => Wireless LAN, aka CONFIG_B43_DEBUG=y 2) SSB Debugging in Drivers => Sonics Silicon Backplane, aka CONFIG_SSB_DEBUG=y There is good news and bad news. The good news is that there are only 35 commits between 2.6.36 and 2.6.37 that affect either ssb or b43. The bad news is that I cannot see any of them affecting your card. My copy of a 14e4:4312 card is loaned out and I cannot test it; however, I do have a 14e4:4311, which has the same 802.11B/G part as the 4312 - no 802.11A part. When I get a chance, I will test it. Patrick, can you run a git bisect between 2.6.36 and 2.6.37 to narrow-down the commit that causes this issue? As I told I think it is a hardware issue Do you think your hardware is broken? If so, then this bug should not be labeled a regression. I am unable to duplicate the issue with my hardware. (In reply to comment #7) > Do you think your hardware is broken? If so, then this bug should not be > labeled a regression. > > I am unable to duplicate the issue with my hardware. Damn sorry, I replied before to another bugreport (to the wrong one), this was my answer to the issue HERE: (In reply to comment #14) > Hmm, speaking for my case, I'm thinking that it is more a hardware error. > > I reproduced it a second time with 2.6.37 and it occured where I put my > notebook maybe a bit fast on my desk, maybe it is also a HW error with your > notebook? Args, sorry, I replied to the wrong bug! This should go to https://bugzilla.kernel.org/show_bug.cgi?id=26802 instead of 10398 :( So, I'm closing this as invalid. Please shout, if that is wrong. Please reopen the bug, it's not a hardware fault. It happens quite often here, and it's been reported many times on internet. Symptoms are the same, doing rmmod/modprobe helps. Will try to collect more debug info, though. Can you verify, that 2.6.36 works and 2.6.37 is broken? If so, can you do as John Linville asked in comment #5 and bisect? As far as I remember, both are broken, but I can't really tell now, I'm using 3.2.0-rc7-686-pae from Debian. |