From: Patrick McHardy <kaber@trash.net>
To: for.poige+linux@gmail.com
Cc: netdev@vger.kernel.org
Subject: Re: re-formated /Re: Hi!Couldn't you take a look at kernel stack's trace? (ip_route_input+0x91a/0xcc9)/
Date: Thu, 12 Jun 2008 14:07:06 +0200 [thread overview]
Message-ID: <4851116A.6040805@trash.net> (raw)
In-Reply-To: <43d009740806100736y343bad9bt3a8b365292cced49@mail.gmail.com>
Igor Podlesny wrote:
> Pid: 8, comm: sirq-net-rx/0 Not tainted (2.6.25.4-rt4aa-gcc43 #1)
> EIP: 0060:[<c0313d75>] EFLAGS: 00010202 CPU: 0
> EIP is at ip_route_input+0x91a/0xcc9
> EAX: 00000000 EBX: f5a69e00 ECX: f7477e14 EDX: 00000001
> ESI: 0f6ea8c0 EDI: f7477ea4 EBP: ffffff8f ESP: f7477e38
> DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068 preempt:00000001
> Process sirq-net-rx/0 (pid: 8, ti=f7476000 task=f746c690 task.ti=f7476000)
> Stack: 00000000 016ea8c0 f6e2f180 00000001 c04f1964 00000001 f5a69e00 016ea8c0
> 00000000 00000000 c04851cc f786d640 00000000 00000006 00000000 016ea8c0
> 0f6ea8c0 00000000 00000000 00000000 00000000 00000000 00000000 00000000
> Call Trace:
> [<c024d578>] __next_cpu+0x12/0x21
> [<c0333ee8>] arp_process+0x1fe/0x5fe
> [<c01277f5>] wake_up_process+0xe/0x10
> [<c0172e80>] __kmalloc+0x97/0xcb
> [<c02f16be>] __alloc_skb+0x45/0xf2
> [<c02f58da>] netif_receive_skb+0x2dd/0x30b
> [<c02f5975>] process_backlog+0x6d/0xc1
> [<c02f46a3>] net_rx_action+0x65/0x14c
> [<c01304dd>] ksoftirqd+0x138/0x214
> [<c01303a5>] ksoftirqd+0x0/0x214
> [<c013c30e>] kthread+0x38/0x5d
> [<c013c2d6>] kthread+0x0/0x5d
> [<c0113f3f>] kernel_thread_helper+0x7/0x10
Whats sirq-net-rx? Doesn't seem to be present in the mainline tree.
next prev parent reply other threads:[~2008-06-12 12:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 14:36 re-formated /Re: Hi!Couldn't you take a look at kernel stack's trace? (ip_route_input+0x91a/0xcc9)/ Igor Podlesny
2008-06-12 12:07 ` Patrick McHardy [this message]
2008-06-12 12:24 ` Igor Podlesny
2008-06-12 12:26 ` Patrick McHardy
2008-06-12 19:36 ` Jarek Poplawski
2008-06-12 19:46 ` > with unpatched kernels, and if you tried other than 2.6.25 versions Igor M Podlesny
2008-06-12 20:15 ` Jarek Poplawski
2008-06-12 20:19 ` > Hm... hard to tell. This shouldn't happen and rebooting isn't a solution Igor M Podlesny
2008-06-12 20:49 ` Jarek Poplawski
2008-06-12 20:51 ` > OK, a reboot after a bug can sometimes prevent further data corruption/loss Igor M Podlesny
2008-06-12 21:04 ` Jarek Poplawski
2008-06-12 20:21 ` > try a more current kernel (e.g. 2.6.26-rc5) Igor M Podlesny
2008-06-12 20:39 ` Stephen Hemminger
2008-06-12 20:44 ` > And kernel developer's can not afford debugging closed source drivers Igor M Podlesny
2008-06-12 20:23 ` > this message has strange "Subject" Igor M Podlesny
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=4851116A.6040805@trash.net \
--to=kaber@trash.net \
--cc=for.poige+linux@gmail.com \
--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 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.