FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian Kernel

 
 
LinkBack Thread Tools
 
Old 07-02-2012, 06:29 PM
Steve Graham
 
Default Bug#679519: unable to obtain better info ( usbhid causes crashes in applications by memory corruption))

After building a kernel with X86_CHECK_BIOS_CORRUPTION enabled, I set it to scan (almost) as
advised. No corruption of the low memory was reported after running some hours either with or
without usbhid loaded.


(Booting with memory_corruption_check_size=640K caused an immediate kernel panic -- early exception
08 --though. Changing it to 620k allowed the boot to continue normally.)


I took the opportunity to include kmemleak in the new kernel as well. After some uptime, one orphan
object was always found, but it happened either with or without usbhid ever having been loaded. To
judge from the traceback it was something ACPI-related anyway.


So, basically, no progress.



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4FF1E897.2040601@annaghvarn.plus.com">http://lists.debian.org/4FF1E897.2040601@annaghvarn.plus.com
 
Old 07-03-2012, 05:15 AM
Ben Hutchings
 
Default Bug#679519: unable to obtain better info ( usbhid causes crashes in applications by memory corruption))

On Mon, 2012-07-02 at 19:29 +0100, Steve Graham wrote:
> After building a kernel with X86_CHECK_BIOS_CORRUPTION enabled, I set it to scan (almost) as
> advised. No corruption of the low memory was reported after running some hours either with or
> without usbhid loaded.

And did you plug in a new HID device?

> (Booting with memory_corruption_check_size=640K caused an immediate kernel panic -- early exception
> 08 --though. Changing it to 620k allowed the boot to continue normally.)
>
> I took the opportunity to include kmemleak in the new kernel as well. After some uptime, one orphan
> object was always found, but it happened either with or without usbhid ever having been loaded. To
> judge from the traceback it was something ACPI-related anyway.
>
> So, basically, no progress.

Can you test Linux 3.4, available from the experimental suite? If that
still has the problem, we can pass this on to the upstream developers;
if not, we can try to work out where it was fixed.

Ben.

--
Ben Hutchings
When in doubt, use brute force. - Ken Thompson
 

Thread Tools




All times are GMT. The time now is 07:43 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org