Bug 12526 - iwlagn crash on shutdown
Summary: iwlagn crash on shutdown
Status: REJECTED UNREPRODUCIBLE
Alias: None
Product: Drivers
Classification: Unclassified
Component: network-wireless (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: drivers_network-wireless@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-23 03:02 UTC by Mircea Gherzan
Modified: 2009-01-30 11:09 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.6.28
Subsystem:
Regression: ---
Bisected commit-id:


Attachments
Call trace photo (970.42 KB, image/jpeg)
2009-01-23 05:28 UTC, Mircea Gherzan
Details

Description Mircea Gherzan 2009-01-23 03:02:42 UTC
Latest working kernel version: -
Earliest failing kernel version: 2.6.28
Distribution: Debian Sid
Hardware Environment: Lenovo T500, IWL 5300 AGN
Software Environment: wpa_supplicant 0.6.4-3
Problem Description: kernel crashes on shutdown from the Gnome environment, only when on battery, and wlan0 is not associated 

Steps to reproduce: start the machine on battery, make sure that wpa_supplicant doesn't associate, wait a bit and then shutdown from the GNOME menu.
Comment 1 Mircea Gherzan 2009-01-23 05:28:50 UTC
Created attachment 19953 [details]
Call trace photo
Comment 2 Reinette Chatre 2009-01-28 10:59:11 UTC
I don't know if this will be possible considering the shutdown scenario ... but could you please try to capture this error from another system using netconsole? I assume this trace does not show up in your system logs after you boot up again ... have you tried to change your syslog.conf to include all kernel messages to a file?

Does this happen very time? Would it be possible to send a better photo, unfortunately in this photo the top of the output is blurry? You can send a few photos.
Comment 3 Mircea Gherzan 2009-01-29 18:27:16 UTC
Unfortunately, even though I tried a lot of times, I cannot reproduce
the bug on 2.6.28.2.
Comment 4 Reinette Chatre 2009-01-30 09:37:41 UTC
Mircea,

Thank you very much for trying to reproduce it.  Could you please close this bug? If you do encounter it again, please create a new bug for it. The problem you encountered was a crash in "thread_info" - so there could have been a fix in that area between 2.6.28 and 2.6.28.2. 

Thank you

Note You need to log in before you can comment on or make changes to this bug.