I was able to capture a soft-lock with sysrq-l [1]. Networking and mouse
were still functional, but focusing windows and window activity in
Plasma were locked.
https://gist.github.com/rphillips/fae9540a8e7a3a83731c9a9809a98df4
Notes:
* AMD Ryzen 2700X
* SuperNOVA 650 G3 650W (Eco switch set to
I'm praying intensely that the new AMD Epyc 3000 Embedded series (low
power e3000) don't have the same issues. Hoping to buy one in the next
few months when they finally put the damn things on some ITX boards.
--
You received this bug notification because you are a member of Kernel
Packages,
(In reply to OptionalRealName from comment #375)
> Thread still ongoing with no response from AMD.
>
> Really shouldn't need to fiddle with custom bios options.
>
> What is big business / big iron or whatever it's called doing with Epyc and
> linux servers? Are those totally fine?
I am running
Thread still ongoing with no response from AMD.
Really shouldn't need to fiddle with custom bios options.
What is big business / big iron or whatever it's called doing with Epyc
and linux servers? Are those totally fine?
--
You received this bug notification because you are a member of Kernel
I have a Ryzen 1800X + Gigabyte GA-AX370-Gaming K7.
I was suffering from these hangs until I changed a few settings in my BIOS. The
change that made the difference was the Power Supply Iddle Control that was
added in the latest BIOS update. All other settings are left by default:
M.I.T->
Hey, guys
We have been seeing this smp function call soft lockup since 3.x kernel.
Unfortunately we don't know how to reproduce it either.
I suspect there is something on other CPU (not shown without sysrq-l)
blocking the smp call function execution, we have to figure out what it
is. So next
(In reply to Artem Hluvchynskyi from comment #366)
> So AMD has finally published the revision guide for 17h family, which
> includes errata:
> https://developer.amd.com/wp-content/resources/55449_1.12.pdf
>
> Would be cool if someone with more knowledge about that kind of stuff could
> have a
Hello James, does this issue already fixed? If not, do we have other
sources sources that might help this to be fixed? Thank you!
Carlo B.
https://ultimatewebtraffic.com/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
(In reply to James Le Cuirot from comment #368)
> I remember seeing the kernel fix/workaround for that issue when I was trying
> to diagnose our issue. I don't think they are related.
https://www.phoronix.com/scan.php?page=news_item=Linux-4.17-AMD-
Power-Fix
But don't know if it's the same MWAIT
(In reply to Artem Hluvchynskyi from comment #366)
> So far "1109 MWAIT Instruction May Hang a Thread" sounds somewhat related.
I remember seeing the kernel fix/workaround for that issue when I was
trying to diagnose our issue. I don't think they are related.
--
You received this bug
@James Le Cuirot:
Linux 4.14 already came with the mentioned patch from beginning and doesn't
prevent freezing on idle at all - same as the MWAIT-patch mentioned at Phoronix
(see link above).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
I was thinking of this but with fresh eyes, maybe that is yet another
issue. I'll shut up now and leave this to the experts. :)
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=88d879d29f9cc0de2d930b584285638cdada6625
--
You received this bug notification because
(In reply to Artem Hluvchynskyi from comment #366)
> So AMD has finally published the revision guide for 17h family, which
> includes errata:
> https://developer.amd.com/wp-content/resources/55449_1.12.pdf
>
> Would be cool if someone with more knowledge about that kind of stuff could
> have a
So AMD has finally published the revision guide for 17h family, which includes
errata:
https://developer.amd.com/wp-content/resources/55449_1.12.pdf
Would be cool if someone with more knowledge about that kind of stuff
could have a quick look through and see if this issue could be related
to
Hi, a follow up. My two Threadripper machines are working flawlessly
since Friday. I tried both, running a test that alternates between high
load and idle that would normally trigger the but, and leave the machine
idle for many hours.
It seems like a possible workaround for someone with a ASUS
Oh, and I forgot to mention. Both machines are using the "Overclocking
Enhancement" options and I have explicitly set c6 state to enabled using
zenstates.py.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
@Eduardo. Yes I've found that option before. It is disabled by default
(so the default is not to try the power saving). I even tried to enable
hoping that the power saving system would be smart and avoid the lock up
but it didn't work.
What I am trying right now is to set the option "Overclocking
On 2018-06-14 09:10 AM, bugzilla-dae...@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=196683
>
> --- Comment #359 from Ryan Phillips (r...@trolocsis.com) ---
> Eco mode supposedly only controls the PSU fan. I'm guessing that will not
> change anything on the CPU soft
@Ryan, yes. Acoording to dmidecode I am using 0601 BIOS that is the last
one available in Asus website.
Interesting that you are having soft lockups even with Typical Current.
It completely solved the problems in my old 1700X system and it seems to
have worked well for others. Are you
@Paulo:
I downloaded the manual for your motherboard and found this
http://dlcdnet.asus.com/pub/ASUS/mb/socketTR4/PRIME_X399-A/E13557_PRIME_X399-A_BIOS_EM_WEB_20171030.pdf
EPU Power Saving Mode
The ASUS EPU (Energy Processing Unit) sets the CPU in its minimum power
consumption
settings.
@Paulo: Are you running the latest bios? There is a newer bios from
~April or so, but I do not have the motherboard to try it out.
To add some more information to this thread, I have the following
machine:
* AMD Ryzen 2700X
* SuperNOVA 650 G3 650W (Eco switch set to On)
* Asus ROG Crosshair
Eco mode supposedly only controls the PSU fan. I'm guessing that will
not change anything on the CPU soft lock side.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1690085
Title:
Ryzen
I would like just to pass some evidence that this affects Threadrippers.
I have two identical system with the 1950X on a Asus X399-A Prime
motherboard. This motherboard does not have the Power Supply option in
the BIOS. Both freeze from time to time.
But more interesting, both systems freeze when
How did I made my system ultra stable after months of despair ?
Easy, I never let it idle anymore :p
Mining crypto money on at least some of the core and I never
had trouble again :)
Le 09/06/2018 à 16:28, bugzilla-dae...@bugzilla.kernel.org a écrit :
>
> I find myself willing to believe the AMD "indirectly" statement: this is
> related to power supply. My power supply is an EVGA 650GQ, with eco switch
> set on to reduce fan noise. I suspect that if I swapped it for some other
Some want to believe and that's fine but AMD story is and always was
On 2018-06-09 07:33 AM, bugzilla-dae...@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=196683
>
> --- Comment #352 from Kai-Heng Feng (kai.heng.f...@canonical.com) ---
> Is there anyone not affected by this when Package C6 is enabled?
> Otherwise I intent to send the
The microcode updates AMD had announced https://www.amd.com/en/corporate
/security-updates are going to be availble to AMD customers "by
downloading BIOS updates provided by PC and server manufacturers and
motherboard providers" are now actually available as separate microcode
packages which can
I haven't noticed any of the issues identified in this ticket since I
upgraded to 18.04 LTS.
The stock 4.15.x kernel doesn't have RCU_NOCBS enabled from what I can
tell.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I compiled (from a make oldconfig) 4.13.16 w/ CONFIG_RCU_NOCB_CPU=y and
rcu_nocbs=0-15 as a boot parameter. I've been almost 60 hours, which is
a first since buying this machine.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
What this very bug report is about is a little blurry since the focus
changed into different directions over time.
It is my understanding that
https://bugzilla.kernel.org/show_bug.cgi?id=196683 is a hardware
(design) bug, which is not going to be fixed (and could not be fixed or
properly
These symptoms definitely still happen to me on 18.04 w/
4.15.0-22-generic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1690085
Title:
Ryzen 1800X freeze - rcu_sched detected stalls
According at least to http://blog.programster.org/stabilizing-
ubuntu-16-04-on-ryzen, 18.04 is supposed to be ok. I haven't upgraded
yet myself.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Is it known if 18.04 has the patches active to support ryzen out of the
box? I have upgraded to 18.04 recently and the system has just hung for
the first time in many months. I wonder if this is by chance or if other
people experienced the same?
--
You received this bug notification because you
I had the same issues this bug describes: Freeze on low load; Runs fine
on heavy load. I even ran stress -c 16 when I had to keep the system up
for long periods of low load.
I tried pretty much everything in this list including compiling a
mainline kernel with CONFIG_RCU_NOCB_CPU enabled and the
Been following this thread along with
https://bugzilla.kernel.org/show_bug.cgi?id=196683. To help us aggregate
data and look for patterns, I created a google form:
https://goo.gl/forms/oGCTPnNK0vJtNntj2
Message me if you want to be a collaborator on it, and also please share
feedback. Goal is to
Opened the new bug at
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1747463
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1690085
Title:
Ryzen 1800X freeze - rcu_sched detected
> On 5 Feb 2018, at 7:21 PM, Peridot <1690...@bugs.launchpad.net> wrote:
>
> This is still an issue even with the bionic dailies. The easiest way
> (read: without recompiling kernels) I have found to get it to work is to
> disable IOMMU in your BIOS and add "iommu=soft" to the kernel booting
>
This is still an issue even with the bionic dailies. The easiest way
(read: without recompiling kernels) I have found to get it to work is to
disable IOMMU in your BIOS and add "iommu=soft" to the kernel booting
options in grub.
linux can then detect everything properly (all cores) and I've had
CPU: Ryzen Threadripper 1920X
Ubuntu 16.04 LTS
Identical problems to the above. Agonizing, irritating, random, low-load
idle-state freezes. No issues while under heavy load.
My fixes:
Disabled c-states in the BIOS
Disabled ASLR in the BIOS
Disabled AMD Cool 'n Quiet in the BIOS.
Compiled a
@tomreyn
My corrent config to get stability
C6 disabled in BIOS
ALSR disabled
kernel >= 4.14.4 with CONFIG_RCU_NOCB_CPU
rcu_nocbs=0-15 processor.max_cstate=1 in GRUB_CMDLINE_LINUX
I got lockups still with ASLR disabled and rcu_nocbs with the custom
built kernel, once I added C6 disabled in bios
So, to sum up, we have several reports here that Ubuntu's default
kernels freeze on low load situations with Ryzen CPUs (or a subset of
Ryzen CPUs?) up to and including the latest mainline releases. This bug
differs from bugzilla.kernel.org #196481 (user space segfaults only on
high CPU load).
Link to correct upstream bug report
** Changed in: linux
Remote watch: Linux Kernel Bug Tracker #196481 => Linux Kernel Bug Tracker
#196683
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Ok, after updating to the latest BIOS the issue seems resolved for me.
I'm now also at an uptime of over 3 weeks, and before I could never get
past 1 week. I've updated the BIOS of my ASRock AB350 Pro4 AMD B350 to
3.20 with AGESA 1.0.0.6b.
I am currently running kernel 4.14.5 with
Just to be clear my mainline kernel is configured with
CONFIG_RCU_NOCB_CPU to yes.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1690085
Title:
Ryzen 1800X freeze - rcu_sched detected
Well I've now hit 3 weeks of uptime with C6 disabled in the BIOS and
GRUB_CMDLINE_LINUX_DEFAULT="rcu_nocbs=0-15 processor.max_cstate=1"
and 4.14.6 built from the mainline kernel repo. At this point I'm
satisfied that for me at least my Ryzen is now stable.
--
You received this bug notification
I experienced the same issue with Ryzen 5 1600 and Ryzen 7 1700, with AsRock
AB350M PRO4 and Asus Prime B350M-A.
I try with ubuntu 16.04 normal and hwe kernel, and ubuntu 17.10.
On the system with Asus motherboard, I found a detailed log:
Dec 19 06:25:04 am02 kernel: [227622.995187] NMI
well another lock up. I've now disabled C6 in the bios and added
max_cstates=1 to the boot parameters
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1690085
Title:
Ryzen 1800X freeze -
Well another watchdog failure with 4.14.5
I also updated to AGESA 1.0.0.6B when I rebooted to 4.14.5.
Just building a 4.14.6 to try again.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
We are experiencing the same behaviour and error messages with a Ryzen5
1600 CPU and an ASUS PRIME A320M-K motherboard.
What we can add is:
1. When no VMs are running, even if there are long idle periods, the machines
can be stable for several days on Ubuntu 16.04.3 using the HWE Kernel 4.10.
After 5 days uptime with my custom ubuntu kernel build I got a different
crash with a reboot vs the watchdog error. I'm now running a mainline
kernel 4.14.3 with ASLR disabled and rcu_nocbs=0-15 and have restarted
my no crash counter.
--
You received this bug notification because you are a
~emmenlau: Try setting up a serial console to or netconsole from this
system to get a better idea of why / how it's freezing.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1690085
Title:
I think its very very unlikely to have a different underlying cause, even
though I there is no guarantee. I assume that I am affected by the same problem
because:
(1) The problem manifests identical to other reports here
(2) The freeze happens particularly during idle times, not under heavy load
It could be something else then ? After applying the fix on several
machines, I have no freezes to report, more than 1 month of uptime, it
looks rock stable. Did you also disable ASLR ? Also I compiled a kernel
from git.kernel.org as suggested in the tutorial, not Ubuntu Kernel.
--
You received
Its great that the frequency of freezes is reduced. But I guess many people
here expect a stable
system and can work with nothing less. Ryzen-Processors are attractive for
CI-systems, and I can
not have regular freezes in our CI. I think this is an all-or-nothing-issue,
and I still had a
freeze
Well I've hit 48 hours uptime since booting to my custom build kernel
(Linux ganymede 4.13.0-17-generic #20+ryzen SMP Sun Dec 3 20:18:51 MST
2017 x86_64 x86_64 x86_64 GNU/Linux) with rcu_nocbs=0-15 in my boot
command and disabled ASLR. That's about double my previous uptime
record, I'll report
** Tags removed: kernel-da-key
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1690085
Title:
Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks
Status in Linux:
Unknown
The workaround discussed at http://blog.programster.org/ubuntu-16-04
-compile-custom-kernel-for-ryzen fixes the recurring (roughly once or
twice in 6 hours of operation, during low or idle CPU load periods)
system freezes for this Ryzen 7 1800X (early weeks), AMD microcode
0x8001129, ASRock X370
Yep I did :) thanks
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1690085
Title:
Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks
Status in Linux:
Unknown
Status in
If you rely on the boot option "rcu_nocbs=0-15" you also need to reboot
to enable it.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1690085
Title:
Ryzen 1800X freeze - rcu_sched
Cool Thanks for the confirmation Franck I've rebuilt 4.13.0-17 with
instructions from here https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel
(Probably similarly to Mario). I'm going to test it with this first
(since don't really want to reboot again). But might get stuff ready
with a 4.14.3
No "processor.max_cstate=1" is not necessary. I'd also suggest to double
check that your motherboard bios is up to date. If it persists I'd try
with a more recent kernel (I'm using 13.6) because IIRC the rcu options
where a little bit different in earlier versions of 4.13.
--
You received this
I have compiled the current Ubuntu 17.10 kernel 4.13.0-17-generic with
CONFIG_RCU_NOCB_CPU
and boot option "rcu_nocbs=0-15" and just had a system freeze again. My System
is a Ryzen 7 1700X
on an ASrock AB350 Pro4 mainboard with 32GB Ram @3200.
I do not use the kernel option
YES the boot option alone has no effect, you must also compile the
kernel with CONFIG_RCU_NOCB_CPU. You should be fine now (I have this
confirmed on several different configs). Here's a tutorial:
http://blog.programster.org/ubuntu-16-04-compile-custom-kernel-for-ryzen
--
You received this bug
@franckc did you have to rebuild your kernel? I tried the kernel
options without that and still had failures. I've just rebuilt with
CONFIG_RCU_NOCB_CPU to see if now the rcu_nocbs=0-15 resolves my lockups
--
You received this bug notification because you are a member of Kernel
Packages, which
Almost 1 month of uptime, it looks solved.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1690085
Title:
Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks
Status in Linux:
I've added "rcu_nocbs=0-15" to the kernel boot parameters this morning
(along with "processor.max_cstate=1" last week), will update if a new
freeze occurs.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
PLEASE post your concerns to this kernel.org thread with this issue!
https://bugzilla.kernel.org/show_bug.cgi?id=196683
CONFIG_RCU_NOCB_CPU_ALL kernel option was removed and would likely fix
this issue if put back! Supposedly there is a kernel command param you
can pass to alleviate some of
Franck: I very much agree that its not related to what you linked. The
link you refer to deals with heavy load compilation segfaults, which is
addressed with a RMAd CPU.
This thread seems to be mostly centered around system idle / low usage
complete system crash. No logs, blank screen.
I have a
More details.
- latest agesa
- disabled nouveau
- disabled randomized mem
- upped SOC voltage
- disabled C-states / cool-n-quiet
- using kernel 4.13.4 with RCU changes made, though only CONFIG_RCU_NOCB_CPU
was available in 4.13.4
I'm open to trying other kernels if requested.
--
You received
It seems that this problem is widespread, and is not related to
https://bugzilla.kernel.org/show_bug.cgi?id=196481 which is linked in
this thread.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
My 1700 is week 33 as well.
https://photos.app.goo.gl/HNwpPJqI85sZU4VU2
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1690085
Title:
Ryzen 1800X freeze - rcu_sched detected stalls on
I can confirm the issue with a week 33 Ryzen 1700 on Asus Prime B350 Plus.
I had segfaults with my previous 1700 (week 22 iirc). No more segfaults with
the week 33 CPU but still random crashes on (long time) idle.
--
You received this bug notification because you are a member of Kernel
Ryzen CPUs manufactured before week 24 of this year were known to have
issues (especially the segfault issue). It was officially fixed for all
ryzen manufactured after week 30. All my ryzen are pre-24 CPUs and they
all have this silent crash issue. Does it also happen with the post week
30 ryzen ?
I too still have random computer shutdowns without logs. Uptime varies
from a couple days to a week or so. It happens it seems after being
relatively idle for a long period. I do have high memory usage because
of the VMs I run.
I've disabled C-states, cool and quiet, tested memory, and so forth.
Hi,
I'm getting the same issues on several identical builds, with an ASUS prime
X370-PRO motherboard.
It's very hard to analyze since it happens randomly every other week, and it
leaves no logs. It seems that the freeze happens at idle after very high memory
load (observation after logging CPU
Stuart,
Does this issue also happen on latest mainline kernel?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1690085
Title:
Ryzen 1800X freeze - rcu_sched detected stalls on
I finally managed to figure out how to compile a kernel with RCU_NOCB
and disabled ASLR as Alex Jones mentioned, and it appears to have worked
for me and another guy who helped me put the tutorial together:
http://blog.programster.org/ubuntu-16-04-compile-custom-kernel-for-ryzen
--
You received
Hi guys,
Im getting the same issues, brand new build.
Ryzen 1800x
Asrock X370 Taichi
BIOS: 3.10 (latest)
I tried disabling cool n quiet and c-state
However there is another option under advanced - for GLOBAL C-States
that i just disabled today and i am waiting to see what will happen.
On BIOS
Just wanting to report that I am also experiencing this issue with a
freshly installed Ubuntu Server 16.04.3 with 4.10 kernel on the 22nd
August 2017. All the updates applied and running as a KVM host with
hardware:
Ryzen 1700 (non-x)
Motherboard: Asus prime B350-Plus
Bios: - Version 0805
-
Ok, this trick did not help and my PC did not make it through the night
without freezing again.
However I finally found the real problem. I installed oibaf a while back
as my Kubuntu was flickering all over the place. Now it seems the be the
source of my problem. I deinstalled oibaf again and now
I've ran into this problem several times. After disabling C-states in
the motherboard, my system has been running stable for ~5 weeks uptime
so far.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I also experience this problem since I updated yesterday.
I am using Kubuntu 16.04 with KDE backports enabled.
I also have a Ryzen 1800X and an Asrock X370 Gaming professional
I experience this either when I boot and don't log in promptly or when I
enter the lockscreen.
After reading this page
This is beyond my expertise - let's see what upstream can do.
** Bug watch added: Linux Kernel Bug Tracker #196481
https://bugzilla.kernel.org/show_bug.cgi?id=196481
** Also affects: linux via
https://bugzilla.kernel.org/show_bug.cgi?id=196481
Importance: Unknown
Status: Unknown
If the motherboard allows it, disabling the OpCache will completely
prevent (or at least greatly reduce the probability of) the ASLR-related
crash, even if ASLR is enabled in the kernel. As far as I'm aware it has
no effect on the other type of crash.
--
You received this bug notification
I've also determined that changing the CPU, memory, or SOC voltages or
timings has little or no effect on either type of crash.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1690085
This is the DragonFlyBSD commit.
https://gitweb.dragonflybsd.org/dragonfly.git/commitdiff/b48dd28447fc8ef62fbc963accd301557fd9ac20
It appears that there are two different ways that the system can crash,
which is why it is necessary to both disable ASLR and to compile the
kernel with
Alex,
Can you provide link on how DragonflyBSD fixed this issue?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1690085
Title:
Ryzen 1800X freeze - rcu_sched detected stalls on
If any of your RAM timings are odd (eg. 17), setting them to the next
even number (eg. 18) helps a lot. Recompiling the kernel with
CONFIG_RCU_NOCB_CPU and CONFIG_RCU_NOCB_CPU_ALL, and disabling ASLR is
still necessary though. It may also be a good idea to give the SOC
slightly more voltage, but
I just tested 1.0.0.6a AGESA, and it does not solve this issue. In some
cases just one program will crash, and in other cases the entire system
will crash. I will test the workaround above later.
--
You received this bug notification because you are a member of Kernel
Packages, which is
AMD has not publicly commented on this issue that I'm aware of. This
issue has been seen on many different operating systems. DragonFlyBSD
includes a workaround for this issue. The workaround on Linux is to
compile the kernel with CONFIG_RCU_NOCB_CPU, CONFIG_RCU_NOCB_CPU_ALL,
and disable ASLR
Was this issue officially confirmed to be a hardware bug in Ryzen processors by
AMD?
If so, could you provide a link to the statement?
Disabling address space layout randomization (ASLR) seems to alleviate
the problem, but does it solve it?
I am investigating unstable behavior under load which
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Tags added: artful
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1690085
Title:
Ryzen
Reopening because even though this is a known issue with the CPU we
could still implement a workaround. One workaround is to disable address
space layout randomization:
echo 0 >/proc/sys/kernel/randomize_va_space
However, that would be disabling a security feature.
** Changed in: linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1690085
Title:
Ryzen 1800X freeze - rcu_sched detected stalls on
This is a hardware bug in the CPU. This ticket should be closed as
invalid.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1690085
Title:
Ryzen 1800X freeze - rcu_sched detected stalls
I'm seeing this crash even with the Nvidia official driver.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1690085
Title:
Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks
Hi Vincent,
> camparijet => did you installed NVIDIA driver instead ?
No. I don't have to use the card for my purpose, so simply i disable it.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hi,
5 days update now and no crash.
camparijet => did you installed NVIDIA driver instead ?
Regards,
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1690085
Title:
Ryzen 1800X
Hi Vincent,
I also met the problem, and your advice removing "nouveau" succeeded for
work-around to stabilize system. Before it freeze every 3-5hr after
booting up, but now working without problem for 2 days.
My enviroment is:
- cpu: Ryzen 1700
- motherboard: ASUS B350M-A
- graphics card: NVIDIA
Hi,
It looks like that the system is stable when removing "nouveau" driver.
Waiting 24/48h and will post again.
Regards,
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1690085
Title:
401 - 500 of 513 matches
Mail list logo
