linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Tejun Heo <htejun@gmail.com>
Cc: jgarzik@pobox.com, linux-ide@vger.kernel.org
Subject: Re: long boot delay for SATA cdrom on current 2.6.17-git
Date: Thu, 29 Jun 2006 22:10:47 -0700	[thread overview]
Message-ID: <20060630051047.GA8150@kroah.com> (raw)
In-Reply-To: <20060630044912.GA2592@htj.dyndns.org>

On Fri, Jun 30, 2006 at 01:49:12PM +0900, Tejun Heo wrote:
> On Thu, Jun 29, 2006 at 07:53:41PM -0700, Greg KH wrote:
> > With Linus's current -git tree (like 2.6.17-git13), it takes a long time
> > to boot my laptop.  Turns out the SATA cdrom discovery process is taking
> > up many seconds.
> 
> Was any previous version okay?  No timeout messages on boot?

2.6.17 and previous was just fine, no timeout messages that I remember
(definatly no slowdown on boot.)

I can do a git bisect tomorrow to try to narrow it down to the single
changeset if you want me to.

> > This laptop does not have a SATA hard drive, only a SATA cdrom drive.
> > I've included the boot log below and trimmed it after the delay
> > happened, as I doubt anything after it would be relevant.
> > 
> > Is there any patch I can test to help fix this?
> 
> This seems to be the ghost device problem which occurs when the first
> device is ATAPI but the second slot is empty.
> 
> > My .config is also attached, if that helps any.
> 
> Please try the following patch.

Ok, will do.

thanks,

greg k-h

  reply	other threads:[~2006-06-30  5:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-30  2:53 long boot delay for SATA cdrom on current 2.6.17-git Greg KH
2006-06-30  4:49 ` Tejun Heo
2006-06-30  5:10   ` Greg KH [this message]
2006-06-30  5:20   ` Greg KH
2006-06-30  5:26     ` Tejun Heo
2006-06-30 22:10       ` Greg KH
2006-07-08 15:19         ` Tejun Heo
2006-07-11  2:30           ` Albert Lee

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=20060630051047.GA8150@kroah.com \
    --to=greg@kroah.com \
    --cc=htejun@gmail.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@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 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).