Date: Tue, 10 Feb 2004 09:58:30 +0300 (MSK) From: Dmitry Morozovsky <marck@rinet.ru> To: freebsd-hackers@freebsd.org Subject: 4-stable bug: comconsole and boot -a option Message-ID: <20040210075552.O78030@woozle.rinet.ru>
next in thread | raw e-mail | index | archive | help
Dear colleagues,
I found very strange bug. Actually, bug was introduced at running system with
vinum root, when I did not succeed in mounting explicit root via `boot -a'
prompt. I did a bit of research, and found that there is certainly a bug when
comconsole is enabled:
ad0: 7339MB <QUANTUM FIREBALL EL7.6A> [15907/15/63] at ata0-master UDMA33
Manual root filesystem specification:
<fstype>:<device> Mount <device> using filesystem <fstype>
eg. ufs:/dev/da0s1a
? List valid disk boot devices
<empty line> Abort manual input
mountroot> ufs:/dev/ad0s1e
Mounting root from ufs:/dev/ad0s1a
Look at two last lines. Input asked at vfs_mountroot_ask() did not used,
possibly because kern/vfs_conf.c:gets() dit not actually read the input from
comconsole. However, I'm not kernel hacker and looking at kern/tty_cons.c
scares me a bit :)
Should I file a PR for this?
Sincerely,
D.Marck [DM5020, MCK-RIPE, DM3-RIPN]
------------------------------------------------------------------------
*** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru ***
------------------------------------------------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040210075552.O78030>