Bug 222908 - Boot hangs on HPET on Intel Apollo Lake
Summary: Boot hangs on HPET on Intel Apollo Lake
Status: Closed FIXED
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 11.1-RELEASE
Hardware: amd64 Any
: --- Affects Many People
Assignee: Konstantin Belousov
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-10-10 18:58 UTC by baraa
Modified: 2018-08-22 04:29 UTC (History)
6 users (show)

See Also:
koobs: mfc-stable11+


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description baraa 2017-10-10 18:58:15 UTC
11.1-RELEASE-p1 - hangs at Timecount HPET.

Workaround set hint.hpet.0.clock=0.
Comment 1 Franco Fichtner 2018-02-01 14:29:04 UTC
Dear FreeBSD developers,

Is there a permanent code fix for this regression from 11.0 to 11.1?

Will it be added as errata?


Cheers,
Franco
Comment 2 Hannes Hauswedell 2018-03-27 18:42:06 UTC
Just ran into this, as well, I have set the hpet hint, but I now I am stuck at atrtc0

Any help would be appreciated, thanks a lot!

This is the dmesg:

CPU: Intel(R) Celeron(R) CPU J3455 @ 1.50GHz (1497.67-MHz K8-class CPU)
  Origin="GenuineIntel"  Id=0x506c9  Family=0x6  Model=0x5c  Stepping=9
  Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
  Features2=0x4ff8ebbf<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,SDBG,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,RDRAND>
  AMD Features=0x2c100800<SYSCALL,NX,Page1GB,RDTSCP,LM>
  AMD Features2=0x101<LAHF,Prefetch>
  Structured Extended Features=0x2294e283<FSGSBASE,TSCADJ,SMEP,ERMS,NFPUSG,MPX,PQE,RDSEED,SMAP,CLFLUSHOPT,PROCTRACE,SHA>
  XSAVE Features=0xf<XSAVEOPT,XSAVEC,XINUSE,XSAVES>
  VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID,VID,PostIntr
  TSC: P-state invariant, performance statistics
real memory  = 4294967296 (4096 MB)
avail memory = 3903700992 (3722 MB)
Event timer "LAPIC" quality 600
ACPI APIC Table: <INTEL  EDK2    >
WARNING: L1 data cache covers less APIC IDs than a core
0 < 1
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
FreeBSD/SMP: 1 package(s) x 4 core(s)
random: unblocking device.
ioapic0 <Version 2.0> irqs 0-119 on motherboard
SMP: AP CPU #2 Launched!
SMP: AP CPU #3 Launched!
SMP: AP CPU #1 Launched!
Timecounter "TSC" frequency 1497668416 Hz quality 1000
random: entropy device external interface
wlan: mac acl policy registered
netmap: loaded module
module_register_init: MOD_LOAD (vesa, 0xffffffff810a67f0, 0) error 19
random: registering fast source Intel Secure Key RNG
random: fast provider: "Intel Secure Key RNG"
kbd1 at kbdmux0
nexus0
cryptosoft0: <software crypto> on motherboard
acpi0: <ALASKA A M I > on motherboard
unknown: I/O range not supported
cpu0: <ACPI CPU> on acpi0
cpu1: <ACPI CPU> on acpi0
cpu2: <ACPI CPU> on acpi0
cpu3: <ACPI CPU> on acpi0
attimer0: <AT timer> port 0x40-0x43,0x50-0x53 irq 0 on acpi0
Timecounter "i8254" frequency 1193182 Hz quality 0
Event timer "i8254" frequency 1193182 Hz quality 100
atrtc0: <AT realtime clock> port 0x70-0x77 on acpi0
atrtc0: Warning: Couldn't map I/O.
Comment 3 Hannes Hauswedell 2018-03-27 19:00:35 UTC
It actually gets past the real time clock, verbose boot shows it hanging at:

atrtc0: <AT realtime clock> port 0x70-0x77 on acpi0
atrtc0: Warning: Couldn't map I/O.
atrtc0: registered as a time-of-day clock (resolution 1000000us, adjustment 0.500000000s)
ioapic0: routing intpin 8 (ISA IRQ 8) to lapic 4 vector 48
ioapic0: routing intpin 8 (ISA IRQ 8) to lapic 0 vector 49


Trying NoACPI+Safe mode results in a kernel panic:

Timeout initializing vt_vga
KDB: debugger backends: ddb
KDB: current backend: ddb
panic: running without device atpic requires a local APIC
cpuid = 0
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xffffffff8249c950
vpanic() at vpanic+0x186/frame 0xffffffff8249c9d0
panic() at panic+0x43/frame 0xffffffff8249ca30
apic_init() at apic_init+0x112/frame 0xffffffff8249ca50
mi_startup() at mi_startup+0x9c/frame 0xffffffff8249ca70
btext() at btext+0x2c
KDB: enter: panic

SafeMode-only boots the system a lot further, but it then hangs on mounting root:

usbus0: 5.0Gbps Super Speed USB v3.0
ugen0.1: <0x8086 XHCI root HUB> at usbus0
uhub0: <0x8086 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0
uhub0: 15 ports with 15 removable, self powered
ugen0.2: <vendor 0x05e3 USB2.0 Hub> at usbus0
uhub1 on uhub0
uhub1: <vendor 0x05e3 USB2.0 Hub, class 9/0, rev 2.00/85.36, addr 1> on usbus0
uhub1: 4 ports with 4 removable, self powered
ugen0.3: <SanDisk Ultra Fit> at usbus0
umass0 on uhub0
umass0: <SanDisk Ultra Fit, class 0/0, rev 3.00/1.00, addr 2> on usbus0
umass0:  SCSI over Bulk-Only; quirks = 0x8100
umass0:4:0: Attached to scbus4
da0 at umass-sim0 bus 0 scbus4 target 0 lun 0
da0: <SanDisk Ultra Fit 1.00> Removable Direct Access SPC-4 SCSI device
da0: Serial Number 4C531146380423113023
da0: 400.000MB/s transfers
da0: 14663MB (30031250 512 byte sectors)
da0: quirks=0x2<NO_6_BYTE>
Trying to mount root from ufs:/dev/ufs/OPNsense_Nano [rw]...
Mounting filesys

(yes, it stops in the middle of the word)
Comment 4 Hannes Hauswedell 2018-04-10 17:40:45 UTC
The workaround does indeed work, other issues are unrelated to this.
Comment 6 Konstantin Belousov freebsd_committer freebsd_triage 2018-04-26 21:54:49 UTC
This should be fixed by r333026.
Comment 7 Jose Luis Duran freebsd_committer freebsd_triage 2018-05-05 00:07:14 UTC
(In reply to Konstantin Belousov from comment #6)

Thank you! It works!

Tested using 12.0-CURRENT (20180503-r333209) on an E3950.
Comment 8 Kubilay Kocak freebsd_committer freebsd_triage 2018-08-22 04:29:48 UTC
Merged (to stable/11) in base r333166

Assign to committer that resolved