https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
tomasjerrii changed:
What|Removed |Added
CC||tomasjer...@gmail.com
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #294 from SF ---
Since 2017 i did find out that the cause of this seemed to be simply the
missing of an temperature sensor value: 60°C+ seemed to cause it to me.
My Ryzen could be surprisingly bug free since 2017, no need to
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
karthikbsd changed:
What|Removed |Added
CC||karthik.gan...@gmail.com
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
Armaan Mitchell changed:
What|Removed |Added
CC||nasreenbibi...@gmail.com
---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
Missa Jones changed:
What|Removed |Added
CC||alinamah...@gmail.com
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
Richard Zilinski changed:
What|Removed |Added
CC||armaangujja...@gmail.com
---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
jerometaylor changed:
What|Removed |Added
CC||romanmiller...@gmail.com
---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
Mubashra Ameen changed:
What|Removed |Added
CC||mubashraamee...@gmail.com
---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
John changed:
What|Removed |Added
CC||kabukimas...@gmail.com
--- Comment #287
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #286 from georgiadeeds ---
Every morning is a charming celebration of the new freedom that life has to
offer. If you are in a positive structure of mind and today yourself with a
strong approach in the morning than you are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
georgiadeeds changed:
What|Removed |Added
CC||georgiadee...@gmail.com
---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
Victor B. Kuntz changed:
What|Removed |Added
CC||saamhoc...@gmail.com
---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
Mark changed:
What|Removed |Added
CC||siyal7...@gmail.com
--- Comment #283 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
Atif Aslam changed:
What|Removed |Added
CC||isongsoundtr...@gmail.com
---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #281 from Sara Taylor ---
root@asbach:/var/crash/#kgdb7121 /boot/kernel/kernel /var/crash/vmcore.3
GNU gdb (GDB) 7.12.1 [GDB v7.12.1 for FreeBSD]
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #280 from Sara Taylor ---
root@asbach:/var/crash/#kgdb7121 /boot/kernel/kernel /var/crash/vmcore.3
GNU gdb (GDB) 7.12.1 [GDB v7.12.1 for FreeBSD]
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #279 from Sara Taylor ---
root@asbach:/var/crash/#kgdb7121 /boot/kernel/kernel /var/crash/vmcore.3
GNU gdb (GDB) 7.12.1 [GDB v7.12.1 for FreeBSD]
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #278 from Sara Taylor ---
root@asbach:/var/crash/#kgdb7121 /boot/kernel/kernel /var/crash/vmcore.3
GNU gdb (GDB) 7.12.1 [GDB v7.12.1 for FreeBSD]
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #277 from Sara Taylor ---
(In reply to Nils Beyer from comment #5)
when the crash happens the screen garbles a little bit, and after a while my
system reboots - please give me some more time to build a DDB-enabled kernel
and
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #276 from SF ---
Do you use ipfw? It's caused by ipfw, after removing some lines within ipfw it
doesn't crash anymore. There is some specific commands you shouldn't use.
e.x.:
don't use "ipfw table" commands
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
Sara Taylor changed:
What|Removed |Added
CC||dragongame...@gmail.com
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
vali gholami changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #273 from SF ---
I've read of people who fixed it by doing similiar things like you did, someone
printed himself an case for an aircooler with an 3d-printer to improve cooling
on his ryzen-motherboard.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #272 from rozhuk...@gmail.com ---
(In reply to Lars Viklund from comment #263)
I was have near issue with black screen/reboot after disk activity on asrock
taichi even with BristolRidge CPU. (Gamming X and AB350M Pro4 was not
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #271 from SF ---
I doubt you did truely ready any of my posts. All details are in there leading
to the conclusion that the powersupply of at least all low-budget mainboards up
to x370 chipset for
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #270 from Mark Millard ---
(In reply to SF from comment #269)
> Isn't it exactly what i sayed? The motherboard is causing this.
Assuming that is a reply to my comment 268:
It was just example evidence
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #269 from SF ---
Isn't it exactly what i sayed? The motherboard is causing this.
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #268 from Mark Millard ---
Just an FYI example about the hangups:
I'm aware of one example of someone with a
Ryzen 7 that was not having any of the hangup
problems until a BIOS update problem caused
a
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #267 from Mark Millard ---
(In reply to SF from comment #262)
> Will building of ghc stop if there is any error? I just put into an loop.
A ghc build will stop with something like a bus error
when it
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #266 from SF ---
Nvm, i quitted this bug a while ago because you people are weakminded out of my
view. The solution i told you is exactly the solution for all kinds of problems
people suffering so far, as
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #265 from Lars Viklund ---
(In reply to SF from comment #264)
Dear SF,
I've read every single comment in this bug, and as I say (if you read my
thread) I've tried adjusting settings both according to AMD's advice
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #264 from SF ---
No, read my recent posts. Thats the error i have with my machine, screen
turning off and only some stuff inside the pc running. I call it simply a
crash, whats happening during running
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #263 from Lars Viklund ---
Let me go on a tangent with my experience since April of Ryzen:
I've had both kinds of AMD problem with my Ryzen 1700 across two ASUS
motherboards, the PRIME B350M-A and the PRIME
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #262 from SF ---
Will building of ghc stop if there is any error? I just put into an loop.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #261 from SF ---
The difference between low budget moterboards and enthusiast-boards are the
switching frequency and better power-supply in general, the cheap bords only
have a low frequency and manually
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #260 from Don Lewis ---
(In reply to Mark Millard from comment #257)
I'm not convinced that the ghc problem is entirely a Ryzen hardware problem.
The first thing I did after I received my replacement CPU
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #259 from Don Lewis ---
(In reply to SF from comment #256)
Neither of my AM4 boards have a VRM frequency adjustment, and none of my large
collection of non-AM4 boards have it either. I think this feature
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #258 from Don Lewis ---
(In reply to Mark Millard from comment #255)
I never got panics. Instead, my machine would either blank the video (text
console, not running Xorg) and hang, or would silently
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #257 from Mark Millard ---
(In reply to SF from comment #256)
My guess is that "system crashed" in
"one system crashed and the other didn't" is
referring to panics and shutdowns but not
to individual
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #256 from SF ---
Noone of you did try changing the cpu-switching frequency and setting load line
balancing. I did try alot of stuff with cooling and all kinds of
power-settings, cooling was the first
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #255 from Mark Millard ---
(In reply to SF from comment #254)
Just reporting a distinct example. . .
The Ryzen 1800X system that I had access to
for a time had water-based cooling that kept
it under 47
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #254 from SF ---
Buy a better cooler, ensure your system stays below 60°C under all
circumstances. Watercooling should completely negate all your misbehavior like
previously sayed, everything i found out
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #253 from Don Lewis ---
(In reply to Nils Beyer from comment #248)
I finally had a chance to install my new CPU. Temperatures under load are
generally in the upper 40s as opposed to the lower 60s, but the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #252 from Don Lewis ---
(In reply to SF from comment #250)
This mega-thread https://community.amd.com/thread/215773?start=0=0 on
AMD Community Forum is full of Linux users who are experiencing random
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #251 from rozhuk...@gmail.com ---
Well, I try all that you describe:
- change power-supply
- decrease freq
- turn off boost
- tune LLC
- many other thing in different combinations
But I found that after I remove oil from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #250 from SF ---
While you were on the search for a softwarefault i found out was is causing it
months before and did finally find a solution. You didn't even try it, noone
did and i told it much more
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #249 from rozhuk...@gmail.com ---
(In reply to Nils Beyer from comment #247)
http://forum.ixbt.com/post.cgi?id=attach:9:68823:5110:1.jpg
(on photo my asrock taichi, and some sort of oil from thermal pad)
17A2 - some constant,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #248 from Nils Beyer ---
(In reply to Don Lewis from comment #246)
yes, temperature is around 51°C - 52°C under load. A couple of degrees cooler
than my old CPU...
--
You are receiving this mail because:
You
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #247 from Nils Beyer ---
(In reply to rozhuk.im from comment #245)
> What is your chipset date?
no idea.
> See after: 17A2.
what does "17A2" mean?
> Example:
>
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #246 from Don Lewis ---
(In reply to Nils Beyer from comment #240)
Does the CPU core temperature look OK?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #245 from rozhuk...@gmail.com ---
What is your chipset date?
See after: 17A2.
Example: http://www.pcdiy.com.tw/assets/images/768/8a89458610…8c293db902ab.jpeg
Mine:
X370 Taichi - 1629 - Freeze/reboot
AB350M Pro4 - 1649 - OK
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #244 from Don Lewis ---
My original CPU had a 1708SUT date code.
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #243 from Don Lewis ---
The shared page relocation (r321899 in HEAD) fixed the hanging/crashing problem
for me, but I still had the random SIGBUS/SIGSEGV problem when running parallel
compiles. I RMAed my
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #242 from Nils Beyer ---
(In reply to rozhuk.im from comment #241)
"UA 1730SUS"
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #241 from rozhuk...@gmail.com ---
(In reply to Nils Beyer from comment #240)
Is your CPU newer than 25 week?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #240 from Nils Beyer ---
(In reply to rozhuk.im from comment #239)
nope, still freezes with black screen and fans still running. Even without
having poudriere builds running. Haven't contacted AMD tech support
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #239 from rozhuk...@gmail.com ---
Any news?
Is ryzen work ok now?
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #238 from Nils Beyer ---
(In reply to Don Lewis from comment #237)
okay, just for fun I increased the dead zone of the user page:
--
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #237 from Don Lewis ---
(In reply to Nils Beyer from comment #236)
We now leave the boundary page unmapped, which is supposed to cure the problem
according to what AMD says. That's why the "program to
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #236 from Nils Beyer ---
(In reply to Don Lewis from comment #235)
> Yeah, I'd get in touch with AMD. I suspect that you'll have to go through
> some hardware troubleshooting again.
I haven't gotten any MCA
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #228 from Nils Beyer ---
(In reply to Nils Beyer from comment #225)
Froze again - black screen, fans still running...
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #235 from Don Lewis ---
You'll need the linux kmods for doing a full poudriere run I believe. The
lower bits really don't matter. The important thing is staying below
0x7000.
I think the only
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #233 from Don Lewis ---
(In reply to Nils Beyer from comment #232)
Yeah that should be ok. I get this:
8
-1 12 0x7fffe000 8
As long as the third value ends with fexxx then you have the shared page
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #231 from Nils Beyer ---
(In reply to Don Lewis from comment #229)
can only guess:
---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #229 from Don Lewis ---
(In reply to Nils Beyer from comment #228)
That really sounds like the share page problem ...
Do you know what was building at the time?
--
You are receiving this mail because:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #234 from Nils Beyer ---
(In reply to Don Lewis from comment #233)
"linux" and "linux64" modules are indeed loaded:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #232 from Nils Beyer ---
(In reply to Don Lewis from comment #230)
--
root@asbach:/home/nbe/#./sigtramp^M
8
-1 12 0x7fffe190 8
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #230 from Don Lewis ---
Created attachment 186143
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=186143=edit
program to print the address of the signal trampoline
Compile and run this program.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #227 from rozhuk...@gmail.com ---
(In reply to Nils Beyer from comment #226)
Now I use Bristol Ridge, it not affected by AGESA, IMHO.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #226 from Nils Beyer ---
(In reply to rozhuk.im from comment #224)
that's very strange. You're running AGESA 1.0.0.6b on the Fatal1ty, right? Do
you run that on the Taichi, too? The AB350M Pro4 and the AB350
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #225 from Nils Beyer ---
(In reply to Nils Beyer from comment #223)
well, it froze again - black screen, fans still running. But, because I cannot
remember whether I had that user page shift patch still active
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #224 from rozhuk...@gmail.com ---
I get money back for my Ryzen, and now looking for >1725 in local markets.
I try with A10-9700 on Taichi and get reboot on rsync upload 100gb file, just
like with ryzen.
A10-9700 on ASRock
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #222 from Don Lewis ---
(In reply to rozhuk.im from comment #221)
I have, works great.
It doesn't take into account the 20C offset on the 1x00X parts, so you'll have
to manually set the offset or remember
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #221 from rozhuk...@gmail.com ---
Offtop: can some one with Ryzen test amdtemp: https://reviews.freebsd.org/D9759
?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #220 from rozhuk...@gmail.com ---
The is some statistic that most problems happen with CPU manufactured before
week 26:
https://www.reddit.com/r/Amd/comments/6ubmd1/ryzen_compilation_segfaults_positive_rma/
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #219 from commit-h...@freebsd.org ---
A commit references this bug:
Author: truckman
Date: Wed Aug 16 07:59:58 UTC 2017
New revision: 322569
URL: https://svnweb.freebsd.org/changeset/base/322569
Log:
MFC r321899
Lower the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
Ed Maste changed:
What|Removed |Added
Status|New |Open
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #218 from Konstantin Belousov ---
(In reply to Don Lewis from comment #216)
This is a reference to FreeBSD-SA-12:04.sysret. We handle that by forcing
normal iret return path instead of the fast syscall
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #217 from Mark Millard ---
(In reply to Nils Beyer from comment #215)
Looking around the comment is newer than the definition
but the comment was added on: 2014-Nov-4. (Based on
"blame".)
By contrast the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #216 from Don Lewis ---
LOL ...
Prior to the fix in r321899, the top page of user memory for amd64 executables
was used by the shared page, the contents of which are controlled by the
kernel. This page
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #215 from Nils Beyer ---
(In reply to Don Lewis from comment #214)
documentation is the keyword, I don't know; I only have this:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #214 from Don Lewis ---
I'm not familiar enough with the Linux memory map to comment, but I haven't
seen any reports of hang/reboot problems that sound like what what we ran into.
There have been reports
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #213 from Nils Beyer ---
(In reply to Nils Beyer from comment #212)
more statements:
I'm new to this myself (I work on the GPU
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #212 from Nils Beyer ---
(In reply to Don Lewis from comment #204)
following claim came from a Linux user regarding freezes near the top memory
limit:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #211 from Don Lewis ---
(In reply to Nils Beyer from comment #210)
No. The kernel needs to be modified to move the shared page out of the way so
that the program can mmap() the top page of user memory.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #210 from Nils Beyer ---
(In reply to Don Lewis from comment #204)
Don, is it possible to modify your program so that it triggers that freeze on a
vanilla 11.1-RELEASE?
--
You are receiving this mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #209 from Nils Beyer ---
(In reply to Don Lewis from comment #208)
> It would also be interesting to see the results on non-Ryzen hardware.
done that on the mentioned Intel Xeon system. 11.1-RELEASE plus the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #208 from Don Lewis ---
The second WHERE 0x04fff000 is someleftover debug stuff from an earlier
version of the program that executed some more complicated code. I needed to
debug that code in a
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #207 from Nils Beyer ---
(In reply to Nils Beyer from comment #206)
answering myself: yes, maybe I should just listen to what Don said: I do need
that origin patch because without it the programm is not able
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #206 from Nils Beyer ---
(In reply to Nils Beyer from comment #205)
sorry, mass confusion in my brain; I accidentially executed that program on my
first Ryzen system with 32GB of RAM and your origin patch
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #205 from Nils Beyer ---
(In reply to Don Lewis from comment #204)
absolutely wonderful test case you've created - despite your instructions I've
run that program on a vanilla 11.1-RELEASE (no patches) on my
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #204 from Don Lewis ---
Created attachment 185022
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=185022=edit
program to cause Ryzen hang/reboot on tweaked FreeBSD by executing code in high
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #203 from Nils Beyer ---
(In reply to Don Lewis from comment #202)
> BTW, using either my origin workaround patch, or the committed version if the
> sv_maxuser adjustment is commented out, it is possible to
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #202 from Don Lewis ---
(In reply to Nils Beyer from comment #200)
I believe so. It's pretty unlikely that the problem is caused by undefined
opcodes, and we are not seeing any evidence (SIGILL) of valid
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #201 from Nils Beyer ---
(In reply to Nils Beyer from comment #200)
maybe the artificial intelligence inside the Ryzen is freaking out... I don't
know:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #200 from Nils Beyer ---
(In reply to Don Lewis from comment #198)
so, we're on the wrong track with "sandsifter" in order to find out what's
buggy in the CPU and how to possibly circumvent it, correct?
--
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #199 from Nils Beyer ---
(In reply to Nils Beyer from comment #197)
it's still running; as a side note: I cannot tell whether the overclocking is
really noticeable regarding compilation performance - I think
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #198 from Don Lewis ---
(In reply to rozhuk.im from comment #190)
The slide deck here:
https://github.com/xoreaxeaxeax/sandsifter/blob/master/references/domas_breaking_the_x86_isa.pdf
is pretty
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
Nils Beyer changed:
What|Removed |Added
See Also|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
Nils Beyer changed:
What|Removed |Added
Blocks||221029
Referenced
1 - 100 of 288 matches
Mail list logo