ICH6 ID'd correctly now, but breaks in 5.4-STABLE?
Hi All, 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=51READY,DSC,ERROR error=4ABORTED LBA=117210177 ad0: FAILURE - READ_DMA status=51READY,DSC,ERROR error=4ABORTED LBA=0 ad0: FAILURE - READ_DMA status=51READY,DSC,ERROR error=4ABORTED LBA=1 ad0: FAILURE - READ_DMA status=51READY,DSC,ERROR error=4ABORTED LBA=0 ad0: FAILURE - READ_DMA status=51READY,DSC,ERROR error=4ABORTED LBA=0 acd0: DVDR SONY DVD+/-RW DW-D56A/PDS7 at ata1-master PIO4 I did find PR80656: http://www.freebsd.org/cgi/query-pr.cgi?pr=80656 These changes at least on the surface appear to get the controller ID'd OK - but it breaks badly :( The laptop is a Dell XPS Gen 2. I'd guess it's got something to do with the DMA speed being mis-set or something? -Kp ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ICH6 ID'd correctly now, but breaks in 5.4-STABLE?
--On 27 August 2005 16:33 -0400 J. T. Farmer [EMAIL PROTECTED] wrote: ad0: FAILURE - READ_DMA status=51READY,DSC,ERROR error=4ABORTED 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 bt#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. I guess I missed that one, as I was specifically looking for ICH6 issues (hence found the PR, and a lot of chat about ICH6 RAID support) and missed all the rest :( 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. I can't run 6.0 on it - I might see if there's a way of forcing the system to pick the generic/DMA33 driver it was using before, or check the patches out. Failing that, I guess it's back to 5.4-R for me :( Thanks for the info, -Karl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.4 not running HTT
--On 10 June 2005 17:35 +0200 kama [EMAIL PROTECTED] wrote: I have several boxes that I have upgraded from 5.3 to 5.4 and has stopped using the HTT virtal CPU's. This have been going on for a while. the oldest is dated 20050519 and the latest is yesterday. Is there something that I have missed? Been using same configs for 5.3 without any problems. Perhaps, ftp://ftp.freebsd.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-05:09.htt.asc :) -Karl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Going -stable - not as easy as you'd think?
On Sunday 10 June 2001 6:50 pm, Mixtim wrote: Is it related to the recent ipfilter migration to contrib/ ? A lot of people must have a bad source tree or wacky /etc/make.conf options. I've done several make buildworld's with 4.3-STABLE since the IPFilter move and haven't had a single build failure. And yes, I use IPFilter. Hmmm, none of the machines I've been building have actually used it, or had it anywhere in the kernel config... As for 'wacky make.conf'? - Not here :) - Source trees? - The jury's still out - on two of the three machines I'd blown away the whole of /usr/src and re-cvsup'd to see if that fixed... I guess it must (hope) it's just a 'bad patch' [excuse the pun, please :)] -Kp To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
