[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#679519: linux-image-3.2.0-3-rt-amd64: usbhid causes crashes in applications by memory corruption



On Fri, 2012-06-29 at 11:47 +0100, Steve Graham wrote:
> Package: src:linux Version: 3.2.21-2
> X-Mailer: reportbug 4.12.6
> Date: Fri, 29 Jun 2012 11:26:06 +0100
> 
> Severity: normal Tags: upstream
> 
> When I plug in a USB mouse (or keyboard, but I don't normally do that) into
> this laptop, the first event -- mouse movement -- causes some applications to
> crash with a memory corruption message from malloc.
> 
> Applications which reliably crash every time are audacious, cairo-dock and
> zenity. However, if re-started, they may or may not crash again.
> 
> If usbhid is blacklisted, no crashes occur, although, obviously, the mouse
> does not work. I can use the built-in trackpad.
> 
> I've tried a "vanilla" kernel compiled from source (although not the Debian
> way; sorry) and the result is the same.

Is that a standard (non-realtime) kernel?  If not, can you also test a
standard kernel configuration (linux-image-3.2.0-3-amd64)?

> I don't know much about kernel modules
> and memory, so I don't know how to provide more useful information.
> Obviously usbhid must be in use on every linux desktop or laptop in the world,
> and I've found no other reports of similar problems. Am I the only person
> using 64-bit linux on a dual-core Intel Atom?
[...]

Probably not!

Please try booting with the extra kernel parameters:

    memory_corruption_check=1 memory_corruption_check_size=640K memory_corruption_check_period=5

Does that avoid the problem, and if so what does the kernel log show
after you plug in the device?

Ben.

-- 
Ben Hutchings
Lowery's Law:
             If it jams, force it. If it breaks, it needed replacing anyway.

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: