[Bug 450472] New: ath5k driver gets into a state where it cannot connect anymore

https://bugzilla.novell.com/show_bug.cgi?id=450472 Summary: ath5k driver gets into a state where it cannot connect anymore Product: openSUSE 11.1 Version: Factory Platform: x86 OS/Version: Linux Status: NEW Severity: Major Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: swesemeyer@hotmail.com QAContact: qa@suse.de Found By: --- Created an attachment (id=256943) --> (https://bugzilla.novell.com/attachment.cgi?id=256943) relevant var/log/messages section I have a Samsung NC10 with a: 02:00.0 Ethernet controller: Atheros Communications Inc. AR242x 802.11abg Wireless PCI Express Adapter (rev 01) Subsystem: Askey Computer Corp. Device 7131 Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at f0100000 (64-bit, non-prefetchable) [size=64K] Capabilities: [40] Power Management version 2 Capabilities: [50] Message Signalled Interrupts: Mask- 64bit- Count=1/1 Enable- Capabilities: [60] Express Legacy Endpoint, MSI 00 Capabilities: [90] MSI-X: Enable- Mask- TabSize=1 Capabilities: [100] Advanced Error Reporting UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq+ ACSVoil- UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSVoil- UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSVoil- CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr- CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr- AERCap: First Error Pointer: 14, GenCap+ CGenEn- ChkCap+ ChkEn- Capabilities: [140] Virtual Channel <?> Kernel driver in use: ath5k_pci Kernel modules: ath5k WIFI card. The card has worked flawlessly so far. However, this morning after a reboot, NM failed to connect to my AP. I changed the card to be manually brought up with ifup and kInternet and rebooted several times with no improvement. It simply didn't reconnect. Only after checking the card in Windows and then rebooting back into OpenSuse did the card come alive again. /var/log/messages is massive with messages from the ath5k driver about not being able to reset the hardware as described in the following bugreport: http://bugzilla.kernel.org/show_bug.cgi?id=12080 It looks as if the card gets into a state where the ath5k driver cannot reset it. However, the windows driver seems to have corrected that and it started working after that again. I'll attach the messages log for the last 4 hours which covers the period of it: working, not working with NM after a reboot, not working with ifup, and then it working again after I booted into Windows and then back into Linux. I'll also attach the relevant NM logs. Cheers, Steve -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=450472 User swesemeyer@hotmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450472#c1 --- Comment #1 from Steve Wesemeyer <swesemeyer@hotmail.com> 2008-12-01 07:03:48 MST --- Created an attachment (id=256945) --> (https://bugzilla.novell.com/attachment.cgi?id=256945) relevant NetworkManager logs -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=450472 User swesemeyer@hotmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450472#c2 --- Comment #2 from Steve Wesemeyer <swesemeyer@hotmail.com> 2008-12-01 07:05:30 MST --- This is with Factory updates as of this morning. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=450472 Andreas Jaeger <aj@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |kernel-maintainers@forge.provo.novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=450472 Jeff Mahoney <jeffm@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kernel-maintainers@forge.provo.novell.com |jbenc@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=450472 User jslaby@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450472#c4 --- Comment #4 from Jiri Slaby <jslaby@novell.com> 2008-12-08 03:44:51 MST --- Could you identify kernel (e.g. from older /var/log/messages) which kernel have you been using till Dec 1? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=450472 User swesemeyer@hotmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450472#c5 --- Comment #5 from Steve Wesemeyer <swesemeyer@hotmail.com> 2008-12-08 08:39:58 MST --- Unfortunately not as I did a completer re-install on Friday (5th) using RC1. Sorry... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=450472 User jslaby@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450472#c6 --- Comment #6 from Jiri Slaby <jslaby@novell.com> 2008-12-08 09:47:06 MST --- Nevermind, could you try a kernel from: http://labs.suse.cz/jslaby/bug-446541/ ? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=450472 Jiri Slaby <jslaby@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |swesemeyer@hotmail.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=450472 User swesemeyer@hotmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450472#c7 --- Comment #7 from Steve Wesemeyer <swesemeyer@hotmail.com> 2008-12-10 03:42:18 MST --- Hiya, I'm now running : Linux NC10Linux 2.6.27.8-20081208_e022b172-default #1 SMP 2008-12-06 21:53:01 +0100 i686 i686 i386 GNU/Linux Is there anything else that you want me to do? BTW, I looked at bug 446541 and it does look as if my bug is a dupe. Note that since I reported the bug, I had no further instances of this behaviour occurring. Cheers, Steve -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=450472 User swesemeyer@hotmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450472#c8 --- Comment #8 from Steve Wesemeyer <swesemeyer@hotmail.com> 2008-12-13 08:20:52 MST --- Created an attachment (id=259927) --> (https://bugzilla.novell.com/attachment.cgi?id=259927) relevant messages log -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=450472 User swesemeyer@hotmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450472#c9 Steve Wesemeyer <swesemeyer@hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|swesemeyer@hotmail.com | --- Comment #9 from Steve Wesemeyer <swesemeyer@hotmail.com> 2008-12-13 08:24:23 MST --- I have now encountered the same problem again. This morning I connected to a WIFI point at my local LUG meeting. I suspended the laptop (suspend2ram) and when I started it at home it would not reconnect. Please see attached log in comment #8 for the relevant message log. It covers the period from the last successful connection at home to the one at the LUG and then the failure at home. Please let me know if you need any further information. Cheers, Steve -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=450472 User swesemeyer@hotmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450472#c10 --- Comment #10 from Steve Wesemeyer <swesemeyer@hotmail.com> 2008-12-13 09:04:00 MST --- This time it was actually so bad that even Windows did not recognise the card after a reboot. I had to power the laptop down completely and reboot into Windows to get it working again. Very worrying for a second! It looks as if the driver does not like to be suspended sometimes. It usually works fine but there must be scenarios when it gets corrupted somehow. I take it this driver cannot corrupt the card permanently (thinking of the recent e1000 problem)???? Cheers, Steve -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=450472 User jslaby@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450472#c11 Jiri Slaby <jslaby@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |DUPLICATE --- Comment #11 from Jiri Slaby <jslaby@novell.com> 2009-01-02 04:53:14 MST --- No(In reply to comment #10 from Steve Wesemeyer)
I take it this driver cannot corrupt the card permanently (thinking of the recent e1000 problem)????
No, it doesn't overwrite any parts of the eeproms like in the e1000e case. This only makes the processor on the card to loop somewhere so that it doesn't even respond to the PCI bus commands unless you power off and on the machine. Also there are 2 patches around which should fix the issue which we will use in our kernels. *** This bug has been marked as a duplicate of bug 446541 *** https://bugzilla.novell.com/show_bug.cgi?id=446541 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com