Arch Linux

c0degardener

Member

From: Salvador, Brazil

Registered: 2016-07-09

Posts: 5

Kernel panic when attempting to connect to wifi

Hey guys,

I've had this kernel panic issue when attempting to connect to a wifi network ever since I broke out my ~6 year old Lenovo Thinkpad T410 3 months ago. I can connect to the internet using ethernet without any issues. I'm fairly a fairly new Arch user, and while I've been using linux for about 6 years, this is the first time in my life that I'm really getting down in the weeds with my OS.

My laptop has a hardware wifi switch, so my workaround in the mean time has been to switch the wifi off and use ethernet for now.

Relevant information:

Relevant output from `lspci -k`

03:00.0 Network controller: Intel Corporation Centrino Wireless-N 1000 [Condor Peak]
        Subsystem: Intel Corporation Centrino Wireless-N 1000 BGN
        Kernel driver in use: iwlwifi
        Kernel modules: iwlwifi

Output from `iw dev`:

phy#0
	Interface wlp3s0
		ifindex 3
		wdev 0x1
		addr 00:26:c7:ec:78:70
		type managed
		txpower 0.00 dBm

Output from `ip link show wlp3s0`

3: wlp3s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether 00:26:c7:ec:78:70 brd ff:ff:ff:ff:ff:ff

Output from `dmesg | grep iwlwifi`

[   11.659198] iwlwifi 0000:03:00.0: can't disable ASPM; OS doesn't have ASPM control
[   11.723969] iwlwifi 0000:03:00.0: loaded firmware version 39.31.5.1 build 35138 op_mode iwldvm
[   11.749092] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEBUG disabled
[   11.749093] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEBUGFS disabled
[   11.749094] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEVICE_TRACING enabled
[   11.749095] iwlwifi 0000:03:00.0: Detected Intel(R) Centrino(R) Wireless-N 1000 BGN, REV=0x6C
[   11.749225] iwlwifi 0000:03:00.0: L1 Enabled - LTR Disabled
[   11.756590] iwlwifi 0000:03:00.0: RF_KILL bit toggled to disable radio.
[   12.134646] iwlwifi 0000:03:00.0 wlp3s0: renamed from wlan0

Kernel panic occurs when trying to connect to wifi network using `wifi-menu wlp3s0`

Output from `journalctl` from earlier today. I forced this crash to happen to attempting to run `wifi-menu wlp3s0`. This is very reproducable and occurs every time:

Jul 09 15:07:43 yellowstone kernel: iwl data: 00000000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
Jul 09 15:07:43 yellowstone kernel: iwl data: 00000010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
Jul 09 15:07:43 yellowstone kernel: ------------[ cut here ]------------
Jul 09 15:07:43 yellowstone kernel: WARNING: CPU: 2 PID: 258 at drivers/net/wireless/intel/iwlwifi/pcie/tx.c:1690 iwl_pcie_hcmd_complete+0x421/0x530 [iwlwifi]
Jul 09 15:07:43 yellowstone kernel: wrong command queue 0 (should be 4), sequence 0x0 readp=27 writep=28
Jul 09 15:07:43 yellowstone kernel: Modules linked in: intel_powerclamp coretemp kvm_intel joydev mousedev kvm arc4 iwldvm mac80211 irqbypass crct10dif_pclmul 
Jul 09 15:07:43 yellowstone kernel:  sch_fq_codel ip_tables x_tables ext4 crc16 jbd2 mbcache sr_mod cdrom sd_mod atkbd libps2 ahci libahci libata scsi_mod sdhc
Jul 09 15:07:43 yellowstone kernel: CPU: 2 PID: 258 Comm: irq/30-iwlwifi Tainted: G        W       4.6.3-1-ARCH #1
Jul 09 15:07:43 yellowstone kernel: Hardware name: LENOVO 2516CTO/2516CTO, BIOS 6IET74WW (1.34 ) 10/25/2010
Jul 09 15:07:43 yellowstone kernel:  0000000000000286 00000000fe00bf90 ffff88022e12fbc8 ffffffff812e54c2
Jul 09 15:07:43 yellowstone kernel:  ffff88022e12fc18 0000000000000000 ffff88022e12fc08 ffffffff8107a6bb
Jul 09 15:07:43 yellowstone kernel:  0000069a30203030 0000000000000000 0000000000000000 0000000000000000
Jul 09 15:07:43 yellowstone kernel: Call Trace:
Jul 09 15:07:43 yellowstone kernel:  [<ffffffff812e54c2>] dump_stack+0x63/0x81
Jul 09 15:07:43 yellowstone kernel:  [<ffffffff8107a6bb>] __warn+0xcb/0xf0
Jul 09 15:07:43 yellowstone kernel:  [<ffffffff8107a73f>] warn_slowpath_fmt+0x5f/0x80
Jul 09 15:07:43 yellowstone kernel:  [<ffffffffa093c051>] iwl_pcie_hcmd_complete+0x421/0x530 [iwlwifi]
Jul 09 15:07:43 yellowstone kernel:  [<ffffffffa08af9d8>] ? iwl_rx_dispatch+0xc8/0xe0 [iwldvm]
Jul 09 15:07:43 yellowstone kernel:  [<ffffffffa0936c73>] iwl_pcie_rx_handle+0x5e3/0x980 [iwlwifi]
Jul 09 15:07:43 yellowstone kernel:  [<ffffffffa0938485>] iwl_pcie_irq_handler+0x5b5/0xb10 [iwlwifi]
Jul 09 15:07:43 yellowstone kernel:  [<ffffffff810d6990>] ? irq_forced_thread_fn+0x70/0x70
Jul 09 15:07:43 yellowstone kernel:  [<ffffffff810d69b0>] irq_thread_fn+0x20/0x50
Jul 09 15:07:43 yellowstone kernel:  [<ffffffff810d6c8d>] irq_thread+0x12d/0x1c0
Jul 09 15:07:43 yellowstone kernel:  [<ffffffff815c34fd>] ? __schedule+0x8dd/0xad0
Jul 09 15:07:43 yellowstone kernel:  [<ffffffff810d6ab0>] ? wake_threads_waitq+0x30/0x30
Jul 09 15:07:43 yellowstone kernel:  [<ffffffff810d6b60>] ? irq_thread_dtor+0xb0/0xb0
Jul 09 15:07:43 yellowstone kernel:  [<ffffffff81099998>] kthread+0xd8/0xf0
Jul 09 15:07:43 yellowstone kernel:  [<ffffffff815c73c2>] ret_from_fork+0x22/0x40
Jul 09 15:07:43 yellowstone kernel:  [<ffffffff810998c0>] ? kthread_worker_fn+0x170/0x170
Jul 09 15:07:43 yellowstone kernel: ---[ end trace 1c0d12e66248df12 ]---

I'm still pretty new to linux in general and very new to Arch Linux. In all honesty, this is the first time I'm trying to debug an OS issue on my own, so I'm really not sure how to interpret this stack trace, or what my next steps should be. I've searched online and the Arch Linux Forums and Wiki for help with this issue and haven't come across the same issue anywhere here.

Could anyone give me some insight on what I should try next?

Thanks!

c0degardener

Member

From: Salvador, Brazil

Registered: 2016-07-09

Posts: 5

Re: Kernel panic when attempting to connect to wifi

Wanted to include the output from when I last attempted to cause the crash (and was successful). I began by first disconnecting my ethernet cable (indicated in the output), switched the wifi hardware button on, then attempted to connect to wifi using wifi-menu.

Jul 09 15:07:03 yellowstone dhcpcd[378]: enp0s25: carrier lost
Jul 09 15:07:03 yellowstone kernel: e1000e: enp0s25 NIC Link is Down
Jul 09 15:07:03 yellowstone dhcpcd[378]: enp0s25: deleting address fe80::d8c7:d615:e096:9029
Jul 09 15:07:03 yellowstone dhcpcd[378]: enp0s25: deleting route to 192.168.1.0/24
Jul 09 15:07:03 yellowstone dhcpcd[378]: enp0s25: deleting default route via 192.168.1.1
Jul 09 15:07:07 yellowstone kernel: ACPI Warning: \_SB.PCI0.PEG.VID._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20160108/nsargum
Jul 09 15:07:07 yellowstone kernel: ACPI Warning: \_SB.PCI0.PEG.VID._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20160108/nsargum
Jul 09 15:07:07 yellowstone kernel: nouveau 0000:01:00.0: DRM: suspending console...
Jul 09 15:07:07 yellowstone kernel: nouveau 0000:01:00.0: DRM: suspending display...
Jul 09 15:07:07 yellowstone kernel: nouveau 0000:01:00.0: DRM: evicting buffers...
Jul 09 15:07:07 yellowstone kernel: nouveau 0000:01:00.0: DRM: waiting for kernel channels to go idle...
Jul 09 15:07:07 yellowstone kernel: nouveau 0000:01:00.0: DRM: suspending client object trees...
Jul 09 15:07:07 yellowstone kernel: nouveau 0000:01:00.0: DRM: suspending kernel object tree...
Jul 09 15:07:08 yellowstone kernel: thinkpad_acpi: EC reports that Thermal Table has changed
Jul 09 15:07:13 yellowstone kernel: iwlwifi 0000:03:00.0: RF_KILL bit toggled to enable radio.
Jul 09 15:07:13 yellowstone systemd[1]: Starting Load/Save RF Kill Switch Status...
Jul 09 15:07:13 yellowstone systemd[1]: Started Load/Save RF Kill Switch Status.
Jul 09 15:07:42 yellowstone sudo[6252]:    brian : TTY=tty1 ; PWD=/home/brian ; USER=root ; COMMAND=/usr/bin/wifi-menu wlp3s0
Jul 09 15:07:42 yellowstone sudo[6252]: pam_unix(sudo:session): session opened for user root by brian(uid=0)
Jul 09 15:07:42 yellowstone kernel: iwlwifi 0000:03:00.0: L1 Enabled - LTR Disabled
Jul 09 15:07:42 yellowstone kernel: iwlwifi 0000:03:00.0: L1 Enabled - LTR Disabled
Jul 09 15:07:42 yellowstone kernel: iwlwifi 0000:03:00.0: Radio type=0x0-0x0-0x3
Jul 09 15:07:42 yellowstone kernel: iwlwifi 0000:03:00.0: L1 Enabled - LTR Disabled
Jul 09 15:07:42 yellowstone kernel: iwlwifi 0000:03:00.0: L1 Enabled - LTR Disabled
Jul 09 15:07:42 yellowstone kernel: iwlwifi 0000:03:00.0: Radio type=0x0-0x0-0x3

This is all of the output between those two events and right before the stack trace above ^

jasonwryan

Anarchist

From: .nz

Registered: 2009-05-09

Posts: 30,424

Website

Re: Kernel panic when attempting to connect to wifi

Moving to Kernel & Hardware...

---

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

madpierre

Member

Registered: 2016-05-27

Posts: 188

Re: Kernel panic when attempting to connect to wifi

c0degardner writes:

I've had this kernel panic issue...

Sorry, "kernel panic" is a vague explanation of your problem. What are you seeing and experiencing?

Is the OS current (# pacman -Syu)? Is the BIOS firmware current? Which DE are you using?

Last edited by madpierre (2016-07-12 00:04:33)

c0degardener

Member

From: Salvador, Brazil

Registered: 2016-07-09

Posts: 5

Re: Kernel panic when attempting to connect to wifi

Hmm guess I didn't realize that there were various manifestations of kernel panics..

The issue I was seeing from my end is that the computer would freeze and CapsLk key would flash. I googled this and read that it indicated a kernel panic. At one point I was able to see the words kernel panic appear on screen when forcing the crash in a tty. When the freeze occurs I cannot switch to any tty sessions either and am forced to poweroff with the laptop power button.

The OS is current, I'm familiar with the Forum rules and didn't (and won't in the future) post any help requests without having my OS current.

I'll look into the BIOS upgrade now. This laptop is about 6 years old now so very good suggestion. Thanks!

I'm assuming by DE you mean Desktop Environment (still pretty new to the lingo around here). I don't use a DE, just xorg with xinit and i3.

Thanks for the suggestions and response. I'll get back to you with the details on the BIOS update and if it needs an update, I'll look into updating it.

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 19,774

Re: Kernel panic when attempting to connect to wifi

Nope, that is a kernel panic    Sometimes people assert there is a panic when, in reality, something else is going on.  Not so here.

Afore we go any further, is this an Intel processor?  Have you installed, configured, and verified that you microcode updates are being installed at boot time?

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

madpierre

Member

Registered: 2016-05-27

Posts: 188

Re: Kernel panic when attempting to connect to wifi

c0degardener writes:

I'm assuming by DE you mean Desktop Environment

Thanks for the timely response. Yes. My apologies.

ewaller will guide you down a good road.

c0degardener

Member

From: Salvador, Brazil

Registered: 2016-07-09

Posts: 5

Re: Kernel panic when attempting to connect to wifi

Sorry for the long turnaround, wanted to make sure my BIOS is now up to date (took me a bit to figure out how to burn a BIOS .iso from Lenovo to usb stick).

To answer your questions, this is an intel processor. I followed the instructions for verifying microcode updates at boot time.

>>> dmesg | grep microcode
[    0.000000] microcode: microcode updated early to revision 0x4, date = 2013-06-28
[    1.006629] microcode: CPU0 sig=0x20655, pf=0x10, revision=0x4
[    1.006639] microcode: CPU1 sig=0x20655, pf=0x10, revision=0x4
[    1.006679] microcode: CPU2 sig=0x20655, pf=0x10, revision=0x4
[    1.006689] microcode: CPU3 sig=0x20655, pf=0x10, revision=0x4
[    1.006730] microcode: Microcode Update Driver: v2.01 <tigran@aivazian.fsnet.co.uk>, Peter Oruba

Attempted to reproduce the crash after updating Arch (new updates this morning), updating BIOS, and verifying microcode updates. Unfortunately the crash still occurs.