[Bug 1690085]
I am still receiving lockups even with the latest BIOS, all the BIOS setting recommendations here, and with the idle=halt kernel parameter. Although I am now fairly certain that I have a faulty motherboard (x470) which seems to be getting worse, and sometimes doesn't even get to the BIOS at all (I should have suspected something was up when I first bought it and the PS/2 port didn't work). I'm going to try replacing it and hopefully that'll help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1690085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690085]
(In reply to Philip Rosvall from comment #541) > Try idle=halt! It is the workaround that fixes the random freezes! You don't > need anything else (at least not with Ryzen 1*** and 2***U processors, as it > works wonders on my desktop with a 1600 and my notebook with a 2700U). > > IDLE=HALT IS THE WORKAROUND THAT FIXES THIS BULLSHIT! > I REPEAT: > IDLE=HALT! > > It will probably work for most of you too! In light of the last few comments here I can say that I may have been confusing 2 separate issues: The random segfaults and the lockups. I tested idle=halt a while back and I may have inadvertently concluded that it didn't work due to my machine still receiving segfaults, which I was assuming would eventually lead to a lockup. Likewise, the solution I mentioned earlier (disabling PAGE_TABLE_ISOLATION) seems to have fixed my crashes, but my machine just locked up. I've set idle=halt again and this time I'll try to keep the two issues separate and only post back here if I still receive lockups. Thanks for clarifying the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1690085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690085]
I have tested it on 5.0 and still experienced the soft lockups just as frequently as with 4.20. However, I am currently testing kernel 5.0 with PAGE_TABLE_ISOLATION disabled and it seems that it may be a fix. Although maybe it's a bit premature to say that, since my experience with this issue (on 2700X) has been extremely inconsistent. I get the soft lockups, but in addition to the lockups (and usually preceding them) it seems like my whole system becomes unstable. Applications start segfaulting, or turning into zombies that can't be killed, then the lockup happens if I just let it go. What's strange is that once this sort of "instability" occurs it seems to stay unstable even across reboots, and I can only have my machine running 20-30min before things start segfaulting or locking up again. Usually it takes me about 5 or 6 restarts before it just seems to hit some sweet spot and become "stable". Once it's stable it stays stable for days, even if I restart the machine. So based on the above description I can see that narrowing down the problem could be very difficult since something might seem to be working for a while, until it doesn't. At any rate, the solution I'm currently testing was proposed in this Gentoo thread: https://forums.gentoo.org/viewtopic-t-1074860-start-0.html which I stumbled upon after receiving a kernel panic and noticing this error >Unexpected reschedule of offline CPU#0! >From what I can tell "offline CPU" sounds very relevant to our issue. Their solution was to disable PAGE_TABLE_ISOLATION in the kernel. This also intrigues me as I remember seeing other errors in dmesg relating to "page" writing. Apparently that kernel option isn't even necessary for AMD CPU's anyway. It was meant to fix an insecurity in intel CPU's, so it can be safely disabled. NOTE: I am testing this with some of the BIOS modifications recommended by others here (such as disabling c6 state and "typical current idle", etc..) If this solution works for another week or so I'll try restoring the BIOS settings to their defaults and testing again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1690085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 118346] Sound not working after kernel upgrade
Public bug reported: After upgrading Feisty Fawn from 2.6.20-15-generic to 2.6.20-16-generic sounds no longer working. [EMAIL PROTECTED]:~$ cat /proc/asound/cards 0 [SB ]: HDA-Intel - HDA ATI SB HDA ATI SB at 0xc000 irq 19 [EMAIL PROTECTED]:~$ lsmod | grep snd snd_hda_intel 21912 2 snd_hda_codec 205056 1 snd_hda_intel snd_pcm_oss44544 0 snd_mixer_oss 17408 3 snd_pcm_oss snd_pcm79876 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss snd_seq_dummy 4740 0 snd_seq_oss32896 0 snd_seq_midi9600 0 snd_rawmidi25472 1 snd_seq_midi snd_seq_midi_event 8448 2 snd_seq_oss,snd_seq_midi snd_seq52592 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event snd_timer 23684 2 snd_pcm,snd_seq snd_seq_device 9100 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq snd54020 10 snd_hda_intel,snd_hda_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device soundcore 8672 3 snd snd_page_alloc 10888 2 snd_hda_intel,snd_pcm ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: Unconfirmed -- Sound not working after kernel upgrade https://bugs.launchpad.net/bugs/118346 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
