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] [day] [month] [year] [list]

Message-ID: <4DB08623.9010905@candelatech.com>
Date:	Thu, 21 Apr 2011 12:31:47 -0700
From:	Ben Greear <greearb@...delatech.com>
To:	Tejun Heo <tj@...nel.org>
CC:	Jeff Garzik <jeff@...zik.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.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/21/2011 06:25 AM, Tejun Heo wrote:
> Hello,
>
> On Wed, Apr 20, 2011 at 07:03:18PM -0700, Ben Greear wrote:
>> I tried today's kernel (39-rc4+) and it seems much more stable on my
>> system.  So, I think the problem must be fixed.  It appears it was not
>> fixed in the plain 39-rc4, for what that's worth.
>
> Hmmm... interesting.  I don't know of any changes which could have
> affected that but then again I've been half offline for the last three
> weeks.  Can you please try to boot earlier kernel and determine
> whether the kernel version difference is actually making the
> difference?

I tried the 39-rc4-wl (wireless-testing) kernel that was based off of
39-rc4, and I see hard-drive read errors there, and eventually
crashes.  I didn't try Linus's 39-rc4.

Yesterday's rc4+ kernel ran fine overnight.

I had previously bisected this to a merge in post 2.6.38 code, but
I never found time to figure out what part of the merge was
funky.  In general, from 2.6.38 to very recently, the kernels
have been very unstable on my systems, with multiple networking
crashes and this block level and/or hard-drive stuff causing
trouble, so it's hard to tell exactly when certain bugs
were introduced.

2.6.38 has been stable, as has 2.6.38-wl.

If there is some other specific commit you'd like me to test
I can do so.

Thanks,
Ben

-- 
Ben Greear <greearb@...delatech.com>
Candela Technologies Inc  http://www.candelatech.com

--
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/