From owner-freebsd-smp Mon May 28 16: 4:55 2001 Delivered-To: freebsd-smp@freebsd.org Received: from matt.MUNICH.v-net.org (u57n248.syd.eastlink.ca [24.222.57.248]) by hub.freebsd.org (Postfix) with ESMTP id 316B137B424 for ; Mon, 28 May 2001 16:04:48 -0700 (PDT) (envelope-from matt@cape-breton-island.com) Received: from unisys (Windozzze [192.168.8.2]) by matt.MUNICH.v-net.org (8.11.3/8.11.3) with ESMTP id f4SN4ed65755 for ; Mon, 28 May 2001 20:04:41 -0300 (ADT) From: "Matt Rudderham" To: Subject: Slightly OT: Monitoring Temps on SMP Machine Date: Mon, 28 May 2001 20:04:38 -0300 Message-ID: <000001c0e7ca$929014e0$0208a8c0@munich.vnet.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, Sorry if this is a bit off topic, but I've found this varies quite a bit between the normal kernel and the SMP. I'm running a Supermicro 370DL3 board (serverworks chipset) with dual PIII-800s. None of the normal utilities (healthd, lmmon) seem to sucessfully be able to monitor fan speeds or temps. I have the standard options in ther kernel (listed below) and have tried both using the -I for IO in lieu of smbus. Has anyone had any success at monitoring these? Thanks a lot. Device smbus0 device iicbus0 device iicbb0 device intpm0 device smb0 Matthew Rudderham To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Wed May 30 15:29:27 2001 Delivered-To: freebsd-smp@freebsd.org Received: from matt.MUNICH.v-net.org (u57n248.syd.eastlink.ca [24.222.57.248]) by hub.freebsd.org (Postfix) with ESMTP id D36A637B423 for ; Wed, 30 May 2001 15:29:12 -0700 (PDT) (envelope-from matt@cape-breton-island.com) Received: from unisys (Windozzze [192.168.8.2]) by matt.MUNICH.v-net.org (8.11.3/8.11.3) with ESMTP id f4UMTAd71535 for ; Wed, 30 May 2001 19:29:11 -0300 (ADT) From: "Matt Rudderham" To: Subject: SMP Kernel Panic Date: Wed, 30 May 2001 19:29:21 -0300 Message-ID: <000001c0e957$f97fc220$0208a8c0@munich.vnet.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, I just logged into one of my remotely aministered machines to find out it had rebooted itself. It's been up for only a few days, can anyone make anything of this? How should I go about looking into the prob? Thanks guys. May 30 18:08:18 cfxu /kernel:=20 May 30 18:08:18 cfxu /kernel: Fatal trap 12: page fault while in kernel mode May 30 18:08:18 cfxu /kernel: mp_lock =3D 00000002; cpuid =3D 0; = lapic.id =3D 00000000 May 30 18:08:18 cfxu /kernel: fault virtual address =3D 0xe8e6f315 May 30 18:08:18 cfxu /kernel: fault code =3D supervisor read, page not present May 30 18:08:18 cfxu /kernel: instruction pointer =3D = 0x8:0xc0162502 May 30 18:08:18 cfxu /kernel: stack pointer =3D 0x10:0xd56f0d24 May 30 18:08:18 cfxu /kernel: frame pointer =3D 0x10:0xd56f0d28 May 30 18:08:18 cfxu /kernel: code segment =3D base 0x0, limit 0xfffff, type 0x1b May 30 18:08:18 cfxu /kernel: =3D DPL 0, pres 1, def32 1, gran 1 May 30 18:08:18 cfxu /kernel: processor eflags =3D interrupt enabled, resume, IOPL =3D 0 May 30 18:08:18 cfxu /kernel: current process =3D 322 = (hlds_run) May 30 18:08:18 cfxu /kernel: interrupt mask =3D bio <- SMP: XXX May 30 18:08:18 cfxu /kernel: trap number =3D 12 May 30 18:08:18 cfxu /kernel: panic: page fault May 30 18:08:18 cfxu /kernel: mp_lock =3D 00000002; cpuid =3D 0; = lapic.id =3D 00000000 May 30 18:08:18 cfxu /kernel: boot() called on cpu#0 May 30 18:08:18 cfxu /kernel:=20 May 30 18:08:18 cfxu /kernel: syncing disks... 13 13 13 13 13 13 13 13 13 13 13 13 13 13 13 13 13 13 13 13=20 May 30 18:08:18 cfxu /kernel: giving up on 13 buffers May 30 18:08:18 cfxu /kernel: Uptime: 1d23h57m8s May 30 18:08:18 cfxu /kernel: Automatic reboot in 15 seconds - press a key on the console to abort May 30 18:08:18 cfxu /kernel: Rebooting... May 30 18:08:18 cfxu /kernel: cpu_reset called on cpu#0 May 30 18:08:18 cfxu /kernel: cpu_reset: Stopping other CPUs To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Wed May 30 18:36:57 2001 Delivered-To: freebsd-smp@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 7E9A237B424 for ; Wed, 30 May 2001 18:36:55 -0700 (PDT) (envelope-from grog@lemis.com) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id AC7016ACC3; Thu, 31 May 2001 11:06:50 +0930 (CST) Date: Thu, 31 May 2001 11:06:50 +0930 From: Greg Lehey To: Matt Rudderham Cc: freebsd-smp@freebsd.org Subject: Re: SMP Kernel Panic Message-ID: <20010531110650.K81040@wantadilla.lemis.com> References: <000001c0e957$f97fc220$0208a8c0@munich.vnet.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <000001c0e957$f97fc220$0208a8c0@munich.vnet.org>; from matt@cape-breton-island.com on Wed, May 30, 2001 at 07:29:21PM -0300 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wednesday, 30 May 2001 at 19:29:21 -0300, Matt Rudderham wrote: > Hi, > I just logged into one of my remotely aministered machines to find out > it had rebooted itself. It's been up for only a few days, can anyone > make anything of this? How should I go about looking into the prob? FreeBSD-smp is a developers' list. Post here if you have very specific information. Otherwise send a message to FreeBSD-questions. Don't wrap computer output, and do give at least a backtrace and basic information on your setup, like what version of FreeBSD you're running. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Sat Jun 2 11:22:53 2001 Delivered-To: freebsd-smp@freebsd.org Received: from munin.odin-corporation.com (munin.odin-corporation.com [216.233.173.18]) by hub.freebsd.org (Postfix) with ESMTP id D1BCC37B423 for ; Sat, 2 Jun 2001 11:22:35 -0700 (PDT) (envelope-from lars@odin-corporation.com) Received: from odin-corporation.com (localhost [127.0.0.1]) by munin.odin-corporation.com (8.11.3/8.11.1) with ESMTP id f52IMZP02427 for ; Sat, 2 Jun 2001 13:22:35 -0500 (CDT) (envelope-from lars@odin-corporation.com) Message-ID: <3B192EEA.68CE9AF1@odin-corporation.com> Date: Sat, 02 Jun 2001 13:22:34 -0500 From: Lars Fredriksen Organization: Odin Corporation X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: no, en MIME-Version: 1.0 To: smp@freebsd.org Subject: shared interrupt handling Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, I have noticed that my mptable (ASUS bios 1013) on my p2b-ds always indicate that the interrupt source bus is ISA, even for the PCI device. This happens also when one reserves a couple of irqs for ISA in the bios. When you do this, a couple of the PCI cards end up sharing interrupt, which typically doesn't seem to work. I suspect the problem is that the interrupt sharing that is set up span buses, that is that is the cards on the PCI bus end up sharing irqs with the ISA cards or with built in devices like com ports or ide controllers. One case in particular that we don't handle at all, is when the mptable specifies that we share irq 14 or 15. This doesn't work at all since the ata driver currently doesn't allow for interrupt sharing (RF_SHAREABLE is not set). Has anyone else seen this? Would implementing the PCI IRQ reroutes that LINUX does fix this problem? Also, is it the fact that this MB has both and ISA and PCI bus that causes the interrupt source bus be set to ISA no matter what? Because it is in any configuration I can seem to come up with, pci_apic_irq() always fails, and we resort to isa_apic_irq() which in turn always return the irq that the BIOS mptable came up with, which seems to always be < 16, thus a lot of irq sharing takes place, between hardwired ISA devices, PNP ISA devices and PCI devices. If you are so lucky that the pci device work, you can be sure that the ISA ones do not. Anyway, can anyone shed some light here - is it all because of bogus mptables or do we not handle the above cases correctly? Thanks, Lars To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Sat Jun 2 21:14:35 2001 Delivered-To: freebsd-smp@freebsd.org Received: from midten.fast.no (midten.fast.no [213.188.8.11]) by hub.freebsd.org (Postfix) with ESMTP id 0951C37B423 for ; Sat, 2 Jun 2001 21:14:33 -0700 (PDT) (envelope-from Tor.Egge@fast.no) Received: from fast.no (IDENT:tegge@midten.fast.no [213.188.8.11]) by midten.fast.no (8.9.3/8.9.3) with ESMTP id GAA30030; Sun, 3 Jun 2001 06:14:28 +0200 (CEST) Message-Id: <200106030414.GAA30030@midten.fast.no> To: lars@odin-corporation.com Cc: smp@FreeBSD.ORG Subject: Re: shared interrupt handling From: Tor.Egge@fast.no In-Reply-To: Your message of "Sat, 02 Jun 2001 13:22:34 -0500" References: <3B192EEA.68CE9AF1@odin-corporation.com> X-Mailer: Mew version 1.70 on Emacs 19.34.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sun, 03 Jun 2001 06:14:28 +0200 Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > Hi, > > I have noticed that my mptable (ASUS bios 1013) on my p2b-ds always > indicate that the interrupt source bus is ISA, even for the PCI device. > This happens also when one reserves a couple of irqs for ISA in the > bios. When you do this, a couple of the PCI cards end up sharing > interrupt, which typically doesn't seem to work. Enable the MPS 1.4 support in your BIOS. I do that on my development machine (Asus P2B-DS, bios 1012B). When the MPS 1.4 support is disabled, the BIOS presents an MPS 1.1 table that overloads all PCI interrupts onto the ISA bus. - Tor Egge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message