Jaromir Dolecek wrote:

>Andrew Gillham wrote:
>  
>
>>Running mysqld under gdb didn't help, I ended up panic'ing the box after
>>doing 'kill -ABRT' on the mysql process, and then 'quit' in gdb.
>>The panic:
>>login: uvm_fault(0xe34a53c0, 0, 0, 1) -> 0xe
>>kernel: page fault trap, code=0
>>Stopped in pid 1772.1 (gdb) at  netbsd:kpsignal2+0x11b: testl   
>>%eax,0(%ebx,%edx
>>,4)
>>db{0}> tr
>>kpsignal2(e3e879cc,e3f03e64,1,e3e87d0c,0) at netbsd:kpsignal2+0x11b
>>psignal1(e3e879cc,1,1,e3e879cc,0) at netbsd:psignal1+0x29
>>orphanpg(e34df140,0,e3f03eec,c035b593,c076afa8) at netbsd:orphanpg+0x33
>>fixjobc(e3e87d0c,e34df100,0,e34a2fd8,0) at netbsd:fixjobc+0x76
>>exit1(e34a8e58,0,0,0,e3f03f5c) at netbsd:exit1+0x13f
>>sys_exit(e34a8e58,e3f03f64,e3f03f5c,1,7) at netbsd:sys_exit+0x23
>>syscall_plain(e3f03fa8,1f,1f,821001f,bfbf001f) at netbsd:syscall_plain+0x173
>>db{0}>
>>    
>>
>
>At least this part of the problem should be fixed with
>src/sys/kern_sig.c rev. 1.173. Can you confirm whether or not
>you can repeat the problem with updated kernel?
>  
>

I am still unable to stop mysqld.  Although '/etc/rc.d/mysqld stop' worked
one time after a reboot, I haven't been able to duplicate it.

I still get a uvm_fault if I 'kill -ABRT' the mysqld process that gdb
is running.  It drops to gdb, but when I do 'quit' it panics the kernel.

Looks like the same fault as above:
uvm_fault(0xe34af6e0, 0, 0, 1) -> 0xe
kernel: page fault trap, code=0
Stopped in pid 6132.1 (gdb) at  netbsd:kpsignal2+0x11b: testl   
%eax,0(%ebx,%edx
,4)
db{0}> tr
kpsignal2(e3eb168c,e3ef0e64,1,e3eb1d0c,0) at netbsd:kpsignal2+0x11b
psignal1(e3eb168c,1,1,e3eb168c,0) at netbsd:psignal1+0x29
orphanpg(e34e9100,0,e3ef0eec,c035c0db,c0774a08) at netbsd:orphanpg+0x33
fixjobc(e3eb1d0c,e34e90f0,0,e34acfd8,0) at netbsd:fixjobc+0x76
exit1(e34b2990,0,0,0,e3ef0f5c) at netbsd:exit1+0x13f
sys_exit(e34b2990,e3ef0f64,e3ef0f5c,1,7) at netbsd:sys_exit+0x23
syscall_plain(e3ef0fa8,1f,1f,1f,1f) at netbsd:syscall_plain+0x18a
db{0}>

-Andrew