From: Valdis.Kletnieks@vt.edu
To: David Miller <davem@davemloft.net>
Cc: akpm@linux-foundation.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, shemminger@vyatta.com
Subject: Re: mmotm 2010-03-23 - IPv6 warnings...
Date: Fri, 26 Mar 2010 02:18:22 -0400 [thread overview]
Message-ID: <4161.1269584302@localhost> (raw)
In-Reply-To: Your message of "Thu, 25 Mar 2010 21:40:50 PDT." <20100325.214050.101816448.davem@davemloft.net>
[-- Attachment #1: Type: text/plain, Size: 1777 bytes --]
On Thu, 25 Mar 2010 21:40:50 PDT, David Miller said:
> From: Valdis.Kletnieks@vt.edu
> Date: Thu, 25 Mar 2010 12:45:30 -0400
>
> > On Wed, 24 Mar 2010 18:42:26 EDT, Andrew Morton said:
> >> On Wed, 24 Mar 2010 21:36:41 -0400 Valdis.Kletnieks@vt.edu wrote:
> >>
> >> > On Tue, 23 Mar 2010 15:34:59 PDT, akpm@linux-foundation.org said:
> >> > > The mm-of-the-moment snapshot 2010-03-23-15-34 has been uploaded to
> >> > >
> >> > > http://userweb.kernel.org/~akpm/mmotm/
> >> >
> >> > Seen in my dmesg. It may be relevant that I'm at home, and my IPv6
> >> > prefix arrives via a PPP VPN connection. This happened about 20-25 secon
ds
> >> > after I launched pppd.
> >>
> >> Yes, thanks, I get the same - it doesn't seem to break anything. It
> >> also happens some time after boot has completed.
> >
> > Just doing an 'ifup eth0' on a network with IPv6 on it is sufficient.
>
> I just checked the following into net-next-2.6 which should at least
> kill that dmesg log.
>
> If you still are missing your ipv6 addresses, let me know how
> they normally get added, maybe that's enough to let me figure
> it out.
Confirming looks like a good fix - no cruft in dmesg, and I have ipv6 addresses:
% ifconfig ppp0
ppp0 Link encap:Point-to-Point Protocol
inet addr:128.173.34.103 P-t-P:128.173.32.21 Mask:255.255.255.255
inet6 addr: 2001:468:c80:3b04:105d:a65c:28c4:75d1/64 Scope:Global
inet6 addr: fe80::105d:a65c:28c4:75d1/10 Scope:Link
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1460 Metric:1
RX packets:79 errors:0 dropped:0 overruns:0 frame:0
TX packets:85 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:30943 (30.2 KiB) TX bytes:6746 (6.5 KiB)
[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2010-03-26 6:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201003232301.o2NN1bms031050@imap1.linux-foundation.org>
2010-03-25 1:36 ` mmotm 2010-03-23 - IPv6 warnings Valdis.Kletnieks
2010-03-24 22:42 ` Andrew Morton
2010-03-25 16:45 ` Valdis.Kletnieks
2010-03-25 20:25 ` David Miller
2010-03-26 4:40 ` David Miller
2010-03-26 6:18 ` Valdis.Kletnieks [this message]
2010-03-26 6:23 ` David Miller
2010-03-28 3:32 ` Stephen Hemminger
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=4161.1269584302@localhost \
--to=valdis.kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).