[Solved] Possible kernel panic?

doug piston · 2013-02-20 01:34:59

I booted up my PC, logged in and started x. I am not at my home so I started wicd-curses to login to my school's network. Machine seem to put me into what I think is tty2. I hit ctrl+alt+f1 and get back to my xsesssion. At this point I re-run wicd-curses and it just sits there at the prompt(Htop did work). Try to reboot with the command 'reboot' and it seems to put me back into tty2. Hangs there. Power button does not work and have to physically pull the battery to get out

I am still new to linux(Couple years now) and this is the first time I think I've seen a kernel panic.

Feb 19 17:14:58 watson kernel: wlan0: authenticate with 00:25:61:92:f4:23
Feb 19 17:14:58 watson kernel: wlan0: send auth to 00:25:61:92:f4:23 (try 1/3)
Feb 19 17:14:58 watson kernel: wlan0: authenticated
Feb 19 17:14:58 watson kernel: wlan0: associate with 00:25:61:92:f4:23 (try 1/3)
Feb 19 17:14:58 watson kernel: wlan0: RX AssocResp from 00:25:61:92:f4:23 (capab=0xc21 status=0 aid=1)
Feb 19 17:14:58 watson kernel: wlan0: associated
Feb 19 17:14:58 watson kernel: wlan0: deauthenticating from 00:25:61:92:f4:23 by local choice (reason=3)
Feb 19 17:14:59 watson kernel: wlan0: deauthenticating from           (null) by local choice (reason=3)
Feb 19 17:14:59 watson kernel: BUG: unable to handle kernel NULL pointer dereference at           (null)
Feb 19 17:14:59 watson kernel: IP: [<ffffffffa03f561f>] ieee80211_send_deauth_disassoc+0x3f/0x130 [mac80211]
Feb 19 17:14:59 watson kernel: PGD 22bb34067 PUD 232f33067 PMD 0 
Feb 19 17:14:59 watson kernel: Oops: 0000 [#1] PREEMPT SMP 
Feb 19 17:14:59 watson kernel: Modules linked in: i2400m_usb i2400m wimax joydev uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core videodev me
Feb 19 17:14:59 watson kernel: CPU 1 
Feb 19 17:14:59 watson dhcpcd[1637]: version 5.6.4 starting
Feb 19 17:14:59 watson kernel: Pid: 1636, comm: iwconfig Tainted: P           O 3.7.9-1-ck #1 SAMSUNG ELECTRONICS CO., LTD. RC512/RC512
Feb 19 17:14:59 watson kernel: RIP: 0010:[<ffffffffa03f561f>]  [<ffffffffa03f561f>] ieee80211_send_deauth_disassoc+0x3f/0x130 [mac80211]
Feb 19 17:14:59 watson kernel: RSP: 0018:ffff8802343cbb08  EFLAGS: 00010202
Feb 19 17:14:59 watson kernel: RAX: 0000000000000000 RBX: ffff8802343cbb56 RCX: 0000000000000003
Feb 19 17:14:59 watson kernel: RDX: 00000000000000c0 RSI: 0000000000000000 RDI: ffff8802326b2800
Feb 19 17:14:59 watson kernel: RBP: ffff8802343cbb28 R08: 0000000000000001 R09: ffff8802343cbb56
Feb 19 17:14:59 watson kernel: R10: 0000000000000000 R11: 000000000000039c R12: ffff8802326b2800
Feb 19 17:14:59 watson kernel: R13: ffff8802343cbbc8 R14: ffff8802326205a0 R15: 0000000000000001
Feb 19 17:14:59 watson kernel: FS:  00007fb854988700(0000) GS:ffff88023fa20000(0000) knlGS:0000000000000000
Feb 19 17:14:59 watson kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Feb 19 17:14:59 watson kernel: CR2: 0000000000000000 CR3: 000000022c9fc000 CR4: 00000000000407e0
Feb 19 17:14:59 watson kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Feb 19 17:14:59 watson kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Feb 19 17:14:59 watson kernel: Process iwconfig (pid: 1636, threadinfo ffff8802343ca000, task ffff88022689aed0)
Feb 19 17:14:59 watson kernel: Stack:
Feb 19 17:14:59 watson kernel:  ffff8802326b2800 ffff8802326b2e88 ffff8802343cbbc8 ffff8802343cbb56
Feb 19 17:14:59 watson kernel:  ffff8802343cbba8 ffffffffa0410a12 0000000100000000 ffff8802326b2aac
Feb 19 17:14:59 watson kernel:  00000000000280da 00c0000000000246 ffff880200000000 ffffffff81888640
Feb 19 17:14:59 watson kernel: Call Trace:
Feb 19 17:14:59 watson kernel:  [<ffffffffa0410a12>] ieee80211_mgd_deauth+0x162/0x300 [mac80211]
Feb 19 17:14:59 watson kernel:  [<ffffffffa03e6538>] ieee80211_deauth+0x18/0x20 [mac80211]
Feb 19 17:14:59 watson kernel:  [<ffffffffa0290c55>] __cfg80211_mlme_deauth+0x75/0x90 [cfg80211]
Feb 19 17:14:59 watson kernel:  [<ffffffffa0294416>] __cfg80211_disconnect+0xf6/0x1d0 [cfg80211]
Feb 19 17:14:59 watson kernel:  [<ffffffffa0297c99>] cfg80211_mgd_wext_siwap+0x129/0x260 [cfg80211]
Feb 19 17:14:59 watson kernel:  [<ffffffffa0297025>] cfg80211_wext_siwap+0xd5/0xf0 [cfg80211]
Feb 19 17:14:59 watson kernel:  [<ffffffff8147802f>] ioctl_standard_call+0x5f/0xd0
Feb 19 17:14:59 watson kernel:  [<ffffffff813a384c>] ? __dev_get_by_name+0x6c/0x90
Feb 19 17:14:59 watson kernel:  [<ffffffff81478c50>] ? iw_handler_get_private+0x70/0x70
Feb 19 17:14:59 watson kernel:  [<ffffffff81477fd0>] ? call_commit_handler+0x40/0x40
Feb 19 17:14:59 watson kernel:  [<ffffffff81477e7e>] wireless_process_ioctl+0x16e/0x1b0
Feb 19 17:14:59 watson kernel:  [<ffffffff814781a4>] wext_handle_ioctl+0x74/0xc0
Feb 19 17:14:59 watson kernel:  [<ffffffff813aa9a9>] dev_ioctl+0xc9/0x5a0
Feb 19 17:14:59 watson kernel:  [<ffffffff8113b0d1>] ? handle_mm_fault+0x261/0x330
Feb 19 17:14:59 watson kernel:  [<ffffffff8138f4aa>] sock_ioctl+0xea/0x2a0
Feb 19 17:14:59 watson kernel:  [<ffffffff8117ea37>] do_vfs_ioctl+0x97/0x530
Feb 19 17:14:59 watson kernel:  [<ffffffff8116e9bb>] ? alloc_file+0x2b/0xd0
Feb 19 17:14:59 watson kernel:  [<ffffffff81189c07>] ? __fd_install+0x57/0x70
Feb 19 17:14:59 watson kernel:  [<ffffffff8117ef61>] sys_ioctl+0x91/0xb0
Feb 19 17:14:59 watson kernel:  [<ffffffff814af31d>] system_call_fastpath+0x1a/0x1f
Feb 19 17:14:59 watson kernel: Code: 4c 89 cb 4c 89 65 e8 49 89 fc 4c 89 6d f0 4c 89 75 f8 4c 8b b7 90 02 00 00 66 41 89 11 66 41 c7 41 02 00 00 66 41 c7 41 16 00 00 <8b> 06 41 89 41 04 0f b7 46 04 66 41 89 41 08 8b 87 50 08 00 00 
Feb 19 17:14:59 watson kernel: RIP  [<ffffffffa03f561f>] ieee80211_send_deauth_disassoc+0x3f/0x130 [mac80211]
Feb 19 17:14:59 watson kernel:  RSP <ffff8802343cbb08>
Feb 19 17:14:59 watson kernel: CR2: 0000000000000000
Feb 19 17:14:59 watson kernel: ---[ end trace c0148519e1723ee0 ]---
Feb 19 17:15:01 watson crond[1639]: pam_unix(crond:session): session opened for user jarvis by (uid=0)
Feb 19 17:15:01 watson CROND[1640]: (jarvis) CMD (/home/jarvis/.mutt/mailrun.sh)
Feb 19 17:15:01 watson CROND[1639]: (jarvis) CMDOUT (ERROR: Exceptions occurred during the run!)
Feb 19 17:15:01 watson CROND[1639]: (jarvis) CMDOUT (ERROR: Could not resolve name 'imap.gmail.com' for repository 'Gmail-Remote'. Make sure you have configured the server name correctly and that you are online.)
Feb 19 17:15:01 watson CROND[1639]: (jarvis) CMDOUT (ERROR: Could not resolve name 'imap.gmail.com' for repository 'Edcc-Remote'. Make sure you have configured the server name correctly and that you are online.)
Feb 19 17:15:01 watson CROND[1639]: pam_unix(crond:session): session closed for user jarvis
Feb 19 17:15:13 watson systemd[1]: Starting Getty on tty2...
Feb 19 17:15:13 watson systemd[1]: Started Getty on tty2.
Feb 19 17:16:11 watson dbus-daemon[288]: dbus[288]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service'
Feb 19 17:16:11 watson dbus[288]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service'
Feb 19 17:16:11 watson systemd[1]: Starting Authorization Manager...
Feb 19 17:16:11 watson polkitd[1785]: Started polkitd version 0.109
Feb 19 17:16:11 watson polkitd[1785]: Loading rules from directory /etc/polkit-1/rules.d
Feb 19 17:16:11 watson polkitd[1785]: Loading rules from directory /usr/share/polkit-1/rules.d
Feb 19 17:16:11 watson polkitd[1785]: Finished loading, compiling and executing 1 rules
Feb 19 17:16:11 watson dbus-daemon[288]: dbus[288]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Feb 19 17:16:11 watson dbus[288]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Feb 19 17:16:11 watson polkitd[1785]: Acquired the name org.freedesktop.PolicyKit1 on the system bus
Feb 19 17:16:11 watson systemd[1]: Started Authorization Manager.
Feb 19 17:16:11 watson polkitd[1785]: Registered Authentication Agent for unix-process:1782:13245 (system bus name :1.11 [/usr/bin/pkttyagent --notify-fd 6 --fallback], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
Feb 19 17:16:11 watson systemd-logind[292]: System is rebooting.

Linux watson 3.7.9-1-ck #1 SMP PREEMPT Sun Feb 17 18:44:00 EST 2013 x86_64 GNU/Linux

My question is, is this a kernel panic and should I be concerned/take some action or just brush it off?

Thanks for your time and hope to learn something from this.
Cheers.

Last edited by doug piston (2013-02-20 18:00:38)

ewaller · 2013-02-20 02:36:13

It is not a kernel panic. The kernel continued after a serious problem (an Oops) occurred with your wireless driver (I think). An 'Oops' is a serious bug; generally a dereference of a null pointer (it was in this case) But, the kernel was not so confused that it proceeded so that you could decide how to deal with it.

Did you initiate the shutdown at 17:16?

A kernel panic means that the kernel is so confused, that it decided it was unsafe to continue. When it finds itself in this state, it pretty much halts the system and flashes the LEDs on your keyboard until you power down or reset your system.

Should you be concerned? Yes. Keep an eye out and see if it happens again.

Last edited by ewaller (2013-02-20 03:03:12)

doug piston · 2013-02-20 03:00:51

I did initiate the shutdown. Thanks for the insight on the matter. It is the first time I've seen this on this install. Can't think of what might of set it off. I'll report back if I see it again.

Thank you.

Arch Linux

#1 2013-02-20 01:34:59

[Solved] Possible kernel panic?

#2 2013-02-20 02:36:13

Re: [Solved] Possible kernel panic?

#3 2013-02-20 03:00:51

Re: [Solved] Possible kernel panic?

Board footer