From owner-freebsd-stable@FreeBSD.ORG Sun Jan 7 21:54:46 2007 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 53C1B16A49E for ; Sun, 7 Jan 2007 21:54:46 +0000 (UTC) (envelope-from ian@niw.com.au) Received: from cerberus.apdata.com.au (cerberus.apdata.com.au [202.14.95.17]) by mx1.freebsd.org (Postfix) with ESMTP id B3FB313C4AA for ; Sun, 7 Jan 2007 21:54:45 +0000 (UTC) (envelope-from ian@niw.com.au) Received: from localhost.apdata.com.au (localhost.apdata.com.au [127.0.0.1]) by cerberus.apdata.com.au (Postfix) with SMTP id 6814B254194 for ; Mon, 8 Jan 2007 08:03:52 +1030 (CST) Received: from aleph.niw.com.au (aleph.niw.com.au [192.168.101.4]) by cerberus.apdata.com.au (Postfix) with ESMTP id 9B0C22541A2 for ; Mon, 8 Jan 2007 08:03:51 +1030 (CST) Received: from aleph.niw.com.au (localhost [127.0.0.1]) by aleph.niw.com.au (Postfix) with SMTP id A0CBD78C8B for ; Mon, 8 Jan 2007 08:03:50 +1030 (CST) Received: by aleph.niw.com.au (Postfix, from userid 1000) id 2C52D78C8A; Mon, 8 Jan 2007 08:03:50 +1030 (CST) Date: Mon, 8 Jan 2007 08:03:50 +1030 From: Ian West To: freebsd-stable@freebsd.org Message-ID: <20070107213350.GA61293@aleph.niw.com.au> References: <20070105165910.GA37906@zone3000.net> <20070107164336.GA13511@crodrigues.org> <200701071922.l07JMp3K016382@lava.sentex.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200701071922.l07JMp3K016382@lava.sentex.ca> User-Agent: Mutt/1.5.11 X-Kavpostfix-Config: /etc/mail/kavpostfix.aleph X-Kavpostfix-Perl: /etc/mail/aleph.pl X-Kavpostfix-Version: 3.09 X-Spam-Not-Checked: Message sender whitelisted X-Complete-Junk: NO X-Kavpostfix-Config: /etc/mail/kavpostfix.cfg X-Kavpostfix-Perl: /etc/mail/testcode.pl X-Kavpostfix-Version: 3.09 X-Spam-Not-Checked: Message sender whitelisted Subject: Re: kernel panic on 6.2-RC2 with GENERIC. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Jan 2007 21:54:46 -0000 On Sun, Jan 07, 2007 at 02:25:02PM -0500, Mike Tancsa wrote: > At 11:43 AM 1/7/2007, Craig Rodrigues wrote: > >On Fri, Jan 05, 2007 at 06:59:10PM +0200, Nikolay Pavlov wrote: > >> Hello folks. > >> I have kernel panic on GENERIC kernel while executing postmark. > > > >The sequence of steps that Nikolay used to produce this panic was: > > > >- install benchmarks/postmark from ports > > > >root# postmark > >PostMark v1.5 : 3/27/01 > >pm>set number=10000 > >pm>set transactions=10000 > >pm>set subdirectories=10000 > >pm>show > >pm>run > > I am able to do this on an AMD64 on a AREAC RAID6 file system and on > a plain old ata drive on i386 without issue. > > the i386 is a few weeks old but I will cvsup and re-try to confirm on > both today > > [tyan-1u]# postmark > PostMark v1.5 : 3/27/01 > pm>set number=10000 > pm>set transactions=10000 > pm>set subdirectories=10000 > pm>set location /tmp > pm>run > Creating subdirectories...Done > Creating files...Done > Performing transactions..........Done > Deleting files...Done > Deleting subdirectories...Done > Time: > 481 seconds total > 233 seconds of transactions (42 per second) > > Files: > 15027 created (31 per second) > Creation alone: 10000 files (62 per second) > Mixed with transactions: 5027 files (21 per second) > 4990 read (21 per second) > 5009 appended (21 per second) > 15027 deleted (31 per second) > Deletion alone: 10054 files (115 per second) > Mixed with transactions: 4973 files (21 per second) > > Data: > 27.14 megabytes read (57.78 kilobytes per second) > 85.08 megabytes written (181.13 kilobytes per second) > pm>quit > [tyan-1u]# uname -a > FreeBSD tyan-1u.sentex.ca 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #1: > Mon Dec 11 17:45:45 EST > 2006 mdtancsa@tyan-1u.sentex.ca:/usr/obj/usr/src/sys/tyan i386 > [tyan-1u]# > > > and amd64 > > pm>show > Current configuration is: > The base number of files is 10000 > Transactions: 10000 > Files range between 500 bytes and 9.77 kilobytes in size > Working directory: > /mnt (weight=1) > 10000 subdirectories will be used > Block sizes are: read=512 bytes, write=512 bytes > Biases are: read/append=5, create/delete=5 > Using Unix buffered file I/O > Random number generator seed is 42 > Report format is verbose. > pm>run > Creating subdirectories...Done > Creating files...Done > Performing transactions..........Done > Deleting files...Done > Deleting subdirectories...Done > Time: > 310 seconds total > 155 seconds of transactions (64 per second) > > Files: > 15027 created (48 per second) > Creation alone: 10000 files (103 per second) > Mixed with transactions: 5027 files (32 per second) > 4990 read (32 per second) > 5009 appended (32 per second) > 15027 deleted (48 per second) > Deletion alone: 10054 files (173 per second) > Mixed with transactions: 4973 files (32 per second) > > Data: > 27.14 megabytes read (89.65 kilobytes per second) > 85.08 megabytes written (281.04 kilobytes per second) > pm>quit > [r2-releng6-64]# uname -a > FreeBSD r2-releng6-64.sentex.ca 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE > #0: Thu Dec 28 23:13:18 EST > 2006 mdtancsa@r2-releng6-64.sentex.ca:/usr/obj/usr/src/sys/router amd64 > [r2-releng6-64]# > > > both file systems have normal newfs options and fairly standard > kernels with default /etc/make.conf and both are SMP I have seen this identical fault with the new areca driver, my machine is opteron hardware, but running a regular i386/SMP kernel/world. With everything at 6.2RC2 (as of 29th of December) except the areca driver the machine is rock solid, with the 29th of december version of the areca driver the box will crash on extract of a large tar file, removal of a large directory structure, or pretty much anything that does a lot of disk io to different files/locations. There is no error log prior to seeing the following messages.. Dec 29 14:26:44 aleph kernel: g_vfs_done():da0s1g[WRITE(offset=433078272, length=8192)]error = 5 Dec 29 14:26:44 aleph kernel: g_vfs_done():da0s1g[WRITE(offset=433111040, length=16384)]error = 5 Dec 29 14:26:44 aleph kernel: g_vfs_done():da0s1g[WRITE(offset=433209344, length=16384)]error = 5 Dec 29 14:26:44 aleph kernel: g_vfs_done():da0s1g[WRITE(offset=433242112, length=32768)]error = 5 Dec 29 14:26:44 aleph kernel: g_vfs_done():da0s1g[WRITE(offset=437612544, length=4096)]error = 5 Dec 29 14:26:44 aleph kernel: g_vfs_done():da0s1g[WRITE(offset=437616640, length=12288)]error = 5 Dec 29 14:26:44 aleph kernel: g_vfs_done():da0s1g[WRITE(offset=437633024, length=6144)]error = 5 Dec 29 14:26:44 aleph kernel: g_vfs_done():da0s1g[WRITE(offset=437639168, length=2048)]error = 5 Dec 29 14:26:44 aleph kernel: g_vfs_done():da0s1g[WRITE(offset=437641216, length=6144)]error = 5 There are a string of these, followed by a crash and reboot. The file system state can be left very dirty to the point where background fsck seems unable to recover it. The areca card in question is running the latest firmware/boot and has shown no problems either before, or since backing out the areca driver. The volume is ran the tests on was a 250G on a raid6 raid set.