From owner-freebsd-hackers Wed Nov 22 00:02:43 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id AAA14155 for hackers-outgoing; Wed, 22 Nov 1995 00:02:43 -0800 Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id XAA13578 for ; Tue, 21 Nov 1995 23:57:51 -0800 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) id IAA16504 for freebsd-hackers@freefall.cdrom.com; Wed, 22 Nov 1995 08:50:29 +0100 Date: Wed, 22 Nov 1995 08:50:29 +0100 From: "Christoph P. Kukulies" Message-Id: <199511220750.IAA16504@gilberto.physik.rwth-aachen.de> To: freebsd-hackers@freefall.FreeBSD.org Subject: Re: ncr/pci problem Sender: owner-hackers@FreeBSD.ORG Precedence: bulk I reported a panic caused by an integer divide by zero trap (located as of DG in pentium_microtime (off memory)). This was repeatable as long as I had not set the PCI IRQ for that slot. I was so eager to see the board working that I plugged it in booted and - poof,panic instead of thinking and setting the IRQ first. mea culpa - though it is strange that an unset IRQ is causing such behaviour - a diagnostic would sure be better but I don't know whether it is possible at all to diagnose if an IRQ is set for a PCI slot. (I'm no PCI expert at all) So just to clarify - it was neither a ncr nor a 'general pci' problem as I put it in that posting. --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de