From: Pete Zaitcev <zaitcev@redhat.com>
To: Eric Lammerts <eric@lammerts.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: rootfs on USB storage device
Date: Fri, 16 Nov 2001 12:30:53 -0500 [thread overview]
Message-ID: <20011116123053.A7379@devserv.devel.redhat.com> (raw)
In-Reply-To: <200111160306.fAG36ZW05331@devserv.devel.redhat.com> <Pine.LNX.4.40.0111161403001.991-100000@ally.lammerts.org>
In-Reply-To: <Pine.LNX.4.40.0111161403001.991-100000@ally.lammerts.org>; from eric@lammerts.org on Fri, Nov 16, 2001 at 02:21:04PM +0100
> Date: Fri, 16 Nov 2001 14:21:04 +0100 (CET)
> From: Eric Lammerts <eric@lammerts.org>
> To: Pete Zaitcev <zaitcev@redhat.com>
> cc: josn@josn.myip.org, Greg KH <greg@kroah.com>,
> <linux-kernel@vger.kernel.org>
> > I think khubd needs to run to complete whole process and mdelay()
> > locks it out. You need something that calls schedule() for USB
> > detection to work. Try to use schedule_timeout() instead of mdelay().
>
> This patch works for me.
Looks like a well done patch but what does happen if root= was
indeed incorrect? I wish there was a way to print something
meaningful for the operator.
-- Pete
P.S. - quoting the patch, saved for future reference
> --- linux-2.4.14-pre8-ext3/fs/super.c.orig Fri Nov 16 00:59:18 2001
> +++ linux-2.4.14-pre8-ext3/fs/super.c Fri Nov 16 01:07:26 2001
> @@ -1009,11 +1009,13 @@
> * Allow the user to distinguish between failed open
> * and bad superblock on root device.
> */
> - printk ("VFS: Cannot open root device \"%s\" or %s\n",
> + printk ("VFS: Cannot open root device \"%s\" or %s, retrying in 1s.\n",
> root_device_name, kdevname (ROOT_DEV));
> - printk ("Please append a correct \"root=\" boot option\n");
> - panic("VFS: Unable to mount root fs on %s",
> - kdevname(ROOT_DEV));
> +
> + /* wait 1 second and try again */
> + current->state = TASK_INTERRUPTIBLE;
> + schedule_timeout(HZ);
> + goto retry;
> }
>
> check_disk_change(ROOT_DEV);
next prev parent reply other threads:[~2001-11-16 17:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1005878220.14858.linux-kernel2news@redhat.com>
2001-11-16 3:06 ` rootfs on USB storage device Pete Zaitcev
2001-11-16 13:21 ` Eric Lammerts
2001-11-16 17:30 ` Pete Zaitcev [this message]
2001-11-15 3:22 Jos Nouwen
2001-11-15 5:07 ` Greg KH
2001-11-16 2:32 ` Jos Nouwen
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=20011116123053.A7379@devserv.devel.redhat.com \
--to=zaitcev@redhat.com \
--cc=eric@lammerts.org \
--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