From: "Henning P. Schmiedehausen" <hps@intermeta.de>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.19-ac4 IRQ messup?
Date: Tue, 6 Aug 2002 16:50:33 +0000 (UTC) [thread overview]
Message-ID: <aiouop$5ut$1@forge.intermeta.de> (raw)
In-Reply-To: 200208061643.56773.tmi@wikon.de
Thomas Mierau <tmi@wikon.de> writes:
>I switched cables, checked the switch etc....
>nothing helps.
>I installed an extra PCI card which came up as eth0, making the internal ones
>eth1 and eth2. No I started pinging with eth0, which was giving me strange
>effects again.
>eth0 = 192.168.47.11
>eth1 = 192.168.47.12
>eth2 = 192.168.47.13
>I took a tcpdump on the receiving box. It was kind of interesting.
>There were arp packages askin who is 192.168.47.11 and answers coming back
>with two dofferent MAC-Id's One from the eth0 and the other one from the eth2
>which was actually configured on IP .13
> After I shut down etho1 and 2 and ran the box with "noapic" it preforms
>perfect with the external card.
>Either the NIC's are broken, or the driver or whatever. I hate that !!
Are they all on the same ethernet? If yes, then
a) don't do this
b) try echo "1"> /proc/sys/net/ipv4/conf/all/arp_filter
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen -- Geschaeftsfuehrer
INTERMETA - Gesellschaft fuer Mehrwertdienste mbH hps@intermeta.de
Am Schwabachgrund 22 Fon.: 09131 / 50654-0 info@intermeta.de
D-91054 Buckenhof Fax.: 09131 / 50654-20
prev parent reply other threads:[~2002-08-06 16:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-05 21:03 Heavy Clock-Drift after update from Kernel 2.4.9 to 2.4.19 Matthias Schniedermeyer
2002-08-05 22:26 ` Alan Cox
2002-08-05 22:17 ` Matthias Schniedermeyer
2002-08-06 8:14 ` 2.4.19-ac4 IRQ messup? Thomas Mierau
2002-08-06 8:39 ` Willy Tarreau
2002-08-06 9:39 ` Thomas Mierau
2002-08-06 10:01 ` Willy Tarreau
2002-08-06 14:44 ` Thomas Mierau
2002-08-06 16:50 ` Henning P. Schmiedehausen [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='aiouop$5ut$1@forge.intermeta.de' \
--to=hps@intermeta.de \
--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.