[Bug 2051720]
(In reply to Nickolas Gupton from comment #32) > this issue has been reported starting in 5.16 on the original bug linked that > they closed and asked for someone to make a new issue if it was still > present. Bug 215167 [1] reports a regression in Linux 5.14, and the referenced openSUSE report says at the end it should be fixed in 5.16.1. Nickolas, thank you for attaching the full Linux logs. As the error from the bug title is not present in the log, I recommend to close this issue, and create a new one for your problem with a descriptive title like *Bluetooth only starts working after reloading btusb and btintel*, attaching all the files there. If you could bisect [3] the commit, that would even get you there faster. The Bluetooth device can even be passed to a virtual machine, and if the problem is reproducible there, bisection is quite fast [4][5]. I am sorry about this, but unfortunately, the comments by others on probably different issues, make it very hard and time consuming to understanding the actual issue. It looks like the maintainers are overworked and the subsystem has not enough resources. Still if you buy a device with Intel hardware (and even better a device with official GNU/Linux support), it’s valid to expect that Intel hardware works also on GNU/Linux. [1]: https://bugzilla.kernel.org/show_bug.cgi?id=215167 [2]: https://bugzilla.opensuse.org/show_bug.cgi?id=1193124 [3]: https://www.kernel.org/doc/html/latest/admin-guide/verify-bugs-and-bisect-regressions.html [4]: https://lore.kernel.org/linux-bluetooth/5891f0d5-8d51-9da5-7663-718f30149...@molgen.mpg.de/ [5]: https://lore.kernel.org/lkml/d7206e12-1b99-c3be-84f4-df22af427...@molgen.mpg.de/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051720 Title: Bluetooth Broken In Kernel Versions 6.5+ (Intel AX210) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2051720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051720]
@dustin, thank you, but please *attach* the full log next time. [90310.622241] Bluetooth: hci0: Retrieving Intel exception info failed (-16) is different from this issue title. Please create a new issue, and attach all the information there. > This is a regression. It has been broken since 6.5. It worked fine in prior > kernel versions. That is actually a good thing. It’d be great if you bisected the commit introducing the regression [1]. [1]: https://www.kernel.org/doc/html/latest/admin-guide/verify-bugs-and- bisect-regressions.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051720 Title: Bluetooth Broken In Kernel Versions 6.5+ (Intel AX210) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2051720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051720]
@nickolas, from your bug description it’s unclear, if this is a regression, or if Bluetooth never worked for you. Could you please clarify? Please attach the output of `dmesg`. Also, please run `bluetoothctl` and share all the output. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051720 Title: Bluetooth Broken In Kernel Versions 6.5+ (Intel AX210) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2051720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521173]
[Please remove the quote next time from your reply. If you look at the Web interface, the comments get needlessly long because of that.] (In reply to cspadijer from comment #20) […] > Okay yes. I will mark as fixed and open up new for other issues you > clarified as linux. Thanks for your help. Thank you. > For the firmware issues should I be reaching out to the vendors? Yes, only the vendors can fix the firmware, unless you use FLOSS firmware like coreboot based firmware for example. Unfortunately, my track record of getting vendors to fix their firmware is not so good, as you are only one customer using this weird operating system and not Microsoft Windows. But fingers crossed. Additionally you might want to point them to the Firmware Test Suite (FWTS) [1]. [1]: https://wiki.ubuntu.com/FirmwareTestSuite/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1521173 Title: AER: Corrected error received: id=00e0 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1521173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521173]
(In reply to cspadijer from comment #18) > Are you good with me using kernel: 5.11.0-37-generic or would you > prefer I use a different kernel? > The X555U is currently running Linux Mint 20.2 Cinnamon. > > FYI: > I tried removing pci=noaer and it does boot now (without your patch). > It has been a while since I tried removing pci=noaer and new kernels get > installed all the time so not sure what kernel first started allowing it > to boot without needing that line. > However, there are still many errors on boot. The original bug seems to be solved now. As there are over ten comments already, could you mark it as fixed, and create new issues? > dmesg --level=err,warn > [ 0.105337] x86/cpu: VMX (outside TXT) disabled by BIOS > [ 0.110761] MDS CPU bug present and SMT on, data leak possible. See > https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for > more details. Is GNU/Linux applying the latest microcode updates? > [ 0.110761] #3 Cosmetic error. > [ 0.114598] ENERGY_PERF_BIAS: Set to 'normal', was 'performance' > [ 0.135583] ACPI BIOS Error (bug): Could not resolve symbol > [\_SB.PCI0.RP01.PXSX], AE_NOT_FOUND (20201113/psargs-330) > [ 0.135597] ACPI Error: Skipping While/If block (20201113/psloop-427) > [ 0.527786] tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not > cover the entire command/response buffer. [mem 0xfed4-0xfed4087f flags > 0x200] vs fed40080 f80 > [ 0.527874] tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not > cover the entire command/response buffer. [mem 0xfed4-0xfed4087f flags > 0x200] vs fed40080 f80 Firmware issues. > [ 0.736009] i8042: PNP: PS/2 appears to have AUX port disabled, if this is > incorrect please boot with i8042.nopnp Can be ignored. > [ 0.738042] platform eisa.0: EISA: Cannot allocate resource for mainboard > [ 0.738044] platform eisa.0: Cannot allocate resource for EISA slot 1 > [ 0.738045] platform eisa.0: Cannot allocate resource for EISA slot 2 > [ 0.738046] platform eisa.0: Cannot allocate resource for EISA slot 3 > [ 0.738048] platform eisa.0: Cannot allocate resource for EISA slot 4 > [ 0.738049] platform eisa.0: Cannot allocate resource for EISA slot 5 > [ 0.738050] platform eisa.0: Cannot allocate resource for EISA slot 6 > [ 0.738051] platform eisa.0: Cannot allocate resource for EISA slot 7 > [ 0.738052] platform eisa.0: Cannot allocate resource for EISA slot 8 Is there an EISA slot? > [ 1.268806] r8169 :02:00.0: can't disable ASPM; OS doesn't have ASPM > control Can be ignored. > [ 1.329939] i2c_hid i2c-ELAN1000:00: supply vdd not found, using dummy > regulator > [ 1.329973] i2c_hid i2c-ELAN1000:00: supply vddl not found, using dummy > regulator Please contact the Linux folks about this. But first try the latest Linux mainline version. > [ 1.611704] ata1.00: supports DRM functions and may not be fully > accessible > [ 1.613394] ata1.00: supports DRM functions and may not be fully > accessible > [ 5.726419] elan_i2c i2c-ELAN1000:00: supply vcc not found, using dummy > regulator > [ 6.376762] nvidia: loading out-of-tree module taints kernel. > [ 6.376775] nvidia: module license 'NVIDIA' taints kernel. > [ 6.376776] Disabling lock debugging due to kernel taint > > [ 6.884240] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 470.63.01 Tue > Aug 3 20:44:16 UTC 2021 > [ 6.958699] nvidia_uvm: module uses symbols from proprietary module > nvidia, inheriting taint. > [ 8.533945] ACPI Warning: \_SB.PCI0.RP01.PEGP._DSM: Argument #4 type > mismatch - Found [Buffer], ACPI requires [Package] (20201113/nsarguments-61) Firmware issue. > Chris I do not see any AER messages, so please create new issues. > On 2021-10-03 2:03 a.m., bugzilla-dae...@bugzilla.kernel.org wrote: […] Please remove the citation/quotes when replying by email in the future, when not using interleaved style when replying. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1521173 Title: AER: Corrected error received: id=00e0 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1521173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521173]
As the ASUS X541UVK is a different device, please create a new bug report with all the necessary information included/attached. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1521173 Title: AER: Corrected error received: id=00e0 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1521173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690085]
Agmon, thank you for your report. Please open a separate issue with the full output of `dmesg` attached, and the output of `acpidump`. Please reference the issues here. -- 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 Ashesh Ambasta from comment #736) […] > I also see the following when looking at all similar messages: > > |╰─$ journalctl| grep 'xhci.*Mismatch' || > ||Jun 13 14:43:09 quasar-nixos-tr kernel: xhci_hcd :09:00.3: > Mismatch between completed Set TR Deq Ptr command & xHCI internal > state.|| […] Please report that to the Linux USB folks (entry for USB SUBSYSTEM in the file MAINTAINERS [1]). If you do, please also attach output of `lsusb`. [1]: https://www.kernel.org/doc/linux/MAINTAINERS -- 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 Ashesh Ambasta from comment #720) > I can confirm that in my case, all the suggested alternatives in this > thread didn't work (the ones that were applicable to my use-case anyway). > > In the end, I threw my hands up and did an RMA. And that was over a > month ago. It seems to have solved the isssue. The processor I had > previously and its replacement were different batches; the former being > from 2019 and the latter from Feb. 2020. It seems to me that AMD ironed > out some issues with processors and I got lucky with the replacement. Or > it could just be some tiny variations in fabrication. I can never be sure. > > But my machine has been up since the RMA without any crashes. As you disassembled the processor, were you able to copy the serial numbers from the old and new one, and could post them here please? Could you pleas PS: Please always remove the full quote from messages, when replying by email, as it just clutters the Web interface. -- 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 Ashesh Ambasta from comment #699) > Created attachment 290243 [details] > attachment-20700-0.html I am getting: > Sorry, you are not authorized to access attachment #290243. […] > AMD did publish an errata in which they claim an issue like this exists; > but a solution is ruled out. Which is further bad news. There was some > discussion on a fix being at the kernel level, but that isn't anywhere > in sight either. I believe these CPU's are plagued by several issues, > which probably makes a fix for this at the kernel level hard. However, > Windows seems to have managed to fix it. That’s interesting. Could you please share the URL to these statements? […] raulvior.bcn, Asheesh: Please always remove the cited parts, as otherwise the Web issue page gets even more convoluted. Thanks. > Anyway; rants aside, this is my current take on the CPU. > > On 7/12/20 3:58 PM, bugzilla-dae...@bugzilla.kernel.org wrote: > > https://bugzilla.kernel.org/show_bug.cgi?id=196683 > > > > --- Comment #698 from raulvior@gmail.com --- > > Did you ask for an RMA? Did it work? > > (In reply to Ashesh Ambasta from comment #692) > >> As a last resort, I've tried `idle=halt` on this machine. And yet my > >> system just crashed after 3 weeks of uptime. > >> > >> I'm done with AMD. I will RMA this processor to try things out, but > >> overall, if that doesn't work, this thing is headed to the junkyard and > >> I'm going to live with Intel. > >> > >> At least in the 13 or so odd Intel systems I've tried, I've not had > >> exhasperating issues like these where the company is positively trying > >> to ignore this ongoing issue. > >> > >> This is disgusting from AMD. > >> > >> On 6/11/20 6:03 PM, bugzilla-dae...@bugzilla.kernel.org wrote: > >>> https://bugzilla.kernel.org/show_bug.cgi?id=196683 > >>> > >>> --- Comment #689 from raulvior@gmail.com --- > >>> (In reply to raulvior.bcn from comment #653) > (In reply to txrx from comment #651) > > Typical Current Idle might not be working. Read the sensor output. If > voltage is not higher than without enabling it, try to increase the core > voltage. > > My Ryzen 7 1800X seems to not produce hangs since I upgraded to 1003ABB > >> with > an ASUS Crosshair VI Hero and enabled Typical current idle. > > > > I was able to update my BIOS to version 18, but my system still locks > up. > > I tried the following with the new BIOS: > >- use factory defaults > >- disable SMT > >- disable SMT with Typical Current Idle > >- all of the above with SVM disabled/enabled > > Right now I set the power supply idle control to "Low ..." and will > >> report > > back. > > > >>> The motherboard kept hanging. I had to remove the Vitals GNOME Extension. > >> It > >>> seems that polling voltage values hangs the motherboard... Still, there > are > >>> times that the computer does not come back from suspend. There's > something > >>> wrong with the BIOS/UEFI. > >>> -- 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 Ashesh Ambasta from comment #680) > I've been facing the same issue since I've bought this machine and setting > my BIOS power settings to "Typical current idle" has only partially fixed > things (the system still crashes every 1-2 weeks during idle: I leave my > desk, screensaver fires up, then screens go to sleep, and by the time I get > back to my desk, the system no longer responds to any input and the only > option is a hard reset.). > > At the time of writing, I can't tell if the AGESA version has made it into > my motherboard: https://www.asrock.com/mb/AMD/X399M%20Taichi/index.asp#BIOS [I have an MSI board, but checked the firmware update files for you.] The description for version 3.60 includes: > Update AMD AGESA ThreadRipperPI-SP3r2 1.1.0.2 Reading the ASRock forum thread *What happened to Fatality X399 Bios 1.60?* [1], it’s enough to run the firmware update file through a hexeditor. I searched for *GES* and was lucky for version 3.80. $ hexdump -C X399MT3.80 | less […] 00e34ce0 00 00 00 00 00 00 00 00 00 00 00 00 be 2c 63 17 |.,c.| 00e34cf0 80 6c b6 49 82 07 12 b5 3d 9b 25 70 41 47 45 53 |.l.I=.%pAGES| 00e34d00 41 21 56 39 00 54 68 72 65 61 64 52 69 70 70 65 |A!V9.ThreadRippe| 00e34d10 72 50 49 2d 53 50 33 72 32 2d 31 2e 31 2e 30 2e |rPI-SP3r2-1.1.0.| 00e34d20 32 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |2...| […] ``` So, it still has AGESA version 1.1.0.2. […] [1]: http://forum.asrock.com/forum_posts.asp?TID=6165=4=what-happened-to-fatality-x399-bios-160 -- 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 Charles Lim from comment #673) > For those who are looking for a solution or already found a solution, there > is a new update of AGESA rolling out. The new version 1.0.0.4 claims: > > * Improved system stability when switching through ACPI power states. > > It has arrived on my Asus PRIME B350M days ago, I have upgraded and kept > default optimised BIOS settings. When I used ZenState to check cpu status, > the C6 state is now: > > C6 State - Package - Enabled > C6 State - Core - Disabled > > Previously they were all enabled, I guessed the new AGESA release finally > solved this problem from source? I will report back days later to see if the > system still hangs. Are you sure about the AGESA version string? For the Dell OptiPlex 5055, firmware version 1.1.20 [1], running it through *Dell PFS BIOS Extractor*, and then grepping for `AGESA!` in the strings/hexdump, it says it includes AGESA version 1.0.0.7a. $ strings 1\ --\ 1\ OptiPlex\ System\ BIOS\ v1.1.20.bin | grep -A1 AGESA! %pAGESA!V9 SummitPI-AM4 1.0.0.7a [1]: https://www.dell.com/support/home/de-de/drivers/driversdetails?driverid=w6mw5=wt64a=optiplex-5055-ryzen-cpu [2]: https://github.com/platomav/BIOSUtilities -- 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 Rafal Kupiec from comment #675) > (In reply to Paul Menzel from comment #674) > > (In reply to Charles Lim from comment #673) > > > > > For those who are looking for a solution or already found a solution, > there > > > is a new update of AGESA rolling out. The new version 1.0.0.4 claims: > > > > > > * Improved system stability when switching through ACPI power states. […] > > Are you sure about the AGESA version string? For the Dell OptiPlex 5055, > > firmware version 1.1.20 [1], running it through *Dell PFS BIOS Extractor*, > > and then grepping for `AGESA!` in the strings/hexdump, it says it includes > > AGESA version 1.0.0.7a. […] > 1.0.0.7a is for Zen+ > 1.0.0.4 is for Zen2. > > AMD resets versioning every new CPU generation. 1.0.0.4 is newer than 1.0.0.7 Thank you for the clarification. Though I am confused now, as I thought you could use Zen2 devices in “Zen+ boards” (boards original for Zen+). So, AGESA 1.0.0.4 for Zen2 also support the predecessor generation? -- 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 1748565]
Should this be added to the stable series too? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1748565 Title: Kernel regularly logs: Bluetooth: hci0: last event is not cmd complete (0x0f) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1748565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 952080]
Ben, Alan, Rafael, could you please close it then? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/952080 Title: laptop immediately resumes after sending to standby To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/952080/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690085]
The title of the bug should be changed to include Ryzen 7 1700X, and the reporter should follow up, if the problem still occurs with Linux 4.18. For the other issues, separate bug reports should be submitted. Though the mailing lists might be the better forum for this, as the Linux kernel developers for the subsystem do not seem to use the Kernel.org Bugzilla. -- 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 Antoine Pitrou from comment #398) > @Daniel what makes you think this bug is fixed? It certainly isn't for me. > I have a ASRock Fatal1ty X370 Gaming X motherboard, a Ryzen 7 1700 CPU, have > updated the motherboard BIOS to its latest version (4.80 with > PinnaclePI-AM4_1.0.0.2 Patch A) and am still getting idle lockups with > kernel 4.15.0-32-generic (Ubuntu 18.04.1 kernel). The workaround for me is > to disable C6 states using the Zenstates.py script (which has the > unfortunate side effect of lowering the max CPU frequency in single-threaded > mode). Please remember, this is the upstream Linux kernel bug tracker. So, reports should only be for the latest stable releases, which currently is 4.18.3 [1]. Some distributions make it easy to install those. Packages are available for Ubuntu [2]. Please report issues with the heavily patched Ubuntu default Linux kernel to the Ubuntu bug tracker [3]. [1]: https://www.kernel.org/ [2]: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18.3/ [3]: https://bugs.launchpad.net/ubuntu/+source/linux/+bugs -- 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
