1 |
On Sat, Dec 7, 2019 at 2:13 PM Rich Freeman <rich0@g.o> wrote: |
2 |
> |
3 |
> On Sat, Dec 7, 2019 at 10:19 AM n952162 <n952162@×××.de> wrote: |
4 |
> > |
5 |
> > On 12/07/19 13:17, Mick wrote: |
6 |
> > |
7 |
> > > On Friday, 6 December 2019 11:38:09 GMT n952162 wrote: |
8 |
> > >> I rebuilt my kernel and now have the Network Block Device, but now my |
9 |
> > >> system doesn't power off anymore, using shutdown -h now, and doesn't |
10 |
> > >> reboot with reboot (orshutdown -r now). |
11 |
> > > I'm not sure which kernel you said you're running at present, but this commit |
12 |
> > > was made to handle a similar behaviour: |
13 |
> > > |
14 |
> > > https://lkml.org/lkml/2019/10/6/338 |
15 |
> > > |
16 |
> > >> Anybody have any idea what could have become misconfigured? |
17 |
> > > As per above commit, it could be a matter of a kernel driver bug rather a |
18 |
> > > misconfiguration on your part. |
19 |
> > Oh! That's interesting. I'm using AMDGPU, which might be related. But |
20 |
> > it's happening in a more recent kernel: 4.19.72 rather than the [PATCH |
21 |
> > 4.14 08/68] listed in the bug report (although, I don't know what 08/68 |
22 |
> > refers to) |
23 |
> > |
24 |
> |
25 |
> First, it looks like that was reverted in |
26 |
> 8d13c187c42e110625d60094668a8f778c092879 due to some problem. |
27 |
> |
28 |
|
29 |
Ok, I'm being dense. The revert is supposed to FIX the reboot |
30 |
problem. For 4.19 the problem was introduced in 4.19.78 and fixed in |
31 |
4.19.81. If you're running 4.19.72 I don't think you should be |
32 |
affected by this. |
33 |
|
34 |
-- |
35 |
Rich |