All of lore.kernel.org
 help / color / mirror / Atom feed
From: Justin Madru <jdm64@gawab.com>
To: Tejun Heo <tj@kernel.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-ide@vger.kernel.org, "Rafael J. Wysocki" <rjw@sisk.pl>,
	Jeff Garzik <jeff@garzik.org>
Subject: Re: [2.6.28-rc] Sata soft reset filling log
Date: Sat, 27 Dec 2008 12:14:37 -0800	[thread overview]
Message-ID: <49568CAD.7050509@gawab.com> (raw)
In-Reply-To: <49504B8C.8080907@kernel.org>

Tejun Heo wrote:
>> What changes happened between .27 and .28 could've caused this?
>> Anyways, below is what I get now (with your patch), including the
>> frequency of occurrence.
>>     
>
> I have no idea and I'm afraid we'll need a bisection here. :-( Can you
> please try the attached patch?
>
> Thanks.
>
>   

I applied the patch and get the following:

ata2: XXX status=50 after 100 tries
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata2.00: ST_FIRST: !(DRQ|ERR|DF)
ata2.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
         cdb 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
         res 50/00:01:00:00:00/00:00:00:00:00/a0 Emask 0x2 (HSM violation)
ata2.00: status: { DRDY }
ata2: soft resetting link
ata2.00: configured for UDMA/33
ata2: EH complete

I tried to git bisect the problem. First time I thought the error was 
between rc2 and rc3,
but the bisect gave inconclusive results because I couldn't tell for 
sure a good commit from a bad.
I tried again with .27 to .28-rc3, but I was unable to bisect because of 
compile errors (in pre-rc1),
and doing git bisect skip, again landed on a commit with compile errors.

Unless you can think of anything else, I'm just going to wait and see if 
a commit in .29 will fix the problem.

Justin Madru

  reply	other threads:[~2008-12-27 20:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-13  2:07 [2.6.28-rc] Sata soft reset filling log Justin Madru
2008-12-17  5:02 ` Andrew Morton
2008-12-17  7:26   ` Jeff Garzik
2008-12-17 10:13   ` Alan Cox
2008-12-19  7:09     ` Justin Madru
2008-12-22  2:37 ` Tejun Heo
2008-12-22  6:59   ` Justin Madru
2008-12-22  7:14     ` Tejun Heo
2008-12-22 21:51       ` Justin Madru
2008-12-23  2:23         ` Tejun Heo
2008-12-27 20:14           ` Justin Madru [this message]
2008-12-29  6:23             ` Tejun Heo

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=49568CAD.7050509@gawab.com \
    --to=jdm64@gawab.com \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jeff@garzik.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --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 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.