From owner-freebsd-bugs Thu May 16 06:51:55 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA02788 for bugs-outgoing; Thu, 16 May 1996 06:51:55 -0700 (PDT) Received: from uruk.org (uruk.org [198.145.95.253]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id GAA02779 for ; Thu, 16 May 1996 06:51:49 -0700 (PDT) From: erich@uruk.org Received: from loopback (loopback [127.0.0.1]) by uruk.org (8.7.4/8.7.3) with SMTP id GAA20179; Thu, 16 May 1996 06:53:49 -0700 (PDT) Message-Id: <199605161353.GAA20179@uruk.org> X-Authentication-Warning: uruk.org: Host loopback [127.0.0.1] didn't use HELO protocol To: freebsd-bugs@freebsd.org cc: erich@uruk.org Subject: Post 2.1.0 FreeBSD bug in PCI code ?? Date: Thu, 16 May 1996 06:53:45 -0700 Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [ I'm not subscribed to this e-mail list, so please respond directly. ] 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". I will probably try to get the source code and do a real debug run of this at some point soon... ---------------------------(error message)-------------------------- avail memory = 61763584 (60316K bytes) eisa0: 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 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 stack pointer = 0x10:0xefbfff0c frame pointer = 0x10:0xefbfff1c code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 0 () interrupt mask = net tty bio panic: page fault ---------------------------(error message)-------------------------- -- Erich Stefan Boleyn \_ E-mail (preferred): Mad Genius wanna-be, CyberMuffin \__ (finger me for other stats) Web: http://www.uruk.org/~erich/ Motto: "I'll live forever or die trying" This is my home system, so I'm speaking only for myself, not for Intel.