DragonFly BSD
DragonFly bugs List (threaded) for 2006-01
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

nge panic on PREVIEW


From: "Steve O'Hara-Smith" <steve@xxxxxxxxxx>
Date: Mon, 9 Jan 2006 17:00:20 +0000

	Hi,

	I just updated to the latest PREVIEW (1.5.0) and got the panic
below as soon as my nge interface saw traffic:

	Killing the NFS mounts didn't help nor did disabling everything
that used the network. The latter enabled me to get to a multiuser login
but as soon as I enabled the bge interface a similar panic followed in a
fraction of a second.

	My dmesg is too full of things like:
------------------- dmesg contents -----------------
10 lwkt RW Node
  256 untimely_switch RW *Handler Int
  257 panic_on_cscount RW *Handler Int
  258 switch_count RW *Handler Quad
  259 preempt_hit RW *Handler Quad
  260 preempt_miss RW *Handler Quad
  261 preempt_weird RW *Handler Quad
  262 token_contention_count RW *Handler Quad
  263 mplock_contention_count RW *Handler Quad
  264 token_debug RW *Handler Int
256 jail RW Node
----------------------------------------------------

	to get anything useful from but pciconf -lv has this to say
about the bge device:

nge0@pci0:12:0: class=0x020000 card=0x00000000 chip=0x0022100b rev=0x00 hdr=0x00
    vendor   = 'National Semiconductor'
    device   = 'DP83820/1 10/100/1000 Gigabit Ethernet Adapter'
    class    = network
    subclass = ethernet

----------- panic message -------------
Mounting NFS file systems:panic: assertion: s->last_td != curthread in lwkt_serialize_enter
Trace beginning at frame 0xd0ff8c68
panic(c0428471,c04e4580,c044c384,d0ff8c98,d0ffe000) at panic+0x99
panic(c044c284,c0451070,d0ffe000,d0ffe000,d362a600) at panic+0x99
lwkt_serialize_enter(cce3b254,d0ffe000,0,d3633000,c) at lwkt_serialize_enter+0x32
nge_rxeof(cce3b0b8,cce3b0b8,c01e8868,cce3b254,ff800000) at nge_rxeof+0x1a4
nge_intr(cce3b0b8,0,c04f9a70,cce3b254,c16c26a0) at nge_intr+0xe2
lwkt_serialize_handler_call(cce3b254,c019c3c1,cce3b0b8,0,d0) at lwkt_serialise_handler_call+0x5f
ithread_handler(a,0,0,0,0) at ithread_handler+0x8d
lwkt_exit() at lwkt_exit
Debugger("panic")
Stopped at      Debugger+0x44: movb     $0,in_Debugger.0
db>

PS: Is there any way to suppress that output in dmesg so that I can
keep the normal stuff ?

-- 
C:>WIN                                      |   Directable Mirror Arrays
The computer obeys and wins.                | A better way to focus the sun
You lose and Bill collects.                 |    licences available see
                                            |    http://www.sohara.org/



[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]