From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Garzik Subject: Re: cached PCS Date: Wed, 09 Aug 2006 06:27:06 -0400 Message-ID: <44D9B87A.8020507@garzik.org> References: <44D97F07.9000301@garzik.org> <44D9AF83.80507@gmail.com> <44D9B43A.9010807@garzik.org> <44D9B4BC.5050707@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from srv5.dvmed.net ([207.36.208.214]:1963 "EHLO mail.dvmed.net") by vger.kernel.org with ESMTP id S1030655AbWHIK1I (ORCPT ); Wed, 9 Aug 2006 06:27:08 -0400 In-Reply-To: <44D9B4BC.5050707@gmail.com> Sender: linux-ide-owner@vger.kernel.org List-Id: linux-ide@vger.kernel.org To: Tejun Heo Cc: "linux-ide@vger.kernel.org" Tejun Heo wrote: > Jeff Garzik wrote: >> Tejun Heo wrote: >>> Jeff Garzik wrote: >>>> can you resurrect your cached PCS patch? >>>> >>>> 2.6.18-rc didn't fix the ghost device and long boot delay problems >>>> for everybody. >>> >>> The cached PCS patch was to fix device detection failure on some >>> ICH5s where PCS is cleared while probing the first port. Remaining >>> ghost device and long boot delay are fixed by honor-PCS patch. Do >>> you want me to resurrect both? >> >> hrm. Maybe just honor-PCS? > > Yeap, we need to verify whether the less-jealous-PCS-update patch cured > the ICH5 problem. If you are talking about the patch currently in 2.6.18-rc, I got several ACKs that it fixed their problems. But OTOH, there was also http://marc.theaimsgroup.com/?t=115346292700002&r=1&w=2 Jeff