Bug 44251
| Summary: | iwl4965 driver crashes randomly. | ||
|---|---|---|---|
| Product: | Drivers | Reporter: | Istvan Toth (tothi) |
| Component: | network-wireless | Assignee: | Stanislaw Gruszka (stf_xl) |
| Status: | CLOSED WILL_NOT_FIX | ||
| Severity: | high | CC: | alan, chris, linville, stf_xl |
| Priority: | P1 | ||
| Hardware: | x86-64 | ||
| OS: | Linux | ||
| Kernel Version: | 3.5.0 | Subsystem: | |
| Regression: | No | Bisected commit-id: | |
| Attachments: |
syslog: iwl4965 crash
full dmesg output lspci -vvnn as root DMI table (output of dmidecode as root) /proc/interrupts /proc/mtrr output of ver_linux script in kernel tree iwlegacy_tracing_for_3.5.patch trace output after iwl4965 crash (using iwlegacy_tracing_for_3.5.patch) dmesg after iwl4965 crash (using iwlegacy_tracing_for_3.5.patch) trace output (w/16M buffer) after iwl4965 crash (running kernel 3.5.0-rc7) dmesg after iwl4965 crash (running kernel 3.5.0-rc7) |
||
|
Description
Istvan Toth
2012-07-04 19:55:32 UTC
Created attachment 74831 [details]
full dmesg output
my full dmesg output.
(last lines after iwl4965 crash: inserting an atheros cardbus wireless card. it works fluently...)
Created attachment 74841 [details]
lspci -vvnn as root
Created attachment 74851 [details]
DMI table (output of dmidecode as root)
Created attachment 74861 [details]
/proc/interrupts
Created attachment 74871 [details]
/proc/mtrr
Created attachment 74881 [details]
output of ver_linux script in kernel tree
Looks like firmware hangs so bad that is not possible to reset it. Or that could be some PCIe bus problems. Anyway nothing that would be easy to solve, but there are few things to try: there are some pending fixes that _maybe_ help with this problem: http://marc.info/?l=linux-wireless&m=134140106808740&w=2 http://marc.info/?l=linux-wireless&m=134140341109543&w=2 Please apply those patches and see if they help by a chance. If not, I will need to get debugging logs, I'll let you know how to capture that. Patches from above comments are now applied on 3.5-rc7 kernel. Does the problem still occurs on that version or later? pff... :) I've began testing on 3.5-rc7. I've also applied your patches without looking at the source. :) the patch ran without errors so maybe it wasn't harmful. :) so the testing is in progress: there is no error yet. unfortunately I've encountered the same bug with the patched rc6 kernel and using the stock rc7 kernel too. :( Created attachment 76671 [details] iwlegacy_tracing_for_3.5.patch Debug patch. How to use it is described here: https://bugzilla.kernel.org/show_bug.cgi?id=42766#c16 except we are on 3.5 kernel now, and looking for "Queue stuck" or first microcode error. is it possible to use it for the latest 3.6-rc1? the question is answered: the simple answer is no, the patch doesn't work out-of-the-box with 3.6-rc1. so i'm using it with 3.5-rc7. Created attachment 76811 [details]
trace output after iwl4965 crash (using iwlegacy_tracing_for_3.5.patch)
Created attachment 76821 [details]
dmesg after iwl4965 crash (using iwlegacy_tracing_for_3.5.patch)
related to trace.txt
I'm sorry, but trace does not include amount of information I expect to see. Seems trace buffer size defaults was changed. Please increase buffer size (by following command) after "mount -t debugfs debugfs /sys/kernel/debug/" and before "modprobe iwl4965 debug=0x47833fff" echo 16384 > /sys/kernel/debug/tracing/buffer_size_kb Sorry again for wrong instructions. Created attachment 77851 [details]
trace output (w/16M buffer) after iwl4965 crash (running kernel 3.5.0-rc7)
finally got it.
Created attachment 77861 [details]
dmesg after iwl4965 crash (running kernel 3.5.0-rc7)
and the dmesg log. maybe it's useful...h
Sorry, this will not be fixed. |