Re: BUG: unable to handle kernel paging request at 00010016
On 21/08/2012 14:46, Neal Cardwell wrote: On Mon, Aug 20, 2012 at 8:05 PM, Dave Haywood wrote: Bisected to: 5d299f3d3c8a2fbc732b1bf03af36333ccec3130 is the first bad commit commit 5d299f3d3c8a2fbc732b1bf03af36333ccec3130 Author: Eric Dumazet Date: Mon Aug 6 05:09:33 2012 + net: ipv6: fix TCP early demux Yes, this is expected. There was a fix checked into the "net" tree yesterday: http://git.kernel.org/?p=linux/kernel/git/davem/net.git;a=commitdiff;h=fae6ef87faeb8853896920c68ee703d715799d28 Please let us know if that doesn't fix the crashes for you. Yes, this fixes the crash for me. Thanks! Dave. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: BUG: unable to handle kernel paging request at 00010016
On 21/08/2012 14:46, Neal Cardwell wrote: On Mon, Aug 20, 2012 at 8:05 PM, Dave Haywood t...@oak.selfip.net wrote: Bisected to: 5d299f3d3c8a2fbc732b1bf03af36333ccec3130 is the first bad commit commit 5d299f3d3c8a2fbc732b1bf03af36333ccec3130 Author: Eric Dumazet eduma...@google.com Date: Mon Aug 6 05:09:33 2012 + net: ipv6: fix TCP early demux Yes, this is expected. There was a fix checked into the net tree yesterday: http://git.kernel.org/?p=linux/kernel/git/davem/net.git;a=commitdiff;h=fae6ef87faeb8853896920c68ee703d715799d28 Please let us know if that doesn't fix the crashes for you. Yes, this fixes the crash for me. Thanks! Dave. -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: BUG: unable to handle kernel paging request at 00010016
On Mon, Aug 20, 2012 at 8:05 PM, Dave Haywood wrote: > Bisected to: > > 5d299f3d3c8a2fbc732b1bf03af36333ccec3130 is the first bad commit > > commit 5d299f3d3c8a2fbc732b1bf03af36333ccec3130 > > Author: Eric Dumazet > > Date: Mon Aug 6 05:09:33 2012 + > > net: ipv6: fix TCP early demux Yes, this is expected. There was a fix checked into the "net" tree yesterday: http://git.kernel.org/?p=linux/kernel/git/davem/net.git;a=commitdiff;h=fae6ef87faeb8853896920c68ee703d715799d28 Please let us know if that doesn't fix the crashes for you. thanks, neal -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: BUG: unable to handle kernel paging request at 00010016
On Mon, Aug 20, 2012 at 8:05 PM, Dave Haywood t...@oak.selfip.net wrote: Bisected to: 5d299f3d3c8a2fbc732b1bf03af36333ccec3130 is the first bad commit commit 5d299f3d3c8a2fbc732b1bf03af36333ccec3130 Author: Eric Dumazet eduma...@google.com Date: Mon Aug 6 05:09:33 2012 + net: ipv6: fix TCP early demux Yes, this is expected. There was a fix checked into the net tree yesterday: http://git.kernel.org/?p=linux/kernel/git/davem/net.git;a=commitdiff;h=fae6ef87faeb8853896920c68ee703d715799d28 Please let us know if that doesn't fix the crashes for you. thanks, neal -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: BUG: unable to handle kernel paging request at 00010016
On 19/08/2012 09:21, Artem Savkov wrote: On Sat, Aug 18, 2012 at 11:25:43PM -0500, Shaun Ruffell wrote: Adding linux-net to the CC list. On Fri, Aug 17, 2012 at 11:57:56PM +0100, Dave Haywood wrote: [1.] One line summary of the problem: BUG: unable to handle kernel paging request at 00010016 System boots then crashes a 5-10 or so seconds after getting to the login prompt Booting without the network cable attached prevents the crash (no evidence beyond 10 minutes after boot) Diagnostics: Captured the boot and managed a login + dmesg before the crash Some of the log looks corrupted. Probably my crappy usb dongle serial flow control but left it in anyway [snip] Just a note that I see this as well. It happens reliably for me after trying to login to the machine via ssh. Here is the back trace I collected on the serial port. There is a patch posted on netdev that fixes this for me: http://patchwork.ozlabs.org/patch/178525/ Bisected to: 5d299f3d3c8a2fbc732b1bf03af36333ccec3130 is the first bad commit commit 5d299f3d3c8a2fbc732b1bf03af36333ccec3130 Author: Eric Dumazet Date: Mon Aug 6 05:09:33 2012 + net: ipv6: fix TCP early demux IPv6 needs a cookie in dst_check() call. We need to add rx_dst_cookie and provide a family independent sk_rx_dst_set(sk, skb) method to properly support IPv6 TCP early demux. Signed-off-by: Eric Dumazet Signed-off-by: David S. Miller :04 04 96ade77f304a89c1886fbaa125b03d1f5699e418 485a021044b8f52ae8562e4e90d8f6536863f5e7 M include :04 04 1ebd6792af2014ad11979216b9a56504a28d5782 7a53fc9e7fb219c4cacb1bbb3b6867f30790dfd1 M net -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: BUG: unable to handle kernel paging request at 00010016
On 19/08/2012 09:21, Artem Savkov wrote: On Sat, Aug 18, 2012 at 11:25:43PM -0500, Shaun Ruffell wrote: Adding linux-net to the CC list. On Fri, Aug 17, 2012 at 11:57:56PM +0100, Dave Haywood wrote: [1.] One line summary of the problem: BUG: unable to handle kernel paging request at 00010016 System boots then crashes a 5-10 or so seconds after getting to the login prompt Booting without the network cable attached prevents the crash (no evidence beyond 10 minutes after boot) Diagnostics: Captured the boot and managed a login + dmesg before the crash Some of the log looks corrupted. Probably my crappy usb dongle serial flow control but left it in anyway [snip] Just a note that I see this as well. It happens reliably for me after trying to login to the machine via ssh. Here is the back trace I collected on the serial port. There is a patch posted on netdev that fixes this for me: http://patchwork.ozlabs.org/patch/178525/ Bisected to: 5d299f3d3c8a2fbc732b1bf03af36333ccec3130 is the first bad commit commit 5d299f3d3c8a2fbc732b1bf03af36333ccec3130 Author: Eric Dumazet eduma...@google.com Date: Mon Aug 6 05:09:33 2012 + net: ipv6: fix TCP early demux IPv6 needs a cookie in dst_check() call. We need to add rx_dst_cookie and provide a family independent sk_rx_dst_set(sk, skb) method to properly support IPv6 TCP early demux. Signed-off-by: Eric Dumazet eduma...@google.com Signed-off-by: David S. Miller da...@davemloft.net :04 04 96ade77f304a89c1886fbaa125b03d1f5699e418 485a021044b8f52ae8562e4e90d8f6536863f5e7 M include :04 04 1ebd6792af2014ad11979216b9a56504a28d5782 7a53fc9e7fb219c4cacb1bbb3b6867f30790dfd1 M net -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: BUG: unable to handle kernel paging request at 00010016
[ Fixing netdev cc to use proper dadress... ] On Sun, Aug 19, 2012 at 12:21:17PM +0400, Artem Savkov wrote: > On Sat, Aug 18, 2012 at 11:25:43PM -0500, Shaun Ruffell wrote: > > Adding linux-net to the CC list. > > > > On Fri, Aug 17, 2012 at 11:57:56PM +0100, Dave Haywood wrote: > > > [1.] One line summary of the problem: > > > BUG: unable to handle kernel paging request at 00010016 > > > > > > System boots then crashes a 5-10 or so seconds after getting to the > > > login prompt > > > Booting without the network cable attached prevents the crash (no > > > evidence beyond 10 minutes after boot) > > > > > > Diagnostics: > > > Captured the boot and managed a login + dmesg before the crash > > > Some of the log looks corrupted. Probably my crappy usb dongle serial > > > flow control but left it in anyway > > > > [snip] > > > > Just a note that I see this as well. It happens reliably for me after > > trying to > > login to the machine via ssh. > > > > Here is the back trace I collected on the serial port. > > There is a patch posted on netdev that fixes this for me: > http://patchwork.ozlabs.org/patch/178525/ Thanks, I just applied that patch and confirmed that it does indeed resolve the crash for me as well. Cheers, Shaun -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: BUG: unable to handle kernel paging request at 00010016
On Sat, Aug 18, 2012 at 11:25:43PM -0500, Shaun Ruffell wrote: > Adding linux-net to the CC list. > > On Fri, Aug 17, 2012 at 11:57:56PM +0100, Dave Haywood wrote: > > [1.] One line summary of the problem: > > BUG: unable to handle kernel paging request at 00010016 > > > > System boots then crashes a 5-10 or so seconds after getting to the > > login prompt > > Booting without the network cable attached prevents the crash (no > > evidence beyond 10 minutes after boot) > > > > Diagnostics: > > Captured the boot and managed a login + dmesg before the crash > > Some of the log looks corrupted. Probably my crappy usb dongle serial > > flow control but left it in anyway > > [snip] > > Just a note that I see this as well. It happens reliably for me after trying > to > login to the machine via ssh. > > Here is the back trace I collected on the serial port. There is a patch posted on netdev that fixes this for me: http://patchwork.ozlabs.org/patch/178525/ -- Kind regards, Artem -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: BUG: unable to handle kernel paging request at 00010016
On Sat, Aug 18, 2012 at 11:25:43PM -0500, Shaun Ruffell wrote: Adding linux-net to the CC list. On Fri, Aug 17, 2012 at 11:57:56PM +0100, Dave Haywood wrote: [1.] One line summary of the problem: BUG: unable to handle kernel paging request at 00010016 System boots then crashes a 5-10 or so seconds after getting to the login prompt Booting without the network cable attached prevents the crash (no evidence beyond 10 minutes after boot) Diagnostics: Captured the boot and managed a login + dmesg before the crash Some of the log looks corrupted. Probably my crappy usb dongle serial flow control but left it in anyway [snip] Just a note that I see this as well. It happens reliably for me after trying to login to the machine via ssh. Here is the back trace I collected on the serial port. There is a patch posted on netdev that fixes this for me: http://patchwork.ozlabs.org/patch/178525/ -- Kind regards, Artem -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: BUG: unable to handle kernel paging request at 00010016
[ Fixing netdev cc to use proper dadress... ] On Sun, Aug 19, 2012 at 12:21:17PM +0400, Artem Savkov wrote: On Sat, Aug 18, 2012 at 11:25:43PM -0500, Shaun Ruffell wrote: Adding linux-net to the CC list. On Fri, Aug 17, 2012 at 11:57:56PM +0100, Dave Haywood wrote: [1.] One line summary of the problem: BUG: unable to handle kernel paging request at 00010016 System boots then crashes a 5-10 or so seconds after getting to the login prompt Booting without the network cable attached prevents the crash (no evidence beyond 10 minutes after boot) Diagnostics: Captured the boot and managed a login + dmesg before the crash Some of the log looks corrupted. Probably my crappy usb dongle serial flow control but left it in anyway [snip] Just a note that I see this as well. It happens reliably for me after trying to login to the machine via ssh. Here is the back trace I collected on the serial port. There is a patch posted on netdev that fixes this for me: http://patchwork.ozlabs.org/patch/178525/ Thanks, I just applied that patch and confirmed that it does indeed resolve the crash for me as well. Cheers, Shaun -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: BUG: unable to handle kernel paging request at 00010016
Adding linux-net to the CC list. On Fri, Aug 17, 2012 at 11:57:56PM +0100, Dave Haywood wrote: > [1.] One line summary of the problem: > BUG: unable to handle kernel paging request at 00010016 > > System boots then crashes a 5-10 or so seconds after getting to the > login prompt > Booting without the network cable attached prevents the crash (no > evidence beyond 10 minutes after boot) > > Diagnostics: > Captured the boot and managed a login + dmesg before the crash > Some of the log looks corrupted. Probably my crappy usb dongle serial > flow control but left it in anyway [snip] > [6.] Output of Oops.. message (if applicable) with symbolic information > resolved (see Documentation/oops-tracing.txt) > [ 62.907899] BUG: unable to handle kernel paging request at 00010016 > [ 62.908002] IP: [] inet6_sk_rx_dst_set+0x29/0x40 > [ 62.908002] *pde = > [ 62.908002] Oops: [#1] SMP > [ 62.908002] Pid: 2168, comm: mprime Not tainted 3.6.0-rc2 #297 Compaq > Deskpro/06C4h > [ 62.908002] EIP: 0060:[] EFLAGS: 00010202 CPU: 0 > [ 62.908002] EIP is at inet6_sk_rx_dst_set+0x29/0x40 > [ 62.908002] EAX: ce738508 EBX: ce73a760 ECX: cf377000 EDX: 00010002 > [ 62.908002] ESI: ca06c900 EDI: ce738000 EBP: cf80bc7c ESP: cf80bc7c > [ 62.908002] DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 > [ 62.908002] CR0: 80050033 CR2: 00010016 CR3: 0a036000 CR4: 07d0 > [ 62.908002] DR0: DR1: DR2: DR3: > [ 62.908002] DR6: 0ff0 DR7: 0400 > [ 62.908002] Process mprime (pid: 2168, ti=cf80a000 task=ce4f7390 > task.ti=ca052000) > [ 62.908002] Stack: > [ 62.908002] cf80bc9c c15449cb ce436780 ce738508 > ca06c900 ce738000 > [ 62.908002] cf80bcc0 c154337e c167545e cf80bcec c124b318 ce436780 > ce738508 ce738000 > [ 62.908002] ce436780 cf80bd48 c15aff9d 0001 cf80bcec > c1236880 ce691ec0 > [ 62.908002] Call Trace: > [ 62.908002] [] tcp_create_openreq_child+0x3b/0x4a0 > [ 62.908002] [] tcp_v4_syn_recv_sock+0x2e/0x2a0 > [ 62.908002] [] ? _raw_spin_unlock_bh+0xe/0x10 > [ 62.908002] [] ? selinux_netlbl_sock_rcv_skb+0x18/0x190 > [ 62.908002] [] tcp_v6_syn_recv_sock+0x3ed/0x6d0 > [ 62.908002] [] ? selinux_parse_skb+0x50/0xb0 > [ 62.908002] [] tcp_check_req+0x283/0x450 > [ 62.908002] [] tcp_v4_hnd_req+0x51/0x140 > [ 62.908002] [] tcp_v4_do_rcv+0x129/0x1b0 > [ 62.908002] [] ? sk_filter+0x25/0xb0 > [ 62.908002] [] tcp_v4_rcv+0x5fe/0x730 > [ 62.908002] [] ? ip_rcv_finish+0x2f0/0x2f0 > [ 62.908002] [] ip_local_deliver_finish+0x8c/0x260 > [ 62.908002] [] ? inet_del_protocol+0x30/0x30 > [ 62.908002] [] ip_local_deliver+0x7f/0x90 > [ 62.908002] [] ? ip_rcv_finish+0x2f0/0x2f0 > [ 62.908002] [] ip_rcv_finish+0xf1/0x2f0 > [ 62.908002] [] ? inet_del_protocol+0x30/0x30 > [ 62.908002] [] ip_rcv+0x252/0x320 > [ 62.908002] [] ? inet_del_protocol+0x30/0x30 > [ 62.908002] [] __netif_receive_skb+0x46b/0x670 > [ 62.908002] [] netif_receive_skb+0x22/0x80 > [ 62.908002] [] rtl8139_rx+0xd2/0x370 > [ 62.908002] [] rtl8139_poll+0x42/0xb0 > [ 62.908002] [] net_rx_action+0xed/0x1c0 > [ 62.908002] [] ? fbcon_add_cursor_timer+0xd0/0xd0 > [ 62.908002] [] __do_softirq+0xa7/0x200 > [ 62.908002] [] ? local_bh_enable_ip+0x80/0x80 > [ 62.908002] > [ 62.908002] [] ? irq_exit+0x6e/0x90 > [ 62.908002] [] ? do_IRQ+0x46/0xb0 > [ 62.908002] [] ? irq_exit+0x57/0x90 > [ 62.908002] [] ? smp_apic_timer_interrupt+0x56/0x90 > [ 62.908002] [] ? common_interrupt+0x29/0x30 > [ 62.908002] Code: 90 90 55 8b 4a 48 89 e5 83 e1 fe 3e ff 41 40 89 88 8c 00 > 00 00 8b 52 74 89 90 cc 01 00 00 8b 51 58 85 d2 74 0c 8b 80 a0 01 00 00 <8b> > 52 14 89 50 68 5d c3 eb 0d 90 90 90 90 90 90 90 90 90 90 90 > [ 62.908002] EIP: [] inet6_sk_rx_dst_set+0x29/0x40 SS:ESP > 0068:cf80bc7c > [ 62.908002] CR2: 00010016 > [ 63.212118] ---[ end trace 1fcc7fe92846c9d3 ]--- > [ 63.216734] Kernel panic - not syncing: Fatal exception in interrupt Just a note that I see this as well. It happens reliably for me after trying to login to the machine via ssh. Here is the back trace I collected on the serial port. [ 67.258206] BUG: unable to handle kernel paging request at 00010016 [ 67.260010] IP: [] inet6_sk_rx_dst_set+0x3a/0x89 [ipv6] [ 67.260010] *pde = [ 67.260010] Oops: [#1] SMP [ 67.260010] Modules linked in: bluetooth rfkill crc16 lockd sunrpc ipv6 dm_multipath lp sg pcspkr serio_raw e1000 ata_piix libata floppy parport_pc pa rport e7xxx_edac edac_core ide_cd_mod cdrom intel_rng dm_snapshot dm_zero dm_mirror dm_region_hash dm_log dm_mod megaraid_mbox megaraid_mm sd_mod scs
Re: BUG: unable to handle kernel paging request at 00010016
Adding linux-net to the CC list. On Fri, Aug 17, 2012 at 11:57:56PM +0100, Dave Haywood wrote: [1.] One line summary of the problem: BUG: unable to handle kernel paging request at 00010016 System boots then crashes a 5-10 or so seconds after getting to the login prompt Booting without the network cable attached prevents the crash (no evidence beyond 10 minutes after boot) Diagnostics: Captured the boot and managed a login + dmesg before the crash Some of the log looks corrupted. Probably my crappy usb dongle serial flow control but left it in anyway [snip] [6.] Output of Oops.. message (if applicable) with symbolic information resolved (see Documentation/oops-tracing.txt) [ 62.907899] BUG: unable to handle kernel paging request at 00010016 [ 62.908002] IP: [c15acfc9] inet6_sk_rx_dst_set+0x29/0x40 [ 62.908002] *pde = [ 62.908002] Oops: [#1] SMP [ 62.908002] Pid: 2168, comm: mprime Not tainted 3.6.0-rc2 #297 Compaq Deskpro/06C4h [ 62.908002] EIP: 0060:[c15acfc9] EFLAGS: 00010202 CPU: 0 [ 62.908002] EIP is at inet6_sk_rx_dst_set+0x29/0x40 [ 62.908002] EAX: ce738508 EBX: ce73a760 ECX: cf377000 EDX: 00010002 [ 62.908002] ESI: ca06c900 EDI: ce738000 EBP: cf80bc7c ESP: cf80bc7c [ 62.908002] DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 [ 62.908002] CR0: 80050033 CR2: 00010016 CR3: 0a036000 CR4: 07d0 [ 62.908002] DR0: DR1: DR2: DR3: [ 62.908002] DR6: 0ff0 DR7: 0400 [ 62.908002] Process mprime (pid: 2168, ti=cf80a000 task=ce4f7390 task.ti=ca052000) [ 62.908002] Stack: [ 62.908002] cf80bc9c c15449cb ce436780 ce738508 ca06c900 ce738000 [ 62.908002] cf80bcc0 c154337e c167545e cf80bcec c124b318 ce436780 ce738508 ce738000 [ 62.908002] ce436780 cf80bd48 c15aff9d 0001 cf80bcec c1236880 ce691ec0 [ 62.908002] Call Trace: [ 62.908002] [c15449cb] tcp_create_openreq_child+0x3b/0x4a0 [ 62.908002] [c154337e] tcp_v4_syn_recv_sock+0x2e/0x2a0 [ 62.908002] [c167545e] ? _raw_spin_unlock_bh+0xe/0x10 [ 62.908002] [c124b318] ? selinux_netlbl_sock_rcv_skb+0x18/0x190 [ 62.908002] [c15aff9d] tcp_v6_syn_recv_sock+0x3ed/0x6d0 [ 62.908002] [c1236880] ? selinux_parse_skb+0x50/0xb0 [ 62.908002] [c15450b3] tcp_check_req+0x283/0x450 [ 62.908002] [c1541191] tcp_v4_hnd_req+0x51/0x140 [ 62.908002] [c1542e69] tcp_v4_do_rcv+0x129/0x1b0 [ 62.908002] [c14f5b45] ? sk_filter+0x25/0xb0 [ 62.908002] [c154407e] tcp_v4_rcv+0x5fe/0x730 [ 62.908002] [c15209b0] ? ip_rcv_finish+0x2f0/0x2f0 [ 62.908002] [c1520a3c] ip_local_deliver_finish+0x8c/0x260 [ 62.908002] [c15206c0] ? inet_del_protocol+0x30/0x30 [ 62.908002] [c1520d9f] ip_local_deliver+0x7f/0x90 [ 62.908002] [c15209b0] ? ip_rcv_finish+0x2f0/0x2f0 [ 62.908002] [c15207b1] ip_rcv_finish+0xf1/0x2f0 [ 62.908002] [c15206c0] ? inet_del_protocol+0x30/0x30 [ 62.908002] [c1521002] ip_rcv+0x252/0x320 [ 62.908002] [c15206c0] ? inet_del_protocol+0x30/0x30 [ 62.908002] [c14e19bb] __netif_receive_skb+0x46b/0x670 [ 62.908002] [c14e4b72] netif_receive_skb+0x22/0x80 [ 62.908002] [c13eb6e2] rtl8139_rx+0xd2/0x370 [ 62.908002] [c13eb9c2] rtl8139_poll+0x42/0xb0 [ 62.908002] [c14e56dd] net_rx_action+0xed/0x1c0 [ 62.908002] [c12c6110] ? fbcon_add_cursor_timer+0xd0/0xd0 [ 62.908002] [c10427a7] __do_softirq+0xa7/0x200 [ 62.908002] [c1042700] ? local_bh_enable_ip+0x80/0x80 [ 62.908002] IRQ [ 62.908002] [c1042b0e] ? irq_exit+0x6e/0x90 [ 62.908002] [c1004176] ? do_IRQ+0x46/0xb0 [ 62.908002] [c1042af7] ? irq_exit+0x57/0x90 [ 62.908002] [c10224a6] ? smp_apic_timer_interrupt+0x56/0x90 [ 62.908002] [c1676289] ? common_interrupt+0x29/0x30 [ 62.908002] Code: 90 90 55 8b 4a 48 89 e5 83 e1 fe 3e ff 41 40 89 88 8c 00 00 00 8b 52 74 89 90 cc 01 00 00 8b 51 58 85 d2 74 0c 8b 80 a0 01 00 00 8b 52 14 89 50 68 5d c3 eb 0d 90 90 90 90 90 90 90 90 90 90 90 [ 62.908002] EIP: [c15acfc9] inet6_sk_rx_dst_set+0x29/0x40 SS:ESP 0068:cf80bc7c [ 62.908002] CR2: 00010016 [ 63.212118] ---[ end trace 1fcc7fe92846c9d3 ]--- [ 63.216734] Kernel panic - not syncing: Fatal exception in interrupt Just a note that I see this as well. It happens reliably for me after trying to login to the machine via ssh. Here is the back trace I collected on the serial port. [ 67.258206] BUG: unable to handle kernel paging request at 00010016 [ 67.260010] IP: [f93a4ae6] inet6_sk_rx_dst_set+0x3a/0x89 [ipv6] [ 67.260010] *pde = [ 67.260010] Oops: [#1] SMP [ 67.260010] Modules linked in: bluetooth rfkill crc16 lockd sunrpc ipv6 dm_multipath lp sg pcspkr serio_raw e1000 ata_piix libata floppy parport_pc pa rport e7xxx_edac edac_core ide_cd_mod cdrom intel_rng dm_snapshot dm_zero dm_mirror dm_region_hash dm_log dm_mod megaraid_mbox megaraid_mm sd_mod scsi_mo d ext3 jbd uhci_hcd ohci_hcd
