linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nick Piggin <npiggin@suse.de>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: Sachin Sant <sachinp@in.ibm.com>,
	Pekka Enberg <penberg@cs.helsinki.fi>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, linux-s390@vger.kernel.org
Subject: Re: Next June 29: Boot failure with SLQB on s390
Date: Mon, 29 Jun 2009 12:39:43 +0200	[thread overview]
Message-ID: <20090629103943.GA31299@wotan.suse.de> (raw)
In-Reply-To: <20090629103123.GC9321@osiris.boeblingen.de.ibm.com>

On Mon, Jun 29, 2009 at 12:31:23PM +0200, Heiko Carstens wrote:
> On Mon, Jun 29, 2009 at 03:14:40PM +0530, Sachin Sant wrote:
> > I still have problems booting next with SLQB on a s390 box.
> >
> > Write protected kernel read-only data: 0x12000 - 0x446fff
> > Experimental hierarchical RCU implementation.
> > Experimental hierarchical RCU init done.
> > console ÝttyS0¨ enabled
> > Unable to handle kernel pointer dereference at virtual kernel address (null)

This could I suppose be due to failed allocation where the caller
isn't expecting failure (or using SLAB_PANIC).

Did you manage to test with the prink debugging patch for SLQB that
I sent for the power6 boot failure? I don't think I saw a reply from
you but maybe I missed it?

Thanks,
Nick

  reply	other threads:[~2009-06-29 10:39 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-29  6:48 linux-next: Tree for June 29 Stephen Rothwell
2009-06-29  9:44 ` Next June 29: Boot failure with SLQB on s390 Sachin Sant
2009-06-29 10:31   ` Heiko Carstens
2009-06-29 10:39     ` Nick Piggin [this message]
2009-06-29 11:50       ` Heiko Carstens
2009-06-29 11:58         ` Nick Piggin
2009-06-29 13:09           ` Heiko Carstens
2009-06-29 14:12           ` Heiko Carstens
2009-06-30  7:34             ` Nick Piggin
2009-06-30  9:06             ` Nick Piggin
2009-06-30  9:20               ` Pekka Enberg
2009-06-30  9:27                 ` Nick Piggin
2009-06-30  9:30                   ` Pekka Enberg
2009-06-30 10:09               ` Heiko Carstens
2009-06-30 10:29                 ` Nick Piggin
2009-06-30 10:57                   ` Pekka Enberg
2009-06-30  5:33       ` Sachin Sant
2009-06-30  8:34         ` Nick Piggin
2009-06-30 10:56           ` Sachin Sant

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=20090629103943.GA31299@wotan.suse.de \
    --to=npiggin@suse.de \
    --cc=heiko.carstens@de.ibm.com \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=penberg@cs.helsinki.fi \
    --cc=sachinp@in.ibm.com \
    --cc=sfr@canb.auug.org.au \
    /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;
as well as URLs for NNTP newsgroup(s).