https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266145
rkober...@gmail.com changed:
What|Removed |Added
Status|In Progress |Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266145
Graham Perrin changed:
What|Removed |Added
Status|Open|In Progress
--
You are receiving
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266145
--- Comment #20 from commit-h...@freebsd.org ---
A commit in branch stable/13 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=567cc4e6bfd92d7351e385569f2bb4b7c89b6db0
commit 567cc4e6bfd92d7351e385569f2bb4b7c89b6db0
Author
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266145
--- Comment #19 from Ed Maste ---
cde70e312c3f should solve the problem as a workaround, but the underlying issue
likely needs new microcode or a new CPU. Once those are available we'll ask
folks to test the original code path (via the vm.p
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266145
Graham Perrin changed:
What|Removed |Added
Summary|[Intel Alder Lake] Crashes |Intel Alder Lake: crashes
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266145
--- Comment #18 from rkober...@gmail.com ---
After commit cde70e312c3fde5b37a29be1dacb7fde9a45b94a the issue seems to be
resolved. All cores running with pmap enabled for several hours.
While I can't claim that this is the final resolution
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266145
--- Comment #17 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=cde70e312c3fde5b37a29be1dacb7fde9a45b94a
commit cde70e312c3fde5b37a29be1dacb7fde9a45b94a
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266145
Graham Perrin changed:
What|Removed |Added
See Also||https://reviews.freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266145
--- Comment #16 from Konstantin Belousov ---
https://reviews.freebsd.org/D37770
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266145
--- Comment #15 from rkober...@gmail.com ---
(In reply to Amar Takhar from comment #14)
Sorry for the noise! The version I am running is from 2-Dec. I removed the
patched version on 9-Dec, so I am running the patched code.
I'll go re-instal
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266145
--- Comment #14 from Amar Takhar ---
(In reply to rkoberman from comment #13)
I don't think anything has been pushed regarding this. It's possible you've
been lucky. You sure you're running the unpatched version? How recent is it I
trie
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266145
--- Comment #13 from rkober...@gmail.com ---
I am now very confused. I thought that the patch had been committed and checked
out the latest sources. I've been running unpatched main for almost two weeks
with no problems with al 12 "cores" en
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266145
--- Comment #12 from Amar Takhar ---
(In reply to rkoberman from comment #11)
As far as I know nothing has landed yet in src for this. Just the patch that
appears to work so I wouldn't close this ticket just yet until something is
finalis
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266145
--- Comment #11 from rkober...@gmail.com ---
After over a month I have been running with all cores and PCID enabled with no
crashes on my Alder Lake. Is it time to call this "fixed"?
--
You are receiving this mail because:
You are the assi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266145
Graham Perrin changed:
What|Removed |Added
See Also||https://bugs.freebsd.org/bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266145
Graham Perrin changed:
What|Removed |Added
Status|New |Open
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266145
--- Comment #10 from rkober...@gmail.com ---
Can I assume that, with this patch, I should re-enable PCID?
Building new kernel now. Will report any issues I see.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266145
Konstantin Belousov changed:
What|Removed |Added
CC||k...@freebsd.org
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266145
--- Comment #8 from Amar Takhar ---
(In reply to rkoberman from comment #7)
Every crash I had was UFS/VFS as well. I still have all my coredumps. I'm
able to disable my E-cores via the BIOS which is what I have done the system
runs very
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266145
--- Comment #7 from rkober...@gmail.com ---
Small update on this. I ran the Alder Lake system on only the 2 P cores for at
least three days with no panics. I tried switch to only 8 E cores and the
system crashed again. I am back to P cores.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266145
--- Comment #6 from rkober...@gmail.com ---
(In reply to Amar Takhar from comment #5)
There are two unrelated issues causing the crashes. One is the UFS/VFS issue I
described in this ticket. It is distinct form the iwlwifi crash that only
oc
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266145
--- Comment #5 from Amar Takhar ---
(In reply to rkoberman from comment #4)
Yes I would believe that as the issues aren't always in VFS. Sometimes may
machine just reboots immediately. No dump just instantly reboots. There is
also the i
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266145
--- Comment #4 from rkober...@gmail.com ---
(In reply to Amar Takhar from comment #3)
I'm reasonably sure that it is not that it has a problem with the file system.
It's likely a race of some sort caused by the different performance of the
c
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266145
Amar Takhar changed:
What|Removed |Added
CC||v...@darkbeer.org
--- Comment #3 fro
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266145
rkober...@gmail.com changed:
What|Removed |Added
Severity|Affects Only Me |Affects Some People
--
You a
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266145
rkober...@gmail.com changed:
What|Removed |Added
Summary|[Intel Alder Lake] Crashes |[Intel Alder Lake] Crashes
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266145
--- Comment #2 from rkober...@gmail.com ---
I now have had a crash with soft updates disabled, s disabling them is not a
work around. It dos seem to significantly reduce the frequency of the crashes.
I am saving the vmcoore and core.txt file
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266145
--- Comment #1 from rkober...@gmail.com ---
After building over 200 ports today after disabling soft updates, no crashes.
While not complete proof, it looks pretty clear that the problem is in soft
updates. I still have a lot of ports to bui
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266145
Bug ID: 266145
Summary: [Intel Alder Lake] Crashes on CURRENT vfs/softupdate
Product: Base System
Version: CURRENT
Hardware: amd64
OS: Any
Status: New
29 matches
Mail list logo
