Bug 17371
| Summary: | Total freeze at boot | ||
|---|---|---|---|
| Product: | Memory Management | Reporter: | Christian Casteyde (casteyde.christian) |
| Component: | Other | Assignee: | Andrew Morton (akpm) |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | ||
| Priority: | P1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Kernel Version: | 2.6.36-rc2 | Subsystem: | |
| Regression: | Yes | Bisected commit-id: | |
| Attachments: |
screenshot after the bug
first freeze second freeze |
||
Still present in 2.6.36-rc4 I've got two more screenshots (the end of the oops, before freeze) Created attachment 29882 [details]
first freeze
Created attachment 29892 [details]
second freeze
Maybe the same as https://bugzilla.kernel.org/show_bug.cgi?id=17361 At least I haven't seen these call stacks (with scsi...) with -rc5, so closing. 17361 is just enough. *** This bug has been marked as a duplicate of bug 17361 *** |
Created attachment 28371 [details] screenshot after the bug Kernel 2.6.36-rc3 Athlon 64X2 3GHz in 64 bits mode Slackware64 13.1 Since kernel 2.6.36-rc2 (and maybe -rc1), sometime the kernel freezes totally at boot. The kernel is compiled with kmemcheck, deadlock detection, etc. I've got a photo on -rc3, since I cannot save anything when that happens. Basically, its confusing, there is a warning, a: BUG: sleeping function called on invalid context at mm/mmap.c: 232 and a general protection fault, to terminate with a panic - exception in interrupt. The call stack doesn't appeared after the crash. I've appended the photo if it can help. This occurs roughly one boot every ten.