*** This bug is a duplicate of bug 1734327 ***
https://bugs.launchpad.net/bugs/1734327
** This bug has been marked a duplicate of bug 1734327
Kernel panic on a nfsroot system
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
No kernel oops with 4.13.0-19-TwoReverts after 24h
--
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/1731031
Title:
Kernel Oops with 17.10
Status in linux package in Ubuntu:
In Progress
I can confirm a crash with the default 4.13.0-19-generic kernel
--
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/1731031
Title:
Kernel Oops with 17.10
Status in linux package in Ubuntu:
I just triggered a kernel oops with 4.13.0-17, but the system remains
responsive afterwards:
[ 18.645733] random: crng init done
[ 76.860979] BUG: unable to handle kernel paging request at ea15932d2020
[ 76.861025] IP: kfree+0x53/0x160
[ 76.861039] PGD 0
[ 76.861040] P4D 0
[ 76.
I was unable to trigger the bug with the 4.13.0-19-TwoReverts kernel
(one hour of observation).
The stack traces in bug 1734327 look very similar to the ones I see,
like that bug I have one machine that triggers the bug (kernel panic
within 5 minutes of internet usage), and one that doesn't. I can
I am travelling right now, and I won't be able to try the test kernel
until after Christmas.
--
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/1731031
Title:
Kernel Oops with 17.10
Status
That is correct. Ubuntu starts with the mainline kernel and adds
patches on top. From your testing, it appears the bug may have been
introduce by an Ubuntu SAUCE patch, since you cannot reproduce it with
any of the upstream kernels.
We should figure out which Ubuntu kernel version introduced the
** Changed in: linux (Ubuntu Artful)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Artful)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigne
Is the ubuntu kernel built with 4.13 mainline plus a series of patches,
and I could rebuild the kernel while bisecting that set of patches? Or
is the situation more complicated than that?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to lin
I've been unable to reproduce the bug with 4.13-rc1
--
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/1731031
Title:
Kernel Oops with 17.10
Status in linux package in Ubuntu:
Triaged
Sta
Can you see if the bug happens with 4.13-rc1:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc1/
--
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/1731031
Title:
Kernel Oops with 17.1
I do have a crashkernel dump of 4.13.0-16-generic
--
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/1731031
Title:
Kernel Oops with 17.10
Status in linux package in Ubuntu:
Triaged
Statu
I have been able to reproduce the problem with 4.13 mainline so far
I managed to capture a kernel dump with stock 4.13.0-16-generic
This is a MacBook, I managed to get a similar error with a thunderbolt-
ethernet adapter instead of wifi. I have captured a second backtrace
with netconsole
[ 305.
sorry, I have been _unable_ to reproduce with 4.13 mainline
--
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/1731031
Title:
Kernel Oops with 17.10
Status in linux package in Ubuntu:
Tri
Can you try 4.13 final? If it has the bug, we can "Reverse" bisect
between 4.13 final and 4.14-rc1.
4.13 final is available from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
no crashes with 4.14-rc1 either
--
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/1731031
Title:
Kernel Oops with 17.10
Status in linux package in Ubuntu:
Triaged
Status in linux source
currently testing 4.14-rc4 (no crash kernel), no crashes so far (I can
still trigger the problem with 4.13)
--
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/1731031
Title:
Kernel Oops with
specifically, adding or removing the option "crashkernel=384M-:128M"
seems to affect my ability to trigger the bug
--
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/1731031
Title:
Kernel Oo
Unfortunately, I am no longer sure the issue is fixed at all, as opposed
to it just gets no longer triggered: I changed back to the stock kernel
affected by the bug, but changed boot parameters to capture a kernel
dump with a crash kernel - and now I get days of uptime without the
kernel oops.
--
Can you see which release candidate in 4.14 fixes this bug? If we know
that, we can "Reverse" bisect to identify the specific commit that is
the fix.
All of the release candidates are here:
http://kernel.ubuntu.com/~kernel-ppa/mainline/
You already tested 4.14-rc8, so maybe try 4.14-rc4 and 4.14
** Tags added: kernel-fixed-upstream
--
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/1731031
Title:
Kernel Oops with 17.10
Status in linux package in Ubuntu:
Confirmed
Bug description
trying to reproduce with http://kernel.ubuntu.com/~kernel-
ppa/mainline/v4.14-rc8/
--
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/1731031
Title:
Kernel Oops with 17.10
Status in linux p
xorg was auto selected when I used apport and said "freeze"
** Package changed: xorg (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/1731031
Title:
Kernel Oops
[ 305.778878] BUG: unable to handle kernel paging request at f9cafc20
[ 305.778915] IP: kfree+0x53/0x160
[ 305.778924] PGD 0
[ 305.778924] P4D 0
[ 305.778939] Oops: [#1] SMP
[ 305.778948] Modules linked in: rfcomm cmac bnep binfmt_misc
intel_spi_platform intel_spi spi_nor mtd
I boot, I connect to wifi, I browse the internet, freeze happens within
minutes
had no similar issue with Ubuntu 17.04 before update
--
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/1731031
25 matches
Mail list logo
