From: Laurent CARON <lcaron@unix-scripts.info>
To: Borislav Petkov <bp@alien8.de>,
linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org,
Vinod Koul <vinod.koul@intel.com>, Dan Williams <djbw@fb.com>
Subject: Re: Strange crash on Dell R720xd
Date: Tue, 16 Oct 2012 14:52:25 +0200 [thread overview]
Message-ID: <20121016145039.eizeigon@trusted.unix-scripts.info> (raw)
In-Reply-To: <20121016124825.GA8509@x1.osrc.amd.com>
On Tue, Oct 16, 2012 at 02:48:25PM +0200, Borislav Petkov wrote:
> On Tue, Oct 16, 2012 at 11:26:01AM +0200, Laurent CARON wrote:
> > On Tue, Oct 16, 2012 at 11:03:53AM +0200, Borislav Petkov wrote:
> > > That's:
> > >
> > > BUG_ON(async_tx_test_ack(depend_tx) || txd_next(depend_tx) ||
> > > txd_parent(tx));
> > >
> > > but probably the b0rkage happens up the stack. And this __raid_run_ops
> > > is probably starting the whole TX so maybe we should add
> > > linux-raid@vger.kernel.org to CC. Added.
> >
> >
> > Hi,
> >
> > The machines seem stable after disabling I/O AT DMA at the BIOS level.
>
> That's a good point because the backtrace goes through I/O AT DMA so it
> could very well be the culprit. Let's add some more people to Cc.
>
> Vinod/Dan, here's the BUG_ON Laurent is hitting:
>
> http://marc.info/?l=linux-kernel&m=135033064724794&w=2
>
> and it has ioat2_tx_submit_unlock in the backtrace. Disabling ioat dma
> in the BIOS makes the issue disappear so ...
>
> > > What is that "r510" thing in the kernel version? You have your patches
> > > ontop? If yes, please try reproducing this with a kernel.org kernel
> > > without anything else ontop.
> >
> > My kernel is vanilla from Kernel.org. The -r510 string is because I
> > tried it on a -r510 also.
>
> Ok, good.
>
> > > Also, it might be worth trying plain 3.6 to rule out a regression
> > > introduced in the stable 3.6 series.
> >
> > I tried 3.5.x, 3.6, 3.6.1, 3.6.2 with exactly the same results.
> >
> > For now, I did create more volumes, rsync lors of data over the network
> > to the disks with no crashs (after disabling I/O AT DMA).
>
> And when you do this with ioat dma enabled, you get the bug, right? So
> it is reproducible...?
It is 100% reproductible. The only "nondeterministic" point is the time
it takes to have the machine crash.
next prev parent reply other threads:[~2012-10-16 12:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20121015213522.kaiyahro@trusted.unix-scripts.info>
2012-10-16 9:03 ` Strange crash on Dell R720xd Borislav Petkov
2012-10-16 9:26 ` Laurent CARON
2012-10-16 12:48 ` Borislav Petkov
2012-10-16 12:52 ` Laurent CARON [this message]
2012-10-16 17:58 ` Dan Williams
2012-10-17 7:31 ` Laurent CARON
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=20121016145039.eizeigon@trusted.unix-scripts.info \
--to=lcaron@unix-scripts.info \
--cc=bp@alien8.de \
--cc=djbw@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=vinod.koul@intel.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).