From owner-freebsd-scsi@FreeBSD.ORG Tue Jun 15 14:12:42 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 374A716A4CE; Tue, 15 Jun 2004 14:12:42 +0000 (GMT) Received: from out-mx1.crosswinds.net (out-mx1.crosswinds.net [216.18.117.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF8EE43D5C; Tue, 15 Jun 2004 14:12:41 +0000 (GMT) (envelope-from tony@crosswinds.net) Received: from admin.crosswinds.net (out-mx1.crosswinds.net [216.18.117.38]) by out-mx1.crosswinds.net (Postfix) with ESMTP id 8A15C2BA66; Tue, 15 Jun 2004 10:12:33 -0400 (EDT) Received: by admin.crosswinds.net (Postfix, from userid 1001) id 544C53F0B; Tue, 15 Jun 2004 10:12:33 -0400 (EDT) Date: Tue, 15 Jun 2004 10:12:33 -0400 From: Tony Holmes To: freebsd-scsi@freebsd.org, freebsd-stable@freebsd.org Message-ID: <20040615141233.GA41523@crosswinds.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: SCSI Probe Problem X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Jun 2004 14:12:42 -0000 Hi! I have a server running 4.9-STABLE that I updated to 4.10 so that I could use a Promise TX-S150 to mirror a pair of SATA disks (seagate). The system currently has 4 SCSI drives on an Adaptec 19160 working flawlessly in them. Prior to the upgrade, the Promise controller and disks were installed, the disks configured in the promise controller and all was fine, except the kernel didn't recognize it, hence the reboot. Initially, I attempted an upgrade to a later 4.9-STABLE and on Friday, to 4.10-RELEASE. In both cases, the boot sequence hung at the SCSI reset (waiting for 15 sec) on the newer kernels. The new kernels were GENERIC with HZ set to 2000 and quotas turned on. Due to the fact that it is a production system, I could not debug further and reverted to the older kernel (with the new world) and it's running fine. Has anyone else experienced this? I noticed no details of any issues with the ahc driver or other issues in the UPDATING, so this perplexes me a litte. I assume that to aid I will have to eventually go in, install the new kernel and boot -v with a paste, but need to do it in the wee hours and warn my customers. -- Tony Holmes Founder and Senior Systems Architect Crosswinds Internet Communications Inc.