8086:0091 Kernel Panic when re-enabling wifi via Fn+F2 on Dell XPS 15z

Bug #1021086 reported by Rainer Rohde on 2012-07-04
32
This bug affects 5 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
High
Joseph Salisbury

Bug Description

I get a kernel panic when when re-enabling my wireless card pressing Fn+F2 on my Dell XPS 15z. Disabling it works just fine, but re-enabling it kills it.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: linux-image-3.5.0-3-generic 3.5.0-3.3
ProcVersionSignature: Ubuntu 3.5.0-3.3-generic 3.5.0-rc5
Uname: Linux 3.5.0-3-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
ApportVersion: 2.2.5-0ubuntu2
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: PCH [HDA Intel PCH], device 0: ALC269VB Analog [ALC269VB Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: rrohde 1887 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'PCH'/'HDA Intel PCH at 0xf1c00000 irq 27'
   Mixer name : 'Intel CougarPoint HDMI'
   Components : 'HDA:10ec0269,10280446,00100100 HDA:80862805,10280446,00100000'
   Controls : 24
   Simple ctrls : 11
Date: Wed Jul 4 18:23:01 2012
MachineType: Dell Inc. Dell System XPS 15Z
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-3-generic root=UUID=b1eec17b-cae9-41d1-941c-029a89deb344 ro quiet splash acpi=noirq vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.5.0-3-generic N/A
 linux-backports-modules-3.5.0-3-generic N/A
 linux-firmware 1.82
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/20/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A10
dmi.board.name: 00WW5M
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 0.1
dmi.modalias: dmi:bvnDellInc.:bvrA10:bd02/20/2012:svnDellInc.:pnDellSystemXPS15Z:pvr:rvnDellInc.:rn00WW5M:rvrA00:cvnDellInc.:ct8:cvr0.1:
dmi.product.name: Dell System XPS 15Z
dmi.sys.vendor: Dell Inc.

Rainer Rohde (rainer-rohde) wrote :
Brad Figg (brad-figg) on 2012-07-04
Changed in linux (Ubuntu):
status: New → Confirmed
Rainer Rohde (rainer-rohde) wrote :

Just a couple of screen photos that document the effect...

Rainer Rohde (rainer-rohde) wrote :
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.5kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5-rc5-quantal/

Changed in linux (Ubuntu):
importance: Undecided → High
tags: added: needs-upstream-testing
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-unable-to-test-upstream
removed: needs-upstream-testing
Joseph Salisbury (jsalisbury) wrote :

Do you happen to know if this issue also happened in Precise(12.04)?

Rainer Rohde (rainer-rohde) wrote :

Sadly, no. I only recently got this laptop and installed the current Quantal Alpha built on it right away.

Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to boot the precise kernel on this installation and see if the bug still exists? The precise kernel can be downloaded from:

https://launchpad.net/~canonical-kernel-team/+archive/ppa/+build/3576352/+files/linux-image-3.2.0-26-generic_3.2.0-26.41_amd64.deb

Rainer Rohde (rainer-rohde) wrote :

When I try to install the kernel package, I get the following error message: "Failed to satisfy all dependencies (broken cache)". I am currently experiencing a bug with updating python3. Not sure if this is the reason for the error message.

Joseph Salisbury (jsalisbury) wrote :

Can you test the latest upstream v3.2 kernel:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2.23-precise/

Rainer Rohde (rainer-rohde) wrote :

uname -r
3.2.23-030223-generic

Joseph,

good news (I hope) -- the latest 3.2.23 kernel does *not* give me a kernel panic when using Fn+F2 to re-enable wifi. I tried it again with 3.5.0-4-generic, and it results in kernel panic each -- time!

On a side note, I noticed that with 3.2.23, after multiple times of trying, pressing Fn+F2 did no longer turn wifi back on for some reason (Bluetooth, on the other hand, came back on). See pasted dmesg output below:

[ 148.026701] iwlwifi 0000:03:00.0: Error sending COEX_PRIORITY_TABLE_CMD: enqueue_hcmd failed: -5
[ 148.026703] iwlwifi 0000:03:00.0: Could not complete ALIVE transition: -5
[ 148.026706] iwlwifi 0000:03:00.0: Failed to start RT ucode: -5
[ 148.027413] iwlwifi 0000:03:00.0: Unable to initialize device.
[ 148.027514] ieee80211 phy0: Hardware restart was requested

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Joseph Salisbury (jsalisbury) wrote :

I'd like to perform a kernel bisect to identify which commit introduced this regression. First we need to identify the kernel version when this first appeared. Would it be possible for you to test the following two kernels and report back if they have the bug or not:

v3.3 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.3-precise/
v3.4 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-rc2-precise/

tags: added: performing-bisect
Rainer Rohde (rainer-rohde) wrote :

Here are my test results:

uname -r
3.4.0-030400rc2-generic >>> WORKS!

uname -r
3.3.0-030300-generic >>> WORKS!

Rainer Rohde (rainer-rohde) wrote :

Here we go:

uname -r
3.5.0-030500rc1-generic >>> KERNEL PANIC! (Fatal exception in interrupt)

Joseph Salisbury (jsalisbury) wrote :

@Rainer,

I started a kernel bisect between v3.4 and v3.5-rc1. The first test kernel is up to comit:

6f73b3629f774c6cba589b15fd095112b25ca923

The test kernel can be downloaded from:
http://people.canonical.com/~jsalisbury/lp1021086/

Can you test that kernel and report back if it has the bug or not?

Thanks in advance!

Rainer Rohde (rainer-rohde) wrote :

Results:

uname -r
3.4.0-030400-generic >>> WORKS!

Joseph Salisbury (jsalisbury) wrote :

I built the next test kernel, which is up to commit:
07acfc2a9349a8ce45b236c2624dad452001966b

This kernel is available from:
http://people.canonical.com/~jsalisbury/lp1021086/

Can you test that kernel and report back if it has the bug or not?

Thanks in advance!

Rainer Rohde (rainer-rohde) wrote :

There you are:

uname -r
3.4.0-030400-generic >>> KERNEL PANIC! (Fatal exception in interrupt)

Joseph Salisbury (jsalisbury) wrote :

I built the next test kernel, which is up to commit:
654443e20dfc0617231f28a07c96a979ee1a0239

This kernel is available from:
http://people.canonical.com/~jsalisbury/lp1021086/

Can you test that kernel and report back if it has the bug or not?

Thanks in advance!

Rainer Rohde (rainer-rohde) wrote :

Here you go, Joseph:

uname -r
3.4.0-030400-generic >>> WORKS!

Joseph Salisbury (jsalisbury) wrote :

I built the next test kernel, which is up to commit:
8c914028f5ddaa417b7d0f4b7fdc24caceaa8043

This kernel is available from:
http://people.canonical.com/~jsalisbury/lp1021086/

Can you test that kernel and report back if it has the bug or not?

Thanks in advance!

Rainer Rohde (rainer-rohde) wrote :

Works again:

uname -r
3.4.0-030400rc6-generic >>> WORKS!

Joseph Salisbury (jsalisbury) wrote :

I built the next test kernel, which is up to commit:
2f78d8e249973f1eeb88315e6444e616c60177ae

This kernel is available from:
http://people.canonical.com/~jsalisbury/lp1021086/

Can you test that kernel and report back if it has the bug or not?

Thanks in advance!

Rainer Rohde (rainer-rohde) wrote :

Alright, here we go again:

uname -r
3.4.0-030400-generic >>> KERNEL PANIC! (Fatal exception in interrupt)

Joseph Salisbury (jsalisbury) wrote :

I built the next test kernel, which is up to commit:
0ed462875a7825e89674f3e7ff9d67835feb9f73

This kernel is available from:
http://people.canonical.com/~jsalisbury/lp1021086/

Can you test that kernel and report back if it has the bug or not?

There's about six more kernels that might need to be tested before we narrow down the commit that caused this regression.

Thanks in advance!

Rainer Rohde (rainer-rohde) wrote :

Here's this one's result:

uname -r
3.4.0-030400rc5-generic >>> KERNEL PANIC! (Fatal exception in interrupt)

Joseph Salisbury (jsalisbury) wrote :

I built the next test kernel, which is up to commit:
341352d13dae752610342923c53ebe461624ee2c

This kernel is available from:
http://people.canonical.com/~jsalisbury/lp1021086/

Can you test that kernel and report back if it has the bug or not?

Rainer Rohde (rainer-rohde) wrote :

Here we go:

uname -r
3.4.0-030400rc5-generic >>> WORKS!

Joseph Salisbury (jsalisbury) wrote :

I built the next test kernel, which is up to commit:
12d9568333de3bfc50ff8d3312c097ba7ea7fe3c

This kernel is available from:
http://people.canonical.com/~jsalisbury/lp1021086/

Can you test that kernel and report back if it has the bug or not?

Rainer Rohde (rainer-rohde) wrote :

This time, I got this:

uname -r
3.4.0-030400rc5-generic >>> KERNEL PANIC! (Fatal exception in interrupt)

Joseph Salisbury (jsalisbury) wrote :

I built the next test kernel, which is up to commit:
03bed29e0501b5757ce62ebdb01829f7bd8d9819

This kernel is available from:
http://people.canonical.com/~jsalisbury/lp1021086/

Can you test that kernel and report back if it has the bug or not?

Rainer Rohde (rainer-rohde) wrote :

Result:

uname -r
3.4.0-030400rc5-generic >>> KERNEL PANIC! (Fatal exception in interrupt)

Joseph Salisbury (jsalisbury) wrote :

I built the next test kernel, which is up to commit:
d8b3fc59f24c0e0e965efbb49be4199360125aa7

This kernel is available from:
http://people.canonical.com/~jsalisbury/lp1021086/

Can you test that kernel and report back if it has the bug or not?

Rainer Rohde (rainer-rohde) wrote :

Next:

uname -r
3.4.0-030400rc5-generic >>> KERNEL PANIC! (Fatal exception in interrupt)

Joseph Salisbury (jsalisbury) wrote :

I built the next test kernel, which is up to commit:
abb7fbb4a727f8bd446658a061a039674c907aec

This kernel is available from:
http://people.canonical.com/~jsalisbury/lp1021086/

Can you test that kernel and report back if it has the bug or not?

Rainer Rohde (rainer-rohde) wrote :

Again:

uname -r
3.4.0-030400rc5-generic >>> KERNEL PANIC! (Fatal exception in interrupt)

Joseph Salisbury (jsalisbury) wrote :

I built the next test kernel, which is up to commit:
a46c3e424b2325c2592b65999466d4445e410b24

This kernel is available from:
http://people.canonical.com/~jsalisbury/lp1021086/

Can you test that kernel and report back if it has the bug or not?

Rainer Rohde (rainer-rohde) wrote :

And again:

uname -r
3.4.0-030400rc5-generic >>> KERNEL PANIC! (Fatal exception in interrupt)

Joseph Salisbury (jsalisbury) wrote :

I built the next test kernel, which is up to commit:
83ce21de686a67b74ae9ba419c0fc144029a3063

This kernel is available from:
http://people.canonical.com/~jsalisbury/lp1021086/

Can you test that kernel and report back if it has the bug or not?

Rainer Rohde (rainer-rohde) wrote :

Does that mean we're done now?

uname -r
3.4.0-030400rc5-generic >>> KERNEL PANIC! (Fatal exception in interrupt)

Joseph Salisbury (jsalisbury) wrote :

Looks like we could have two more kernels or so to test:

Bisecting: 3 revisions left to test after this (roughly 2 steps)
[dd551ab7b47ace14753b0d73f79437cc35adcf6b] iwlwifi: include rssi as part of decision making for reduce txpower

Joseph Salisbury (jsalisbury) wrote :

I built the next test kernel, which is up to commit:
dd551ab7b47ace14753b0d73f79437cc35adcf6b

This kernel is available from:
http://people.canonical.com/~jsalisbury/lp1021086/

Can you test that kernel and report back if it has the bug or not?

Rainer Rohde (rainer-rohde) wrote :

Here we go:

uname -r
3.4.0-030400rc5-generic >>> KERNEL PANIC! (Fatal exception in interrupt)

Joseph Salisbury (jsalisbury) wrote :

I built the next test kernel, which is up to commit:
f3a138c10b9a5f716d2b773e0ae08401ebd19f80

This kernel is available from:
http://people.canonical.com/~jsalisbury/lp1021086/

Can you test that kernel and report back if it has the bug or not?

tags: added: kernel-da-key
Rainer Rohde (rainer-rohde) wrote :

Here you go:

uname -r
3.4.0-030400rc5-generic >>> WORKS!

Rainer Rohde (rainer-rohde) wrote :

So, what's next?

Joseph Salisbury (jsalisbury) wrote :

Sorry for the delay, Rainer. I was out last week. I will start on this bisect again tomorrow. We are a kernel or two away from the bad commit.

Thanks again for testing!

Joseph Salisbury (jsalisbury) wrote :

test post. please ignore.

Joseph Salisbury (jsalisbury) wrote :

I built the next test kernel, which is up to commit:
9365073f30ae2dcf7501cc792749825712c12c2b

This kernel is available from:
http://people.canonical.com/~jsalisbury/lp1021086/

Can you test that kernel and report back if it has the bug or not?

Rainer Rohde (rainer-rohde) wrote :

Here you are:

uname -r
3.4.0-030400rc5-generic >>> KERNEL PANIC! (Fatal exception in interrupt)

Joseph Salisbury (jsalisbury) wrote :

Hi Rainer,

It appears commit dd551ab7b47ace14753b0d73f79437cc35adcf6b introduced the regression. I tried a revert of this commit, but it looks like some work will need to be done to get commit to revert cleanly.

I'll update you shortly when a test kernel with this commit reverted is available.

Thanks again for all your help!

Changed in linux (Ubuntu):
assignee: nobody → Joseph Salisbury (jsalisbury)
status: Confirmed → In Progress
tags: added: bisect-done
removed: performing-bisect
tags: removed: kernel-unable-to-test-upstream
Rainer Rohde (rainer-rohde) wrote :

Sounds good Joseph. Nice to know that you've nailed it. :) Thank you for your work.

Joseph Salisbury (jsalisbury) wrote :

Hi Rainer,

I created a Quantal test kernel with commit dd551ab7b47ace14753b0d73f79437cc35adcf6b reverted.

This kernel is available from:
http://people.canonical.com/~jsalisbury/lp1021086/

Can you test that kernel and report back if it has the bug or not?

Joseph Salisbury (jsalisbury) wrote :

Not with the test kernel you will need to install both the linux-image and linux-image-extra .debs

Rainer Rohde (rainer-rohde) wrote :

Currently I am unable to test because an update today broke Xorg on my 12.10 alpha 3 and now I am unable to get a GUI. Once this is fixed, I will get right to it.

Rainer Rohde (rainer-rohde) wrote :

Says "A later version is already installed" when I try to install this kernel.

uname -r
3.5.0-7-generic

Was updated earlier today via dist-upgrade. What now?

Joseph Salisbury (jsalisbury) wrote :

Are you running the following from a terminal:

sudo dpkg -i linux-image-3.5.0-7-generic_3.5.0-7.7~lp1021086v1_amd64.deb
then
sudo dpkg -i linux-image-extra-3.5.0-7-generic_3.5.0-7.7~lp1021086v1_amd64.deb

Can you post the output from uname -a

Rainer Rohde (rainer-rohde) wrote :

I did... here's the output:

uname -r
3.5.0-7-generic

Joseph Salisbury (jsalisbury) wrote :

Can you also post the output from:

uname -a

That will give the full text.

Rainer Rohde (rainer-rohde) wrote :

Here you go:

Linux rrohde-Dell-XPS 3.5.0-7-generic #7-Ubuntu SMP Tue Jul 31 07:22:20 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

Joseph Salisbury (jsalisbury) wrote :

I created another Quantal test kernel with commit dd551ab7b47ace14753b0d73f79437cc35adcf6b reverted and with an updated version string.

This kernel is available from:
http://people.canonical.com/~jsalisbury/lp1021086/

Rainer Rohde (rainer-rohde) wrote :

Here you go:

 uname -a
Linux rrohde-Dell-XPS 3.5.0-7-generic #8~lp1021086v1 SMP Thu Aug 2 21:47:11 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux >>> WORKS!

Joseph Salisbury (jsalisbury) wrote :

Hi Rainer,

I think it's safe to say that commit dd551ab7b47ace14753b0d73f79437cc35adcf6b introduced this regression. I'll open an upstream bug for this and request it be reverted in Quantal until a fix is available upstream.

Thanks so much for your help with this bug!

Rainer Rohde (rainer-rohde) wrote :

This is good news, Joseph. Thanks for all your hard work. :)

Joseph Salisbury (jsalisbury) wrote :

@Rainer,

It appears commit e19ebcab01cc130fa will fix this bug. It has been submitted to linux-stable and should be in v3.5 soon. I'll build a quantal test kernel with this commit applied and post it shortly.

Joseph Salisbury (jsalisbury) wrote :

I created another Quantal test kernel with commit e19ebcab01cc130fa backported and applied

This kernel is available from:
http://people.canonical.com/~jsalisbury/lp1021086/

Can you test that kernel and report back if it has the bug or not?

Rainer Rohde (rainer-rohde) wrote :

Here's the result:

uname -a
Linux rrohde-Dell-XPS 3.5.0-7-generic #8~lp1021086v3 SMP Fri Aug 3 16:54:32 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux >>> WORKS!

summary: - Kernel Panic when re-enabling wifi via Fn+F2 on Dell XPS 15z
+ 8086:0091 Kernel Panic when re-enabling wifi via Fn+F2 on Dell XPS 15z
Launchpad Janitor (janitor) wrote :
Download full text (3.7 KiB)

This bug was fixed in the package linux - 3.5.0-8.8

---------------
linux (3.5.0-8.8) quantal-proposed; urgency=low

  [ Andy Whitcroft ]

  * ubuntu: AUFS -- add BOM and automated update script
  * ubuntu: AUFS -- include the aufs_types.h file in linux-libc-headers
    - LP: #684666
  * ubuntu: AUFS -- update aufs-update to track new locations of headers
  * ubuntu: AUFS -- clean up the aufs updater and BOM
  * ubuntu: AUFS -- documentation on updating aufs2
  * ubuntu: AUFS -- fix undefined __devcgroup_inode_permission
  * ubuntu: AUFS -- update to 4cf5db36bcd9748e8e7270022f295f84d1fc2245
  * ubuntu: AUFS -- updateconfigs following update
  * ubuntu: AUFS -- suppress benign plink warning messages
    - LP: #621195
  * ubuntu: AUFS -- enable in config and makefile
  * ubuntu: AUFS -- disable in favor of overlayfs
  * ubuntu: AUFS -- adapt to the new changelog handling
  * ubuntu: AUFS -- sort out the relative header paths
  * ubuntu: AUFS -- update to d266b0c5d0693d6383976ee54b9e2c0fa9a3f5b0
  * ubuntu: AUFS -- aufs3-base.patch
  * ubuntu: AUFS -- aufs3-standalone.patch
  * ubuntu: AUFS -- update to 4a5e660ed7f5c1d0467c81c535d0fedcfe62d15f
  * ubuntu: AUFS -- reenable

  [ Chris Van Hoof ]

  * [Config] Add cifs support to the nfs-modules list
    - LP: #1031398

  [ Ilan Peer ]

  * (pre-stable) iwlwifi: Check BSS ctx active before call mac80211
    - LP: #1021086

  [ John Johansen ]

  * SAUCE: Update aufs for build failure caused by apparmor backport

  [ Tim Gardner ]

  * SAUCE: firmware: Remove ess files duplicated in linux-firmware
  * SAUCE: firmware: Remove kaweth files duplicated in linux-firmware
  * SAUCE: firmware: Remove obsolete Chelsio cxgb3 firmware
  * SAUCE: firmware: Remove cxgb3 files duplicated in linux-firmware
  * SAUCE: firmware: Remove edgeport files duplicated in linux-firmware
  * SAUCE: firmware: Remove ti_usb_3410_5052 duplicated in linux-firmware
  * SAUCE: firmware: Remove adaptec files duplicated in linux-firmware
  * SAUCE: firmware: Remove advansys files duplicated in linux-firmware
  * SAUCE: firmware: Remove ambassador files duplicated in linux-firmware
  * SAUCE: firmware: Remove av7110 files duplicated in linux-firmware
  * SAUCE: cpia2: Declare MODULE_FIRMWARE usage
  * SAUCE: firmware: Remove cpia2 files duplicated in linux-firmware
  * SAUCE: firmware: Remove korg files duplicated in linux-firmware
  * SAUCE: firmware: Remove matrox files duplicated in linux-firmware
  * SAUCE: firmware: Remove r128 files duplicated in linux-firmware
  * SAUCE: firmware: Remove radeon files duplicated in linux-firmware

  [ Upstream Kernel Changes ]

  * intel_idle: initial IVB support
  * KVM: x86: change PT_FIRST_AVAIL_BITS_SHIFT to avoid conflict with EPT
    Dirty bit
  * KVM: VMX: Use EPT Access bit in response to memory notifiers
  * KVM: VMX: Enable EPT A/D bits if supported by turning on relevant bit
    in EPTP
  * KVM: VMX: Add parameter to control A/D bits support, default is on
  * KVM: VMX: Add EPT A/D bits definitions
  * KVM: VMX: Implement PCID/INVPCID for guests with EPT
  * xhci: Export Latency Tolerance Messaging capabilities.
  * USB: Fix LPM disable/enable during device reset.
  * usb: convert ...

Read more...

Changed in linux (Ubuntu):
status: In Progress → Fix Released

will upgrade tonight and test this new kernel

The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions.

Shawn Pringle (shawn.pringle) wrote :

I have a similar but worse problem. I tried to disable wifi and it panicked. Now it panics on normal boot. In recovery console, it panics when enabling networking. If I disable the wifi mac80211 module, it boots but panics when I plug in the mouse or keyboard. The device is an EXO netbook.

Reboots do not help. Powerdowns and restats do not help.
How do I set this to a state where ir doesn't panic anymore?

The work around is this: on panic unplug everything even the AC and remove the battery or wait for it to stop completely. Then perhaps wait five minutes. Dance in a circle saying "Thank you Shawn. I am grateful" three times. Then plug it back in again and restart.

To disable wifi, the same procedure would seem to cause fewer problems but I feel you could simply go through the shutdown procedure. I will post later from the computer later for devs

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers