From owner-freebsd-current Tue Jul 23 18:21:46 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA00141 for current-outgoing; Tue, 23 Jul 1996 18:21:46 -0700 (PDT) Received: from prozac.neuron.net (prozac.neuron.net [165.254.1.213]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA00132 for ; Tue, 23 Jul 1996 18:21:43 -0700 (PDT) Received: (from amir@localhost) by prozac.neuron.net (8.7.5/8.6.12) id VAA00646 for freebsd-current@freebsd.org; Tue, 23 Jul 1996 21:32:09 -0400 (EDT) From: "Amir Y. Rosenblatt" Message-Id: <199607240132.VAA00646@prozac.neuron.net> Subject: more on SCSI problems To: freebsd-current@freebsd.org Date: Tue, 23 Jul 1996 21:32:08 -0400 (EDT) X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Well, despite the CD-ROM drive now being disconnected, as I sat here I heard a couple clicking sounds from the hard drives and beforew I could tail the messages file the machine rebooted. A later look at the messages file showed it didn't even panic -- it just *click* rebooted. I tried bringing it back up; fscked the disks, but as soon as it started syslog I got dropped into the debugger: spec_getpages: I/O read error vm_fault: pager input (probably hardware) error, PID 80 failure Fatal trap 12: page fault while in kernel mode fault virtual address = 0xf602c000 fault code = supervisor read, page not present instruction pointer = 0x8:0xf0108877 stack pointer = 0x10:0xefbffde0 frame pointer = 0x10:0xefbffe0c code segment = base 0x0, limit 0xfffff, type 0x1b = DPL0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume IOPL=0 current process = 80 (sh) interrupt mask = kernel: type 12 trap, code=0 stopped at _exec_aout_imgact+0x17: movl 0(%esi), %edx I rebooted and this time brought up the Adaptec BIOS setup program. Double-checked the settings and then turned off Wide-Negotiation for the tape drive. It's never caused a proibelm before to have it turned on but maybe the newer aic7xxx driver is more sensitive to that stuff. Couldn;t hurt. Any other suggestions? -Amir