linux-kernel - Re: WARNING at libata-core.c:5015 in 2.6.39-rc3-wl+, then lockup. (bisected)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4DA88707.4060704@garzik.org>
Date:	Fri, 15 Apr 2011 13:57:27 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	Ben Greear <greearb@...delatech.com>
CC:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Tejun Heo <tj@...nel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linux IDE mailing list <linux-ide@...r.kernel.org>
Subject: Re: WARNING at libata-core.c:5015 in 2.6.39-rc3-wl+, then lockup.
 (bisected)

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


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/