On 12/02/07, Chavdar Ivanov <ci4ic4@gmail.com> wrote:
> On 12/02/07, Chavdar Ivanov <ci4ic4@gmail.com> wrote:
> > On 12/02/07, Kouichirou Hiratsuka <hira@po6.nsk.ne.jp> wrote:
> > > Hello,
> > >
> ...
> > >
> > > It works fine for me too.
> > > However, I got a kernel panic with the following command.
> >
> > I am getting exactly the same with
> >
> >    ktruss java -version
> >
> > (well, the addresses are different, if that matters - I think not).
> >
> > I can write down the output from bt if necessary - this machine does
> > not have a serial port to redirect the debugger unfortunately. I might
> > try the same under VMware and get the output there.
>
> And I can't force it to dump - reboot 0x104 results in 'device
> timeout' for my ahcisata connected disk...
>
>
> >
> > With a slightly earlier verson of the kernel it froze itself trying to
> > open an entry under /emul/linux/proc.
> >
> > >
> > > % ls -la /proc/*/*
> > > Mutex error: mutex_vector_enter: locking against myself
> > >
> > > lock address : 0x00000000c0505e70
> > > current cpu  :                  0
> > > current lwp  : 0x00000000cbc6f2e0
> > > owner field  : 0x00000000cbc6f2e0 wait/spin:                 0/0
> > >
> > >
> > > panic: lock error
> > > Stopped in pid 120.1 (ls) at    netbsd:cpu_Debugger+0x4:         leave
> > > db>
> > >

And (expectedly) the same happens with OpenOffice-bin - javaldx...

> > > best regards.
> > > --
> > >  Kouichirou Hiratsuka
> > >    hira@po6.nsk.ne.jp
> > >
> > Chavdar Ivanov
> >
>