Re: Network Messed After Resume

[fra-dlap-no-spam@tourde.org (François TOURDE)]

Le 12915ième jour après Epoch,
Goran Ristic écrivait:

> Hi Michael!

Hi both...

> On Wed, 11 May 2005, Michael Perry wrote:
>
>>I have /etc/network/interfaces kinda tricked out so I can have support for
>>different locations wireless requirements.  I just do a "ifdown eth1" and
>>then I do a "ifup eth1=home".  Sometimes, the ipw2200 driver is in a state
>
> I use "ifsheme" for different locations. - Normally after a resume hotplug
> starts uploading the needed firmware. Changes can be made by "ifsheme any"
> "ifsheme home" ...
>
>>of funk and it requires more manual intervention so I remove it and
>>re-insert it and it comes back.  This is with apm, BTW.  My laptop will
>>not talk acpi.
>
> As I said: sometimes. :)

I'm on the same situation. My Dell Latitude C840 with Prism54 Wifi
card is sometimes unable to restart correctly the driver. rmmod and
modprobe aren't my friends :(

On resume, I have following messages on kern.log:

May 12 09:35:58 fermat kernel: eth1: timeout waiting for mgmt response 1000, triggering device
May 12 09:35:59 fermat kernel: eth1: timeout waiting for mgmt response 900, triggering device
May 12 09:35:59 fermat kernel: eth1: timeout waiting for mgmt response 800, triggering device
...
May 12 09:36:02 fermat kernel: eth1: mgmt tx queue is still full
May 12 09:36:28 fermat last message repeated 103 times
May 12 09:36:29 fermat kernel: eth1: mgmt tx queue is still full
May 12 09:37:00 fermat last message repeated 106 times
May 12 09:38:01 fermat last message repeated 216 times
May 12 09:39:02 fermat last message repeated 216 times
May 12 09:39:43 fermat last message repeated 146 times
May 12 09:39:43 fermat kernel: NETDEV WATCHDOG: eth1: transmit timed out
...
May 12 09:39:48 fermat kernel: eth1: interface reset failure
May 12 09:39:48 fermat kernel: prism54: Your card/socket may be faulty, or IRQ line too busy :(

Then, no more wifi... Only reboot is helpfull :(

I suppose it's a wifi card power management problem, but I don't know
how to resolve this problem.

Some infos:

fermat:~# uname -a
Linux fermat 2.6.10-1-686 #1 Sun Jan 9 01:40:18 EST 2005 i686 GNU/Linux

May 12 10:19:30 fermat kernel: eth1: firmware version: 1.0.4.3

0000:02:03.0 Network controller: Intersil Corporation Intersil ISL3890 [Prism GT/Prism Duette] (rev 01)
	Subsystem: Unknown device 17cf:0014
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 80 (2500ns min, 7000ns max), Cache Line Size: 0x20 (128 bytes)
	Interrupt: pin A routed to IRQ 11
	Region 0: Memory at f8ffc000 (32-bit, non-prefetchable) [size=8K]
	Capabilities: [dc] Power Management version 1
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-


> Maybe it is better to use one of the tools, which do this automatically?
> Don't know, if they do better?

I'm using whereami and ifplugd for suspend/resume and location
detection... It works fine for me... when prism54 is running ;)