[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1301496
T
Thank you for taking the time to file a bug report on this issue.
However, given the number of bugs that the Kernel Team receives during
any development cycle it is impossible for us to review them all.
Therefore, we occasionally resort to using automated bots to request
further testing. This is s
** Tags removed: kernel-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1301496
Title:
kernel crash: Unable to handle kernel paging request for data
To manage notifications about this bug go to:
regarding stack 4k page kernel, this just happened on wolfe-02. running (I
believe) a 4k page kernel.
$ grep CONFIG_PPC.*.*PAGES /boot/config-3.13.0-8-generic
CONFIG_PPC_4K_PAGES=y
# CONFIG_PPC_64K_PAGES is not set
wolfe-02 login: [241848.101690] Unable to handle kernel paging request for data
000044
LEN TYPE
00001400020001034b
LEN TYPE
100802fe80000100080001007f0100
Got hold of one of these machines in this "everything is exploding"
state. Used the below test program to dump out the static variables and
obtain the alignment of the corruption. (This program does not
manipulate this data which eliminates a bug in dpkg as cause.) Note
that the corruption is at
Ad this seems to be reproducible we might want to spin up one of the
affected machines with a 4K kernel and see if that avoids the issue. Of
course as we have seen with other bugs, assumptions in the client s/w
may be to blame.
--
You received this bug notification because you are a member of Ub
For what it's worth, the stability offered by a reboot was short-lived,
and wolfe's gone back to hating its users.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1301496
Title:
kernel crash: Unable t
fwiw, I've investigated the dpkg segfaults, and seen the following:
$ gdb dpkg
GNU gdb (Ubuntu 7.7-0ubuntu3) 7.7
[...]
Reading symbols from dpkg...Reading symbols from
/usr/lib/debug//usr/bin/dpkg...done.
done.
(gdb) run -l
Starting program: /usr/bin/dpkg -l
Program received signal SIGSEGV, Segm
Was there a prior Trusty kernel version that did not exhibit this bug?
** Tags added: kernel-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1301496
Title:
kernel crash: Unable to handle kernel
Lots going on here. First looking at the syslog file from Matt. I notice
a lot of:
Apr 3 20:57:45 wolfe-01 kernel: [ 4062.074422] jujud[1929]: bad frame
in setup_rt_frame: nip lr
Looks like we smashed our stack. This seems to be a separate issue
** Attachment added: "The /var/log/syslog file from wolfe-01."
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1301496/+attachment/4064026/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
We just experienced the same problem on wolfe-01 today. We were
deploying charms with juju and noticed that juju status did not return
the right output.
The kernel that was running is:
Linux wolfe-01 3.13.0-21-generic #43-Ubuntu SMP Mon Mar 31 22:54:04 UTC
2014 ppc64le ppc64le ppc64le GNU/Linux
Can you see if this issue also happens on the 3.13.0-21 kernel? It can
be downloaded from:
https://launchpad.net/ubuntu/trusty/+source/linux/3.13.0-21.43
The ppc64el image can be directly downloaded from:
https://launchpad.net/ubuntu/+source/linux/3.13.0-21.43/+build/5866502
** Changed in: linu
apport information
** Tags added: apport-collected trusty uec-images
** Description changed:
We've seen this happen twice now on ppc64el guests that are probably
under load. I don't have a lot of the details on what was going on when
they failed, but I have the stack traces.
[101168.
I was doing a juju deploy when this happened. I got a segfault for doing
a "juju status" and then the terminal/ssh connection froze almost
immediately after.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
** Attachment added: "trace from 3.13.0-19-generic"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1301496/+attachment/4060946/+files/wolfe-01-kernel-trace.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
** Attachment added: "trace from 3.13.0-8-generic"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1301496/+attachment/4060945/+files/wolfe-02-kernel-trace.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
18 matches
Mail list logo