From owner-freebsd-current Thu Feb 19 06:00:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA18080 for freebsd-current-outgoing; Thu, 19 Feb 1998 06:00:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from crafti.com.au (root@crafti.com.au [203.23.236.72]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA18071 for ; Thu, 19 Feb 1998 06:00:34 -0800 (PST) (envelope-from operations@stargate.crafti.com.au) Received: from Concordia (modem008.tsv2.crafti.com.au [203.23.238.80]) by crafti.com.au (8.8.8/8.7.3) with SMTP id BAA29136 for ; Fri, 20 Feb 1998 01:04:00 +1100 (EST) Message-Id: <3.0.3.32.19980220010107.00939150@mail.crafti.com.au> X-Sender: sgis@mail.crafti.com.au X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Fri, 20 Feb 1998 01:01:07 +1100 To: current@FreeBSD.ORG From: Kevin Lam Subject: Fatal Trap 18: integer divide fault Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been attempting to install FreeBSD with the latest 3.0-980218-SNAP boot floppy, from scratch, and if I select visual mode to configure my kernel, removing all ISA devices except fdc0, and wdc0, and removing all network cards, and lpt1, it results in fatal trap 18. Earlier symptoms of vm_page_free have since disappeared, though. changing root device to fd0c rootfs is 1440 Kbyte compiled in MFS Fatal trap 18: integer divide fault while in kernel mode instruction pointer = 0x8:0xf01af2f8 stack pointer = 0x10:0xf03c0e64 frame pointer = 0x10:0xf03c0e80 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 0 (swapper) interrupt mask = bio trap number = 18 panic: integer divide fault However, the interesting thing is that if I SKIP kernel configuration and launch with the default kernel, letting them bypass all those devices not present, /stand/sysinstall starts normally. But not all is good, during a custom install, in fact any installation option, results in numerous errors culminating in a failure to create the root partition and filesystem. Switching to vty2 shows a slew of error messages revolving around the SCSI controller, ie. sd0: SCB Abort Request sent, or various other exception errors, and sometimes, reboots. Ultimately, the problems got so severe, the Quantum Fireball TM could no longer be detected _AT_ALL_, wierd noises were heard and the disk subsequently required a low-level format performed by the SCSI controller to restore readable track data. System configuration : AMD K5-PR166, Asus T2P4 (203 BIOS), Adaptec AHA-2940AU (AIC-7860) single-channel, Quantum Fireball TM 3.2GB UltraSCSI on ID 0, Matrox Mystique 4MB SGRAM, IDE CDROM on wdc0, 3Com 3C905 Fast EtherLink XL on vx0, and that's about it. -- Kevin Lam To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message