[Bug 260868] possible i386 regression after ce35a3bc852d25cb989bc1f3dc4ddb723d7d5117
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 260868] possible i386 regression after ce35a3bc852d25cb989bc1f3dc4ddb723d7d5117"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 260868] possible i386 regression after ce35a3bc852d25cb989bc1f3dc4ddb723d7d5117"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 260868] possible i386 regression after ce35a3bc852d25cb989bc1f3dc4ddb723d7d5117"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 260868] possible i386 regression after ce35a3bc852d25cb989bc1f3dc4ddb723d7d5117"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 260868] possible i386 regression after ce35a3bc852d25cb989bc1f3dc4ddb723d7d5117"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 260868] possible i386 regression after ce35a3bc852d25cb989bc1f3dc4ddb723d7d5117"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 260868] possible i386 regression after ce35a3bc852d25cb989bc1f3dc4ddb723d7d5117"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 260868] possible i386 regression after ce35a3bc852d25cb989bc1f3dc4ddb723d7d5117"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 260868] possible i386 regression after ce35a3bc852d25cb989bc1f3dc4ddb723d7d5117"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 260868] possible i386 regression after ce35a3bc852d25cb989bc1f3dc4ddb723d7d5117"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 260868] possible i386 regression after ce35a3bc852d25cb989bc1f3dc4ddb723d7d5117"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 260868] possible i386 regression after ce35a3bc852d25cb989bc1f3dc4ddb723d7d5117"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 260868] possible i386 regression after ce35a3bc852d25cb989bc1f3dc4ddb723d7d5117"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 260868] possible i386 regression after ce35a3bc852d25cb989bc1f3dc4ddb723d7d5117"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Sat, 01 Jan 2022 21:06:39 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260868
Bug ID: 260868
Summary: possible i386 regression after
ce35a3bc852d25cb989bc1f3dc4ddb723d7d5117
Product: Base System
Version: 13.0-STABLE
Hardware: Any
OS: Any
Status: New
Keywords: regression
Severity: Affects Only Me
Priority: ---
Component: kern
Assignee: bugs@FreeBSD.org
Reporter: mike@sentex.net
Created attachment 230609
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=230609&action=edit
sysctl -A | grep -i timer and dmesg for working and non working images
For some deployments, we are still using some legacy PC Engine's Alix devices.
These are GEODE processors, running i386 FreeBSD 13. I noticed on a latest
build as of Jan 1, boot times because impossibly slow (approx 10x times the
normal amount to boot) and I cant seem to run the watchdog with an interval
below 10 seconds as it does not get processed fast enough.
If I rewind to a commit just prior to
https://cgit.freebsd.org/src/commit/?h=stable/13&id=1e40acb545391169b8e13fd27724e3699d6824c3
all works as normal
Also seemingly related is that I had been using a kernel definition that did
not include SMP nor APIC. If I checkout to
1a305490732cdd30d19627b49847ebe09009a8f7
I can no longer compile said kernel as it fails with
--- vers.c ---
MAKE="make" sh /usr/src/sys/conf/newvers.sh ALIX_DSK
--- vers.o ---
cc -target i386-unknown-freebsd13.0
--sysroot=/usr/obj/nanobsd.alix2b/usr/src/i386.i386/tmp
-B/usr/obj/nanobsd.alix2b/usr/src/i386.i386/tmp/usr/bin -c -O2 -pipe
-fno-strict-aliasing -nostdinc -I. -I/usr/src/sys
-I/usr/src/sys/contrib/ck/include -I/usr/src/sys/contrib/libfdt -D_KERNEL
-DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common
-fdebug-prefix-map=./machine=/usr/src/sys/i386/include
-fdebug-prefix-map=./x86=/usr/src/sys/x86/include -mno-mmx -mno-sse
-msoft-float -ffreestanding -fwrapv -fstack-protector -Wall -Wredundant-decls
-Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith
-Wcast-qual -Wundef -Wno-pointer-sign -D__printf__=__freebsd_kprintf__
-Wmissing-include-dirs -fdiagnostics-show-option -Wno-unknown-pragmas
-Wno-error=tautological-compare -Wno-error=empty-body
-Wno-error=parentheses-equality -Wno-error=unused-function
-Wno-error=pointer-sign -Wno-error=shift-negative-value
-Wno-address-of-packed-member -Wno-error=unused-but-set-variable
-Wno-format-zero-length -mno-aes -mno-avx -std=iso9899:1999 -Werror vers.c
ctfconvert -L VERSION vers.o
ERROR: ctfconvert: vers.o doesn't have type data to convert
--- kernel ---
linking kernel
ld: error: undefined symbol: apic_ops
>>> referenced by clock.c
>>> clock.o:(cpu_initclocks)
*** [kernel] Error code 1
make[2]: stopped in /usr/obj/nanobsd.alix2b/usr/src/i386.i386/sys/alix
1 error
make[2]: stopped in /usr/obj/nanobsd.alix2b/usr/src/i386.i386/sys/alix
make[1]: stopped in /usr/src
make: stopped in /usr/src
Adding in
device apic
to the kernel config allows me to compile, but the resultant kernel is dead
slow / unusable.
Attached is a working and non working dmesg and output of sysctl -A | grep time
(in case that helps)
--
You are receiving this mail because:
You are the assignee for the bug.