[Expired for linux (Ubuntu Cosmic) because there has been no activity
for 60 days.]
** Changed in: linux (Ubuntu Cosmic)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
[Expired for linux (Ubuntu Bionic) because there has been no activity
for 60 days.]
** Changed in: linux (Ubuntu Bionic)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Tags removed: kernel-key
** Tags added: kernel-da-key
--
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/1780466
Title:
Kernel panic at boot
Status in linux package in Ubuntu:
I'll mark this bug as incomplete for now. Just move it back to
confirmed if the panic starts happening again.
** Changed in: linux (Ubuntu Cosmic)
Status: Confirmed => Incomplete
** Changed in: linux (Ubuntu Bionic)
Status: Confirmed => Incomplete
--
You received this bug
That all those kernels are working now was a bit suspicious to me. I did
upgrade yesterday my system which also involved an issue: The vboxdrv
(VirtualBox) kernel module couldn't be loaded anymore because of a
format error or such. Since a downgrade from version 5.2.14 to version
5.2.12 of
I have tested all those 4 kernels (amd64; generic) but none of them
causes a kernel panic at boot.
--
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/1780466
Title:
Kernel panic at boot
I'd like to perform a bisect to figure out what commit caused this
regression. We need to identify the earliest kernel where the issue
started happening as well as the last kernel that did not have this
issue.
Can you test the following kernels and report back? We are looking for
the first kernel
Edit: I checked the uncompromisedness via GPG - as I do not want to risk
waiting a very long time until the https issue is solved. The kernel
still panics at boot and claims this time about a tick-broadcast.c:652.
** Tags added: kernel-bug-exists-upstream
** Changed in: linux (Ubuntu Cosmic)
At the current time kernel.ubuntu.com has no https availability (it
times out) and downloading those packages over http is very insecure. I
hope https becomes available soon so I can test this kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.18 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
apport information
** Tags added: apport-collected
** Description changed:
Initially I have reported this issue here:
https://bugzilla.kernel.org/show_bug.cgi?id=197815
But after testing out linux-image-4.17.0-4-generic on Ubuntu 18.10 dev
the details changed a bit. Mainly I'm
** Description changed:
Initially I have reported this issue here:
https://bugzilla.kernel.org/show_bug.cgi?id=197815
- But after testing out linux-image-4.17.0-4-generic the details changed a
- bit. Mainly I'm getting the error message "VFS: Cannot open root device
- "sda1" or
12 matches
Mail list logo
