Comment 42 for bug 1041883

Alex, my experiments show that the problem is caused by wifi and bluetooth
initialization in rfkill. I've noticed that the problem can be reproduced
with these turned on (uncommented). I tried enabling/disabling wifi and
bluetooth NOT simultaneously, one is on and other is off. After reboot I
could get kernel crash almost 100%. However, when they're turned on or off
at the same time, booting is stable in most cases. As for me, it seems like
some kind of race condition. Do rfkills have something in common with
interrupt handling?

2012/9/18 Carsten Otto <email address hidden>

> Sorry, I used the wrong account. The last comment was done by me.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1041883
>
> Title:
> Recent patch to asus-wmi module makes system unbootable
>
> Status in “linux” package in Ubuntu:
> In Progress
> Status in “linux” source package in Quantal:
> In Progress
>
> Bug description:
> There has been recently a patch to the asus-wmi module (see
> http://comments.gmane.org/gmane.linux.kernel/1315719). This updated
> module is part of the linux-image-3.5.0-11-generic package. Using this
> module renders the system unbootable (For reasons probably described
> in the logs, but currently beyond my knowledge, stacktraces can be
> seen though)
>
> I have applied this patch before through dkms and had the exact same
> problems. So I removed the patch, it is now part of the ubuntu kernel
> though.
>
> The behaviour seems somewhat random, sometimes the system boots, and
> the Function hotkeys (keyboard backlight, volume etc) work (except the
> known problem with the brightness keys and ambient light sensor). But
> most of the time the system simply wont boot. I can however first
> start the system in recovery mode, and then proceed normal boot, the
> problem does not occur then.
>
> Hardware: Asus Zenbook UX32V
>
> If further information/testing is needed, please contact me.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 12.10
> Package: linux-image-3.5.0-11-generic 3.5.0-11.11
> ProcVersionSignature: Ubuntu 3.5.0-10.10-generic 3.5.1
> Uname: Linux 3.5.0-10-generic x86_64
> ApportVersion: 2.5.1-0ubuntu2
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: peterrus 2343 F.... pulseaudio
> /dev/snd/pcmC0D0c: peterrus 2343 F...m pulseaudio
> /dev/snd/pcmC0D0p: peterrus 2343 F...m pulseaudio
> Date: Sun Aug 26 18:08:05 2012
> EcryptfsInUse: Yes
> HibernationDevice: RESUME=UUID=2e120efe-dafa-40e8-868d-06223b0be158
> InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64
> (20120627)
> MachineType: ASUSTeK COMPUTER INC. UX32VD
> ProcEnviron:
> TERM=xterm
> PATH=(custom, user)
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> ProcFB: 0 inteldrmfb
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-10-generic
> root=UUID=9bb3948b-2fd3-46c4-b0bb-0ae32a87278a ro quiet splash
> pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 nmi_watchdog=0
> RelatedPackageVersions:
> linux-restricted-modules-3.5.0-10-generic N/A
> linux-backports-modules-3.5.0-10-generic N/A
> linux-firmware 1.90
> SourcePackage: linux
> StagingDrivers: rts5139
> UpgradeStatus: No upgrade log present (probably fresh install)
> dmi.bios.date: 06/29/2012
> dmi.bios.vendor: American Megatrends Inc.
> dmi.bios.version: UX32VD.207
> dmi.board.asset.tag: ATN12345678901234567
> dmi.board.name: UX32VD
> dmi.board.vendor: ASUSTeK COMPUTER INC.
> dmi.board.version: 1.0
> dmi.chassis.asset.tag: No Asset Tag
> dmi.chassis.type: 10
> dmi.chassis.vendor: ASUSTeK COMPUTER INC.
> dmi.chassis.version: 1.0
> dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvrUX32VD.207:bd06/29/2012:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
> dmi.product.name: UX32VD
> dmi.product.version: 1.0
> dmi.sys.vendor: ASUSTeK COMPUTER INC.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1041883/+subscriptions
>