From: Jay Lan <jlan@engr.sgi.com>
To: johnpol@2ka.mipt.ru
Cc: Andrew Morton <akpm@osdl.org>,
Guillaume Thouvenin <guillaume.thouvenin@bull.net>,
greg@kroah.com, linux-kernel@vger.kernel.org,
efocht@hpce.nec.com, linuxram@us.ibm.com, gh@us.ibm.com,
elsa-devel@lists.sourceforge.net, aquynh@gmail.com,
dean-list-linux-kernel@arctic.org, pj@sgi.com
Subject: Re: [patch 2.6.12-rc1-mm4] fork_connector: add a fork connector
Date: Thu, 07 Apr 2005 15:40:18 -0700 [thread overview]
Message-ID: <4255B6D2.7050102@engr.sgi.com> (raw)
In-Reply-To: <1112341968.9334.109.camel@uganda>
Hi Evgeniy,
Should i be concerned about this bugcheck?
I have seen this happening a number of times, all with the same signature
in my testing. I ran a mix of AIM7, ubench, fork-test (continuously
fork new
processes), and another program reading from the fork connector socket.
Thanks,
- jay
cqueue/1[656]: bugcheck! 0 [1]
Modules linked in: nfs lockd sunrpc sg st sr_mod ipv6 usbcore
Pid: 656, CPU 1, comm: cqueue/1
psr : 00001010085a6010 ifs : 8000000000000289 ip :
[<a0000001005cee50>] Not tainted
ip is at __kfree_skb+0x1b0/0x220
unat: 0000000000000000 pfs : 0000000000000289 rsc : 0000000000000003
rnat: 0000000000000000 bsps: 0000000000000000 pr : 0000000000009641
ldrs: 0000000000000000 ccv : 0000000000000000 fpsr: 0009804c8a70433f
csd : 0000000000000000 ssd : 0000000000000000
b0 : a0000001005cee50 b6 : a00000010000e7e0 b7 : a0000001003ae440
f6 : 0fffbccccccccc8c00000 f7 : 0ffdaa200000000000000
f8 : 100008000000000000000 f9 : 10002a000000000000000
f10 : 0fffcccccccccc8c00000 f11 : 1003e0000000000000000
r1 : a000000100c0ec00 r2 : 0000000000004000 r3 : 0000000000004000
r8 : 0000000000000028 r9 : a0000001008eaac8 r10 : 0000000000000004
r11 : 0000000000000028 r12 : e00000307a99fd60 r13 : e00000307a998000
r14 : a000000100887c00 r15 : a000000100a24b18 r16 : a000000100a22e18
r17 : ffffffffffffffff r18 : a000000100887bec r19 : a000000100a9080f
r20 : 0000000000003517 r21 : 00000000000fffff r22 : 0000000000000034
r23 : 0000000000000034 r24 : a000000100a90810 r25 : 0000000000003518
r26 : 0000000000003518 r27 : 00000010085a6010 r28 : a000000100a90811
r29 : 0000000000003519 r30 : 0000000000000000 r31 : a000000100a24ae8
Call Trace:
[<a0000001000126a0>] show_stack+0x80/0xa0
sp=e00000307a99f920 bsp=e00000307a999078
[<a000000100012f00>] show_regs+0x840/0x880
sp=e00000307a99faf0 bsp=e00000307a999018
[<a000000100034890>] die+0x150/0x1c0
sp=e00000307a99fb00 bsp=e00000307a998fd0
[<a000000100034940>] die_if_kernel+0x40/0x60
sp=e00000307a99fb00 bsp=e00000307a998fa0
[<a000000100035d20>] ia64_bad_break+0x300/0x380
sp=e00000307a99fb00 bsp=e00000307a998f78
[<a00000010000b5e0>] ia64_leave_kernel+0x0/0x280
sp=e00000307a99fb90 bsp=e00000307a998f78
[<a0000001005cee50>] __kfree_skb+0x1b0/0x220
sp=e00000307a99fd60 bsp=e00000307a998f30
[<a00000010044f630>] kfree_skb+0x50/0xa0
sp=e00000307a99fd60 bsp=e00000307a998f10
[<a00000010044e400>] cn_queue_wrapper+0xe0/0x100
sp=e00000307a99fd60 bsp=e00000307a998ee8
[<a0000001000cb880>] worker_thread+0x3e0/0x520
sp=e00000307a99fd60 bsp=e00000307a998e60
[<a0000001000d7210>] kthread+0x290/0x300
sp=e00000307a99fdd0 bsp=e00000307a998e20
[<a000000100010a00>] kernel_thread_helper+0xe0/0x100
sp=e00000307a99fe30 bsp=e00000307a998df0
[<a000000100009120>] start_kernel_thread+0x20/0x40
sp=e00000307a99fe30 bsp=e00000307a998df0
next prev parent reply other threads:[~2005-04-07 22:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-31 13:59 [patch 2.6.12-rc1-mm4] fork_connector: add a fork connector Guillaume Thouvenin
2005-03-31 22:44 ` Andrew Morton
2005-04-01 0:10 ` Jay Lan
2005-04-01 7:52 ` Evgeniy Polyakov
2005-04-07 22:40 ` Jay Lan [this message]
2005-04-07 22:47 ` Jay Lan
2005-04-08 10:24 ` Evgeniy Polyakov
2005-04-08 10:52 ` Evgeniy Polyakov
2005-04-08 20:27 ` Jay Lan
2005-04-08 22:08 ` Jay Lan
2005-04-08 22:18 ` Evgeniy Polyakov
2005-04-09 3:31 ` Jay Lan
2005-04-09 6:29 ` Evgeniy Polyakov
2005-04-11 5:43 ` Jay Lan
2005-04-11 6:44 ` Evgeniy Polyakov
2005-04-11 6:51 ` Andrew Morton
2005-04-11 7:31 ` Evgeniy Polyakov
2005-03-31 22:53 ` Andrew Morton
2005-04-01 10:56 ` Guillaume Thouvenin
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=4255B6D2.7050102@engr.sgi.com \
--to=jlan@engr.sgi.com \
--cc=akpm@osdl.org \
--cc=aquynh@gmail.com \
--cc=dean-list-linux-kernel@arctic.org \
--cc=efocht@hpce.nec.com \
--cc=elsa-devel@lists.sourceforge.net \
--cc=gh@us.ibm.com \
--cc=greg@kroah.com \
--cc=guillaume.thouvenin@bull.net \
--cc=johnpol@2ka.mipt.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxram@us.ibm.com \
--cc=pj@sgi.com \
/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.