Can someone please look into this ipv6 panic?  It is now my #1 panic
on 6.0 (every few days, and I hardly make any use of ipv6 except for
light nfs and tcp traffic), so it would be good to get it fixed before
the release.

Kris

----- Forwarded message from Kris Kennaway <[EMAIL PROTECTED]> -----

X-Original-To: [EMAIL PROTECTED]
Delivered-To: [EMAIL PROTECTED]
X-Original-To: [EMAIL PROTECTED]
Delivered-To: [EMAIL PROTECTED]
X-Original-To: [EMAIL PROTECTED]
Delivered-To: [EMAIL PROTECTED]
Resent-Date: Tue, 6 Sep 2005 04:10:11 GMT
Resent-Message-Id: <[EMAIL PROTECTED]>
Resent-From: [EMAIL PROTECTED] (GNATS Filer)
Resent-To: [EMAIL PROTECTED]
Resent-Reply-To: [EMAIL PROTECTED],
        Kris Kennaway <[EMAIL PROTECTED]>
Date: Tue, 6 Sep 2005 04:00:34 GMT
From: Kris Kennaway <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Send-Pr-Version: www-2.3
Cc: 
Subject: kern/85780: 'panic: bogus refcnt 0' in routing/ipv6
X-BeenThere: [EMAIL PROTECTED]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
        <mailto:[EMAIL PROTECTED]>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:[EMAIL PROTECTED]>
List-Help: <mailto:[EMAIL PROTECTED]>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
        <mailto:[EMAIL PROTECTED]>
Errors-To: [EMAIL PROTECTED]
X-UIDL: fH3"!MZN!!D<H"!#di!!
X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=0.96.0


>Number:         85780
>Category:       kern
>Synopsis:       'panic: bogus refcnt 0' in routing/ipv6
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Sep 06 04:10:11 GMT 2005
>Closed-Date:
>Last-Modified:
>Originator:     Kris Kennaway
>Release:        7.0
>Organization:
FreeBSD
>Environment:
sparc64
>Description:
This panic occurred on an SMP sparc64 machine.

> panic: bogus refcnt 0
> cpuid = 0
> KDB: enter: panic
> [thread pid 15 tid 100003 ]
> Stopped at      kdb_enter+0x3c: ta              %xcc, 1
> db> wh
> Tracing pid 15 tid 100003 td 0xfffff8001fb75680
> panic() at panic+0x164
> rtfree() at rtfree+0x7c
> nd6_na_output() at nd6_na_output+0x4d0
> nd6_ns_input() at nd6_ns_input+0x704
> icmp6_input() at icmp6_input+0xc38
> ip6_input() at ip6_input+0xf5c
> netisr_processqueue() at netisr_processqueue+0x7c
> swi_net() at swi_net+0xdc
> ithread_loop() at ithread_loop+0x18c
> fork_exit() at fork_exit+0x94
> fork_trampoline() at fork_trampoline+0x8

  It uses ipv6 to e.g. mount nfs /home directories and for ssh traffic, but the 
machine seems to have been idle at the time of panic (no other processes active 
on the other CPUs, and nothing much else running on the system either).  core 
available.

>How-To-Repeat:
It's only happened once so far.
>Fix:
      
>Release-Note:
>Audit-Trail:
>Unformatted:
_______________________________________________
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


----- End forwarded message -----

Attachment: pgpN7v7xaOFRF.pgp
Description: PGP signature

Reply via email to