public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jack Steiner <steiner@sgi.com>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Cc: "Siddha, Suresh B" <suresh.b.siddha@intel.com>,
	"mingo@elte.hu" <mingo@elte.hu>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Panic in reserve_memtype()
Date: Wed, 24 Feb 2010 15:37:29 -0600	[thread overview]
Message-ID: <20100224213729.GA15936@sgi.com> (raw)
In-Reply-To: <1267045764.16916.920.camel@localhost.localdomain>

On Wed, Feb 24, 2010 at 01:09:24PM -0800, Pallipadi, Venkatesh wrote:
> 
> On Wed, 2010-02-24 at 12:22 -0800, Jack Steiner wrote:
> > We see an X86_64 regression that started a few days ago. The kernel is booted
> > via EFI & panics in the pat.c code trying to deref a NULL pointer.
> > 
> > I didn't debug the problem but am suspicious of
> > 	x86, pat: Migrate to rbtree only backend for pat memtype management  x86/pat
> > 		author	Pallipadi, Venkatesh <venkatesh.pallipadi@intel.com>	
> > 		Wed, 10 Feb 2010 23:26:07 +0000 (15:26 -0800)
> > 	committer	H. Peter Anvin <hpa@zytor.com>	
> > 		Thu, 18 Feb 2010 23:41:36 +0000 (15:41 -0800)
> > 
> > 
> > 
> > Has anyone seen this? If not, I can debug further....
> > 
> 
> 
> Haven't seen this on my test systems here, but I haven't tested with EFI
> boot either.
> 
> I assume this is repeatable, and you always see this panic. I am looking
> at the code right now. Can you rollback this particular patch and see
> whether it goes away?

The problem is very repeatible.

FWIW, we have a nightly regression test that builds/tests the x86 tree
everynight at 1 AM. The failure started on the morning of Feb 22.

The build on Feb 21 (& all of Feb before then) passed w/o errors.
I can't rule out other errors but I don't see anything else that changed.

The linux-next tree appears to have the same problem.



--- jack

  reply	other threads:[~2010-02-24 21:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-24 20:22 Panic in reserve_memtype() Jack Steiner
2010-02-24 21:09 ` Pallipadi, Venkatesh
2010-02-24 21:37   ` Jack Steiner [this message]
2010-02-24 21:43     ` Pallipadi, Venkatesh
2010-02-24 22:05       ` Jack Steiner
2010-03-01 15:11         ` Jack Steiner
2010-03-01 17:55           ` Pallipadi, Venkatesh
2010-03-01 23:21       ` [tip:x86/pat] x86, pat: In rbt_memtype_check_insert(), update new->type only if valid tip-bot for Pallipadi, Venkatesh

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=20100224213729.GA15936@sgi.com \
    --to=steiner@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=suresh.b.siddha@intel.com \
    --cc=tglx@linutronix.de \
    --cc=venkatesh.pallipadi@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox