Re: Kernel memory allocation bug ...

Xavier Galleri wrote: [...] >> 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'

Re: Kernel memory allocation bug ...

Alfred Perlstein wrote: > * Xavier Galleri <[EMAIL PROTECTED]> [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

Re: Kernel memory allocation bug ...

* Jordan Hubbard <[EMAIL PROTECTED]> [010125 10:52] wrote: > > 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 is

Re: Kernel memory allocation bug ...

* Xavier Galleri <[EMAIL PROTECTED]> [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

Re: Kernel memory allocation bug ...

> 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 discus

Re: Kernel memory allocation bug ...

Alfred Perlstein wrote: > * Xavier Galleri <[EMAIL PROTECTED]> [010125 09:53] >wrote: > >> Well, I am a bit disappointed to get no answer at all to my issue. Is it >> because this is not the correct fashion to ask for support on what has >> been identified as a pote

Re: Kernel memory allocation bug ...

* Xavier Galleri <[EMAIL PROTECTED]> [010125 09:53] wrote: > > Well, I am a bit disappointed to get no answer at all to my issue. Is it > because this is not the correct fashion to ask for support on what has > been identified as a potential kernel bug ? Please, let me know what I > am suppose

Re: Kernel memory allocation bug ...

Xavier Galleri wrote: > Peter Wemm wrote: > >> Xavier Galleri wrote: >> >>> Hi everybody, >>> >>> This mail is related to the 'Need help for crash dump analysis' >>> mail serie and the more recent 'Information on kernel crash dump >>> analysis' mail. >> >> What kernel version again? Any u

Re: Kernel memory allocation bug ...

Peter Wemm wrote: > Xavier Galleri wrote: > >> Hi everybody, >> >> This mail is related to the 'Need help for crash dump analysis' mail >> serie and the more recent 'Information on kernel crash dump analysis' mail. > > > What kernel version again? Any unusual options? (eg: SMP etc) > > Ch

Re: Kernel memory allocation bug ...

Xavier Galleri wrote: > Hi everybody, > > This mail is related to the 'Need help for crash dump analysis' mail > serie and the more recent 'Information on kernel crash dump analysis' mail. What kernel version again? Any unusual options? (eg: SMP etc) Cheers, -Peter -- Peter Wemm - [EMAIL PRO

Kernel memory allocation bug ...

Hi everybody, This mail is related to the 'Need help for crash dump analysis' mail serie and the more recent 'Information on kernel crash dump analysis' mail. I have achieved to (manually) get a stack dump by getting my 'curpcb' value at the time I call MALLOC and then issuing 'info frame' and