On Fri, Sep 27, 2002 at 03:39:14PM +0000, Eric Belhomme wrote:
> Steve Langasek <[email protected]> ecrivait dans le message
> news:[email protected] :
>
> > Definitely a kernel bug or a hardware bug. I would suggest upgrading
> > to the latest kernel in whichever (2.2,2.4) series you're running, if
> > you haven't already done so, and seeing if that fixes the problem. If
> > it doesn't, you probably need to talk to the Linux kernel developers
> > about this, or perhaps try to test it on a different set of hardware.
> >
> I done tests with these different kernels :
> - debian package "kernel-image-2.4.18-k6"
> - debian package "kernel-image-2.4.18-386"
> - custom debian package for kernel image-2.4.19 with i386 cpu support
> - custom debian package for kernel image-2.4.19 with 586 cpu support
> - custom debian package for kernel image-2.4.19 with k6 cpu support
>
> I also done tests with the lastest stable samba 2.2.5 debian packages
> (compiled by myself) et the official debian stable packages (2.2.3)
>
> So I done 10 tests (about on night of builds, install/uninstall !) ans in
> EVERY CASES, i get the kernel panic caused by smbd process !
>
> It seems to occur when the transfered data volume approaches of 2Gb,
> someties less...
It's a kernel bug. The fact that it happens with these different kernels
means it's a generic kernel bug that is currently unfixed.
*Nothing* smbd does should cause a kernel panic, unless we're overwriting
/dev/kmem. I doubt that.
Jeremy.
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.