From: arno@natisbad.org (Arnaud Ebalard)
To: "Marc (Marc-Angelo) Carino" <mcarino@broadcom.com>
Cc: Robert Hancock <hancockrwd@gmail.com>,
Marc Carino <marc.ceeeee@gmail.com>, Tejun Heo <tj@kernel.org>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
Andrew Lunn <andrew@lunn.ch>,
Ezequiel Garcia <ezequiel.garcia@free-electrons.com>,
Jason Gunthorpe <jgunthorpe@obsidianresearch.com>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Gregory Clement <gregory.clement@free-electrons.com>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
willy tarreau <w@1wt.eu>, Jason Cooper <jason@lakedaemon.net>
Subject: Re: [BUG,REGRESSION] SATA regression on 12.0-rc4 kernel
Date: Wed, 09 Oct 2013 20:56:39 +0200 [thread overview]
Message-ID: <87a9iiuvbs.fsf@natisbad.org> (raw)
In-Reply-To: <202B57C13565C241A5ED05E38B705C82012397EC@IRVEXCHMB08.corp.ad.broadcom.com> (Marc Carino's message of "Wed, 9 Oct 2013 15:22:48 +0000")
Hi guys,
I went crazy on that one: I managed to reproduce the bug w/ another disk
(Seagate barracuda 7200.9). Then after a 'make clean' on the tree and a
compilation from ground of the stock 3.12-rc4, I never managed to
reproduce the error I had. I tested again with a WD30EFRX, the
WD2500AAJS and the Seagate barracuda 7200.9, all the three in two
different instances of the NAS: the error is gone.
The only logical conclusion is that it was due to some missing 'make
clean' on my tree.
I guess I owe you all some apologies for the noise.
Cheers,
a+
ps: and yes, I hate myself for having overwritten the erroneous image
WARNING: multiple messages have this Message-ID (diff)
From: arno@natisbad.org (Arnaud Ebalard)
To: linux-arm-kernel@lists.infradead.org
Subject: [BUG,REGRESSION] SATA regression on 12.0-rc4 kernel
Date: Wed, 09 Oct 2013 20:56:39 +0200 [thread overview]
Message-ID: <87a9iiuvbs.fsf@natisbad.org> (raw)
In-Reply-To: <202B57C13565C241A5ED05E38B705C82012397EC@IRVEXCHMB08.corp.ad.broadcom.com> (Marc Carino's message of "Wed, 9 Oct 2013 15:22:48 +0000")
Hi guys,
I went crazy on that one: I managed to reproduce the bug w/ another disk
(Seagate barracuda 7200.9). Then after a 'make clean' on the tree and a
compilation from ground of the stock 3.12-rc4, I never managed to
reproduce the error I had. I tested again with a WD30EFRX, the
WD2500AAJS and the Seagate barracuda 7200.9, all the three in two
different instances of the NAS: the error is gone.
The only logical conclusion is that it was due to some missing 'make
clean' on my tree.
I guess I owe you all some apologies for the noise.
Cheers,
a+
ps: and yes, I hate myself for having overwritten the erroneous image
next prev parent reply other threads:[~2013-10-09 18:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-06 21:38 [BUG,REGRESSION] ARM: mvebu: SATA regression w/ 12.0-rc4 kernel Arnaud Ebalard
2013-10-07 12:59 ` Jason Cooper
2013-10-07 19:12 ` [BUG,REGRESSION] SATA regression on " Arnaud Ebalard
2013-10-08 2:38 ` Robert Hancock
2013-10-08 2:38 ` Robert Hancock
2013-10-08 6:10 ` Arnaud Ebalard
2013-10-08 6:10 ` Arnaud Ebalard
2013-10-09 5:50 ` Robert Hancock
2013-10-09 5:50 ` Robert Hancock
2013-10-09 8:40 ` Arnaud Ebalard
2013-10-09 8:40 ` Arnaud Ebalard
2013-10-09 15:22 ` Marc (Marc-Angelo) Carino
2013-10-09 15:22 ` Marc (Marc-Angelo) Carino
2013-10-09 18:56 ` Arnaud Ebalard [this message]
2013-10-09 18:56 ` Arnaud Ebalard
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=87a9iiuvbs.fsf@natisbad.org \
--to=arno@natisbad.org \
--cc=andrew@lunn.ch \
--cc=ezequiel.garcia@free-electrons.com \
--cc=gregory.clement@free-electrons.com \
--cc=hancockrwd@gmail.com \
--cc=jason@lakedaemon.net \
--cc=jgunthorpe@obsidianresearch.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-ide@vger.kernel.org \
--cc=marc.ceeeee@gmail.com \
--cc=mcarino@broadcom.com \
--cc=sebastian.hesselbarth@gmail.com \
--cc=thomas.petazzoni@free-electrons.com \
--cc=tj@kernel.org \
--cc=w@1wt.eu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.