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

2006-02-23 Thread Will Stephenson
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

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

2006-02-22 Thread Robert Love
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 >

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

2006-02-22 Thread Nikolaus Filus
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 <[EMAIL PROTECTED]> : > [...] > > > I'm using linux 2.6.14.3 with swsusp2 2.2rc14 (not the

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

2006-02-22 Thread Pierre Ossman
Francois Romieu wrote: > > http://bugzilla.kernel.org/show_bug.cgi?id=5681 suggests that > suspend/resume support is broken in 8139cp but I have some > code to test (see above). > Seems to solve the problem. Good work! :) Once this gets merged then Andrew should drop the hack that's in -mm. R

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

2006-02-22 Thread Nikolaus Filus
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 <[EMAIL PROTECTED]> : > [...] > > > I'm using linux 2.6.14.3 with swsusp2 2.2rc14 (not the most new > > ones). Since I'm using NetworkManager, which switc

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

2006-02-21 Thread Francois Romieu
(owner of http://bugzilla.kernel.org/show_bug.cgi?id=5681 Cc:ed) Nikolaus Filus <[EMAIL PROTECTED]> : [...] > 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 8139t

no carrier detection after resume from swsusp (8139too)

2006-02-21 Thread Nikolaus Filus
Hi, 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