linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Brian King <brking@linux.vnet.ibm.com>
Cc: ppc-dev <linuxppc-dev@ozlabs.org>,
	Wayne Boyer <wayneb@linux.vnet.ibm.com>,
	linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: ipr boot failure caused by MSI (2.6.30-rc1+)
Date: Thu, 21 May 2009 14:51:55 -0500	[thread overview]
Message-ID: <1242935515.3007.10.camel@localhost.localdomain> (raw)
In-Reply-To: <4A15A1B2.8060609@linux.vnet.ibm.com>

On Thu, 2009-05-21 at 13:47 -0500, Brian King wrote:
> cc'ing linuxppc-dev...
> 
> -Brian
> 
> 
> James Bottomley wrote:
> > Kernels after 2.6.30-rc1 stopped booting on my powerstation.  The ipr
> > just times out and refuses to probe devices.  If I let it drop into the
> > initramfs system, this is what the interrupts shows:
> > 
> > (initramfs) cat /proc/interrupts 
> >            CPU0       CPU1       CPU2       CPU3       
> >  16:         20         10         13         11   MPIC      Level     pata_amd
> >  20:          0          0          0          0   MPIC      Level     ohci_hcd:usb1, ohci_hcd:usb2
> >  21:          0          0          0          0  MPIC-U3MSI Edge      ipr
> >  68:         37         37         48         37   MPIC      Edge      serial
> > 251:         10         71         69         72   MPIC      Edge      ipi call function
> > 252:       1555       1779       1372       1155   MPIC      Edge      ipi reschedule
> > 253:          0          0          0          0   MPIC      Edge      ipi call function single
> > 254:          0          0          0          0   MPIC      Edge      ipi debugger
> > BAD:        416
> > 
> > So you see the IPR is the only device not receiving them.
> > 
> > I can fix the boot hang by reverting
> > 
> > commit 5a9ef25b14d39b8413364df12cb8d9bb7a673a32
> > Author: Wayne Boyer <wayneb@linux.vnet.ibm.com>
> > Date:   Fri Jan 23 09:17:35 2009 -0800
> > 
> >     [SCSI] ipr: add MSI support
> > 
> > The system in question is:
> > 
> > SYSTEM INFORMATION
> >  Processor  = PowerPC,970MP @ 2500 MHz
> >  I/O Bridge = U4 (4.4)
> >  SMP Size   = 4 (#0 #1 #2 #3)
> >  Boot-Date  = 2009-04-21 17:13:36
> >  Memory     = 2 GB of RAM @ 666 MHz
> >  Board Type = Bimini (7047191/0000000/1)
> >  MFG Date   = 1608
> >  Part No.   = 10N8748     
> >  FRU No.    = 10N7182     
> >  FRU Serial = YL30W8106038
> >  UUID       = 00000000000000000000000000000000
> >  Flashside  = 1 (temporary)
> >  Version    = HEAD
> >  Build Date = 12-04-2008 16:13

OK, so as an update, I booted to the initrd and inserted the network
modules, which are also MSI enabled and this is what I get:

(initramfs) cat /proc/interrupts 
           CPU0       CPU1       CPU2       CPU3       
 16:         14         11         11         18   MPIC      Level     pata_amd
 20:          0          0          0          0   MPIC      Level     ohci_hcd:usb1, ohci_hcd:usb2
 21:          0          0          0          0  MPIC-U3MSI Edge      ipr
 22:          1          0          1          0  MPIC-U3MSI Edge      eth0
 23:          0          2          1          0  MPIC-U3MSI Edge      eth1
 68:        193        166        113        177   MPIC      Edge      serial
251:         16         65         71         70   MPIC      Edge      ipi call function
252:       1574       1804       1346       1289   MPIC      Edge      ipi reschedule
253:          0          0          0          0   MPIC      Edge      ipi call function single
254:          0          0          0          0   MPIC      Edge      ipi debugger
BAD:       1866

So clearly the MSI interrupts to the network cards are working and it
looks like just a local problem with the ipr rather than a platform
problem with MSI.

James

  reply	other threads:[~2009-05-21 20:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1242926159.3007.5.camel@localhost.localdomain>
2009-05-21 18:47 ` ipr boot failure caused by MSI (2.6.30-rc1+) Brian King
2009-05-21 19:51   ` James Bottomley [this message]
2009-05-22 16:23     ` James Bottomley
2009-05-29 22:01       ` Brian King
2009-06-11  3:23         ` Wayne Boyer

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=1242935515.3007.10.camel@localhost.localdomain \
    --to=james.bottomley@hansenpartnership.com \
    --cc=brking@linux.vnet.ibm.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=wayneb@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).