From owner-freebsd-smp Sun Feb 9 09:57:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA26056 for smp-outgoing; Sun, 9 Feb 1997 09:57:04 -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 JAA26004 for ; Sun, 9 Feb 1997 09:56:29 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by clem.systemsix.com (8.6.12/8.6.12) with SMTP id KAA26116 for ; Sun, 9 Feb 1997 10:55:17 -0700 Message-Id: <199702091755.KAA26116@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: freebsd-smp@freebsd.org Subject: -current will be flaky Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 09 Feb 1997 10:55:16 -0700 Sender: owner-smp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I thought all the people in the SMP world should know about this: ---------------------------------------------------------------------------- From: "John S. Dyson" Date: Sun, 9 Feb 1997 10:16:06 -0500 (EST) Subject: Warning to -current *PLEASE READ* I am getting alot of pressure to commit the Lite/2 kernel changes. That pressure is justifiable, and so, in order to expedite our progress, I will be committing the changes starting at 21:00 EST, or 02:00 GMT. The kernel will likely be unstable (esp EXT2FS, MSDOSFS) until we have done enough testing. Get your snapshot NOW if you want a stable kernel. It will likely be at least 2wks before -current is stable enough for general use again. Sorry for the late warning. John Dyson dyson@freebsd.org ---------------------------------------------------------------------------- -- Steve Passe | powered by smp@csn.net | FreeBSD From owner-freebsd-smp Sun Feb 9 10:16:59 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA26952 for smp-outgoing; Sun, 9 Feb 1997 10:16:59 -0800 (PST) Received: from spinner.DIALix.COM (spinner.DIALix.COM [192.203.228.67]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA26934 for ; Sun, 9 Feb 1997 10:16:50 -0800 (PST) Received: from spinner.DIALix.COM (localhost.DIALix.oz.au [127.0.0.1]) by spinner.DIALix.COM (8.8.4/8.8.4) with ESMTP id CAA08974; Mon, 10 Feb 1997 02:16:28 +0800 (WST) Message-Id: <199702091816.CAA08974@spinner.DIALix.COM> X-Mailer: exmh version 2.0gamma 1/27/96 To: Steve Passe cc: freebsd-smp@freebsd.org Subject: Re: -current will be flaky In-reply-to: Your message of "Sun, 09 Feb 1997 10:55:16 MST." <199702091755.KAA26116@clem.systemsix.com> Date: Mon, 10 Feb 1997 02:16:27 +0800 From: Peter Wemm Sender: owner-smp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Steve Passe wrote: > Hi, > > I thought all the people in the SMP world should know about this: > [..] > The kernel will likely be unstable (esp EXT2FS, MSDOSFS) until we have > done enough testing. Get your snapshot NOW if you want a stable kernel. > > It will likely be at least 2wks before -current is stable enough for general > use again. I will import a snapshot of -current into the smp kernel right now before things get turned upside down. I am nearly asleep, so I might not get to finish resolving conflicts, but they can wait. If I expire before getting the smp tree building again, please give me a few hours for some sleep before warming up the flame throwers.. :-] Cheers, -Peter From owner-freebsd-smp Sun Feb 9 11:17:36 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA01371 for smp-outgoing; Sun, 9 Feb 1997 11:17:36 -0800 (PST) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA01357 for ; Sun, 9 Feb 1997 11:17:28 -0800 (PST) Received: (from root@localhost) by dyson.iquest.net (8.8.4/8.6.9) id OAA00499; Sun, 9 Feb 1997 14:16:57 -0500 (EST) From: "John S. Dyson" Message-Id: <199702091916.OAA00499@dyson.iquest.net> Subject: Re: -current will be flaky To: peter@spinner.dialix.com (Peter Wemm) Date: Sun, 9 Feb 1997 14:16:57 -0500 (EST) Cc: smp@csn.net, freebsd-smp@freebsd.org In-Reply-To: <199702091816.CAA08974@spinner.DIALix.COM> from "Peter Wemm" at Feb 10, 97 02:16:27 am X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-smp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Steve Passe wrote: > > Hi, > > > > I thought all the people in the SMP world should know about this: > > > [..] > > The kernel will likely be unstable (esp EXT2FS, MSDOSFS) until we have > > done enough testing. Get your snapshot NOW if you want a stable kernel. > > > > It will likely be at least 2wks before -current is stable enough for general > > use again. > > I will import a snapshot of -current into the smp kernel right now before > things get turned upside down. > Good!!! That was one of my worries. John dyson@freebsd.org From owner-freebsd-smp Mon Feb 10 07:55:54 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id HAA08572 for smp-outgoing; Mon, 10 Feb 1997 07:55:54 -0800 (PST) Received: from gds.de (ns.gds.de [194.77.222.14]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA08567 for ; Mon, 10 Feb 1997 07:55:49 -0800 (PST) Received: from pluto.gds.de (donald.plusnet.de [194.231.79.11]) by gds.de (8.8.4/8.6.12) with SMTP id QAA05759 for ; Mon, 10 Feb 1997 16:55:31 +0100 (MET) Message-Id: <199702101555.QAA05759@gds.de> Comments: Authenticated sender is From: "Richard Gresek" To: freebsd-smp@freebsd.org Date: Fri, 10 Jan 1997 16:53:11 +0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: kvm_read: bad address Reply-to: rg@gds.de Priority: normal X-mailer: Pegasus Mail for Win32 (v2.42a) Sender: owner-smp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hallo, 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? The kernel config file is included at the end of this mail. Richard # # GENERIC -- Generic machine with WD/AHx/NCR/BTx family disks # # For more information read the handbook part System Administration -> # Configuring the FreeBSD Kernel -> The Configuration File. # The handbook is available in /usr/share/doc/handbook or online as # latest version from the FreeBSD World Wide Web server # # # An exhaustive list of options and more detailed explanations of the # device lines is present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # # $Id: GENERIC,v 1.82 1996/12/21 02:09:04 se Exp $ machine "i386" #cpu "I386_CPU" #cpu "I486_CPU" cpu "I586_CPU" #cpu "I686_CPU" ident GENERIC maxusers 30 options CHILD_MAX=512 options OPEN_MAX=256 options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options FFS #Berkeley Fast Filesystem options NFS #Network Filesystem options MSDOSFS #MSDOS Filesystem options "CD9660" #ISO 9660 Filesystem options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=15 #Be pessimistic about Joe SCSI device options BOUNCE_BUFFERS #include support for DMA bounce buffers options UCONSOLE #Allow users to grab the console options FAILSAFE #Be conservative options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options SMP options NCPU=2 options NBUS=2 options NAPIC=1 options NINTR=24 options APIC_IO options SMP_INVLTLB options SYSVSHM options SYSVSEM options SYSVMSG config kernel root on wd0 controller isa0 controller eisa0 controller pci0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 disk fd1 at fdc0 drive 1 tape ft0 at fdc0 drive 2 controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 controller wdc1 at isa? port "IO_WD2" bio irq 15 vector wdintr disk wd2 at wdc1 drive 0 disk wd3 at wdc1 drive 1 options ATAPI #Enable ATAPI support for IDE bus options ATAPI_STATIC #Don't do it as an LKM device wcd0 #IDE CD-ROM # A single entry for any of these controllers (ncr, ahb, ahc, amd) is # sufficient for any number of installed devices. controller ncr0 controller amd0 controller ahb0 controller ahc0 controller bt0 at isa? port "IO_BT0" bio irq ? vector bt_isa_intr controller uha0 at isa? port "IO_UHA0" bio irq ? drq 5 vector uhaintr controller aha0 at isa? port "IO_AHA0" bio irq ? drq 5 vector ahaintr controller aic0 at isa? port 0x340 bio irq 11 vector aicintr controller nca0 at isa? port 0x1f88 bio irq 10 vector ncaintr controller nca1 at isa? port 0x350 bio irq 5 vector ncaintr controller sea0 at isa? bio irq 5 iomem 0xc8000 iosiz 0x2000 vector seaintr controller scbus0 device sd0 device od0 #See LINT for possible `od' options. device st0 device cd0 #Only need one of these, the code dynamically grows device wt0 at isa? port 0x300 bio irq 5 drq 1 vector wtintr device mcd0 at isa? port 0x300 bio irq 10 vector mcdintr controller matcd0 at isa? port 0x230 bio device scd0 at isa? port 0x230 bio # syscons is the default console driver, resembling an SCO console device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? port "IO_KBD" tty irq 1 vector pcrint #options PCVT_FREEBSD=210 # pcvt running on FreeBSD >= 2.0.5 #options XSERVER # include code for XFree86 #options FAT_CURSOR # start with block cursor # If you have a ThinkPAD, uncomment this along with the rest of the PCVT lines #options PCVT_SCANSET=2 # IBM keyboards are non-std # Mandatory, don't remove device npx0 at isa? port "IO_NPX" irq 13 vector npxintr # # Laptop support (see LINT for more options) # device apm0 at isa? disable # Advanced Power Management options APM_BROKEN_STATCLOCK # Workaround some buggy APM BIOS # PCCARD (PCMCIA) support #controller crd0 #device pcic0 at crd? #device pcic1 at crd? device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr #device sio2 at isa? disable port "IO_COM3" tty irq 5 vector siointr #device sio3 at isa? disable port "IO_COM4" tty irq 9 vector siointr device lpt0 at isa? port? tty irq 7 vector lptintr device lpt1 at isa? port? tty device mse0 at isa? port 0x23c tty irq 5 vector mseintr device psm0 at isa? disable port "IO_KBD" conflicts tty irq 12 vector psmintr # Order is important here due to intrusive probes, do *not* alphabetize # this list of network interfaces until the probes have been fixed. # Right now it appears that the ie0 must be probed before ep0. See # revision 1.20 of this file. device de0 device fxp0 device vx0 #device ed0 at isa? port 0x280 net irq 5 iomem 0xd8000 vector edintr #device ed1 at isa? port 0x300 net irq 5 iomem 0xd8000 vector edintr #device ie0 at isa? port 0x360 net irq 7 iomem 0xd0000 vector ieintr #device ep0 at isa? port 0x320 net irq 5 vector epintr #device fe0 at isa? port 0x300 net irq ? vector feintr #device ix0 at isa? port 0x300 net irq 10 iomem 0xd0000 iosiz 32768 vector ixintr #device le0 at isa? port 0x300 net irq 5 iomem 0xd0000 vector le_intr #device lnc0 at isa? port 0x280 net irq 10 drq 0 vector lncintr #device ze0 at isa? port 0x300 net irq 5 iomem 0xd8000 vector zeintr #device zp0 at isa? port 0x300 net irq 10 iomem 0xd8000 vector zpintr pseudo-device loop pseudo-device ether pseudo-device log pseudo-device sl 1 # ijppp uses tun instead of ppp device #pseudo-device ppp 1 pseudo-device tun 1 pseudo-device pty 16 pseudo-device gzip # Exec gzipped a.out's # KTRACE enables the system-call tracing facility ktrace(2). # This adds 4 KB bloat to your kernel, and slightly increases # the costs of each syscall. #options KTRACE #kernel tracing +-------------------------------------------------------------------+ : Plus.Net Internet PoP fuer : Oppenheimer Landstr. 55 Frankfurt & Westerwald : 60596 Frankfurt : Tel.: +49 69 61991275 http://www.plusnet.de : Fax : +49 69 610238 +-------------------------------------------------------------------+ 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 From owner-freebsd-smp Tue Feb 11 15:03:19 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA27227 for smp-outgoing; Tue, 11 Feb 1997 15:03:19 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id PAA27205 for ; Tue, 11 Feb 1997 15:02:56 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA29240; Tue, 11 Feb 1997 15:56:54 -0700 From: Terry Lambert Message-Id: <199702112256.PAA29240@phaeton.artisoft.com> Subject: Re: kvm_read: bad address To: smp@csn.net (Steve Passe) Date: Tue, 11 Feb 1997 15:56:53 -0700 (MST) Cc: rg@gds.de, freebsd-smp@FreeBSD.ORG In-Reply-To: <199702112122.OAA11253@clem.systemsix.com> from "Steve Passe" at Feb 11, 97 02:22:51 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-smp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >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". If you boot with a kernel other than the default kernel, the symbol table reference for "/kernel" will be wrong for most utilities. If the utility uses the path value rather than the sysctl() value for the running kernel, it will have this problem. If you boot with a kernel other than the default kernel, and the kernel header files (like proc.h) declare critical system structures to be a different size or layout than expected, then when the utility goes to read form /dev/kmem using valid symbol offsets, the relative pointer values in the returned structure will contain invalid data. Most utilities, "ps", "w", and so on, detect proc structure size changes automatically. Not all do. If you use a utility that does not detect structure size changes, then you will get these errors. You need to recompile *all* kernel structure dependent programs which link to libkvm, or which read /dev/kmem or /dev/mem directly, each tim you change which kernel you are using. For instance, if the "swap" structure changes, or the network interface structure changes, you will have to recompile "swapon" and "vmstat", or "netstat" and "ifconfig", and so on, respectively. Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.