public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: osb972ww-linuxczmil@yahoo.com
Cc: linux-kernel@vger.kernel.org,
	IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: Fw: 2.6.24.X: SATA/AHCI related boot delay. - not with 2.6.24.3
Date: Fri, 21 Mar 2008 18:56:10 +0900	[thread overview]
Message-ID: <47E3863A.1010700@gmail.com> (raw)
In-Reply-To: <217535.99274.qm@web34505.mail.mud.yahoo.com>

Hello,

osb972ww-linuxczmil@yahoo.com wrote:
> 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.

libata drivers don't need or support hdparm -u settings.

>  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. ?

Well, IRQ 18 is taken offline during USB initialization.  The IRQ is
shared with the SATA controller, so SATA controller doesn't work either.
 It isn't clear why the IRQ handler is taken offline.  It could be the
USB controller but can also be the SATA controller.  Does not loading
usb driver make any difference?

-- 
tejun

  reply	other threads:[~2008-03-21  9:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-21  3:04 Fw: 2.6.24.X: SATA/AHCI related boot delay. - not with 2.6.24.3 osb972ww-linuxczmil
2008-03-21  9:56 ` Tejun Heo [this message]
2008-03-21 10:42 ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2008-03-21 15:12 Fw: " osb972ww-linuxczmil
2008-03-22  8:18 ` Tejun Heo
2008-03-20 18:03 osb972ww-linuxczmil
2008-03-21  2:23 ` Tejun Heo

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=47E3863A.1010700@gmail.com \
    --to=htejun@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=osb972ww-linuxczmil@yahoo.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox