From owner-freebsd-smp Tue Feb 11 13:29:37 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA19873 for smp-outgoing; Tue, 11 Feb 1997 13:29:37 -0800 (PST) Received: from clem.systemsix.com (clem.systemsix.com [198.99.86.131]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id NAA19724 for ; Tue, 11 Feb 1997 13:27:39 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by clem.systemsix.com (8.6.12/8.6.12) with SMTP id OAA11253; Tue, 11 Feb 1997 14:22:51 -0700 Message-Id: <199702112122.OAA11253@clem.systemsix.com> X-Authentication-Warning: clem.systemsix.com: Host localhost didn't use HELO protocol X-Mailer: exmh version 1.6.5 12/11/95 From: Steve Passe To: rg@gds.de cc: freebsd-smp@freebsd.org Subject: Re: kvm_read: bad address In-reply-to: Your message of "Fri, 10 Jan 1997 16:53:11 GMT." <199702101555.QAA05759@gds.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 11 Feb 1997 14:22:51 -0700 Sender: owner-smp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, >I am running the SMP kernel on a 3.0-970124-SNAP system and a >Gigabyte GA586DX Dual motherboard with 2 x P5 / 200 MHz and 96 MB >RAM. The machine runs mostly OK for several days. Only under heavy >load it breaks down quite immadiatelly. It seems that there is a >problem with swap. Some apps cannot be started and show the message >kvm_read kvm_read: bad address". One of these apps is "dmesg". > >This occures very irregularly, mostly quite after booting. Some >minutes later (in case the machine is still running ;-)) also dmesg >works fine again. > >The same environment works very steadily with the GENERIC 970124-SNAP >kernel. --- >Can it be a bug in the SMP kernel or is it because of the differences >between the SNAP and the kernel version? Or do I have some >misconfiguration in my kernel? this is the board I use, with 64MB, no such problems. no one else reports this ERROR, *probably* not a bug. could be the differences between -current an SMP... kernel config looks ok... I don't see a MAXMEM in the config for > 64MB. might try removing memory so you have 64MB or less. might also try setting the BIOS for 70ns just for testing purposes. -- Steve Passe | powered by smp@csn.net | FreeBSD