Re: kern/37933: very frequent crashes after suspend/resume

["Steven M. Bellovin" <smb%cs.columbia.edu@localhost>]

The following reply was made to PR kern/37933; it has been noted by GNATS.

From: "Steven M. Bellovin" <smb%cs.columbia.edu@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: jmcneill%invisible.ca@localhost, kern-bug-people%NetBSD.org@localhost, 
gnats-admin%NetBSD.org@localhost,
        netbsd-bugs%NetBSD.org@localhost
Subject: Re: kern/37933: very frequent crashes after suspend/resume
Date: Thu, 31 Jan 2008 23:20:46 -0500

 On Fri,  1 Feb 2008 03:35:03 +0000 (UTC)
 "Jared D. McNeill" <jmcneill%invisible.ca@localhost> wrote:
 
 > The following reply was made to PR kern/37933; it has been noted by
 > GNATS.
 > 
 > From: "Jared D. McNeill" <jmcneill%invisible.ca@localhost>
 > To: gnats-bugs%NetBSD.org@localhost
 > Cc: kern-bug-people%netbsd.org@localhost, gnats-admin%netbsd.org@localhost, 
 >  netbsd-bugs%netbsd.org@localhost
 > Subject: Re: kern/37933: very frequent crashes after suspend/resume
 > Date: Thu, 31 Jan 2008 21:12:35 -0500
 > 
 >  smb%cs.columbia.edu@localhost wrote:
 >  >   The panics are usually in uvm_fault or amap_wipeout.
 >  
 >  How about a backtrace? sysctl -w ddb.commandonenter=tr
 >  
 
 
 kernel:protection fault trap, code=0
 Stopped in pid 8.1 (sysctl) at amap_wipeout+0x82:  movl 0(%r13),%esi
 
 
 Beyond that:
 
 uvm_unmap_detach()+0x45
 uvmspace_free()+0xe4
 exit1()+0x236
 sys_exit()+0x67
 syscall()+0xa9
 
 When I typed 'reboot 0x101', it did dump; however, it didn't reboot.
 And I can't do anything useful with the dump; savecore says "/dev/wd0b:
 device busy"...