Subject: Re: procfs broken on -current?
To: Kouichirou Hiratsuka <firstname.lastname@example.org>
From: Chavdar Ivanov <email@example.com>
Date: 02/12/2007 10:04:47
On 12/02/07, Chavdar Ivanov <firstname.lastname@example.org> wrote:
> On 12/02/07, Kouichirou Hiratsuka <email@example.com> 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>
> > best regards.
> > --
> > Kouichirou Hiratsuka
> > firstname.lastname@example.org
> Chavdar Ivanov