From owner-freebsd-hackers  Mon Aug  7 12:27:16 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.11/8.6.6) id MAA26874
          for hackers-outgoing; Mon, 7 Aug 1995 12:27:16 -0700
Received: from relay3.UU.NET (relay3.UU.NET [192.48.96.8])
          by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id MAA26867
          for <hackers@FreeBSD.ORG>; Mon, 7 Aug 1995 12:27:07 -0700
Received: from uucp3.UU.NET by relay3.UU.NET with SMTP 
	id QQzbuj07491; Mon, 7 Aug 1995 15:26:58 -0400
Received: from uanet.UUCP by uucp3.UU.NET with UUCP/RMAIL
        ; Mon, 7 Aug 1995 15:26:50 -0400
Received: by crocodil.monolit.kiev.ua (8.6.8.1/8.5) id WAA29206 for hackers@FreeBSD.ORG; Mon, 7 Aug 1995 22:24:07 +0300
Date: Mon, 7 Aug 1995 22:24:07 +0300
From: System daemons <daemon@crocodil.monolit.kiev.ua>
Message-Id: <199508071924.WAA29206@crocodil.monolit.kiev.ua>
Apparently-To: hackers@FreeBSD.ORG
Sender: hackers-owner@FreeBSD.ORG
Precedence: bulk

I have frequent problems while booting my 2.0.5-RELEASE
with PCI SOYO 486 board and PCI SCI NCR controller
(I have external SCSI CD connected to controller).

Sometimes it boots, and sometimes panics during probing.

happens both with GENERIC and custom kernel.

My PCI board have dynamic INT-to-IRQ assignment, and SCSI uses INT A
(mapped to IRQ 9), on-board 2-channel IDE uses INT B and INT C (should
be IRQ 10 and 11).

The CD-ROM is old HITACHI one. The NCR is SIDE-2953(?).
The motherboard has its own BIOS, which is used before boot, but I dunno
it is used by the driver ;-)