From owner-freebsd-bugs Mon Aug 18 10:20:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA04276 for bugs-outgoing; Mon, 18 Aug 1997 10:20:15 -0700 (PDT) Received: (from gnats@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA04210; Mon, 18 Aug 1997 10:20:06 -0700 (PDT) Resent-Date: Mon, 18 Aug 1997 10:20:06 -0700 (PDT) Resent-Message-Id: <199708181720.KAA04210@hub.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@FreeBSD.ORG, unger@raindrop.seaslug.org Received: from camco.celestial.com (root@camco.celestial.com [192.136.111.1]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA03716 for ; Mon, 18 Aug 1997 10:10:51 -0700 (PDT) Received: from localhost (3687 bytes) by camco.celestial.com via rmail with P:stdio/R:inet_hosts/T:smtp (sender: ) (ident using unix) id for ; Mon, 18 Aug 1997 17:15:09 +0000 (GMT) (Smail-3.2.0.96 1997-Jun-2 #17 built 1997-Jun-24) Received: (from unger@localhost) by raindrop.seaslug.org (8.8.5/8.6.12) id KAA15406; Mon, 18 Aug 1997 10:08:34 -0700 (PDT) Message-Id: <199708181708.KAA15406@raindrop.seaslug.org> Date: Mon, 18 Aug 1997 10:08:34 -0700 (PDT) From: unger@raindrop.seaslug.org Reply-To: unger@raindrop.seaslug.org To: FreeBSD-gnats-submit@FreeBSD.ORG X-Send-Pr-Version: 3.2 Subject: kern/4332: System crash after SCSI DAT tape access. Sender: owner-freebsd-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Number: 4332 >Category: kern >Synopsis: System crash after SCSI DAT tape access. >Confidential: no >Severity: critical >Priority: medium >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Aug 18 10:20:03 PDT 1997 >Last-Modified: >Originator: Thomas Unger >Organization: WWC >Release: FreeBSD 2.2.1-RELEASE i386 >Environment: FreeBSD 2.2.1. See dmesg log in Description section. >Description: After installing 2.2.1 my system would crash when doing tape backups. This seems to happen mostly when it is closing the tape device. Once the system did not crash and I got saved this dmesg log. I do beleive that other crashes show similar messags on the console before the reboot. Copyright (c) 1992-1996 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 2.2.1-RELEASE #0: Mon Jun 23 11:13:15 PDT 1997 rootz@raindrop.seaslug.org:/usr/src/sys/compile/RAINDROP CPU: Pentium (99.87-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x525 Stepping=5 Features=0x3bf real memory = 33554432 (32768K bytes) avail memory = 31145984 (30416K bytes) Probing for devices on PCI bus 0: chip0 rev 17 on pci0:0 chip1 rev 3 on pci0:2:0 vga0 rev 3 on pci0:14 bt0 rev 0 int a irq 11 on pci0:15 bt0: Bt946C/ 0-(32bit) bus bt0: reading board settings, busmastering, int=11 bt0: version 4.28D, async only, parity, 32 mbxs, 32 ccbs bt0: targ 0 async bt0: targ 3 async bt0: targ 5 async bt0: Using Strict Round robin scheme bt0 waiting for scsi devices to settle (bt0:0:0): "SEAGATE ST31230N 0594" type 0 fixed SCSI 2 sd0(bt0:0:0): Direct-Access 1010MB (2069860 512 byte sectors) (bt0:3:0): "SONY CD-ROM CDU-76S 1.1c" type 5 removable SCSI 2 cd0(bt0:3:0): CD-ROM can't get the size (bt0:5:0): "WANGTEK 6130-FS 3.04" type 1 removable SCSI 2 st0(bt0:5:0): Sequential-Access density code 0x13, drive empty Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface mse0 at 0x23c irq 5 on isa fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.44MB 3.5in bt: unit number (1) too high bt1 not found at 0x330 1 3C5x9 board(s) on ISA found at 0x300 ep0 at 0x300-0x30f irq 10 on isa ep0: aui/utp/bnc[*BNC*] address 00:a0:24:2a:3c:77 npx0 on motherboard npx0: INT 16 interface bt0: Try to abort bt0: Abort Operation has timed out st0(bt0:5:0): ILLEGAL REQUEST asc:26,0 Invalid field in parameter list sks:8f,0 Reading from the tape does not seem to cause the problem. Looks similar to problem reports kern/2980 and kern/3671 Tom Unger unger@raindrop.seaslug.org >How-To-Repeat: Pretty much anytime I do a backup I see this problem. >Fix: No known work around. I have to plan on having my system crash after every backup. >Audit-Trail: >Unformatted: