NetBSD Problem Report #36427

From root@garbled.net  Sat Jun  2 15:49:12 2007
Return-Path: <root@garbled.net>
Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11])
	by narn.NetBSD.org (Postfix) with ESMTP id 63D7063B880
	for <gnats-bugs@gnats.NetBSD.org>; Sat,  2 Jun 2007 15:49:12 +0000 (UTC)
Message-Id: <20070602155009.66E025B215@polaris.garbled.net>
Date: Sat,  2 Jun 2007 08:50:09 -0700 (MST)
From: root@garbled.net
Reply-To: root@garbled.net
To: gnats-bugs@NetBSD.org
Subject: pcn related panic in m_freem
X-Send-Pr-Version: 3.95

>Number:         36427
>Category:       kern
>Synopsis:       TCP: pcn related panic in m_freem
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Jun 02 15:50:00 +0000 2007
>Last-Modified:  Sat May 19 10:47:32 +0000 2018
>Originator:     Tim Rightnour
>Release:        NetBSD 4.0_BETA2
>Organization:

>Environment:


System: NetBSD polaris.garbled.net 4.0_BETA2 NetBSD 4.0_BETA2 (GENERIC) #14: Sun Mar 25 01:26:44 MST 2007 root@polaris.garbled.net:/usr/src/obj/i386/sys/arch/i386/compile/GENERIC i386
Architecture: powerpc
Machine: prep
>Description:
While doing lots of NFS stuff (a pkgsrc bulk build) the machine panic'd.

The arp_drain messages are new to me, never seen those before. I'm assuming
they are related somehow.  This panic is very uncommon, never seen it before.

arp_drain: locked; punting
arp_drain: locked; punting
arp_drain: locked; punting
trap: kernel read DSI trap @ 0x3869001c by 0x2fcc34 (DSISR 0x40000000, err=14), lr 0x2fcc34
panic: trap
Stopped in pid 4.1 (pagedaemon) at      netbsd:cpu_Debugger+0x10:       lwz     r
0, r1, 0x14
db> where
No such command
db> bt
0x004f2aa0: at panic+0x1b4
0x004f2af0: at trap+0x124
0x004f2b70: kernel DSI read trap @ 0x3869001c by m_freem+0x98: srr1=0x9032
            r1=0x4f2c30 cr=0x20002034 xer=0 ctr=0x126404 dsisr=0x40000000
0x004f2c30: at m_freem+0x80
0x004f2c60: at tcp_freeq+0x5c
0x004f2c80: at tcp_drain+0x9c
0x004f2cb0: at m_reclaim+0x5c
0x004f2cd0: at pool_grow+0x2e0
0x004f2d00: at pool_get+0x30
0x004f2d20: at pool_cache_get_paddr+0x150
0x004f2d50: at pcn_add_rxbuf+0x108
0x004f2d80: at pcn_intr+0x294
0x004f2dd0: at ext_intr_openpic+0x160
0x004f2e10: at trapstart+0x8fc
0x004f2e70: at 0x5a4
0x004f2ea0: at pool_put+0x34
0x004f2ed0: at tcp_close+0x1ac
0x004f2f00: at tcp_timer_keep+0x1a4
0x004f2f20: at softclock+0x2c8
0x004f2f50: at hardclock+0x130
0x004f2f70: at decr_intr+0x110
0x004f2fa0: at trapstart+0xbb8
0xda471e40: at uvmpdpol_selectvictim+0xc8
0xda471e60: at uvmpdpol_balancequeue+0xd8
0xda471e90: at uvm_pageout+0x200
0xda471f40: at cpu_switchto+0x44
0xda471f50: at _prop_dictionary_keysym32_pool+0xffb6c288
db> 

>How-To-Repeat:
Unknown.  Heavy NFS traffic over a pcn device?

>Fix:
Unknown


>Release-Note:

>Audit-Trail:

>Unformatted:

Home	PR Database Search