Hi again,
I am having problems with a machine and cannot pin down why it's abruptly
rebooting...
I can find no messages in any of the logs !
My theories are pointing the blame towards the following configuration :
Redhat 7.2
kernel 2.4.17 patched with i2c-2.6.2.tar.gz.
I am about to attempt building a a fresh kernel... can anyone recommmend a
stable kernel or has anyone experienced problems with 2.4.17 patched with
i2c ?
Many thanks in advance,
Shaf
On Tuesday, 15 January 2002, at 09:59:21 -0000,
Shaf Ali wrote:
> I am having problems with a machine and cannot pin down why it's abruptly
> rebooting...
> I can find no messages in any of the logs !
>
> My theories are pointing the blame towards the following configuration :
> Redhat 7.2
> kernel 2.4.17 patched with i2c-2.6.2.tar.gz.
>
Using i2c 2.6.2 for a while now, with 2.4.17, for use with some TV
capture cards, and no problems so far.
--
Jos? Luis Domingo L?pez
Linux Registered User #189436 Debian Linux Woody (P166 64 MB RAM)
jdomingo AT internautas DOT org => Spam at your own risk
Thanks Jose for your input...
Apparently the culprit was not the the i2c modules afterall....
It was ntop in conjunction with iptables/ians (Intel load balancing
module)...
The macnine is still up after the removal of ntop.
Shaf
----- Original Message -----
From: "Shaf Ali" <[email protected]>
To: <[email protected]>
Cc: <[email protected]>
Sent: Tuesday, January 15, 2002 9:59 AM
Subject: 2.4.17 instability with i2c ?
> Hi again,
>
> I am having problems with a machine and cannot pin down why it's abruptly
> rebooting...
> I can find no messages in any of the logs !
>
> My theories are pointing the blame towards the following configuration :
> Redhat 7.2
> kernel 2.4.17 patched with i2c-2.6.2.tar.gz.
>
> I am about to attempt building a a fresh kernel... can anyone recommmend a
> stable kernel or has anyone experienced problems with 2.4.17 patched with
> i2c ?
>
> Many thanks in advance,
> Shaf
>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>