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.