linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Kevin Radloff <radsaq@gmail.com>,
	Linus Torvalds <torvalds@osdl.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: Linux 2.6.19-rc2
Date: Fri, 20 Oct 2006 17:12:36 -0400	[thread overview]
Message-ID: <45393BC4.5020903@garzik.org> (raw)
In-Reply-To: <1161377586.26440.61.camel@localhost.localdomain>

Alan Cox wrote:
> Ar Gwe, 2006-10-20 am 14:30 -0400, ysgrifennodd Kevin Radloff:
>> On 10/13/06, Linus Torvalds <torvalds@osdl.org> wrote:
>>> Ok, it's a week since -rc1, so -rc2 is out there.
>> A bit behind, but booting still takes ages on my laptop as
>> libata/ata_piix tries to probe a device that isn't there (I reported
>> this previously against -rc1, but got no response):
> 
> Probing is somewhat broken in 2.6.18 - something in the core code
> changed as its upset quite a few drivers at once. One case causes
> repeated errors and finally detection of an ATAPI device, the other
> causes repeated errors and then failure when no device is present but
> takes a few minutes and keeps IRQs locked off for long periods. Both
> appear to be fallouts from the new EH code.

There are definitely warts related to the new EH stuff, but specifically 
for SATA + ata_piix, it has been a long hard road of trying various 
probing mechanisms.  Tejun has some patches that revert all the PCS work 
and rewinds back to original SATA ata_piix probing, in -mm for testing.

If testing feedback proves positive, let's go ahead and fast-track that 
up the line.

With ata_piix, I would worry more about PCS register follies than core 
libata.  Users can try the module option force_pcs=[0|1|2] to experiment 
and see if any of the three possibilities improves their boot.

	Jeff

  parent reply	other threads:[~2006-10-20 21:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.64.0610130941550.3952@g5.osdl.org>
     [not found] ` <20061014111458.GI30596@stusta.de>
2006-10-14 11:22   ` [1/3] 2.6.19-rc2: known unfixed regressions Adrian Bunk
2006-10-17 15:59 ` 2.6.19-rc2: known unfixed regressions (v2) Adrian Bunk
     [not found]   ` <4534C7A7.7000607@hp.com>
     [not found]     ` <20061018221520.GK3502@stusta.de>
     [not found]       ` <20061018231844.GA16857@devserv.devel.redhat.com>
2006-10-19 15:26         ` [2.6.19 patch] drivers/ide/pci/generic.c: re-add the __setup("all-generic-ide",...) Adrian Bunk
2006-10-19 16:07           ` Randy Dunlap
2006-10-19 16:13             ` Adrian Bunk
2006-10-19 16:29               ` Alan Cox
2006-10-20 21:05                 ` Adrian Bunk
2006-10-21 17:54                   ` Randy Dunlap
     [not found] ` <3b0ffc1f0610201130i8f15e49oec2cdc68abb8dbd@mail.gmail.com>
     [not found]   ` <1161377586.26440.61.camel@localhost.localdomain>
2006-10-20 21:12     ` Jeff Garzik [this message]
2006-10-22 12:23 ` 2.6.19-rc2: known unfixed regressions (v3) Adrian Bunk
2006-10-24 15:00   ` Michael S. Tsirkin
2006-10-25  8:28     ` Pavel Machek
2006-10-25  8:37       ` Michael S. Tsirkin

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=45393BC4.5020903@garzik.org \
    --to=jeff@garzik.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=radsaq@gmail.com \
    --cc=torvalds@osdl.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).