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 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 ? > > [...] > > > mobile ~ # cat /sys/class/net/eth1/carrier > > cat: /sys/class/net/eth1/carrier: Invalid argument > > ---------- > > mobile src # rtl8139-diag -mm > > rtl8139-diag.c:v2.11 4/22/2003 Donald Becker ([EMAIL PROTECTED]) > > http://www.scyld.com/diag/index.html > > Index #1: Found a RealTek RTL8139 adapter at 0x4000. > > Realtek station address 00:00:f0:92:f7:5f, chip type 'rtl8139C+'. > > ^^^^^^^^^ > Can you send a lspci -vx ? 0000:02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) Subsystem: Samsung Electronics Co Ltd: Unknown device c00c Flags: bus master, medium devsel, latency 64, IRQ 5 I/O ports at 4000 [size=256] Memory at d0201800 (32-bit, non-prefetchable) [size=256] Capabilities: [50] Power Management version 2 00: ec 10 39 81 07 01 90 02 10 00 00 02 00 40 00 00 10: 01 40 00 00 00 18 20 d0 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 4d 14 0c c0 30: 00 00 00 00 50 00 00 00 00 00 00 00 05 01 20 40 > If it really is a 8139C+, you could use the 8139cp instead. Doesn't seem so: 8139cp: 10/100 PCI Ethernet driver v1.2 (Mar 22, 2004) 8139cp: pci dev 0000:02:00.0 (id 10ec:8139 rev 10) is not an 8139C+ compatible chip 8139cp: Try the "8139too" driver instead. > > 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). As 8139cp doesn't work for me, I can't test it. But anyway looks like the same effects. Can someone have a look at 8139too and say if the fix applies to it? > (please upgrade to 2.6.14-rc4 kernel while you are at it) I think you mean 2.6.16-rc4? I have a very patched kernel and somehow working suspend, so I would like to wait a little until some real enhancements come with an upgrade ... Thanks, Nikolaus - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
