Bug 157074

Summary:	[boot] [usb8] vfs_mountroot_ask is called when no usb keyboard is initialized
Product:	Base System	Reporter:	Dmitry <hanabana>
Component:	usb	Assignee:	freebsd-usb (Nobody) <usb>
Status:	Open ---
Severity:	Affects Only Me	CC:	ngie
Priority:	Normal
Version:	8.2-STABLE
Hardware:	Any
OS:	Any

Description Dmitry 2011-05-15 20:40:08 UTC

When kernel can not locate root filesystem it asks user to input
filesystem specification. But no USB keyboards are initialized at that
moment. And user is not capable to fix problem unless he have an AT
keyboard.


This is a part of dmesg of normal boot process.  start_init functions
calls vfs_mountroot right before searching for the "init" executable.
In case of unavailability of root system vfs_mountroot_ask is called
from vfs_mountroot.  And usb keyboard stays uninitialized.

Trying to mount root from ufs:/dev/ad6p3.journal
start_init: trying /sbin/init
ugen2.2: <Microsoft> at usbus2
ukbd0: <Microsoft Comfort Curve Keyboard 2000, class 0/0, rev 2.00/1.73, addr 2> on usbus2
kbd2 at ukbd0
kbd2: ukbd0, generic (0), config:0x0, flags:0x3d0000
uhid0: <Microsoft Comfort Curve Keyboard 2000, class 0/0, rev 2.00/1.73, addr 2> on usbus2
ugen2.3: <Microsoft> at usbus2

How-To-Repeat: Comment out or spoil the line of /etc/fstab specifying a root
filesystem. Reboot system. Try to use usb keyboard to fix problem.

Comment 1 Gavin Atkinson freebsd_committer

2011-10-19 17:51:35 UTC

Responsible Changed
From-To: freebsd-bugs->freebsd-usb

I'm not sure, but I think that this is a duplicate of usb/133989. 
Perhaps somebody more knowledgeable could verify that and close 
this?

Comment 2 Enji Cooper freebsd_committer

2014-07-28 08:44:21 UTC

(In reply to Gavin Atkinson from comment #1)
> Responsible Changed
> From-To: freebsd-bugs->freebsd-usb
> 
> I'm not sure, but I think that this is a duplicate of usb/133989. 
> Perhaps somebody more knowledgeable could verify that and close 
> this?

This is definitely a dupe.

Comment 3 Eitan Adler freebsd_committer

2018-05-28 19:48:31 UTC

batch change:

For bugs that match the following
-  Status Is In progress 
AND
- Untouched since 2018-01-01.
AND
- Affects Base System OR Documentation

DO:

Reset to open status.


Note:
I did a quick pass but if you are getting this email it might be worthwhile to double check to see if this bug ought to be closed.