Re: port-amd64/32400 (init loops getting signal 4 on Atlon X2 64 with amd64)

To: port-amd64-maintainer%netbsd.org@localhost,netbsd-bugs%netbsd.org@localhost,gnats-admin%netbsd.org@localhost,dholland%NetBSD.org@localhost,Bernhard Moellemann <zza%serpens.de@localhost>
Subject: Re: port-amd64/32400 (init loops getting signal 4 on Atlon X2 64 with amd64)
From: dholland%NetBSD.org@localhost
Date: Mon, 26 May 2008 06:16:45 +0000 (UTC)

Synopsis: init loops getting signal 4 on Atlon X2 64 with amd64

State-Changed-From-To: open->feedback
State-Changed-By: dholland%NetBSD.org@localhost
State-Changed-When: Mon, 26 May 2008 06:16:45 +0000
State-Changed-Why:
I tried this a while back with 4.99.something (at some length actually,
including hacking around the issues with /dev) and I didn't see this problem
either. Have you seen it recently, or can we assume it's been fixed?

Follow-Ups:
- Re: port-amd64/32400 (init loops getting signal 4 on Atlon X2 64 with amd64)
  - From: Manuel Bouyer

Prev by Date: Re: kern/32072 (Kernel crashes on NFS writes because of a failed assertion)
Next by Date: Re: kern/32433 (GENERIC_LAPTOP does not have the option of having the fwohci dev and related firewire devs.... yet GENERIC does.)
Previous by Thread: Re: kern/32072 (Kernel crashes on NFS writes because of a failed assertion)
Next by Thread: Re: port-amd64/32400 (init loops getting signal 4 on Atlon X2 64 with amd64)
Indexes:

Home | Main Index | Thread Index | Old Index