, but the DDB
traceback looks like this:
panic: ata_dmasetup: transfer active on this device!
cpuid = 0
[...]
panic [...]
ata_dmastart(d3075000,4000,0,101) [...]
ata_pci_dmastart(d3075000,4000,0,20) [...]
ata_transaction [...]
ata_start
certain conditions.
Type show copying to see the conditions.
There is absolutely no warranty for GDB. Type show warranty for details.
This GDB was configured as i386-undermydesk-freebsd...
panic: bdwrite: buffer is not busy
panic messages:
---
panic: ata_dmasetup: transfer active on this device
-undermydesk-freebsd...
panic: bdwrite: buffer is not busy
panic messages:
---
panic: ata_dmasetup: transfer active on this device!
syncing disks, buffers remaining... panic: bdwrite: buffer is not busy
Uptime: 3h16m31s
Dumping 255 MB
ata0: resetting devices ..
done
16 32 48 64 80 96 112
On Wed, 05 Mar 2003, Ruslan Ermilov wrote:
A known issue. Soren is working on that.
Ok, I knew in fact that Soren was working on that. What strikes me is
that, from what i see, the situation degrades from kernel to kernel.
So I posted a backtrace in case of an interaction with other
It seems Ian Dowse wrote:
Hi Søren,
I get the above panic every few days when resuming, especially if
the disk was active while the laptop was suspending - it's easy to
reproduce by starting some disk-intensive activity and then hitting
the suspend button. I see that IWASAKI-san posted
devices ..
done
ata1: resetting devices ..
done
panic: ata_dmasetup: transfer active on this device!
Ian
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
