Subject: kern/32794: wscons seemingly related panic
To: None <kern-bug-people@netbsd.org, gnats-admin@netbsd.org,>
From: None <paul@plectere.com>
List: netbsd-bugs
Date: 02/10/2006 17:00:00
>Number:         32794
>Category:       kern
>Synopsis:       panic in wscons
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Feb 10 17:00:00 +0000 2006
>Originator:     Paul Shupak
>Release:        NetBSD 3.99.15
>Organization:
>Environment:
	
	
System: NetBSD cobalt 3.99.15 NetBSD 3.99.15 (COBALT-$Revision: 1.4 $) #25: Wed Feb 8 18:39:50 PST 2006 paul@svcs:/sys/arch/i386/compile/COBALT i386
Architecture: i386
Machine: i386
>Description:
	Machines panic seemingly at random in wscons code.
	Immediately before the panics, either the mouse or keyboard becomes
very "sluggish" (long delays for input to take effect).
	Traceback:
pms0: resetting mouse interface
panic: kernel diagnostic assertion "nevents > 0 && nevents <= sizeof(events) / sizeof(struct wscons_event)" failed: file "../../../../dev/wscons/wsmouse.c", line 487
Begin traceback...
__main(c047d724,c04e9b80,1e7,c04e9b20,1) at netbsd:__main
wsmouse_input_xyzw(c2678f00,2,0,0,0) at netbsd:wsmouse_input_xyzw+0x30f
pmsinput(c2677f80,0,c08d9e40,f359e,246) at netbsd:pmsinput+0x1a7
pckbportintr(c08315c0,1,0,c0336d7e,1) at netbsd:pckbportintr+0x3a
pckbcintr(c2671080,0,10d00010,40030,9a780010) at netbsd:pckbcintr+0x94
Xintr_ioapic_edge12() at netbsd:Xintr_ioapic_edge12+0x97
--- interrupt ---
cpu_switch(c084b1e0,0,0,282,0) at netbsd:cpu_switch+0x9f
ltsleep(c084ae60,4,c049df94,0,0) at netbsd:ltsleep+0x36f
uvm_scheduler(c08491ec,0,c084793c,c048901c,0) at netbsd:uvm_scheduler+0x74
main(0,0,0,0,0) at netbsd:main+0x483
End traceback...
syncing disks... fatal page fault in supervisor mode
trap type 6 code 0 eip c0276689 cs 8 eflags 10246 cr2 34 ilevel 0
panic: trap
Begin traceback...
trap() at netbsd:trap+0x151
--- trap (number 6) ---
lfs_seglock(c223b000,5,c08d99f0,c0316e3f,cec1bf98) at netbsd:lfs_seglock+0x8d
lfs_segwrite(c2240000,5,c080c1c4,c2240000,c2f30018) at netbsd:lfs_segwrite+0x6a
lfs_sync(c2240000,2,ccaa0f6c,0,c08d9aa0) at netbsd:lfs_sync+0x4f
sys_sync(0,0,0,0,c08d9adc) at netbsd:sys_sync+0xba
vfs_shutdown(c04fe960,0,c08d9b00,c02e7a8a,100) at netbsd:vfs_shutdown+0x50
cpu_reboot(100,0,1,1,10) at netbsd:cpu_reboot+0x155
panic(c04fe960,c047d724,c04e9b20,c04e9b80,1e7) at netbsd:panic+0x116
__main(c047d724,c04e9b80,1e7,c04e9b20,1) at netbsd:__main
wsmouse_input_xyzw(c2678f00,2,0,0,0) at netbsd:wsmouse_input_xyzw+0x30f
pmsinput(c2677f80,0,c08d9e40,f359e,246) at netbsd:pmsinput+0x1a7
pckbportintr(c08315c0,1,0,c0336d7e,1) at netbsd:pckbportintr+0x3a
pckbcintr(c2671080,0,10d00010,40030,9a780010) at netbsd:pckbcintr+0x94
Xintr_ioapic_edge12() at netbsd:Xintr_ioapic_edge12+0x97
--- interrupt ---
cpu_switch(c084b1e0,0,0,282,0) at netbsd:cpu_switch+0x9f
ltsleep(c084ae60,4,c049df94,0,0) at netbsd:ltsleep+0x36f
uvm_scheduler(c08491ec,0,c084793c,c048901c,0) at netbsd:uvm_scheduler+0x74
main(0,0,0,0,0) at netbsd:main+0x483
End traceback...

dumping to dev 0,1 offset 2357255
dump 1535 1534 1533 1532 1531 1530 1529 1528 1527 1526 1525 1524 1523 1522 1521 
...
>How-To-Repeat:
	Use any kernel from Feb. 8 forward on an i386 box while running X.
This has occured on three machines, but only one has a ".gdb" kernel built
and available.  The LFS activity is unrelated - not all affected machines
have or use LFS.  This has occured 7 times in the past 24 hours in the
affected machines - other machines which do not experience much load or run
X Windows seem not to show the problem (kernels built at the same time and
from the same source tree).  NOTE:  X seems to have to be running, but the
same panic occurs on another machine when noone is at the console (heavy
NFS activity triggers it also - still the traceback and assertion are the
same).
>Fix:
	No idea - a full debug kernel and dump can be made available.

>Unformatted: