From sos@spider.deepcore.dk  Sat Feb 22 03:56:38 2003
Return-Path: <sos@spider.deepcore.dk>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 1067937B401; Sat, 22 Feb 2003 03:56:38 -0800 (PST)
Received: from spider.deepcore.dk (cpe.atm2-0-56339.0x50c6aa0a.abnxx2.customer.tele.dk [80.198.170.10])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 2F7DA43FBF; Sat, 22 Feb 2003 03:56:35 -0800 (PST)
	(envelope-from sos@spider.deepcore.dk)
Received: (from sos@localhost)
	by spider.deepcore.dk (8.12.5/8.12.6) id h1MBuXQv094483;
	Sat, 22 Feb 2003 12:56:33 +0100 (CET)
	(envelope-from sos)
Message-Id: <200302221156.h1MBuXQv094483@spider.deepcore.dk>
Date: Sat, 22 Feb 2003 12:56:33 +0100 (CET)
From: Soeren Schmidt <sos@spider.deepcore.dk>
To: David Schultz <dschultz@uclink.Berkeley.EDU>
Cc: FreeBSD-gnats-submit@freebsd.org, sos@freebsd.org
In-Reply-To: <20030222112002.GA71537@HAL9000.homeunix.com>
Subject: Re: ata driver incorrectly downgrades UDMA4 drives

>Number:         48558
>Category:       kern
>Synopsis:       Re: ata driver incorrectly downgrades UDMA4 drives
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    gnats-admin
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Feb 22 04:00:26 PST 2003
>Closed-Date:    Mon Feb 24 14:26:21 PST 2003
>Last-Modified:  Mon Feb 24 14:26:21 PST 2003
>Originator:     
>Release:        
>Organization:
>Environment:
>Description:
 It seems David Schultz wrote:
 > > >Description:
 > > My primary IDE controller has two drives, only one of which is
 > > normally mounted.  The other one spins down after twenty minutes.
 > > But if I suspend the system using either `zzz' or `acpiconf -s 1'
 > > and then resume, the `sleeping' drive is downgraded to UDMA2 when
 > > the controller is reset.  The exact message is:
 > > 
 > >         DMA limited to UDMA33, non-ATA66 cable or device
 > > 
 > > Both drives support UDMA4 and have worked fine for years.
 > 
 > FYI, the new ATA code in -CURRENT solves this problem.  I would
 > have referenced this PR when I mailed you the fix the other
 > month, but I forgot I filed this!
 
 Okies, thanks for reporting back!
 
 -Sren
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: keramida 
State-Changed-When: Mon Feb 24 14:25:32 PST 2003 
State-Changed-Why:  
Followup to kern/40225 misfiled as a new PR. 

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