Date: Thu, 16 May 1996 20:15:17 +0200 From: se@zpr.uni-koeln.de (Stefan Esser) To: erich@uruk.org Cc: freebsd-bugs@freebsd.org Subject: Re: Post 2.1.0 FreeBSD bug in PCI code ?? Message-ID: <199605161815.AA11453@Sparcy42> In-Reply-To: erich@uruk.org "Post 2.1.0 FreeBSD bug in PCI code ??" (May 16, 6:53)
next in thread | raw e-mail | index | archive | help
On May 16, 6:53, erich@uruk.org wrote: } Subject: Post 2.1.0 FreeBSD bug in PCI code ?? } } [ I'm not subscribed to this e-mail list, so please respond directly. ] Hi! I'm currently maintaining the PCI code and I'll look into this ... } I think there is a systematic problem with any version of FreeBSD after } 2.1.0 I've tried. (I've tried most of the 2.2-SNAP releases and they } all exhibit this behavior) } } When running on a PC with multiple PCI buses (and the EISA bus bring } bridged off of a PCI bus), buring the boot sequence, the machine crashes } with a page fault that always looks very similar (I hadn't carefully } written down the dump message from the earlier versions). } } I've tried this on both an Intel Xtended Xpress (Pentium CPUs) and Intel } Alder (Pentium Pro CPUs). They have different chipsets, and are known } to work with other OSes just fine. They even work with 2.1.0 correctly. } A Pentium-Pro machine with the same chipset, but one PCI bus (and no } EISA bridge) works fine. } } I wrote down the error message from 2.2-960501-SNAP. This occurs when } trying "boot.flp". Could please boot with the "-v" option to get verbose boot messages ? Those will give a much better picture of what's going wrong ... } I will probably try to get the source code and do a real debug run of this } at some point soon... Sources are in /sys/pci/pci.c. } avail memory = 61763584 (60316K bytes) } eisa0: <INT31c0 (System Board)> } Probing for devices on the EISA bus } ep0: <3Com 3C579-TP EISA Network Adapter> at 0x3000-0x300f, 0x3c80-0x3c89 irq 5 } ep0: on eisa0 slot 3 } ep0: aui/utp[*AUI*] address 00:20:af:0b:7e:e0 } Probing for devices on PCI bus 0: } chip0 <Intel 82375EB PCI-EISA bridge> rev 5 on pci0:14:0 } pci0:15:0: Intel Corporation, device 0x0008, class=0xff } } Fatal trap 12: page fault while in kernel mode } fault virtual address = 0x16d0d16c } fault code = supervisor read, page not present } instruction pointer = 0x8:0xf016d1aa Could you please check what function fails ? # nm /kernel | grep ^f016 | sort will provide you with a list of symbols. This has to be done with the kernel that wrote the panic message, of course, to be of value ... Regards, STefan -- Stefan Esser, Zentrum fuer Paralleles Rechnen Tel: +49 221 4706021 Universitaet zu Koeln, Weyertal 80, 50931 Koeln FAX: +49 221 4705160 ============================================================================== http://www.zpr.uni-koeln.de/~se <se@ZPR.Uni-Koeln.DE>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199605161815.AA11453>