Bug 14347 - Boot failure (as shown in attachment)
Summary: Boot failure (as shown in attachment)
Status: CLOSED OBSOLETE
Alias: None
Product: Memory Management
Classification: Unclassified
Component: Slab Allocator (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: Andrew Morton
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-08 15:41 UTC by Aioanei Rares
Modified: 2012-06-13 19:34 UTC (History)
2 users (show)

See Also:
Kernel Version: 2.6.32-rc3-linux-next-20091008
Subsystem:
Regression: No
Bisected commit-id:


Attachments
The only messages I got to see on screen before the lockup. (670.42 KB, image/jpeg)
2009-10-08 15:45 UTC, Aioanei Rares
Details
dmesg_2010-03-30 (68.04 KB, application/octet-stream)
2010-04-11 22:12 UTC, Denis Laxalde
Details
dmesg_2010-04-06 (72.49 KB, application/octet-stream)
2010-04-11 22:16 UTC, Denis Laxalde
Details

Description Aioanei Rares 2009-10-08 15:41:55 UTC
I compiled the kernel first with the standard Debian .config debug options, then with LOTS of debug options, but it won't help. The computer gets a hard lock and I have to reboot it. See attachment below.
Comment 1 Aioanei Rares 2009-10-08 15:45:48 UTC
Created attachment 23309 [details]
The only messages I got to see on screen before the lockup.
Comment 2 Denis Laxalde 2010-04-11 22:08:25 UTC
I think I'm experiencing a similar issue with 2.6.32-10 from Debian. This happens sporadically.
See the Debian bug report for additional information.
    http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=575924
Comment 3 Denis Laxalde 2010-04-11 22:12:47 UTC
Created attachment 25963 [details]
dmesg_2010-03-30

a dmesg from bad boot
Comment 4 Denis Laxalde 2010-04-11 22:16:57 UTC
Created attachment 25964 [details]
dmesg_2010-04-06

another one (just in case)

Note You need to log in before you can comment on or make changes to this bug.