linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Tejun Heo <tj@kernel.org>
Cc: Jeff Garzik <jeff@garzik.org>,
	Linux Kernel Mailing List <linux-kernel@vger.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: Thu, 21 Apr 2011 12:31:47 -0700	[thread overview]
Message-ID: <4DB08623.9010905@candelatech.com> (raw)
In-Reply-To: <20110421132529.GC31724@htj.dyndns.org>

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@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


      reply	other threads:[~2011-04-21 19:32 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
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 [this message]

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=4DB08623.9010905@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=akpm@linux-foundation.org \
    --cc=jeff@garzik.org \
    --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;
as well as URLs for NNTP newsgroup(s).