From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Wayne Boyer <wayneb@linux.vnet.ibm.com>, Brian King <bjking1@us.ibm.com>
Cc: linux-scsi <linux-scsi@vger.kernel.org>
Subject: ipr boot failure caused by MSI (2.6.30-rc1+)
Date: Thu, 21 May 2009 12:15:59 -0500 [thread overview]
Message-ID: <1242926159.3007.5.camel@localhost.localdomain> (raw)
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
James
next reply other threads:[~2009-05-21 17:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-21 17:15 James Bottomley [this message]
2009-05-21 17:23 ` ipr boot failure caused by MSI (2.6.30-rc1+) James Bottomley
2009-05-21 18:47 ` Brian King
2009-05-21 19:51 ` James Bottomley
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=1242926159.3007.5.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=bjking1@us.ibm.com \
--cc=linux-scsi@vger.kernel.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