From owner-freebsd-current  Tue Sep  3 12:57: 8 2002
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 9EF6037B400
	for <current@freebsd.org>; Tue,  3 Sep 2002 12:57:03 -0700 (PDT)
Received: from mailout10.sul.t-online.com (mailout10.sul.t-online.com [194.25.134.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP id ECAD543E6A
	for <current@freebsd.org>; Tue,  3 Sep 2002 12:57:02 -0700 (PDT)
	(envelope-from D.Rock@t-online.de)
Received: from fwd07.sul.t-online.de 
	by mailout10.sul.t-online.com with smtp 
	id 17mJnJ-0000aV-07; Tue, 03 Sep 2002 21:57:01 +0200
Received: from dialin.t-online.de (340029380333-0001@[217.224.23.110]) by fmrl07.sul.t-online.com
	with esmtp id 17mJn3-053knoC; Tue, 3 Sep 2002 21:56:45 +0200
Received: from t-online.de (server [172.23.7.1])
	by dialin.t-online.de (8.11.6+Sun/8.11.6/Rock) with ESMTP id g83JuWv77234
	for <current@freebsd.org>; Tue, 3 Sep 2002 21:56:32 +0200 (CEST)
Message-ID: <3D7513F0.5000803@t-online.de>
Date: Tue, 03 Sep 2002 21:56:32 +0200
From: "D. Rock" <D.Rock@t-online.de>
User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:0.9.4.1) Gecko/20020518 Netscape6/6.2.3
X-Accept-Language: en-us
MIME-Version: 1.0
To: current@freebsd.org
Subject: CURRENT unstable during heavy file system I/O
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Sender: 340029380333-0001@t-dialin.net
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG

Hi,

since some months now my -CURRENT is very unstable during heavy file system
activity (parallel accesses while deleting large subdirectories).

Today, I ran the following command for simple cleanup of /usr/ports:

# find /usr/ports -type d -name work -print | xargs rm -rf

[Yes, I should have added an option -maxdepth 3]. During this cleanup the
machine panic'd twice. I don't have a crash dump, only console output:

Fatal double fault:
eip = 0xc04304c8
esp = 0xd85e8fb8
ebp = 0xd85e980c
panic: double fault
Debugger("panic")
Stopped at      Debugger+0x54:  xchgl   %ebx,in_Debugger.0
db> c

syncing disks... panic: bwrite: buffer is not busy???
Debugger("panic")
Stopped at      Debugger+0x54:  xchgl   %ebx,in_Debugger.0
db> c
Uptime: 26m29s
Dumping 127 MB
ata0: resetting devices ..
panic: bremfree: removing a buffer not on a queue
Debugger("panic")
Stopped at      Debugger+0x54:  xchgl   %ebx,in_Debugger.0
db> c
Uptime: 26m29s
Terminate ACPI
Automatic reboot in 15 seconds - press a key on the console to abort

gdb at address 0xc04304c8:
Dump of assembler code for function bus_dmamap_load:
0xc0430340 <bus_dmamap_load>:   push   %ebp
[...]
0xc04304b8 <bus_dmamap_load+376>:       mov    %eax,0xfffffff0(%ebp)
0xc04304bb <bus_dmamap_load+379>:       mov    0xffffffe4(%ebp),%edx
0xc04304be <bus_dmamap_load+382>:       mov    %edx,0xffffffe0(%ebp)
0xc04304c1 <bus_dmamap_load+385>:       movl   $0x1,0xffffffdc(%ebp)
0xc04304c8 <bus_dmamap_load+392>:       movl   $0x0,0x4(%edx)
0xc04304cf <bus_dmamap_load+399>:       movl   $0x0,0xffffffd4(%ebp)
0xc04304d6 <bus_dmamap_load+406>:       lea    0x0(%esi),%esi
0xc04304d9 <bus_dmamap_load+409>:       lea    0x0(%edi,1),%edi
0xc04304e0 <bus_dmamap_load+416>:       mov    0xfffffff0(%ebp),%ecx
0xc04304e3 <bus_dmamap_load+419>:       mov    %ecx,%eax
0xc04304e5 <bus_dmamap_load+421>:       shr    $0x16,%eax

The panic "bwrite: buffer is not busy???" is always the same.


Daniel


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message