BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init]

Bug #969576 reported by Krzysztof Klimonda on 2012-03-30
82
This bug affects 12 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Critical
AceLan Kao
Precise
Critical
AceLan Kao

Bug Description

[ 12.371250] BUG: unable to handle kernel NULL pointer dereference at (null)
[ 12.371436] IP: [<ffffffffa00a6d08>] asus_wmi_rfkill_init+0x188/0x200 [asus_wmi]
[ 12.371569] PGD 1254bf067 PUD 1254be067 PMD 0
[ 12.371797] Oops: 0000 [#1] SMP
[ 12.371970] CPU 3
[ 12.372026] Modules linked in: eeepc_wmi(+) asus_wmi mei(C) usbhid hid mac_hid soundcore snd_page_alloc sparse_keymap mxm_wmi wmi dm_multipath serio_raw dm_snapshot firewire_ohci firewire_core crc_itu_t e1000e
[ 12.373206]
[ 12.373270] Pid: 821, comm: modprobe Tainted: G C 3.2.0-21-generic #34-Ubuntu System manufacturer System Product Name/P8P67 PRO
[ 12.373513] RIP: 0010:[<ffffffffa00a6d08>] [<ffffffffa00a6d08>] asus_wmi_rfkill_init+0x188/0x200 [asus_wmi]
[ 12.373646] RSP: 0018:ffff8801254abc98 EFLAGS: 00010246
[ 12.373712] RAX: 0000000000000000 RBX: ffff88012717c400 RCX: 0000000000000be0
[ 12.373781] RDX: 0000000000000000 RSI: 00000000000165a0 RDI: ffff88012a802600
[ 12.373849] RBP: ffff8801254abca8 R08: 0000000000010021 R09: ffffffffa00a50bb
[ 12.373917] R10: 0000000000000000 R11: 0000000000000000 R12: 00000000ffffffed
[ 12.373986] R13: ffffffffa0088088 R14: 0000000000000000 R15: ffff88012717cc00
[ 12.374055] FS: 00007f53bd2df700(0000) GS:ffff88012f580000(0000) knlGS:0000000000000000
[ 12.374131] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 12.374197] CR2: 0000000000000000 CR3: 00000001254bc000 CR4: 00000000000406e0
[ 12.374266] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 12.374334] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[ 12.374403] Process modprobe (pid: 821, threadinfo ffff8801254aa000, task ffff8801258dc4d0)
[ 12.374479] Stack:
[ 12.374543] ffff88012717c400 ffff88012717cc00 ffff8801254abcd8 ffffffffa00a6ff7
[ 12.374833] ffff88012717cc00 ffffffffa0088088 ffffffffa0088088 0000000000000000
[ 12.375125] ffff8801254abcf8 ffffffffa00a7194 ffffffffa0088088 ffff88012717cc10
[ 12.375413] Call Trace:
[ 12.375480] [<ffffffffa00a6ff7>] asus_wmi_add+0x117/0x260 [asus_wmi]
[ 12.375548] [<ffffffffa00a7194>] asus_wmi_probe+0x54/0x80 [asus_wmi]
[ 12.375619] [<ffffffff813f6167>] platform_drv_probe+0x17/0x20
[ 12.375685] [<ffffffff813f49c8>] really_probe+0x68/0x190
[ 12.375752] [<ffffffff813f4c55>] driver_probe_device+0x45/0x70
[ 12.375819] [<ffffffff813f4d2b>] __driver_attach+0xab/0xb0
[ 12.375886] [<ffffffff813f4c80>] ? driver_probe_device+0x70/0x70
[ 12.375953] [<ffffffff813f4c80>] ? driver_probe_device+0x70/0x70
[ 12.376022] [<ffffffff813f3abc>] bus_for_each_dev+0x5c/0x90
[ 12.376088] [<ffffffff813f478e>] driver_attach+0x1e/0x20
[ 12.376155] [<ffffffff813f43e0>] bus_add_driver+0x1a0/0x270
[ 12.376222] [<ffffffff813f5296>] driver_register+0x76/0x140
[ 12.376290] [<ffffffff813f6726>] platform_driver_register+0x46/0x50
[ 12.376358] [<ffffffff813f6758>] platform_driver_probe+0x28/0xb0
[ 12.376426] [<ffffffff813f6ef1>] platform_create_bundle+0xc1/0xf0
[ 12.376495] [<ffffffffa00a7140>] ? asus_wmi_add+0x260/0x260 [asus_wmi]
[ 12.376563] [<ffffffffa0050000>] ? 0xffffffffa004ffff
[ 12.376631] [<ffffffffa00a596a>] asus_wmi_register_driver+0x5a/0x70 [asus_wmi]
[ 12.376707] [<ffffffffa0050010>] eeepc_wmi_init+0x10/0x1000 [eeepc_wmi]
[ 12.376778] [<ffffffff81002040>] do_one_initcall+0x40/0x180
[ 12.376847] [<ffffffff810a89ce>] sys_init_module+0xbe/0x230
[ 12.376914] [<ffffffff81664602>] system_call_fastpath+0x16/0x1b
[ 12.376981] Code: 00 48 c7 c2 06 87 0a 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
[ 12.380562] RIP [<ffffffffa00a6d08>] asus_wmi_rfkill_init+0x188/0x200 [asus_wmi]
[ 12.380693] RSP <ffff8801254abc98>
[ 12.380758] CR2: 0000000000000000
[ 12.380830] ---[ end trace a01667d4cc0c35c5 ]---

I'm not sure what's the effect of this OOPS, kernel seems stable so far and I can use /sys/class/rfkill/rfkill0/state to disable/enable bluetooth (it's a desktop computer so no hardware switch).

It wasn't a problem on vmlinuz-3.2.0-20-generic so it seems to be a regression related to the latest update

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-21-generic 3.2.0-21.34
ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13
Uname: Linux 3.2.0-21-generic x86_64
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: kklimonda 4138 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Date: Fri Mar 30 22:24:43 2012
HibernationDevice: RESUME=UUID=67bba538-b17b-4f70-83a2-5f74d881f6e2
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120125)
MachineType: System manufacturer System Product Name
ProcEnviron:
 LANGUAGE=en_US:en
 TERM=xterm
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-21-generic root=/dev/mapper/vg_red-root ro recovery nomodeset
RfKill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
StagingDrivers: mei
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/08/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1704
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8P67 PRO
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1704:bd06/08/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8P67PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Krzysztof Klimonda (kklimonda) wrote :
Joseph Salisbury (jsalisbury) wrote :

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
Krzysztof Klimonda (kklimonda) wrote :

it has happened both times I have rebooted with 3.2.0-21-generic kernel so I think it's reproducible.

Brad Figg (brad-figg) on 2012-03-30
Changed in linux (Ubuntu):
status: New → Confirmed
Download full text (4.4 KiB)

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: [<ffffffffa0dc8d08>] asus_wmi_rfkill_init+0x188/0x200 [asus_wmi]
[ 7.349175] PGD 4006f8067 PUD 4023c2067 PMD 0
[ 7.349177] Oops: 0000 [#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:[<ffffffffa0dc8d08>] [<ffffffffa0dc8d08>] asus_wmi_rfkill_init+0x188/0x200 [asus_wmi]
[ 7.349198] RSP: 0018:ffff88040264dc98 EFLAGS: 00010246
[ 7.349199] RAX: 0000000000000000 RBX: ffff8803fa8ebc00 RCX: 0000000000000a59
[ 7.349200] RDX: 0000000000000000 RSI: 00000000000165a0 RDI: ffff88040e802600
[ 7.349201] RBP: ffff88040264dca8 R08: 0000000000010021 R09: ffffffffa0dc70bb
[ 7.349203] R10: 0000000000000000 R11: 0000000000000000 R12: 00000000ffffffed
[ 7.349204] R13: ffffffffa0d22088 R14: 0000000000000000 R15: ffff8803fa8eb800
[ 7.349205] FS: 00007f082c7ee700(0000) GS:ffff88041f500000(0000) knlGS:0000000000000000
[ 7.349207] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[ 7.349208] CR2: 0000000000000000 CR3: 0000000401f7d000 CR4: 00000000000406e0
[ 7.349209] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 7.349210] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[ 7.349211] Process modprobe (pid: 807, threadinfo ffff88040264c000, task ffff880402662de0)
[ 7.349212] Stack:
[ 7.349213] ffff8803fa8ebc00 ffff8803fa8eb800 ffff88040264dcd8 ffffffffa0dc8ff7
[ 7.349216] ffff8803fa8eb800 ffffffffa0d22088 ffffffffa0d22088 0000000000000000
[ 7.349218] ffff88040264dcf8 ffffffffa0dc9194 ffffffffa0d22088 ffff8803fa8eb810
[ 7.349220] Call Trace:
[ 7.349223] [<ffffffffa0dc8ff7>] asus_wmi_add+0x117/0x260 [asus_wmi]
[ 7.349225] [<ffffffffa0dc9194>] asus_wmi_probe+0x54/0x80 [asus_wmi]
[ 7.349228] [<ffffffff813f6197>] platform_drv_probe+0x17/0x20
[ 7.349230] [<ffffffff813f49f8>] really_probe+0x68/0x190
[ 7.349232] [<ffffffff813f4c85>] driver_probe_device+0x45/0x70
[ 7.349233] [<ffffffff813f4d5b>] __driver_attach+0xab/0xb0
[ 7.349235] [<ffffffff813f4cb0>] ? driver_probe_device+0x70/0x70
[ 7.349237] [<ffffffff813f4cb0>] ? driver_probe_device+0x70/0x70
[ 7.349240] [<ffffffff813f3aec>] bus_for_each_dev+0x5c/0x90
[ 7.34...

Read more...

Joseph Salisbury (jsalisbury) wrote :

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?

Krzysztof Klimonda (kklimonda) wrote :

I just booted with 3.2.0-20 and the problem doesn't show up here.

Krzysztof Klimonda (kklimonda) wrote :

and yes, my motherboard is also Asus P8P67 PRO (rev3.0)

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

Avery-yates (avery-yates) wrote :

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.

Avery-yates (avery-yates) wrote :

My motherboard however is an asus P9X79-Pro

Avery-yates (avery-yates) wrote :

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.

AceLan Kao (acelankao) wrote :

So sorry about this,
I think we forgot to cheery pick other important commit.
I'll give you a testing kernel ASAP.

AceLan Kao (acelankao) wrote :

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/

AceLan Kao (acelankao) on 2012-03-31
Changed in linux (Ubuntu):
assignee: nobody → AceLan Kao (acelankao)
importance: Medium → Critical
AceLan Kao (acelankao) on 2012-03-31
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Tuomas Heino (iheino+ub) wrote :

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

Maxim Loparev (laplandersan) wrote :

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.

AceLan Kao (acelankao) wrote :

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
Krzysztof Klimonda (kklimonda) wrote :
Download full text (4.1 KiB)

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 0000000000000004
[ 15.720229] IP: [<ffffffffa0091a07>] asus_wmi_platform_init+0x87/0x150 [asus_wmi]
[ 15.720354] PGD 122837067 PUD 126e90067 PMD 0
[ 15.720567] Oops: 0000 [#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:[<ffffffffa0091a07>] [<ffffffffa0091a07>] asus_wmi_platform_init+0x87/0x150 [asus_wmi]
[ 15.722508] RSP: 0018:ffff8801251ddc88 EFLAGS: 00010246
[ 15.722571] RAX: 0000000000000000 RBX: ffff88012717f800 RCX: 000000000008e5f8
[ 15.722636] RDX: 0000000000000000 RSI: 00000000000165a0 RDI: ffff88012a802600
[ 15.722702] RBP: ffff8801251ddca8 R08: ffffea0004906240 R09: ffffffffa00910bb
[ 15.722766] R10: 0000000000000000 R11: 0000000000000000 R12: ffff88012717e800
[ 15.722831] R13: ffffffffa00fd080 R14: 00000000fffffff4 R15: ffff88012717e800
[ 15.722896] FS: 00007fcc75f92700(0000) GS:ffff88012f400000(0000) knlGS:0000000000000000
[ 15.722969] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 15.723032] CR2: 0000000000000004 CR3: 0000000125288000 CR4: 00000000000406f0
[ 15.723097] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 15.723162] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[ 15.723227] Process modprobe (pid: 797, threadinfo ffff8801251dc000, task ffff880124cd16f0)
[ 15.723299] Stack:
[ 15.723359] ffff8801251ddca8 00000000a00fb0a3 00000000fffffff4 ffff88012717f800
[ 15.723633] ffff8801251ddcd8 ffffffffa0092f75 ffff88012717e800 ffffffffa00fd080
[ 15.723907] ffffffffa00fd080 0000000000000000 ffff8801251ddcf8 ffffffffa0093184
[ 15.724181] Call Trace:
[ 15.724243] [<ffffffffa0092f75>] asus_wmi_add+0x95/0x250 [asus_wmi]
[ 15.724308] [<ffffffffa0093184>] asus_wmi_probe+0x54/0x80 [asus_wmi]
[ 15.724374] [<ffffffff813f6167>] platform_drv_probe+0x17/0x20
[ 15.724438] [<ffffffff813f49c8>] really_probe+0x68/0x190
[ 15.724503] [<ffffffff813f4c55>] driver_probe_device+0x45/0x70
[ 15.724567] [<ffffffff813f4d2b>] __driver_attach+0xab/0xb0
[ 15.724631] [<ffffffff813f4c80>] ? driver_probe_device+0x70/0x70
[ 15.724695] [<ffffffff813f4c80>] ? driver_probe_device+0x70/0x70
[ 15.724760] [<ffffffff813f3abc>] bus_for_each_dev+0x5c/0x90
[ 15.724824] [<ffffffff813f478e>] driver_attach+0x1e/0x20
[ 15.724887] [<ffffffff813f43e0>] bus_add_driver+0x1a0/0x270
[ 15.724951] [<ffffffff813f5296>] driver_register+0x76/0x140
[ 15.725016] [<ffffffff813f6726>] platform_driver_register+0x46/0x50
[ 15.725081] [<ffffffff813f6758>] platform_driver_probe+0x28/0xb0
[ 15.725146] [<ffffffff813f6ef1>] platform_create_bundle+0xc1/0xf0
[ 15.725212] [<ffffffffa0093130>] ? asus_wmi_add+0x250/0x250...

Read more...

AceLan Kao (acelankao) wrote :

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?

Krzysztof Klimonda (kklimonda) wrote :
Krzysztof Klimonda (kklimonda) wrote :
Krzysztof Klimonda (kklimonda) wrote :

I've attached lsmod output and dmesg log from the 3.2.0-20 kernel

AceLan Kao (acelankao) wrote :

The new kernel and patches is here[1], please have it a test.

1. http://people.canonical.com/~acelan/bugs/lp969576/2/

Stefan Taferner (taferner) wrote :

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.

Stefan Taferner (taferner) wrote :

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.

Kiril (kiril-mik-os) wrote :

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.

b3nn0 (agib) wrote :

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?

Kiril (kiril-mik-os) wrote :

With kernel from comment #22 volume keys works on my laptop.

AceLan Kao (acelankao) wrote :

Stefan, B3nn0,

Please try the kernel from comment #22, the problem should be fixed by that kernel.

panproteus (panproteus) wrote :

Patched kernel (comment #22) fixed issue here (Asus N55).

Johan Ferner (johan-ferner) wrote :

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.

Tim Gardner (timg-tpi) wrote :

asus-wmi: move WAPF variable into quirks_entry

Changed in linux (Ubuntu Precise):
status: In Progress → Fix Committed
Gabriel de Perthuis (g2p) wrote :

Patched kernel boots again. Asus P8Z68 here.

Martin Lindhe (martinlindhe) wrote :

Patched kernel from #22 worked for me too

Chris D (cdekter) wrote :

Asus UX31E here - patched kernel from #22 fixes kernel oops during boot, and hotkeys and suspend are again working.

Launchpad Janitor (janitor) wrote :
Download full text (5.2 KiB)

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
...

Read more...

Changed in linux (Ubuntu Precise):
status: Fix Committed → Fix Released
To post a comment you must log in.