[Bug 969576] Re: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init]
Asus UX31E here - patched kernel from #22 fixes kernel oops during boot, and hotkeys and suspend are again working. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969576 Title: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/969576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969576] Re: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init]
This bug was fixed in the package linux - 3.2.0-22.35 --- linux (3.2.0-22.35) precise; urgency=low [ Andy Whitcroft ] * Revert SAUCE: hotkey quirks for various Zeptro Znote and Fujitsu Amilo laptops * SAUCE: (no-up) elide some ioctl warnings which are known benign - LP: #972355 [ Brad Figg ] * SAUCE (no-up) Provide a param for allowing the BIOS to handle changing the brightness on AC/battery status changes. - LP: #949311 * SAUCE (drop after 3.4) Quirk for enabling backlight hotkeys on Samsung N150P - LP: #875893 [ Colin Ian King ] * SAUCE: PCI: Allow pcie_aspm=force to work even when FADT indicates it is unsupported - LP: #962038 [ Daniel Vetter ] * SAUCE: (drop after 3.5) drm/i915: reinstate GM45 TV detection fix - LP: #638939 [ Kees Cook ] * SAUCE: SECCOMP: audit: always report seccomp violations * SAUCE: SECCOMP: adjust prctl constant [ Leann Ogasawara ] * [Config] Enable CONFIG_USBIP_CORE=m - LP: #900384 * Rebase to v3.2.14 * [Config] Updateconfigs after rebase to v3.2.14 [ Stefan Bader ] * d-i: Fix module name for dm-raid45 - LP: #969248 [ Tim Gardner ] * SAUCE: remove __initdata from vesafb_fix - LP: #969309 [ Upstream Kernel Changes ] * Revert sched: tg-se-load should be initialised to tg-shares * toshiba_acpi: make one-bit bitfields unsigned - LP: #810015 * ACPI: EC: Add ec_get_handle() - LP: #810015 * toshiba_acpi: Support alternate hotkey interfaces - LP: #810015 * toshiba_acpi: Support additional hotkey scancodes - LP: #810015 * toshiba_acpi: Refuse to load on machines with buggy INFO implementations - LP: #810015 * ata_piix: Add Toshiba Satellite Pro A120 to the quirks list due to broken suspend functionality. - LP: #886850 * sweep the floors and convert some .get_drvinfo routines to strlcpy - LP: #921793 * be2net: init (vf)_if_handle/vf_pmac_id to handle failure scenarios - LP: #921793 * be2net: stop checking the UE registers after an EEH error - LP: #921793 * be2net: don't log more than one error on detecting EEH/UE errors - LP: #921793 * be2net: stop issuing FW cmds if any cmd times out - LP: #921793 * be2net: Fix TX queue create for Lancer - LP: #921793 * be2net: add register dump feature for Lancer - LP: #921793 * be2net: Add EEPROM dump feature for Lancer - LP: #921793 * be2net: Fix VLAN promiscous mode for Lancer - LP: #921793 * be2net: Use V1 query link status command for lancer - LP: #921793 * be2net: Move to new SR-IOV implementation in Lancer - LP: #921793 * be2net: Fix error recovery paths - LP: #921793 * be2net: Add error handling for Lancer - LP: #921793 * be2net: Use new hash key - LP: #921793 * be2net: Fix non utilization of RX queues - LP: #921793 * be2net: netpoll support - LP: #921793 * be2net: update some counters to display via ethtool - LP: #921793 * be2net: workaround to fix a bug in BE - LP: #921793 * be2net: fix ethtool ringparam reporting - LP: #921793 * be2net: refactor/cleanup vf configuration code - LP: #921793 * be2net: Add support for Skyhawk cards - LP: #921793 * be2net: Fix INTx processing for Lancer - LP: #921793 * be2net: fix range check for set_qos for a VF - LP: #921793 * be2net: query link status in be_open() - LP: #921793 * netdev: make net_device_ops const - LP: #921793 * be2net: create RSS rings even in multi-channel configs - LP: #921793 * ethtool: Null-terminate filename passed to ethtool_ops::flash_device - LP: #921793 * sched: Fix nohz load accounting - LP: #838811 * ACPICA: Fix regression in FADT revision checks - LP: #883441 * asus-wmi: move WAPF variable into quirks_entry - LP: #969576 * eeepc-wmi: refine quirks handling - LP: #969576 * drm/i915: Sanitize BIOS debugging bits from PIPECONF - LP: #968307 * drivers: hv: Get rid of some unnecessary code * drivers: hv: kvp: Add/cleanup connector defines * drivers: hv: kvp: Move the contents of hv_kvp.h to hyperv.h * net/hyperv: Convert camel cased variables in rndis_filter.c to lower cases * net/hyperv: Correct the assignment in netvsc_recv_callback() * net/hyperv: Remove the unnecessary memset in rndis_filter_send() * tools: hv: Use hyperv.h to get the KVP definitions * drivers: hv: Cleanup the kvp related state in hyperv.h * drivers: hv: kvp: Cleanup the kernel/user protocol * drivers: hv: Increase the number of VCPUs supported in the guest * net/hyperv: Fix data corruption in rndis_filter_receive() * net/hyperv: Add support for vlan trunking from guests * Drivers: hv: Add new message types to enhance KVP * net/hyperv: fix erroneous NETDEV_TX_BUSY use * NLS: improve UTF8 - UTF16 string conversion routine * Drivers: hv: Support the newly introduced KVP messages in the driver * Tools: hv: Fully support the new
[Bug 969576] Re: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init]
asus-wmi: move WAPF variable into quirks_entry ** Also affects: linux (Ubuntu Precise) Importance: Critical Assignee: AceLan Kao (acelankao) Status: In Progress ** Changed in: linux (Ubuntu Precise) Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969576 Title: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/969576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969576] Re: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init]
Patched kernel boots again. Asus P8Z68 here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969576 Title: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/969576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969576] Re: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init]
Patched kernel from #22 worked for me too -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969576 Title: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/969576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969576] Re: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init]
Patched kernel (comment #22) fixed issue here (Asus N55). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969576 Title: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/969576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969576] Re: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init]
Patched kernel (comment #22) works for me as well SABERTOOTH P67. Be sure to unselect the kernel from the update tool until this has been fixed in the repos otherwise it will downgrade to the old nonworking kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969576 Title: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/969576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969576] Re: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init]
Please change priority to high . Please remove this whole asus cosmetic fix Aleksi Hankalahti mentioned in his first and second link until the author can be sure it doesn't break anything somewhat more important , like a filesystem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969576 Title: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/969576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969576] Re: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init]
So sorry about this, I think we forgot to cheery pick other important commit. I'll give you a testing kernel ASAP. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969576 Title: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/969576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969576] Re: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init]
I'm building the new kernel with one more patch. I uploaded the patch on my directory[1], you can try to build your own kernel and I'll upload the kernel package once it finished. I'm pretty sure that this patch can fix the problem, but still need you guys to confirm this. Really sorry about this. 1. http://people.canonical.com/~acelan/bugs/lp969576/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969576 Title: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/969576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969576] Re: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init]
** Changed in: linux (Ubuntu) Assignee: (unassigned) = AceLan Kao (acelankao) ** Changed in: linux (Ubuntu) Importance: Medium = Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969576 Title: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/969576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969576] Re: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init]
** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969576 Title: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/969576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969576] Re: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init]
In my case this also prevents X from starting normally; had to resort to the following to make X start properly on bootup: $ cat /etc/modprobe.d/blacklist-asuswmi.conf # NULL ptr deref @ Ubuntu 3.2.0-21.34-generic 3.2.13 blacklist eeepc_wmi blacklist asus_wmi blacklist wmi $ sudo update-initramfs -k 3.2.0-21-generic -u -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969576 Title: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/969576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969576] Re: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init]
With the kernel from http://people.canonical.com/~acelan/bugs/lp969576/ asus_wmi doesn't crash at boot and doesn't prevent system to boot normally to DM what is more important :) Seems there is another problem with init, upstart or whatever, as if i enable recovery or just text mode it drops me to tty login and i could run 'start lightdm' without problems, even with crashed asus_wmi. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969576 Title: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/969576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969576] Re: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init]
Maxim, Cool, thanks to confirm that the problem could be fixed by that patch. I'll let the kernel team to cherry pick that commit. Thanks. ** Changed in: linux (Ubuntu) Status: Incomplete = In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969576 Title: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/969576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969576] Re: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init]
This patch fixed the original OOPS, but a new, related, one shows up on my computer: [ 15.719997] BUG: unable to handle kernel NULL pointer dereference at 0004 [ 15.720229] IP: [a0091a07] asus_wmi_platform_init+0x87/0x150 [asus_wmi] [ 15.720354] PGD 122837067 PUD 126e90067 PMD 0 [ 15.720567] Oops: [#1] SMP [ 15.720730] CPU 0 [ 15.720783] Modules linked in: eeepc_wmi(+) asus_wmi snd joydev sparse_keymap mac_hid btusb mei(C) soundcore serio_raw snd_page_alloc bluetooth mxm_wmi wmi hid_microsoft usbhid hid dm_snapshot firewire_ohci firewire_core crc_itu_t e1000e [ 15.722094] [ 15.722154] Pid: 797, comm: modprobe Tainted: G C 3.2.0-21-generic #34 System manufacturer System Product Name/P8P67 PRO [ 15.722382] RIP: 0010:[a0091a07] [a0091a07] asus_wmi_platform_init+0x87/0x150 [asus_wmi] [ 15.722508] RSP: 0018:8801251ddc88 EFLAGS: 00010246 [ 15.722571] RAX: RBX: 88012717f800 RCX: 0008e5f8 [ 15.722636] RDX: RSI: 000165a0 RDI: 88012a802600 [ 15.722702] RBP: 8801251ddca8 R08: ea0004906240 R09: a00910bb [ 15.722766] R10: R11: R12: 88012717e800 [ 15.722831] R13: a00fd080 R14: fff4 R15: 88012717e800 [ 15.722896] FS: 7fcc75f92700() GS:88012f40() knlGS: [ 15.722969] CS: 0010 DS: ES: CR0: 80050033 [ 15.723032] CR2: 0004 CR3: 000125288000 CR4: 000406f0 [ 15.723097] DR0: DR1: DR2: [ 15.723162] DR3: DR6: 0ff0 DR7: 0400 [ 15.723227] Process modprobe (pid: 797, threadinfo 8801251dc000, task 880124cd16f0) [ 15.723299] Stack: [ 15.723359] 8801251ddca8 a00fb0a3 fff4 88012717f800 [ 15.723633] 8801251ddcd8 a0092f75 88012717e800 a00fd080 [ 15.723907] a00fd080 8801251ddcf8 a0093184 [ 15.724181] Call Trace: [ 15.724243] [a0092f75] asus_wmi_add+0x95/0x250 [asus_wmi] [ 15.724308] [a0093184] asus_wmi_probe+0x54/0x80 [asus_wmi] [ 15.724374] [813f6167] platform_drv_probe+0x17/0x20 [ 15.724438] [813f49c8] really_probe+0x68/0x190 [ 15.724503] [813f4c55] driver_probe_device+0x45/0x70 [ 15.724567] [813f4d2b] __driver_attach+0xab/0xb0 [ 15.724631] [813f4c80] ? driver_probe_device+0x70/0x70 [ 15.724695] [813f4c80] ? driver_probe_device+0x70/0x70 [ 15.724760] [813f3abc] bus_for_each_dev+0x5c/0x90 [ 15.724824] [813f478e] driver_attach+0x1e/0x20 [ 15.724887] [813f43e0] bus_add_driver+0x1a0/0x270 [ 15.724951] [813f5296] driver_register+0x76/0x140 [ 15.725016] [813f6726] platform_driver_register+0x46/0x50 [ 15.725081] [813f6758] platform_driver_probe+0x28/0xb0 [ 15.725146] [813f6ef1] platform_create_bundle+0xc1/0xf0 [ 15.725212] [a0093130] ? asus_wmi_add+0x250/0x250 [asus_wmi] [ 15.725276] [a009e000] ? 0xa009dfff [ 15.725339] [a009196a] asus_wmi_register_driver+0x5a/0x70 [asus_wmi] [ 15.725412] [a009e010] eeepc_wmi_init+0x10/0x1000 [eeepc_wmi] [ 15.725478] [81002040] do_one_initcall+0x40/0x180 [ 15.725543] [810a89ce] sys_init_module+0xbe/0x230 [ 15.725608] [81664602] system_call_fastpath+0x16/0x1b [ 15.725671] Code: 0f 84 99 00 00 00 31 c9 31 d2 31 f6 bf 44 43 54 53 e8 4e f6 ff ff 85 c0 75 4a c7 03 44 43 54 53 48 8b 83 90 03 00 00 48 8b 40 38 8b 50 04 85 d2 78 11 31 c9 be 03 00 01 00 bf 44 45 56 53 e8 21 [ 15.729040] RIP [a0091a07] asus_wmi_platform_init+0x87/0x150 [asus_wmi] [ 15.729163] RSP 8801251ddc88 [ 15.729224] CR2: 0004 [ 15.729292] ---[ end trace e72536b1b8b35ab0 ]--- And yes, on my computer with 3.2.0-21-generic boot also stalls if I don't boot in the rescue mode (and then I can start lightdm by hand) but I'm not sure if it's related -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969576 Title: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/969576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969576] Re: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init]
Krzysztof, Could you boot into 3.2.0-20 kernel and upload the dmesg and lsmod log? Thanks. And does anyone encounter the same problem as Krzysztof's? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969576 Title: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/969576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969576] Re: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init]
** Attachment added: lsmod output https://bugs.launchpad.net/ubuntu/+source/linux/+bug/969576/+attachment/2976586/+files/lsmod.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969576 Title: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/969576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969576] Re: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init]
** Attachment added: dmesg.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/969576/+attachment/2976587/+files/dmesg.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969576 Title: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/969576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969576] Re: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init]
I've attached lsmod output and dmesg log from the 3.2.0-20 kernel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969576 Title: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/969576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969576] Re: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init]
The new kernel and patches is here[1], please have it a test. 1. http://people.canonical.com/~acelan/bugs/lp969576/2/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969576 Title: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/969576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969576] Re: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init]
I can also confirm this bug, it happens for me too for every boot since 3.2.0-21, no problems before. Mainboard is almost the same, Asus P8P67 with internal bluetooth. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969576 Title: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/969576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969576] Re: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init]
Another problem that might be related is that dpkg --pendinging configure hangs in initramfs-tools. Booting the 3.2.0-20 kernel fixes this, so it might be the same driver that makes problem. Sorry if this seems off topic, I report this here in the hope that it might be of any help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969576 Title: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/969576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969576] Re: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init]
I got this on my laptop (Asus P31): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/970310 after latest kernel update. Confirming that kernel from #22 fixes this oops. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969576 Title: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/969576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969576] Re: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init]
Same problem exists on my Asus eeePC 1005HA. Also, the Volume control hotkeys stopped working with this kernel version. Is this related to this bug or should I file a new one? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969576 Title: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/969576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969576] Re: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init]
With kernel from comment #22 volume keys works on my laptop. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969576 Title: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/969576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969576] Re: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init]
Stefan, B3nn0, Please try the kernel from comment #22, the problem should be fixed by that kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969576 Title: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/969576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969576] Re: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init]
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969576 Title: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/969576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969576] Re: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init]
Do you have a way to reproduce this oops, or was a one time event? ** Changed in: linux (Ubuntu) Importance: Undecided = Medium ** Tags added: asus-wmi-rfkill-init -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969576 Title: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/969576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969576] Re: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init]
** Changed in: linux (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969576 Title: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/969576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969576] Re: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init]
it has happened both times I have rebooted with 3.2.0-21-generic kernel so I think it's reproducible. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969576 Title: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/969576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969576] Re: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init]
For me it seems to happen on every boot with linux- image-3.2.0-21-generic 3.2.0-21.34. Error does not appear with older vmlinuz-3.2.0-20-generic. My motherboard is (same?) Asus P8P67 PRO. From my machine: [7.347037] asus_wmi: ASUS WMI generic driver loaded [7.347315] asus_wmi: Initialization: 0x0 [7.347328] asus_wmi: BIOS WMI version: 0.9 [7.347350] asus_wmi: SFUN value: 0x0 [7.347491] input: Eee PC WMI hotkeys as /devices/platform/eeepc-wmi/input/input9 [7.349168] BUG: unable to handle kernel NULL pointer dereference at (null) [7.349171] IP: [a0dc8d08] asus_wmi_rfkill_init+0x188/0x200 [asus_wmi] [7.349175] PGD 4006f8067 PUD 4023c2067 PMD 0 [7.349177] Oops: [#1] SMP [7.349179] CPU 2 [7.349180] Modules linked in: eeepc_wmi(+) asus_wmi sparse_keymap mxm_wmi snd_rawmidi snd_seq btusb bluetooth joydev snd_timer nvidia(P) psmouse serio_raw snd_seq_device wmi snd mac_hid soundcore snd_page_alloc mei(C) lp parport vesafb usbhid hid r8169 firewire_ohci firewire_core crc_itu_t [7.349191] [7.349192] Pid: 807, comm: modprobe Tainted: P C O 3.2.0-21-generic #34 System manufacturer System Product Name/P8P67-M PRO [7.349195] RIP: 0010:[a0dc8d08] [a0dc8d08] asus_wmi_rfkill_init+0x188/0x200 [asus_wmi] [7.349198] RSP: 0018:88040264dc98 EFLAGS: 00010246 [7.349199] RAX: RBX: 8803fa8ebc00 RCX: 0a59 [7.349200] RDX: RSI: 000165a0 RDI: 88040e802600 [7.349201] RBP: 88040264dca8 R08: 00010021 R09: a0dc70bb [7.349203] R10: R11: R12: ffed [7.349204] R13: a0d22088 R14: R15: 8803fa8eb800 [7.349205] FS: 7f082c7ee700() GS:88041f50() knlGS: [7.349207] CS: 0010 DS: ES: CR0: 8005003b [7.349208] CR2: CR3: 000401f7d000 CR4: 000406e0 [7.349209] DR0: DR1: DR2: [7.349210] DR3: DR6: 0ff0 DR7: 0400 [7.349211] Process modprobe (pid: 807, threadinfo 88040264c000, task 880402662de0) [7.349212] Stack: [7.349213] 8803fa8ebc00 8803fa8eb800 88040264dcd8 a0dc8ff7 [7.349216] 8803fa8eb800 a0d22088 a0d22088 [7.349218] 88040264dcf8 a0dc9194 a0d22088 8803fa8eb810 [7.349220] Call Trace: [7.349223] [a0dc8ff7] asus_wmi_add+0x117/0x260 [asus_wmi] [7.349225] [a0dc9194] asus_wmi_probe+0x54/0x80 [asus_wmi] [7.349228] [813f6197] platform_drv_probe+0x17/0x20 [7.349230] [813f49f8] really_probe+0x68/0x190 [7.349232] [813f4c85] driver_probe_device+0x45/0x70 [7.349233] [813f4d5b] __driver_attach+0xab/0xb0 [7.349235] [813f4cb0] ? driver_probe_device+0x70/0x70 [7.349237] [813f4cb0] ? driver_probe_device+0x70/0x70 [7.349240] [813f3aec] bus_for_each_dev+0x5c/0x90 [7.349241] [813f47be] driver_attach+0x1e/0x20 [7.349242] [813f4410] bus_add_driver+0x1a0/0x270 [7.349244] [813f52c6] driver_register+0x76/0x140 [7.349246] [813f6756] platform_driver_register+0x46/0x50 [7.349248] [813f6788] platform_driver_probe+0x28/0xb0 [7.349250] [813f6f21] platform_create_bundle+0xc1/0xf0 [7.349252] [a0dc9140] ? asus_wmi_add+0x260/0x260 [asus_wmi] [7.349254] [a001d000] ? 0xa001cfff [7.349255] [a0dc796a] asus_wmi_register_driver+0x5a/0x70 [asus_wmi] [7.349258] [a001d010] eeepc_wmi_init+0x10/0x1000 [eeepc_wmi] [7.349261] [81002040] do_one_initcall+0x40/0x180 [7.349265] [810a89ce] sys_init_module+0xbe/0x230 [7.349267] [81664602] system_call_fastpath+0x16/0x1b [7.349268] Code: 00 48 c7 c2 06 a7 dc a0 48 89 df e8 33 f3 ff ff 83 f8 ed 41 89 c4 74 08 85 c0 0f 85 f3 fe ff ff 48 8b 83 90 03 00 00 48 8b 40 40 80 38 00 75 18 41 83 fc ed 0f 84 e1 fe ff ff 45 85 e4 0f 84 d8 [7.349286] RIP [a0dc8d08] asus_wmi_rfkill_init+0x188/0x200 [asus_wmi] [7.349288] RSP 88040264dc98 [7.349289] CR2: [7.349291] ---[ end trace c2fb9004c43e3ec4 ]--- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969576 Title: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/969576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969576] Re: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init]
So it seems this only happens with the new 3.2.0-21 kernel? Can you boot back into 3.2.0-20 and see if you can reproduce the bug? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969576 Title: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/969576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969576] Re: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init]
I just booted with 3.2.0-20 and the problem doesn't show up here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969576 Title: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/969576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969576] Re: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init]
and yes, my motherboard is also Asus P8P67 PRO (rev3.0) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969576 Title: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/969576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969576] Re: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init]
I don't know how to reproduce (or even try) it. It just appears after system loads asus_wmi (asus_wmi: ASUS WMI generic driver loaded). With 3.2.0-20 it just loads the module and nothing crashes. :) But there is more! This is related to bug #968016 because patches [1] and [2] breaks suspend (but not in the same way as #968016) and also produces this error. Currently I am running kernel compiled from source [3] where I removed patches [1] and [2], and applied patch [4]. With this kernel no asus_wmi_rfkill_init error appears and the machine suspends without problems. [1] http://kernel.ubuntu.com/git?p=ubuntu/ubuntu- precise.git;a=commit;h=4b9161676f4507209b9871f9358421c512b20534 [2] http://kernel.ubuntu.com/git?p=ubuntu/ubuntu- precise.git;a=commit;h=d725ae12539389eb502c6257ccedd2a0bf6025da [3] http://kernel.ubuntu.com/git?p=ubuntu/ubuntu- precise.git;a=tag;h=refs/tags/Ubuntu-3.2.0-21.34 [4] http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=8931d9ea78848b073bf299594f148b83abde4a5e -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969576 Title: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/969576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969576] Re: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init]
For me this broke my ZFS , my zpools are gone , everything is ok again when I start up with .20 Pastebin of trace , as not to clutter this thread. http://pastebin.com/73d54Zpp For me this is quite fatal , happens every boot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969576 Title: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/969576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969576] Re: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init]
My motherboard however is an asus P9X79-Pro -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969576 Title: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/969576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
