Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#16705 - [kernel26] ath5k module crashes after resuming from suspend2ram on 2.6.31.4-1

Attached to Project: Arch Linux
Opened by Panagiotis Papadopoulos (pano) - Saturday, 17 October 2009, 10:50 GMT
Last edited by Tobias Powalowski (tpowa) - Friday, 08 January 2010, 11:15 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas Bächler (brain0)
Architecture i686
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

After resuming from the suspend2ram mode, my wireless card is not working: Wicd (and iwlist) cannot find any wlan access points.
Looking into the system log, I saw that the ath5k module probably has crashed. If I rmmod the module and modprobe it again, wireless stuff works again.
On previous kernel version this bug did not appear at all.


Additional info:
* 2.6.31.4-1

I attached a excerpt from my sytem log.
   system.log (5.3 KiB)
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Friday, 08 January 2010, 11:15 GMT
Reason for closing:  Fixed
Comment by Gerardo Exequiel Pozzi (djgera) - Saturday, 17 October 2009, 14:48 GMT
  • Field changed: Status (Unconfirmed → Assigned)
  • Field changed: Category (Packages: Core → Upstream Bugs)
  • Task assigned to Tobias Powalowski (tpowa)
Please request this to upstream if not already reported on LKML with CC to maintainer of the ath5k and/or to bugzilla. This is the way to solve these type of issues. Thanks.
Comment by Laszlo Papp (djszapi) - Sunday, 06 December 2009, 18:42 GMT
Status, can it be closed ?
Comment by Panagiotis Papadopoulos (pano) - Sunday, 06 December 2009, 19:31 GMT
Currently running 2.6.31.6-1 and I still have the mentioned problem. I forgot to report this at the kernel bugtracker though :-/
Will do tomorrow, I promise ;-)
Comment by Laszlo Papp (djszapi) - Sunday, 06 December 2009, 19:41 GMT
okay, and don't forget to link that report here.
Comment by Panagiotis Papadopoulos (pano) - Sunday, 06 December 2009, 21:47 GMT
I found the time to report it:
http://bugzilla.kernel.org/show_bug.cgi?id=14756
Comment by Panagiotis Papadopoulos (pano) - Friday, 08 January 2010, 11:14 GMT
this has been fixed, with the 2.6.32 kernel

Loading...