On Monday 30 May 2016 17:25:26 Peter Saunderson wrote: > On 30/05/16 10:36, Pali Rohár wrote: > >Hi Peter! Thank you for information! Are you able to try to call that > >function on some old kernel (e.g. 3.12 or 3.14) to verify that it is > >caused only and only by that function? > > > I have tried to use my old 3.19.0 kernel that did not have the problem but > now it will not boot. The boot screen is left with > > Loading Linux linux... > Loading initial ramdisk... > > No logs etc.. I am guessing that some grub or ram disk change is giving me > the problem. I have just upgraded to Ubuntu 16.04 and do not want to > downgrade so I am a bit stuck at the moment and doubt that I can do this > test. > > Peter. You can try to regenerate initramfs with ubuntu command: $ sudo update-initramfs -u -k all In case you modified or updated some initram files or kernel modules you need to regenerate it to take effect at boot... -k all tells to regenerate *all* initramfs images, not only for currently booted kernel. -- Pali Rohár pali.rohar@xxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-hwmon" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html