From: Dave Jones <davej@redhat.com>
To: Greg KH <greg@kroah.com>
Cc: Andrew Morton <akpm@osdl.org>, Neal Becker <ndbecker2@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.16-rc1 panic on startup (acpi)
Date: Tue, 7 Feb 2006 18:30:59 -0500 [thread overview]
Message-ID: <20060207233059.GA17665@redhat.com> (raw)
In-Reply-To: <20060207231835.GA19648@kroah.com>
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 <ndbecker2@gmail.com> 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.
Dave
next prev parent reply other threads:[~2006-02-07 23:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-06 11:46 2.6.12-rc1 panic on startup (acpi_ Neal Becker
2006-02-06 12:22 ` 2.6.16-rc1 panic on startup (acpi) Neal Becker
2006-02-07 22:59 ` Andrew Morton
2006-02-07 23:18 ` Greg KH
2006-02-07 23:30 ` Dave Jones [this message]
2006-02-07 23:35 ` Randy.Dunlap
2006-02-07 23:40 ` Dave Jones
2006-02-08 0:07 ` Greg KH
2006-02-08 0:10 ` Andi Kleen
2006-02-08 1:25 ` Neal Becker
2006-02-08 3:03 ` Dave Jones
2006-02-08 7:55 ` Andi Kleen
2006-02-09 20:49 ` Dave Jones
2006-02-09 20:57 ` Dave Jones
2006-02-07 23:32 ` Neal Becker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060207233059.GA17665@redhat.com \
--to=davej@redhat.com \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ndbecker2@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.