| 1 |
On Fri, Jul 19, 2019 at 7:52 AM Alan Mackenzie <acm@×××.de> wrote: |
| 2 |
> |
| 3 |
> On Fri, Jul 19, 2019 at 01:30:48 +0200, gentoo-user@××××.de wrote: |
| 4 |
> |
| 5 |
> > > Running ASUS Prime x470 Prime with ryzen 2700 and have upgraded kernel |
| 6 |
> > > to latest stable when running emerge --update... |
| 7 |
> |
| 8 |
> I've been having this problem ever since I built my "new" (April 2017) |
| 9 |
> machine, Ryzen something or other on an ASUS Prime x370pro. My machine |
| 10 |
> has been hanging, perhaps, about once a week. |
| 11 |
> |
| 12 |
|
| 13 |
What kernel version are you both running? The new integrated vega |
| 14 |
APUs and the vega GPUs use the amdgpu kernel driver, which is new. It |
| 15 |
was fairly unstable until recently. |
| 16 |
|
| 17 |
If you're on the latest 4.19 that probably isn't the problem (not that |
| 18 |
it is impossible). 4.19.59 is the current upstream longterm. If |
| 19 |
you're on something pre-4.18 I'd expect problems. I don't know if all |
| 20 |
the amdgpu issues are backported to 4.14 - I would probably stick with |
| 21 |
4.19 with anything Ryzen/Vega-related. |
| 22 |
|
| 23 |
It is possible this isn't the problem, but this sounds like some kind |
| 24 |
of KMS-related issue. If you can't switch to a virtual console with |
| 25 |
KMS that is probably a kernel issue. |
| 26 |
|
| 27 |
I'm assuming you are using the in-kernel amdgpu drivers. If you're |
| 28 |
using some kind of proprietary driver that could be a problem as well. |
| 29 |
|
| 30 |
-- |
| 31 |
Rich |
Archives