https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262638
Mark Johnston changed:
What|Removed |Added
Assignee|b...@freebsd.org|ma...@freebsd.org
--- Comment #7 f
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262638
--- Comment #6 from John F. Carr ---
Created attachment 232639
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=232639&action=edit
another patch
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262638
--- Comment #5 from Mark Johnston ---
(In reply to John F. Carr from comment #4)
This looks like it'd work, but it's hard for a reader to understand where the
value of HPET_MEM_MIN_WIDTH comes from. Why not make it just large enough to
rea
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262638
--- Comment #4 from John F. Carr ---
Created attachment 232585
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=232585&action=edit
a more complicated patch
With this patch the kernel enables HPET on an AMD Opteron x3421 (which wor
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262638
Mark Johnston changed:
What|Removed |Added
Status|New |Open
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262638
--- Comment #2 from John F. Carr ---
Lowering the minimum region size does the trick. Now my kernel says
hpet0: iomem 0xfed0-0xfed001ff on acpi0
hpet0: vendor 0x1022, rev 0x1, 14318180Hz, 3 timers, legacy route
Timecounter "HPET" fre
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262638
--- Comment #1 from John F. Carr ---
Created attachment 232539
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=232539&action=edit
lower minimum region size to 512
--
You are receiving this mail because:
You are the assignee for
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262638
Bug ID: 262638
Summary: overly strict check of hpet region size
Product: Base System
Version: 13.0-STABLE
Hardware: amd64
OS: Any
Status: New
Severi
