From nobody@FreeBSD.org  Wed Mar 29 05:01:02 2000
Return-Path: <nobody@FreeBSD.org>
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
	by hub.freebsd.org (Postfix) with ESMTP id 86F2B37C091
	for <freebsd-gnats-submit@FreeBSD.org>; Wed, 29 Mar 2000 05:01:02 -0800 (PST)
	(envelope-from nobody@FreeBSD.org)
Received: (from nobody@localhost)
	by freefall.freebsd.org (8.9.3/8.9.2) id FAA89257;
	Wed, 29 Mar 2000 05:01:02 -0800 (PST)
	(envelope-from nobody@FreeBSD.org)
Message-Id: <200003291301.FAA89257@freefall.freebsd.org>
Date: Wed, 29 Mar 2000 05:01:02 -0800 (PST)
From: gandalf@nm.ruhr-uni-bochum.de
Sender: nobody@FreeBSD.org
To: freebsd-gnats-submit@FreeBSD.org
Subject: 4.0-REL hangs after detecting ata1
X-Send-Pr-Version: www-1.0

>Number:         17661
>Category:       i386
>Synopsis:       4.0-REL hangs after detecting ata1
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    sos
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Mar 29 05:10:01 PST 2000
>Closed-Date:    Tue Nov 14 00:21:20 PST 2000
>Last-Modified:  Tue Nov 14 00:22:35 PST 2000
>Originator:     Andre Groe Bley
>Release:        4.0-RELEASE
>Organization:
University of Bochum
>Environment:
(no chance, doesnt boot)
>Description:
AMD K6-2/300, 128 MB Ram, ASUS Board (dont know what type)
Kernel detects atapci "Acer Labs Aladdin ATA 33 Controller", Port 0xb400-0xb40f IRQ 0  (???) dev 15.0 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
And here the machine hangs. CTRL-ALT-DEL wont work.
(hardware connected: ata0: maxtor 20gig hdd, ata1: cdrom, disabling ata1 in bios doesnt help)
>How-To-Repeat:
Just boot from 4.0-REL CD (iso image) or floppy
>Fix:


>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-bugs->sos 
Responsible-Changed-By: sheldonh 
Responsible-Changed-When: Wed Mar 29 05:44:33 PST 2000 
Responsible-Changed-Why:  
Over to the ata maintainer. 

From: Andre Grosse Bley <Andre.Grosse.Bley@nm.ruhr-uni-bochum.de>
To: freebsd-gnats-submit@FreeBSD.org
Cc:  
Subject: Re: i386/17661: 4.0-REL hangs after detecting ata1
Date: Thu, 30 Mar 2000 13:59:45 +0200

 It's an ASUS P5A board. Funny: My father has an ASUS P5A, too. and on
 his machine the boot does complete. It's even the same IDE Controller
 revision - but he has 2 devices on both channels (as far i unterstand
 the driver the controller cant use UDMA then). I suspect UDMA
 initialisation responsible for this problem, i'll try to find out on
 monday. Sorry, no time before...
 
     Andre
 
 

From: Andre Grosse Bley <Andre.Grosse.Bley@nm.Ruhr-Uni-Bochum.DE>
To: freebsd-gnats-submit@FreeBSD.org
Cc:  
Subject: Re: i386/17661: 4.0-REL hangs after detecting ata1
Date: Tue, 18 Apr 2000 17:52:44 +0200

 3.4 runs fine on this, as long i dont enable DMA for wdc0/master. System
 boots, but gives something like "dma error 5: dma active" on every disc access.
 (sorry, forgot to note the correct error message)
 

From: Andre Grosse Bley <Andre.Grosse.Bley@nm.ruhr-uni-bochum.de>
To: freebsd-gnats-submit@FreeBSD.org, gandalf@nm.ruhr-uni-bochum.de
Cc:  
Subject: Re: i386/17661: 4.0-REL hangs after detecting ata1
Date: Mon, 15 May 2000 11:25:39 +0200

 Ha!
 Problem solved. After a long search i found out that a NE 2000 at 0x340
 (and 0x300) hangs the system.
 Win 2k had problems with 0x340, too, but works with 0x300. It looks for
 me like that the PNP read probe
 (Read_port) is misunderstood by the ne2k and blocks the isa bus. But i
 cant imagine why it even in bootverbose hangs after ata1 ....
 
     Andre
 
 
State-Changed-From-To: open->closed 
State-Changed-By: sos 
State-Changed-When: Tue Nov 14 00:21:20 PST 2000 
State-Changed-Why:  
Hardware conflict. 


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