From: Robert Love <rml@tech9.net>
To: Russell King <rmk@arm.linux.org.uk>
Cc: Dan Chen <crimsun@email.unc.edu>,
linux-kernel@vger.kernel.org, andrea@suse.de
Subject: Re: 2.4.18pre4aa1
Date: 22 Jan 2002 05:12:28 -0500 [thread overview]
Message-ID: <1011694349.850.658.camel@phantasy> (raw)
In-Reply-To: <20020122100230.B20650@flint.arm.linux.org.uk>
In-Reply-To: <20020122074806.A1547@athlon.random> <1011682739.17096.563.camel@phantasy> <20020122073742.GA767@opeth.ath.cx> <20020122100230.B20650@flint.arm.linux.org.uk>
On Tue, 2002-01-22 at 05:02, Russell King wrote:
> On Tue, Jan 22, 2002 at 02:37:42AM -0500, Dan Chen wrote:
> > No weird anomalies here. I believe the ones you refer to were a result
> > of ipv6 bits not being updated as well. Russell posted two patches for
> > those.
>
> No - I do see weirdness in ipv4 as well:
OK, this is the anomaly I spoke of. Weird ICMP errors. I've seen
others with this problem.
I don't think we have a proper solution here.
> bash-2.04# uptime
> 10:00am up 18:57, 1 user, load average: 0.02, 0.03, 0.00
> bash-2.04# dmesg|grep 'broad'
> 127.0.0.1 sent an invalid ICMP error to a broadcast.
> 127.0.0.1 sent an invalid ICMP error to a broadcast.
> 127.0.0.1 sent an invalid ICMP error to a broadcast.
> 127.0.0.1 sent an invalid ICMP error to a broadcast.
> 127.0.0.1 sent an invalid ICMP error to a broadcast.
> 127.0.0.1 sent an invalid ICMP error to a broadcast.
> 127.0.0.1 sent an invalid ICMP error to a broadcast.
> 127.0.0.1 sent an invalid ICMP error to a broadcast.
> 127.0.0.1 sent an invalid ICMP error to a broadcast.
> 127.0.0.1 sent an invalid ICMP error to a broadcast.
> 127.0.0.1 sent an invalid ICMP error to a broadcast.
> 127.0.0.1 sent an invalid ICMP error to a broadcast.
>
> Only one of these happened on boot. The rest randomly pop up over time.
> I'm going to try tcpdumping lo to see if I can work out what's causing
> them.
Robert Love
next prev parent reply other threads:[~2002-01-22 10:08 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-22 6:48 2.4.18pre4aa1 Andrea Arcangeli
2002-01-22 6:58 ` 2.4.18pre4aa1 Robert Love
2002-01-22 7:37 ` 2.4.18pre4aa1 Dan Chen
2002-01-22 7:43 ` 2.4.18pre4aa1 Robert Love
2002-01-22 10:02 ` 2.4.18pre4aa1 Russell King
2002-01-22 10:12 ` Robert Love [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-24 5:23 2.4.18pre4aa1 rwhron
2002-01-24 6:27 ` 2.4.18pre4aa1 Daniel Phillips
2002-01-25 0:09 ` 2.4.18pre4aa1 Andrea Arcangeli
2002-01-28 9:53 ` 2.4.18pre4aa1 Daniel Phillips
2002-01-28 15:29 ` 2.4.18pre4aa1 Andrea Arcangeli
2002-01-28 20:28 ` 2.4.18pre4aa1 Daniel Phillips
2002-01-28 23:40 ` 2.4.18pre4aa1 Andrea Arcangeli
2002-01-29 0:15 ` 2.4.18pre4aa1 Daniel Phillips
2002-01-29 13:05 ` 2.4.18pre4aa1 Pavel Machek
2002-01-25 0:19 ` 2.4.18pre4aa1 rwhron
2002-01-25 0:29 ` 2.4.18pre4aa1 Rik van Riel
2002-01-25 3:23 ` 2.4.18pre4aa1 rwhron
2002-01-25 3:35 ` 2.4.18pre4aa1 Rik van Riel
2002-01-25 4:56 ` 2.4.18pre4aa1 rwhron
2002-01-25 4:57 ` 2.4.18pre4aa1 Rik van Riel
2002-01-25 5:18 ` 2.4.18pre4aa1 David Weinehall
2002-01-25 17:03 ` 2.4.18pre4aa1 Rik van Riel
2002-01-25 17:29 ` 2.4.18pre4aa1 Dave Jones
2002-01-25 12:26 ` 2.4.18pre4aa1 Dave Jones
2002-01-25 14:57 ` 2.4.18pre4aa1 rwhron
2002-01-28 0:37 ` 2.4.18pre4aa1 Andrea Arcangeli
2002-01-25 0:11 ` 2.4.18pre4aa1 Andrea Arcangeli
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=1011694349.850.658.camel@phantasy \
--to=rml@tech9.net \
--cc=andrea@suse.de \
--cc=crimsun@email.unc.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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.