From nobody@FreeBSD.org  Sat Mar 24 21:43:57 2001
Return-Path: <nobody@FreeBSD.org>
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by hub.freebsd.org (Postfix) with ESMTP id 6D17337B718
	for <freebsd-gnats-submit@FreeBSD.org>; Sat, 24 Mar 2001 21:43:57 -0800 (PST)
	(envelope-from nobody@FreeBSD.org)
Received: (from nobody@localhost)
	by freefall.freebsd.org (8.11.1/8.11.1) id f2P5hvp46321;
	Sat, 24 Mar 2001 21:43:57 -0800 (PST)
	(envelope-from nobody)
Message-Id: <200103250543.f2P5hvp46321@freefall.freebsd.org>
Date: Sat, 24 Mar 2001 21:43:57 -0800 (PST)
From: RonDzierwa@home.com
To: freebsd-gnats-submit@FreeBSD.org
Subject: 4.2 ata driver fails on CTX laptop
X-Send-Pr-Version: www-1.0

>Number:         26061
>Category:       kern
>Synopsis:       4.2 ata driver fails on CTX laptop
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    sos
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Mar 24 21:50:02 PST 2001
>Closed-Date:    Wed May 30 00:43:17 PDT 2001
>Last-Modified:  Wed May 30 11:10:02 PDT 2001
>Originator:     Ron Dzierwa
>Release:        4.2
>Organization:
Innovative Engineering, Inc.
>Environment:
atapci0: <Generic PCI ATA controller> port
0xfcf0-0xfcff,0x374-0x377,0x170-0x177
,0x2f4-0x3f7,0x1f0-0x1f7 at device 18.1 on pci0
atapci0: Busmastering DMA not supported
ata2: at 0x1f0 on atapci0
ata2: unable to allocate interrupt
device_probe_and_attach: ata2 attach returned 6
ata3: at 0x170 on atapci0
ata3: unable to allocate interrupt
device_probe_and_attach: ata3 attach returned 6

>Description:
I have used this laptop with 2.2.8 for about two years.  I
recently upgraded the disk and decided to upgrade to a newer
version of FreeBSD as well.  The old wd driver worked fine
(my old 2.2.8 boot disk finds the new disk as well as the 
old one). 

Why does the ata driver think it has found ata2 and 3 instead
of ata0 and 1?

>How-To-Repeat:
boot the install flop
>Fix:

>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-bugs->sos 
Responsible-Changed-By: kris 
Responsible-Changed-When: Sun Mar 25 16:41:24 PST 2001 
Responsible-Changed-Why:  
sos is Mr ATA 

http://www.freebsd.org/cgi/query-pr.cgi?pr=26061 
State-Changed-From-To: open->Analyzed 
State-Changed-By: sos 
State-Changed-When: Mon Apr 2 12:17:49 PDT 2001 
State-Changed-Why:  
I have no idea why this happens actually, so you need 
to sit down and try to debug why this fails, evt by 
spprinkling printf's around the probe/attach code. 
If you get me a prober description of what goes wrong 
I'm sure it can be fixed. 


http://www.freebsd.org/cgi/query-pr.cgi?pr=26061 
State-Changed-From-To: Analyzed->closed 
State-Changed-By: sos 
State-Changed-When: Wed May 30 00:43:17 PDT 2001 
State-Changed-Why:  
The problem is that the CTX has bogus PCI reg values 
that screw up the probes, this is not easily worked 
around, and will probably break alot of other (correct) 
machines. My suggestion is to use a local hack for 
this box (which already is done). 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=26061 

From: Ron Dzierwa <RonDzierwa@home.com>
To: freebsd-gnats-submit@FreeBSD.org, RonDzierwa@home.com
Cc:  
Subject: Re: kern/26061: 4.2 ata driver fails on CTX laptop
Date: Wed, 30 May 2001 14:04:36 -0400

 I am not using a local hack.  I am using the WD driver, which works.
 It seems to me the ata driver IS a local hack that only works on the
 small universe of machines that Soren has available to him.  His driver
 sucks.  AND he sucks as well since he is unwilling to fix his bugs. I
 have worked in software engineering for over 20 years, and no self
 respecting engineer would let this kind of thing go by, especially when
 he has been offered help in fixing it!  This ata driver is the only
 piece
 of software that cannot understand the ide controller on this laptop -
 Windoze 95/98/NT all have no problems.  Even Linux 6.2 and 7.1
 understand it.  In his last message, Soren said:
 
 "Other than that it can only be solved by adding even more heuristics
 to the pci probe stuff (which needs ALOT of testing to make sure it
 doesn't break elsewhere)
 
 -Sren
 
 what he needs is less heuristics, and a little more smarts.  If he
 really
 did ALOT of testing in the first place, we would have never gotten
 in this situation.  It seems to me he just got it working for a handful
 of machines that he encountered, and never really designed it to
 work with the real world.
 
 This issue has become a black eye for FreeBSD, at least in the area
 where I work.  It saddens me to see a hacker such as Soren make
 the whole effort look bad to so many people.  RedHat, here I come.
 
 ron.
 
 
 
 
 
 
 
 
 
>Unformatted:
