netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: adi@drcomp.erfurt.thur.de (Adrian Knoth)
To: netdev@vger.kernel.org
Subject: No IPv6 addresses after resume (No buffer space available)
Date: Mon, 4 Feb 2008 14:16:15 +0100	[thread overview]
Message-ID: <20080204131615.GT11368@ltw.loris.tv> (raw)

Hi!

I use suspend-to-RAM on my HP nx6325 laptop. I have three main
locations:

   - place A: IPv4 + IPv6
   - place B: IPv4 + IPv6
   - place C: IPv4 only

Suspending in place A and travelling to place B is no problem, I'm
always getting the local RAs, the right addresses a.s.o.

But once I've been in place C (no IPv6 there at this site), resuming in
A or B doesn't give me IPv6, I don't even get a link local address. Only
the loopback interface is left functional:

adi@chopin:~$ ls /proc/sys/net/ipv6/conf/
all  default  eth1  lo

chopin:/home/adi# ip -6 a s
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 
    inet6 ::1/128 scope host 
           valid_lft forever preferred_lft forever

eth0 is missing, also in /proc/sys/net/ipv6/conf (as shown above).

When I try to assign my link local address, it fails:

chopin:/home/adi# ip -6 a a fe80::0217:a4ff:fed7:a23e/64 scope link dev eth0
RTNETLINK answers: No buffer space available

It doesn't help to cycle the interface down and up. My current
workaround is to unload the NIC driver (tg3) and modprobe it again: 

[rmmod tg3 ; modprobe tg3]
chopin:/home/adi# ip -6 a s
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
15: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000
    inet6 fe80::217:a4ff:fed7:a23e/64 scope link 
       valid_lft forever preferred_lft forever

[and a few moments later]
chopin:/home/adi# ip -6 a s
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
15: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000
    inet6 2001:638:906:2:217:a4ff:fed7:a23e/64 scope global dynamic 
       valid_lft 2591987sec preferred_lft 604787sec
    inet6 fe80::217:a4ff:fed7:a23e/64 scope link 
       valid_lft forever preferred_lft forever


Hope you can identify the culprit.


TIA,

Cheerio


-- 
mail: adi@thur.de  	http://adi.thur.de	PGP/GPG: key via keyserver

                 reply	other threads:[~2008-02-04 13:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20080204131615.GT11368@ltw.loris.tv \
    --to=adi@drcomp.erfurt.thur.de \
    --cc=netdev@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 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).