From owner-freebsd-smp Sun Nov 18 16:43:26 2001 Delivered-To: freebsd-smp@freebsd.org Received: from yourwebsite.com (evrtwa1-ar1-252-128.elnk.dsl.gtei.net [4.34.252.128]) by hub.freebsd.org (Postfix) with SMTP id A2E9237B417 for ; Sun, 18 Nov 2001 16:43:13 -0800 (PST) Reply-To: bawf@usa.net From: bawf@usa.net To: smp@FreeBSD.org Subject: Accept Credit Cards For Your Business Mime-Version: 1.0 Content-Type: text/html; charset="iso-8859-1" Date: Sun, 18 Nov 2001 15:59:50 -0800 Message-Id: <20011119004313.A2E9237B417@hub.freebsd.org> 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 If you agree with these statements, we need to talk as soon as possible:

If you agree with these statements, we need to talk as soon as possible:

1. It would be desirable to increase your income by at least 30%-75%.

2. No-shows and cancellations cost you time and (more importantly)
money.

3. It would be desirable to guarantee payment in advance for every
sale you make, eliminating the need for time-consuming invoices and
follow-up calls to demand payment for your services.

4. Cash flow is probably the single most important element in your
business today.

There is a cost-efficient method to increase impulse buying, attract new
clients and their referrals, increase the ticket price of each item,
accept deposits, and guarantee payment from otherwise delinquent
clients- A MERCHANT ACCOUNT THAT WILL ALLOW YOU TO ACCEPT CREDIT CARDS
AS A FORM OF PAYMENT!

I don't need to tell you how important a merchant account is to the
success of your business. If you don't provide your clients with every
payment option available, they will take their business elsewhere.

Visa/MasterCard reports that customers tend to spend twice as much when
they can use their credit cards- that means more frequent and more
lucrative sales for you, which equals more money!

We have low, competitive rates and unbeatable, custom-tailored services
that cater to your individual needs. We also have a 98% approval rate
(and for any home-based merchant who has attempted applying for a
merchant account, you know how difficult it can be to get approved!).
Starting as low as 39.99/month, you can begin accepting credit cards within
10 business days!

We pride ourselves in excellent customer service and guaranteed
satisfaction with 24-hour customer/technical support. Our company has
been helping businesses like yours for years across the country. But
our longevity and our impressive client list are not why you should use
our service. They're simply the reason customers continue to use our
services. We not only employ the best-trained personnel; we also
utilize sophisticated technology to ensure the success and efficiency of
your merchant account.

Please email us at Broad & Wall Financial for more
information and start accepting credit cards for your home-based,
Internet, mail order/telephone order, or retail storefront business
now! In your email, please include your contact information and a good
time for one of our knowledgeable account representatives to reach you.

Sincerely,
New Accounts Dept.


PS- We have some great specials going until the end of the month!!

 

To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Tue Nov 20 13:24:57 2001 Delivered-To: freebsd-smp@freebsd.org Received: from vellocet.insync.net (vellocet.insync.net [204.253.208.10]) by hub.freebsd.org (Postfix) with ESMTP id E3B2037B416 for ; Tue, 20 Nov 2001 13:24:52 -0800 (PST) Received: from localhost (calvin@localhost) by vellocet.insync.net (8.9.3/8.9.3) with ESMTP id PAA10728 for ; Tue, 20 Nov 2001 15:24:52 -0600 (CST) Date: Tue, 20 Nov 2001 15:24:51 -0600 (CST) From: "Calvin G." To: Subject: SMP with Proliant 1600??? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 4.4 install went well, except for when I re-compiled the kernel with SMP support. It is now hanging on boot. I have noticed this has been a problem in later versions but they said they fixed it. I have submited a problem report but I thought I would also ask around and see if anyone else has had this problem. http://www.freebsd.org/cgi/query-pr.cgi?pr=32127 Calvin Gorriaran System Administrator, ATS Insync Internet Services, Inc. 713-439-2273 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Tue Nov 20 13:43:29 2001 Delivered-To: freebsd-smp@freebsd.org Received: from vellocet.insync.net (vellocet.insync.net [204.253.208.10]) by hub.freebsd.org (Postfix) with ESMTP id B526C37B418 for ; Tue, 20 Nov 2001 13:43:25 -0800 (PST) Received: from localhost (calvin@localhost) by vellocet.insync.net (8.9.3/8.9.3) with ESMTP id PAA11554 for ; Tue, 20 Nov 2001 15:43:25 -0600 (CST) Date: Tue, 20 Nov 2001 15:43:24 -0600 (CST) From: "Calvin G." To: Subject: SMP with Proliant 1600??? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 4.4 install went well, except for when I re-compiled the kernel with SMP support. It is now hanging on boot. I have noticed this has been a problem in later versions but they said they fixed it. I have submited a problem report but I thought I would also ask around and see if anyone else has had this problem. Details... http://www.freebsd.org/cgi/query-pr.cgi?pr=32127 Calvin Gorriaran System Administrator, ATS Insync Internet Services, Inc. 713-439-2273 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Tue Nov 20 23:31:39 2001 Delivered-To: freebsd-smp@freebsd.org Received: from peter3.wemm.org (c1315225-a.plstn1.sfba.home.com [24.14.150.180]) by hub.freebsd.org (Postfix) with ESMTP id 422A237B416 for ; Tue, 20 Nov 2001 23:31:37 -0800 (PST) Received: from overcee.netplex.com.au (overcee.wemm.org [10.0.0.3]) by peter3.wemm.org (8.11.0/8.11.0) with ESMTP id fAL7VbM49521 for ; Tue, 20 Nov 2001 23:31:37 -0800 (PST) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id F33673811; Tue, 20 Nov 2001 23:31:36 -0800 (PST) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: "Calvin G." Cc: freebsd-smp@FreeBSD.ORG Subject: Re: SMP with Proliant 1600??? In-Reply-To: Date: Tue, 20 Nov 2001 23:31:36 -0800 From: Peter Wemm Message-Id: <20011121073137.F33673811@overcee.netplex.com.au> 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 "Calvin G." wrote: > > 4.4 install went well, except for when I re-compiled the kernel with SMP > support. It is now hanging on boot. I have noticed this has been a problem > in later versions but they said they fixed it. I have submited a problem > report but I thought I would also ask around and see if anyone else has > had this problem. > > Details... > > http://www.freebsd.org/cgi/query-pr.cgi?pr=32127 Not enough.. More dmesg is required. Also, boot -v. If I had to guess, I'd say that you selected "Other" as the OS type. If so, Dont Do That. Select either Windows NT or Linux. If you dont select an OS that Compaq deem to have SMP support, it partly disables some of the SMP hardware and causes this sort of lockup. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Tue Nov 20 23:57:57 2001 Delivered-To: freebsd-smp@freebsd.org Received: from vellocet.insync.net (vellocet.insync.net [204.253.208.10]) by hub.freebsd.org (Postfix) with ESMTP id E29F337B405 for ; Tue, 20 Nov 2001 23:57:50 -0800 (PST) Received: from localhost (calvin@localhost) by vellocet.insync.net (8.9.3/8.9.3) with ESMTP id BAA02617; Wed, 21 Nov 2001 01:57:48 -0600 (CST) Date: Wed, 21 Nov 2001 01:57:47 -0600 (CST) From: "Calvin G." To: Peter Wemm Cc: Subject: Re: SMP with Proliant 1600??? In-Reply-To: <20011121073137.F33673811@overcee.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 You are right, I did select other during the smart start config. Calvin Gorriaran System Administrator, ATS Insync Internet Services, Inc. 713-439-2273 On Tue, 20 Nov 2001, Peter Wemm wrote: > Date: Tue, 20 Nov 2001 23:31:36 -0800 > From: Peter Wemm > To: Calvin G. > Cc: freebsd-smp@FreeBSD.ORG > Subject: Re: SMP with Proliant 1600??? > > "Calvin G." wrote: > > > > 4.4 install went well, except for when I re-compiled the kernel with SMP > > support. It is now hanging on boot. I have noticed this has been a problem > > in later versions but they said they fixed it. I have submited a problem > > report but I thought I would also ask around and see if anyone else has > > had this problem. > > > > Details... > > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=32127 > > Not enough.. More dmesg is required. Also, boot -v. > If I had to guess, I'd say that you selected "Other" as the OS type. If > so, Dont Do That. Select either Windows NT or Linux. If you dont select > an OS that Compaq deem to have SMP support, it partly disables some of the > SMP hardware and causes this sort of lockup. > > Cheers, > -Peter > -- > Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au > "All of this is for nothing if we don't go to the stars" - JMS/B5 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Wed Nov 21 0: 4:38 2001 Delivered-To: freebsd-smp@freebsd.org Received: from vellocet.insync.net (vellocet.insync.net [204.253.208.10]) by hub.freebsd.org (Postfix) with ESMTP id 6722A37B417 for ; Wed, 21 Nov 2001 00:04:34 -0800 (PST) Received: from localhost (calvin@localhost) by vellocet.insync.net (8.9.3/8.9.3) with ESMTP id CAA02836; Wed, 21 Nov 2001 02:04:33 -0600 (CST) Date: Wed, 21 Nov 2001 02:04:32 -0600 (CST) From: "Calvin G." To: Peter Wemm Cc: Subject: Re: SMP with Proliant 1600??? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 Well that fixed it. I set the OS in the BIOS to Windows NT and it boots fine now. Thanks for your help, that was driving me crazy. Calvin Gorriaran System Administrator, ATS Insync Internet Services, Inc. 713-439-2273 On Wed, 21 Nov 2001, Calvin G. wrote: > Date: Wed, 21 Nov 2001 01:57:47 -0600 (CST) > From: Calvin G. > To: Peter Wemm > Cc: freebsd-smp@FreeBSD.ORG > Subject: Re: SMP with Proliant 1600??? > > You are right, I did select other during the smart start config. > > > Calvin Gorriaran > System Administrator, ATS > Insync Internet Services, Inc. > 713-439-2273 > > On Tue, 20 Nov 2001, Peter Wemm wrote: > > > Date: Tue, 20 Nov 2001 23:31:36 -0800 > > From: Peter Wemm > > To: Calvin G. > > Cc: freebsd-smp@FreeBSD.ORG > > Subject: Re: SMP with Proliant 1600??? > > > > "Calvin G." wrote: > > > > > > 4.4 install went well, except for when I re-compiled the kernel with SMP > > > support. It is now hanging on boot. I have noticed this has been a problem > > > in later versions but they said they fixed it. I have submited a problem > > > report but I thought I would also ask around and see if anyone else has > > > had this problem. > > > > > > Details... > > > > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=32127 > > > > Not enough.. More dmesg is required. Also, boot -v. > > If I had to guess, I'd say that you selected "Other" as the OS type. If > > so, Dont Do That. Select either Windows NT or Linux. If you dont select > > an OS that Compaq deem to have SMP support, it partly disables some of the > > SMP hardware and causes this sort of lockup. > > > > Cheers, > > -Peter > > -- > > Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au > > "All of this is for nothing if we don't go to the stars" - JMS/B5 > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-smp" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Wed Nov 21 6: 2:25 2001 Delivered-To: freebsd-smp@freebsd.org Received: from grafin.fujimori.cache.waseda.ac.jp (grafin.fujimori.cache.waseda.ac.jp [133.9.152.154]) by hub.freebsd.org (Postfix) with ESMTP id F35D537B416 for ; Wed, 21 Nov 2001 06:02:22 -0800 (PST) Received: from grafin.fujimori.cache.waseda.ac.jp (fujimori@localhost [127.0.0.1]) by grafin.fujimori.cache.waseda.ac.jp (8.11.3/3.7W) with ESMTP id fALE2IV07067 for ; Wed, 21 Nov 2001 23:02:18 +0900 Message-Id: <200111211402.fALE2IV07067@grafin.fujimori.cache.waseda.ac.jp> To: freebsd-smp@freebsd.org Subject: nfsd/ypserv die on smp Date: Wed, 21 Nov 2001 23:02:18 +0000 From: Yoriaki FUJIMORI 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 Dear Folks, I am running R4.4 on dual P3/1GHz PC box. The box is meant to be the file server and nis server in my network. In these weeks, I am observing very funny things on this box. The problem is that, as stated in the Subject line, nfsd and ypserv die on this smp box. (1) When I started running R4.3, I noticed ypserv dies within a few days, while nfsd dies very rarely. `lastcomm ypserv' returns "-SFX" mark. (2) Now, on R4.4, nfsd die often. `lastcomm nfsd' also returns the same. # Yesterday, I invoked nfsd with `-u -t -n 16', but now only 9 of them are alive. I run ypserv on other uni-processor box (slave server), and this is fine. So, I guess the problem might be related to smp. I wonder if some of you have got a similar observation. Yoriaki Fujimori To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Wed Nov 21 10:40:10 2001 Delivered-To: freebsd-smp@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id D13F037B41C for ; Wed, 21 Nov 2001 10:40:06 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1192) id A4D7D81D17; Wed, 21 Nov 2001 12:40:01 -0600 (CST) Date: Wed, 21 Nov 2001 12:40:01 -0600 From: Alfred Perlstein To: Yoriaki FUJIMORI Cc: freebsd-smp@freebsd.org Subject: Re: nfsd/ypserv die on smp Message-ID: <20011121124001.H13393@elvis.mu.org> References: <200111211402.fALE2IV07067@grafin.fujimori.cache.waseda.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200111211402.fALE2IV07067@grafin.fujimori.cache.waseda.ac.jp>; from fujimori@grafin.fujimori.cache.waseda.ac.jp on Wed, Nov 21, 2001 at 11:02:18PM +0000 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 * Yoriaki FUJIMORI [011121 08:02] wrote: > Dear Folks, > I am running R4.4 on dual P3/1GHz PC box. The box is meant to be the > file server and nis server in my network. In these weeks, I am observing > very funny things on this box. > > The problem is that, as stated in the Subject line, nfsd and ypserv die > on this smp box. > (1) When I started running R4.3, I noticed ypserv dies within a few days, > while nfsd dies very rarely. `lastcomm ypserv' returns "-SFX" mark. > (2) Now, on R4.4, nfsd die often. `lastcomm nfsd' also returns the > same. > # Yesterday, I invoked nfsd with `-u -t -n 16', but now only 9 > of them are alive. I think there's some weirdness in either the nfsd userland or kernel code that makes "max startups" limited to 8 or so. The nfsds probably didn't die, they just never started up. Can you test to see what happens right away if you issue -n 16? -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' http://www.morons.org/rants/gpl-harmful.php3 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Wed Nov 21 10:50:35 2001 Delivered-To: freebsd-smp@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id 6029437B405 for ; Wed, 21 Nov 2001 10:50:31 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1192) id 6090C81D18; Wed, 21 Nov 2001 12:50:31 -0600 (CST) Date: Wed, 21 Nov 2001 12:50:31 -0600 From: Alfred Perlstein To: Yoriaki FUJIMORI Cc: freebsd-smp@freebsd.org Subject: Re: nfsd/ypserv die on smp Message-ID: <20011121125031.I13393@elvis.mu.org> References: <200111211402.fALE2IV07067@grafin.fujimori.cache.waseda.ac.jp> <20011121124001.H13393@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011121124001.H13393@elvis.mu.org>; from bright@mu.org on Wed, Nov 21, 2001 at 12:40:01PM -0600 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 * Alfred Perlstein [011121 12:40] wrote: > * Yoriaki FUJIMORI [011121 08:02] wrote: > > Dear Folks, > > I am running R4.4 on dual P3/1GHz PC box. The box is meant to be the > > file server and nis server in my network. In these weeks, I am observing > > very funny things on this box. > > > > The problem is that, as stated in the Subject line, nfsd and ypserv die > > on this smp box. > > (1) When I started running R4.3, I noticed ypserv dies within a few days, > > while nfsd dies very rarely. `lastcomm ypserv' returns "-SFX" mark. > > (2) Now, on R4.4, nfsd die often. `lastcomm nfsd' also returns the > > same. > > # Yesterday, I invoked nfsd with `-u -t -n 16', but now only 9 > > of them are alive. > > I think there's some weirdness in either the nfsd userland or kernel > code that makes "max startups" limited to 8 or so. The nfsds probably > didn't die, they just never started up. Can you test to see what > happens right away if you issue -n 16? Hmm, that limit actually seems to be '20' not '8', so ok, any log messages you can find? Any "funny" admins? Did you restart services? It sort of seems like at least in 4.4 that there's about two places where nfsd can exit(3), odd though... -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' http://www.morons.org/rants/gpl-harmful.php3 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Thu Nov 22 4:19:51 2001 Delivered-To: freebsd-smp@freebsd.org Received: from prinz.fujimori.cache.waseda.ac.jp (prinz.fujimori.cache.waseda.ac.jp [133.9.152.239]) by hub.freebsd.org (Postfix) with ESMTP id 0C2BD37B416 for ; Thu, 22 Nov 2001 04:19:44 -0800 (PST) Received: from prinz.fujimori.cache.waseda.ac.jp (localhost [127.0.0.1]) by prinz.fujimori.cache.waseda.ac.jp (8.11.6/8.11.6) with ESMTP id fAMCJgw10422; Thu, 22 Nov 2001 21:19:43 +0900 (JST) (envelope-from fujimori@prinz.fujimori.cache.waseda.ac.jp) Message-Id: <200111221219.fAMCJgw10422@prinz.fujimori.cache.waseda.ac.jp> To: Alfred Perlstein Cc: freebsd-smp@freebsd.org Subject: Re: nfsd/ypserv die on smp In-reply-to: Your message of "Wed, 21 Nov 2001 12:50:31 CST." <20011121125031.I13393@elvis.mu.org> Date: Thu, 22 Nov 2001 21:19:42 +0900 From: Yoriaki FUJIMORI 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 There is no log message about this. I tested several environmental changes such as nfs_reserveved_port_only="YES" or "NO" etc in rc.conf. But, the situation does not change at all. After rebooting this server running nfsd, I noticed a case in which this happens. Suppose S is an nfs server and C1, C2, .., Cn are nfs clients. Assume nfsd servers are invoked on S on Nov 22, while nfsiod on C1, .., Cn are invoked earlier, say on Nov 21. Then, nfsd server dies. This can easily reproduced by invoking on C1, say, find /hogehoge -name brahbrah -print where /hogehoge is nfs mount from S. From `lastcomm nfsd' on S, I know that nfsd dies with the invoke date Nov 21 xx:yy, at this date nfsiod is invoked on C1. So, nfsd dies when it is combined with clients' nfsiod which is older than nfsd itself. I do not know yet, if this is a default from the security reason. However, as I said previously, this happens only on smp systems. (No problem at all on uni processor systems here.) Yoriaki Fujimori To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Thu Nov 22 5: 1:28 2001 Delivered-To: freebsd-smp@freebsd.org Received: from prinz.fujimori.cache.waseda.ac.jp (prinz.fujimori.cache.waseda.ac.jp [133.9.152.239]) by hub.freebsd.org (Postfix) with ESMTP id 059BA37B416 for ; Thu, 22 Nov 2001 05:01:26 -0800 (PST) Received: from prinz.fujimori.cache.waseda.ac.jp (localhost [127.0.0.1]) by prinz.fujimori.cache.waseda.ac.jp (8.11.6/8.11.6) with ESMTP id fAMD1Ow10621 for ; Thu, 22 Nov 2001 22:01:24 +0900 (JST) (envelope-from fujimori@prinz.fujimori.cache.waseda.ac.jp) Message-Id: <200111221301.fAMD1Ow10621@prinz.fujimori.cache.waseda.ac.jp> To: freebsd-smp@freebsd.org Subject: Re: nfsd/ypserv die on smp In-reply-to: Your message of "Thu, 22 Nov 2001 21:19:42 JST." <200111221219.fAMCJgw10422@prinz.fujimori.cache.waseda.ac.jp> Date: Thu, 22 Nov 2001 22:01:24 +0900 From: Yoriaki FUJIMORI 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 I have to correct some of my reports. The time stamp of nfsd which is dead is wrong. Theire date do not match the date of corresponding nfsiod. Their date which appears in `lastcomm nfsd' result line is just much older than now, I have to say. Something is wrong on smp of 4.4R, though. Yoriaki Fujimori To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Thu Nov 22 5:24:18 2001 Delivered-To: freebsd-smp@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 17C6937B416 for ; Thu, 22 Nov 2001 05:24:09 -0800 (PST) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 22 Nov 2001 13:24:08 +0000 (GMT) To: Yoriaki FUJIMORI Cc: freebsd-smp@freebsd.org Subject: Re: nfsd/ypserv die on smp In-Reply-To: Your message of "Thu, 22 Nov 2001 22:01:24 +0900." <200111221301.fAMD1Ow10621@prinz.fujimori.cache.waseda.ac.jp> Date: Thu, 22 Nov 2001 13:24:07 +0000 From: Ian Dowse Message-ID: <200111221324.aa00865@salmon.maths.tcd.ie> 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 In message <200111221301.fAMD1Ow10621@prinz.fujimori.cache.waseda.ac.jp>, Yoria ki FUJIMORI writes: > >I have to correct some of my reports. >The time stamp of nfsd which is dead is wrong. >Theire date do not match the date of corresponding nfsiod. >Their date which appears in `lastcomm nfsd' result line is just >much older than now, I have to say. >Something is wrong on smp of 4.4R, though. It would be useful if you could capture a ktrace dump of what happens when the nfsd exits. That should provide a few hints about why it is exiting. The easiest way to do this would be to kill all the nfsd's and then run: ktrace -i nfsd -u -t -n 10 Then, whenever you see an nfsd exit, stop the tracing ("ktrace -C"), and use kdump to look for the last few things the nfsd did before it exited. Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Thu Nov 22 6:16:58 2001 Delivered-To: freebsd-smp@freebsd.org Received: from prinz.fujimori.cache.waseda.ac.jp (prinz.fujimori.cache.waseda.ac.jp [133.9.152.239]) by hub.freebsd.org (Postfix) with ESMTP id E8CE637B417 for ; Thu, 22 Nov 2001 06:16:41 -0800 (PST) Received: from prinz.fujimori.cache.waseda.ac.jp (localhost [127.0.0.1]) by prinz.fujimori.cache.waseda.ac.jp (8.11.6/8.11.6) with ESMTP id fAMEGVw11024; Thu, 22 Nov 2001 23:16:31 +0900 (JST) (envelope-from fujimori@prinz.fujimori.cache.waseda.ac.jp) Message-Id: <200111221416.fAMEGVw11024@prinz.fujimori.cache.waseda.ac.jp> To: Ian Dowse Cc: freebsd-smp@freebsd.org Subject: Re: nfsd/ypserv die on smp In-reply-to: Your message of "Thu, 22 Nov 2001 13:24:07 GMT." <200111221324.aa00865@salmon.maths.tcd.ie> Date: Thu, 22 Nov 2001 23:16:31 +0900 From: Yoriaki FUJIMORI 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 I once stopped the machine and started ktrace on it. The following is a part of ktrace.out by kdump: pid 3998 is the master nfsd, and the 3999 is its child; 3999 nfsd CSW stop kernel 3999 nfsd CSW resume kernel 3999 nfsd CSW stop kernel 3999 nfsd CSW resume kernel 3999 nfsd CSW stop kernel 3999 nfsd CSW resume kernel 3999 nfsd CSW stop kernel 3999 nfsd CSW resume kernel 3999 nfsd CSW stop kernel 3999 nfsd CSW resume kernel 3999 nfsd CSW stop kernel 3999 nfsd CSW resume kernel 3999 nfsd CSW stop kernel 3999 nfsd CSW resume kernel 3999 nfsd CSW stop kernel 3999 nfsd CSW resume kernel 3999 nfsd CSW stop kernel 3999 nfsd CSW resume kernel 3999 nfsd CSW stop kernel 3999 nfsd CSW resume kernel 3999 nfsd CSW stop kernel 3999 nfsd CSW resume kernel 3999 nfsd CSW stop kernel 3999 nfsd CSW resume kernel 3999 nfsd CSW stop kernel 3999 nfsd CSW resume kernel 3999 nfsd CSW stop kernel 3999 nfsd CSW resume kernel 3999 nfsd CSW stop kernel 3999 nfsd CSW resume kernel 3999 nfsd CSW stop kernel 3999 nfsd CSW resume kernel 3999 nfsd CSW stop kernel 3999 nfsd CSW resume kernel 3999 nfsd CSW stop kernel 3999 nfsd CSW resume kernel 3999 nfsd CSW stop kernel 3999 nfsd CSW resume kernel 3999 nfsd CSW stop kernel 3999 nfsd CSW resume kernel 3999 nfsd CSW stop kernel 3999 nfsd CSW resume kernel 3999 nfsd CSW stop kernel 3999 nfsd CSW resume kernel 3999 nfsd CSW stop kernel 3999 nfsd CSW resume kernel 3999 nfsd CSW stop kernel 3999 nfsd CSW resume kernel 3999 nfsd CSW stop kernel 3999 nfsd CSW resume kernel 3999 nfsd CSW stop kernel 3999 nfsd CSW resume kernel 3999 nfsd CSW stop kernel 3999 nfsd CSW resume kernel 3999 nfsd CSW stop kernel 3999 nfsd CSW resume kernel 3999 nfsd CSW stop kernel 3999 nfsd CSW resume kernel 3999 nfsd PSIG SIGPROF SIG_DFL 3998 nfsd CSW resume kernel 3998 nfsd PSIG SIGCHLD caught handler=0x8048bf8 mask=0x0 code=0x0 3998 nfsd RET accept RESTART 3998 nfsd CALL wait4(0xffffffff,0,0x1,0) 4000 nfsd CSW resume kernel As you see in tha above, at the sizth line from the bottom, 3999 is dead. Before that point, a thousnd of similar lines of CSW appear. # I guess the scheduling between two cpus are not working. Yoriaki Fujimori To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Thu Nov 22 6:54:43 2001 Delivered-To: freebsd-smp@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 896DB37B416 for ; Thu, 22 Nov 2001 06:54:40 -0800 (PST) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 22 Nov 2001 14:54:39 +0000 (GMT) To: Yoriaki FUJIMORI Cc: freebsd-smp@freebsd.org Subject: Re: nfsd/ypserv die on smp In-Reply-To: Your message of "Thu, 22 Nov 2001 23:16:31 +0900." <200111221416.fAMEGVw11024@prinz.fujimori.cache.waseda.ac.jp> Date: Thu, 22 Nov 2001 14:54:39 +0000 From: Ian Dowse Message-ID: <200111221454.aa21292@salmon.maths.tcd.ie> 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 In message <200111221416.fAMEGVw11024@prinz.fujimori.cache.waseda.ac.jp>, Yoria ki FUJIMORI writes: > > 3999 nfsd PSIG SIGPROF SIG_DFL Ah, SIGPROF. This is a common side-effect of overflows in the per-process kernel stack. Shortly after 4.4-RELEASE the size of the per-process kernel stack was increased due to this problem. If you cvsup to 4-STABLE, or alternatively change the definition of "UPAGES" in /usr/src/sys/i386/include/param.h from 2 to 3 and rebuild your kernel, then the problem should go away. Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message