Re: 2.6.11-mm4 and 2.6.12-rc1-mm1

[Andrew Morton]

Borislav Petkov <petkov@xxxxxxxxxxxxxxx> wrote:
>
> On Thursday 17 March 2005 10:18, Andrew Morton wrote:
> > Borislav Petkov <petkov@xxxxxxxxxxxxxxx> wrote:
> > > Mar 17 09:19:28 zmei kernel: [    4.109241] PM: Checking swsusp image.
> > >  Mar 17 09:19:28 zmei kernel: [    4.109244] PM: Resume from disk failed.
> > >  Mar 17 09:19:28 zmei kernel: [    4.112220] VFS: Mounted root (ext2
> > > filesystem) readonly. Mar 17 09:19:28 zmei kernel: [    4.112465] Freeing
> > > unused kernel memory: 188k freed Mar 17 09:19:28 zmei kernel: [   
> > > 4.142002] logips2pp: Detected unknown logitech mouse model 1 Mar 17
> > > 09:19:28 zmei kernel: [    4.274620] input: PS/2 Logitech Mouse on
> > > isa0060/serio1 [EOF]
> > >  <-- and here it stops waiting forever. What actually has to come next is
> > > the init process, i.e. something of the likes of:
> > >  INIT version x.xx loading
> > >  but it doesn't. And by the way, how do you debug this? serial console?
> >
> > Serial console would be useful.  Do sysrq-P and sysrq-T provide any info?
> > -
> <snip>
> 
> Hi Andrew,
> 
> I've tried 2.6.12-rc1-mm1 today and it stops booting at the same point as 
> 2.6.11-mm4. What might help is the info that rc1 boots just fine so it is 
> something in the mm series that impedes the boot process. However, sysrq-P 
> and sysrq-T do not provide anything - sysrq doesn't show any activity at all, 
> i.e. it doesn't even print the usage info message. Infact, the keyboard is 
> dead, it doesn't even turn on or off any lights (NumLock etc).
> 
> Any ideas? (Additional printk's added manually, etc..)
> 

- Make sure that io-apic is enabled, boot with `nmi_watchdog=1'.

- Make sure that CONFIG_DETECT_SOFTLOCKUP is enabled

- Add `initcall_debug' to the boot command line, see if that tells us
  anything.

- Disable CONFIG_DEBUG_PAGEALLOC, if it was enabled

- Send me your .config.

kgdb is the way to diagnose this one.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/