From owner-freebsd-smp Tue Apr 21 12:36:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA00302 for freebsd-smp-outgoing; Tue, 21 Apr 1998 12:36:09 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA00260 for ; Tue, 21 Apr 1998 19:36:01 GMT (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.8.8/8.8.8) with ESMTP id UAA16137 for ; Tue, 21 Apr 1998 20:35:57 +0100 (BST) (envelope-from kpielorz@tdx.co.uk) Message-ID: <353CF50D.C523CD2C@tdx.co.uk> Date: Tue, 21 Apr 1998 20:35:41 +0100 From: Karl Pielorz Organization: TDX X-Mailer: Mozilla 4.04 [en] (WinNT; I) MIME-Version: 1.0 To: smp@FreeBSD.ORG Subject: Cause for concern - messages in dmesg... Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The system is running great, but I've just noticed a few errors in dmesg - which seem a little concerning... Is the following any cause for concern? (from dmesg) this... APIC_IO: Testing 8254 interrupt delivery APIC_IO: Broken MP table detected: 8254 is not connected to IO APIC int pin 2 APIC_IO: routing 8254 via 8259 on pin 0 and this... wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (wd2): wd2: 4110MB (8418816 sectors), 14848 cyls, 9 heads, 63 S/T, 512 B/S Freeing (NOT implemented) redirected ISA irq 15. and... wd2: interrupt timeout: wd2: status 58 error 0 wd2: wdtimeout() DMA status 4 I can post the output from mptable if it will help, but it's a bit long for an initial 'whats this' type message ;-) Regards, Karl Pielorz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message