-tip: origin tree boot crash
in [Kernel]
|
Prev: [PATCH] backlight: lcd: Add Epson L4F00242T03 LCD driver.
Next: improve the performance of large sequential write NFS workloads
From: Len Brown on 26 Dec 2009 15:20 > [ 28.643216] evbug.c: Connected device: input1 (Dell WMI hotkeys at wmi/input0) > [ 28.650449] BUG: unable to handle kernel NULL pointer dereference at 00000014 > [ 28.654439] IP: [<c17f7f21>] wmi_install_notify_handler+0x31/0x70 Rather than reverting the broken patch that caused wmi to load, does applying this patch to deal with the broken error handling cause the oops to go away? thanks, -Len From d11e073ee3e3091d9190dace97ce480e960cca1b Mon Sep 17 00:00:00 2001 From: Len Brown <len.brown(a)intel.com> Date: Fri, 25 Dec 2009 23:14:26 -0500 Subject: [PATCH] Revert "wmi: Free the allocated acpi objects through wmi_get_event_data" X-Patchwork-Hint: ignore This reverts commit 3e9b988e4edf065d39c1343937f717319b1c1065. Reported-by: Sedat Dilek <sedat.dilek(a)googlemail.com> Tested-by Maciej Rutecki <maciej.rutecki(a)gmail.com> Signed-off-by: Len Brown <len.brown(a)intel.com> --- drivers/platform/x86/dell-wmi.c | 1 - drivers/platform/x86/hp-wmi.c | 2 -- drivers/platform/x86/wmi.c | 4 ++-- 3 files changed, 2 insertions(+), 5 deletions(-) diff --git a/drivers/platform/x86/dell-wmi.c b/drivers/platform/x86/dell-wmi.c index 916ccb2..46244c6 100644 --- a/drivers/platform/x86/dell-wmi.c +++ b/drivers/platform/x86/dell-wmi.c @@ -238,7 +238,6 @@ static void dell_wmi_notify(u32 value, void *context) input_sync(dell_wmi_input_dev); } } - kfree(obj); } diff --git a/drivers/platform/x86/hp-wmi.c b/drivers/platform/x86/hp-wmi.c index 8781d8f..222ab57 100644 --- a/drivers/platform/x86/hp-wmi.c +++ b/drivers/platform/x86/hp-wmi.c @@ -388,8 +388,6 @@ static void hp_wmi_notify(u32 value, void *context) } else printk(KERN_INFO "HP WMI: Unknown key pressed - %x\n", eventcode); - - kfree(obj); } static int __init hp_wmi_input_setup(void) diff --git a/drivers/platform/x86/wmi.c b/drivers/platform/x86/wmi.c index 9f93d6c..e425a86 100644 --- a/drivers/platform/x86/wmi.c +++ b/drivers/platform/x86/wmi.c @@ -540,8 +540,8 @@ EXPORT_SYMBOL_GPL(wmi_remove_notify_handler); /** * wmi_get_event_data - Get WMI data associated with an event * - * @event: Event to find - * @out: Buffer to hold event data. out->pointer should be freed with kfree() + * @event - Event to find + * &out - Buffer to hold event data * * Returns extra data associated with an event in WMI. */ -- 1.6.6.rc4.11.g129a5 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Len Brown on 26 Dec 2009 23:30 On Sat, 26 Dec 2009, Len Brown wrote: > > [ 28.643216] evbug.c: Connected device: input1 (Dell WMI hotkeys at wmi/input0) > > [ 28.650449] BUG: unable to handle kernel NULL pointer dereference at 00000014 > > [ 28.654439] IP: [<c17f7f21>] wmi_install_notify_handler+0x31/0x70 > > Rather than reverting the broken patch that caused wmi to load, > does applying this patch to deal with the broken error handling > cause the oops to go away? > Subject: [PATCH] Revert "wmi: Free the allocated acpi objects through wmi_get_event_data" > > This reverts commit 3e9b988e4edf065d39c1343937f717319b1c1065. These kfree's look correct, assuming we properly check the return status. So perhaps instead you can test the patch below? thanks, -Len From 5caa3ab36da77d59017cff9b9d1e910862b489e7 Mon Sep 17 00:00:00 2001 Message-Id: <5caa3ab36da77d59017cff9b9d1e910862b489e7.1261887124.git.len.brown(a)intel.com> In-Reply-To: <51b0f1c2b8c32ee44ff01ef74599a1f17e4fc565.1261887124.git.len.brown(a)intel.com> References: <51b0f1c2b8c32ee44ff01ef74599a1f17e4fc565.1261887124.git.len.brown(a)intel.com> From: Len Brown <len.brown(a)intel.com> Date: Sat, 26 Dec 2009 23:02:24 -0500 Subject: [PATCH 3/3] dell-wmi, hp-wmi, msi-wmi: check wmi_get_event_data() return value X-Patchwork-Hint: ignore When acpi_evaluate_object() is passed ACPI_ALLOCATE_BUFFER, the caller must kfree the returned buffer if AE_OK is returned. The callers of wmi_get_event_data() pass ACPI_ALLOCATE_BUFFER, and thus must check its return value before accessing or kfree() on the buffer. Signed-off-by: Len Brown <len.brown(a)intel.com> --- drivers/platform/x86/dell-wmi.c | 7 ++++++- drivers/platform/x86/hp-wmi.c | 7 ++++++- drivers/platform/x86/msi-wmi.c | 7 ++++++- 3 files changed, 18 insertions(+), 3 deletions(-) diff --git a/drivers/platform/x86/dell-wmi.c b/drivers/platform/x86/dell-wmi.c index 4c7e702..500af8c 100644 --- a/drivers/platform/x86/dell-wmi.c +++ b/drivers/platform/x86/dell-wmi.c @@ -202,8 +202,13 @@ static void dell_wmi_notify(u32 value, void *context) struct acpi_buffer response = { ACPI_ALLOCATE_BUFFER, NULL }; static struct key_entry *key; union acpi_object *obj; + acpi_status status; - wmi_get_event_data(value, &response); + status = wmi_get_event_data(value, &response); + if (status != AE_OK) { + printk(KERN_INFO "dell-wmi: bad event status 0x%x\n", status); + return; + } obj = (union acpi_object *)response.pointer; diff --git a/drivers/platform/x86/hp-wmi.c b/drivers/platform/x86/hp-wmi.c index 18bf741..5b648f0 100644 --- a/drivers/platform/x86/hp-wmi.c +++ b/drivers/platform/x86/hp-wmi.c @@ -338,8 +338,13 @@ static void hp_wmi_notify(u32 value, void *context) static struct key_entry *key; union acpi_object *obj; int eventcode; + acpi_status status; - wmi_get_event_data(value, &response); + status = wmi_get_event_data(value, &response); + if (status != AE_OK) { + printk(KERN_INFO "hp-wmi: bad event status 0x%x\n", status); + return; + } obj = (union acpi_object *)response.pointer; diff --git a/drivers/platform/x86/msi-wmi.c b/drivers/platform/x86/msi-wmi.c index f746c67..f5f70d4 100644 --- a/drivers/platform/x86/msi-wmi.c +++ b/drivers/platform/x86/msi-wmi.c @@ -149,8 +149,13 @@ static void msi_wmi_notify(u32 value, void *context) static struct key_entry *key; union acpi_object *obj; ktime_t cur; + acpi_status status; - wmi_get_event_data(value, &response); + status = wmi_get_event_data(value, &response); + if (status != AE_OK) { + printk(KERN_INFO DRV_PFX "bad event status 0x%x\n", status); + return; + } obj = (union acpi_object *)response.pointer; -- 1.6.0.6 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Ingo Molnar on 28 Dec 2009 04:50 * Len Brown <lenb(a)kernel.org> wrote: > On Sat, 26 Dec 2009, Len Brown wrote: > > > > [ 28.643216] evbug.c: Connected device: input1 (Dell WMI hotkeys at wmi/input0) > > > [ 28.650449] BUG: unable to handle kernel NULL pointer dereference at 00000014 > > > [ 28.654439] IP: [<c17f7f21>] wmi_install_notify_handler+0x31/0x70 > > > > Rather than reverting the broken patch that caused wmi to load, > > does applying this patch to deal with the broken error handling > > cause the oops to go away? > > > Subject: [PATCH] Revert "wmi: Free the allocated acpi objects through wmi_get_event_data" > > > > This reverts commit 3e9b988e4edf065d39c1343937f717319b1c1065. > > These kfree's look correct, assuming we properly check > the return status. So perhaps instead you can test > the patch below? Applied it to tip:out-of-tree for testing, and have dropped the revert as well. Will let you know how it goes. (if you dont hear from me later today you an assume it's all fixed.) Thanks, Ingo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Ingo Molnar on 28 Dec 2009 07:10 * Ingo Molnar <mingo(a)elte.hu> wrote: > * Len Brown <lenb(a)kernel.org> wrote: > > > On Sat, 26 Dec 2009, Len Brown wrote: > > > > > > [ 28.643216] evbug.c: Connected device: input1 (Dell WMI hotkeys at wmi/input0) > > > > [ 28.650449] BUG: unable to handle kernel NULL pointer dereference at 00000014 > > > > [ 28.654439] IP: [<c17f7f21>] wmi_install_notify_handler+0x31/0x70 > > > > > > Rather than reverting the broken patch that caused wmi to load, > > > does applying this patch to deal with the broken error handling > > > cause the oops to go away? > > > > > Subject: [PATCH] Revert "wmi: Free the allocated acpi objects through wmi_get_event_data" > > > > > > This reverts commit 3e9b988e4edf065d39c1343937f717319b1c1065. > > > > These kfree's look correct, assuming we properly check > > the return status. So perhaps instead you can test > > the patch below? > > Applied it to tip:out-of-tree for testing, and have dropped the revert as > well. Will let you know how it goes. (if you dont hear from me later today > you an assume it's all fixed.) Still a very similar looking crash (attached). I went for the plain revert in tip:out-of-tree again. (Note that the system does not have this hardware, and that it's booted with the driver built-in. So the relevant codepath should be very simple. Config attached.) Ingo [ 27.447053] initcall compal_init+0x0/0xf7 returned -19 after 3 usecs [ 27.453409] calling dell_wmi_init+0x0/0x129 @ 1 [ 27.458255] PM: Adding info for No Bus:input3 [ 27.462676] input: Dell WMI hotkeys as /class/input/input3 [ 27.468179] BUG: unable to handle kernel NULL pointer dereference at 00000014 [ 27.472165] IP: [<c1f26aa8>] wmi_install_notify_handler+0x28/0x80 [ 27.472165] *pde = 00000000 [ 27.472165] Oops: 0000 [#1] PREEMPT SMP [ 27.472165] last sysfs file: [ 27.472165] [ 27.472165] Pid: 1, comm: swapper Not tainted 2.6.33-rc2-tip-00212-g3c2365e-dirty #3297 A8N-E/System Product Name [ 27.472165] EIP: 0060:[<c1f26aa8>] EFLAGS: 00010282 CPU: 0 [ 27.472165] EIP is at wmi_install_notify_handler+0x28/0x80 [ 27.472165] EAX: fffffff4 EBX: c1f1e200 ECX: 22b612b0 EDX: c2b2d1e0 [ 27.472165] ESI: 00000000 EDI: 00000001 EBP: f64b3f84 ESP: f64b3f78 [ 27.472165] DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068 [ 27.472165] Process swapper (pid: 1, ti=f64b3000 task=f64d0000 task.ti=f64b3000) [ 27.472165] Stack: [ 27.472165] fffffff4 00000000 00000006 f64b3f98 c28d70d7 64a0689d 00000006 64a0689d [ 27.472165] <0> f64b3fc4 c100112b c255aa54 c28d6fb6 00000001 00000003 00000000 c28d6fb6 [ 27.472165] <0> c294a50c c2882310 00000000 f64b3fd0 c28822fd c29493e8 f64b3fe4 c2882392 [ 27.472165] Call Trace: [ 27.472165] [<c28d70d7>] ? dell_wmi_init+0x121/0x129 [ 27.472165] [<c100112b>] ? do_one_initcall+0x2b/0x1c0 [ 27.472165] [<c28d6fb6>] ? dell_wmi_init+0x0/0x129 [ 27.472165] [<c28d6fb6>] ? dell_wmi_init+0x0/0x129 [ 27.472165] [<c2882310>] ? kernel_init+0x0/0xc9 [ 27.472165] [<c28822fd>] ? do_basic_setup+0x44/0x57 [ 27.472165] [<c2882392>] ? kernel_init+0x82/0xc9 [ 27.472165] [<c1039816>] ? kernel_thread_helper+0x6/0x10 [ 27.472165] Code: 00 00 00 55 89 e5 56 53 83 ec 04 0f 1f 44 00 00 89 d3 89 ce 85 c0 74 2b 85 d2 74 27 8d 55 f4 e8 2f fd ff ff 8b 45 f4 85 c0 74 48 <8b> 50 20 85 d2 74 21 b8 15 00 00 00 59 5b 5e 5d c3 8d b4 26 00 [ 27.472165] EIP: [<c1f26aa8>] wmi_install_notify_handler+0x28/0x80 SS:ESP 0068:f64b3f78 [ 27.472165] CR2: 0000000000000014 [ 27.638896] ---[ end trace 7a45c2b3ab0f183e ]--- [ 27.643524] Kernel panic - not syncing: Fatal exception [ 27.648758] Pid: 1, comm: swapper Tainted: G D 2.6.33-rc2-tip-00212-g3c2365e-dirty #3297 [ 27.657546] Call Trace: [ 27.659997] [<c2170a4a>] ? printk+0x1d/0x1f [ 27.664281] [<c217097f>] panic+0x52/0x100 [ 27.668390] [<c103ce33>] oops_end+0xb3/0xc0 [ 27.672673] [<c1064d74>] no_context+0xb4/0xd0 [ 27.677124] [<c1064e27>] __bad_area_nosemaphore+0x97/0x140 [ 27.682706] [<c1082437>] ? vprintk+0x297/0x420 [ 27.687248] [<c1064ee7>] bad_area_nosemaphore+0x17/0x20 [ 27.692570] [<c10652c6>] do_page_fault+0x296/0x350 [ 27.697460] [<c1f1e200>] ? dell_wmi_notify+0x0/0x1c0 [ 27.702518] [<c1065030>] ? do_page_fault+0x0/0x350 [ 27.707408] [<c2173a16>] error_code+0x66/0x70 [ 27.711863] [<c1f1e200>] ? dell_wmi_notify+0x0/0x1c0 [ 27.716924] [<c1065030>] ? do_page_fault+0x0/0x350 [ 27.721810] [<c1f26aa8>] ? wmi_install_notify_handler+0x28/0x80 [ 27.727827] [<c28d70d7>] dell_wmi_init+0x121/0x129 [ 27.732713] [<c100112b>] do_one_initcall+0x2b/0x1c0 [ 27.737688] [<c28d6fb6>] ? dell_wmi_init+0x0/0x129 [ 27.742576] [<c28d6fb6>] ? dell_wmi_init+0x0/0x129 [ 27.747465] [<c2882310>] ? kernel_init+0x0/0xc9 [ 27.752094] [<c28822fd>] do_basic_setup+0x44/0x57 [ 27.756896] [<c2882392>] kernel_init+0x82/0xc9 [ 27.761436] [<c1039816>] kernel_thread_helper+0x6/0x10
From: Paul Rolland on 28 Dec 2009 10:10
Hello, On Mon, 28 Dec 2009 13:01:25 +0100 Ingo Molnar <mingo(a)elte.hu> wrote: > (Note that the system does not have this hardware, and that it's booted > with the driver built-in. So the relevant codepath should be very simple. > Config attached.) > > Ingo > > [ 27.447053] initcall compal_init+0x0/0xf7 returned -19 after 3 usecs > [ 27.453409] calling dell_wmi_init+0x0/0x129 @ 1 > [ 27.458255] PM: Adding info for No Bus:input3 > [ 27.462676] input: Dell WMI hotkeys as /class/input/input3 > [ 27.468179] BUG: unable to handle kernel NULL pointer dereference at > 00000014 [ 27.472165] IP: [<c1f26aa8>] > wmi_install_notify_handler+0x28/0x80 [ 27.472165] *pde = 00000000 > [ 27.472165] Oops: 0000 [#1] PREEMPT SMP > [ 27.472165] last sysfs file: > [ 27.472165] > [ 27.472165] Pid: 1, comm: swapper Not tainted > 2.6.33-rc2-tip-00212-g3c2365e-dirty #3297 A8N-E/System Product Name > [ 27.472165] EIP: 0060:[<c1f26aa8>] EFLAGS: 00010282 CPU: 0 > [ 27.472165] EIP is at wmi_install_notify_handler+0x28/0x80 > [ 27.472165] EAX: fffffff4 EBX: c1f1e200 ECX: 22b612b0 EDX: c2b2d1e0 > [ 27.472165] ESI: 00000000 EDI: 00000001 EBP: f64b3f84 ESP: f64b3f78 > [ 27.472165] DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068 > [ 27.472165] Process swapper (pid: 1, ti=f64b3000 task=f64d0000 > task.ti=f64b3000) [ 27.472165] Stack: [ 27.472165] fffffff4 00000000 > 00000006 f64b3f98 c28d70d7 64a0689d 00000006 64a0689d [ 27.472165] <0> > f64b3fc4 c100112b c255aa54 c28d6fb6 00000001 00000003 00000000 c28d6fb6 > [ 27.472165] <0> c294a50c c2882310 00000000 f64b3fd0 c28822fd c29493e8 > f64b3fe4 c2882392 [ 27.472165] Call Trace: [ 27.472165] > [<c28d70d7>] ? dell_wmi_init+0x121/0x129 [ 27.472165] [<c100112b>] ? > do_one_initcall+0x2b/0x1c0 [ 27.472165] [<c28d6fb6>] ? > dell_wmi_init+0x0/0x129 [ 27.472165] [<c28d6fb6>] ? > dell_wmi_init+0x0/0x129 [ 27.472165] [<c2882310>] ? > kernel_init+0x0/0xc9 [ 27.472165] [<c28822fd>] ? > do_basic_setup+0x44/0x57 [ 27.472165] [<c2882392>] ? > kernel_init+0x82/0xc9 [ 27.472165] [<c1039816>] ? > kernel_thread_helper+0x6/0x10 [ 27.472165] Code: 00 00 00 55 89 e5 56 > 53 83 ec 04 0f 1f 44 00 00 89 d3 89 ce 85 c0 74 2b 85 d2 74 27 8d 55 f4 > e8 2f fd ff ff 8b 45 f4 85 c0 74 48 <8b> 50 20 85 d2 74 21 b8 15 00 00 00 > 59 5b 5e 5d c3 8d b4 26 00 [ 27.472165] EIP: [<c1f26aa8>] > wmi_install_notify_handler+0x28/0x80 SS:ESP 0068:f64b3f78 [ 27.472165] > CR2: 0000000000000014 [ 27.638896] ---[ end trace 7a45c2b3ab0f183e ]--- > [ 27.643524] Kernel panic - not syncing: Fatal exception [ 27.648758] > Pid: 1, comm: swapper Tainted: G D > 2.6.33-rc2-tip-00212-g3c2365e-dirty #3297 [ 27.657546] Call Trace: > [ 27.659997] [<c2170a4a>] ? printk+0x1d/0x1f [ 27.664281] > [<c217097f>] panic+0x52/0x100 [ 27.668390] [<c103ce33>] > oops_end+0xb3/0xc0 [ 27.672673] [<c1064d74>] no_context+0xb4/0xd0 > [ 27.677124] [<c1064e27>] __bad_area_nosemaphore+0x97/0x140 > [ 27.682706] [<c1082437>] ? vprintk+0x297/0x420 [ 27.687248] > [<c1064ee7>] bad_area_nosemaphore+0x17/0x20 [ 27.692570] [<c10652c6>] > do_page_fault+0x296/0x350 [ 27.697460] [<c1f1e200>] ? > dell_wmi_notify+0x0/0x1c0 [ 27.702518] [<c1065030>] ? > do_page_fault+0x0/0x350 [ 27.707408] [<c2173a16>] error_code+0x66/0x70 > [ 27.711863] [<c1f1e200>] ? dell_wmi_notify+0x0/0x1c0 > [ 27.716924] [<c1065030>] ? do_page_fault+0x0/0x350 > [ 27.721810] [<c1f26aa8>] ? wmi_install_notify_handler+0x28/0x80 > [ 27.727827] [<c28d70d7>] dell_wmi_init+0x121/0x129 > [ 27.732713] [<c100112b>] do_one_initcall+0x2b/0x1c0 > [ 27.737688] [<c28d6fb6>] ? dell_wmi_init+0x0/0x129 > [ 27.742576] [<c28d6fb6>] ? dell_wmi_init+0x0/0x129 > [ 27.747465] [<c2882310>] ? kernel_init+0x0/0xc9 > [ 27.752094] [<c28822fd>] do_basic_setup+0x44/0x57 > [ 27.756896] [<c2882392>] kernel_init+0x82/0xc9 > [ 27.761436] [<c1039816>] kernel_thread_helper+0x6/0x10 Looks like it is very similar to what I have when I run : modprobe dell-wmi on my Dell laptop (Vostro 1520). Message from syslogd(a)tux at Dec 28 16:00:22 ... kernel:Oops: 0000 [#1] SMP Message from syslogd(a)tux at Dec 28 16:00:22 ... kernel:last sysfs file: /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq Message from syslogd(a)tux at Dec 28 16:00:22 ... kernel:Stack: Message from syslogd(a)tux at Dec 28 16:00:22 ... kernel:Call Trace: Message from syslogd(a)tux at Dec 28 16:00:22 ... kernel:Code: 65 f8 48 89 f3 49 89 d4 48 85 f6 74 35 48 85 ff 74 30 48 8d 75 e8 e8 27 fd ff ff 48 8b 55 e8 b8 06 00 00 00 48 85 d2 74 09 b0 15 <48> 83 7a 30 00 74 20 48 8b 5d f0 4c 8b 65 f8 c9 c3 66 0f 1f 44 Message from syslogd(a)tux at Dec 28 16:00:22 ... kernel:CR2: 0000000100000024 Dec 28 16:00:22 tux kernel: ACPI: WMI: Mapper loaded Dec 28 16:00:22 tux kernel: input: Dell WMI hotkeys as /devices/virtual/input/input13 Dec 28 16:00:22 tux kernel: BUG: unable to handle kernel paging request at 0000000100000024 Dec 28 16:00:22 tux kernel: IP: [<ffffffffa0003789>] wmi_install_notify_handler+0x39/0x80 [wmi] Dec 28 16:00:22 tux kernel: PGD 565f3067 PUD 0 Dec 28 16:00:22 tux kernel: Oops: 0000 [#1] SMP Dec 28 16:00:22 tux kernel: last sysfs file: /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq Dec 28 16:00:22 tux kernel: CPU 1 Dec 28 16:00:22 tux kernel: Pid: 20215, comm: modprobe Not tainted 2.6.33-rc2 #1 0T816J/Vostro 1520 Dec 28 16:00:22 tux kernel: RIP: 0010:[<ffffffffa0003789>] [<ffffffffa0003789>] wmi_install_notify_handler+0x39/0x80 [wmi] Dec 28 16:00:22 tux kernel: RSP: 0018:ffff88009434bed8 EFLAGS: 00010202 Dec 28 16:00:22 tux kernel: RAX: 0000000000000015 RBX: ffffffffa014f0f0 RCX: 000000000000009d Dec 28 16:00:22 tux kernel: RDX: 00000000fffffff4 RSI: ffff88009434be98 RDI: ffff88009434be8c Dec 28 16:00:22 tux kernel: RBP: ffff88009434bef8 R08: ffff88009434be88 R09: 0000000000000010 Dec 28 16:00:22 tux kernel: R10: ffff88009434bee0 R11: 0000000000000006 R12: 0000000000000000 Dec 28 16:00:22 tux kernel: R13: 0000000002188470 R14: 0000000000000000 R15: 0000000000000000 Dec 28 16:00:22 tux kernel: FS: 00007fb6aa7446f0(0000) GS:ffff880028300000(0000) knlGS:0000000000000000 Dec 28 16:00:22 tux kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b Dec 28 16:00:22 tux kernel: CR2: 0000000100000024 CR3: 00000000bd319000 CR4: 00000000000406e0 Dec 28 16:00:22 tux kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Dec 28 16:00:22 tux kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Dec 28 16:00:22 tux kernel: Process modprobe (pid: 20215, threadinfo ffff88009434a000, task ffff8800a3a0ace0) Dec 28 16:00:22 tux kernel: Stack: Dec 28 16:00:22 tux kernel: ffff88009434bef8 00000000fffffff4 0000000000000000 ffffffffa0152000 Dec 28 16:00:22 tux kernel: <0> ffff88009434bf18 ffffffffa0152142 0000000000000000 0000000000000000 Dec 28 16:00:22 tux kernel: <0> ffff88009434bf48 ffffffff810001d7 0000000000000000 ffffffffa014f780 Dec 28 16:00:22 tux kernel: Call Trace: Dec 28 16:00:22 tux kernel: [<ffffffffa0152000>] ? dell_wmi_init+0x0/0x14a [dell_wmi] Dec 28 16:00:22 tux kernel: [<ffffffffa0152142>] dell_wmi_init+0x142/0x14a [dell_wmi] Dec 28 16:00:22 tux kernel: [<ffffffff810001d7>] do_one_initcall+0x37/0x190 Dec 28 16:00:22 tux kernel: [<ffffffff81074408>] sys_init_module+0xd8/0x250 Dec 28 16:00:22 tux kernel: [<ffffffff810024ab>] system_call_fastpath+0x16/0x1b Dec 28 16:00:22 tux kernel: Code: 65 f8 48 89 f3 49 89 d4 48 85 f6 74 35 48 85 ff 74 30 48 8d 75 e8 e8 27 fd ff ff 48 8b 55 e8 b8 06 00 00 00 48 85 d2 74 09 b0 15 <48> 83 7a 30 00 74 20 48 8b 5d f0 4c 8b 65 f8 c9 c3 66 0f 1f 44 Dec 28 16:00:22 tux kernel: RIP [<ffffffffa0003789>] wmi_install_notify_handler+0x39/0x80 [wmi] Dec 28 16:00:22 tux kernel: RSP <ffff88009434bed8> Dec 28 16:00:22 tux kernel: CR2: 0000000100000024 Dec 28 16:00:22 tux kernel: ---[ end trace d18b623021a6c139 ]--- -- Paul Rolland E-Mail : rol(at)witbe.net CTO - Witbe.net SA Tel. +33 (0)1 47 67 77 77 Les Collines de l'Arche Fax. +33 (0)1 47 67 77 99 F-92057 Paris La Defense RIPE : PR12-RIPE LinkedIn : http://www.linkedin.com/in/paulrolland This is dedicated to all the ones who want to control Internet, its content or its usage : "I worry about my child and the Internet all the time, even though she's too young to have logged on yet. Here's what I worry about. I worry that 10 or 15 years from now, she will come to me and say 'Daddy, where were you when they took freedom of the press away from the Internet?'" --Mike Godwin, Electronic Frontier Foundation -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |