linux-kernel - Re: [PATCH] Re: [git patches] libata updates - (improve post-reset device ready test) regression

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20080508161805.GA3941@gentoox2.trippelsdorf.de>
Date:	Thu, 8 May 2008 18:18:05 +0200
From:	Markus Trippelsdorf <markus@...ppelsdorf.de>
To:	Takashi Iwai <tiwai@...e.de>
Cc:	Jeff Garzik <jeff@...zik.org>, linux-ide@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>, htejun@...il.com,
	marc.c.dionne@...il.com, dl9pf@....de, bug-track@...her-privat.net,
	sitsofe@...oo.com
Subject: Re: [PATCH] Re: [git patches] libata updates - (improve post-reset
	device ready test) regression

On Thu, May 08, 2008 at 06:05:08PM +0200, Takashi Iwai wrote:
> At Thu, 08 May 2008 11:35:11 -0400,
> Jeff Garzik wrote:
> > 
> > Markus Trippelsdorf wrote:
> > >> Tejun Heo (12):
> > >>       libata: improve post-reset device ready test
> > > 
> > > This commit (78ab88f04f44bed566d51dce0c7cbfeff6449a06) causes a long
> > > boot delay with my onboard Promise controller. It seems like libata
> > > probes for a nonexisting PATA drive...
> > > 
> > 
> > Does the attached patch fix things?
> > 
> > It basically reverts the patch, while still maintaining the 
> > consolidation.  It looks like that status evaluation is not as universal 
> > as believed.
> 
> Yes, the patch fixes the problem on my machine.
> 

Your patch fixes the problem for me, too...

-- 
Markus
--
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/