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: Fri, 1 Feb 2008 03:54:24 +0000

 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
 >  
 I've been unable to get anything meaningful, including any usable dumps
 (or indeed, any dumps, most of the time).  On the occasions when I get
 a command prompt (when in multiuser, I have ddb.onpanic=0 set -- and I
 don't get dumps), I've tried 'reboot 0x101', and it just hangs.  bt
 hasn't given anything useful, either.  But I'll try the command you
 suggest and see if anything better happens.
 
 
                --Steve Bellovin, http://www.cs.columbia.edu/~smb