From owner-freebsd-hackers Fri Jan 26 2:31:15 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.nettoll.com (matrix.nettoll.net [212.155.143.61]) by hub.freebsd.org (Postfix) with ESMTP id 135AD37B400 for ; Fri, 26 Jan 2001 02:30:57 -0800 (PST) Received: by smtp.nettoll.com; Fri, 26 Jan 2001 11:29:40 +0100 (MET) Message-ID: <3A7151D5.2040405@enition.com> Date: Fri, 26 Jan 2001 11:30:45 +0100 From: Xavier Galleri User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; m18) Gecko/20001108 Netscape6/6.0 X-Accept-Language: en MIME-Version: 1.0 To: Alfred Perlstein Cc: Peter Wemm , freebsd-hackers@FreeBSD.ORG Subject: Re: Kernel memory allocation bug ... References: <200101191524.f0JFOtk14877@mobile.wemm.org> <3A6861DF.8060108@enition.com> <3A706788.5040509@enition.com> <20010125101659.N26076@fw.wintelcom.net> <3A707211.2080801@enition.com> <20010125114602.Q26076@fw.wintelcom.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein wrote: > * Xavier Galleri [010125 10:36] wrote: > >> Alfred Perlstein wrote: >> >>> I told you about 3 times to provide us with a stipped down source >>> code module which reproduces this "bug". >>> >>> You haven't done this. >>> >>> Therefore I can't help you. >>> >> I did not expect to make trouble to anyone, just sorry for the >> inconvenience ... I am not sure that we could easily provide for some >> code sample on this issue since this could be expensive, but I will see >> for sure (I easily understand that this is easier for anybody to track >> down a problem in such conditions ;-). >> >> That said, I still remain astonished not to get any comments or >> questions or hints or any other reactions about the analysis I have >> already provided. I have seen other mails in this list that exposed >> different kind of issues without requiring code sample to feed a >> constructive discussion. Did I miss something ? > > > You missed the two other people reporting "bugs" the same week you > began to. I spend a couple of hours trying to track them down and > they wound up being errors in thier code and not FreeBSD's. > > Honestly the symptoms you describe lean towards error on your part. > Even if they are not your error they seem pretty hard to reproduce. > > You've been complaining about this problem for at least a week. > Producing some code so that we can test couldn't take more than a > couple of hours and would have probably had your issue resolved > by now. > > This is why I'm irritated that you still haven't provided any code > to reproduce it. I wish I could avoid this misunderstanding ! The fact is that I was expecting some hints to track down the problem on myown, especially concerning the FreeBSD behaviour in case of free list shortage. Also, I would appreciate to know if my understanding of the figures I got from 'cnt' or of the scheduling behaviour with regard to kernel preemption is correct. I think this would be helpful for me to build the code sample you are requesting. > I do appreciate your mini-kernel debug howto, I've got it saved > for future reference. I am sincerely happy that I could provide something helpful ... Well, actually, it sounds that I did go to far to be able to retract myself, so I will let you know of any progress I will make asap ;-) Cheers, Xavier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message