Bug 10334
| Summary: | iwlwifi: circular locking on suspend | ||
|---|---|---|---|
| Product: | Drivers | Reporter: | Mircea Gherzan (mgherzan) |
| Component: | network-wireless | Assignee: | drivers_network-wireless (drivers_network-wireless) |
| Status: | CLOSED PATCH_ALREADY_AVAILABLE | ||
| Severity: | normal | CC: | bunk, reinette.chatre |
| Priority: | P1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Kernel Version: | 2.6.24.4 | Subsystem: | |
| Regression: | --- | Bisected commit-id: | |
| Bug Depends on: | |||
| Bug Blocks: | 7216 | ||
| Attachments: |
relevant dmesg on suspend
another suspend, with wireless OFF |
||
Created attachment 15454 [details]
relevant dmesg on suspend
Created attachment 15555 [details]
another suspend, with wireless OFF
It seems that the issue remains even with the wireless interface not associated (RFKILL switch ON).
Is this happening with 2.6.25 or later? No, it is not happening with 2.6.25. Thanks for this update. |
Latest working kernel version: Earliest failing kernel version: Distribution: Debian Sid Hardware Environment: Fujitsu-Siemens E8110 notebook, T2400, 1.5G RAM, IWL3945 Software Environment: GNOME 2.22, vanilla kernel Problem Description: [ 1871.551306] ======================================================= [ 1871.551311] [ INFO: possible circular locking dependency detected ] [ 1871.551315] 2.6.24.4-pso #1 [ 1871.551318] ------------------------------------------------------- [ 1871.551322] bash/4519 is trying to acquire lock: [ 1871.551325] (iwl3945){--..}, at: [<c013997d>] cleanup_workqueue_thread+0xd/0x70 [ 1871.551339] [ 1871.551340] but task is already holding lock: [ 1871.551343] (workqueue_mutex){--..}, at: [<c0139ae2>] workqueue_cpu_callback+0x102/0x130 [ 1871.551352] [ 1871.551353] which lock already depends on the new lock. Steps to reproduce: sudo bash -c "echo mem > /sys/power/state" with the wireless interface associated