From nobody  Tue Sep  2 10:37:50 1997
Received: (from nobody@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id KAA17687;
          Tue, 2 Sep 1997 10:37:50 -0700 (PDT)
Message-Id: <199709021737.KAA17687@hub.freebsd.org>
Date: Tue, 2 Sep 1997 10:37:50 -0700 (PDT)
From: atrens@nortel.ca
To: freebsd-gnats-submit@freebsd.org
Subject: 2.2.2 lockup on restart with ASUS-TX97 motherboard + AUTO_EOI_1
X-Send-Pr-Version: www-1.0

>Number:         4453
>Category:       kern
>Synopsis:       2.2.2 lockup on restart with ASUS-TX97 motherboard + AUTO_EOI_1
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Sep  2 10:40:00 PDT 1997
>Closed-Date:    Fri Mar 19 05:03:54 PST 1999
>Last-Modified:  Fri Mar 19 05:04:37 PST 1999
>Originator:     Andrew Atrens
>Release:        2.2.2
>Organization:
self :)
>Environment:
Can't, I've since upgraded to 3.0-SNAP-Aug08 (whatever)
>Description:

I changed from a ASUS T2P4 motherboard with 430HX chipset to an
ASUS TX97 motherboard with a 430TX chipset... System locks up 
on restart while accessing my IDE disks. This behaviour only occurs
when the AUTO_EOI_1, AUTO_EOI_2 kernel options are used.
>How-To-Repeat:

On a system with an ASUS TX97 motherboard, build a kernel with these
options and reboot :) .. Should lock up during filesystem checking/
mounting.
>Fix:

Build a kernel without the AUTO_EOI_X options.
>Release-Note:
>Audit-Trail:

From: Charlie Root <root@genesis.triton.da.ru>
To: freebsd-gnats-submit@freebsd.org, atrens@nortel.ca
Cc:  Subject: Re: kern/4453: 2.2.2 lockup on restart with ASUS-TX97 motherboard + AUTO_EOI_1
Date: Tue, 18 Aug 1998 23:41:13 +0700

 It seems that this problem is occured when any mainboard based on 430TX
 chipset is used. I have changed my motherboard to Lucky Star TX and my
 system was locked when I've just tried to run my old kernel
 configuration. This kernel had AUTO_EOI_X lines. I've solved this
 problem by commenting AUTO_EOI_2 line.
 
State-Changed-From-To: open->closed 
State-Changed-By: sheldonh 
State-Changed-When: Fri Mar 19 05:03:54 PST 1999 
State-Changed-Why:  
Closed on feedback from originator. 
>Unformatted:
