From owner-freebsd-current  Sat Nov  7 20:56:13 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id UAA27838
          for freebsd-current-outgoing; Sat, 7 Nov 1998 20:56:13 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA27833
          for <current@FreeBSD.ORG>; Sat, 7 Nov 1998 20:56:09 -0800 (PST)
          (envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id PAA07388;
	Sun, 8 Nov 1998 15:55:48 +1100
Date: Sun, 8 Nov 1998 15:55:48 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199811080455.PAA07388@godzilla.zeta.org.au>
To: chris@netmonger.net, current@FreeBSD.ORG
Subject: Re: Lock up on accessing sio?
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>As another data point, we had previously tried putting 2.2.7-STABLE on
>it, and it was locking up right after booting.. it's possible that the

2.2.7 probably suffers from the same change as 3.0.

>sio0: configured irq 4 not in bitmap of probed irqs 0
>sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa
>sio0: type 8250

>The "configured irq 4 not in bitmap" line also appeared when booting
>2.2.5.. I don't think it's significant.

It's very significant, but can't appear in 2.2.5.  It means that interrupts
don't seem to be working.  2.2.5 would have failed the probe at this point.

Bruce

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message