On Sun, 2018-03-18 at 11:06 -0300, Alexandre Oliva wrote: > Commit 304acb717e5b67cf56f05bc5b21123758e1f7ea0 AKA > https://patchwork.linux-mips.org/patch/9705/ was backported to 3.16.55 > stable as 8605aa2fea28c0485aeb60c114a9d52df1455915 and I'm afraid it > causes yeeloongs to fail to boot up. 3.16.54 was fine; bisection took > me to this patch. > > The symptom is a kernel panic -- attempt to kill init. No further info > is provided. > > Is this problem already known? Is there by any chance a known fix for > me to try, or should I investigate further? Guenter Roeck reported the same problem on QEMU Malta emulation. I haven't yet ivnestigated why this causes breakage. I will aim to fix this in the next update (will be 3.16.57 now), if necessary by reverting that and whatever depends on it. Ben. -- Ben Hutchings Logic doesn't apply to the real world. - Marvin Minsky
Attachment:
signature.asc
Description: This is a digitally signed message part
