Subject: kern/30949: system crash on shutdown
To: None <kern-bug-people@netbsd.org, gnats-admin@netbsd.org,>
From: None <j+nbsd@2005.salmi.ch>
List: netbsd-bugs
Date: 08/09/2005 08:39:00
>Number: 30949
>Category: kern
>Synopsis: system crash on shutdown
>Confidential: no
>Severity: critical
>Priority: high
>Responsible: kern-bug-people
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Tue Aug 09 08:39:00 +0000 2005
>Originator: Jukka Salmi
>Release: NetBSD 3.99.7
>Environment:
System: NetBSD moray.salmi.ch 3.99.7 NetBSD 3.99.7 (GENERIC) #1: Mon Aug 1 14:22:29 CEST 2005 build@moray.salmi.ch:/build/nbsd/i386/sys/arch/i386/compile/GENERIC i386
Architecture: i386
Machine: i386
>Description:
About once a week this -current NetBSD/i386 system which I shut down
almost daily crashes while shutting down. Ddb output from yesterday's
crash follows:
uvm_fault(0xcaa48460, 0, 0, 1) -> 0xe
kernel: page fault trap, code=0
Stopped in pid 28404.1 (ksh) at netbsd:spec_ioctl+0xe: movl 0xc(%eax),%esi
db> bt
spec_ioctl(caa09ce4,c0468651,c1341284,3e8,c06328e0) at netbsd:spec_ioctl+0xe
VOP_IOCTL(d1a2ab30,802c7415,caa09ea4,3,ffffffff) at netbsd:VOP_IOCTL+0x40
cttyioctl(100,802c7415,caa09ea4,3,cbb634c8) at netbsd:cttyioctl+0x52
spec_ioctl(caa09d84,ffffffff,caa491e0,1b5bf000,c06328e0) at netbsd:spec_ioctl+0x46
VOP_IOCTL(cb639004,802c7415,caa09ea4,3,cb81d5ec) at netbsd:VOP_IOCTL+0x40
vn_ioctl(cb81ceac,802c7415,caa09ea4,cbb634c8,0) at netbsd:vn_ioctl+0x9a
sys_ioctl(cb8468c8,caa09f64,caa09f5c,0,caa09fa4) at netbsd:sys_ioctl+0x122
syscall_plain() at netbsd:syscall_plain+0x7e
--- syscall (number 54) ---
0xbdbc764f:
db> show registers
ds 0x10
es 0x10
fs 0x30
gs 0x10
edi 0
esi 0x802c7415
ebp 0xcaa09ccc
ebx 0xcaa09ce4
edx 0xd1a2ab30
ecx 0xcbb634c8
eax 0
eip 0xc03d5cd6 spec_ioctl+0xe
cs 0x8
eflags 0x10286
esp 0xcaa09cc4
ss 0x10
netbsd:spec_ioctl+0xe: movl 0xc(%eax),%esi
db> ps
PID PPID PGRP UID S FLAGS LWPS COMMAND WAIT
5319 1 843 1000 2 0x4002 1 halt nanosle
>28404 16923 28404 1000 2 0x4002 1 ksh
23470 1 23470 1000 2 0 1 ssh-agent biowait
16923 1 16923 0 2 0x6103 1 login biowait
862 1 1018 0 2 0 1 smartd vnlock
764 1 764 0 2 0 1 sshd vnlock
339 1 339 0 2 0 1 syslogd biowait
17 0 0 0 2 0x20200 1 aiodoned aiodone
16 0 0 0 2 0x20200 1 ioflush syncer
15 0 0 0 2 0x20200 1 pagedaemon pgdaemo
14 0 0 0 2 0x20200 1 raidio0 raidiow
13 0 0 0 2 0x20200 1 raid0 rfwcond
12 0 0 0 2 0x20200 1 atapibus1 sccomp
11 0 0 0 2 0x20200 1 atapibus0 sccomp
10 0 0 0 2 0x20200 1 pms0 pmsrese
9 0 0 0 2 0x20200 1 atabus1 atath
8 0 0 0 2 0x20200 1 atabus0 atath
7 0 0 0 2 0x20200 1 usb3 usbevt
6 0 0 0 2 0x20200 1 usb2 usbevt
5 0 0 0 2 0x20200 1 usb1 usbevt
4 0 0 0 2 0x20200 1 usbtask usbtsk
3 0 0 0 2 0x20200 1 usb0 usbevt
2 0 0 0 2 0x20200 1 cryptoret crypto_
1 0 1 0 2 0x4000 1 init vnlock
0 -1 0 0 2 0x20200 1 swapper schedul
727 1 727 15 5 0x2100 0 ntpd *
100 1 100 0 5 0x6002 0 getty *
101 1 101 0 5 0x6002 0 getty *
1078 1 1078 0 5 0x6108 0 master *
1044 1 1078 12 5 0x6108 0 qmgr *
27633 1 1078 12 5 0x6108 0 pickup *
db>
I was not able to get a crash dump this time. However, I still have a
dump available from the last [1]crash.
[1] http://mail-index.netbsd.org/current-users/2005/08/01/0008.html
>How-To-Repeat:
Don't; it happens _sometimes_ while shutting down...
>Fix:
none