From: Paul Johnson <pjay@nwtrail.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Yinghai Lu <yinghai@kernel.org>, linux-pci <linux-pci@vger.kernel.org>
Subject: Re: [problem] mpt2sas load fails with LSISAS2008
Date: Wed, 11 Feb 2015 08:11:37 -0800 [thread overview]
Message-ID: <54DB7F39.8030306@nwtrail.com> (raw)
In-Reply-To: <CAErSpo4ZYfs9EhdZMXGdjbDY4WUfTNFz+CPBq-Gx3eQ563Fogw@mail.gmail.com>
On 02/10/2015 08:49 AM, Bjorn Helgaas wrote:
> We need to work out what's going wrong here before we rush into a band-aid.
>
> What changed between v3.4 and v3.4.1 that exposed this problem? "git
> log --oneline v3.4..v3.4.1" doesn't show any likely culprits. Paul,
> are those the versions you tested? Your dmesg logs at
> https://bugzilla.kernel.org/show_bug.cgi?id=92351 show
> "3.4.0-030400-generic" and "3.4.1-030401-generic" but I don't know
> whether those are precisely v3.4 and v3.4.1.
>
> I assume this system works fine with Windows, and I doubt Windows has
> a hack like "never move LSI devices." So it would be useful to know
> if we're doing something stupid in Linux that makes us trip over this.
> Paul, if you happen to have Windows on this machine as well, a
> complete AIDA64 report (free trial version at http://www.aida64.com)
> would show what Windows did.
>
> The resource allocation we're doing is related SR-IOV, and
> unfortunately we don't print enough information in dmesg to figure
> everything out. Paul, can you attach the complete "lspci -vv" output
> to the bugzilla?
>
> Bjorn
>
The system I have had this problem on is in production, though it should
be replaced by a real server. Because it is in use, I have used a
separate boot disk to test kernels. I also have limited access to take
the machine down. The system runs ubuntu server, though I have used an
ubuntu desktop to test kernels. There is not a windows system on the
machine, though, just guessing, LSI likely provides the windows driver
and that driver may well have dealt with a problem that is looking to be
specific to a firmware/bios version on this card.
Someone found another of these cards here, so I tried it last night in
an unused machine. It worked on the ubuntu 3.13 kernel without realloc.
The card that has been the problem has these versions of firmware:
[ 9.004647] mpt2sas0: LSISAS2008: FWVersion(17.00.01.00),
ChipRevision(0x03), BiosVersion(07.33.00.00)
and the card that works has a newer version:
[ 15.725011] mpt2sas0: LSISAS2008: FWVersion(18.00.00.00),
ChipRevision(0x03), BiosVersion(07.35.00.00)
Now, the cards are in very different machines so the difference could be
due to the machines and not the firmware, but I would tend to go with
the firmware difference. LSI firmware is now beyond both these firmware
versions, but if I can find a copy of the older firmware, I'll try it on
the card with the newer firmware.
Just a suggestion, but from the linux end, if you could trap the older
firmware version and put a message out about the realloc flag and
firmware version, that would help someone else who might fall into the
same hole I found myself in.
Paul
next prev parent reply other threads:[~2015-02-11 16:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-27 23:12 [problem] mpt2sas load fails with LSISAS2008 Paul Johnson
2015-01-28 4:02 ` Bjorn Helgaas
2015-01-28 4:44 ` Yinghai Lu
2015-01-28 16:46 ` Bjorn Helgaas
2015-01-30 16:25 ` Paul Johnson
2015-01-30 21:37 ` Yinghai Lu
2015-02-02 18:03 ` Paul Johnson
2015-02-02 22:30 ` Yinghai Lu
2015-02-03 23:58 ` Paul Johnson
2015-02-07 23:34 ` Yinghai Lu
2015-02-08 2:15 ` Paul Johnson
2015-02-08 3:11 ` Yinghai Lu
2015-02-08 18:43 ` Paul Johnson
2015-02-10 16:49 ` Bjorn Helgaas
2015-02-11 16:11 ` Paul Johnson [this message]
2015-02-11 16:57 ` Bjorn Helgaas
2015-02-19 23:40 ` Paul Johnson
2015-02-26 0:28 ` Bjorn Helgaas
2015-02-26 6:02 ` Yinghai Lu
2015-02-26 15:59 ` Bjorn Helgaas
2015-02-26 18:08 ` Yinghai Lu
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=54DB7F39.8030306@nwtrail.com \
--to=pjay@nwtrail.com \
--cc=bhelgaas@google.com \
--cc=linux-pci@vger.kernel.org \
--cc=yinghai@kernel.org \
/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).