kernel panic when removing mceusb module

[ill]

when using modprobe to manually remove the mceusb kernel driver, the machine will inevitably panic a short while afterwards everytime on 12.10.
---
ApportVersion: 2.6.1-0ubuntu6
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ill 1714 F.... xfce4-volumed
                      ill 1735 F.... pulseaudio
 /dev/snd/controlC1: ill 1714 F.... xfce4-volumed
                      ill 1735 F.... pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
DistroRelease: Ubuntu 12.10
InstallationDate: Installed on 2012-07-28 (124 days ago)
InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
MachineType: System manufacturer System Product Name
MarkForUpload: True
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.5.0-18-generic root=UUID=d1b86751-29b4-4068-bebb-3d662aa6d99b ro rootflags=subvol=@ xbmc=autostart
ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
RelatedPackageVersions:
 linux-restricted-modules-3.5.0-18-generic N/A
 linux-backports-modules-3.5.0-18-generic N/A
 linux-firmware 1.95
RfKill:

Tags: quantal
Uname: Linux 3.5.0-18-generic x86_64
UpgradeStatus: Upgraded to quantal on 2012-10-12 (48 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 02/04/2010
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: ASUS M2N-SLI DELUXE ACPI BIOS Revision 5001
dmi.board.name: M2N-SLI DELUXE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.XX
dmi.chassis.asset.tag: 123456789000
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2N-SLIDELUXEACPIBIOSRevision5001:bd02/04/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N-SLIDELUXE:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1084190/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Edward Donovan (edward.donovan)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We need some more information from you before we can start working on this bug.

Please run the following command which will attach necessary information:

  apport-collect 1084190

For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies. Thanks in advance!

[ill (illumilore)]

apport information

[ill (illumilore)]

apport information

[ill (illumilore)]

apport information

[ill (illumilore)]

apport information

[ill (illumilore)]

apport information

[ill (illumilore)]

apport information

[ill (illumilore)]

apport information

[ill (illumilore)]

apport information

[ill (illumilore)]

apport information

[ill (illumilore)]

apport information

[ill (illumilore)]

apport information

[ill (illumilore)]

apport information

[ill (illumilore)]

apport information

[Luis Henriques (henrix)]

ill, do you still get this kernel panic with recent Quantal kernels? If so, is it possible to post a kernel log containing the stack trace? (you can get the stack trace by running the command "dmesg" on a terminal. If the system freezes completely, a photo would also be OK). Thanks.

[ill (illumilore)]

The recent Quantal kernels don't boot on my machine.

[Luis Henriques (henrix)]

Hi! Can you please provide more information? For example: when did this started to happen (last kernel version known to boot)? Is it a crash? Do you believe this is still due to the mceusb driver? (if not, could you please open a new bug report?). Thanks.

[ill (illumilore)]

It started on 12.10 (3.5 kernel), as the previous versions of ubuntu did not ignore the blacklist.conf file so would not load with mceusb.

It is a complete machine lockup

It only happens when removing the mceusb driver from what I have found. I am able to unload other mods without problems.

[Luis Henriques (henrix)]

I took a look at this driver and found that there's something wrong with the mceusb_dev_disconnect() function, which is invoked when the driver is rmmod'ed. Would you be able to try a test kernel i've uploaded here:

http://people.canonical.com/~henrix/lp1084190/v1/

You only need to download the .deb files. There's a patch there that contains the changes to the driver. Please let me know if this solves the problem (sorry, I don't have the hardware to test it myself). Thanks.

[Daniel Hartwig (wigs)]

Please test the proposed fix.

[ill (illumilore)]

I did. It works.

[Daniel Hartwig (wigs)]

Patch from <http://people.canonical.com/~henrix/lp1084190/v1/>.

[Luis Henriques (henrix)]

And can you confirm you still see the kernel panic with recent Quantal kernels? It would be great if you could get us the kernel logs after a panic (either from dmesg or photo). Thanks.

[ill (illumilore)]

I cannot test it on more recent kernels, as anything that is 3.6 and above does not boot on m2n-sli deluxe motherboards.

[penalvch (penalvch)]

ill, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

[ill (illumilore)]

this still happens

[Brad Figg (brad-figg)]

This change was made by a bot.

[Luis Henriques (henrix)]

ill, is it possible for you to capture the panic as per comment #16? Thanks.

[penalvch (penalvch)]

Pending panic capture following https://wiki.ubuntu.com/DebuggingSystemCrash as requested in #16.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]