kernel BUG at /build/buildd/linux-3.2.0/mm/slub.c:3427!; EIP is at kfree+0x10f/0x120
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Low
|
Unassigned |
Bug Description
Just a few days ago I fresh installed Ubuntu 12.04 32-bits in my laptop.
I have a bluetooth dongle attached to an USB port and a bluetooth mouse paired with it.
Since the installation I've been experiencing multiple crashes, quite randomly, until I found out that turning off my bluetooth mouse solved it. In fact, I had to do it so I could install Ubuntu.
As I said, I couldn't find yet a clearly situation in which the crash occurs. It can happen just a few seconds after turning the mouse on, hours later, or when returning from a suspension state. Actually, the only certain situation for a crash I found out is when returning from suspension mode.
So, some steps to reproduce this bug are:
1) Turn on bluetooth mouse
2) Turn on computer and log on Ubuntu
3) Wait
or, alternatively:
3.0) Suspend your session
3.1) Return from suspension
Results can be three:
A) Computer is completely frozen, showing the last screen. Mouse cursor is on the screen, you can't move it and any keyboard command has no effects (I can't go to terminal nor restart X).
B) Similar to A, but the screen is black, showing just the cursor.
C) Screen shows lots of messages, probably from a kernel oops.
In all cases, I have to do a hard reboot.
I've been experiencing this issue since Ubuntu 11.10 (Ubuntu 11.04 worked flawlessly). However, I don't think it's just an Ubuntu related issue. Trying to install Fedora 16 also resulted in multiple crashes.
I tried to reproduce these situations, and I'm attaching the correspondent kern.log here. However, I didn't found any relevant information in the output of Situation 2 and 3.
Situation 1) Turned the mouse on, with system already running. Just a few seconds after, screen went black (with cursor in it) and totally frozen. Had to do a hard reboot.
Situation 2) Turned the mouse on before booting the system. After login, waited a few moments and entered suspension mode. After some moments returned from suspension. Ubuntu was froozen in lock screen.
Situation 3) After the crash in situation 2, turned again the computer on. After login, moved the mouse a bit and screen froze.
I tried to reproduce the kernel oops, but wasn't successful. So I am attaching the kern.log of one of the kernel oops I had yesterday. I think it will be useful.
Finally, I just like to add it's very common my wallpaper and other preferences are gone after a crash like that, and I have to do change them all over again.
WORKAROUND: Disable Bluetooth.
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
**** List of PLAYBACK Hardware Devices ****
card 0: Intel [HDA Intel], device 0: ALC262 Analog [ALC262 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
ApportVersion: 2.0.1-0ubuntu8
Architecture: i386
ArecordDevices:
**** List of CAPTURE Hardware Devices ****
card 0: Intel [HDA Intel], device 0: ALC262 Analog [ALC262 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf6700000 irq 46'
Mixer name : 'Realtek ALC262'
Components : 'HDA:10ec0262,
Controls : 20
Simple ctrls : 11
DistroRelease: Ubuntu 12.04
EcryptfsInUse: Yes
HibernationDevice: RESUME=
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
MachineType: SAMSUNG ELECTRONICS CO., LTD. R509
Package: linux (not installed)
ProcEnviron:
TERM=xterm
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=
ProcVersionSign
RelatedPackageV
linux-
linux-
linux-firmware 1.79
SourcePackage: linux
Tags: precise precise
Uname: Linux 3.2.0-25-
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 04/01/2010
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 03LP.M008.
dmi.board.name: R509
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: Not Applicable
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: R509
dmi.product.
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 1003624
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.