From: "Shaf Ali" <shaf@shaf.net>
To: <linux-admin@vger.kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <jdomingo@internautas.org>
Subject: Re: 2.4.17 instability with i2c ?
Date: Wed, 16 Jan 2002 18:31:20 -0000 [thread overview]
Message-ID: <014501c19ebb$fe9adf00$308d14ac@tosh> (raw)
In-Reply-To: <1010951831.3241.0.camel@penarol01> <15425.60130.574569.697952@cerise.nosuchdomain.co.uk> <002a01c19dab$4de66dc0$a52efea9@tosh>
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" <shaf@shaf.net>
To: <linux-admin@vger.kernel.org>
Cc: <linux-kernel@vger.kernel.org>
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 majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2002-01-16 18:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1010951831.3241.0.camel@penarol01>
[not found] ` <15425.60130.574569.697952@cerise.nosuchdomain.co.uk>
2002-01-15 9:59 ` 2.4.17 instability with i2c ? Shaf Ali
2002-01-15 21:30 ` Jose Luis Domingo Lopez
2002-01-16 18:31 ` Shaf Ali [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='014501c19ebb$fe9adf00$308d14ac@tosh' \
--to=shaf@shaf.net \
--cc=jdomingo@internautas.org \
--cc=linux-admin@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.