From owner-freebsd-scsi@FreeBSD.ORG Thu Mar 29 13:49:58 2012 Return-Path: Delivered-To: scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8DC9B106566B; Thu, 29 Mar 2012 13:49:58 +0000 (UTC) (envelope-from v.a.popov@gmail.com) Received: from mail-qc0-f182.google.com (mail-qc0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id 38D638FC1D; Thu, 29 Mar 2012 13:49:57 +0000 (UTC) Received: by qcsg15 with SMTP id g15so1636462qcs.13 for ; Thu, 29 Mar 2012 06:49:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:cc:content-type; bh=5Xz6Zi9ivsJKWmDRe0kEbmx3U5M+rmVMjEG9fAx/ynM=; b=iM4eaSG6yGrEXxDpZBUeFKPmpg4ItlSsBPX0kVgyIolU/lsx4N2VJ/Zon7pUnVSWu+ lIizez2vaP/jtARow5hC0U9/RreJTU3vLDaisEZHJkuvjgUtY9XcyTaUaS1SrJOtSHi5 SWjIvJ06rA/YUkA8YbXJ9LAaFUk9TkMIpW77g2C6jfxNOW9AgIpGH5tLnvaRqaZhitoL RAsASSfac2fw80PTO/agVL99ZfioY+UsQqaXhnOios5NLQTEbZMf7+rTjdyJODkF/iKu q5DIgLxvBmqHSZstOqP7XF+TXcJJ3dA6rCfraiXb/tY6gDVtNZUDE4poKb0f6jy3slzZ j/Xw== Received: by 10.224.173.141 with SMTP id p13mr71950qaz.82.1333028997317; Thu, 29 Mar 2012 06:49:57 -0700 (PDT) MIME-Version: 1.0 Received: by 10.229.53.149 with HTTP; Thu, 29 Mar 2012 06:49:40 -0700 (PDT) From: Victor Popov Date: Thu, 29 Mar 2012 17:49:40 +0400 Message-ID: To: stable@freebsd.org Content-Type: text/plain; charset=UTF-8 Cc: scsi@freebsd.org Subject: 9.0-release panics with ASR_COMPAT and raidutil X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Mar 2012 13:49:58 -0000 Hi, My box panics when I use raidutil tool to turn off write-back for arrays and disks, as advised for database setup (because of no battery) and when getting status. Panic occurs immediately after issuing command 'raidutil -d 0 -w off d0b0t0d0', but sometimes it manages to complete and echo that write-back has been turned off. Several minutes after that it panics anyway, maybe on next disk, maybe on 'raidutil -d 0 -L all' to get information about status, maybe on reboot. Sometimes it panics after only one informational command 'raidutil -d 0 -L all' (immediate and several minutes later). Kernel config: include GENERIC ident CTRL1 options SC_HISTORY_SIZE=2000 options IPFIREWALL options IPFIREWALL_DEFAULT_TO_ACCEPT options IPFIREWALL_FORWARD options DUMMYNET options QUOTA options RACCT options RCTL device smbus device smb device ichsmb device ichwd options ASR_COMPAT raidutil is from port sysutils/asr-utils, ASR_COMPAT is added to kernel config to get it working. Several panic textdumps: http://pastebin.com/pnehc75B http://pastebin.com/NnpijeYJ http://pastebin.com/m8qJPPzD http://pastebin.com/UUUwcFMX http://pastebin.com/bP1BEbzG http://pastebin.com/1CWSEgqL No consistent backtrace among them - all different, so I am not including any in this message. vmcore.* dumps are preserved for a while, so they can be used if needed. I have to say that previously this box was running 7.4-release, and at least informational command 'raidutil -d 0 -L all' did not lead to panic. Any hint to help debugging this issue would be greatly appreciated. -- Best regards, Victor Popov