linux-kernel - Re: Regression 3.2 -> 3.3-rc1 10 sec hang at boot and resume, COMRESET failed

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1328242884.15079.22.camel@minggr>
Date:	Fri, 03 Feb 2012 12:21:24 +0800
From:	Lin Ming <ming.m.lin@...el.com>
To:	"Srivatsa S. Bhat" <srivatsa.bhat@...ux.vnet.ibm.com>
Cc:	Norbert Preining <preining@...ic.at>, linux-kernel@...r.kernel.org,
	jeff@...zik.org, Tejun Heo <tj@...nel.org>,
	"stern@...land.harvard.edu >> Alan Stern" <stern@...land.harvard.edu>,
	linux-ide@...r.kernel.org,
	Linux PM mailing list <linux-pm@...r.kernel.org>,
	"Rafael J. Wysocki" <rjw@...k.pl>
Subject: Re: Regression 3.2 -> 3.3-rc1 10 sec hang at boot and resume,
 COMRESET failed

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/