From owner-freebsd-current@FreeBSD.ORG  Thu Dec  4 17:16:57 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 9AB4E16A4CE
	for <current@freebsd.org>; Thu,  4 Dec 2003 17:16:57 -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 C158D43FD7
	for <current@freebsd.org>; Thu,  4 Dec 2003 17:16:56 -0800 (PST)
	(envelope-from strattbo@fsp1.physik.ruhr-uni-bochum.de)
Received: by fsp1.physik.ruhr-uni-bochum.de (Postfix, from userid 514)
	id 7E82A240DE; Fri,  5 Dec 2003 02:17:11 +0100 (CET)
Date: Fri, 5 Dec 2003 02:17:11 +0100
To: current@freebsd.org
Message-ID: <20031205011711.GA31684@fsp1.physik.ruhr-uni-bochum.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.28i
From: strattbo@fsp1.physik.ruhr-uni-bochum.de (Thomas Stratmann)
Subject: 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: Fri, 05 Dec 2003 01:16:57 -0000

Hi current,

I'm in the middle of upgrading from 4.8 to Current. I build a new kernel
following the instructions in UPDATING (bottom of file). The new kernel
panics in the npx probe with:

panic: npx: can't get interrupt

(not sure about each char, typing this out of my memory)
I also noticed that the message like "can't find parallel port" (less
sure than above) is printed three or more times.
The machine is a Toshiba Libretto 110. It has been running Current from
about three months ago successfully.
I was aware of the current acpi module issues, so the kernel that
panic'd had

device   acpi
option   ACPI_DEBUG

in its config file.

Can anyone tell me why I seem to be running out of interrupts, or
otherwise help me to fix this problem?
If the exact kernel probe messages are needed for this, please someone
tell me if it's possible to get these without setting up a serial
console connection, it would quite some trouble with my little
machine...

Thanks in advance,
Thomas