From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Wayne Boyer <wayneb@linux.vnet.ibm.com>
Cc: Brian King <bjking1@us.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 12:23:03 -0500 [thread overview]
Message-ID: <1242926583.3007.7.camel@localhost.localdomain> (raw)
In-Reply-To: <1242926159.3007.5.camel@localhost.localdomain>
On Thu, 2009-05-21 at 12:15 -0500, James Bottomley wrote:
> 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
>
Just as a follow up, after reverting the above and booting successfully,
this is what /proc/interrupts now shows:
claymoor:~# cat /proc/interrupts
CPU0 CPU1 CPU2 CPU3
16: 31 24 35 19 MPIC Level pata_amd, serial
17: 374 421 434 381 MPIC Level ipr
20: 0 0 0 0 MPIC Level ohci_hcd:usb1, ohci_hcd:usb2
21: 135 140 152 146 MPIC-U3MSI Edge eth1
68: 59 66 60 57 MPIC Edge serial
251: 65 124 119 108 MPIC Edge ipi call function
252: 1018 1383 1127 746 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: 621
So MSI seems to be being used successfully on the ethernet controller,
pointing to an ipr specific problem.
James
next prev parent reply other threads:[~2009-05-21 17:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-21 17:15 ipr boot failure caused by MSI (2.6.30-rc1+) James Bottomley
2009-05-21 17:23 ` James Bottomley [this message]
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=1242926583.3007.7.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