From owner-freebsd-current@FreeBSD.ORG Sun Mar 13 01:14:15 2005 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 DC3E416A4CE; Sun, 13 Mar 2005 01:14:15 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 404F643D54; Sun, 13 Mar 2005 01:14:15 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.13.3/8.13.1) with ESMTP id j2D1D0Hn030383; Sat, 12 Mar 2005 18:13:00 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sat, 12 Mar 2005 18:13:15 -0700 (MST) Message-Id: <20050312.181315.128047222.imp@bsdimp.com> To: mdodd@freebsd.org From: "M. Warner Losh" In-Reply-To: <20050312153002.U88834@sasami.jurai.net> References: <423350B6.1000706@gmx.de> <20050312153002.U88834@sasami.jurai.net> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: incmc@gmx.de cc: freebsd-current@freebsd.org Subject: Re: Apm / Resume: pir0: ROUTE_INTERRUPT on resume .... failed 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: Sun, 13 Mar 2005 01:14:16 -0000 In message: <20050312153002.U88834@sasami.jurai.net> "Matthew N. Dodd" writes: : On Sat, 12 Mar 2005, Jochen Gensch wrote: : > On resume, the system fails with the following message: : > : > pir0: ROUTE_INTERRUPT on resume for link 0x68 failed : : pir0: ROUTE_INTERRUPT on resume for link 0x60 failed. : pir0: ROUTE_INTERRUPT on resume for link 0x63 failed. : pir0: ROUTE_INTERRUPT on resume for link 0x61 failed. : : I get this too, but it doesn't seem to cause any problems. My experiences with PCI BIOS suggest that routing a pin that's already routed will produce an error return from the call, but the pin will still be routed and interrupts will still work. Some systems apparently report an error also when you reroute an interrupt after suspend/resume in APM as well. Unless it causes problems, chances are excellent it can be ignored. Warner