Hi all
I'm experiencing something weird, I use distcc over a couple of boxes using
fedora, both of them crash every once in a while if compiling something
remotelly. But it seems to happen only when the sender is my box running
2.6.4-rc1-mm1 kernel, not tried other 2.6 kernels, but with 2.4.25 nothing
bad happened.
The fedora kernel version is 2.4.22-1.2149.nptl.
I know this is not the correct list to ask problems about fedora, but maybe
someone knows what can be happening, and what can I do to trace the problem
down. Should I try to install a vanilla kernel to see if that corrects the
problem ?
Max
--
Linux garaged 2.6.3-mm3 #2 SMP Tue Feb 24 15:44:58 CST 2004 i686 Intel(R)
Pentium(R) 4 CPU 2.80GHz GenuineIntel GNU/Linux
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GS/S d- s: a-29 C++(+++) ULAHI+++ P+ L++>+++ E--- W++ N* o-- K- w++++ O- M--
V-- PS+ PE Y-- PGP++ t- 5- X+ R tv++ b+ DI+++ D- G++ e++ h+ r+ z**
------END GEEK CODE BLOCK------
gpg-key: http://garaged.homeip.net/gpg-key.txt
On Sun, 7 Mar 2004, Max Valdez wrote:
> I know this is not the correct list to ask problems about fedora, but maybe
> someone knows what can be happening, and what can I do to trace the problem
> down. Should I try to install a vanilla kernel to see if that corrects the
> problem ?
One of the fedora mailing lists would be a better place to post.
Do you have SELinux enabled?
Try and get a log of the kernel oops via serial console, or at least write
down the traceback functions.
- James
--
James Morris
<[email protected]>
James Morris wrote:
> On Sun, 7 Mar 2004, Max Valdez wrote:
>
>
>>I know this is not the correct list to ask problems about fedora, but maybe
>>someone knows what can be happening, and what can I do to trace the problem
>>down. Should I try to install a vanilla kernel to see if that corrects the
>>problem ?
>
>
> One of the fedora mailing lists would be a better place to post.
>
> Do you have SELinux enabled?
Just a note : kernel 2.4.22-1.2149.nptl is one of the update kernels for
Fedora Core 1, and SELlinux wasn't included in FC1.
> Try and get a log of the kernel oops via serial console, or at least write
> down the traceback functions.
// Stefan