>Number:         23382
>Category:       kern
>Synopsis:       panic on sparc64 while playing toppler with remote $DISPLAY
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Nov 07 01:34:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     
>Release:        NetBSD 1.6.2_RC1
>Organization:
>Environment:
System: NetBSD procrustes.blef.org 1.6.2_RC1 NetBSD 1.6.2_RC1 (GENERIC) #0: Thu Nov 6 14:15:16 PST 2003 soren@procrustes.blef.org:/usr/src/sys/arch/sparc64/compile/GENERIC sparc64
Architecture: sparc64
Machine: sparc64
Userland still at 1.6.1
http://www.pobox.com/~snj/machines/dmesg.PROCRUSTES
>Description:

With $DISPLAY set to a remote X server, after playing toppler for a few
seconds, I get the following panic:

panic: setrunnable
kdb breakpoint at 12c8194
Stopped at      cpu_Debugger+0x4:       nop
db> trace
setrunnable(9314880, 18805c8, 9314880, 1, a, 934fa40) at setrunnable+0x30
selwakeup(1, 3890, 4b0, 4d00, 3, 3a38) at selwakeup+0x9c
sowakeup(1eb4980, 1eb4a30, 1eb4a30, 1eca9b0, 5a8, 1fffe) at sowakeup+0x4
tcp_input(1dce700, 1dce764, 1eca9b0, 34, 1dce750, 1eb4980) at tcp_input+0x278c
ip_input(1dce750, 1dce700, 188b400, 188b478, 1, 1d) at ip_input+0x9a0
ipintr(1000000, 1, f, 80, 2c37f0, 40f1a1f4) at ipintr+0x60
softnet(4, 0, e0017ed0, 1590, 12bc7f4, 113d180) at softnet+0x5c
sparc_intr_retry(0, 0, 13137b0, 0, ffffffffffffffff, 0) at sparc_intr_retry+0x48

VOP_POLL(9314880, b499, 1898b38, 1a, a, 934fa40) at VOP_POLL+0x2c
mi_switch(9314880, 92c1, 934c428, 9314880, a, 0) at mi_switch+0x158
ltsleep(0, a, 13452a8, 3e5, 0, 1) at ltsleep+0x1d8
sys_select(0, 934fdd0, 934fdc0, 11679a4, 0, 0) at sys_select+0x2bc
syscall(934fed0, 5d, 0, 40f1a1fc, 800, 45d) at syscall+0x2f4
syscall_setup(b, 2c3900, 2c3880, 2c3800, 2c37f0, 40f1a1f4) at syscall_setup+0xec

db> 

I'm don't know what other information would be useful, so let me know what
I can do to further aid in tracking this down.

I'll try to see if I can get some other heavy X11 traffic (like playing
a movie) going and see if it produces the panic as well.

>How-To-Repeat:
Get pkgsrc-wip from http://pkgsrc-wip.sf.net/, install toppler, set DISPLAY
to some remote X server, run toppler, start mission, poke around (usually
doesn't take more than 20 seconds), boom.
>Fix:
Not the slightest clue.
>Release-Note:
>Audit-Trail:
>Unformatted: