Re: no carrier detection after resume from swsusp (8139too)

netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed

* Re: no carrier detection after resume from swsusp (8139too)
       [not found] ` <20060221234947.GA29806@electric-eye.fr.zoreil.com>
@ 2006-02-22 15:12   ` Nikolaus Filus
  2006-02-22 15:19     ` Robert Love
  0 siblings, 1 reply; 3+ messages in thread
From: Nikolaus Filus @ 2006-02-22 15:12 UTC (permalink / raw)
  To: netdev; +Cc: networkmanager-list, Francois Romieu

Cc: networkamanger-list, as it seems now to be related to nm

On Wednesday 22 February 2006 00:49, Francois Romieu wrote:
> (owner of http://bugzilla.kernel.org/show_bug.cgi?id=5681 Cc:ed)
>
> Nikolaus Filus <nfilus@gmx.net> :
> [...]
>
> > I'm using linux 2.6.14.3 with swsusp2 2.2rc14 (not the most new
> > ones). Since I'm using NetworkManager, which switches and manages my
> > wired and wireless devices, I have to reload 8139too after resume,
> > before plugin events of wired network are recognized. Some other
> > users of NM are reporting similar problems.
>
> May I assume that your 8139too device does not need to be reloaded when
> you suspend/resume and NM is not used ?

I didn't look enough on this issue before.

After resume, I get "invalid argument" from
/sys/class/net/eth1/carrier. Reloading the driver *OR* restarting
networkmanager solves the problem! Is it possible a process like nm blocks 
some ressources, which are re-initialised by reloading the driver or 
restarting nm? Notice, that just stopping nm is not enough.

Thanks in advance,

Nikolaus

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: no carrier detection after resume from swsusp (8139too)
  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
  0 siblings, 1 reply; 3+ messages in thread
From: Robert Love @ 2006-02-22 15:19 UTC (permalink / raw)
  To: Nikolaus Filus; +Cc: netdev, networkmanager-list, Francois Romieu

On Wed, 2006-02-22 at 16:12 +0100, Nikolaus Filus wrote:

> I didn't look enough on this issue before.
> 
> After resume, I get "invalid argument" from
> /sys/class/net/eth1/carrier. Reloading the driver *OR* restarting
> networkmanager solves the problem! Is it possible a process like nm blocks 
> some ressources, which are re-initialised by reloading the driver or 
> restarting nm? Notice, that just stopping nm is not enough.
> 
> Thanks in advance,

e100 or e1000?

`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?

	Robert Love

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: no carrier detection after resume from swsusp (8139too)
  2006-02-22 15:19     ` Robert Love
@ 2006-02-23  9:20       ` Will Stephenson
  0 siblings, 0 replies; 3+ messages in thread
From: Will Stephenson @ 2006-02-23  9:20 UTC (permalink / raw)
  To: networkmanager-list, James Ettle; +Cc: netdev, Francois Romieu

[-- 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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2006-02-23  9:20 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [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 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).