Kernel Bug Tracker – Bug 22842
iwl3945 suddenly stops working
Last modified: 2012-07-23 12:02:00 UTC
Just like that, there's no warning or anything.
I can recover by trying:
* bring down/up the interface
* reload the module
None of these alone makes it work, I don't know what exactly does, I just try all of them until it works again.
This seems to have started on 2.6.36, but I'm not sure.
Recategorised as network-wireless
Does turning on debugging in the driver give some clues?
(In reply to comment #2)
> Does turning on debugging in the driver give some clues?
What kind of debugging?
echo 0x43fff > /sys/class/net/wlan0/device/debug_level
I will try that, however, a bit more of clarification: I can reconnect to the access point just fine, even get an IP from DHCP, and the other APs are listed correctly. However, once connected I cannot even ping the gateway.
Perhaps we could see some dmesg output from after the failure?
echo 0x43fff > /sys/class/net/wlan0/device/debug_level will help a lot
Created attachment 37682 [details]
Here is a debug log.
At this point issuing a ping command returns nothing but iwl3945_mac_tx seems to enter and leave.
This time I didn't try to make any changes (bring down the iface, rkfill) and it seems after some time it recovered.
So? What else do you need?
This issue is very annoying.
I'm going to try 2.6.35 again and see if I can narrow down the issue.
BTW. Why can't I change the status from NEEDINFO? The info has been provided.
The configuration of this bugzilla seems to be not ideal. I changed it for you.
(In reply to comment #9)
> The configuration of this bugzilla seems to be not ideal. I changed it for you.
Thanks, I've filed a bug for that:
Other projects use needinfo as a flag.
Wey-Yi, is the infor Felipe provided sufficient for you?
got the log, will have someone look into it.
Felipe, I will ask for more information if needed.
Is this still a problem in 2.6.38.y?
If problem is not solved, does disable_hw_scan=1 helps? If not, bisection will be needed to solve it ...
Attachment should change MIME type to application/x-xz (I have no permissions to change this).
(In reply to comment #14)
> If problem is not solved, does disable_hw_scan=1 helps? If not, bisection will
> be needed to solve it ...
Unfortunately I have a new laptop and I haven't managed to use the old one at all. I'll try to use it a bit more to see if I can reproduce.
> Attachment should change MIME type to application/x-xz (I have no permissions
> to change this).
Ok, I'm closing the bug with insufficient data resolution.