All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Andi Kleen <ak@suse.de>, Greg KH <greg@kroah.com>,
	"Randy.Dunlap" <rdunlap@xenotime.net>,
	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: Thu, 9 Feb 2006 15:57:54 -0500	[thread overview]
Message-ID: <20060209205754.GD9576@redhat.com> (raw)
In-Reply-To: <20060209204940.GC9576@redhat.com>

On Thu, Feb 09, 2006 at 03:49:40PM -0500, Dave Jones wrote:
 > On Wed, Feb 08, 2006 at 08:55:05AM +0100, Andi Kleen wrote:
 >  > >  > Workaround is pci=nommconf btw
 >  > > I'm puzzled.  I'm still seeing this crash with latest -git which
 >  > > has this patch (I just double checked the source I built).
 >  > 
 >  > That's surprising. Can you addr2line the exactly address it's crashing on?
 > 
 > Still there in todays git snapshot.
 > http://people.redhat.com/davej/dsc00150.jpg is the top of the oops.

Actually I think this is pilot error.  I've been running a mispatched tree.

		Dave


  reply	other threads:[~2006-02-09 20:58 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
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 [this message]
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=20060209205754.GD9576@redhat.com \
    --to=davej@redhat.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ndbecker2@gmail.com \
    --cc=rdunlap@xenotime.net \
    /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.