On Tue, Feb 07, 2006 at 03:35:31PM -0800, Randy.Dunlap wrote:
> On Tue, 7 Feb 2006, Dave Jones wrote:
>
> > On Tue, Feb 07, 2006 at 03:18:35PM -0800, Greg Kroah-Hartman wrote:
> > > On Tue, Feb 07, 2006 at 02:59:13PM -0800, Andrew Morton wrote:
> > > > Neal Becker <[email protected]> wrote:
> > > > >
> > > > > Sorry, I meant 2.6.16-rc1 (not 2.6.12)
> > > > >
> > > > > Neal Becker wrote:
> > > > >
> > > > > > HP dv8000 notebook
> > > > > > 2.6.15 is fine, but 2.6.12-rc1 panics immediately on startup
> > > > > >
> > > > > > Here is a picture of some traceback
> > > > > > https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=124152&action=view
> > > > >
> > > > >
> > > >
> > > > It died in pci_mmcfg_read(). Greg, didn't a crash in there get fixed recently?
> > >
> > > Yes. Can you try 2.6.16-rc2? Is this a x86-64 machine?
> >
> > I can hit this on my dv8000 too. It's still there in 2.6.12-rc2-git3
> > I'm building a kernel with Randy's 'pause after printk' patch right now
> > to catch the top of the oops. It's enormous. Even with a 50 line display,
> > and x86-64s dual-line backtrace, it scrolls off the top.
>
> Just be patient. A boot can take a few minutes... ;)
It doesn't get that far. What did bugger things up though was the NMI watchdog
kicking in. I've thrown a touch_nmi_watchdog in the delay, and kicked off another build
hoping for a cleaner dump.
In the meantime, here's what I got..
http://people.redhat.com/davej/DSC00148.JPG
Dave
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]