sparc64/82261: DMA-support on Sparc64 broken

Linh Pham question at
Thu Jul 28 02:30:22 GMT 2005

The following reply was made to PR sparc64/82261; it has been noted by GNATS.

From: Linh Pham <question at>
To: bug-followup at, aces at
Subject: Re: sparc64/82261: DMA-support on Sparc64 broken
Date: Wed, 27 Jul 2005 19:25:22 -0700

 I just wanted to report that I experienced the same problem with my Sun
 Blade 100 system (using both the stock Sun hard drive and two
 off-the-shelf drives, one Seagate 7200.7 ATA100 and an older WD 8GB)
 running 5.4-RELEASE.
 I'm guessing this impacts all Blade 100/150, Netra X1 and Fire V100
 servers as they all seem to use the same chipset (give or take a little
 Setting hw.ata.ata_dma to 0 does fix the problem with my Blade 100 (and
 Blade 150, nearly if not identical motherboard but US-IIi instead of
 I haven't run into the same problem while running 5.4-RELEASE or
 6.0-BETA on a Sun Ultra 10 using a Seagate Barracuda IV 40GB drive;
 probably because it uses a different ATA controller (which isn't great
 to begin with).
 Linh Pham
 question at

More information about the freebsd-sparc64 mailing list