From owner-freebsd-hackers Sun Mar 7 10:24: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from luke.pmr.com (luke.pmr.com [207.170.114.132]) by hub.freebsd.org (Postfix) with ESMTP id D819B14D6D for ; Sun, 7 Mar 1999 10:23:43 -0800 (PST) (envelope-from bob@luke.pmr.com) Received: (from bob@localhost) by luke.pmr.com (8.9.2/8.9.2) id MAA01086 for freebsd-hackers@freebsd.org; Sun, 7 Mar 1999 12:23:25 -0600 (CST) (envelope-from bob) Date: Sun, 7 Mar 1999 12:23:25 -0600 From: Bob Willcox To: hackers list Subject: Need help isolating prob w/rtc0 intr's stopping Message-ID: <19990307122325.A969@luke.pmr.com> Reply-To: Bob Willcox Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm hoping that someone out there can give me some suggestions on what I can do to track down a problem I'm having on my dual Xeon system that's running 3.1-stable. When I first boot the machine rtc0 interrupts just fine, however, as soon as I put a load on it (like starting X) my rtc0 interrupts stop. This causes all of the system monitors (like top, vmstat, iostat, etc.) to display 0% cpu usage and idle times. My system is consists of the following: ASUS XG-DLS motherboard 2 Xeon 400MHz/512KB cache processors 512MB of ECC SDRAM Note that if I boot a UP kernel the problem does not occur. I have exchanged email with Tor Egge who suggested that I change the interrupt vector for IRQ8 (from 0x68 to 0x48) but that didn't solve the problem. I have already opened a PR on this: kern/10411. Thanks for any help you can offer, Bob -- Bob Willcox The man who follows the crowd will usually get no bob@luke.pmr.com further than the crowd. The man who walks alone is Austin, TX likely to find himself in places no one has ever been. -- Alan Ashley-Pitt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message