All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: "Berck E. Nash" <flyboy@gmail.com>
Cc: "linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: 2.6.23-rc7-mm1 AHCI ATA errors -- won't boot
Date: Mon, 24 Sep 2007 21:37:30 -0400	[thread overview]
Message-ID: <46F8665A.4000206@garzik.org> (raw)
In-Reply-To: <46F7FBCB.4030803@gmail.com>

Berck E. Nash wrote:
> Greetings,
> 
> I get a few million of these on boot-- the system never actually boots.
> Works fine in 2.6.23-rc7.
> 
> [   50.456012] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> [   50.462484] ata2.00: irq_stat 0x40000001
> [   50.466441] ata2.00: cmd e5/00:00:00:00:00/00:00:00:00:00/a0 tag 0
> cdb 0x0 data 0
> [   50.466442]          res 51/04:00:01:01:80/00:00:00:00:00/a0 Emask
> 0x1 (device error)
> [   50.481914] ata2.00: status: {DRDY ERR }
> [   50.485876] ata2.00: error: {ABRT }
> [   50.489533] ata2.00: configured for UDMA/133
> [   50.493839] ata2: EH complete
> 
> I've attached the entire dmesg and lspci.

Are you "git-friendly"?  A few quick kernel compiles and reboots would 
help us narrow down the problem, given that it's a reproducible regression.

The first step would be to clone the "upstream" branch of 
git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev.git

and see if the problem is reproducible there.  If yes, then you have 
narrowed down the problem to something my ATA devel tree has introduced 
into -mm.

Once the blame has been squared fixed upon me :) you can use git-bisect 
to locate the precise change that broke your setup.

Info at http://kerneltrap.org/node/11753 or 
http://www.kernel.org/pub/software/scm/git/docs/v1.3.3/howto/isolate-bugs-with-bisect.txt
or "man git-bisect"

	Jeff



  reply	other threads:[~2007-09-25  1:37 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-24 18:02 2.6.23-rc7-mm1 AHCI ATA errors -- won't boot Berck E. Nash
2007-09-25  1:37 ` Jeff Garzik [this message]
2007-09-25 18:14   ` Berck E. Nash
2007-09-25 18:21     ` Jens Axboe
2007-09-25 18:28       ` Berck E. Nash
2007-09-25 18:32         ` Jens Axboe
2007-09-25 19:29   ` Berck E. Nash
2007-09-25 20:40     ` Jeff Garzik
2007-09-25 22:07       ` Berck E. Nash
2007-09-25 22:46         ` Berck E. Nash
2007-09-26  1:21     ` Jeff Garzik
2007-09-26  2:25       ` Berck E. Nash
2007-09-26  2:33         ` Jeff Garzik
2007-09-26  4:40 ` Jeff Garzik
2007-09-26 10:03   ` Bernd Schmidt
2007-09-26 14:22     ` Berck E. Nash
2007-09-27  1:05       ` Tejun Heo
2007-09-26 14:19   ` Berck E. Nash
2007-10-03 21:18 ` Jeff Garzik
     [not found] <fa.7B5oGGPZtkIAG9trDHdybt+z9Qg@ifi.uio.no>
     [not found] ` <fa.lh2GEsFivC+TeMBqgRXU+5p7ySM@ifi.uio.no>
     [not found]   ` <fa.tqIC/0YXN2BDEJQ7WBFuJ0EEUrI@ifi.uio.no>
     [not found]     ` <fa.Q/HeymU0u7VpG+dN5Lc1DraTos0@ifi.uio.no>
2007-09-25 22:39       ` Robert Hancock
2007-09-26  1:10         ` Jeff Garzik

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=46F8665A.4000206@garzik.org \
    --to=jeff@garzik.org \
    --cc=akpm@linux-foundation.org \
    --cc=flyboy@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.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.