From owner-freebsd-current Fri Dec 6 00:30:03 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA06868 for current-outgoing; Fri, 6 Dec 1996 00:30:03 -0800 (PST) Received: from rodent.iafrica.com (4Rwmtb5PKakVQfaQPaghC3BuFRmgqSRo@rodent.iafrica.com [196.31.1.10]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id AAA06836 for ; Fri, 6 Dec 1996 00:29:59 -0800 (PST) Received: from rodent.iafrica.com (OS9iqddoVDLZJt3g5J/AFIP9WptW4yh4@localhost [127.0.0.1]) by rodent.iafrica.com (8.8.2/8.7.3) with ESMTP id KAA00115; Fri, 6 Dec 1996 10:28:38 +0200 (SAT) Message-Id: <199612060828.KAA00115@rodent.iafrica.com> X-Mailer: exmh version 1.6.9 8/22/96 To: reg@shale.csir.co.za (Jeremy Lea) cc: current@freebsd.org Subject: Re: 3.0-current Kernel panicking on bootup Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 06 Dec 1996 10:28:38 +0200 From: Mark R V Murray Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk wrote: > Hi... > > Mark R V Murray writes: > > I have a 386sx/40 which is consistently panicking on bootup. This is > > happening in the igmp_init() routine, near as I can determine, and > > the error message at panic time is "priveliged instruction fault > > while in kernel mode". > > Hey, someone else having the same problem as me... was introuced somewhere > after the 28th Nov. Machine is a 386DX/40, with 8MB. Unfortunately I dont > have the space for the CVS tree (dont even have space for /usr/obj :) so I > can't go and back out changes... These files were modified after the 28th > and are being built as part of my kernel: > > sys/i386/i386/machdep.c > sys/i386/i386/support.s : : Strange thing with this it that the same sources are used to build a kernel on a 486dx/50, and that does _not_ panic. Clues, anyone? > Kernel config makes no difference AFAIK. I built about 9 kernels last night - threw out this, put in that. No difference. > Another thought... some pci files are being built (not sure if it's because > of recent changes to if_ed.c etc.) and I'm not including any other pci > stuff... I saw that ed/pci thing and wondered. This board of mine is too ancient to be PCI. M -- Mark Murray Network Engineer, UUNET Internet Africa