netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Will Stephenson <wstephenson@kde.org>
To: networkmanager-list@gnome.org, James Ettle <jhe@phys.soton.ac.uk>
Cc: netdev@vger.kernel.org, Francois Romieu <romieu@fr.zoreil.com>
Subject: Re: no carrier detection after resume from swsusp (8139too)
Date: Thu, 23 Feb 2006 10:20:51 +0100	[thread overview]
Message-ID: <200602231020.52298.wstephenson@kde.org> (raw)
In-Reply-To: <1140621599.6269.10.camel@betsy.boston.ximian.com>

[-- Attachment #1: Type: text/plain, Size: 962 bytes --]

On Wednesday 22 February 2006 16:19, Robert Love wrote:
> e100 or e1000?

8139cp here.  Seems to have picked up this behaviour since SL10.1beta2 or so, 
still in beta4.

See https://bugzilla.novell.com/show_bug.cgi?id=151892

> `carrier' returns EINVAL if the device is not UP.  It might be a bug in
> NM if the device is not UP after a resume.  What does `ifconfig eth1`
> show before and after a resume?

carrier is 1 before and after, eth0 is UP before and after, restarting NM 
doesn't help, nor does stopping NM, rmmod, modprobe, and starting NM.  

I didn't think it is NM related, as I could not configure the network by hand 
after resume.   However, I just switched my network config to SUSE 
traditional ifup+ifplugd (joys of flexibility), and although eth0 does not 
work on resume, rcnetwork restart fixes it, whereas when NM is in charge, 
this does not help.  So my understanding is NM is not the direct cause but is 
a contributing factor.

Will


[-- Attachment #2: ifconfig.after.resume --]
[-- Type: text/plain, Size: 1312 bytes --]

eth0      Link encap:Ethernet  HWaddr 00:02:3F:67:0A:E3  
          inet addr:169.254.137.164  Bcast:169.254.255.255  Mask:255.255.0.0
          inet6 addr: fe80::202:3fff:fe67:ae3/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2769 errors:0 dropped:3144 overruns:0 frame:0
          TX packets:180 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:285833 (279.1 Kb)  TX bytes:14752 (14.4 Kb)
          Interrupt:10 Base address:0x2000 

eth1      Link encap:Ethernet  HWaddr 00:0C:F1:13:76:CB  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:5 Memory:90000000-90000fff 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:277 errors:0 dropped:0 overruns:0 frame:0
          TX packets:277 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:21838 (21.3 Kb)  TX bytes:21838 (21.3 Kb)


[-- Attachment #3: ifconfig.before.suspend --]
[-- Type: text/plain, Size: 1378 bytes --]

eth0      Link encap:Ethernet  HWaddr 00:02:3F:67:0A:E3  
          inet addr:10.10.101.143  Bcast:10.10.255.255  Mask:255.255.0.0
          inet6 addr: 2001:780:101:a00:202:3fff:fe67:ae3/64 Scope:Global
          inet6 addr: fe80::202:3fff:fe67:ae3/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2210 errors:0 dropped:0 overruns:0 frame:0
          TX packets:177 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:251842 (245.9 Kb)  TX bytes:14494 (14.1 Kb)
          Interrupt:10 Base address:0x2000 

eth1      Link encap:Ethernet  HWaddr 00:0C:F1:13:76:CB  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:5 Memory:90000000-90000fff 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:149 errors:0 dropped:0 overruns:0 frame:0
          TX packets:149 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:12784 (12.4 Kb)  TX bytes:12784 (12.4 Kb)


[-- Attachment #4: Type: text/plain, Size: 170 bytes --]

_______________________________________________
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

      reply	other threads:[~2006-02-23  9:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200602212312.23903.nfilus@gmx.net>
     [not found] ` <20060221234947.GA29806@electric-eye.fr.zoreil.com>
2006-02-22 15:12   ` no carrier detection after resume from swsusp (8139too) Nikolaus Filus
2006-02-22 15:19     ` Robert Love
2006-02-23  9:20       ` Will Stephenson [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=200602231020.52298.wstephenson@kde.org \
    --to=wstephenson@kde.org \
    --cc=jhe@phys.soton.ac.uk \
    --cc=netdev@vger.kernel.org \
    --cc=networkmanager-list@gnome.org \
    --cc=romieu@fr.zoreil.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).