From owner-freebsd-current@FreeBSD.ORG  Tue Aug  3 01:32:01 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 0110116A4CE
	for <current@freebsd.org>; Tue,  3 Aug 2004 01:32:01 +0000 (GMT)
Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 8EA4343D5F
	for <current@freebsd.org>; Tue,  3 Aug 2004 01:32:00 +0000 (GMT)
	(envelope-from scottl@freebsd.org)
Received: from [192.168.0.12] (g4.samsco.home [192.168.0.12])
	(authenticated bits=0)
	by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id i731dPpL037554;
	Mon, 2 Aug 2004 19:39:26 -0600 (MDT)
	(envelope-from scottl@freebsd.org)
Message-ID: <410EEAC8.8010900@freebsd.org>
Date: Mon, 02 Aug 2004 19:30:48 -0600
From: Scott Long <scottl@freebsd.org>
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US;
	rv:1.7) Gecko/20040514
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Daniel Eriksson <daniel_k_eriksson@telia.com>
References: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAA0VcX9IoJqUaXPS8MjT1PdsKAAAAQAAAA5PQ1jek5/EqvRvENdXMWUAEAAAAA@telia.com>
In-Reply-To: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAA0VcX9IoJqUaXPS8MjT1PdsKAAAAQAAAA5PQ1jek5/EqvRvENdXMWUAEAAAAA@telia.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org
cc: 'freebsd current' <current@freebsd.org>
Subject: Re: Panic in today's current, UFS problem?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Aug 2004 01:32:01 -0000

Daniel Eriksson wrote:

> I was trying out the new patch from Ville-Pertti Keinonen that might fix my
> interrupt storm problems with SATA when I ran into a panic. The dmesg is
> attached.
> 
> OS: CURRENT, 2004.08.02.16.00.00
>     + VIA/SATA patch from Ville-Pertti Keinonen
> (http://docs.freebsd.org/cgi/getmsg.cgi?fetch=505643+0+current/freebsd-curre
> nt)
>     + libdisk patch from Lukas Ertl
> (http://docs.freebsd.org/cgi/getmsg.cgi?fetch=526964+0+current/freebsd-curre
> nt)
> 
> 
> What I did:
> 1. fdisk/label two 250GB discs hooked up to the on-board SATA controller
> (using sysinstall)
> 2. copy ~20GB of data to both discs

Is this step necessary in order to produce the panic?

> 3. successfully run the stress-test mentioned in Ville-Pertti Keinonen's
> mail (above)

Is this step necessary also?

> 4. unmount both discs
> 5. run "atacontrol create RAID0 128 ad20 ad22" (the two SATA discs)
> 6. fdisk/label the striped array (using sysinstall, forcing it to UFS1)
> 7. mount the new partition, and create three empty dirs
> 8. *boom*
> 

How reproducable is this, and does it always panic in the same spot? 
There is definitely some sort of buffer corruption going on, and either 
it's happening in the buffer/cache layer or it's a bad DMA from the
drive.

Scott