From owner-freebsd-current@FreeBSD.ORG  Fri Dec  5 21:50:23 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id A8BE216A4CF
	for <current@freebsd.org>; Fri,  5 Dec 2003 21:50:23 -0800 (PST)
Received: from fsp1.physik.ruhr-uni-bochum.de (fsp1.physik.ruhr-uni-bochum.de
	[134.147.168.26])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 794C243FE3
	for <current@freebsd.org>; Fri,  5 Dec 2003 21:49:51 -0800 (PST)
	(envelope-from strattbo@fsp1.physik.ruhr-uni-bochum.de)
Received: by fsp1.physik.ruhr-uni-bochum.de (Postfix, from userid 514)
	id BD4CB240DE; Sat,  6 Dec 2003 06:49:10 +0100 (CET)
Date: Sat, 6 Dec 2003 06:49:10 +0100
To: current@freebsd.org
Message-ID: <20031206054910.GA15692@fsp1.physik.ruhr-uni-bochum.de>
References: <20031205011711.GA31684@fsp1.physik.ruhr-uni-bochum.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20031205011711.GA31684@fsp1.physik.ruhr-uni-bochum.de>
User-Agent: Mutt/1.3.28i
From: strattbo@fsp1.physik.ruhr-uni-bochum.de (Thomas Stratmann)
Subject: Re: npx: can't get interrupt
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 06 Dec 2003 05:50:23 -0000

Hi current,

the problem exists irrespective of the presence of a device.hints file.
I copied the complete /boot directory from 5.2-BETA (glad the letter "b"
is pretty early in the tar archives...) including a kernel. The result
is the same as stated earlier.

I once had the strange (planned?) effect that after a panic, the kernel
message buffer seemed to simply have been appended to during a
following succesful boot (of a different kernel). If this worked again,
it would be a neat way of capturing the messages without a serial
cable... Since it did not work when I tried a few minutes ago, it might
need something like the chance of nearby kernels using the same address
for the buffer or something.

I will now try an upgrade to 5.1 anyway, which already worked once for
me. Maybe I can tell you more about the problem in a few days (building
is *seriously* slow on this machine...).

Cheers,
Thomas