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

* 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