Steve Litt via plug on 7 Dec 2020 16:33:13 -0800 |
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
Re: [PLUG] Question about AMD Ryzen 3000x rdrand bug |
Hi Bhaskar, So do you think your reinstall removed a package that was somehow messing things up via conflict with other software or with the hardware? This was an intermittent problem, as evidenced by the fact that it worked "until I attempted to download an application which froze almost immediately with a long chain of 0xFFFFFFFF notations." Is it possible the problem's still there but hasn't symptomed yet? What made you so sure this was a "rdrand" problem? Thanks, SteveT Steve Litt Autumn 2020 featured book: Thriving in Tough Times http://www.troubleshooters.com/thrive On Mon, 7 Dec 2020 15:10:59 -0500 "K.S. Bhaskar via plug" <plug@lists.phillylinux.org> wrote: > Randall – > > I successfully did a fresh install of Lubuntu 20.10 on that machine > this morning. It worked as advertised. > > Regards > – Bhaskar > > On Sun, Dec 6, 2020 at 11:05 AM K.S. Bhaskar <ksbhaskar@gmail.com> > wrote: > > > It so happens that I will be setting up Ubuntu 20.10 on a Ryzen 7 > > 3700X this week. I will let you know how it goes. > > > > Regards > > – Bhaskar > > > > On Sat, Dec 5, 2020 at 8:42 PM Randall Detra via plug < > > plug@lists.phillylinux.org> wrote: > > > >> Hello everyone, > >> > >> I have been using a Ryzen 5 3600 CPU with Ubuntu 20.04.1 > >> successfully > >> > >> I know this arises from a flaw in the CPU "rdrand" call which used > >> to make booting Linux impossible. My understanding is Ubuntu came > >> up with a work around for this bug so most of the time a user, > >> such as myself, will never notice it. I also know reflashing the > >> BIOS may correct the issue but I have acquired a 3rd generation > >> Ryzen 7 3700x CPU and would like to install it with the assumption > >> AMD has finally fixed this bug in their product. > >> > >> I am a much much more casual hobbyist with Linux than, perhaps, > >> many of you and would prefer to simply replace the CPU rather than > >> reflash the BIOS. Does anyone know if this bug still exists in > >> newer AMD products? > >> > >> Of course, if I have to reflash the BIOS, I will do so! > >> > >> Randall > >> > >> ___________________________________________________________________________ > >> Philadelphia Linux Users Group -- > >> http://www.phillylinux.org > >> Announcements - > >> http://lists.phillylinux.org/mailman/listinfo/plug-announce > >> General Discussion -- > >> http://lists.phillylinux.org/mailman/listinfo/plug > >> > > ___________________________________________________________________________ Philadelphia Linux Users Group -- http://www.phillylinux.org Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug