Comment 57 for bug 200509

Revision history for this message
Greg Smith (gsmith-gregsmith) wrote :

I doubt I have exactly the same issue here as other posters. My problem is that my Intel 5100AGN wireless works fine against most 802.11B/G networks, but crashes oddly with a microcode error when I try to connect to my primary N network. I even get the right IP address with DHCP, but I can't actually ping anything. It looks like the Microcode restart leaves me in that odd state.

However, I have at least managed to get a useful debug log running against my Jaunty system. Took a bit of experimentation though; here's what I did:

1) Install the iwlwifi-debug-dkms .deb from TJ's PPA area at https://launchpad.net/~intuitivenipple/+archive/ppa , which you need in order to have a version of the kernel modules that are configured with debug support enabled.

2) Tried the instructions shown by "man iwlwifi". These did not work for me; I got:

  iwlcore: Unknown parameter `debug'

3) Tried this alternative instead, as suggested from the Intel Wireless mailing lists:

  modprobe iwlagn debug50=0x43fff

This worked, got lots of additional detail.

Based on that experience, I think the iwlwifi docs need two changes:

-Change "debug" to "debug50" for all the options examples
-The directory for the debug_level control is missing the card location subdirectory. I found the file in /sys/bus/pci/drivers/iwlagn/0000:03:00.0/debug_level on my system. (the 0000:03:00.0 part is missing from the description in the man page).

After those I think that PPA package will be ready for more people to use.

Here's what the main additional detail when the error pops up looks like for me:

iwlagn: Microcode SW error detected. Restarting 0x2000000.
iwlagn: Start IWL Error Log Dump:
iwlagn: Status: 0x000212E4, count: 5
iwlagn: Desc Time data1 data2 line
iwlagn: SYSASSERT (#5) 1472749560 0x40808015 0x00008904 1353
iwlagn: blink1 blink2 ilink1 ilink2
iwlagn: 0x03768 0x03768 0x0090E 0x00000
iwlagn: Start IWL Event Log Dump: display count 512, wraps 8

That's followed by a big dump of data. Attached file has everything.