From owner-freebsd-questions@FreeBSD.ORG Mon Mar 29 01:31:24 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 48FB916A4CE for ; Mon, 29 Mar 2004 01:31:24 -0800 (PST) Received: from smtp3.adl2.internode.on.net (smtp3.adl2.internode.on.net [203.16.214.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8A58143D31 for ; Mon, 29 Mar 2004 01:31:23 -0800 (PST) (envelope-from ws+freebsd-questions@au.dyndns.ws) Received: from lillith-iv.ovirt.dyndns.ws (ppp34-232.lns1.adl1.internode.on.net [150.101.34.232])i2T9VMUK074527 for ; Mon, 29 Mar 2004 19:01:22 +0930 (CST) X-Envelope-From: ws+freebsd-questions@au.dyndns.ws X-Envelope-To: Received: from [192.168.100.132] (ppp34-232.lns1.adl1.internode.on.net [150.101.34.232])i2T9VL6i055311 for ; Mon, 29 Mar 2004 19:01:21 +0930 (CST) (envelope-from ws+freebsd-questions@au.dyndns.ws) From: Wayne Sierke To: freebsd-questions@freebsd.org Content-Type: text/plain Message-Id: <1080552680.682.41.camel@ovirt.dyndns.ws> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Mon, 29 Mar 2004 19:01:21 +0930 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.39 X-Scanned-By: SpamAssassin 2.63 (2004-01-11) X-Scanned-By: F-Prot X-Scanned-By: ClamAV X-Spam-Score: 0 () Subject: $PIR: ROUTE_INTERRUPT failed. X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Mar 2004 09:31:24 -0000 Do I need to be concerned about these boot entries in /var/log/messages (running -CURRENT i386): kernel: pci1: on pcib1 -> kernel: $PIR: ROUTE_INTERRUPT failed. kernel: pci1: at device 0.0 (no driver attached) and I presume to be related: kernel: vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 -> kernel: unknown: can't assign resources (port) -> kernel: unknown: can't assign resources (port) -> kernel: unknown: can't assign resources (port) -> kernel: unknown: can't assign resources (port) -> kernel: unknown: can't assign resources (port) -> kernel: unknown: can't assign resources (port) The system is prone to random lock-up (not observed previously when running 5.2-RELEASE). The lockup can be induced by running xmms - quite quickly when playing from a streaming source and playing through the sound card[1]. However the lockup will also occur at random although it has always been observed to happen as a result of user activity (I don't recall having returned to find the system rebooted[2]). Aside from running xmms, this lockup will usually not occur until after some (variable) hours of use. Another symptom I get is that because of the unclean unmounts of / and /usr, the delayed fsck kicks in at about the same time that my desktop session is reloading. This currently[3] results in evolution-alarm-notify crashing. I can get no crashdump info from bug-buddy, however. If the background fsck isn't running (e.g. if I wait for it to complete before logging in to the desktop), I don't get the crash. I don't get any log entries or core dumps to work with and am currently at a loss as to the likely cause or resolution. Any and all tips, clues, hints, pointers, instructions, directives and derisive comments appreciated. Wayne [1] Recently the system booted without (the BIOS) finding the soundcard (this happens very occasionally, nothing to do with FBSD). Curious, I ran xmms from the streaming source and set the output to write to a file. I left this running for around two hours and it had written around 1.5G before I stopped it. I can't run xmms and play through the soundcard (Xitel Storm Platinum/Aureal Vortex 2) for anywhere near that long without experiencing a lock up. [2] The system always reboots itself, about 20 seconds after the lockup occurs. [3] These symptoms (programs crashing while the destop is reloading and the background fsck is running) have been varied, changing as I've recompiled various ports.