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
I see. But that is assuming that the 1.0.0.4 version “fixes” this issue. At
this point it’s only a guess but it seems likely given the previous replies
I’ve seen.
My god what a nightmare this has been. :-)
Best,
Ashesh Ambasta
> On 1 Jun 2020, at 17:59, bugzilla-dae...@bugzilla.kernel.org
I’ve tried that option of “Typical current idle” to no avail.
Best,
Ashesh Ambasta
> On 1 Jun 2020, at 20:51, bugzilla-dae...@bugzilla.kernel.org wrote:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=196683
>
> --- Comment #685 from ChrisB (c.budde...@web.de) ---
> Several experiments with
Created attachment 289445
attachment-1715-0.html
Does this mean the issue could be motherboard related? I actually
received a reply from AMD and they’re asking me for pictures of the
processor installed on the motherboard for some reason.
Best,
Ashesh Ambasta
> On 1 Jun 2020, at 12:46,
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
Even with screensavers enabled and displays never going to sleep; I just
experienced a crash on idle.
Here's the logs (https://pastebin.com/D7SEJn9J). I did change the
display configuration just before leaving my desk (with xrandr) which
explain some of these logs. But I can see nothing from
Created attachment 290243
attachment-20700-0.html
I haven't; and to be honest, I've been procrastinating this issue.
As a very ugly hack/workaround; I've disabled screen power management in
xscreensaver: so the CPU keeps drawing graphics on my screen instead of
my displays going to sleep.
Moreover, from a bit of reading I see that PBO is related to how fast
the processor clock speeds are boosted. How is this related to crashes
when idle?
Best,
Ashesh Ambasta
> On 28 Jun 2020, at 07:23, Ashesh Ambasta wrote:
>
> I’ll try that, but I doubt if at this stage it will have any
I’ll try that, but I doubt if at this stage it will have any effect.
Best,
Ashesh Ambasta
> On 27 Jun 2020, at 22:31, bugzilla-dae...@bugzilla.kernel.org wrote:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=196683
>
> --- Comment #693 from Arup (arup.chowdh...@gmail.com) ---
> Before you
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
I've also found
https://www.reddit.com/r/Amd/comments/8yzvxz/ryzen_c6_state_sleep_power_supply_common_current/e33lc6s/
which seems to be promising. It is, however, appalling to see this kind
of response from AMD and I'm quite sure this is my last AMD system.
I'm currently testing my system with
Have you tried the suggested fixes in this thread? And what changed
between that reinstall and earlier?
On 7/24/20 4:17 AM, bugzilla-dae...@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=196683
>
> Victor Queiroz (victorcqueir...@gmail.com) changed:
>
> What
Apologies for the late reply.
> As you disassembled the processor, were you able to copy the serial numbers
I did copy and send the older processor's serial numbers to the dealer,
for the RMA. That was a processor from a batch in late 2018 IIRC.
> from the old and new one, and could post them
So after months after my RMA, this issue seems to have surfaced again. I
experienced a lockup on system idle just a while ago.
It seems to also somehow be related to particular boots: my system was
off (not suspend, powered down) last night. It had been stable for
months before that.
I'll be
I did some research into the latest Ryzens, and I suspect the issue is
still not solved. I did manage to read some alarming posts discussing
similar lockups.
I suspect this also has to do with the motherboard. At this stage, I'm
no longer willing to try (I've done one RMA and 2.5 years with an
Created attachment 294817
attachment-13720-0.html
After some more digging around, I see the following in `journalctl -b-1`
:
Jan 23 14:48:41 quasar-nixos-tr kernel: xhci_hcd :09:00.3: Mismatch
between completed Set TR Deq Ptr command & xHCI internal state.
Jan 23 14:48:41
Created attachment 294819
attachment-29532-0.html
Actually, never mind.
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
17 matches
Mail list logo
