[Bug 1301496] Re: kernel crash: Unable to handle kernel paging request for data
[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 Title: kernel crash: Unable to handle kernel paging request for data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1301496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1301496] Re: kernel crash: Unable to handle kernel paging request for data
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 such a request. With the recent release of this Ubuntu release, would like to confirm if this bug is still present. Please test again with the newer kernel and indicate in the bug if this issue still exists or not. You can update to the latest development kernel by simply running the following commands in a terminal window: sudo apt-get update sudo apt-get dist-upgrade If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released. If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging. Thank you for your help, we really do appreciate it. ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Tags added: kernel-request-3.13.0-24.46 -- 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: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1301496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1301496] Re: kernel crash: Unable to handle kernel paging request for data
** 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: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1301496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1301496] Re: kernel crash: Unable to handle kernel paging request for data
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 at address 0x200140044 [241848.112613] Faulting instruction address: 0xc0954b60 [241848.112704] Oops: Kernel access of bad area, sig: 11 [#1] [241848.112777] SMP NR_CPUS=2048 NUMA pSeries [241848.112871] Modules linked in: btrfs xor raid6_pq libcrc32c veth xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables dm_crypt [241848.113353] CPU: 1 PID: 10355 Comm: kworker/u4:0 Not tainted 3.13.0-8-generic #28-Ubuntu [241848.113465] Workqueue: netns .cleanup_net [241848.113540] task: c002192621f0 ti: c00253eec000 task.ti: c00253eec000 [241848.113655] NIP: c0954b60 LR: c0954b68 CTR: c0954b00 [241848.113768] REGS: c00253eef760 TRAP: 0300 Not tainted (3.13.0-8-generic) [241848.113871] MSR: 80009033 CR: 44002024 XER: [241848.114117] CFAR: c01d2820 DAR: 000200140044 DSISR: 4000 SOFTE: 1 GPR00: c0954b68 c00253eef9e0 c10b0dd0 000200140044 GPR04: fb7698d8 c0034674d900 c0954b68 c003fe023508 GPR08: 0001 c002536a 000e 0001 GPR12: 44002028 cfe80300 c00c3f00 c00363207c40 GPR16: GPR20: 0001 c0f630fc GPR24: 0001 fef7 c0f58638 GPR28: 0001 c003506f3900 2000 [241848.115585] NIP [c0954b60] .tcp_net_metrics_exit+0x60/0x110 [241848.115675] LR [c0954b68] .tcp_net_metrics_exit+0x68/0x110 [241848.115762] Call Trace: [241848.115805] [c00253eef9e0] [c0954b68] .tcp_net_metrics_exit+0x68/0x110 (unreliable) [241848.115945] [c00253eefa70] [c08cc49c] .ops_exit_list.isra.2+0x6c/0xd0 [241848.116078] [c00253eefb00] [c08ccef0] .cleanup_net+0x150/0x250 [241848.116198] [c00253eefbc0] [c00b9e28] .process_one_work+0x1a8/0x4d0 [241848.116320] [c00253eefc60] [c00baaf0] .worker_thread+0x180/0x4a0 [241848.116429] [c00253eefd30] [c00c4010] .kthread+0x110/0x130 [241848.116538] [c00253eefe30] [c000a160] .ret_from_kernel_thread+0x5c/0x7c [241848.116659] Instruction dump: [241848.116731] 7d295030 2f89 e93d0288 419e0058 3bc0 3b81 6000 6042 [241848.116920] 7bc81f24 7c69402a 2fa3 419e0024 4b8b809d 6000 2fbf [241848.117115] ---[ end trace 531dcfc8ed4b2948 ]--- [241848.124367] [241848.129853] Unable to handle kernel paging request for data at address 0xffd8 [241848.129968] Faulting instruction address: 0xc00c49c0 [241848.130056] Oops: Kernel access of bad area, sig: 11 [#2] [241848.130128] SMP NR_CPUS=2048 NUMA pSeries [241848.130220] Modules linked in: btrfs xor raid6_pq libcrc32c veth xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables dm_crypt [241848.130695] CPU: 0 PID: 10355 Comm: kworker/u4:0 Tainted: G D 3.13.0-8-generic #28-Ubuntu [241848.130833] task: c002192621f0 ti: c00253eec000 task.ti: c00253eec000 [241848.130938] NIP: c00c49c0 LR: c00bb278 CTR: c00ded80 [241848.131042] REGS: c00253d0 TRAP: 0300 Tainted: G D (3.13.0-8-generic) [241848.131145] MSR: 80009033 CR: 42004028 XER: [241848.131391] CFAR: 3fff90fa7250 DAR: ffd8 DSISR: 4000 SOFTE: 0 GPR00: c00bb278 c00253eef150 c10b0dd0 c002192621f0 GPR04: 0001 0800 GPR08: 0001 0001 0018 GPR12: 22004088 cfe8 0075a000 0001 GPR16: c0eee780 c0096c48 c110df34 GPR20: c0eee780 0001 0004 GPR24: c0eee780 c1109a60 c00253eec000 c0eee780 GPR28: c00219262690 c002192621f0 c002192621f0 [241848.132789] NIP [c00c49c0] .kthread_data+0x20/0x40 [241848.132861] LR [c00bb278] .wq_worker_sleeping+0x28/0xf0 [241848.132947] Call Trace: [241848.132988] [c00253eef150] [c002192632d4] 0xc002192632d4 (unreliable) [241848.133109] [c00253eef1d0] [c00bb278] .wq_worker_sleeping+0x28/0xf0 [241848.133231] [c00253eef260] [c0a14a7c] .__schedule+0
[Bug 1301496] Re: kernel crash: Unable to handle kernel paging request for data
000044
LEN TYPE
00001400020001034b
LEN TYPE
100802fe80000100080001007f0100
LEN TYPE127.0.0.1
2000080002007f0100000700036f6c
LEN TYPE127.0.0.1 LEN TYPElo
3000140006bb720054
LEN TYPE
40bb720054
400050
LEN TYPE
40001400020001
LEN TYPE
50034b18020080000c00080001
LEN TYPE
60000a820300080002000a820300080004
10.0.3.130 LEN TYPE10.0.3.130 LEN TYPE
70000aff030009000374653068
10.0.3.255 LEN TYPEeth0
8000140006bcc80054
LEN TYPE
90bcc80054
This looks a little bit like the sort of contents we might expect to see dumped
from a call to GETADDRS
against PF_UNSPEC which calls out to all of the inet{,6}_fill_ifaddr()
handlers, though nested:
[IFA_LOCAL(fe80...), IFA_ADDRESS(127.0.0.1), IFA_LOCAL(127.0.0.1),
IFA_LABEL(lo),IFA_CACHEINFO(...)]
[IFA_LOCAL(8000...??), IFA_ADDRESS(10.0.3.130), IFA_LOCAL(10.0.3.130),
IFA_BROADCAST(10.0.3.255), IFA_LABEL(eth0)]
Where:
IFA_LOCAL (16 bytes, ipv6 or 4 bytes, ipv4)
IFA_ADDRESS (4 bytes, ipv4)
IFA_BROADCAST (4 bytes, ipv4)
IFA_CACHEINFO (16 bytes)
--
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:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1301496/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1301496] Re: kernel crash: Unable to handle kernel paging request for data
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 the start of the page (and although most
elided here repeats on each page thereafter):
===
#include
static char b[65536 * 16];
main(int argc, char *argv[])
{
int p;
printf("%08lx\n", (long)b);
for (p = 0; p < sizeof(b); p++) {
if (b[p]) {
printf("%d != 0 @ %d [%08lx]\n", b[p], p, (long)&b[p]);
}
}
}
===
10011068
68 != 0 @ 61336 [1002]
20 != 0 @ 61340 [10020004]
2 != 0 @ 61342 [10020006]
1 != 0 @ 61344 [10020008]
75 != 0 @ 61348 [1002000c]
3 != 0 @ 61349 [1002000d]
2 != 0 @ 61352 [10020010]
8 != 0 @ 61353 [10020011]
[...]
68 != 0 @ 126872 [1003]
20 != 0 @ 126876 [10030004]
2 != 0 @ 126878 [10030006]
1 != 0 @ 126880 [10030008]
75 != 0 @ 126884 [1003000c]
3 != 0 @ 126885 [1003000d]
2 != 0 @ 126888 [10030010]
8 != 0 @ 126889 [10030011]
[...]
===
I also dumped the corruption in full in a more readable form, I would
note that this seems to contain 'lo' and 'eth0' as if it were networking
related:
===
000044001400020001034b
D \0 \0 \0 024 \0 002 \0 001 \0 \0 \0 K 003 \0 \0
100802fe80000100080001007f0100
002 \b 200 376 001 \0 \0 \0 \b \0 001 \0 177 \0 \0 001
2000080002007f0100000700036f6c
\b \0 002 \0 177 \0 \0 001 \a \0 003 \0 l o \0 \0
3000140006bb720054
024 \0 006 \0 377 377 377 377 377 377 377 377 r 273 T \0
40bb7200540050001400020001
r 273 T \0 P \0 \0 \0 024 \0 002 \0 001 \0 \0 \0
50034b18020080000c00080001
K 003 \0 \0 002 030 200 \0 \f \0 \0 \0 \b \0 001 \0
60000a820300080002000a820300080004
\n \0 003 202 \b \0 002 \0 \n \0 003 202 \b \0 004 \0
70000aff030009000374653068
\n \0 003 377 \t \0 003 \0 e t h 0 \0 \0 \0 \0
8000140006bcc80054
024 \0 006 \0 377 377 377 377 377 377 377 377 310 274 T \0
90bcc80054
310 274 T \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0
a0
\0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0
*
010044001400020001034b
===
I should note at this point that this differs from the corruption as
seen by @vorlon which showed a single bit change in each page.
--
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:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1301496/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1301496] Re: kernel crash: Unable to handle kernel paging request for data
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 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: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1301496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1301496] Re: kernel crash: Unable to handle kernel paging request for data
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 to handle kernel paging request for data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1301496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1301496] Re: kernel crash: Unable to handle kernel paging request for data
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, Segmentation fault.
filesdbinit () at ../../src/filesdb.c:571
571 ../../src/filesdb.c: No such file or directory.
(gdb) print bins
$1 = {0x0 , 0x1, 0x0 , 0x1,
0x0 , 0x1, 0x0 , 0x1,
0x0 , 0x1, 0x0 , 0x1,
0x0 , 0x1, 0x0 , 0x1,
0x0 , 0x1, 0x0 , 0x1,
0x0 , 0x1, 0x0 , 0x1,
0x0 , 0x1, 0x0 , 0x1,
0x0 , 0x1, 0x0 }
(gdb)
On a healthy system, this looks like:
(gdb) break filesdbinit
Breakpoint 2 at 0x10003338: file ../../src/filesdb.c, line 565.
(gdb) print bins
$12 = {0x0 }
(gdb)
Note that bins is an array of pointers.
(gdb) print sizeof(bins[0])
$6 = 8
(gdb)
So once every 8192 elements, there's a wrong bit in the array; 8192*8 is
64k of memory.
This could be a bug in any of the kernel, qemu, or the underlying host.
Note that after a reboot of wolfe, the VMs are reported to be stable
again for the past 72 hours (!). So it's possible this points to a bug
with the host OS/kernel.
There is a second P7 system, postal, which has been exhibiting the same
kinds of problems as wolfe. Adam can speak to this in more detail, and
facilitate any necessary diagnostics on postal.
--
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:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1301496/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1301496] Re: kernel crash: Unable to handle kernel paging request for data
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 paging request for data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1301496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1301496] Re: kernel crash: Unable to handle kernel paging request for data
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 because we continue on even after these failures. At some point dpkg-query starts SEGVing: Apr 3 20:57:54 wolfe-01 kernel: [ 4071.263070] dpkg-query[20115]: unhandled signal 11 at 00010028 nip 10003380 lr 10002968 code 30001 Apr 3 20:57:57 wolfe-01 kernel: [ 4074.437029] dpkg-query[20208]: unhandled signal 11 at 00010028 nip 10003380 lr 10002968 code 30001 Apr 3 20:58:00 wolfe-01 kernel: [ 4077.612284] dpkg-query[20291]: unhandled signal 11 at 00010028 nip 10003380 lr 10002968 code 30001 -- 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: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1301496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1301496] Re: kernel crash: Unable to handle kernel paging request for data
** 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.net/bugs/1301496 Title: kernel crash: Unable to handle kernel paging request for data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1301496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1301496] Re: kernel crash: Unable to handle kernel paging request for data
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 I got the syslog and the dmesg file off the server and will attach them to this report. ** Attachment added: "The /var/log/dmesg file from wolfe-01." https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1301496/+attachment/4064025/+files/dmesg -- 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: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1301496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1301496] Re: kernel crash: Unable to handle kernel paging request for data
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: linux (Ubuntu) Importance: Undecided => High ** Tags added: kernel-da-key ppc64el ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- 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: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1301496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1301496] Re: kernel crash: Unable to handle kernel paging request for data
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.836780] Unable to handle kernel paging request for data at address 0x00010001 [101168.836886] Faulting instruction address: 0xc0954b60 [101168.836934] Oops: Kernel access of bad area, sig: 11 [#1] [101168.836971] SMP NR_CPUS=2048 NUMA pSeries [101168.837020] Modules linked in: veth xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables dm_crypt [101168.837234] CPU: 1 PID: 19760 Comm: kworker/u4:0 Not tainted 3.13.0-8-generic #28-Ubuntu [101168.837294] Workqueue: netns .cleanup_net [101168.837332] task: c003f99d43e0 ti: c001cce44000 task.ti: c001cce44000 [101168.837386] NIP: c0954b60 LR: c0954b68 CTR: c0954b00 [101168.837439] REGS: c001cce47760 TRAP: 0300 Not tainted (3.13.0-8-generic) [101168.837493] MSR: 80009033 CR: 24002024 XER: [101168.837620] CFAR: 1063ea4c DAR: 00010001 DSISR: 4000 SOFTE: 1 GPR00: c0954b68 c001cce479e0 c10b0dd0 00010001 GPR04: f99918f0 c002be072380 c0954b68 c003fe023508 GPR08: 0001 c00209fc 000e 0001 GPR12: 44002028 cfe80300 c00c3f00 c002be1e8bc0 GPR16: GPR20: 0001 c0f630fc GPR24: 0001 fef7 c0f58638 GPR28: 0001 c003fbdc 2000 [101168.838355] NIP [c0954b60] .tcp_net_metrics_exit+0x60/0x110 [101168.838402] LR [c0954b68] .tcp_net_metrics_exit+0x68/0x110 [101168.838448] Call Trace: [101168.838469] [c001cce479e0] [c0954b68] .tcp_net_metrics_exit+0x68/0x110 (unreliable) [101168.838542] [c001cce47a70] [c08cc49c] .ops_exit_list.isra.2+0x6c/0xd0 [101168.838605] [c001cce47b00] [c08ccef0] .cleanup_net+0x150/0x250 [101168.838662] [c001cce47bc0] [c00b9e28] .process_one_work+0x1a8/0x4d0 [101168.838726] [c001cce47c60] [c00baaf0] .worker_thread+0x180/0x4a0 [101168.838783] [c001cce47d30] [c00c4010] .kthread+0x110/0x130 [101168.838841] [c001cce47e30] [c000a160] .ret_from_kernel_thread+0x5c/0x7c [101168.838903] Instruction dump: [101168.838940] 7d295030 2f89 e93d0288 419e0058 3bc0 3b81 6000 6042 [101168.839031] 7bc81f24 7c69402a 2fa3 419e0024 4b8b809d 6000 2fbf [101168.839127] ---[ end trace fb028b2b5c006a6a ]--- + --- + AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory + AplayDevices: Error: [Errno 2] No such file or directory + ApportVersion: 2.14-0ubuntu1 + Architecture: ppc64el + ArecordDevices: Error: [Errno 2] No such file or directory + CRDA: Error: [Errno 2] No such file or directory + DistroRelease: Ubuntu 14.04 + Lspci: + + Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: + + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-3.13.0-19-generic root=UUID=19eaa2f9-0f24-49b9-ba48-24879242481c ro console=hvc0 earlyprintk + ProcVersionSignature: User Name 3.13.0-19.40-generic 3.13.6 + RelatedPackageVersions: + linux-restricted-modules-3.13.0-19-generic N/A + linux-backports-modules-3.13.0-19-generic N/A + linux-firmware N/A + RfKill: Error: [Errno 2] No such file or directory + Tags: trusty uec-images + Uname: Linux 3.13.0-19-generic ppc64le + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video + WifiSyslog: + + _MarkForUpload: True ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/1301496/+attachment/4060971/+files/AudioDevicesInUse.txt -- 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: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1301496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1301496] Re: kernel crash: Unable to handle kernel paging request for data
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/bugs/1301496 Title: kernel crash: Unable to handle kernel paging request for data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1301496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1301496] Re: kernel crash: Unable to handle kernel paging request for data
** 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.launchpad.net/bugs/1301496 Title: kernel crash: Unable to handle kernel paging request for data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1301496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1301496] Re: kernel crash: Unable to handle kernel paging request for data
** 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.launchpad.net/bugs/1301496 Title: kernel crash: Unable to handle kernel paging request for data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1301496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
