From: kurk <kurk@shiftmail.org>
To: "Prakash, Sathya" <sathya.prakash@lsi.com>,
James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Bjorn Helgaas <bjorn.helgaas@hp.com>,
"Support, Software" <support@lsi.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"bugme-daemon@bugzilla.kernel.org"
<bugme-daemon@bugzilla.kernel.org>,
"Moore, Eric" <Eric.Moore@lsi.com>
Subject: Re: [Bugme-new] [Bug 11045] New: Bug in MPT Fusion 2.6.26-rc7 unbootable
Date: Thu, 10 Jul 2008 16:24:41 +0200 [thread overview]
Message-ID: <48761BA9.9020704@shiftmail.org> (raw)
In-Reply-To: <20080709080814.GA801@lsil.com>
Hi all,
Good news! James and Sathya were correct, the bug is related to MSI:
specifying mpt_msi_enable=0 as option for the mptbase module solves the
problem and the system can boot as usual.
Having said this, do you still want me to try a patch, or perform some
additional test?
Just out of curiosity: do you intend to eventually modify the kernel so
to "support" and work around buggy hardware like the one we have (IBM
xSeries 335), so that Linux can work out of the box even on this hardware?
Thank everybody for your help
next prev parent reply other threads:[~2008-07-10 14:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-11045-10286@http.bugzilla.kernel.org/>
2008-07-06 19:34 ` [Bugme-new] [Bug 11045] New: Bug in MPT Fusion 2.6.26-rc7 unbootable Andrew Morton
[not found] ` <C5679C710E19AF4C8D9C02FF5C72E3C133C9C76A@cosmail01.lsi.com>
2008-07-08 8:57 ` Andrew Morton
2008-07-08 14:08 ` James Bottomley
2008-07-08 16:51 ` Bjorn Helgaas
2008-07-08 17:23 ` James Bottomley
2008-07-08 20:56 ` Bjorn Helgaas
2008-07-08 21:47 ` Andrew Morton
2008-07-08 21:57 ` James Bottomley
2008-07-09 8:08 ` Prakash, Sathya
2008-07-10 14:24 ` kurk [this message]
2008-07-10 14:52 ` kurk
2008-07-10 23:44 ` Andrew Morton
2008-07-11 0:42 ` James Bottomley
2008-07-11 4:33 ` Prakash, Sathya
2008-07-11 14:05 ` James Bottomley
2008-07-10 14:24 ` kurk
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=48761BA9.9020704@shiftmail.org \
--to=kurk@shiftmail.org \
--cc=Eric.Moore@lsi.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=bjorn.helgaas@hp.com \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=sathya.prakash@lsi.com \
--cc=support@lsi.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).