From owner-freebsd-smp@FreeBSD.ORG Sun Aug 1 16:11:14 2004 Return-Path: Delivered-To: freebsd-smp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B943416A4CE; Sun, 1 Aug 2004 16:11:14 +0000 (GMT) Received: from mail.revolutionsp.com (ganymede.revolutionsp.com [64.246.0.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 67A8843D2D; Sun, 1 Aug 2004 16:11:14 +0000 (GMT) (envelope-from klr@6s-gaming.com) Received: from mail.revolutionsp.com (localhost [127.0.0.1]) by mail.revolutionsp.com (Postfix) with ESMTP id AE4D215C95; Sun, 1 Aug 2004 13:08:56 +0000 (GMT) Received: from 81.84.175.12 (SquirrelMail authenticated user klr@6s-gaming.com); by mail.revolutionsp.com with HTTP; Sun, 1 Aug 2004 13:08:56 -0000 (GMT) Message-ID: <50335.81.84.175.12.1091365736.squirrel@81.84.175.12> Date: Sun, 1 Aug 2004 13:08:56 -0000 (GMT) From: "Hugo Silva" To: freebsd-smp@freebsd.org, freebsd-questions@FreeBSD.org User-Agent: SquirrelMail/1.4.3a X-Mailer: SquirrelMail/1.4.3a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Subject: FreeBSD 5.2.1 kernel w/ SMP under high load = panic X-BeenThere: freebsd-smp@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD SMP implementation group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Aug 2004 16:11:14 -0000 I am running a Dual Xeon 2.8ghz w/ SMP, SCHED_ULE on FreeBSD 5.2.1-RELEASE-p9. Whenever I load the server a bit more (let seti@home run, compile stuff in multiple jails, etc), it will simple go offline. I confirmed with the datacenter and it is indeed a panic, but the datacenter didn't give me the panic message. I know for *sure* it's because of the high loads. I need to sort this out, this is a powerful server being cut because of FreeBSD/SMP, and I know there is a kernel option to prevent the panic, I read about it ages ago on a forum. But I can't locate it. That user said if he disabled SMP, panics would stop. But another user suggested adding a kernel option (which I simply don't remember), and panics stopped, even with SMP. I tried KVA_PAGES=512, but it only caused another panic, this time as soon as the system started up.. syncing disks, buffers remaining... panic: pmap_invalidate_range: interrupts disabled cpuid = 0; boot() called on cpu#0 uptime: 9s That was the most I got from the datacenter since the sysadmin is on vacations and the guy I spoke to isn't very technical. So, KVA_PAGES isn't the solution.. Here are my rc.conf & sysctl.conf & loader.conf: rc.conf: sshd_enable="YES" usbd_enable="YES" sendmail_enable="NONE" syslogd_enable="YES" syslogd_flags="-ss" linux_enable="YES" inetd_enable="NO" clear_tmp_enable="YES" enable_quotas="YES" check_quotas="YES" update_motd="NO" pf_enable="YES" pf_logd="YES" pf_conf="/etc/pf.conf" sysctl.conf: security.bsd.see_other_uids=0 net.inet.tcp.recvspace=32768 net.inet.tcp.sendspace=32768 net.inet.icmp.drop_redirect=1 net.inet.tcp.blackhole=2 net.inet.udp.blackhole=2 net.inet.tcp.log_in_vain=0 net.inet.udp.log_in_vain=0 kern.maxfiles=32768 security.jail.set_hostname_allowed=0 kern.maxfilesperproc=2000 kern.maxprocperuid=400 kern.coredump=0 net.inet.tcp.msl=7500 kern.ipc.somaxconn=16424 loader.conf: hint.acpi.0.disabled=1 kern.ipc.nmbclusters=32768 kern.ipc.maxsockets=16424 kern.maxproc=8000 These are my custom kernel options: options IPSTEALTH options QUOTA options RANDOM_IP_ID options SC_DISABLE_REBOOT Any help is really appreciated, I have this server idling (compile lots of stuff=die) for 2 weeks now :/ Regards From owner-freebsd-smp@FreeBSD.ORG Sun Aug 1 17:20:21 2004 Return-Path: Delivered-To: freebsd-smp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 44A0116A4CE; Sun, 1 Aug 2004 17:20:21 +0000 (GMT) Received: from www.wcborstel.nl (wcborstel.demon.nl [82.161.134.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id ECEB943D5C; Sun, 1 Aug 2004 17:20:20 +0000 (GMT) (envelope-from jorn@wcborstel.nl) Received: from localhost (localhost.chello.nl [127.0.0.1]) by www.wcborstel.nl (Postfix) with ESMTP id 9FD3D813A; Sun, 1 Aug 2004 19:21:47 +0200 (CEST) Received: from www.wcborstel.nl ([127.0.0.1]) by localhost (www.wcborstel.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 32081-09; Sun, 1 Aug 2004 19:21:47 +0200 (CEST) Received: from [192.168.2.110] (unknown [192.168.2.110]) by www.wcborstel.nl (Postfix) with ESMTP id 5BD5C80F6; Sun, 1 Aug 2004 19:21:47 +0200 (CEST) From: Jorn Argelo To: freebsd-questions@freebsd.org Date: Sun, 1 Aug 2004 19:20:21 +0200 User-Agent: KMail/1.6.2 References: <50335.81.84.175.12.1091365736.squirrel@81.84.175.12> In-Reply-To: <50335.81.84.175.12.1091365736.squirrel@81.84.175.12> MIME-Version: 1.0 Content-Disposition: inline Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-Id: <200408011920.28898.jorn@wcborstel.nl> X-Virus-Scanned: by amavisd-new at mail.domain.tld cc: freebsd-smp@freebsd.org cc: Hugo Silva Subject: Re: FreeBSD 5.2.1 kernel w/ SMP under high load = panic X-BeenThere: freebsd-smp@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD SMP implementation group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Aug 2004 17:20:21 -0000 =2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday 01 August 2004 15:08, Hugo Silva wrote: > I am running a Dual Xeon 2.8ghz w/ SMP, SCHED_ULE on FreeBSD > 5.2.1-RELEASE-p9. Why aren't you running FreeBSD 4.10 on a machine like that? 5.2.1 is simply= =20 NOT ready for production enviroments. Why do you think it's still considere= d=20 as unstable? Your panic is probably being caused by a bad driver, but of=20 course I can't tell you which one. So get in touch with your data centre and get 4.10 on that machine. It will= =20 probably solve most of your problems. Jorn =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBDSZXs2lBCry7iusRAjUlAKCqRB/BZ3invP1wxV0EcD/amkdGRACgjUtR 4JW+zZU9g1JZutwBECAfJJM=3D =3Da8U6 =2D----END PGP SIGNATURE----- From owner-freebsd-smp@FreeBSD.ORG Sun Aug 1 21:48:06 2004 Return-Path: Delivered-To: freebsd-smp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 90A6016A4CE for ; Sun, 1 Aug 2004 21:48:06 +0000 (GMT) Received: from host.teammediaonline.com (host.teammediaonline.com [209.239.38.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id CEB3443D4C for ; Sun, 1 Aug 2004 21:48:05 +0000 (GMT) (envelope-from ftp@vic.cc) Received: (from wwwvic@localhost) by host.teammediaonline.com (8.12.10/8.12.10) id i71Lm4Y0006018; Sun, 1 Aug 2004 17:48:04 -0400 Date: Sun, 1 Aug 2004 17:48:04 -0400 From: ftp@vic.cc Message-Id: <200408012148.i71Lm4Y0006018@host.teammediaonline.com> X-Authentication-Warning: host.teammediaonline.com: wwwvic set sender to ftp@vic.cc using -f To: freebsd-smp@freebsd.org References: <200408012148.i71Llc8h005576@host.teammediaonline.com> In-Reply-To: <200408012148.i71Llc8h005576@host.teammediaonline.com> X-Loop: default@vic.cc Precedence: junk Subject: Re: Status X-BeenThere: freebsd-smp@freebsd.org X-Mailman-Version: 2.1.1 List-Id: FreeBSD SMP implementation group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Aug 2004 21:48:06 -0000 This is an autoresponder. I'll never see your message. From owner-freebsd-smp@FreeBSD.ORG Mon Aug 2 20:57:56 2004 Return-Path: Delivered-To: freebsd-smp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D166C16A4DC for ; Mon, 2 Aug 2004 20:57:54 +0000 (GMT) Received: from mail2.speakeasy.net (mail2.speakeasy.net [216.254.0.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 68ED343D66 for ; Mon, 2 Aug 2004 20:57:50 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 20904 invoked from network); 2 Aug 2004 20:57:49 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 2 Aug 2004 20:57:48 -0000 Received: from 10.50.40.208 (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id i72KvNC4020109; Mon, 2 Aug 2004 16:57:45 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-smp@FreeBSD.org Date: Mon, 2 Aug 2004 15:32:52 -0400 User-Agent: KMail/1.6 References: <50335.81.84.175.12.1091365736.squirrel@81.84.175.12> In-Reply-To: <50335.81.84.175.12.1091365736.squirrel@81.84.175.12> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200408021532.52817.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: Hugo Silva cc: freebsd-questions@FreeBSD.org Subject: Re: FreeBSD 5.2.1 kernel w/ SMP under high load = panic X-BeenThere: freebsd-smp@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD SMP implementation group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Aug 2004 20:57:56 -0000 On Sunday 01 August 2004 09:08 am, Hugo Silva wrote: > I am running a Dual Xeon 2.8ghz w/ SMP, SCHED_ULE on FreeBSD > 5.2.1-RELEASE-p9. > > Whenever I load the server a bit more (let seti@home run, compile stuff in > multiple jails, etc), it will simple go offline. I confirmed with the > datacenter and it is indeed a panic, but the datacenter didn't give me the > panic message. I know for *sure* it's because of the high loads. Hmm, we'd really need the panic message to even start debugging it. > I need to sort this out, this is a powerful server being cut because of > FreeBSD/SMP, and I know there is a kernel option to prevent the panic, I > read about it ages ago on a forum. But I can't locate it. That user said > if he disabled SMP, panics would stop. But another user suggested adding a > kernel option (which I simply don't remember), and panics stopped, even > with SMP. > > I tried KVA_PAGES=512, but it only caused another panic, this time as soon > as the system started up.. > > syncing disks, buffers remaining... panic: pmap_invalidate_range: > interrupts disabled > cpuid = 0; > boot() called on cpu#0 > uptime: 9s Unfortunately, I'd really need the backtrace to see how to fix this panic. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-smp@FreeBSD.ORG Tue Aug 3 00:07:40 2004 Return-Path: Delivered-To: freebsd-smp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6252416A4CE; Tue, 3 Aug 2004 00:07:40 +0000 (GMT) Received: from kira.epconline.net (kira.epconline.net [68.90.68.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id DCA8043D67; Tue, 3 Aug 2004 00:07:39 +0000 (GMT) (envelope-from carock@epconline.com) Received: from kira.epconline.net (localhost [127.0.0.1]) by kira.epconline.net (8.12.11/8.12.10) with ESMTP id i7307Z2t048251; Mon, 2 Aug 2004 19:07:35 -0500 (CDT) (envelope-from carock@epconline.com) Received: from localhost (carock@localhost)i7307ZY7048243; Mon, 2 Aug 2004 19:07:35 -0500 (CDT) (envelope-from carock@epconline.com) X-Authentication-Warning: kira.epconline.net: carock owned process doing -bs Date: Mon, 2 Aug 2004 19:07:35 -0500 (CDT) From: Chuck Rock X-X-Sender: carock@kira.epconline.net To: John Baldwin In-Reply-To: <200408021532.52817.jhb@FreeBSD.org> Message-ID: <20040802190220.B40403@kira.epconline.net> References: <50335.81.84.175.12.1091365736.squirrel@81.84.175.12> <200408021532.52817.jhb@FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Hugo Silva cc: freebsd-smp@freebsd.org cc: freebsd-questions@freebsd.org Subject: Re: FreeBSD 5.2.1 kernel w/ SMP under high load = panic X-BeenThere: freebsd-smp@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD SMP implementation group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Aug 2004 00:07:40 -0000 I had a similar problem with this release running on any Dell 2550 Rack server I had. I tried three different servers with the same config, and I had kernel panics at various times. All of them had different information on the screen at each panic. I had several people tel lme they had no such problems with the same systems. I chalked it up to bad driver for the PERC3/DC raid controller. All panics seemd to happen under very high disk I/O. The machine would run fine for a few days, then just puke. I moved all the stuff over to a refurb Compaq Dual Xeon 2.8, and have had only one problem lockup in the 5 months I've been running it under increasing loads. The last lockup I had also seemed related to disk I/O. Otherwise, 5.2.1 has been a very stable production server processing over 1 million E-mail's a day incoming and hundred thousand out. Chuck On Mon, 2 Aug 2004, John Baldwin wrote: > On Sunday 01 August 2004 09:08 am, Hugo Silva wrote: > > I am running a Dual Xeon 2.8ghz w/ SMP, SCHED_ULE on FreeBSD > > 5.2.1-RELEASE-p9. > > > > Whenever I load the server a bit more (let seti@home run, compile stuff in > > multiple jails, etc), it will simple go offline. I confirmed with the > > datacenter and it is indeed a panic, but the datacenter didn't give me the > > panic message. I know for *sure* it's because of the high loads. > > Hmm, we'd really need the panic message to even start debugging it. > > > I need to sort this out, this is a powerful server being cut because of > > FreeBSD/SMP, and I know there is a kernel option to prevent the panic, I > > read about it ages ago on a forum. But I can't locate it. That user said > > if he disabled SMP, panics would stop. But another user suggested adding a > > kernel option (which I simply don't remember), and panics stopped, even > > with SMP. > > > > I tried KVA_PAGES=512, but it only caused another panic, this time as soon > > as the system started up.. > > > > syncing disks, buffers remaining... panic: pmap_invalidate_range: > > interrupts disabled > > cpuid = 0; > > boot() called on cpu#0 > > uptime: 9s > > Unfortunately, I'd really need the backtrace to see how to fix this panic. > > -- > John Baldwin <>< http://www.FreeBSD.org/~jhb/ > "Power Users Use the Power to Serve" = http://www.FreeBSD.org > _______________________________________________ > freebsd-smp@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-smp > To unsubscribe, send any mail to "freebsd-smp-unsubscribe@freebsd.org" > From owner-freebsd-smp@FreeBSD.ORG Tue Aug 3 08:09:12 2004 Return-Path: Delivered-To: freebsd-smp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 86B5916A4CE; Tue, 3 Aug 2004 08:09:12 +0000 (GMT) Received: from www.wcborstel.nl (wcborstel.demon.nl [82.161.134.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC8CD43D68; Tue, 3 Aug 2004 08:09:09 +0000 (GMT) (envelope-from jorn@wcborstel.nl) Received: from localhost (localhost.chello.nl [127.0.0.1]) by www.wcborstel.nl (Postfix) with ESMTP id DA456813A; Tue, 3 Aug 2004 10:10:36 +0200 (CEST) Received: from www.wcborstel.nl ([127.0.0.1]) by localhost (www.wcborstel.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 46267-01; Tue, 3 Aug 2004 10:10:36 +0200 (CEST) Received: from [192.168.2.110] (unknown [192.168.2.110]) by www.wcborstel.nl (Postfix) with ESMTP id 5FDEC80B3; Tue, 3 Aug 2004 10:10:36 +0200 (CEST) From: Jorn Argelo To: freebsd-questions@freebsd.org Date: Tue, 3 Aug 2004 10:08:43 +0200 User-Agent: KMail/1.6.2 References: <50335.81.84.175.12.1091365736.squirrel@81.84.175.12> <200408021532.52817.jhb@FreeBSD.org> <20040802190220.B40403@kira.epconline.net> In-Reply-To: <20040802190220.B40403@kira.epconline.net> MIME-Version: 1.0 Content-Disposition: inline Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-Id: <200408031009.20022.jorn@wcborstel.nl> X-Virus-Scanned: by amavisd-new at mail.domain.tld cc: freebsd-smp@freebsd.org cc: Hugo Silva cc: Chuck Rock Subject: Re: FreeBSD 5.2.1 kernel w/ SMP under high load = panic X-BeenThere: freebsd-smp@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD SMP implementation group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Aug 2004 08:09:12 -0000 =2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday 03 August 2004 02:07, Chuck Rock wrote: > I had a similar problem with this release running on any Dell 2550 Rack > server I had. I tried three different servers with the same config, and I > had kernel panics at various times. All of them had different information > on the screen at each panic. > > I had several people tel lme they had no such problems with the same > systems. > > I chalked it up to bad driver for the PERC3/DC raid controller. All panics > seemd to happen under very high disk I/O. The machine would run fine for a > few days, then just puke. > > I moved all the stuff over to a refurb Compaq Dual Xeon 2.8, and have had > only one problem lockup in the 5 months I've been running it under > increasing loads. The last lockup I had also seemed related to disk I/O. > > Otherwise, 5.2.1 has been a very stable production server processing over > 1 million E-mail's a day incoming and hundred thousand out. > > Chuck > During my traineeship we had an PowerEdge 2650 (Dual Xeon with FreeBSD 5.1 = at=20 that time). The machine had quite high loads (8.00 - 11.00, which was 24/7)= ,=20 but it kept working most times. Sometimes after a few days or weeks it=20 resulted in a panic. My mentor (who was the Unix specialist) said that it w= as=20 probably been caused by the RAID controller as well. It was a PERC2/DC or=20 PERC3/DC, not really sure. I think it's the latter. Anyway, when 5.2 came=20 out, my mentor immediately upgraded to 5.2, and the machine became rock=20 solid, even with very high loads. It was a monitoring machine, which=20 collected over 1600 SMNP requests from every server, so I'm not really sure= =20 if that produces an high disk I/O or not.=20 Perhaps the story is not interesting, but I felt like sharing that. Cheers, Jorn =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBD0gQs2lBCry7iusRAozeAJ9ID3yBuNSui9EU7tuLJaPZcOc67wCfT7UQ LB+IWXbsYiQQZNs/2CJYz64=3D =3Dr1AQ =2D----END PGP SIGNATURE----- From owner-freebsd-smp@FreeBSD.ORG Thu Aug 5 22:06:25 2004 Return-Path: Delivered-To: freebsd-smp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1A24C16A4CE for ; Thu, 5 Aug 2004 22:06:25 +0000 (GMT) Received: from mail.revolutionsp.com (ganymede.revolutionsp.com [64.246.0.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id D623F43D55 for ; Thu, 5 Aug 2004 22:06:24 +0000 (GMT) (envelope-from klr@6s-gaming.com) Received: from mail.revolutionsp.com (localhost [127.0.0.1]) by mail.revolutionsp.com (Postfix) with ESMTP id B15EF15CB4 for ; Thu, 5 Aug 2004 19:03:56 +0000 (GMT) Received: from 81.84.175.12 (SquirrelMail authenticated user klr@6s-gaming.com); by mail.revolutionsp.com with HTTP; Thu, 5 Aug 2004 19:03:56 -0000 (GMT) Message-ID: <49777.81.84.175.12.1091732636.squirrel@81.84.175.12> Date: Thu, 5 Aug 2004 19:03:56 -0000 (GMT) From: "Hugo Silva" To: freebsd-smp@freebsd.org User-Agent: SquirrelMail/1.4.3a X-Mailer: SquirrelMail/1.4.3a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Subject: FreeBSD 5.2.1 (w/ SMP) - panic - SuperMicro X5DEI-GG ? X-BeenThere: freebsd-smp@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD SMP implementation group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Aug 2004 22:06:25 -0000 Hi, I got a full list of the hardware on this server (Dual Xeon 2.8ghz, 4GB ram), and I was googling for every piece of hardware + FreeBSD. I seem to have found people with problems using the SuperMicro X5DEI-GG mobo. http://unix.derkeiler.com/Mailing-Lists/FreeBSD/net/2003-05/0016.html For those who don't followed my previous messages, the server simply dies (I still don't have the panic message, but someone will go to the datacenter tomorrow and mail it to me - finally) after some hours of usage. First, I thought it was only under high loads. I killed seti@home and let it idle with only postfix & bind9 running, but it died again. In the thread mentioned above, someone recommended removing device apm from the kernel. The problem also seems related to the em0 (which this server has 2, em0 and em1), disabling them in BIOS and adding another NIC (fxp0?) would solve this ? Did anyone have problems with the SuperMicro X5DEI-GG on FreeBSD (5.2.1-rel-p9), and if yes, am I on the right track to solve this issue ? I hope to have more info tomorrow. Many thanks! Regards, Hugo -- www.6s-gaming.com From owner-freebsd-smp@FreeBSD.ORG Fri Aug 6 08:07:53 2004 Return-Path: Delivered-To: freebsd-smp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BE94B16A4CE for ; Fri, 6 Aug 2004 08:07:53 +0000 (GMT) Received: from mail.gmx.net (imap.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 1242943D31 for ; Fri, 6 Aug 2004 08:07:53 +0000 (GMT) (envelope-from h.sandring@gmx.net) Received: (qmail 24506 invoked by uid 65534); 6 Aug 2004 08:07:50 -0000 Received: from unknown (EHLO kojo) (203.70.36.119) by mail.gmx.net (mp016) with SMTP; 06 Aug 2004 10:07:50 +0200 X-Authenticated: #2341648 From: "H. Sandring" To: Date: Fri, 6 Aug 2004 16:13:38 +0800 Message-ID: <001801c47b8d$498ba430$0501a8c0@kojo> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal Subject: MPS X-BeenThere: freebsd-smp@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD SMP implementation group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Aug 2004 08:07:53 -0000 Dear list What is the MPS version of FreeBSD 4.10 and 5.2.1? My BIOS wants to know ;-) TIA Zheyu PLEASE CC me as I am not on this list From owner-freebsd-smp@FreeBSD.ORG Fri Aug 6 19:02:13 2004 Return-Path: Delivered-To: freebsd-smp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2689316A4CE for ; Fri, 6 Aug 2004 19:02:13 +0000 (GMT) Received: from mail5.speakeasy.net (mail5.speakeasy.net [216.254.0.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id E900043D1F for ; Fri, 6 Aug 2004 19:02:12 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 6054 invoked from network); 6 Aug 2004 19:02:12 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 6 Aug 2004 19:02:12 -0000 Received: from 10.50.40.208 (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id i76J28sn050814; Fri, 6 Aug 2004 15:02:09 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-smp@FreeBSD.org Date: Fri, 6 Aug 2004 15:01:18 -0400 User-Agent: KMail/1.6 References: <001801c47b8d$498ba430$0501a8c0@kojo> In-Reply-To: <001801c47b8d$498ba430$0501a8c0@kojo> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200408061501.18107.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: "H. Sandring" Subject: Re: MPS X-BeenThere: freebsd-smp@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD SMP implementation group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Aug 2004 19:02:13 -0000 On Friday 06 August 2004 04:13 am, H. Sandring wrote: > Dear list > > What is the MPS version of FreeBSD 4.10 and 5.2.1? > > My BIOS wants to know ;-) Probably 1.4, but 1.1 should work ok as well. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org