** Changed in: linux (Ubuntu Trusty)
Assignee: Guilherme G. Piccoli (gpiccoli) => (unassigned)
--
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/1592597
Title:
3.13.0-88-generic:amd64
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
** Changed in: linux (Ubuntu Trusty)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
** Changed in: linux (Ubuntu Trusty)
Status: Incomplete => Triaged
--
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/1592597
Title:
3.13.0-88-generic:amd64 fails to boot on Dell Powe
This second trace looks related to the fix below which was in v3.16 and
would support at least that issue being fixed in lts-x kernel:
commit eb7a59b2c888c2518ba2c9d0020343ca71aa9dee
Author: Michael wang
Date: Thu Feb 20 11:14:53 2014 +0800
sched/fair: Reset se-depth when task switch
Moving to a Xenial kernel seemed to cure some affected systems, so we
would assume it being fixed released from there.
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
There also was some case of a different panic which looked like below:
[ 16.191583] BUG: unable to handle kernel NULL pointer dereference at
0148
[ 16.201096] IP: [] check_preempt_wakeup+0x137/0x270
[ 16.208349] PGD 0
[ 16.211201] Oops: [#1] SMP
[ 16.214877] Modules lin
We look to have had a hard recurrance of this issue on the system. After
much messing about we appear to have gotten some real stack traces. We
see similar ones on a range of kernel versions in 3.13.0-* series:
NULL pointer dereference at 0010
[ 15.316900] IP: [] rb_next+0x1/0x50
[
@vik, would it be possible for you test test the latest upstream kernel
mentioned in comment #4?
--
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/1592597
Title:
3.13.0-88-generic:amd64 fai
I'm also getting kernel panic with this kernel on Fujitsu T730. I can
successfully boot 3.13.0-87.
--
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/1592597
Title:
3.13.0-88-generic:amd64 f
Testing the latest upstream kernel will tell us if this bug is already
fixed in mainline. If it is fixed, we can then work to identify the
commit that fixes the bug.
An alternative would be to perform a kernel bisect, which will identify
the commit that introduced the regression. However, that w
system is headless, getting a 403 with lynx (lp#997020). what logs can
I provide?
--
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/1592597
Title:
3.13.0-88-generic:amd64 fails to boot on
Joe, this is a production customer environment, so no we can't test
newer kernels. I'm also not sure why a new upstream version would be
relevant since this appears to be a regression in released kernels?
** Changed in: linux (Ubuntu)
Status: Incomplete => New
** Changed in: linux (Ubuntu
Would it be possible for you to test the latest upstream stable kernel?
Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the
latest v3.13 stable kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel
https://private-fileshare.canonical.com/~jillr/lp1592597/sosreport-
os-1-20160614233237.tar.xz
md5: c27d8c988ee155cf61532285866907d4
--
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/1592597
14 matches
Mail list logo