From owner-freebsd-stable@FreeBSD.ORG Sun Jun 26 08:14:02 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 43A4516A41C for ; Sun, 26 Jun 2005 08:14:02 +0000 (GMT) (envelope-from christias@gmail.com) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id F2DE343D5C for ; Sun, 26 Jun 2005 08:14:01 +0000 (GMT) (envelope-from christias@gmail.com) Received: by rproxy.gmail.com with SMTP id i8so696639rne for ; Sun, 26 Jun 2005 01:14:01 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:mime-version:content-type:content-transfer-encoding:content-disposition; b=ONGbjpUsJH/1tFoDRLtsV8bUKicFrHw6/W9BB/vsGK/ZzMIWwLnZ/KU8/Z580946fkxuSmLjfRjQgThZhMHHOfFz5+Gx09vnFnL1pXrYico77zjZ/SCny9QpRx8B3apaE+ZJYL+JIMIf6ZlgEjThC40pCeYwupzXPqkybxeNE0w= Received: by 10.38.78.53 with SMTP id a53mr2095517rnb; Sun, 26 Jun 2005 01:14:01 -0700 (PDT) Received: by 10.38.78.72 with HTTP; Sun, 26 Jun 2005 01:14:01 -0700 (PDT) Message-ID: Date: Sun, 26 Jun 2005 11:14:01 +0300 From: Panagiotis Christias To: freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Cc: freebsd-scsi@freebsd.org Subject: Strange SCSI behavior after upgrading from 5.2.1 to 5.4 (and a panic) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Panagiotis Christias List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Jun 2005 08:14:02 -0000 Hello, on Thurday we upgraded one of our last 5.2.1 servers to 5.4. Tonight the server panicked, crashed and I had to power it off and on. Here are the logs before the panic: Jun 26 03:45:50 patroklos kernel: (da0:ahc0:0:0:0): lost device Jun 26 03:45:50 patroklos kernel: (da0:ahc0:0:0:0): Invalidating pack Jun 26 03:46:00 patroklos last message repeated 2 times Jun 26 03:46:06 patroklos kernel: initiate_write_filepage: already started Jun 26 03:46:07 patroklos last message repeated 9 times Jun 26 03:46:07 patroklos kernel: (da0:ahc0:0:0:0): READ(10). CDB: 28 0 72 f 16 0 0 0 80 0 Jun 26 03:46:07 patroklos kernel: (da0:ahc0:0:0:0): CAM Status: SCSI Status Error Jun 26 03:46:07 patroklos kernel: (da0:ahc0:0:0:0): SCSI Status: Check Cond= ition Jun 26 03:46:07 patroklos kernel: (da0:ahc0:0:0:0): UNIT ATTENTION asc:29,0 Jun 26 03:46:07 patroklos kernel: (da0:ahc0:0:0:0): Power on, reset, or bus device reset occurred Jun 26 03:46:07 patroklos kernel: (da0:ahc0:0:0:0): Retries Exhausted Jun 26 03:46:07 patroklos kernel: (da0:ahc0:0:0:0): Invalidating pack Jun 26 03:46:31 patroklos kernel: initiate_write_filepage: already started Jun 26 03:46:43 patroklos kernel: panic: initiate_write_inodeblock_ufs2: already started As I said the machine could not recover from the panic so there ais no crashdump. The 5.4 version of the dmesg output is available at: http://noc.ntua.gr/~christia/tmp/dmesg-5.4.txt The 5.2.1 version of the dmesg output is available at: http://noc.ntua.gr/~christia/tmp/dmesg-5.2.1.txt da0 is an 1302GB external IDE to SCSI RAID (8x200GB IDE drives in RAID5 configuration and a SCSI U160 interface). FreeBSD 5.4 connects to da0 at 80MB/s (40.000MHz, offset 31, 16bit, Tagged Queueing Enabled), while FreeBSD 2.5.1 (and FreeBSD 5.3 - just tried to boot with the 5.3-RELEASE-i386-miniinst.iso) connects happily at 160MB/s (80.000MHz, offset 62, 16bit, Tagged Queueing Enabled) which is the transfer rate supported by the RAID device and the SCSI card (Adaptec 3960D Ultra160 SCSI adapter/aic7899). Any ideas what could be or where could be the problem? What has changed in = 5.4? We had preserved the 5.2.1 system disks and after the crash we moved back to 5.2.1 until further notice. Now I'm thinking of trying 5.3 which seems to have the same behavior as 5.2.1 and will be still supported for a year or so. Thanks, Panagiotis