From: "George Spelvin" <linux@horizon.com>
To: James.Bottomley@HansenPartnership.com, linux@horizon.com
Cc: DL-MPTFusionLinux@lsi.com, kashyap.desai@lsi.com,
linux-scsi@vger.kernel.org, Nagalakshmi.Nandigama@lsi.com
Subject: Re: [mptscsih] Watchdog detected hard LOCKUP on cpu 0
Date: 28 Nov 2013 05:06:16 -0500 [thread overview]
Message-ID: <20131128100616.640.qmail@science.horizon.com> (raw)
In-Reply-To: <1385380914.2354.38.camel@dabdike>
> The reason for the lack of replies is that no-one has much of an idea.
> This really looks like a hardware problem. The qi_submit_sync() is
> suggestive: it's the intel IOMMU mapping call ... have you tried
> reproducing this with the iommu disabled?
I turned off VT-d, and the problem went away.
I turned on VT-d, and turned off all of the sub-options:
Interrupt remapping
Coherency
ATS support
Pass-through DMA
and the problem remained.
So them I did a hail mary, and upgraded my GA-X79-UP4 from the F2 BIOS
to the beta F5c BIOS.
VT-d and all of the sub-features are turned on, and I'm on my 6th full
read pass over the entire RAID array (when it would crash before 15%
before), with no problem.
Hardware problem, indeed.
Thanks for the pointer; I wouldn't have thought of trying a BIOS
upgrade without it.
prev parent reply other threads:[~2013-11-28 10:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-13 13:42 Hard lockup during intense reads from BR10i George Spelvin
2013-10-14 9:08 ` George Spelvin
2013-11-25 7:48 ` [mptscsih] Watchdog detected hard LOCKUP on cpu 0 George Spelvin
2013-11-25 12:01 ` James Bottomley
2013-11-25 17:16 ` George Spelvin
2013-11-28 10:06 ` George Spelvin [this message]
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=20131128100616.640.qmail@science.horizon.com \
--to=linux@horizon.com \
--cc=DL-MPTFusionLinux@lsi.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=Nagalakshmi.Nandigama@lsi.com \
--cc=kashyap.desai@lsi.com \
--cc=linux-scsi@vger.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).