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 [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to