ICH6 ID'd correctly now, but breaks in 5.4-STABLE?

J. T. Farmer jfarmer at goldsword.com
Sat Aug 27 20:32:31 GMT 2005


Karl Pielorz wrote:

> I recently installed FreeBSD 5.4-R onto my Dell laptop, and it worked 
> fine. I then updated to 5.4-STABLE (as of 26/08/05) - and it broke...
>
> Specifically, with the new sources it fails to mount the root files 
> system - and instead displays:
>
> "
> Mounting root from ufs:/dev/ad0s2a
> setrootbyname failed
> ffs_mountroot: can't find rootvp
> Rout mount failed: 6
> "
>
> Under 5.4-RELEASE, the IDE controller is ID'd as:
> "
> atapci0: <GENERIC ATA controller> port 
> 0xbfa0-0xbfaf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 irq 10 at device 
> 31.2 on pci0
> ...
> ad0: 57231MB <HTs726060M9AT00/MH40A6EA> [116280/16/63] at ata0-master 
> UDMA33
> "
>
> Under 5.4-STABLE it's now ID'd as:
> "
> atapci0: <Intel ICH6 SATA150 contoller> port 
> 0xbfa0-0xbfaf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 irq 17 at device 
> 31.2 on pci0
> ...
> ad0: 57231MB <HTS726060M9AT100/MH40A6EA> [116280/16/63
> at ata0-master UDMA100
> ad0: FAILURE - READ_DMA status=51<READY,DSC,ERROR> error=4<ABORTED> 
> LBA=117210177
> ad0: FAILURE - READ_DMA status=51<READY,DSC,ERROR> error=4<ABORTED> LBA=0
> ad0: FAILURE - READ_DMA status=51<READY,DSC,ERROR> error=4<ABORTED> LBA=1
> ad0: FAILURE - READ_DMA status=51<READY,DSC,ERROR> error=4<ABORTED> LBA=0
> ad0: FAILURE - READ_DMA status=51<READY,DSC,ERROR> error=4<ABORTED> LBA=0
> acd0: DVDR <SONY DVD+/-RW DW-D56A/PDS7> at ata1-master PIO4


That's because 5.4 is BROKEN.  Check the archives.  You will see a
lot of us b&t#hing and whining about it.  Your original install was
operating the controller in generic mode & using PIO and/or DMA33. 
ANY, repeat ANY attempt to use DMA other than that base mode will
cause the errors you are seeing. 

It's not just the ICH6 chipset.  It's not just SATA.  It happens with
several different chipsets, and with both SATA and PATA.  New
chipsets and old chipsets.  It happens with controllers that used to
work & are still marked as working.

Since there is NO support for the current ATA driver(1), the only
recourse we have been given is to try using Soren's Beta ATA MkIII
patches OR jump to a beta release of 6.0.  So, I suggest that you try
that.


Sigh.  I've used FreeBSD for my servers since the 2.0.x days.  Now
I'm trying to get a basic workstation up under the current STABLE
release so that I can "give back" by working on my current area of
interest (sound subsystem & music creation).  Guys, I want to help.
But I'm not in a position to devote tons of time to dealing with disk
driver issues.  My time for this _has_ to be directed to sound and
music tools & the underlying components.  The sad thing is when
we complain and explain why running beta code is not a choice,
we get ignored or accused of ranting for the sake of ranting.


John      <Yes, I'm not a happy camper...>



(1)  Soren has stated publicly that he is not supporting the current code
       in 5.4.  No-one has come forward to try to fix the current mess.

----------------------------------------------------------------------
John T. Farmer            Owner & CTO                GoldSword Systems
jfarmer at goldsword.com     865-691-6498               Knoxville TN
    Consulting, Design, & Development of Networks & Software



More information about the freebsd-stable mailing list