All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Alessandro Suardi <alessandro.suardi@gmail.com>
Cc: netdev@oss.sgi.com,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	netfilter-devel@lists.netfilter.org
Subject: Re: oops in 2.6.13-rc6-git12 in tcp/netfilter routines
Date: Fri, 26 Aug 2005 19:52:07 +0200	[thread overview]
Message-ID: <430F56C7.8070500@trash.net> (raw)
In-Reply-To: <5a4c581d05082506395fa984ae@mail.gmail.com>

Alessandro Suardi wrote:
> Stack is hand-copied from the dead box's console. 
> 
> [<c0103714>] die+0xe4/0x170
> [<c010381f>] do_trap+0x7f/0xc0
> [<c0103b33>] do_invalid_op+0xa3/0xb0
> [<c0102faf>] error_code+0x4f/0x54
> [<c02eb05b>] kfree_skbmem+0xb/0x20
> [<c02eb0cf>] __kfree_skb+0x5f/0xf0
> [<c031304a>] tcp_clean_rtx_queue+0x16a/0x470
> [<c0313746>] tcp_ack+0xf6/0x360
> [<c0315d57>] tcp_rcv_established+0x277/0x7a0
> [<c031eba0>] tcp_v4_do_rcv+0xf0/0x110
> [<c031f2a0>] tcp_v4_rcv+0x6e0/0x820
> [<c0305594>] ip_local_deliver_finish+0x84/0x160
> [<c02fbe4a>] nf_reinject+0x13a/0x1c0
> [<c033f0d8>] ipq_issue_verdict+0x28/0x40
> [<c033f968>] ipq_set_verdict+0x48/0x70
> [<c033fa79>] ipq_receive_peer+0x39/0x50
> [<c033fc72>] ipq_receive_sk+0x172/0x190
> [<c02fffa5>] netlink_data_ready+0x35/0x60
> [<c02ff4a4>] netlink_sendskb+0x24/0x60
> [<c02ff657>] netlink_unicast+0x127/0x160
> [<c02ffcc4>] netlink_sendmsg+0x204/0x2b0
> [<c02e6dc0>] sock_sendmsg+0xb0/0xe0
> [<c02e83f4>] sys_sendmsg+0x134/0x240
> [<c02e88e4>] sys_socketcall+0x224/0x230
> [<c0102d3b>] sysenter_past_esp+0x54/0x75
> Code: 8b 41 0c 85 c0 75 1b 8b 86 94 00 00 00 e8 9e 37 e5 ff 5b 5e c9
> c3 89 d0 e8 43 46 e5 ff 8d 76 00 eb d2 89 f0 e8 f7 fe ff ff eb dc <0f>
> 0b 54 01 16 d2 36 c0 eb b4 8d 74 26 00 8d bc 27 00 00 00 00
> <0>Kernel panic - not syncing: Fatal exception in interrupt
> 
> If there's need for further info I'd be happy to provide it. For now
>  the box is rebooted into the same kernel and running the same
>  PG/eD2k programs, if the issue reproduces I'll follow up on my
>  own message.

Any chance you can get the entire Oops including registers etc
using netconsole or serial console?

  parent reply	other threads:[~2005-08-26 17:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-25 13:39 oops in 2.6.13-rc6-git12 in tcp/netfilter routines Alessandro Suardi
2005-08-25 16:55 ` Harald Welte
2005-08-25 17:26   ` Alessandro Suardi
2005-08-25 21:02   ` Sven Schuster
2005-08-26  8:35     ` Harald Welte
2005-08-26  8:35     ` Harald Welte
2005-08-26  8:35       ` Harald Welte
2005-08-25 21:02   ` Sven Schuster
2005-08-25 16:55 ` Harald Welte
2005-08-26 17:52 ` Patrick McHardy
2005-08-26 17:52 ` Patrick McHardy [this message]
2005-08-26 20:40   ` Alessandro Suardi
2005-08-26 20:40   ` Alessandro Suardi
  -- strict thread matches above, loose matches on Subject: below --
2005-08-25 13:39 Alessandro Suardi

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=430F56C7.8070500@trash.net \
    --to=kaber@trash.net \
    --cc=alessandro.suardi@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@oss.sgi.com \
    --cc=netfilter-devel@lists.netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.