From: Romain Francoise <romain@orebokech.com>
To: Pete Clements <clem@clem.clem-digital.net>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
David Miller <davem@davemloft.net>,
Eric Dumazet <eric.dumazet@gmail.com>
Subject: Re: 3.6-rc2 Panic -- Network interrupt
Date: Fri, 17 Aug 2012 23:13:15 +0200 [thread overview]
Message-ID: <87pq6pb4t0.fsf@silenus.orebokech.com> (raw)
In-Reply-To: <201208171820.q7HIKB34001961@clem.clem-digital.net> (Pete Clements's message of "Fri, 17 Aug 2012 14:20:11 -0400 (EDT)")
Pete Clements <clem@clem.clem-digital.net> writes:
> Fyi:
> Get below panic with 3.6-rc2 soon after boot (hand copy of screen).
> [<c11ec9b6>] ? tcp_v4_rcv+0x626/0x740
> [<C11ccecf>] ? ip_local_deliver_finish+0x6f/0x120
> [<c11cce60>] ? ip_rcv+0x2b0/0x2b0
> [<c11cc9c3>] ? ip_rcv_finish+0xe3/0x2d0
> [<c11ae0a8>] ? __netif_receive_skb+03a8/0x4a0
> [<c11ae20b>] ? process_backlog+0x6b/0x100
> [<c11ae4aa>] ? net_rx_action+07a/0x100
> [<c102769f>] ? __do_softirq+0x7f/0x120
> [<c1027620>] ? irq_enter+0x50/0x50
> <IRQ>
> [<c10274b5>] ? irq_exit+0x55/0x60
> [<c1003a23>] ? do_IRQ+0x43/0xa0
> [<c121cc29>] ? common_interrupt+0x29/0x30
> [<c1007f44>] ? default_idle+0x14/0x30
> [<c1006116>] ? cpu_idle+0x26/0x40
> [<c12d490a>] ? start_kernel+0x244/0x249
> [<c12d4545>] ? kernel_init+0x16e/0x16e
> Code: a9 ff ff e9 14 ff ff ff 90 8b 4a 48 83 e1 fe ff 41 40 89 48 78 8b 52 70 89
> 90 84 01 00 00 8b 51 58 85 d2 74 8c 8b 80 58 01 00 00 <8b> 52 14 89 50 68 c3 8d
> b4 26 00 00 00 00 83 ec 84 0f b6 50 0e
> EIP: [<d8886332>] inet6_sk_rx_dst_set+0x22/0x30 [ipv6] SS:ESP 0068:d7000dcc
> CR2:0000000000010016
> ---[ end trace 71149a645a111f5d ]---
> Kernel panic - not syncing: Fatal exception in interrupt
Maybe related to the IPv6 early demux patches? Adding Cc's.
prev parent reply other threads:[~2012-08-17 21:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-17 18:20 3.6-rc2 Panic -- Network interrupt Pete Clements
2012-08-17 21:13 ` Romain Francoise [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pq6pb4t0.fsf@silenus.orebokech.com \
--to=romain@orebokech.com \
--cc=clem@clem.clem-digital.net \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).