From nobody@FreeBSD.org  Tue Jul  6 19:09:27 2004
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 697F516A4CE
	for <freebsd-gnats-submit@FreeBSD.org>; Tue,  6 Jul 2004 19:09:27 +0000 (GMT)
Received: from www.freebsd.org (www.freebsd.org [216.136.204.117])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 66FDA43D39
	for <freebsd-gnats-submit@FreeBSD.org>; Tue,  6 Jul 2004 19:09:27 +0000 (GMT)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.12.11/8.12.11) with ESMTP id i66J9Qbi025260
	for <freebsd-gnats-submit@FreeBSD.org>; Tue, 6 Jul 2004 19:09:27 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.12.11/8.12.11/Submit) id i66J9Q47025259;
	Tue, 6 Jul 2004 19:09:26 GMT
	(envelope-from nobody)
Message-Id: <200407061909.i66J9Q47025259@www.freebsd.org>
Date: Tue, 6 Jul 2004 19:09:26 GMT
From: Adam Retter <adam@adamretter.eclipse.co.uk>
To: freebsd-gnats-submit@FreeBSD.org
Subject: Cant boot 5.2.1-RELEASE GENERIC kernel
X-Send-Pr-Version: www-2.3

>Number:         68735
>Category:       kern
>Synopsis:       Cant boot 5.2.1-RELEASE GENERIC kernel
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    sos
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Jul 06 19:10:24 GMT 2004
>Closed-Date:    Tue Aug 24 20:00:56 GMT 2004
>Last-Modified:  Tue Aug 24 20:00:56 GMT 2004
>Originator:     Adam Retter
>Release:        5.2.1-RELEASE
>Organization:
(Just Me)
>Environment:
>Description:
I have been trying to cvsup from 5.2-RELEASE to 5.2.1-RELEASE. 5.2-RELEASE had been installed for severall weeks and working fine.

I can boot the 5.2-RELEASE GENERIC kernel, but if I build the 5.2.1-RELEASE GENERIC kernel after a cvsup of /usr/src and then a buildworld and reboot the machine. The system hangs whilst booting the 5.2.1-RELEASE GENERIC kernel with the following messages -

Mounting Root from ufs: /dev/ad8s2a
ad8: TIMEOUT READ_DMA retrying (2 retries left) LBA=51199379
GEOM: destroy disk ad8 dp=0xc6a4ea60
ad8: WARNING - removed from configuration

From http://www.uk.freebsd.org/releases/5.2.1R/announce.html I see this "Significantly improved ATA/IDE and SATA handling. Problems with timeouts, error recovery, and certain master/slave configurations have been largely addressed."

Unfortunately these significant improvements have actually broken my SATA support :-( This is most upsetting as my SATA drives wouldnt work under 4.x, 5 or 5.1 but did work nicely under 5.2, but 5.2.1 seems to be a step backwards.

I have an MSI 848P-Neo Motherboard that uses the Intel ICH5 SATA Chipset and I am using two Maxtor SATA hard-disks (1x120GB and 1x160GB).

Can someone help me or can I help someone debug this problem and get my SATA support working again, I really dont want to go to -CURRENT as this is my workstation machine, I usually use -RELENG.

Thanks
>How-To-Repeat:

Get an MSI 848P-Neo motherboard and a SATA hard-disk and try and boot 5.2.1-RELEASE.
>Fix:

Merge the SATA code for the ICH5 from 5.2 with that from 5.2.1???2
>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-bugs->sos 
Responsible-Changed-By: arved 
Responsible-Changed-When: Tue Aug 24 19:08:11 GMT 2004 
Responsible-Changed-Why:  
Another PR for the ATA maintainer. 


http://www.freebsd.org/cgi/query-pr.cgi?pr=68735 
State-Changed-From-To: open->closed 
State-Changed-By: sos 
State-Changed-When: Tue Aug 24 19:58:50 GMT 2004 
State-Changed-Why:  
The ich5 problems has been solved in -current fro quite some time. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=68735 
>Unformatted:
