Bug#679519: same on non-RT kernel (Re: usbhid causes crashes in applications by memory corruption)

To: 679519@bugs.debian.org
Subject: Bug#679519: same on non-RT kernel (Re: usbhid causes crashes in applications by memory corruption)
From: Steve Graham <bugs@annaghvarn.plus.com>
Date: Fri, 29 Jun 2012 17:30:01 +0100
Message-id: <[🔎] 4FEDD809.3090308@annaghvarn.plus.com>
Reply-to: Steve Graham <bugs@annaghvarn.plus.com>, 679519@bugs.debian.org
In-reply-to: <handler.679519.B.134096733022731.ack@bugs.debian.org>
References: <[🔎] 4FED87B4.8070801@annaghvarn.plus.com> <handler.679519.B.134096733022731.ack@bugs.debian.org>

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


Identical behaviour on linux-image-3.2.0-3-amd64

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?

It seems that X86_CHECK_BIOS_CORRUPTION is disabled in the Debian kernels. I'm compiling a customone with it enabled and will post any significant results.

Reply to:

Follow-Ups:
- Bug#679519: same on non-RT kernel (Re: usbhid causes crashes in applications by memory corruption)
  - From: Ben Hutchings <ben@decadent.org.uk>

References:
- Bug#679519: linux-image-3.2.0-3-rt-amd64: usbhid causes crashes in applications by memory corruption
  - From: Steve Graham <steve.graham@annaghvarn.plus.com>

Prev by Date: Bug#666108: megaraid_sas: which patches are needed for 2.6.32.y?
Next by Date: Bug#679519: same on non-RT kernel (Re: usbhid causes crashes in applications by memory corruption)
Previous by thread: Bug#679519: linux-image-3.2.0-3-rt-amd64: usbhid causes crashes in applications by memory corruption
Next by thread: Bug#679519: same on non-RT kernel (Re: usbhid causes crashes in applications by memory corruption)
Index(es):
- Date
- Thread