All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: "liyu@WAN" <liyu@ccoss.com.cn>
Cc: Linux-newbie@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Problem booting 2.6.13 on RHEL 4
Date: Wed, 14 Sep 2005 12:20:32 -0400	[thread overview]
Message-ID: <43284DD0.5080709@tmr.com> (raw)
In-Reply-To: <4327DBBB.7090108@ccoss.com.cn>

liyu@WAN wrote:
> 
> It seem that kernel have no time to probe your disk, and do not
> read parttion table.
> 
> I use kernel 2.6.12 and SATA disk on FC3, also failed to boot.
> but after some experiment, I found if we place 'sleep 5'
> statement between insmod commands in linuxrc or init, it will
> boot up!
> 
> However, this idea is too HACK.

It would have been nice, back in the 2.5.46 timeframe when modules were 
complete reinvented, to have provided a hook by which modprobe could 
have waited until insertion init was complete.

The sleep is a hack indeed, as is the slightly more reliable solution to 
tail the log and look for init messages to appear. Perhaps look for the 
devices in /proc/scsi/scsi or something?

There doesn't seem to be a "right way" for this, particularly if you 
have both warm and cold boots, which may differ by minutes depending on 
disk spin-up already being done.

-- 
    -bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
  last possible moment - but no longer"  -me

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

WARNING: multiple messages have this Message-ID (diff)
From: Bill Davidsen <davidsen@tmr.com>
To: "liyu@WAN" <liyu@ccoss.com.cn>
Cc: Linux-newbie@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Problem booting 2.6.13 on RHEL 4
Date: Wed, 14 Sep 2005 12:20:32 -0400	[thread overview]
Message-ID: <43284DD0.5080709@tmr.com> (raw)
In-Reply-To: <4327DBBB.7090108@ccoss.com.cn>

liyu@WAN wrote:
> 
> It seem that kernel have no time to probe your disk, and do not
> read parttion table.
> 
> I use kernel 2.6.12 and SATA disk on FC3, also failed to boot.
> but after some experiment, I found if we place 'sleep 5'
> statement between insmod commands in linuxrc or init, it will
> boot up!
> 
> However, this idea is too HACK.

It would have been nice, back in the 2.5.46 timeframe when modules were 
complete reinvented, to have provided a hook by which modprobe could 
have waited until insertion init was complete.

The sleep is a hack indeed, as is the slightly more reliable solution to 
tail the log and look for init messages to appear. Perhaps look for the 
devices in /proc/scsi/scsi or something?

There doesn't seem to be a "right way" for this, particularly if you 
have both warm and cold boots, which may differ by minutes depending on 
disk spin-up already being done.

-- 
    -bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
  last possible moment - but no longer"  -me


  reply	other threads:[~2005-09-14 16:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-14  4:08 Problem booting 2.6.13 on RHEL 4 Rajat Jain
2005-09-14  4:08 ` Rajat Jain
2005-09-14  8:13 ` liyu@WAN
2005-09-14  8:13   ` liyu@WAN
2005-09-14 16:20   ` Bill Davidsen [this message]
2005-09-14 16:20     ` Bill Davidsen
2005-09-14 16:50     ` Roger Heflin
2005-09-14 16:50       ` Roger Heflin
2005-09-15 15:30 ` Jason Baron
2005-09-15 15:30   ` Jason Baron
2005-09-28  9:18   ` Rajat Jain

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=43284DD0.5080709@tmr.com \
    --to=davidsen@tmr.com \
    --cc=Linux-newbie@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liyu@ccoss.com.cn \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.