From: Lin Ming <ming.m.lin@intel.com>
To: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
Cc: Norbert Preining <preining@logic.at>,
linux-kernel@vger.kernel.org, jeff@garzik.org,
Tejun Heo <tj@kernel.org>,
"stern@rowland.harvard.edu >> Alan Stern"
<stern@rowland.harvard.edu>,
linux-ide@vger.kernel.org,
Linux PM mailing list <linux-pm@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: Regression 3.2 -> 3.3-rc1 10 sec hang at boot and resume, COMRESET failed
Date: Fri, 03 Feb 2012 12:21:24 +0800 [thread overview]
Message-ID: <1328242884.15079.22.camel@minggr> (raw)
In-Reply-To: <1328231716.15079.15.camel@minggr>
On Fri, 2012-02-03 at 09:15 +0800, Lin Ming wrote:
> On Thu, 2012-02-02 at 14:08 +0530, Srivatsa S. Bhat wrote:
> > Adding some Cc's.
> >
> > On 02/02/2012 10:42 AM, Norbert Preining wrote:
> >
> > > Dear all,
> > >
> > > (please Cc)
> > >
> > > since going from 3.2 to 3.3-rc1 I see a kind of regression wrt booting
> > > time, namely the detection of the CD drive hangs for 10sec (both
> > > dmesg were taken on the same hardware on the same day):
> > >
> > > with 3.3-rc1 and rc2:
> > > [ 3.694012] sd 0:0:0:0: [sda] Attached SCSI disk
> > > [ 9.004013] ata2: link is slow to respond, please be patient (ready=0)
> > > [ 13.652013] ata2: COMRESET failed (errno=-16)
> > > [ 13.972022] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
>
> I'm looking into this problem.
> But I can't reproduce this regression.
>
> Could you attach the full 3.3-rc2 dmesg?
And could you do a bisect?
First, you can check if commit 318893e is good or bad.
If it's bad, then you only need to do a bisect between v3.2 and 318893e.
Otherwise, you need to do a bisect between v3.2 and v3.3-rc1.
Thanks,
Lin Ming
next prev parent reply other threads:[~2012-02-03 4:21 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-02 5:12 Regression 3.2 -> 3.3-rc1 10 sec hang at boot and resume, COMRESET failed Norbert Preining
2012-02-02 8:38 ` Srivatsa S. Bhat
2012-02-03 1:15 ` Lin Ming
2012-02-03 4:21 ` Lin Ming [this message]
2012-02-03 5:24 ` Norbert Preining
2012-02-03 5:34 ` Lin Ming
2012-02-03 5:43 ` Norbert Preining
2012-02-03 8:27 ` Lin Ming
2012-02-06 0:46 ` Norbert Preining
2012-02-06 1:36 ` Lin Ming
2012-02-06 2:40 ` Norbert Preining
2012-02-06 2:49 ` Lin Ming
2012-02-06 3:15 ` Norbert Preining
2012-02-06 4:42 ` Lin Ming
2012-02-06 16:19 ` Tejun Heo
2012-02-06 19:20 ` Brian Norris
2012-02-06 22:46 ` Norbert Preining
2012-02-08 9:10 ` Valdis.Kletnieks
2012-02-13 17:44 ` Tejun Heo
2012-02-15 5:15 ` Brian Norris
2012-02-15 16:57 ` Tejun Heo
2012-02-15 18:29 ` Jeff Garzik
2012-02-15 18:31 ` Tejun Heo
2012-02-15 19:18 ` Jeff Garzik
2012-02-15 23:39 ` Brian Norris
2012-02-16 16:22 ` Jeff Garzik
2012-02-16 14:20 ` Mark Lord
2012-02-16 16:19 ` Jeff Garzik
2012-02-03 4:29 ` Norbert Preining
2012-02-03 4:29 ` Norbert Preining
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=1328242884.15079.22.camel@minggr \
--to=ming.m.lin@intel.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=preining@logic.at \
--cc=rjw@sisk.pl \
--cc=srivatsa.bhat@linux.vnet.ibm.com \
--cc=stern@rowland.harvard.edu \
--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.