From owner-freebsd-current@FreeBSD.ORG Sat Jan 17 12:55:00 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9D4C316A4CE for ; Sat, 17 Jan 2004 12:55:00 -0800 (PST) Received: from smtp.covadmail.net (mx07.covadmail.net [63.65.120.67]) by mx1.FreeBSD.org (Postfix) with SMTP id 525AB43D1D for ; Sat, 17 Jan 2004 12:54:57 -0800 (PST) (envelope-from strick@covad.net) Received: (covad.net 19700 invoked from network); 17 Jan 2004 20:54:51 -0000 Received: from unknown (HELO mist.nodomain) (strick@covad.net@67.101.100.89) by sun-qmail17 with SMTP; 17 Jan 2004 20:54:51 -0000 Received: from mist.nodomain (localhost [127.0.0.1]) by mist.nodomain (8.12.9p2/8.12.9) with ESMTP id i0HKskCR000733; Sat, 17 Jan 2004 12:54:47 -0800 (PST) (envelope-from dan@mist.nodomain) Received: (from dan@localhost) by mist.nodomain (8.12.9p2/8.12.9/Submit) id i0HKskV9000732; Sat, 17 Jan 2004 12:54:46 -0800 (PST) (envelope-from dan) Date: Sat, 17 Jan 2004 12:54:46 -0800 (PST) From: Dan Strick Message-Id: <200401172054.i0HKskV9000732@mist.nodomain> To: ben@stuyts.nl cc: pdeuskar@FreeBSD.org cc: current@FreeBSD.org cc: dan@mist.nodomain Subject: Re: em0 watchdog reset (kern/60285) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Jan 2004 20:55:00 -0000 On Sat, 17 Jan 2004 19:29:12 +0100, Ben Stuyts wrote: >> > I am trying to setup -current (just cvsupped) on a Gigabyte GA-8KNXP > and I experience the same symptoms as mentioned in the PR in the > subject: em0 keeps getting watchdog resets, and is unusable. > (http://www.freebsd.org/cgi/query-pr.cgi?pr=kern%2F60285) > > It seems there is an acpi problem, which might be related. (pcib2: > could not get PCI interrupt routing table for \\_SB_.PCI0.CSAB - > AE_NOT_FOUND) >> I have precisely the same problem (which is not surprising since I also have precisely the same motherboard). Unfortunately I also have an ATA CD-writer and four ATA disk drives (two of them SATA). If I boot with ACPI disabled, the ethernet interface (em0) works but the SATA driver breaks ("missing" interrupts). This situation is most frustating since both drivers seem to work ok in both release 4.9 and 5.1. Let me know if you discover how to fix the ethernet problem without disabling ACPI. I would really like to be able to run release 5.2. Dan Strick strick@covad.net