From owner-freebsd-scsi Fri Aug 8 18:51:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA00260 for freebsd-scsi-outgoing; Fri, 8 Aug 1997 18:51:23 -0700 (PDT) Received: from mail.ican.net ([204.92.55.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA00251 for ; Fri, 8 Aug 1997 18:51:17 -0700 (PDT) Received: from oddjob.ican.net (oddjob.ican.net [204.92.55.7]) by mail.ican.net (8.8.6/8.8.6) with ESMTP id VAA00369; Fri, 8 Aug 1997 21:50:36 -0400 (EDT) Received: (from josh@localhost) by oddjob.ican.net (8.8.6/8.8.6) id VAA19917; Fri, 8 Aug 1997 21:51:05 -0400 (EDT) Message-ID: <19970808215105.63789@ican.net> Date: Fri, 8 Aug 1997 21:51:05 -0400 From: Josh Tiefenbach To: Simon Shapiro Cc: scsi@freebsd.org Subject: `problem' with dpt driver v1.2.0 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Shimon, We've been noticing some disturbing behavior with both v1.1.10 and v1.2.0 of the dpt driver. In a nutshell, we cant have unattended reboots. I think the best way of describing the problem, is with dmesg outputs. [shutdown box] syncing disks... 2 done dpt0: Shutting down (mode 0) HBA. Please wait...dpt0: Controller was warned of shutdown and is now disabled Rebooting... [snip] DPT: RAID Manager driver, Version 1.0.0 Probing for devices on PCI bus 0: chip0 rev 2 on pci0:0 DPT: PCI SCSI HBA Driver, version 1.2.0 dpt0 rev 2 int a irq 11 on pci0:13 dpt0: DPT type 3, model PM3334UW firmware 07L0, Protocol 0 on port 1090 with 458753MB Write-Back cache dpt0: Enabled Options: Use Software Interrupts Precisely Track State Transitions Collect Metrics dpt0 waiting for scsi devices to settle dpt0 ERROR: Command "Test Unit Ready [7.24]" recieved for b0t0u0 but controller is shutdown. Aborting... dpt0 ERROR: Command "Inquiry [7.5]" recieved for b0t0u0 but controller is shutdown. Aborting... dpt0 ERROR: Command "Test Unit Ready [7.24]" recieved for b0t1u0 but controller is shutdown. Aborting... [repeated *many* times, followed by eventually] panic: cannot mount root This is, of course, a problem :) The only way I've been able to ameliorate the situation is to boot the machine with an older version of the dpt driver (from floppy no less), wait for it to come up. and reboot with the new driver. Any suggestions? josh -- Josh Tiefenbach - Systems Engineer - ACC TelEnterprises - josh@ican.net