Hi Ben, hi Petra, On Mon, Oct 24, 2016 at 02:35:07PM +0100, Ben Hutchings wrote: > On Mon, 2016-10-24 at 11:49 +0200, Petra Ruebe-Pugliese wrote: > [...] > > Okay. So I've sacrificed the less important of the two > > notebooks again and repeated the "apt-get dist-upgrade" > > so that the current kernel got installed again. > > > > In doing so, two messages appeared that looked approximately > > like this: > > > > /etc/kernel-img.conf:4: ignoring unknown parameter relative_links > > /etc/kernel-img.conf:6: ignoring unknown parameter do_bootfloppy > > > > The second of these lines reminds me of the fact that with > > previous kernel versions the boot process used to stop in the > > same place for quite some (disquieting!) time and then continued > > with some message about a read error on /dev/fd<sth.> > > I don't know what 'do_bootfloppy' used to do, but I think it's unrelated to > loading of the floppy driver. It sounds like you have quite an old > installation that might also have some obsolete scripts left in the boot > process. Also, note that the /dev/fd directory is unrelated to floppy drives. > > > This was the case on all my computers, although these two > > thinkpads no longer have a floppy drive. > > > > Now to the photo. I've tried to make one. > > With these new boot parameters there is a lot of output rushing > > through which I could not catch. So I'm sending only what was > > to be seen when it stopped. Maybe that's enough to put you on > > the right track. If not, please tell me what else I can do > > to bring some light into the matter. > > OK, this is the same crash that someone else reported and I think I > know which change triggered it (though not why).
There seem to be an upstream fix now for this issue: https://git.kernel.org/linus/ff8560512b8d4b7ca3ef4fd69166634ac30b2525 Can you by chance confirm that this works as well for you? Regards, Salvatore
