From: Darren Salt <linux@youmustbejoking.demon.co.uk>
To: linux-kernel@vger.kernel.org
Cc: gregkh@suse.de
Subject: [BUG 2.6.30] Panic in rt2860sta when disabling wireless (eeepc)
Date: Fri, 12 Jun 2009 18:12:08 +0100 [thread overview]
Message-ID: <506FC67D10%linux@youmustbejoking.demon.co.uk> (raw)
I'm seeing the following panic when I disable wireless on my 901 if the
interface is associated: Fn-F2 with current eeepc-acpi-scripts git reliably
triggers it, as does writing 0 to /etc/class/rfkill/rfkill0/state.
(I've also noticed that, should this panic occur while X is active,
inteldrmfb doesn't quite manage to switch back to text mode and not all of
the text may be sent via netconsole.)
BUG: unable to handle kernel NULL pointer dereference at 0000000f
IP: [<c02f1c87>] RTMPWriteTxDescriptor+0xd/0x3f
*pde = 00000000
Oops: 0000 [#1] PREEMPT SMP
last sysfs file: /sys/devices/LNXSYSTM:00/device:00/ASUS010:00/rfkill/rfkill0/state
Modules linked in: rfcomm l2cap bluetooth joydev uvcvideo videodev v4l1_compat
Pid: 174, comm: kacpi_notify Not tainted (2.6.30-eee901 #2) 901
EIP: 0060:[<c02f1c87>] EFLAGS: 00010202 CPU: 1
EIP is at RTMPWriteTxDescriptor+0xd/0x3f
EAX: f87c2000 EBX: 00000000 ECX: 00000001 EDX: 00000000
ESI: 00000000 EDI: 0000002a EBP: 00000000 ESP: f7229de0
DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068
Process kacpi_notify (pid: 174, ti=f7228000 task=f70bac60 task.ti=f7228000)
Stack:
00000000 f87c2000 c032c632 00000000 f6759430 f87c2000 00000001 c02f38cf
f6759420 0000002a f6745480 031f5096 f87c5980 00745480 f6759420 00000001
00000001 0000002a f6759420 0000002a f6759420 f87c2000 f670a800 00000000
Call Trace:
[<c032c632>] ? RtmpPCIMgmtKickOut+0x3a/0xc7
[<c02f38cf>] ? MlmeHardTransmitMgmtRing+0x263/0x278
[<c02f3dba>] ? MiniportMMRequest+0x103/0x16d
[<c0307692>] ? MlmeDisassocReqAction+0x116/0x1a2
[<c031bf8b>] ? rt28xx_close+0xe8/0x1ef
[<c0214fd0>] ? acpi_os_execute_deferred+0x0/0x25
[<c031c119>] ? MainVirtualIF_close+0x2e/0x39
[<c0369a1b>] ? dev_close+0x5b/0x73
[<c0369a9f>] ? rollback_registered+0x6c/0xda
[<c0369b3c>] ? unregister_netdevice+0x2f/0x54
[<c0369b70>] ? unregister_netdev+0xf/0x15
[<c040e9d2>] ? rt2860_remove_one+0x30/0x82
[<c020247a>] ? pci_device_remove+0x16/0x35
[<c027fb15>] ? __device_release_driver+0x42/0x60
[<c027fbc8>] ? device_release_driver+0x15/0x1e
[<c027f8f9>] ? bus_remove_device+0x55/0x60
[<c027e0bb>] ? device_del+0xe9/0x125
[<c027e0ff>] ? device_unregister+0x8/0x10
[<c01fee10>] ? pci_stop_dev+0x20/0x3a
[<c01feec1>] ? pci_remove_bus_device+0x9/0x8f
[<c032d20f>] ? eeepc_rfkill_notify+0x9f/0xbd
[<c02210dd>] ? acpi_ev_notify_dispatch+0x4c/0x55
[<c0214fed>] ? acpi_os_execute_deferred+0x1d/0x25
[<c012cef4>] ? worker_thread+0x106/0x192
[<c012f430>] ? autoremove_wake_function+0x0/0x2b
[<c012cdee>] ? worker_thread+0x0/0x192
[<c012f360>] ? kthread+0x42/0x6a
[<c012f31e>] ? kthread+0x0/0x6a
[<c010321f>] ? kernel_thread_helper+0x7/0x10
Code: 00 03 45 28 8a 53 07 88 43 06 0f b6 c4 83 e0 0f 83 e2 f0 09 c2 88 53 07 58 5b 5e 5f 5d c3 56 89 d6 83 a0 28 f0 01 00 ef 84 c9 53 <8a> 5e 0f 0f 95 c1 8a 54 24 0c 83 e3 f8 83 e2 03 09 cb 01 d2 09
EIP: [<c02f1c87>] RTMPWriteTxDescriptor+0xd/0x3f SS:ESP 0068:f7229de0
CR2: 000000000000000f
---[ end trace f918b4539928a58c ]---
Kernel panic - not syncing: Fatal exception in interrupt
--
| Darren Salt | linux at youmustbejoking | nr. Ashington, | Doon
| Debian GNU/Linux | or ds ,demon,co,uk | Northumberland | Army
| + Output less CO2 => avoid massive flooding. TIME IS RUNNING OUT *FAST*.
I am not young enough to know everything.
reply other threads:[~2009-06-12 17:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=506FC67D10%linux@youmustbejoking.demon.co.uk \
--to=linux@youmustbejoking.demon.co.uk \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®