https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234733
--- Comment #19 from Conrad Meyer ---
(In reply to Conrad Meyer from comment #18)
> I am curious if Linux does any better. Maybe they just ignore c0010061.
Yeah they just ignore c0010061 entirely. Probably we can too.
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234733
--- Comment #18 from Conrad Meyer ---
(In reply to sigsys from comment #15)
> It would already be pretty good if the kernel could detect the situation by
> double checking on one of those registers and log a warning. Assuming it
> wouldn't
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243646
--- Comment #1 from Dirk Meyer ---
some Kernel modules removed:
FreeBSD netcom2.dinoex.sub.de 12.1-RELEASE-p1 FreeBSD 12.1-RELEASE-p1 r357113
GENERIC amd64
panic: bad pte va 118 pte f80081787bf8
GNU gdb 6.1.1 [FreeBSD]
Copyright
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243646
Bug ID: 243646
Summary: panic: bad pte va 966000 pte 0
Product: Base System
Version: 12.1-RELEASE
Hardware: amd64
OS: Any
Status: New
Severity: Affe
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234733
--- Comment #17 from commit-h...@freebsd.org ---
A commit references this bug:
Author: cem
Date: Mon Jan 27 06:04:33 UTC 2020
New revision: 357165
URL: https://svnweb.freebsd.org/changeset/base/357165
Log:
hwpstate(4): Log a debug line w
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234733
--- Comment #16 from sig...@gmail.com ---
Created attachment 211097
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=211097&action=edit
P3.50 acpidump -dt
Upgraded to 3.50 and I'm seeing the *exact* same behavior doing the same tes
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234733
--- Comment #15 from sig...@gmail.com ---
It would already be pretty good if the kernel could detect the situation by
double checking on one of those registers and log a warning. Assuming it
wouldn't risk causing even more problems on some
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234733
--- Comment #14 from Conrad Meyer ---
Sorry, not 3.90, only go to 3.50 maybe?
> ASRock do NOT recommend updating this BIOS if Pinnacle, Raven, Summit or
> Bristol Ridge CPU is being used on your system.
I don't have a clue why they'd rel
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234733
--- Comment #13 from Conrad Meyer ---
Note that there are several newer BIOSes available for that board:
https://www.asrock.com/mb/AMD/B450%20Pro4/#BIOS
The only remark that really jumps out is for 3.31, "Change AMD PBO rule with
Pinnacle
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234733
--- Comment #12 from Conrad Meyer ---
(It's also surprising that writing c0010062 *works* and overwrites c0010061 —
the docs for c0010062 say: "P-state limits are applied to any P-state requests
made through this register. Reads from this f
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234733
--- Comment #11 from Conrad Meyer ---
Very interesting, thanks! It's the low bits of 0xc0010061 following 0xc0010062
up that is surprising / causing hwpstate(4) to ignore the user's supplied
configuration (side note: we should really produ
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234733
--- Comment #10 from sig...@gmail.com ---
(In reply to Conrad Meyer from comment #9)
It's showing some interesting behavior I think. The last 3 bits of 0xc0010061
and 0xc0010062 go up but don't go down. And they go up together.
At boot:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234733
--- Comment #9 from Conrad Meyer ---
Another test to try (maybe after entering a non-P0 p-state, not sure if that
matters) if you'd like:
$ cpucontrol -m '0xc0010061' /dev/cpuctl0
This is the PStateCurLim register, and the low 3 bits are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243640
Bug ID: 243640
Summary: QEMU / KVM Q35 V4.X PCIe Virtual and Physical
(Passthrough) Devices not detected
Product: Base System
Version: 12.1-STABLE
Hardware: amd64
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241079
free...@diyit.org changed:
What|Removed |Added
CC||free...@diyit.org
--- Comment #
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243638
Bug ID: 243638
Summary: panic: worklist_remove: mkdir(0x29) not on list
Product: Base System
Version: 12.1-RELEASE
Hardware: amd64
OS: Any
Status: New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234031
--- Comment #38 from Adam ---
Created attachment 211089
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=211089&action=edit
bootloader debug
I managed to build the boot loader with DISC_DEBUG and SIO and captured the
output via se
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202650
p5b2e9...@t-online.de changed:
What|Removed |Added
Status|New |Closed
Resolution|-
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243620
Conrad Meyer changed:
What|Removed |Added
Summary|Panic / LOR while rebooting |UFS softdep Panic while
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243620
--- Comment #2 from Gordon Bergling ---
I happens within
(ufs) sys/kern/vfs_mount.c:1606
(syncer) sys/kern/vfs_subr.c:3199
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243620
--- Comment #1 from Gordon Bergling ---
Created attachment 211069
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=211069&action=edit
-CURRENT Panic
--
You are receiving this mail because:
You are the assignee for the bug.
__
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243620
Bug ID: 243620
Summary: Panic / LOR while rebooting
Product: Base System
Version: CURRENT
Hardware: Any
OS: Any
Status: New
Severity: Affects Many P
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243249
--- Comment #3 from Jason W. Bacon ---
I should have an 11.3 install running shortly.
What specific info should I provide?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242350
Takahashi Yoshihiro changed:
What|Removed |Added
Resolution|--- |FIXED
CC|
24 matches
Mail list logo
