From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Davidlohr Bueso <davidlohr@hp.com>
Cc: Baoquan He <bhe@redhat.com>,
linux-kernel@vger.kernel.org, scameron@beardog.cce.hp.com,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: hpsa driver bug crack kernel down!
Date: Wed, 09 Apr 2014 16:10:44 -0700 [thread overview]
Message-ID: <1397085044.9519.63.camel@dabdike> (raw)
In-Reply-To: <1397084904.9519.62.camel@dabdike>
On Wed, 2014-04-09 at 16:08 -0700, James Bottomley wrote:
> [+linux-scsi]
> On Wed, 2014-04-09 at 15:49 -0700, Davidlohr Bueso wrote:
> > On Wed, 2014-04-09 at 10:39 +0800, Baoquan He wrote:
> > > Hi,
> > >
> > > The kernel is 3.14.0+ which is pulled just now.
> >
> > Cc'ing more people.
> >
> > While the hpsa driver appears to be involved in some way, I'm sure if
> > this is a related issue, but as of today's pull I'm getting another
> > problem that causes my DL980 not to come up.
> >
> > *Massive* amounts of:
> >
> > DMAR:[fault reason 02] Present bit in context entry is clear
> > dmar: DRHD: handling fault status reg 602
> > dmar: DMAR:[DMA Read] Request device [02:00.0] fault addr 7f61e000
> >
> > Then:
> >
> > hpsa 0000:03:00.0: Controller lockup detected: 0xffff0000
> > ...
> > Workqueue: events hpsa_monitor_ctlr_worker [hpsa]
> > ...
> >
> > Screenshot of the actual LOCKUP:
> > http://stgolabs.net/hpsa-hard-lockup-3.14+.png
> >
> > While I haven't bisected, things worked fine until at least until commit
> > 39de65aa2c3e (April 2nd).
> >
> > Any ideas?
>
> Well, it's either a DMA remapping issue or a hpsa one. Your assertion
> that everything worked fine until 39de65aa2c3e would tend to vindicate
> hpsa, because all the hpsa changes went in before that under
Missing crucial info:
commit 1a0b6abaea78f73d9bc0a2f6df2d9e4c917cade1
> Merge: 3e75c6d b2bff6c
> Author: Linus Torvalds <torvalds@linux-foundation.org>
> Date: Tue Apr 1 18:49:04 2014 -0700
>
> Merge tag 'scsi-misc' of
> git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi
>
> can you revalidate that this commit works OK just to make sure?
>
> James
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-04-09 23:10 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-09 2:39 hpsa driver bug crack kernel down! Baoquan He
2014-04-09 22:49 ` Davidlohr Bueso
2014-04-09 23:08 ` James Bottomley
2014-04-09 23:10 ` James Bottomley [this message]
2014-04-09 23:40 ` Davidlohr Bueso
2014-04-09 23:50 ` James Bottomley
2014-04-10 0:19 ` Davidlohr Bueso
2014-04-10 4:03 ` Bjorn Helgaas
2014-04-10 6:32 ` Davidlohr Bueso
2014-04-10 7:15 ` Joerg Roedel
2014-04-10 8:46 ` Woodhouse, David
2014-04-10 15:14 ` Bjorn Helgaas
2014-04-10 15:34 ` Woodhouse, David
2014-04-10 15:36 ` Linda Knippers
2014-04-10 16:19 ` Davidlohr Bueso
2014-04-10 16:30 ` Woodhouse, David
2014-04-11 9:18 ` Woodhouse, David
2014-04-14 15:45 ` Davidlohr Bueso
2014-04-14 16:19 ` Jiang Liu
2014-04-14 16:44 ` Davidlohr Bueso
2014-04-14 16:47 ` Davidlohr Bueso
2014-04-14 17:03 ` Woodhouse, David
2014-04-16 13:37 ` joro
2014-04-16 13:58 ` Woodhouse, David
2014-04-16 14:13 ` joro
2014-04-14 7:01 ` Jiang Liu
2014-04-14 8:57 ` Jiang Liu
2014-04-14 18:08 ` Davidlohr Bueso
2014-04-10 20:45 ` scameron
2014-04-10 23:17 ` Shuah Khan
2014-04-11 8:57 ` David Woodhouse
2014-04-10 8:34 ` Jiang Liu
2014-04-10 15:54 ` Davidlohr Bueso
2014-04-10 16:02 ` Davidlohr Bueso
2014-04-11 1:34 ` Baoquan He
2014-04-11 3:14 ` Baoquan He
2014-04-10 15:43 ` Bjorn Helgaas
2014-04-10 16:02 ` Bjorn Helgaas
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=1397085044.9519.63.camel@dabdike \
--to=james.bottomley@hansenpartnership.com \
--cc=bhe@redhat.com \
--cc=davidlohr@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=scameron@beardog.cce.hp.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