From owner-freebsd-stable Sun Jul 23 16: 3: 9 2000 Delivered-To: freebsd-stable@freebsd.org Received: from sabre.velocet.net (sabre.velocet.net [198.96.118.66]) by hub.freebsd.org (Postfix) with ESMTP id 814AB37BB74 for ; Sun, 23 Jul 2000 16:03:03 -0700 (PDT) (envelope-from dgilbert@office.tor.velocet.net) Received: from office.tor.velocet.net (trooper.velocet.net [216.126.82.226]) by sabre.velocet.net (Postfix) with ESMTP id 7CC86137F12 for ; Sun, 23 Jul 2000 19:02:52 -0400 (EDT) Received: (from dgilbert@localhost) by office.tor.velocet.net (8.9.3/8.9.3) id TAA28607; Sun, 23 Jul 2000 19:02:52 -0400 (EDT) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14715.31131.941891.705718@trooper.velocet.net> Date: Sun, 23 Jul 2000 19:02:51 -0400 (EDT) To: freebsd-stable@freebsd.org Subject: Advansys SCSI controllers. X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have found that the Advansys controller which probes as: adw0: port 0xe800-0xe83f mem 0xe6820000-0xe68200ff irq 11 at device 9.0 on pci0 adw0: SCSI ID 7, High & Low SE Term Enabled, Queue Depth 253 with drives: da0 at adw0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) da1 at adw0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) will under heavy usage spit out the message: Jul 22 19:00:27 mortar /kernel: (da0:adw0:0:0:0): Invalidating pack After which, the machine will respond to incoming telnet requests, but never print login. I assume this to be because the drive is no longer available. This is a server hosted at "rackspace.com". They report that this definately does not happen under 3.4 (which they consider a standard FreeBSD install), but I've found that it does happen with 4.0 and it appears to happen more often under 4.1-RC2. The message itself comes from CAM (scsi_da.c) in response to an ENXIO return code from the lower driver. A number of ENXIO returns were recently removed from the advansys driver, but they were all in a section dealing with attaching the device, etc. Anyhow, there appear to be several places were ENXIO can happen, and CAM appears to consider this unrecoverable. The server at rackspace.com will likely get IDE drives or a different scsi controller, so this is unfortunately a report without much ability to try patches. Rackspace.com aparently knows of this ... they've had this problem come up before with 4.0 installed customers. Replicating the problem is simple: make buildworld exercises it quite quickly. I will likely create a PR unless someone knows of a fix for this. Dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message