From: Jeff Garzik <jeff@garzik.org>
To: Ben Greear <greearb@candelatech.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Tejun Heo <tj@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux IDE mailing list <linux-ide@vger.kernel.org>
Subject: Re: WARNING at libata-core.c:5015 in 2.6.39-rc3-wl+, then lockup. (bisected)
Date: Fri, 15 Apr 2011 13:57:27 -0400 [thread overview]
Message-ID: <4DA88707.4060704@garzik.org> (raw)
In-Reply-To: <4DA87A72.50809@candelatech.com>
On 04/15/2011 01:03 PM, Ben Greear wrote:
> Ok, it took a while, but I think I have this thing somewhat bisected.
>
> Starting at commit 4cc4d24efce4672f9b0e7fa27963770ae602998f, I see
> hard-drive
> issues. Commits right before this (in git bisect) crash in the
> networking code
> quite often, but the hard-drive logic seems to work at least.
>
> In later builds (ie, -rc3), the crashes and warnings are different, but
> they have something to do with the file system. It's difficult to bisect
> it any better because of all the instability...
>
>
> Here are some console logs from a
> 4cc4d24efce4672f9b0e7fa27963770ae602998f boot:
(linux-ide added to CC)
hmmm... that's a merge commit. Any chance you could mark an individual
commit bad, to narrow things down a bit more? Run "git help bisect" and
check out helpful sections "Avoiding testing a commit" and "Bisect skip".
Jeff
next prev parent reply other threads:[~2011-04-15 17:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-13 16:29 WARNING at libata-core.c:5015 in 2.6.39-rc3-wl+, then lockup Ben Greear
2011-04-13 16:56 ` Ben Greear
2011-04-13 19:04 ` Ben Greear
2011-04-15 17:03 ` WARNING at libata-core.c:5015 in 2.6.39-rc3-wl+, then lockup. (bisected) Ben Greear
2011-04-15 17:57 ` Jeff Garzik [this message]
2011-04-15 18:05 ` Ben Greear
2011-04-21 2:03 ` Ben Greear
2011-04-21 13:25 ` Tejun Heo
2011-04-21 19:31 ` Ben Greear
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=4DA88707.4060704@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@linux-foundation.org \
--cc=greearb@candelatech.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@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
Powered by JetHome