[Bug 1251946] Re: Network related kernel panic on Atom 64bit system using saucy backport stack on precise

2014-03-09 Thread Launchpad Bug Tracker
[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/1251946

Title:
  Network related kernel panic on Atom 64bit system using saucy backport
  stack on precise

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251946/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1251946] Re: Network related kernel panic on Atom 64bit system using saucy backport stack on precise

2014-01-08 Thread Joseph Salisbury
I re-built the next test kernel, up to the following commit, which should have 
PPPoE enabled:
97ebe8f55ae99059c0ad3d3be5c0417647f5e3e0

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1251946

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1251946

Title:
  Network related kernel panic on Atom 64bit system using saucy backport
  stack on precise

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251946/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1251946] Re: Network related kernel panic on Atom 64bit system using saucy backport stack on precise

2014-01-07 Thread Joseph Salisbury
I built the next test kernel, up to the following commit:
97ebe8f55ae99059c0ad3d3be5c0417647f5e3e0

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1251946

Can you test that kernel and report back if it has the bug or not. I
will build the next test kernel based on your test results.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1251946

Title:
  Network related kernel panic on Atom 64bit system using saucy backport
  stack on precise

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251946/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1251946] Re: Network related kernel panic on Atom 64bit system using saucy backport stack on precise

2014-01-07 Thread Stéphane Graber
That kernel doesn't have PPPoE support so it's useless to me, I need a
distro kernel for those tests :)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1251946

Title:
  Network related kernel panic on Atom 64bit system using saucy backport
  stack on precise

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251946/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1251946] Re: Network related kernel panic on Atom 64bit system using saucy backport stack on precise

2014-01-03 Thread Stéphane Graber
Sorry for the delay, I just got back from a couple of weeks on another
continent so didn't feel like testing this remotely :)

I'll do a test run now. By the way, since I first reported this issue, I
managed to reproduce it on two more machines running the 3.11 kernel, it
seems to vary with the number of netfilter rules loaded, the more you
have, the more likely it's to panic (or something along those lines).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1251946

Title:
  Network related kernel panic on Atom 64bit system using saucy backport
  stack on precise

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251946/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1251946] Re: Network related kernel panic on Atom 64bit system using saucy backport stack on precise

2014-01-03 Thread Stéphane Graber
That kernel panics:

[   68.626968] [ cut here ]
[   68.631590] kernel BUG at 
/home/jsalisbury/bugs/lp1251946/linux-stable/net/core/skbuff.c:1040!
[   68.640188] invalid opcode:  [#1] SMP 
[   68.644324] Modules linked in: authenc esp6 xfrm6_mode_transport ipcomp6 
xfrm6_tunnel tunnel6 xfrm4_mode_tunnel xfrm6_mode_tunnel veth zram(C) xfrm_user 
xfe
[   68.747033] CPU 1 
[   68.748881] Pid: 12623, comm: samba Tainted: GWC   
3.7.0-030700-generic #201312051340  /D2500CC
[   68.759828] RIP: 0010:[815c0e76]  [815c0e76] 
pskb_expand_head+0x286/0x2d0
[   68.768358] RSP: 0018:88012fc83728  EFLAGS: 00010202
[   68.773664] RAX: 0002 RBX: 8800bd879100 RCX: 0020
[   68.780792] RDX:  RSI: 0050 RDI: 06c0
[   68.787916] RBP: 88012fc83768 R08: 3f2c68050060 R09: 3f2c68050060
[   68.795043] R10: bfcb2ffeff3e1602 R11: 20270ff0c0f20726 R12: 0050
[   68.802167] R13: 0020 R14: 0001 R15: 81697d80
[   68.809294] FS:  7ff55143d740() GS:88012fc8() 
knlGS:
[   68.817371] CS:  0010 DS:  ES:  CR0: 80050033
[   68.823112] CR2: 010dcff0 CR3: b0ab4000 CR4: 07e0
[   68.830237] DR0:  DR1:  DR2: 
[   68.837361] DR3:  DR6: 0ff0 DR7: 0400
[   68.844489] Process samba (pid: 12623, threadinfo 8800b0ad2000, task 
880125f5c560)
[   68.852738] Stack:
[   68.854754]  e8c8028c 0282 880127566d40 
8800bd879100
[   68.862227]  880115ee5000 8800a3bea000 0001 
81697d80
[   68.869680]  88012fc83798 8165b4d0 8800bd879100 
0001
[   68.877143] Call Trace:
[   68.879586]  IRQ 
[   68.881517]  [81697d80] ? xfrm6_extract_output+0x50/0x50
[   68.887918]  [8165b4d0] xfrm_output_one+0x90/0x220
[   68.893573]  [8165b726] xfrm_output_resume+0xc6/0x170
[   68.899486]  [8165b7e3] xfrm_output2+0x13/0x20
[   68.904791]  [8165b82f] xfrm_output+0x3f/0x100
[   68.910099]  [81697d99] xfrm6_output_finish+0x19/0x20
[   68.916013]  [816660f5] ip6_fragment+0x925/0xab0
[   68.921495]  [81697d80] ? xfrm6_extract_output+0x50/0x50
[   68.927666]  [81697a80] ? xfrm6_local_error+0x80/0x80
[   68.933580]  [81697b82] __xfrm6_output+0x102/0x170
[   68.939232]  [81697dca] xfrm6_output+0x2a/0x70
[   68.944541]  [816653c2] ip6_forward+0x242/0x650
[   68.949935]  [816663f0] ? ip6_output+0xb0/0xb0
[   68.955243]  [81666478] ip6_rcv_finish+0x88/0x90
[   68.960721]  [816663f0] ? ip6_output+0xb0/0xb0
[   68.966038]  [a01c6882] __ipv6_conntrack_in+0xe2/0x180 
[nf_conntrack_ipv6]
[   68.973770]  [815c0c60] ? pskb_expand_head+0x70/0x2d0
[   68.979688]  [a01c6945] ipv6_conntrack_in+0x25/0x30 
[nf_conntrack_ipv6]
[   68.987165]  [815f9e6f] nf_iterate+0x8f/0xd0
[   68.992299]  [81644a38] ? inet_frag_destroy+0xd8/0x120
[   68.998300]  [816663f0] ? ip6_output+0xb0/0xb0
[   69.003607]  [815f9f2d] nf_hook_slow+0x7d/0x150
[   69.008998]  [816663f0] ? ip6_output+0xb0/0xb0
[   69.014309]  [816663f0] ? ip6_output+0xb0/0xb0
[   69.019621]  [a0227f82] nf_ct_frag6_output+0xf2/0x100 
[nf_defrag_ipv6]
[   69.027009]  [816663f0] ? ip6_output+0xb0/0xb0
[   69.032320]  [a02270a8] ipv6_defrag.part.2+0x98/0xe0 
[nf_defrag_ipv6]
[   69.039628]  [a022711c] ipv6_defrag+0x2c/0x30 [nf_defrag_ipv6]
[   69.046324]  [815f9e6f] nf_iterate+0x8f/0xd0
[   69.051460]  [816663f0] ? ip6_output+0xb0/0xb0
[   69.056767]  [815f9f2d] nf_hook_slow+0x7d/0x150
[   69.062158]  [816663f0] ? ip6_output+0xb0/0xb0
[   69.067471]  [81666ac3] ipv6_rcv+0x2b3/0x390
[   69.072601]  [815cd732] __netif_receive_skb+0x602/0x760
[   69.078688]  [815cd890] ? __netif_receive_skb+0x760/0x760
[   69.084956]  [a02bfdd0] ? br_handle_local_finish+0x50/0x50 [bridge]
[   69.092081]  [815cd8b3] netif_receive_skb+0x23/0x90
[   69.097828]  [a02bff91] br_handle_frame_finish+0x1c1/0x2a0 [bridge]
[   69.104961]  [a02c0214] br_handle_frame+0x1a4/0x270 [bridge]
[   69.111491]  [a02c0070] ? br_handle_frame_finish+0x2a0/0x2a0 
[bridge]
[   69.118791]  [815cd34d] __netif_receive_skb+0x21d/0x760
[   69.124878]  [815ce0b1] process_backlog+0xb1/0x190
[   69.130534]  [810f66bd] ? __rcu_process_callbacks+0xad/0x160
[   69.137052]  [815cee44] net_rx_action+0x134/0x260
[   69.142618]  [81061325] ? __do_softirq+0x115/0x240
[   69.148272]  [810612d0] __do_softirq+0xc0/0x240
[   69.153667]  [816e5b1c] call_softirq+0x1c/0x30
[   69.158969]  EOI 
[   69.160901]  

[Bug 1251946] Re: Network related kernel panic on Atom 64bit system using saucy backport stack on precise

2013-12-18 Thread Joseph Salisbury
** Changed in: linux (Ubuntu)
   Status: Confirmed = Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1251946

Title:
  Network related kernel panic on Atom 64bit system using saucy backport
  stack on precise

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251946/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1251946] Re: Network related kernel panic on Atom 64bit system using saucy backport stack on precise

2013-12-06 Thread Joseph Salisbury
Ok, one more shot.  It looks like PPPOE wasn't enabled for amd64 in
mainline.  I enabled it and rebuilt a test kernel.

Again, its up to the following commit:
6be35c700f742e911ecedd07fcc43d4439922334

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1251946

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1251946

Title:
  Network related kernel panic on Atom 64bit system using saucy backport
  stack on precise

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251946/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1251946] Re: Network related kernel panic on Atom 64bit system using saucy backport stack on precise

2013-12-05 Thread Stéphane Graber
That kernel still doesn't have PPPoE support in its config...

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1251946

Title:
  Network related kernel panic on Atom 64bit system using saucy backport
  stack on precise

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251946/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1251946] Re: Network related kernel panic on Atom 64bit system using saucy backport stack on precise

2013-12-04 Thread Stéphane Graber
That kernel is still useless to me...

So I went looking a bit closer at your test kernels and it looks like
the problem is the config you're using, they simply lack PPPoE support
entirely...

root@sateda:~# grep -i pppoe /boot/config-3.7.0-030700rc5-generic

root@sateda:~# grep -i pppoe /boot/config-3.2.0-57-generic 
CONFIG_PPPOE=m

I suspect you'll want to enable that module and then restart the bisect
from the start so we can get relevant results.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1251946

Title:
  Network related kernel panic on Atom 64bit system using saucy backport
  stack on precise

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251946/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1251946] Re: Network related kernel panic on Atom 64bit system using saucy backport stack on precise

2013-12-04 Thread Joseph Salisbury
Thanks for finding that.  That config option is disabled in the mainline
config, so I'll now build the test kernels with a Saucy tree.

I built the first test kernel again, up to the following commit:
6be35c700f742e911ecedd07fcc43d4439922334

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1251946

Can you test that kernel and report back if it has the bug or not. I
will build the next test kernel based on your test results.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1251946

Title:
  Network related kernel panic on Atom 64bit system using saucy backport
  stack on precise

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251946/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1251946] Re: Network related kernel panic on Atom 64bit system using saucy backport stack on precise

2013-12-02 Thread Joseph Salisbury
I also skipped that commit, since we could not test it.

I built the next test kernel, up to the following commit:
abed9a6bf2bb79e94ac6d6127f70be2f9718bb33


The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1251946

Can you test that kernel and report back if it has the bug or not. I
will build the next test kernel based on your test results.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1251946

Title:
  Network related kernel panic on Atom 64bit system using saucy backport
  stack on precise

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251946/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1251946] Re: Network related kernel panic on Atom 64bit system using saucy backport stack on precise

2013-11-28 Thread Stéphane Graber
Same thing as your previous kernel, PPPoE doesn't work so my machine is
essentially useless and the panicing code path doesn't get exercised. So
the result is no idea.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1251946

Title:
  Network related kernel panic on Atom 64bit system using saucy backport
  stack on precise

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251946/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1251946] Re: Network related kernel panic on Atom 64bit system using saucy backport stack on precise

2013-11-26 Thread Joseph Salisbury
Thanks for testing.  I skipped that commit, since we could not test it.

I built the next test kernel, up to the following commit:
b1ca079e7eb6ca862247fe694f320367bd962a24

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1251946

Can you test that kernel and report back if it has the bug or not. I
will build the next test kernel based on your test results.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1251946

Title:
  Network related kernel panic on Atom 64bit system using saucy backport
  stack on precise

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251946/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1251946] Re: Network related kernel panic on Atom 64bit system using saucy backport stack on precise

2013-11-25 Thread Stéphane Graber
Sorry I didn't get back to you earlier, I needed reliable internet the
past few days. I'm doing a test run now.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1251946

Title:
  Network related kernel panic on Atom 64bit system using saucy backport
  stack on precise

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251946/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1251946] Re: Network related kernel panic on Atom 64bit system using saucy backport stack on precise

2013-11-25 Thread Stéphane Graber
Well, I'd if the kernels were there ;)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1251946

Title:
  Network related kernel panic on Atom 64bit system using saucy backport
  stack on precise

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251946/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1251946] Re: Network related kernel panic on Atom 64bit system using saucy backport stack on precise

2013-11-25 Thread Joseph Salisbury
Whoops, sorry, I pasted the incorrect URL to the test kernel.  It can be
downloaded from:

http://kernel.ubuntu.com/~jsalisbury/lp1251946.  And now that I look at
it, all the URLs were wrong.  Let me restart the bisect to ensure all
the tests were ok.

I'll post the next test kernel shortly.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1251946

Title:
  Network related kernel panic on Atom 64bit system using saucy backport
  stack on precise

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251946/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1251946] Re: Network related kernel panic on Atom 64bit system using saucy backport stack on precise

2013-11-25 Thread Joseph Salisbury
I built the first test kernel again, up to the following commit:
6be35c700f742e911ecedd07fcc43d4439922334

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1251946

Can you test that kernel and report back if it has the bug or not. I
will build the next test kernel based on your test results.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1251946

Title:
  Network related kernel panic on Atom 64bit system using saucy backport
  stack on precise

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251946/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1251946] Re: Network related kernel panic on Atom 64bit system using saucy backport stack on precise

2013-11-20 Thread Joseph Salisbury
Thanks for the update.  I'll build the next kernel based on your test
result.  The mainline kernel build script I am using just creates
generic kernel names.  However, the build timestamp should be different
between the kernels.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1251946

Title:
  Network related kernel panic on Atom 64bit system using saucy backport
  stack on precise

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251946/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1251946] Re: Network related kernel panic on Atom 64bit system using saucy backport stack on precise

2013-11-20 Thread Joseph Salisbury
I built the next test kernel, up to the following commit:
7bcb57cde66c19df378f3468ea342166a8a4504d

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1249719

Can you test that kernel and report back if it has the bug or not. I
will build the next test kernel based on your test results.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1251946

Title:
  Network related kernel panic on Atom 64bit system using saucy backport
  stack on precise

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251946/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1251946] Re: Network related kernel panic on Atom 64bit system using saucy backport stack on precise

2013-11-19 Thread Joseph Salisbury
I built the next test kernel, up to the following commit:
97ebe8f55ae99059c0ad3d3be5c0417647f5e3e0

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1249719

Can you test that kernel and report back if it has the bug or not. I
will build the next test kernel based on your test results.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1251946

Title:
  Network related kernel panic on Atom 64bit system using saucy backport
  stack on precise

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251946/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1251946] Re: Network related kernel panic on Atom 64bit system using saucy backport stack on precise

2013-11-19 Thread Stéphane Graber
No luck with that one either:

[  136.619649] [ cut here ]
[  136.624273] Kernel BUG at 81604508 [verbose debug info unavailable]
[  136.631238] invalid opcode:  [#1] SMP 
[  136.635382] Modules linked in: authenc esp6 xfrm6_mode_transport ipcomp6 
xfrm6_tunnel tunnel6 xfrm4_mode_tunnel xfrm6_mode_tunnel veth xfrm_user zram(C) 
xfe
[  136.740573] CPU: 1 PID: 13007 Comm: samba Tainted: GWC   
3.11.5-031105-generic #201311181306
[  136.749703] Hardware name:  /D2500CC, BIOS 
CCCDT10N.86A.0039.2013.0425.1625 04/25/2013
[  136.759012] task: 8800bd082ee0 ti: 8800b768e000 task.ti: 
8800b768e000
[  136.766496] RIP: 0010:[81604508]  [81604508] 
pskb_expand_head+0x288/0x2d0
[  136.775049] RSP: 0018:88012fc83688  EFLAGS: 00010202
[  136.780365] RAX: 0003 RBX: 8800b3e7b500 RCX: 0020
[  136.787505] RDX:  RSI: 0050 RDI: 06c0
[  136.794643] RBP: 88012fc836c8 R08: 3f2c7d050060 R09: 3f2c7d050060
[  136.801782] R10: bfcb2ffeff3e1602 R11: 20270ff0c0f20726 R12: 0050
[  136.808919] R13: 0020 R14: 0001 R15: 816e3880
[  136.816059] FS:  7f37ca7a2740() GS:88012fc8() 
knlGS:
[  136.824150] CS:  0010 DS:  ES:  CR0: 80050033
[  136.829902] CR2: 020fa630 CR3: b768 CR4: 07e0
[  136.837040] Stack:
[  136.839062]  e8c8064c 0286 880127ea9260 
8800b3e7b500
[  136.846536]  8801268c4800 8800b3ffcc40 0001 
816e3880
[  136.854023]  88012fc836f8 816a52e0 8800b3e7b500 
0001
[  136.861499] Call Trace:
[  136.863955]  IRQ 
[  136.865890]  [816e3880] ? xfrm6_extract_output+0x50/0x50
[  136.872303]  [816a52e0] xfrm_output_one+0x90/0x230
[  136.877965]  [816a5546] xfrm_output_resume+0xc6/0x170
[  136.883889]  [816a5603] xfrm_output2+0x13/0x20
[  136.889206]  [816a564f] xfrm_output+0x3f/0x100
[  136.894525]  [816e3899] xfrm6_output_finish+0x19/0x20
[  136.900448]  [816aff49] ip6_fragment+0x929/0xab0
[  136.905938]  [816e3880] ? xfrm6_extract_output+0x50/0x50
[  136.912122]  [816e34d0] ? xfrm6_local_rxpmtu+0x70/0x70
[  136.918133]  [816e35a2] __xfrm6_output+0xd2/0x180
[  136.923711]  [816e38ca] xfrm6_output+0x2a/0x70
[  136.929028]  [816af223] ip6_forward+0x243/0x640
[  136.934431]  [816b0240] ? ip6_output+0xb0/0xb0
[  136.939749]  [816b02c8] ip6_rcv_finish+0x88/0x90
[  136.945239]  [816b0240] ? ip6_output+0xb0/0xb0
[  136.950566]  [a024883d] __ipv6_conntrack_in+0xdd/0x180 
[nf_conntrack_ipv6]
[  136.958317]  [a0248905] ipv6_conntrack_in+0x25/0x30 
[nf_conntrack_ipv6]
[  136.965807]  [816408ff] nf_iterate+0x8f/0xd0
[  136.970951]  [816b0240] ? ip6_output+0xb0/0xb0
[  136.976266]  [816409bd] nf_hook_slow+0x7d/0x150
[  136.981668]  [816b0240] ? ip6_output+0xb0/0xb0
[  136.986988]  [816b0240] ? ip6_output+0xb0/0xb0
[  136.992310]  [a025d3e2] nf_ct_frag6_output+0xf2/0x100 
[nf_defrag_ipv6]
[  136.999711]  [816b0240] ? ip6_output+0xb0/0xb0
[  137.005035]  [a025c0a8] ipv6_defrag.part.2+0x98/0xe0 
[nf_defrag_ipv6]
[  137.012354]  [a025c11c] ipv6_defrag+0x2c/0x30 [nf_defrag_ipv6]
[  137.019063]  [816408ff] nf_iterate+0x8f/0xd0
[  137.024207]  [816b0240] ? ip6_output+0xb0/0xb0
[  137.029522]  [816409bd] nf_hook_slow+0x7d/0x150
[  137.034925]  [816b0240] ? ip6_output+0xb0/0xb0
[  137.040246]  [816b0a33] ipv6_rcv+0x313/0x3f0
[  137.045388]  [816114da] __netif_receive_skb_core+0x5ca/0x720
[  137.051919]  [81611651] __netif_receive_skb+0x21/0x70
[  137.057842]  [816116c3] netif_receive_skb+0x23/0x90
[  137.063601]  [a033c6af] br_pass_frame_up+0x9f/0x110 [bridge]
[  137.070140]  [a033c8fb] br_handle_frame_finish+0x1db/0x330 [bridge]
[  137.077287]  [a033cbe4] br_handle_frame+0x194/0x260 [bridge]
[  137.083827]  [a033ca50] ? br_handle_frame_finish+0x330/0x330 
[bridge]
[  137.091141]  [81611289] __netif_receive_skb_core+0x379/0x720
[  137.097671]  [81611651] __netif_receive_skb+0x21/0x70
[  137.103596]  [81611f11] process_backlog+0xb1/0x190
[  137.109260]  [81612754] net_rx_action+0x134/0x260
[  137.114837]  [8106a592] ? __do_softirq+0x162/0x280
[  137.120502]  [8106a510] __do_softirq+0xe0/0x280
[  137.125905]  [8172a95c] call_softirq+0x1c/0x30
[  137.131218]  EOI 
[  137.133152]  [81015e35] do_softirq+0x65/0xa0
[  137.138509]  [8106a1a4] local_bh_enable+0x94/0xa0
[  137.144086]  [816ad451] ip6_finish_output2+0x1e1/0x4b0
[  137.150097]  [816ad270] ? ip6_flush_pending_frames+0xb0/0xb0
[  137.156627]  

[Bug 1251946] Re: Network related kernel panic on Atom 64bit system using saucy backport stack on precise

2013-11-19 Thread Stéphane Graber
Hmm, is there actually any difference between those two kernels? the
uname in the panic appears identical.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1251946

Title:
  Network related kernel panic on Atom 64bit system using saucy backport
  stack on precise

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251946/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1251946] Re: Network related kernel panic on Atom 64bit system using saucy backport stack on precise

2013-11-18 Thread Joseph Salisbury
** Changed in: linux (Ubuntu)
   Importance: Undecided = High

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1251946

Title:
  Network related kernel panic on Atom 64bit system using saucy backport
  stack on precise

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251946/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1251946] Re: Network related kernel panic on Atom 64bit system using saucy backport stack on precise

2013-11-18 Thread Stéphane Graber
I tried the current -proposed kernel which seems considerably more
reliable, instead of panicing within a couple of minutes from the boot
it now does within 30min or so, current panic message is:

[ 1407.957715] [ cut here ]
[ 1407.962346] Kernel BUG at 815e1310 [verbose debug info unavailable]
[ 1407.969310] invalid opcode:  [#1] SMP 
[ 1407.973445] Modules linked in: authenc(F) esp6(F) xfrm6_mode_transport(F) 
ipcomp6(F) xfrm6_tunnel(F) tunnel6(F) xfrm4_mode_tunnel(F) xfrm6_mode_tunnel(F) 
v)
[ 1408.087941] CPU: 0 PID: 0 Comm: swapper/0 Tainted: GF
3.11.0-14-generic #21-Ubuntu
[ 1408.096465] Hardware name:  /D2500CC, BIOS 
CCCDT10N.86A.0039.2013.0425.1625 04/25/2013
[ 1408.105773] task: 81c15440 ti: 81c0 task.ti: 
81c0
[ 1408.113259] RIP: 0010:[815e1310]  [815e1310] 
pskb_expand_head+0x230/0x280
[ 1408.121810] RSP: 0018:88012fc036b0  EFLAGS: 00010202
[ 1408.127126] RAX: 0003 RBX: 8800b6d80e00 RCX: 0020
[ 1408.134267] RDX: 06d2 RSI: 0012 RDI: 8800b6d80e00
[ 1408.141404] RBP: 88012fc036e8 R08: 3f2c5c050060 R09: 3f2c5c050060
[ 1408.148543] R10: f5fe8db0e1a07e51 R11: 00270ff0c0f20726 R12: 0001
[ 1408.155681] R13: 0012 R14: 8800b6d80e00 R15: 88008933c17e
[ 1408.162822] FS:  () GS:88012fc0() 
knlGS:
[ 1408.170912] CS:  0010 DS:  ES:  CR0: 8005003b
[ 1408.176663] CR2: 028b5180 CR3: 000107f8f000 CR4: 07f0
[ 1408.183800] Stack:
[ 1408.185823]  0282 81cd2940 8800b6d80e00 
0001
[ 1408.193306]  880110c89000 8800b6d80e00 88008933c17e 
88012fc03720
[ 1408.200776]  8167f5d6 a009de62 88011ea25200 
8800b6d80e00
[ 1408.208260] Call Trace:
[ 1408.210716]  IRQ 
[ 1408.212650]  [8167f5d6] xfrm_output_resume+0xa6/0x390
[ 1408.218801]  [a009de62] ? __nf_conntrack_confirm+0x322/0x460 
[nf_conntrack]
[ 1408.226636]  [8167f920] xfrm_output+0x40/0x100
[ 1408.231954]  [816bc82c] xfrm6_output_finish+0x1c/0x20
[ 1408.237877]  [81689dbe] ip6_fragment+0x77e/0xa60
[ 1408.243367]  [816bc810] ? xfrm6_extract_output+0xe0/0xe0
[ 1408.249551]  [816bc5ef] __xfrm6_output+0xcf/0x170
[ 1408.255129]  [816bc85a] xfrm6_output+0x2a/0x70
[ 1408.260445]  [816890da] ip6_forward+0x29a/0x800
[ 1408.265851]  [81696a94] ? ip6_route_input+0xa4/0xd0
[ 1408.271599]  [8168a210] ? ip6_output+0xb0/0xb0
[ 1408.276917]  [8168a290] ip6_rcv_finish+0x80/0x90
[ 1408.282414]  [a010b86e] __ipv6_conntrack_in+0xce/0x1a0 
[nf_conntrack_ipv6]
[ 1408.290167]  [a010b9c7] ipv6_conntrack_in+0x27/0x30 
[nf_conntrack_ipv6]
[ 1408.297656]  [8161cc0b] nf_iterate+0x8b/0xa0
[ 1408.302801]  [8168a210] ? ip6_output+0xb0/0xb0
[ 1408.308117]  [8161cc94] nf_hook_slow+0x74/0x130
[ 1408.313521]  [8168a210] ? ip6_output+0xb0/0xb0
[ 1408.318846]  [a00fe213] nf_ct_frag6_output+0xe3/0x100 
[nf_defrag_ipv6]
[ 1408.326244]  [8168a210] ? ip6_output+0xb0/0xb0
[ 1408.331568]  [a00fd0ca] ipv6_defrag+0xba/0x100 [nf_defrag_ipv6]
[ 1408.338362]  [8168a210] ? ip6_output+0xb0/0xb0
[ 1408.343678]  [8161cc0b] nf_iterate+0x8b/0xa0
[ 1408.348825]  [8168a210] ? ip6_output+0xb0/0xb0
[ 1408.354138]  [8161cc94] nf_hook_slow+0x74/0x130
[ 1408.359542]  [8168a210] ? ip6_output+0xb0/0xb0
[ 1408.364863]  [8168aab8] ipv6_rcv+0x348/0x440
[ 1408.370004]  [815eed06] __netif_receive_skb_core+0x646/0x830
[ 1408.376534]  [815eef08] __netif_receive_skb+0x18/0x60
[ 1408.382457]  [815eef73] netif_receive_skb+0x23/0x90
[ 1408.388218]  [a01cb668] br_handle_frame_finish+0x1d8/0x3d0 [bridge]
[ 1408.395366]  [a01cb9d5] br_handle_frame+0x175/0x250 [bridge]
[ 1408.401895]  [815ee912] __netif_receive_skb_core+0x252/0x830
[ 1408.408429]  [81019e99] ? read_tsc+0x9/0x20
[ 1408.413484]  [815eef08] __netif_receive_skb+0x18/0x60
[ 1408.419408]  [815eef73] netif_receive_skb+0x23/0x90
[ 1408.425159]  [815ef9e0] napi_gro_receive+0x80/0xb0
[ 1408.430843]  [a004657f] e1000_receive_skb+0x7f/0xe0 [e1000e]
[ 1408.437389]  [a0047a1a] e1000_clean_rx_irq+0x24a/0x400 [e1000e]
[ 1408.444200]  [a004f534] e1000e_poll+0x94/0x310 [e1000e]
[ 1408.450295]  [815ef2ac] net_rx_action+0x11c/0x240
[ 1408.455873]  [81067397] __do_softirq+0xf7/0x240
[ 1408.461279]  [816f711c] call_softirq+0x1c/0x30
[ 1408.466594]  [81014bf5] do_softirq+0x55/0x90
[ 1408.471736]  [81067675] irq_exit+0xb5/0xc0
[ 1408.476707]  [816f7a16] do_IRQ+0x56/0xc0
[ 1408.481505]  [816ed02d] common_interrupt+0x6d/0x6d
[ 1408.487165]  EOI 
[ 1408.489099]  

[Bug 1251946] Re: Network related kernel panic on Atom 64bit system using saucy backport stack on precise

2013-11-18 Thread Stéphane Graber
And same thing reproduced after just a few seconds on the current 3.12
kernel:

[   54.047386] [ cut here ]
[   54.052018] Kernel BUG at 81607e40 [verbose debug info unavailable]
[   54.058985] invalid opcode:  [#1] SMP 
[   54.063118] Modules linked in: authenc(F) esp6(F) xfrm6_mode_transport(F) 
ipcomp6(F) xfrm6_tunnel(F) tunnel6(F) xfrm4_mode_tunnel(F) xfrm6_mode_tunnel(F) 
v)
[   54.174614] CPU: 1 PID: 13117 Comm: nsupdate Tainted: GF
3.12.0-2-generic #7-Ubuntu
[   54.183226] Hardware name:  /D2500CC, BIOS 
CCCDT10N.86A.0039.2013.0425.1625 04/25/2013
[   54.192532] task: 88009b38af60 ti: 880096142000 task.ti: 
880096142000
[   54.200018] RIP: 0010:[81607e40]  [81607e40] 
pskb_expand_head+0x230/0x280
[   54.208570] RSP: 0018:88012fc83840  EFLAGS: 00010202
[   54.213886] RAX: 0003 RBX: 8800a68cf800 RCX: 0020
[   54.221027] RDX: 0710 RSI: 0050 RDI: 8800a68cf800
[   54.228164] RBP: 88012fc83878 R08: 46f061feff3e1602 R09: 46f061feff3e1602
[   54.235304] R10: bfcb2ffeff3e1602 R11: 20104b7170040120 R12: 0001
[   54.242440] R13: 0050 R14: 8800a68cf800 R15: 8800a6973840
[   54.249581] FS:  7fdb85441700() GS:88012fc8() 
knlGS:
[   54.257672] CS:  0010 DS:  ES:  CR0: 80050033
[   54.263424] CR2: 7fdb80037fd8 CR3: 9b25b000 CR4: 07e0
[   54.270560] Stack:
[   54.272583]  0286 81cd5f80 8800a68cf800 
0001
[   54.280058]  8800c2321400 8800a68cf800 8800a6973840 
88012fc838b0
[   54.287535]  816a7986 a00a1cf2 8801286cbf00 
8800a68cf800
[   54.295021] Call Trace:
[   54.297475]  IRQ 
[   54.299410]  [816a7986] xfrm_output_resume+0xa6/0x390
[   54.305568]  [a00a1cf2] ? __nf_conntrack_confirm+0x322/0x460 
[nf_conntrack]
[   54.313404]  [816a7cd0] xfrm_output+0x40/0x100
[   54.318720]  [816b000a] ? ip6_xmit+0x27a/0x420
[   54.324037]  [816e500c] xfrm6_output_finish+0x1c/0x20
[   54.329962]  [816b223e] ip6_fragment+0x78e/0xa60
[   54.335450]  [816e4ff0] ? xfrm6_extract_output+0xe0/0xe0
[   54.341636]  [816b2680] ? ip6_output+0xb0/0xb0
[   54.346954]  [816e4dcf] __xfrm6_output+0xcf/0x170
[   54.352531]  [816e503a] xfrm6_output+0x2a/0x70
[   54.357849]  [816b1563] ip6_forward+0x293/0x7e0
[   54.363253]  [816bf0a4] ? ip6_route_input+0xa4/0xd0
[   54.369001]  [816b2680] ? ip6_output+0xb0/0xb0
[   54.374321]  [816b2700] ip6_rcv_finish+0x80/0x90
[   54.379815]  [a00f584e] __ipv6_conntrack_in+0xce/0x1a0 
[nf_conntrack_ipv6]
[   54.387569]  [a00f59a7] ipv6_conntrack_in+0x27/0x30 
[nf_conntrack_ipv6]
[   54.395061]  [81644a9b] nf_iterate+0x8b/0xa0
[   54.400204]  [816b2680] ? ip6_output+0xb0/0xb0
[   54.405519]  [81644b24] nf_hook_slow+0x74/0x130
[   54.410923]  [816b2680] ? ip6_output+0xb0/0xb0
[   54.416247]  [a00fc213] nf_ct_frag6_output+0xe3/0x100 
[nf_defrag_ipv6]
[   54.423647]  [816b2680] ? ip6_output+0xb0/0xb0
[   54.428968]  [a00fb0ca] ipv6_defrag+0xba/0x100 [nf_defrag_ipv6]
[   54.435764]  [816b2680] ? ip6_output+0xb0/0xb0
[   54.441080]  [81644a9b] nf_iterate+0x8b/0xa0
[   54.446227]  [816b2680] ? ip6_output+0xb0/0xb0
[   54.451543]  [81644b24] nf_hook_slow+0x74/0x130
[   54.456945]  [816b2680] ? ip6_output+0xb0/0xb0
[   54.462266]  [816b2fdc] ipv6_rcv+0x3fc/0x4f0
[   54.467407]  [81615db6] __netif_receive_skb_core+0x666/0x840
[   54.473939]  [81615fa8] __netif_receive_skb+0x18/0x60
[   54.479862]  [81616013] netif_receive_skb+0x23/0x90
[   54.485622]  [a01dc698] br_handle_frame_finish+0x1d8/0x3e0 [bridge]
[   54.492765]  [a01dca15] br_handle_frame+0x175/0x260 [bridge]
[   54.499300]  [816159b2] __netif_receive_skb_core+0x262/0x840
[   54.505831]  [81615fa8] __netif_receive_skb+0x18/0x60
[   54.511754]  [81616b6e] process_backlog+0xae/0x1a0
[   54.517419]  [8161638a] net_rx_action+0x15a/0x260
[   54.522998]  [81069b47] __do_softirq+0xf7/0x290
[   54.528401]  [8172255c] call_softirq+0x1c/0x30
[   54.533714]  EOI 
[   54.535647]  [81015d45] do_softirq+0x55/0x90
[   54.541010]  [81069174] local_bh_enable+0x94/0xa0
[   54.546588]  [816afa71] ip6_finish_output2+0x161/0x480
[   54.552600]  [816e79df] ? ipv6_select_ident+0xef/0x120
[   54.558611]  [816b223e] ip6_fragment+0x78e/0xa60
[   54.564101]  [816af910] ? ip6_flush_pending_frames+0xb0/0xb0
[   54.570633]  [816b2591] ip6_finish_output+0x81/0xc0
[   54.576384]  [816b260c] ip6_output+0x3c/0xb0
[   54.581526]  [816e7ab5] ip6_local_out+0x25/0x30
[   54.586931] 

[Bug 1251946] Re: Network related kernel panic on Atom 64bit system using saucy backport stack on precise

2013-11-18 Thread Joseph Salisbury
Can you give the latest 3.12 kernel[0] a test, to see if this is already
fixed in mainline?  If the bug still exits, we can perform a bisect to
find the commit that introduced this.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-trusty/

** Tags added: performing-bisect

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1251946

Title:
  Network related kernel panic on Atom 64bit system using saucy backport
  stack on precise

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251946/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1251946] Re: Network related kernel panic on Atom 64bit system using saucy backport stack on precise

2013-11-18 Thread Stéphane Graber
Same thing on a 3.8 kernel:

[  151.530274] [ cut here ]
[  151.534897] Kernel BUG at 815be3a8 [verbose debug info unavailable]
[  151.541849] invalid opcode:  [#1] SMP 
[  151.545978] Modules linked in: authenc(F) esp6(F) xfrm6_mode_transport(F) 
ipcomp6(F) xfrm6_tunnel(F) tunnel6(F) xfrm4_mode_tunnel(F) xfrm6_mode_tunnel(F) 
v)
[  151.657182] CPU 1 
[  151.659030] Pid: 13133, comm: samba Tainted: GF3.8.0-34-generic 
#49-Ubuntu  /D2500CC
[  151.669380] RIP: 0010:[815be3a8]  [815be3a8] 
pskb_expand_head+0x248/0x290
[  151.677916] RSP: 0018:88012fc83870  EFLAGS: 00010202
[  151.683223] RAX: 0002 RBX: 880010186200 RCX: 0020
[  151.690351] RDX: 0710 RSI: 0050 RDI: 880010186200
[  151.697474] RBP: 88012fc838a8 R08: 46f061feff3e1602 R09: 46f061feff3e1602
[  151.704599] R10: bfcb2ffeff3e1602 R11: 20104b7170040120 R12: 0001
[  151.711726] R13: 0050 R14: 0548 R15: 88011a3fc840
[  151.718853] FS:  7f78e5514740() GS:88012fc8() 
knlGS:
[  151.726930] CS:  0010 DS:  ES:  CR0: 80050033
[  151.732668] CR2: 03f1b3b0 CR3: b864 CR4: 07e0
[  151.739796] DR0:  DR1:  DR2: 
[  151.746921] DR3:  DR6: 0ff0 DR7: 0400
[  151.754047] Process samba (pid: 13133, threadinfo 8800b865a000, task 
880111e9dd00)
[  151.762297] Stack:
[  151.764314]  8106a555 0286 880010186200 
0001
[  151.771793]  8801167cb800 0548 88011a3fc840 
88012fc838e0
[  151.779248]  81656fa4 88012fc838e8 880010186a00 
880010186200
[  151.786713] Call Trace:
[  151.789161]  IRQ 
[  151.791084]  [8106a555] ? mod_timer+0x165/0x200
[  151.796690]  [81656fa4] xfrm_output_resume+0xa4/0x370
[  151.802604]  [81657283] xfrm_output2+0x13/0x20
[  151.807910]  [816572cb] xfrm_output+0x3b/0xe0
[  151.813130]  [81693529] xfrm6_output_finish+0x19/0x20
[  151.819044]  [81661a45] ip6_fragment+0x915/0xa60
[  151.824523]  [81693510] ? xfrm6_extract_output+0xe0/0xe0
[  151.830698]  [816933e9] __xfrm6_output+0x109/0x150
[  151.836352]  [8169355a] xfrm6_output+0x2a/0x70
[  151.841658]  [81660bce] ip6_forward+0x2ae/0x810
[  151.847052]  [8166dd69] ? ip6_route_input+0x99/0xc0
[  151.852793]  [81661d00] ? ip6_output+0xb0/0xb0
[  151.858099]  [81661d80] ip6_rcv_finish+0x80/0x90
[  151.863590]  [a011f7ef] __ipv6_conntrack_in+0xdf/0x180 
[nf_conntrack_ipv6]
[  151.871327]  [a011f917] ipv6_conntrack_in+0x27/0x30 
[nf_conntrack_ipv6]
[  151.878802]  [815f6216] nf_iterate+0x86/0xb0
[  151.883938]  [81661d00] ? ip6_output+0xb0/0xb0
[  151.889244]  [815f62b4] nf_hook_slow+0x74/0x130
[  151.894638]  [81661d00] ? ip6_output+0xb0/0xb0
[  151.899953]  [a0117e62] nf_ct_frag6_output+0xc2/0x100 
[nf_defrag_ipv6]
[  151.907339]  [81661d00] ? ip6_output+0xb0/0xb0
[  151.912651]  [a01170c8] ipv6_defrag+0xb8/0x100 [nf_defrag_ipv6]
[  151.919433]  [815f6216] nf_iterate+0x86/0xb0
[  151.924569]  [81661d00] ? ip6_output+0xb0/0xb0
[  151.929875]  [815f62b4] nf_hook_slow+0x74/0x130
[  151.935267]  [81661d00] ? ip6_output+0xb0/0xb0
[  151.940580]  [81662470] ipv6_rcv+0x350/0x440
[  151.945720]  [815ca252] __netif_receive_skb+0x6e2/0x890
[  151.951806]  [815ca5a0] ? process_backlog+0x1a0/0x1a0
[  151.957718]  [815ca5c3] netif_receive_skb+0x23/0x90
[  151.963467]  [a01a7012] br_handle_frame_finish+0x1c2/0x270 [bridge]
[  151.970599]  [a01a7226] br_handle_frame+0x166/0x270 [bridge]
[  151.977122]  [815ca082] __netif_receive_skb+0x512/0x890
[  151.983206]  [81068cb0] ? cascade+0xa0/0xa0
[  151.988255]  [815ca4c1] process_backlog+0xc1/0x1a0
[  151.993908]  [815cac99] net_rx_action+0x129/0x250
[  151.999477]  [8106115f] __do_softirq+0xcf/0x200
[  152.004869]  [816d725c] call_softirq+0x1c/0x30
[  152.010174]  EOI 
[  152.012106]  [81016605] do_softirq+0x75/0xb0
[  152.017459]  [81060ca4] local_bh_enable+0x94/0xa0
[  152.023026]  [815cc712] dev_queue_xmit+0x1b2/0x440
[  152.028679]  [8165eccc] ip6_finish_output2+0x26c/0x360
[  152.034678]  [81661a45] ip6_fragment+0x915/0xa60
[  152.040159]  [8165ea60] ? ip6_flush_pending_frames+0xb0/0xb0
[  152.046680]  [81661c11] ip6_finish_output+0x81/0xc0
[  152.052418]  [81661c8c] ip6_output+0x3c/0xb0
[  152.057552]  [816603f5] ip6_local_out+0x25/0x30
[  152.062946]  [816606eb] ip6_push_pending_frames+0x2eb/0x450
[  152.069382]  [816789b2] 

[Bug 1251946] Re: Network related kernel panic on Atom 64bit system using saucy backport stack on precise

2013-11-18 Thread Joseph Salisbury
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 latest kernel that did not have this
issue.

Can you test the following kernels and report back? We are looking for the 
first kernel version that exhibits this bug:
v3.3 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.3-precise/
v3.4 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-quantal/
v3.5 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5-quantal/
v3.6 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.6-quantal/
v3.7 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.7-raring/

You don't have to test every kernel, just up until the kernel that first
has this bug.

Thanks in advance!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1251946

Title:
  Network related kernel panic on Atom 64bit system using saucy backport
  stack on precise

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251946/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1251946] Re: Network related kernel panic on Atom 64bit system using saucy backport stack on precise

2013-11-18 Thread Stéphane Graber
I've been running the standard backported 3.5 kernel for an hour without
getting a panic.

I'm currently running a 3.11 debug kernel from Andy, once that one
panics (probably in the next hour), I'll then try the 3.6 and 3.7 you
linked above to try and figure out when the issue was introduced.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1251946

Title:
  Network related kernel panic on Atom 64bit system using saucy backport
  stack on precise

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251946/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1251946] Re: Network related kernel panic on Atom 64bit system using saucy backport stack on precise

2013-11-18 Thread Stéphane Graber
And just as I was typing that, Andy's kernel paniced, here's the dump:

[  580.009012] [ cut here ]
[  580.013637] kernel BUG at 
/home/apw/build/ubuntu-saucy/ubuntu-saucy/net/core/skbuff.c:1059!
[  580.021989] invalid opcode:  [#1] SMP 
[  580.026133] Modules linked in: authenc esp6 xfrm6_mode_transport ipcomp6 
xfrm6_tunnel tunnel6 xfrm4_mode_tunnel xfrm6_mode_tunnel veth xfrm_user 
xfrm4_tunne
[  580.115883] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.11.0-14-generic 
#21lp1251946v201311181709
[  580.124755] Hardware name:  /D2500CC, BIOS 
CCCDT10N.86A.0039.2013.0425.1625 04/25/2013
[  580.134063] task: 81c15440 ti: 81c0 task.ti: 
81c0
[  580.141548] RIP: 0010:[815e26be]  [815e26be] 
pskb_expand_head+0x23e/0x280
[  580.150099] RSP: 0018:88012fc036b0  EFLAGS: 00010202
[  580.155417] RAX: 0003 RBX: 88009d282700 RCX: 0020
[  580.162554] RDX: 06d2 RSI: 0012 RDI: 88009d282700
[  580.169693] RBP: 88012fc036e8 R08: 3f2c4b050060 R09: 3f2c4b050060
[  580.176833] R10: f5fe8db0e1a07e51 R11: 00270ff0c0f20726 R12: 0001
[  580.183969] R13: 0012 R14: 88009d282700 R15: 8800b28991fe
[  580.191110] FS:  () GS:88012fc0() 
knlGS:
[  580.199202] CS:  0010 DS:  ES:  CR0: 8005003b
[  580.204951] CR2: 7fd03715d000 CR3: 0001121c5000 CR4: 07f0
[  580.212090] Stack:
[  580.214112]  0282 81cd2940 88009d282700 
0001
[  580.221595]  880117c1c800 88009d282700 8800b28991fe 
88012fc03720
[  580.229057]  81680aa6 a00a5e62 88009d282c00 
88009d282700
[  580.236534] Call Trace:
[  580.238988]  IRQ 
[  580.240923]  [81680aa6] xfrm_output_resume+0xa6/0x390
[  580.247082]  [a00a5e62] ? __nf_conntrack_confirm+0x322/0x460 
[nf_conntrack]
[  580.254917]  [81680df0] xfrm_output+0x40/0x100
[  580.260235]  [816bdd1c] xfrm6_output_finish+0x1c/0x20
[  580.266156]  [8168b26d] ip6_fragment+0x77d/0xa60
[  580.271648]  [816bdd00] ? xfrm6_extract_output+0xe0/0xe0
[  580.277833]  [816bdadf] __xfrm6_output+0xcf/0x170
[  580.283409]  [816bdd4a] xfrm6_output+0x2a/0x70
[  580.288726]  [8168a58a] ip6_forward+0x29a/0x800
[  580.294130]  [81697f54] ? ip6_route_input+0xa4/0xd0
[  580.299881]  [8168b6c0] ? ip6_output+0xb0/0xb0
[  580.305198]  [8168b740] ip6_rcv_finish+0x80/0x90
[  580.310695]  [a012486e] __ipv6_conntrack_in+0xce/0x1a0 
[nf_conntrack_ipv6]
[  580.318448]  [a01249c7] ipv6_conntrack_in+0x27/0x30 
[nf_conntrack_ipv6]
[  580.325937]  [8161e04b] nf_iterate+0x8b/0xa0
[  580.331083]  [8168b6c0] ? ip6_output+0xb0/0xb0
[  580.336397]  [8161e0d4] nf_hook_slow+0x74/0x130
[  580.341799]  [8168b6c0] ? ip6_output+0xb0/0xb0
[  580.347127]  [a011b213] nf_ct_frag6_output+0xe3/0x100 
[nf_defrag_ipv6]
[  580.354524]  [8168b6c0] ? ip6_output+0xb0/0xb0
[  580.359847]  [a011a0ca] ipv6_defrag+0xba/0x100 [nf_defrag_ipv6]
[  580.366643]  [8168b6c0] ? ip6_output+0xb0/0xb0
[  580.371959]  [8161e04b] nf_iterate+0x8b/0xa0
[  580.377105]  [8168b6c0] ? ip6_output+0xb0/0xb0
[  580.382419]  [8161e0d4] nf_hook_slow+0x74/0x130
[  580.387823]  [8168b6c0] ? ip6_output+0xb0/0xb0
[  580.393143]  [8168bf68] ipv6_rcv+0x348/0x440
[  580.398284]  [815f01b6] __netif_receive_skb_core+0x646/0x830
[  580.404814]  [815f03b8] __netif_receive_skb+0x18/0x60
[  580.410740]  [815f0423] netif_receive_skb+0x23/0x90
[  580.416500]  [a01c7668] br_handle_frame_finish+0x1d8/0x3d0 [bridge]
[  580.423644]  [a01c79d5] br_handle_frame+0x175/0x250 [bridge]
[  580.430177]  [815efdc2] __netif_receive_skb_core+0x252/0x830
[  580.436708]  [81019ea9] ? read_tsc+0x9/0x20
[  580.441764]  [815f03b8] __netif_receive_skb+0x18/0x60
[  580.447690]  [815f0423] netif_receive_skb+0x23/0x90
[  580.453440]  [815f0df0] napi_gro_receive+0x80/0xb0
[  580.459122]  [a004657f] e1000_receive_skb+0x7f/0xe0 [e1000e]
[  580.465669]  [a0047a1a] e1000_clean_rx_irq+0x24a/0x400 [e1000e]
[  580.472478]  [a004f534] e1000e_poll+0x94/0x310 [e1000e]
[  580.478578]  [815f075c] net_rx_action+0x11c/0x240
[  580.484154]  [810673c7] __do_softirq+0xf7/0x240
[  580.489559]  [816f889c] call_softirq+0x1c/0x30
[  580.494874]  [81014bf5] do_softirq+0x55/0x90
[  580.500018]  [810676a5] irq_exit+0xb5/0xc0
[  580.504989]  [816f9196] do_IRQ+0x56/0xc0
[  580.509785]  [816ee7ed] common_interrupt+0x6d/0x6d
[  580.515445]  EOI 
[  580.517370]  [8101a429] ? sched_clock+0x9/0x10
[  580.522908]  [8104d386] ? native_safe_halt+0x6/0x10

[Bug 1251946] Re: Network related kernel panic on Atom 64bit system using saucy backport stack on precise

2013-11-18 Thread Stéphane Graber
It's now been 45min without a panic using the 3.6 mainline build, so
considering that one good and moving on to 3.7.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1251946

Title:
  Network related kernel panic on Atom 64bit system using saucy backport
  stack on precise

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251946/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1251946] Re: Network related kernel panic on Atom 64bit system using saucy backport stack on precise

2013-11-18 Thread Stéphane Graber
And it's now been over 30 minutes on 3.7 mainline still without any
crash.

Now getting the 3.8 mainline to confirm that one gives the same panic as
the Ubuntu 3.8 did.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1251946

Title:
  Network related kernel panic on Atom 64bit system using saucy backport
  stack on precise

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251946/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1251946] Re: Network related kernel panic on Atom 64bit system using saucy backport stack on precise

2013-11-18 Thread Stéphane Graber
Looks like the issue appeared with the 3.8 kernel, just a bit over two
minutes after booting the mainline 3.8 kernel:

[  127.201762] [ cut here ]
[  127.206379] Kernel BUG at 815cca98 [verbose debug info unavailable]
[  127.213331] invalid opcode:  [#1] SMP 
[  127.217459] Modules linked in: authenc esp6 xfrm6_mode_transport ipcomp6 
xfrm6_tunnel tunnel6 xfrm4_mode_tunnel xfrm6_mode_tunnel veth xfrm_user 
xfrm4_tunne
[  127.305010] CPU 0 
[  127.306856] Pid: 0, comm: swapper/0 Not tainted 3.8.0-030800-generic 
#201302181935  /D2500CC
[  127.316853] RIP: 0010:[815cca98]  [815cca98] 
pskb_expand_head+0x278/0x2c0
[  127.325391] RSP: 0018:88012fc03590  EFLAGS: 00010202
[  127.330697] RAX: 0002 RBX: 880129311300 RCX: 0020
[  127.337823] RDX:  RSI: 0012 RDI: 06c0
[  127.344949] RBP: 88012fc035d0 R08: 196ccefeff3e1602 R09: 196ccefeff3e1602
[  127.352074] R10: e9976c2389223888 R11: 201011b570040120 R12: 0012
[  127.359200] R13: 0020 R14: 0001 R15: 816a3e50
[  127.366326] FS:  () GS:88012fc0() 
knlGS:
[  127.374402] CS:  0010 DS:  ES:  CR0: 8005003b
[  127.380144] CR2: 00a7f7c0 CR3: 000107b86000 CR4: 07f0
[  127.387270] DR0:  DR1:  DR2: 
[  127.394395] DR3:  DR6: 0ff0 DR7: 0400
[  127.401521] Process swapper/0 (pid: 0, threadinfo 81c0, task 
81c15440)
[  127.409768] Stack:
[  127.411779]  e8c000e0 0286 880127d38b40 
880129311300
[  127.419249]  880118456c00 8800ad8bf180 0001 
816a3e50
[  127.426712]  88012fc03600 816674d0 880129311300 
0001
[  127.434178] Call Trace:
[  127.436628]  IRQ 
[  127.438559]  [816a3e50] ? xfrm6_extract_output+0x50/0x50
[  127.444950]  [816674d0] xfrm_output_one+0x90/0x220
[  127.450605]  [81667726] xfrm_output_resume+0xc6/0x170
[  127.456517]  [816677e3] xfrm_output2+0x13/0x20
[  127.461826]  [8166782f] xfrm_output+0x3f/0x100
[  127.467133]  [816a3e69] xfrm6_output_finish+0x19/0x20
[  127.473046]  [81672105] ip6_fragment+0x925/0xaa0
[  127.478525]  [816a3e50] ? xfrm6_extract_output+0x50/0x50
[  127.484698]  [816a3b50] ? xfrm6_local_error+0x80/0x80
[  127.490613]  [816a3c52] __xfrm6_output+0x102/0x170
[  127.496265]  [816a3e9a] xfrm6_output+0x2a/0x70
[  127.501575]  [816713d2] ip6_forward+0x242/0x650
[  127.506967]  [816723f0] ? ip6_output+0xb0/0xb0
[  127.512275]  [81672478] ip6_rcv_finish+0x88/0x90
[  127.517755]  [816723f0] ? ip6_output+0xb0/0xb0
[  127.523071]  [a011b882] __ipv6_conntrack_in+0xe2/0x180 
[nf_conntrack_ipv6]
[  127.530804]  [815cc890] ? pskb_expand_head+0x70/0x2c0
[  127.536722]  [a011b945] ipv6_conntrack_in+0x25/0x30 
[nf_conntrack_ipv6]
[  127.544197]  [816058ff] nf_iterate+0x8f/0xd0
[  127.549332]  [81650a08] ? inet_frag_destroy+0xd8/0x120
[  127.555332]  [816723f0] ? ip6_output+0xb0/0xb0
[  127.560638]  [816059bd] nf_hook_slow+0x7d/0x150
[  127.566032]  [816723f0] ? ip6_output+0xb0/0xb0
[  127.571342]  [816723f0] ? ip6_output+0xb0/0xb0
[  127.576652]  [a0115fa2] nf_ct_frag6_output+0xf2/0x100 
[nf_defrag_ipv6]
[  127.584042]  [816723f0] ? ip6_output+0xb0/0xb0
[  127.589353]  [a01150a8] ipv6_defrag.part.2+0x98/0xe0 
[nf_defrag_ipv6]
[  127.596660]  [a011511c] ipv6_defrag+0x2c/0x30 [nf_defrag_ipv6]
[  127.603355]  [816058ff] nf_iterate+0x8f/0xd0
[  127.608494]  [816723f0] ? ip6_output+0xb0/0xb0
[  127.613797]  [816059bd] nf_hook_slow+0x7d/0x150
[  127.619191]  [816723f0] ? ip6_output+0xb0/0xb0
[  127.624503]  [81672ac3] ipv6_rcv+0x2b3/0x390
[  127.629635]  [815d93d2] __netif_receive_skb+0x602/0x760
[  127.635720]  [815d9530] ? __netif_receive_skb+0x760/0x760
[  127.641989]  [a01b6de0] ? br_handle_local_finish+0x50/0x50 [bridge]
[  127.649112]  [815d9553] netif_receive_skb+0x23/0x90
[  127.654862]  [a01b6fa1] br_handle_frame_finish+0x1c1/0x2a0 [bridge]
[  127.661994]  [a01b7224] br_handle_frame+0x1a4/0x270 [bridge]
[  127.668523]  [a01b7080] ? br_handle_frame_finish+0x2a0/0x2a0 
[bridge]
[  127.675824]  [815d8fed] __netif_receive_skb+0x21d/0x760
[  127.681911]  [8101bb69] ? read_tsc+0x9/0x20
[  127.686957]  [815d9553] netif_receive_skb+0x23/0x90
[  127.692698]  [815d9c48] napi_gro_receive+0xe8/0x140
[  127.698453]  [a0016b5b] e1000_receive_skb+0x5b/0x70 [e1000e]
[  127.704989]  [a0018d02] e1000_clean_rx_irq+0x242/0x3e0 [e1000e]
[  127.711774]  

[Bug 1251946] Re: Network related kernel panic on Atom 64bit system using saucy backport stack on precise

2013-11-18 Thread Joseph Salisbury
Can you test the following kernels and report back?  We are looking for
the earliest kernel version that exhibits this bug:

v3.8-rc4: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-rc4-raring/

If v3.8-rc4 does not exhibit the bug then test v3.8-rc6:
v3.8-rc6: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-rc6-raring/

If v3.8-rc4 does exhibit the bug then test v3.8-rc2:
v3.8-rc2: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-rc2-raring

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1251946

Title:
  Network related kernel panic on Atom 64bit system using saucy backport
  stack on precise

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251946/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1251946] Re: Network related kernel panic on Atom 64bit system using saucy backport stack on precise

2013-11-18 Thread Stéphane Graber
rc4 is affected:
[   76.048846] [ cut here ]
[   76.053467] Kernel BUG at 815cf5b8 [verbose debug info unavailable]
[   76.060419] invalid opcode:  [#1] SMP 
[   76.064549] Modules linked in: authenc esp6 xfrm6_mode_transport ipcomp6 
xfrm6_tunnel tunnel6 xfrm4_mode_tunnel xfrm6_mode_tunnel veth xfrm_user 
xfrm4_tunne
[   76.150972] CPU 1 
[   76.152821] Pid: 13301, comm: samba Not tainted 3.8.0-030800rc4-generic 
#201301172335  /D2500CC
[   76.163086] RIP: 0010:[815cf5b8]  [815cf5b8] 
pskb_expand_head+0x278/0x2c0
[   76.171623] RSP: 0018:88012fc83728  EFLAGS: 00010202
[   76.176929] RAX: 0002 RBX: 8800be3ddd00 RCX: 0020
[   76.184054] RDX:  RSI: 0050 RDI: 06c0
[   76.191180] RBP: 88012fc83768 R08: 3f2c7d050060 R09: 3f2c7d050060
[   76.198307] R10: bfcb2ffeff3e1602 R11: 20270ff0c0f20726 R12: 0050
[   76.205431] R13: 0020 R14: 0001 R15: 816a6450
[   76.212557] FS:  7fccaaa4b740() GS:88012fc8() 
knlGS:
[   76.220633] CS:  0010 DS:  ES:  CR0: 80050033
[   76.226375] CR2: 7ff1d5664018 CR3: b6e18000 CR4: 07e0
[   76.233500] DR0:  DR1:  DR2: 
[   76.240625] DR3:  DR6: 0ff0 DR7: 0400
[   76.247751] Process samba (pid: 13301, threadinfo 8800b6e1e000, task 
8801175f1740)
[   76.256001] Stack:
[   76.258018]  88012fc9bfec 000180400040 880127b5c6e0 
8800be3ddd00
[   76.265472]  8801131ac800 8800b38a9c00 0001 
816a6450
[   76.272944]  88012fc83798 81669b70 8800be3ddd00 
0001
[   76.280416] Call Trace:
[   76.282868]  IRQ 
[   76.284799]  [816a6450] ? xfrm6_extract_output+0x50/0x50
[   76.291192]  [81669b70] xfrm_output_one+0x90/0x220
[   76.296845]  [81669dc6] xfrm_output_resume+0xc6/0x170
[   76.302758]  [81669e83] xfrm_output2+0x13/0x20
[   76.308064]  [81669ecf] xfrm_output+0x3f/0x100
[   76.313374]  [816a6469] xfrm6_output_finish+0x19/0x20
[   76.319287]  [81674785] ip6_fragment+0x925/0xaa0
[   76.324766]  [816a6450] ? xfrm6_extract_output+0x50/0x50
[   76.330940]  [816a6150] ? xfrm6_local_error+0x80/0x80
[   76.336853]  [816a6252] __xfrm6_output+0x102/0x170
[   76.342505]  [816a649a] xfrm6_output+0x2a/0x70
[   76.347815]  [81673a52] ip6_forward+0x242/0x650
[   76.353207]  [81674a70] ? ip6_output+0xb0/0xb0
[   76.358516]  [81674af8] ip6_rcv_finish+0x88/0x90
[   76.363997]  [81674a70] ? ip6_output+0xb0/0xb0
[   76.369311]  [a0108882] __ipv6_conntrack_in+0xe2/0x180 
[nf_conntrack_ipv6]
[   76.377044]  [815cf3b0] ? pskb_expand_head+0x70/0x2c0
[   76.382963]  [a0108945] ipv6_conntrack_in+0x25/0x30 
[nf_conntrack_ipv6]
[   76.390437]  [816083ff] nf_iterate+0x8f/0xd0
[   76.395571]  [816530a8] ? inet_frag_destroy+0xd8/0x120
[   76.401574]  [81674a70] ? ip6_output+0xb0/0xb0
[   76.406878]  [816084bd] nf_hook_slow+0x7d/0x150
[   76.412273]  [81674a70] ? ip6_output+0xb0/0xb0
[   76.417582]  [81674a70] ? ip6_output+0xb0/0xb0
[   76.422892]  [a0102fa2] nf_ct_frag6_output+0xf2/0x100 
[nf_defrag_ipv6]
[   76.430282]  [81674a70] ? ip6_output+0xb0/0xb0
[   76.435592]  [a01020a8] ipv6_defrag.part.2+0x98/0xe0 
[nf_defrag_ipv6]
[   76.442901]  [a010211c] ipv6_defrag+0x2c/0x30 [nf_defrag_ipv6]
[   76.449597]  [816083ff] nf_iterate+0x8f/0xd0
[   76.454734]  [81674a70] ? ip6_output+0xb0/0xb0
[   76.460038]  [816084bd] nf_hook_slow+0x7d/0x150
[   76.465432]  [81674a70] ? ip6_output+0xb0/0xb0
[   76.470743]  [81675143] ipv6_rcv+0x2b3/0x390
[   76.475874]  [815dbed2] __netif_receive_skb+0x602/0x760
[   76.481961]  [815dc030] ? __netif_receive_skb+0x760/0x760
[   76.488227]  [a018fde0] ? br_handle_local_finish+0x50/0x50 [bridge]
[   76.495353]  [815dc053] netif_receive_skb+0x23/0x90
[   76.501101]  [a018ffa1] br_handle_frame_finish+0x1c1/0x2a0 [bridge]
[   76.508234]  [a0190224] br_handle_frame+0x1a4/0x270 [bridge]
[   76.514762]  [a0190080] ? br_handle_frame_finish+0x2a0/0x2a0 
[bridge]
[   76.522064]  [815dbaed] __netif_receive_skb+0x21d/0x760
[   76.528149]  [815dc851] process_backlog+0xb1/0x190
[   76.533804]  [815dd5e4] net_rx_action+0x134/0x260
[   76.539372]  [810624a0] __do_softirq+0xc0/0x240
[   76.544766]  [816f549c] call_softirq+0x1c/0x30
[   76.550069]  EOI 
[   76.551999]  [81016835] do_softirq+0x65/0xa0
[   76.557354]  [810623d4] local_bh_enable+0x94/0xa0
[   76.562921]  [815de479] dev_queue_xmit+0x199/0x470
[   

[Bug 1251946] Re: Network related kernel panic on Atom 64bit system using saucy backport stack on precise

2013-11-18 Thread Stéphane Graber
and rc2 is also affected:

[   60.661389] [ cut here ]
[   60.666011] Kernel BUG at 815cc9e8 [verbose debug info unavailable]
[   60.672961] invalid opcode:  [#1] SMP 
[   60.677091] Modules linked in: authenc esp6 xfrm6_mode_transport ipcomp6 
xfrm6_tunnel tunnel6 xfrm4_mode_tunnel xfrm6_mode_tunnel veth xfrm_user 
xfrm4_tunne
[   60.763556] CPU 1 
[   60.765399] Pid: 13066, comm: nsupdate Not tainted 3.8.0-030800rc2-generic 
#201301022235  /D2500CC
[   60.775913] RIP: 0010:[815cc9e8]  [815cc9e8] 
pskb_expand_head+0x278/0x2c0
[   60.784451] RSP: 0018:88012fc83728  EFLAGS: 00010202
[   60.789758] RAX: 0002 RBX: 8800b2869e00 RCX: 0020
[   60.796884] RDX:  RSI: 0050 RDI: 06c0
[   60.804009] RBP: 88012fc83768 R08: 46f061feff3e1602 R09: 46f061feff3e1602
[   60.811135] R10: bfcb2ffeff3e1602 R11: 20104b7170040120 R12: 0050
[   60.818260] R13: 0020 R14: 0001 R15: 816a3860
[   60.825385] FS:  7f9d55f36700() GS:88012fc8() 
knlGS:
[   60.833463] CS:  0010 DS:  ES:  CR0: 80050033
[   60.839203] CR2: 7fa7bfab2f90 CR3: b13e8000 CR4: 07e0
[   60.846328] DR0:  DR1:  DR2: 
[   60.853455] DR3:  DR6: 0ff0 DR7: 0400
[   60.860580] Process nsupdate (pid: 13066, threadinfo 8800b2bfe000, task 
8800cebd5c80)
[   60.869088] Stack:
[   60.871099]  e8c80744 000180400040 880129380ac0 
8800b2869e00
[   60.878561]  880117395000 8801124968c0 0001 
816a3860
[   60.886032]  88012fc83798 81666f40 8800b2869e00 
0001
[   60.893486] Call Trace:
[   60.895929]  IRQ 
[   60.897861]  [816a3860] ? xfrm6_extract_output+0x50/0x50
[   60.904254]  [81666f40] xfrm_output_one+0x90/0x220
[   60.909907]  [81667196] xfrm_output_resume+0xc6/0x170
[   60.915819]  [81667253] xfrm_output2+0x13/0x20
[   60.921125]  [8166729f] xfrm_output+0x3f/0x100
[   60.926433]  [816a3879] xfrm6_output_finish+0x19/0x20
[   60.932348]  [81671b55] ip6_fragment+0x925/0xaa0
[   60.937828]  [816a3860] ? xfrm6_extract_output+0x50/0x50
[   60.944000]  [816a3560] ? xfrm6_local_error+0x80/0x80
[   60.949915]  [816a3662] __xfrm6_output+0x102/0x170
[   60.955567]  [816a38aa] xfrm6_output+0x2a/0x70
[   60.960875]  [81670e22] ip6_forward+0x242/0x650
[   60.966268]  [81671e40] ? ip6_output+0xb0/0xb0
[   60.971576]  [81671ec8] ip6_rcv_finish+0x88/0x90
[   60.977058]  [81671e40] ? ip6_output+0xb0/0xb0
[   60.982372]  [a00f2882] __ipv6_conntrack_in+0xe2/0x180 
[nf_conntrack_ipv6]
[   60.990106]  [815cc7e0] ? pskb_expand_head+0x70/0x2c0
[   60.996025]  [a00f2945] ipv6_conntrack_in+0x25/0x30 
[nf_conntrack_ipv6]
[   61.003498]  [816057ff] nf_iterate+0x8f/0xd0
[   61.008635]  [81671e40] ? ip6_output+0xb0/0xb0
[   61.013940]  [816058bd] nf_hook_slow+0x7d/0x150
[   61.019334]  [81671e40] ? ip6_output+0xb0/0xb0
[   61.024644]  [81671e40] ? ip6_output+0xb0/0xb0
[   61.029953]  [a00ecf82] nf_ct_frag6_output+0xf2/0x100 
[nf_defrag_ipv6]
[   61.037343]  [81671e40] ? ip6_output+0xb0/0xb0
[   61.042655]  [a00ec0a8] ipv6_defrag.part.2+0x98/0xe0 
[nf_defrag_ipv6]
[   61.049963]  [a00ec11c] ipv6_defrag+0x2c/0x30 [nf_defrag_ipv6]
[   61.056659]  [816057ff] nf_iterate+0x8f/0xd0
[   61.061794]  [81671e40] ? ip6_output+0xb0/0xb0
[   61.067100]  [816058bd] nf_hook_slow+0x7d/0x150
[   61.072494]  [81671e40] ? ip6_output+0xb0/0xb0
[   61.077804]  [81672513] ipv6_rcv+0x2b3/0x390
[   61.082937]  [815d92d2] __netif_receive_skb+0x602/0x760
[   61.089020]  [815d9430] ? __netif_receive_skb+0x760/0x760
[   61.095290]  [a0181de0] ? br_handle_local_finish+0x50/0x50 [bridge]
[   61.102416]  [815d9453] netif_receive_skb+0x23/0x90
[   61.108163]  [a0181fa1] br_handle_frame_finish+0x1c1/0x2a0 [bridge]
[   61.115297]  [a0182224] br_handle_frame+0x1a4/0x270 [bridge]
[   61.121823]  [a0182080] ? br_handle_frame_finish+0x2a0/0x2a0 
[bridge]
[   61.129124]  [815d8eed] __netif_receive_skb+0x21d/0x760
[   61.135214]  [816e88a5] ? _raw_spin_lock_irq+0x15/0x20
[   61.141214]  [8106b1e0] ? run_timer_softirq+0x1d0/0x2c0
[   61.147298]  [815d9c51] process_backlog+0xb1/0x190
[   61.152952]  [815da9e4] net_rx_action+0x134/0x260
[   61.158518]  [81062505] ? __do_softirq+0x115/0x240
[   61.164173]  [810624b0] __do_softirq+0xc0/0x240
[   61.169569]  [816f295c] call_softirq+0x1c/0x30
[   61.174871]  EOI 
[   61.176802]  [81016835] 

[Bug 1251946] Re: Network related kernel panic on Atom 64bit system using saucy backport stack on precise

2013-11-18 Thread Stéphane Graber
and same goes for rc1:

[   80.428925] [ cut here ]
[   80.433548] Kernel BUG at 815cc5d8 [verbose debug info unavailable]
[   80.440501] invalid opcode:  [#1] SMP 
[   80.444637] Modules linked in: authenc esp6 xfrm6_mode_transport ipcomp6 
xfrm6_tunnel tunnel6 xfrm4_mode_tunnel xfrm6_mode_tunnel veth xfrm_user 
xfrm4_tunne
[   80.531123] CPU 1 
[   80.532970] Pid: 12843, comm: samba Not tainted 3.8.0-030800rc1-generic 
#201212212135  /D2500CC
[   80.543235] RIP: 0010:[815cc5d8]  [815cc5d8] 
pskb_expand_head+0x278/0x2c0
[   80.551773] RSP: 0018:88012fc83728  EFLAGS: 00010202
[   80.557080] RAX: 0002 RBX: 88010fad3600 RCX: 0020
[   80.564204] RDX:  RSI: 0050 RDI: 06c0
[   80.571330] RBP: 88012fc83768 R08: 46f061feff3e1602 R09: 46f061feff3e1602
[   80.578456] R10: bfcb2ffeff3e1602 R11: 20104b7170040120 R12: 0050
[   80.585581] R13: 0020 R14: 0001 R15: 816a34a0
[   80.592708] FS:  7f393ae12740() GS:88012fc8() 
knlGS:
[   80.600784] CS:  0010 DS:  ES:  CR0: 80050033
[   80.606523] CR2: 013dfb78 CR3: b4c27000 CR4: 07e0
[   80.613651] DR0:  DR1:  DR2: 
[   80.620774] DR3:  DR6: 0ff0 DR7: 0400
[   80.627900] Process samba (pid: 12843, threadinfo 8800b4c3a000, task 
8800bc915c80)
[   80.636150] Stack:
[   80.638160]  88012fc9bff8 0282 880127e10360 
88010fad3600
[   80.645614]  880118bfe400 8800cdb47c00 0001 
816a34a0
[   80.653069]  88012fc83798 81666b80 88010fad3600 
0001
[   80.660541] Call Trace:
[   80.662991]  IRQ 
[   80.664922]  [816a34a0] ? xfrm6_extract_output+0x50/0x50
[   80.671314]  [81666b80] xfrm_output_one+0x90/0x220
[   80.676968]  [81666dd6] xfrm_output_resume+0xc6/0x170
[   80.682882]  [81666e93] xfrm_output2+0x13/0x20
[   80.688188]  [81666edf] xfrm_output+0x3f/0x100
[   80.693497]  [816a34b9] xfrm6_output_finish+0x19/0x20
[   80.699410]  [81671795] ip6_fragment+0x925/0xaa0
[   80.704891]  [816a34a0] ? xfrm6_extract_output+0x50/0x50
[   80.711064]  [816a31a0] ? xfrm6_local_error+0x80/0x80
[   80.716977]  [816a32a2] __xfrm6_output+0x102/0x170
[   80.722631]  [816a34ea] xfrm6_output+0x2a/0x70
[   80.727939]  [81670a62] ip6_forward+0x242/0x650
[   80.71]  [81671a80] ? ip6_output+0xb0/0xb0
[   80.738638]  [81671b08] ip6_rcv_finish+0x88/0x90
[   80.744119]  [81671a80] ? ip6_output+0xb0/0xb0
[   80.749434]  [a0111882] __ipv6_conntrack_in+0xe2/0x180 
[nf_conntrack_ipv6]
[   80.757168]  [815cc3d0] ? pskb_expand_head+0x70/0x2c0
[   80.763086]  [a0111945] ipv6_conntrack_in+0x25/0x30 
[nf_conntrack_ipv6]
[   80.770562]  [8160545f] nf_iterate+0x8f/0xd0
[   80.775698]  [81671a80] ? ip6_output+0xb0/0xb0
[   80.781001]  [8160551d] nf_hook_slow+0x7d/0x150
[   80.786397]  [81671a80] ? ip6_output+0xb0/0xb0
[   80.791707]  [81671a80] ? ip6_output+0xb0/0xb0
[   80.797016]  [a010bf82] nf_ct_frag6_output+0xf2/0x100 
[nf_defrag_ipv6]
[   80.804404]  [81671a80] ? ip6_output+0xb0/0xb0
[   80.809718]  [a010b0a8] ipv6_defrag.part.2+0x98/0xe0 
[nf_defrag_ipv6]
[   80.817024]  [a010b11c] ipv6_defrag+0x2c/0x30 [nf_defrag_ipv6]
[   80.823719]  [8160545f] nf_iterate+0x8f/0xd0
[   80.828856]  [81671a80] ? ip6_output+0xb0/0xb0
[   80.834161]  [8160551d] nf_hook_slow+0x7d/0x150
[   80.839555]  [81671a80] ? ip6_output+0xb0/0xb0
[   80.844865]  [81672153] ipv6_rcv+0x2b3/0x390
[   80.849998]  [815d8ec2] __netif_receive_skb+0x602/0x760
[   80.856084]  [815d9020] ? __netif_receive_skb+0x760/0x760
[   80.862350]  [a0188dd0] ? br_handle_local_finish+0x50/0x50 [bridge]
[   80.869476]  [815d9043] netif_receive_skb+0x23/0x90
[   80.875224]  [a0188f91] br_handle_frame_finish+0x1c1/0x2a0 [bridge]
[   80.882358]  [a0189214] br_handle_frame+0x1a4/0x270 [bridge]
[   80.86]  [a0189070] ? br_handle_frame_finish+0x2a0/0x2a0 
[bridge]
[   80.896186]  [815d8add] __netif_receive_skb+0x21d/0x760
[   80.902275]  [810977cd] ? reweight_entity+0x14d/0x160
[   80.908186]  [815d9841] process_backlog+0xb1/0x190
[   80.913839]  [815da5d4] net_rx_action+0x134/0x260
[   80.919409]  [81062430] __do_softirq+0xc0/0x240
[   80.924802]  [816f25dc] call_softirq+0x1c/0x30
[   80.930107]  EOI 
[   80.932037]  [81016835] do_softirq+0x65/0xa0
[   80.937391]  [81062364] local_bh_enable+0x94/0xa0
[   80.942956]  [815db4d9] dev_queue_xmit+0x199/0x470
[ 

[Bug 1251946] Re: Network related kernel panic on Atom 64bit system using saucy backport stack on precise

2013-11-18 Thread Joseph Salisbury
I'll start a bisect between v3.7 and v3.8-rc1 and post a test kernel
shortly.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1251946

Title:
  Network related kernel panic on Atom 64bit system using saucy backport
  stack on precise

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251946/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1251946] Re: Network related kernel panic on Atom 64bit system using saucy backport stack on precise

2013-11-18 Thread Joseph Salisbury
In addition to the bisect, I'll poke through the git logs and see if a
change sticks out, as well as look upstream for similar issues.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1251946

Title:
  Network related kernel panic on Atom 64bit system using saucy backport
  stack on precise

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251946/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1251946] Re: Network related kernel panic on Atom 64bit system using saucy backport stack on precise

2013-11-18 Thread Joseph Salisbury
I started a kernel bisect between v3.7 and v3.8-rc1. The kernel bisect
will require testing of about 7-10 test kernels.

I built the first test kernel, up to the following commit:
6be35c700f742e911ecedd07fcc43d4439922334

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1249719

Can you test that kernel and report back if it has the bug or not. I
will build the next test kernel based on your test results.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1251946

Title:
  Network related kernel panic on Atom 64bit system using saucy backport
  stack on precise

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251946/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1251946] Re: Network related kernel panic on Atom 64bit system using saucy backport stack on precise

2013-11-18 Thread Stéphane Graber
That kernel panics:

[   65.076034] [ cut here ] 

  
[   65.080663] Kernel BUG at 81604508 [verbose debug info unavailable]  

  
[   65.087628] invalid opcode:  [#1] SMP

  
[   65.091771] Modules linked in: authenc esp6 xfrm6_mode_transport ipcomp6 
xfrm6_tunnel tunnel6 xfrm4_mode_tunnel xfrm6_mode_tunnel veth xfrm_user zram(C) 
xfrm4_tunnel e
[   65.196955] CPU: 0 PID: 12938 Comm: nsupdate Tainted: GWC   
3.11.5-031105-generic #201311181306 
   
[   65.206343] Hardware name:  /D2500CC, BIOS 
CCCDT10N.86A.0039.2013.0425.1625 04/25/2013 

[   65.215652] task: 880125d24650 ti: 8800aa40a000 task.ti: 
8800aa40a000
  
[   65.223137] RIP: 0010:[81604508]  [81604508] 
pskb_expand_head+0x288/0x2d0
  
[   65.231688] RSP: 0018:88012fc03688  EFLAGS: 00010202 

  
[   65.237005] RAX: 0003 RBX: 88012619ee00 RCX: 
0020
  
[   65.244145] RDX:  RSI: 0050 RDI: 
06c0
  
[   65.251283] RBP: 88012fc036c8 R08: 3f2c7e050060 R09: 
3f2c7e050060
  
[   65.258422] R10: bfcb2ffeff3e1602 R11: 20270ff0c0f20726 R12: 
0050
  
[   65.265560] R13: 0020 R14: 0001 R15: 
816e3880
  
[   65.272699] FS:  7f2688d2e700() GS:88012fc0() 
knlGS:  
 
[   65.280791] CS:  0010 DS:  ES:  CR0: 80050033

  
[   65.286541] CR2: 7f268d12b000 CR3: aa76b000 CR4: 
07f0
  
[   65.293680] Stack:   

  
[   65.295700]  e8c00690 000180400040 88012757f260 
88012619ee00
   
[   65.303187]  8801260c7800 880106a66000 0001 
816e3880
   
[   65.310670]  88012fc036f8 816a52e0 88012619ee00 
0001
   
[   65.318155] Call Trace:  

  
[   65.320613]  IRQ   

  
[   65.322548]  [816e3880] ? xfrm6_extract_output+0x50/0x50   

  
[   65.328950]  [816a52e0] xfrm_output_one+0x90/0x230 

  
[   65.334615]  [816a5546] xfrm_output_resume+0xc6/0x170  

  
[   65.340538]  [816a5603] xfrm_output2+0x13/0x20 

  
[   65.345854]  [816a564f] xfrm_output+0x3f/0x100 

  
[   65.351171]  [816e3899] xfrm6_output_finish+0x19/0x20  
   

[Bug 1251946] Re: Network related kernel panic on Atom 64bit system using saucy backport stack on precise

2013-11-16 Thread Stéphane Graber
Moving to Confirmed to make the bot happy, I believe all immediately
useful information is above, let me know if you need more.

** 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/1251946

Title:
  Network related kernel panic on Atom 64bit system using saucy backport
  stack on precise

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251946/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs