--- On Tue, 27/12/11, Ben Hutchings <b...@decadent.org.uk> wrote: > From: Ben Hutchings <b...@decadent.org.uk> > Subject: Re: Bug#653331: linux-image-3.1.0-1-686-pae: CPU#0 stuck for 23s, > system does not boot > To: "P. van Gaans" <mailme...@yahoo.co.uk>, 653...@bugs.debian.org > Date: Tuesday, 27 December, 2011, 7:02 > On Tue, 2011-12-27 at 03:16 +0100, P. > van Gaans wrote: > > Package: linux-2.6 > > Version: 3.1.1-1 > > Please try the current version in testing, 3.1.5-1.
I already ran apt-get update && apt-get upgrade, I am running the newest version available. I admit I too wondered why reportbug told me there was a newer version and apt-get disagrees. > > > Severity: critical > > Justification: breaks the whole system > > > > Dear Maintainer, > > > > First of all, thanks for looking into this.. > > > > I've installed debian-stable with 2.6.32 kernel. > > After that, I made the upgrade to wheezy. From that > moment on, > > the system no longer boots: http://tinypic.com/r/2u9222q/5 > > "BUG: soft lockup - CPU#0 stuck for 23s! [swapper:1]" > > This messages keeps repeating. > [...] > > And there is also the message 'INFO: rcu_sched_state > detected stall on > CPU 0 ...' which is an important clue. > > Assuming that this isn't fixed by the later version, can > you boot > without the 'quiet' kernel parameter (e.g. by selecting > 'recovery mode' > in GRUB) and report the last messages that appear before > these errors? I think I have it: http://tinypic.com/r/2ni9xu1/5 http://tinypic.com/r/166wrxk/5 I used boot_delay=100 so I could photograph it. Something that caught my eye at around 18 seconds, but passed to quick to make a picture (even at boot_delay=1000) was "weird, boot CPU (#0) not listed by BIOS" (iirc). I don't know if it's related. P. van Gaans -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
