From owner-freebsd-bugs Tue Aug 18 09:50:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA15628 for freebsd-bugs-outgoing; Tue, 18 Aug 1998 09:50:06 -0700 (PDT) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA15571 for ; Tue, 18 Aug 1998 09:50:03 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.8/8.8.5) id JAA01695; Tue, 18 Aug 1998 09:50:00 -0700 (PDT) Date: Tue, 18 Aug 1998 09:50:00 -0700 (PDT) Message-Id: <199808181650.JAA01695@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.ORG From: Charlie Root Subject: Re: kern/4453: 2.2.2 lockup on restart with ASUS-TX97 motherboard + AUTO_EOI_1 Reply-To: Charlie Root Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/4453; it has been noted by GNATS. From: Charlie Root 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. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message