From owner-freebsd-current@FreeBSD.ORG Fri Jul 18 15:13:03 2003 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 2F51637B40A for ; Fri, 18 Jul 2003 15:13:03 -0700 (PDT) Received: from msgbas2x.cos.agilent.com (msgbas1tx.cos.agilent.com [192.25.240.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6075E43F85 for ; Fri, 18 Jul 2003 15:13:02 -0700 (PDT) (envelope-from darrylo@soco.agilent.com) Received: from relcos1.cos.agilent.com (relcos1.cos.agilent.com [130.29.152.239]) by msgbas2x.cos.agilent.com (Postfix) with ESMTP id 744401F14; Fri, 18 Jul 2003 16:12:57 -0600 (MDT) Received: from mina.soco.agilent.com (mina.soco.agilent.com [141.121.54.157]) by relcos1.cos.agilent.com (Postfix) with ESMTP id 647042D8; Fri, 18 Jul 2003 16:13:01 -0600 (MDT) Received: from mina.soco.agilent.com (darrylo@localhost [127.0.0.1]) SMKit7.1.1_Agilent) with ESMTP id PAA15451; Fri, 18 Jul 2003 15:13:00 -0700 (PDT) Message-Id: <200307182213.PAA15451@mina.soco.agilent.com> To: "Kevin Oberman" In-Reply-To: Your message of "Fri, 18 Jul 2003 15:00:54 PDT." <20030718220054.3507B5D07@ptavv.es.net> Mime-Version: 1.0 (generated by tm-edit 1.7) Content-Type: text/plain; charset=US-ASCII Date: Fri, 18 Jul 2003 15:12:59 -0700 From: Darryl Okahata cc: Tobias Roth cc: "M. Warner Losh" cc: current@freebsd.org Subject: Re: Problems with fxp0 on T30 with 5.1-RELEASE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Darryl Okahata List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Jul 2003 22:13:03 -0000 "Kevin Oberman" wrote: > Great to hear that it's working. > > Now I just wonder why you had to do this. My T30 has standard IRQs > (most everything shares 11) and I have not seen this. My fxp0 works > fine with CURRENT and has worked for quite some time, maybe since > pre-5.0-Release. I typically update the system about once a week. Has the OP used ``hw.pci.allow_unsupported_io_range="1"''? I had to use this with my A31 to prevent nasty fxp-related crashes in 5.1-RELEASE. -- Darryl Okahata darrylo@soco.agilent.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day.