linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
To: admin@brien.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: SATA probe delay on boot
Date: Thu, 4 Sep 2003 01:53:07 +0200	[thread overview]
Message-ID: <200309040153.07931.bzolnier@elka.pw.edu.pl> (raw)
In-Reply-To: <20030903161848.2109.h004.c000.wm@mail.brien.com.criticalpath.net>


On Thursday 04 of September 2003 01:18, admin@brien.com wrote:
> Hi,

Hi,

> I have a Sil3112A SATA controller, which linux works OK
> with. It supports RAID (up to 4 devices), but I'm using
> BASE option -- only 1 hard drive.
>
> My question is regarding a 15-20 second delay which
> normally occurs every time I boot, unless I pass the

Please try attached patch and send dmesg output (with patch applied).
Patch is against current 2.6-bk tree, but should apply to any recent
2.4.x or 2.6.x kernels.

diff -puN drivers/ide/ide-probe.c~ide-siimage-wait drivers/ide/ide-probe.c
--- linux-2.6.0-test4-bk5/drivers/ide/ide-probe.c~ide-siimage-wait	2003-09-04 01:34:02.285489272 +0200
+++ linux-2.6.0-test4-bk5-root/drivers/ide/ide-probe.c	2003-09-04 01:47:58.145419248 +0200
@@ -56,6 +56,8 @@
 #include <asm/uaccess.h>
 #include <asm/io.h>
 
+#define DEBUG
+
 /**
  *	generic_id		-	add a generic drive id
  *	@drive:	drive to make an ID block for
@@ -345,7 +347,16 @@ static int actual_try_to_identify (ide_d
 		}
 		/* give drive a breather */
 		ide_delay_50ms();
-	} while ((hwif->INB(hd_status)) & BUSY_STAT);
+		s = hwif->INB(hd_status);
+		if (s == 0xff) {
+#ifdef DEBUG
+			printk("%s: status == 0xff\n", drive->name);
+#endif
+			return 1;
+		}
+		if ((s & BUSY_STAT) == 0)
+			break;
+	} while (1);
 
 	/* wait for IRQ and DRQ_STAT */
 	ide_delay_50ms();

_

> options ide3=0 - ide9=0 to fill up the device table. I
> think I have to do this because if I do only ide3=0
> (where the device would be), it uses ide4, and so on. I
> have GRUB set up to do this automatically, but it's not
> exactly adequate (,is it?). So I was wondering if
> there're any other ways to get the same affect. Is or
> could there be an option to simply disable the probing
> of the one specific device/channel every time?

"ide3=noprobe" doesnt work?

--bartlomiej


  reply	other threads:[~2003-09-03 23:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-03 23:18 SATA probe delay on boot admin
2003-09-03 23:53 ` Bartlomiej Zolnierkiewicz [this message]
2003-09-04  0:54 Brien
2003-09-04  4:55 ` Andre Hedrick
2003-09-04 11:04 Brien

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=200309040153.07931.bzolnier@elka.pw.edu.pl \
    --to=b.zolnierkiewicz@elka.pw.edu.pl \
    --cc=admin@brien.com \
    --cc=linux-kernel@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).