From owner-freebsd-questions Tue Jan 10 12:38:19 1995 Return-Path: questions-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id MAA03705 for questions-outgoing; Tue, 10 Jan 1995 12:38:19 -0800 Received: from estienne.cs.berkeley.edu (estienne.CS.Berkeley.EDU [128.32.42.147]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id MAA03699 for ; Tue, 10 Jan 1995 12:38:18 -0800 Received: (from gibbs@localhost) by estienne.cs.berkeley.edu (8.6.9/8.6.9) id NAA12733; Tue, 10 Jan 1995 13:10:06 -0800 From: "Justin T. Gibbs" Message-Id: <199501102110.NAA12733@estienne.cs.berkeley.edu> Subject: Re: problems installing 2.0 To: jcarr@freedom.wit.com (Jeff Carr) Date: Tue, 10 Jan 1995 13:10:06 -0800 (PST) Cc: questions@FreeBSD.org In-Reply-To: <199501091712.RAA02678@freedom.wit.com> from "Jeff Carr" at Jan 9, 95 05:12:54 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1891 Sender: questions-owner@FreeBSD.org Precedence: bulk I think I might have a patch for your problem. My guess is that the 2842 is in the wrong interrupt mode and we are attempting to service a bogus command complete (or something) in the interrupt handler. My latest, latest, latest, boot floppy has code that should avoid this: freefall.cdrom.com:/incoming/294x_boot_144.flp.gz > We are using Freebsd 2.0 to run our site www.wit.com. We have purchased > another machine to take some of the load of our single machine, it is > a 486/66 with an Adaptec 2842VL scsi card and a 3com 3C509 Etherlink III > ethernet card. > While trying to install 2.0 with the newest boot_144 floppy, I get > the following: > > wt0 not found at 0x300 > mcd0: timeout getting status > mcd0: not found at 0x300 > mcd1: timeount getting status > mcd1 not found at 0x340 > ie0 not found at 0x360 > 1 3C5x9 board(s) on ISA found at 0x300 > ep0 at 0x300-0x30f irq 10 on isa > ep0: aui/bnc[*BNC*] address 00:20:af:15:e4:9b > is0 not found at 0x200 > le0 not probed due to I/O address conflict with ep0 at 0x300 > ze0 not probed due to I/O address conflict with ep0 at 0x300 > npx0 on motherboard > changing root device to fd0c > > > Fatal trap 9: general protection fault while in kernal mode > instruction pointer = 0x8:0xf015fda0 > code segment = base 0x0, limit 0xffffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 0 () > inturrupt mask = > panic: general protection fault > hit reset please > > any ideas? I'll make an attempt to get different hardware if that is > the problem. I'd be forever in debt if someone could help me out on this. > jcarr@wit.com > -- Justin T. Gibbs ============================================== TCS Instructional Group - Programmer/Analyst 1 Cory | Po | Danube | Volga | Parker | Torus ==============================================