[vortex] Wont wake up after suspend with 2.4.7 (vortex_suspend?)

[Martin Vonwald]

Hi all!

I have _one_ machine with two setups:
* the old setup is running kernel 2.2.14 (Suse 6.3)
* the new setup is running kernel 2.4.7 (Suse 7.2)

This machine runs pretty all the time and suspends itself via "apm -s" if 
no other machine is connected (smb+nfs). When some other machine accesses 
the network it should wake up on its own - and it does exactly that running 
2.2.14 and it completely fails running 2.4.7 (both using the driver 3c90x 
from the kernel of the distro)

When the the machine (2.4.7) goes into suspend and after that resumes 
(manually!) I see the following messages in /var/log/messages:
---------
Oct 30 07:56:12 Heraklith apmd[564]: Version 3.0final (APM BIOS 1.2, Linux 
driver 1.14)
Oct 30 07:56:13 Heraklith apmd[564]: Charge: * * * (-1% unknown)
Oct 30 07:56:14 Heraklith kernel: vortex_suspend(eth0)
Oct 30 07:56:15 Heraklith apmd[564]: User Suspend
Oct 30 07:56:27 Heraklith kernel: vortex_resume(eth0)
Oct 30 07:56:27 Heraklith kernel: eth0: using NWAY device table, not 8
Oct 30 07:56:28 Heraklith apmd[564]: Normal Resume after 00:00:13 (-1% 
unknown) AC power
---------

The network card is a 3com 905B running in both setups with interrupt 10. 
This interrupt is also enabled in the Bios to wake up the machine.

What makes me a little suspicious is that "vortex_suspend(eth0)" message: 
does that mean the card is completely disabled? And if so, is also the 
interrupt disabled? This would explain this behaviour (I think...).

I would be very thankful if anybody can explain me that message and if there 
are some connections to apm. 
(I'm getting pretty desprated now - even think about downgrading to kernel 
2.2.x again)

Many thanks in advance for any tips/suggestions/comments,
Martin