linux-kernel - Re: Fw: 2.6.24.X: SATA/AHCI related boot delay.

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-next>] [day] [month] [year] [list]

Message-ID: <217535.99274.qm@web34505.mail.mud.yahoo.com>
Date:	Thu, 20 Mar 2008 20:04:13 -0700 (PDT)
From:	osb972ww-linuxczmil@...oo.com
To:	Tejun Heo <htejun@...il.com>
Cc:	linux-kernel@...r.kernel.org,
	IDE/ATA development list <linux-ide@...r.kernel.org>
Subject: Re: Fw: 2.6.24.X: SATA/AHCI related boot delay. - not with 2.6.24.3


HI Tejun,

  setting irqpoll fixed both problems, and there are no "nasty grams" in dmesg now.   The original reason I was trying to use the hdparm -u on /dev/sda was because it was hanging for a few seconds when doing writes to the CFdisk, and in the past that was the kind of thing that hdparm -u would generally fix.   Now with the irqpoll kernel option, the /dev/sdb SATA drive was found, and I can mount it and write to it.  The CFcard /dev/sda is also responding to writes better than before.

Thanks for the suggestion to use irqpoll.    What is the problem within the driver(s) that is requiring irqpoll. ?

Best regards,
C. W. Wright



----- Original Message ----
> From: Tejun Heo <htejun@...il.com>
> To: osb972ww-linuxczmil@...oo.com
> Cc: linux-kernel@...r.kernel.org; IDE/ATA development list <linux-ide@...r.kernel.org>
> Sent: Thursday, March 20, 2008 10:23:50 PM
> Subject: Re: Fw: 2.6.24.X: SATA/AHCI related boot delay. - not with 2.6.24.3
> 
> Hello,
> 
> osb972ww-linuxczmil@...oo.com wrote:
> >  Greetings,
> >   I'm having a problem with 2.6.23.1-42 (Fedora 8) properly driving a SATA 
> > drive.  Although it is detected during boot as indicated by the dmesg below, 
> > once the sytstem is up and running, the drive is not accessible.   The second 
> > issue is with the CFdrive on the the primary IDE.  It works, but I can't 
> enable 
> > interrupts with hdparm -u 1 /dev/sda.   
> > 
> >  The interesting thing is when I put in a Fedora 5 system with a 2.6.17 
> kernel, 
> > everything works as expected.  I can hdparm -u 1 /dev/hda and it works as  
> expected, and
> >  the SATA drive is detected and works properly all on the exact  same 
> hardware.  
> >  
> >  I've tried several different SATA drives also.   Thery all work on the old 
> >  Fedora 5/ 2.6.17 system, and none work on Fedora 8/2.6.23 or 2.6.24 kernels.
> 
> Does irqpoll kernel parameter help?
> 
> -- 
> tejun
> 



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