Thank you Joseph, the upstream kernel from months ago was the cause of
the issue. I had completely forgotten about it being there and did not
recognise the change in version numbering as significant.
I followed the steps outlined in http://askubuntu.com/a/594484/109072 to
remove the kernel and a
I expect I got the kernel the same way I get most of my kernels, though
an `apt-get upgrade`. Although I did try and compile a kernel a while
ago... I wonder if that got left around as an install option and it was
so long since I last rebooted I forgot about it!
Now isn't that a silly thing to do
Where did you happen to get the 4.4.21 kernel? That is an upstream
kernel and not an official Ubuntu kernel like 4.4.0-57.
It might be good to boot 4.4.0-57 and apply the latest updates.
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Tags added: kernel-da-key
--
You receive
apport information
** Tags added: apport-collected
** Description changed:
On powering my PC up after the holiday break I got a welcome back in the
form of a kernel panic. I had completed some upgrades before the
holiday and was seeing a restart to use the newly upgraded packages
messag
I have executed the command `apport-collect 1653636` as requested by
brad-figg. I can see that log files have been added.
Note that this command was performed while running 4.4.0-57-generic not
the 4.4.21 kernel that causes the issue. It is also worth noting that
as the filesystem could not be m
** Package changed: ubuntu => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1653636
Title:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-
block(0,
6 matches
Mail list logo
