From owner-freebsd-smp Sun Apr 2 5:50:46 2000 Delivered-To: freebsd-smp@freebsd.org Received: from ipamzlx.physik.uni-mainz.de (ipamzlx.Physik.Uni-Mainz.DE [134.93.180.54]) by hub.freebsd.org (Postfix) with ESMTP id 1BF0B37BE54; Sun, 2 Apr 2000 05:50:39 -0700 (PDT) (envelope-from ohartman@ipamzlx.physik.uni-mainz.de) Received: from ipamzlx.Physik.Uni-Mainz.DE (ipamzlx.Physik.Uni-Mainz.DE [134.93.180.54]) by ipamzlx.physik.uni-mainz.de (8.9.3/8.9.3) with ESMTP id OAA16463; Sun, 2 Apr 2000 14:50:38 +0200 (CEST) (envelope-from ohartman@ipamzlx.physik.uni-mainz.de) Date: Sun, 2 Apr 2000 14:50:38 +0200 (CEST) From: "O. Hartmann" To: freebsd-smp@freebsd.org Cc: freebsd-stable@freebsd.org Subject: RCC/Reliant Chipset supported by FBSD 4.0??? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dear Sirs. I read about SMP problems with i840 based motherboards and it is well known that this chipset has some serius bugs. So we want to obtain two or three server mainboards from TYAN (TYAN Thunder 2500) as it is available on market. This mainboard has execellent specifications and it it based on the RCC ServerWorks III HE chipset which is supposed to be on of the best high end chipsets. Purchasing is planned at the end of May or middle of June. Has anyone experiences with this chipset and can tell me whether FBSD 4.0 supports this chipset? The TYAN Thunder 2500 comes with two independent SCSI-3 160m LVD channels, I think based on SymBios Logic chipsets. Is this type of chipset already supported in FBSD 4.0? Well, your answer is highly appreciated since I have to make decisions based on that. So, have many thanks in advance and kind regards, O. Hartmann ------------------------------------------------------------------- ohartman@ipamzlx.physik.uni-mainz.de Klimadatenserver des IPA, Universitaet Mainz Netzwerk- und Systembetreuung To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Mon Apr 3 1: 9:33 2000 Delivered-To: freebsd-smp@freebsd.org Received: from smtp-gw.csp.it (cspnsv.csp.it [130.192.68.9]) by hub.freebsd.org (Postfix) with ESMTP id 2F88737BB6F for ; Mon, 3 Apr 2000 01:09:27 -0700 (PDT) (envelope-from Lorenzo.Cavassa@CSP.it) Received: from smtp.intranet.csp.it (rigel.intranet.csp.it [192.168.68.1]) by smtp-gw.csp.it (Postfix) with ESMTP id A86D187C18 for ; Mon, 3 Apr 2000 08:09:22 +0000 (GMT) Received: from CSP.it (cavassa.csp.it [130.192.67.9]) by smtp.intranet.csp.it (Postfix) with ESMTP id 53D622E40 for ; Mon, 3 Apr 2000 08:09:22 +0000 (GMT) Message-ID: <38E851B2.F3E82869@CSP.it> Date: Mon, 03 Apr 2000 10:09:22 +0200 From: Lorenzo Cavassa Reply-To: Lorenzo.Cavassa@CSP.it Organization: CSP - Centro di Eccellenza per la Ricerca, Sviluppo e Sperimentazione di Tecnologie avanzate Informatiche e Telematiche - Torino - http://www.csp.it X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-smp@freebsd.org Subject: Hoard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org You know? http://www.hoard.org/ Hoard is a fast, scalable and memory-efficient allocator for multiprocessors. Hoard solves the heap contention problem caused when multiple threads call dynamic memory allocation functions like malloc() and free() (or new and delete). Hoard can dramatically improve the performance of multithreaded programs running on multiprocessors. kawa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Mon Apr 3 2:51:51 2000 Delivered-To: freebsd-smp@freebsd.org Received: from relativity.student.utwente.nl (wit389306.student.utwente.nl [130.89.234.166]) by hub.freebsd.org (Postfix) with ESMTP id 57E3237BDC9 for ; Mon, 3 Apr 2000 02:51:42 -0700 (PDT) (envelope-from djb@wit389306.student.utwente.nl) Received: by relativity.student.utwente.nl (Postfix, from userid 1000) id B20F35DBF; Mon, 3 Apr 2000 11:51:24 +0200 (CEST) Date: Mon, 3 Apr 2000 11:51:24 +0200 From: Dave Boers To: Matthew Dillon Cc: Tommy Hallgren , Jeremiah Gowdy , bart@ixori.demon.nl, freebsd-smp@FreeBSD.ORG Subject: Re: SMP and vn Message-ID: <20000403115124.A374@relativity.student.utwente.nl> Reply-To: djb@relativity.student.utwente.nl References: <20000327183911.18682.qmail@web124.yahoomail.com> <20000329132919.A10781@relativity.student.utwente.nl> <200003291604.IAA63016@apollo.backplane.com> <20000329203525.A379@relativity.student.utwente.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000329203525.A379@relativity.student.utwente.nl>; from djb@relativity.student.utwente.nl on Wed, Mar 29, 2000 at 08:35:25PM +0200 Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It is rumoured that Dave Boers had the courage to say: > I reconfigured my kernel. It's now booting on the serial terminal as a > console. Also I removed DDB_UNATTENDED from my kernel config and added > DIAGNOSTIC to it. > > _IF_ there's an unnoticed kernel panic going along with the system hang > then I will be dropped in DDB on the serial terminal if all is well. This > way, I won't miss out on any kernel messages while using X. > Talk to you all in 5-7 days or so :-) Well, it's been a little less than 5-7 days. The system just crashed on me. This time, I am _absolutely sure_ that the system is _not_ doing a panic. I configured a serial terminal as console and I repeatedly tested DDB on it. It works fine. However during the latest crash, there was no debugger or panic message on the serial console. The lockup was again complete; the keyboard NUMLOCK key didn't even respond anymore. The lockup occurred while XFree86 was running, along with some editor sessions (vim), some ssh sessions, Licq and (important, I guess) I was burning a cd-recordable using cdrecord. So the system was using the posix realtime scheduling a lot. The crash left my scsi devices in such a state that I had to do a full system power down before I got my cdrom devices back online. Furthermore, this shows that the problem was not the specific kernel configuration or the ATA driver (I was running a kernel configuration sent to me by Lyndon Nerenberg who does not have the lockups on the same hardware; I removed the ATA driver completely from the kernelconfig). This leaves XFree86, cdrecord or licq to trigger the problem. I do have some harddisk space to spare; would it be a good idea to add some logging to some parts of the kernel to a logfile somewhere? Maybe that way we can trace what happened just before the lockups? I don't have any kernel programming experience, so I don't know were to look. Can someone here help out? I don't have a problem with a logfile of, say, 7 Gb or so. Regards, Dave. -- djb@ifa.au.dk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Mon Apr 3 3: 6:36 2000 Delivered-To: freebsd-smp@freebsd.org Received: from manchaca.ece.utexas.edu (manchaca.ece.utexas.edu [128.83.59.38]) by hub.freebsd.org (Postfix) with ESMTP id C6F2F37BA82 for ; Mon, 3 Apr 2000 03:06:33 -0700 (PDT) (envelope-from mwu@tick.ece.utexas.edu) Received: from tick.ece.utexas.edu (tick.ece.utexas.edu [128.83.59.31]) by manchaca.ece.utexas.edu (8.9.3/8.9.3) with SMTP id FAA02442 for ; Mon, 3 Apr 2000 05:06:32 -0500 (CDT) Date: Mon, 3 Apr 2000 05:06:32 -0500 (CDT) From: Michael Chin-yuan Wu To: freebsd-smp@freebsd.org Subject: Re: You know? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I wil go ask him in person about it. :) _________________________________________________________________ keichii@bsdconspiracy.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Mon Apr 3 8:20:24 2000 Delivered-To: freebsd-smp@freebsd.org Received: from ixori.demon.nl (ixori.demon.nl [195.11.248.5]) by hub.freebsd.org (Postfix) with ESMTP id 4BFFF37BFAB for ; Mon, 3 Apr 2000 08:20:14 -0700 (PDT) (envelope-from bart@ixori.demon.nl) Received: from smtp-relay by ixori.demon.nl (8.9.3/8.9.2) with ESMTP id RAA07873 for ; Mon, 3 Apr 2000 17:20:17 +0200 (CEST) (envelope-from bart@ixori.demon.nl) Received: from network (intranet) by smtp-relay (Bart's intranet smtp server) Message-ID: <38E8B77C.1075A351@ixori.demon.nl> Date: Mon, 03 Apr 2000 17:23:40 +0200 From: Bart van Leeuwen Reply-To: bart@ixori.demon.nl Organization: IxorI X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-smp@freebsd.org Subject: Re: SMP and vn References: <20000327183911.18682.qmail@web124.yahoomail.com> <20000329132919.A10781@relativity.student.utwente.nl> <200003291604.IAA63016@apollo.backplane.com> <20000329203525.A379@relativity.student.utwente.nl> <20000403115124.A374@relativity.student.utwente.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dave Boers wrote: > > It is rumoured that Dave Boers had the courage to say: > > I reconfigured my kernel. It's now booting on the serial terminal as a > > console. Also I removed DDB_UNATTENDED from my kernel config and added > > DIAGNOSTIC to it. > > > > _IF_ there's an unnoticed kernel panic going along with the system hang > > then I will be dropped in DDB on the serial terminal if all is well. This > > way, I won't miss out on any kernel messages while using X. > > > Talk to you all in 5-7 days or so :-) > > Well, it's been a little less than 5-7 days. The system just crashed on me. > > This time, I am _absolutely sure_ that the system is _not_ doing a panic. I > configured a serial terminal as console and I repeatedly tested DDB on it. > It works fine. However during the latest crash, there was no debugger or > panic message on the serial console. The lockup was again complete; the > keyboard NUMLOCK key didn't even respond anymore. Sounds like what happens here. Even trying to break into the debugger from the console doesn't work anymore.. > > The lockup occurred while XFree86 was running, along with some editor > sessions (vim), some ssh sessions, Licq and (important, I guess) I was > burning a cd-recordable using cdrecord. So the system was using the posix > realtime scheduling a lot. The crash left my scsi devices in such a state > that I had to do a full system power down before I got my cdrom devices > back online. That might very well be your cd burner... At least, on both cd burners I have here I should never interupt the burning process at the risk of having to power cylcle the burner to get the scsi subnsystem working again. Funny thing is that cdrecord in some cases will notice and advise you to do so when the burner hangs. (fyi, I have a Phillips 3600 SCSI burner, which is something that NEEDS its own power switch, it crashes very often in my experience, and a Plextor scsi burner which doesn't have much problems except when interupting a (dummy) write. I only use the plextor writer in my smp system. The posix realtime stuff is an interesting one, lets keep that one in mind ;-) > > Furthermore, this shows that the problem was not the specific kernel > configuration or the ATA driver (I was running a kernel configuration sent > to me by Lyndon Nerenberg who does not have the lockups on the same > hardware; I removed the ATA driver completely from the kernelconfig). This > leaves XFree86, cdrecord or licq to trigger the problem. > Good to hear (?) that this isn't likely to be ATA related... I can't run without that one ;-) So that leaves me with what I should do anyway.. get an XFree86 3.3.5 on my system ;-) > I do have some harddisk space to spare; would it be a good idea to add some > logging to some parts of the kernel to a logfile somewhere? Maybe that way > we can trace what happened just before the lockups? I don't have any kernel > programming experience, so I don't know were to look. Can someone here help > out? I don't have a problem with a logfile of, say, 7 Gb or so. > Same here. I have like 10gb to spare for such a log. Usually I can reproduce the hangup in about a day or less. If anyone has any hints on how to setup such a thing it would be appreciated. I do have some experience with making small kernel hacks, but no real experience with kernel debugging, tracing and programming so far. ;-( -- Bart van Leeuwen ----------------------------------------------------------- mailto:bart@ixori.demon.nl - http://www.ixori.demon.nl/ ----------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Tue Apr 4 18:33:17 2000 Delivered-To: freebsd-smp@freebsd.org Received: from astro.psu.edu (lonestar.astro.psu.edu [128.118.147.184]) by hub.freebsd.org (Postfix) with ESMTP id 3A46537B9EE; Tue, 4 Apr 2000 18:33:13 -0700 (PDT) (envelope-from kopts@astro.psu.edu) Received: from volk.astro.psu.edu (volk.astro.psu.edu [128.118.147.21]) by astro.psu.edu (8.9.3/8.9.1) with ESMTP id VAA23202; Tue, 4 Apr 2000 21:33:07 -0400 (EDT) Date: Tue, 4 Apr 2000 21:32:46 -0400 (EDT) From: Alexey Koptsevich To: freebsd-questions@freebsd.org, freebsd-smp@freebsd.org Subject: priorities Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, I noticed strange thing: when several computational tasks run, real priority may not depend on nice value. In the example below (FreeBSD 3.4, dual PIII) task "sfp" runs faster than others if nice values are equal, and slower if its nice value is less. In both cases real priorities of all 3 tasks are equal. Both examples are taken at "equilibrium". Are any reasons for such scheduling? Please copy reply to me. Yours, Alex PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU CPU COMMAND 42069 uv 105 20 5412K 4868K CPU0 0 93:27 69.09% 69.09% h.out 40681 bns 105 20 10660K 10068K RUN 1 397:03 65.97% 65.97% a.out 42314 kopts 105 5 2964K 820K RUN 1 30:26 61.33% 61.33% sfp PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU CPU COMMAND 42314 kopts 105 20 2964K 820K RUN 0 32:14 69.92% 69.92% sfp 42069 uv 105 20 5584K 5040K RUN 1 95:12 64.21% 64.21% h.out 40681 bns 105 20 10676K 10084K CPU1 0 398:49 62.65% 62.65% a.out To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Wed Apr 5 4:49:58 2000 Delivered-To: freebsd-smp@freebsd.org Received: from axl.ops.uunet.co.za (axl.ops.uunet.co.za [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id AB9C737BC35; Wed, 5 Apr 2000 04:49:51 -0700 (PDT) (envelope-from sheldonh@axl.ops.uunet.co.za) Received: from sheldonh (helo=axl.ops.uunet.co.za) by axl.ops.uunet.co.za with local-esmtp (Exim 3.13 #1) id 12coJU-0000ra-00; Wed, 05 Apr 2000 13:49:36 +0200 From: Sheldon Hearn To: Alexey Koptsevich Cc: freebsd-questions@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG Subject: Re: priorities In-reply-to: Your message of "Tue, 04 Apr 2000 21:32:46 -0400." Date: Wed, 05 Apr 2000 13:49:36 +0200 Message-ID: <3321.954935376@axl.ops.uunet.co.za> Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 04 Apr 2000 21:32:46 -0400, Alexey Koptsevich wrote: > I noticed strange thing: when several computational tasks run, real > priority may not depend on nice value. Priority is a confusing name. A high priority indicates a CPU-bound process. What you're seeing is that all of these processes are CPU-bound hogs -- they don't often give up their time slice before it's over. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Fri Apr 7 15:31: 1 2000 Delivered-To: freebsd-smp@freebsd.org Received: from kithrup.com (kithrup.com [205.179.156.40]) by hub.freebsd.org (Postfix) with ESMTP id BE80437C19B for ; Fri, 7 Apr 2000 15:30:59 -0700 (PDT) (envelope-from sef@kithrup.com) Received: (from sef@localhost) by kithrup.com (8.8.8/8.8.8) id PAA28551 for freebsd-smp@freebsd.org; Fri, 7 Apr 2000 15:30:48 -0700 (PDT) (envelope-from sef) Date: Fri, 7 Apr 2000 15:30:48 -0700 (PDT) From: Sean Eric Fagan Message-Id: <200004072230.PAA28551@kithrup.com> To: freebsd-smp@freebsd.org Subject: Any problems with serial consoles? Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm having a hard time getting a serial console working correctly under 3.4-RELEASE on a dual-processor system. Has anyone else run into problems with it? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Sat Apr 8 1:13:25 2000 Delivered-To: freebsd-smp@freebsd.org Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (Postfix) with ESMTP id 80D9A37B52A for ; Sat, 8 Apr 2000 01:13:19 -0700 (PDT) (envelope-from vallo@matti.ee) Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (Postfix) with ESMTP id 0CC7B2CE6C; Sat, 8 Apr 2000 10:13:15 +0200 (EET) Received: by myhakas.matti.ee (Postfix, from userid 1000) id DF18A1C57D7; Sat, 8 Apr 2000 10:13:16 +0200 (EET) Date: Sat, 8 Apr 2000 10:13:16 +0200 From: Vallo Kallaste To: Sean Eric Fagan Cc: freebsd-smp@freebsd.org Subject: Re: Any problems with serial consoles? Message-ID: <20000408101316.A91405@myhakas.matti.ee> Reply-To: vallo@matti.ee References: <200004072230.PAA28551@kithrup.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200004072230.PAA28551@kithrup.com>; from sef@kithrup.com on Fri, Apr 07, 2000 at 03:30:48PM -0700 Organization: =?UTF-8?Q?AS_Matti_B=C3=BCrootehnika?= Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Apr 07, 2000 at 03:30:48PM -0700, Sean Eric Fagan wrote: > I'm having a hard time getting a serial console working correctly under > 3.4-RELEASE on a dual-processor system. Has anyone else run into problems > with it? Works for me but I'm using 5.0-current. -- Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Sat Apr 8 4:13:37 2000 Delivered-To: freebsd-smp@freebsd.org Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (Postfix) with ESMTP id 17AC437B57F for ; Sat, 8 Apr 2000 04:13:34 -0700 (PDT) (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.10.0/8.10.0/Kp) with ESMTP id e38BEdI28050; Sat, 8 Apr 2000 12:14:39 +0100 (BST) Message-ID: <38EF1445.4C4328AC@tdx.co.uk> Date: Sat, 08 Apr 2000 12:13:09 +0100 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.7 [en-gb] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Sean Eric Fagan Cc: freebsd-smp@FreeBSD.ORG Subject: Re: Any problems with serial consoles? References: <200004072230.PAA28551@kithrup.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Sean Eric Fagan wrote: > > I'm having a hard time getting a serial console working correctly under > 3.4-RELEASE on a dual-processor system. Has anyone else run into problems > with it? Can you define "hard time"? - I also have a problem, which I suspected was cable, but now I'm not so sure... I got confused about "/usr/src/sys/boot/i386", vs. "/usr/src/sys/i386/boot" - for where to adjust the boot system's definition of buad rate, and port number... Once I figured that out (look in '/usr/src/sys/boot/i386'), I can get it to work - of sorts... I get the initial "boot" prompt OK, I get dmesg, what I can't do is interact with it... If I tip to/from the port, I can send and receive fine... Serial console mode only seems to be able to send to the serial console, the console doesn't appear to be able to send back to the FreeBSD machine... Is this similar to what your seeing? Regards, -Karl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Sat Apr 8 4:15:53 2000 Delivered-To: freebsd-smp@freebsd.org Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (Postfix) with ESMTP id 4526F37B7F4 for ; Sat, 8 Apr 2000 04:15:42 -0700 (PDT) (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.10.0/8.10.0/Kp) with ESMTP id e38BGvT28065 for ; Sat, 8 Apr 2000 12:16:57 +0100 (BST) Message-ID: <38EF14CF.F4A5E99A@tdx.co.uk> Date: Sat, 08 Apr 2000 12:15:27 +0100 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.7 [en-gb] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: smp@freebsd.org Subject: mptable problems / workarounds with ahcX? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Peter Wemm wrote: > > > This really looks like the system is not seeing interrupts from this > > > card. I don't know why (perhaps an mptable problem), but the > > > errors are consistent with that. > > This is a known problem. The workaround for the mptable and/or hardware > configuration problem was implemented in the wrong place and hasn't been > repaired and made to work for all drivers yet. > > Cheers, > -Peter Anyone know when it's going to be fixed? - Or which file changes I should look out for? - This coupled with my serial console not working means 'just testing' a recent -STABLE on the offchance it works is an extreemly long winded affair [especially if it ends up locking the same as before :(] Thanks, -Karl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Sat Apr 8 4:55:12 2000 Delivered-To: freebsd-smp@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id 86FAB37B52A for ; Sat, 8 Apr 2000 04:55:10 -0700 (PDT) (envelope-from jedgar@fxp.org) Received: from earth.fxp (unknown [207.192.76.255]) by pawn.primelocation.net (Postfix) with ESMTP id 3DDEC9B17; Sat, 8 Apr 2000 07:55:08 -0400 (EDT) Date: Sat, 8 Apr 2000 07:55:07 -0400 (EDT) From: "Chris D. Faulhaber" X-Sender: jedgar@earth.fxp To: Sean Eric Fagan Cc: freebsd-smp@freebsd.org Subject: Re: Any problems with serial consoles? In-Reply-To: <200004072230.PAA28551@kithrup.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 7 Apr 2000, Sean Eric Fagan wrote: > I'm having a hard time getting a serial console working correctly under > 3.4-RELEASE on a dual-processor system. Has anyone else run into problems > with it? > My little Dual P-166 here (Tyan Tomcat III) has survived with a working serial console from 3.0-CURRENT ->3.4-STABLE -> 4.0-CURRENT -> 4.0-STABLE. Can you give a description of your 'problems'? ----- Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org -------------------------------------------------------- FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Sat Apr 8 18:47:49 2000 Delivered-To: freebsd-smp@freebsd.org Received: from aurora.sol.net (aurora.sol.net [206.55.65.76]) by hub.freebsd.org (Postfix) with ESMTP id ECA5B37B542 for ; Sat, 8 Apr 2000 18:47:45 -0700 (PDT) (envelope-from jgreco@aurora.sol.net) Received: (from jgreco@localhost) by aurora.sol.net (8.9.2/8.9.2/SNNS-1.02) id HAA20496 for smp@freebsd.org; Tue, 11 Apr 2000 07:52:41 -0500 (CDT) From: Joe Greco Message-Id: <200004111252.HAA20496@aurora.sol.net> Subject: Re: Any problems with serial consoles? To: smp@freebsd.org Date: Tue, 11 Apr 2000 07:52:41 -0500 (CDT) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've a continuing (multi-year) issue with serial consoles on SMP machines. The general issue is that, during bootup, the console "loses it" and seems to switch baud rates or something, and all user I/O becomes garbage. However, kernel messages continue to print out correctly(!). The hardware I typically use is ASUS P2B-DS, large RAM (512MB+), Adaptec 3940's, and SMC Dual EtherPower 10/100(s). The OS revs are basically everything from 3.0 on up, IIRC. The system continues to boot just fine, and eventually the getty on ttyd0 will clear up the situation by resetting the terminal modes. I infrequently see the situation reassert itself after boot, usually after very long uptimes. The real problem is single-user mode. The sequence # ccdconfig -Cv; mount -a; sh /etc/netstart is at least 50% likely to leave the system in the state described, which of course means that it cannot hear further commands such as "reboot god damn it I don't want to drive to Chicago to reset you". So I usually end up doing something like # (sleep 900; reboot)& # ccdconfig -Cv; mount -a; sh /etc/netstart; stty sane; reset which generally seems not to fail in the described manner. I used to be fairly sure it was something in the networking that was causing the problem, but recently I ran into the situation when I was merely puttering with the disks after doing a "vinum start; mount -a" type affair. Solutions solicited. I may be able to provide a box with the described syndrome if anyone wants to look at it. ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message