Bug 241979 - kernel not booting into multiuser/singleuser
Summary: kernel not booting into multiuser/singleuser
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 12.1-RELEASE
Hardware: amd64 Any
: --- Affects Some People
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
: 240676 (view as bug list)
Depends on:
Blocks:
 
Reported: 2019-11-15 07:53 UTC by tschweikle
Modified: 2019-11-15 09:43 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description tschweikle 2019-11-15 07:53:51 UTC
Kernel as of base r354708 wont boot. Last message on screen:

uhub2 on uhub0
uhub2: <VMware, Inc.> on usbus0
uhub1: 6 ports with 6 removable, self powered
uhub2: 7 ports with 7 removable, self powered

No further information available. System does not load init. System does not start. System unusable after upgrade. Last working versions: all before base r339035

Same behaviour for
- FREEBSD-CURRENT
- FREEBSD-11.3-RELEASE
- FREEBSD-12.0-RELEASE
- FREEDSD-12.1-RELEASE

Kernel config: GENERIC with additions/changes:
include         GENERIC
ident           FBSD12
options         SCSI_DELAY=3000

makeoptions     DEBUG=-g   # Build kernel with gdb(1) debug symbols

# VESA video modes
options         VESA
options         VGA_WIDTH90
options         SC_PIXEL_MODE

Same kernel config for FreeBSD 11.3, 12.0, 12.1, CURRENT.
Only difference: ident.

This problem seems to exist for a lot of people upgrading from sources. It started with base r339035 on FreeBSD 12-ALPHA9. FreeBSD 12-ALPHA8 is running as expected. FreeBSD 12-ALPHA9 only boots up to same point as source release base r354705.
Comment 1 tschweikle 2019-11-15 09:41:52 UTC
Bug #209025 is here again.
Module opensolaris seems required by module zfs, but not build. In tune, after installing a new build kernel, module zfs fails to load and the kernel waits forever mounting zfs:root.
Comment 2 tschweikle 2019-11-15 09:43:01 UTC
*** Bug 240676 has been marked as a duplicate of this bug. ***