I can't confirm whether this is actually a duplicate of 26119, but it sounds virtually identical. The problem is only with particular drives. The Seagate ST320413A referenced below causes it, but neither a Seagate ST320420A nor a Western Digital "WDC WD400EB-00CPF0" do.
Paolo:
Assuming it's the same bug, yes, it still persists. This is on a Sun Ultra 5 that's had the problem since it was first reported -- I can't remember whether it started in Breezy or Dapper.
Rouben:
I can't confirm whether this is actually a duplicate of 26119, but it sounds virtually identical. The problem is only with particular drives. The Seagate ST320413A referenced below causes it, but neither a Seagate ST320420A nor a Western Digital "WDC WD400EB-00CPF0" do.
Paolo:
Assuming it's the same bug, yes, it still persists. This is on a Sun Ultra 5 that's had the problem since it was first reported -- I can't remember whether it started in Breezy or Dapper.
root@ull:/etc# cat lsb-release RELEASE= 6.10 CODENAME= edgy DESCRIPTION= "Ubuntu 6.10"
DISTRIB_ID=Ubuntu
DISTRIB_
DISTRIB_
DISTRIB_
root@ull:/etc# cat /proc/ide/hda/model
ST320413A
---[partial dmesg]---
[ 36.653285] hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
[ 36.732586] hda: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=39102336, sector=39102336
[ 36.834668] ide: failed opcode was: unknown
[ 37.025125] hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
[ 37.104357] hda: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=39102336, sector=39102336
[ 37.206434] ide: failed opcode was: unknown
[ 37.397036] hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
[ 37.476233] hda: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=39102336, sector=39102336
[ 37.578311] ide: failed opcode was: unknown
[ 37.768906] hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
[ 37.848109] hda: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=39102336, sector=39102336
[ 37.950187] ide: failed opcode was: unknown
[ 38.000199] hda: DMA disabled
[ 38.094499] ide0: reset: success
Since my Sparc shows the exact same symptoms, it's likely a chipset problem or related to particular drives.