linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nick Piggin <npiggin@suse.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Matthew Wilcox <matthew@wil.cx>, Sachin Sant <sachinp@in.ibm.com>,
	linux-next@vger.kernel.org,
	linux-scsi <linux-scsi@vger.kernel.org>,
	linuxppc-dev@ozlabs.org, Pekka Enberg <penberg@cs.helsinki.fi>
Subject: Re: Next May 11 : BUG during scsi initialization
Date: Tue, 12 May 2009 07:59:18 +0200	[thread overview]
Message-ID: <20090512055918.GF32535@wotan.suse.de> (raw)
In-Reply-To: <20090512155613.881fa2ec.sfr@canb.auug.org.au>

On Tue, May 12, 2009 at 03:56:13PM +1000, Stephen Rothwell wrote:
> Hi Nick,
> 
> On Tue, 12 May 2009 06:57:16 +0200 Nick Piggin <npiggin@suse.de> wrote:
> >
> > Hmm, I think (hope) your problems were fixed with the recent memory
> > coruption bug fix for SLQB. (if not, let me know)
> > 
> > This one possibly looks like a problem with remote memory allocation
> > or memory hotplug or something like that. I'll do a bit of code
> > review....
> 
> These are -next kernels which include the two fixes you posted recently
> (I am pretty sure).

Yes they should do.


>  I am also getting the network failures that Sachin
> is seeing on several of my machines here.  The previously reported
> problems have gone away.

This one is a SCSI failure... was there also a network one reported?
At any rate, I'm fairly sure this is a problem with SLQB, so it could
easily happen in any early driver setup.

  reply	other threads:[~2009-05-12  5:59 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-11  6:14 linux-next: Tree for May 11 Stephen Rothwell
2009-05-11 11:46 ` Next May 11 : BUG during scsi initialization Sachin Sant
2009-05-11 11:52   ` Matthew Wilcox
2009-05-11 12:04     ` Sachin Sant
2009-05-11 12:21       ` Matthew Wilcox
2009-05-11 16:19         ` Sachin Sant
2009-05-11 16:25           ` Matthew Wilcox
2009-05-11 16:59             ` Sachin Sant
2009-05-12  4:57         ` Nick Piggin
2009-05-12  5:56           ` Stephen Rothwell
2009-05-12  5:59             ` Nick Piggin [this message]
2009-05-12  6:03               ` Stephen Rothwell
2009-05-12  6:52                 ` Stephen Rothwell
2009-05-12  6:56                   ` Nick Piggin
2009-05-14  8:30           ` Sachin Sant
2009-05-14  8:51             ` Pekka Enberg
2009-05-14  9:54               ` Sachin Sant
2009-05-14  9:59                 ` Pekka Enberg
2009-05-14 10:01                   ` Pekka Enberg
2009-05-14 11:46                     ` Sachin Sant
2009-06-05 12:04   ` [Powerpc/SLQB] Next June 06 " Sachin Sant
2009-06-07  8:06     ` Pekka J Enberg
2009-06-08 12:12       ` Sachin Sant
2009-06-09 14:19         ` Nick Piggin
2009-06-12  5:44           ` Sachin Sant
2009-06-12  7:42             ` Nick Piggin
2009-06-12  8:08               ` Sachin Sant
2009-06-12  8:21                 ` Nick Piggin
2009-06-12  8:25                   ` Pekka Enberg
2009-06-12  8:35                     ` Stephen Rothwell
2009-06-12  8:38                       ` Pekka Enberg
2009-05-11 16:32 ` [PATCH -next] kvm: fix build error: add missing semi-colon Randy Dunlap
2009-05-12  8:31   ` Avi Kivity
2009-05-11 16:36 ` [PATCH -next] soc_camera: depends on I2C Randy Dunlap
2009-05-11 17:53   ` Guennadi Liakhovetski
2009-05-11 16:37 ` [PATCH -next] v4l2: handle unregister for non-I2C builds Randy Dunlap
2009-05-22  5:48   ` Paul Mundt
2009-05-22  7:55     ` Stephen Rothwell
2009-05-22 15:57       ` Randy Dunlap
2009-05-26 17:31       ` Mauro Carvalho Chehab

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=20090512055918.GF32535@wotan.suse.de \
    --to=npiggin@suse.de \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=matthew@wil.cx \
    --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).