Re: another panic in 8.3-PRERELEASE

2012-02-28 Thread Konstantin Belousov
On Sat, Feb 25, 2012 at 02:58:28AM +0900, Hiroki Sato wrote: > Konstantin Belousov wrote > in <20120224150259.gv55...@deviant.kiev.zoral.com.ua>: > > ko> > > #19 0x000800abecfc in ?? () > ko> > > Previous frame inner to this frame (corrupt stack?) > ko> > > (kgdb) > ko> > Can you, please, p

Re: another panic in 8.3-PRERELEASE

2012-02-24 Thread Hiroki Sato
Konstantin Belousov wrote in <20120224150259.gv55...@deviant.kiev.zoral.com.ua>: ko> > > #19 0x000800abecfc in ?? () ko> > > Previous frame inner to this frame (corrupt stack?) ko> > > (kgdb) ko> > Can you, please, print out the content of *td, e.g. from the frame 16 ? ko> ko> And *req fro

Re: another panic in 8.3-PRERELEASE

2012-02-24 Thread Konstantin Belousov
On Fri, Feb 24, 2012 at 04:33:36PM +0200, Konstantin Belousov wrote: > On Thu, Feb 23, 2012 at 11:45:58PM +0900, Hiroki Sato wrote: > > Hi, > > > > This is another reproducible panic. This seems to happen only when > > top(1) is running for a long time (a sysctl() call for > > CTL_KERN.KERN_PR

Re: another panic in 8.3-PRERELEASE

2012-02-24 Thread Konstantin Belousov
On Thu, Feb 23, 2012 at 11:45:58PM +0900, Hiroki Sato wrote: > Hi, > > This is another reproducible panic. This seems to happen only when > top(1) is running for a long time (a sysctl() call for > CTL_KERN.KERN_PROC.KERN_PROC_PROC MIB triggered it). > > > pool.allbsd.org dumped core - se