* pcnet_cs problems in ARM handheld
@ 2005-04-11 16:22 rafael2k
2005-04-11 19:57 ` Russell King
0 siblings, 1 reply; 2+ messages in thread
From: rafael2k @ 2005-04-11 16:22 UTC (permalink / raw)
To: dahinds, linux-kernel
[-- Attachment #1: Type: text/plain, Size: 1918 bytes --]
Hi David and others kernel developers,
Thanx for your pcnet_cs driver! I use it since old days :-P
I bought a IC-CARD+ pcnet_cs compatible pcmcia nic, and i'm using it on a
StrongARM HP Jornada 710. My kernel is a 2.4.18-rmk3-hh10 and my pcmcia-cs
version is 3.1.33
From dmesg I got this messages:
--
jornada720_pcmcia_configure_socket(): config socket 0 vcc 50 vpp 0
jornada720_pcmcia_configure_socket(): config socket 0 vcc 50 vpp 0
eth0: NE2000 Compatible: io 0xc2800300, irq 114, hw_addr 00:80:C8:88:00:56
eth0: interrupt(s) dropped!
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Tx timed out, lost interrupt? TSR=0x3, ISR=0x96, t=39.
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Tx timed out, lost interrupt? TSR=0x3, ISR=0x3, t=55.
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Tx timed out, lost interrupt? TSR=0x3, ISR=0x3, t=49.
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Tx timed out, lost interrupt? TSR=0x3, ISR=0x3, t=88.
eth0: interrupt(s) dropped!
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Tx timed out, lost interrupt? TSR=0x3, ISR=0x3, t=77.
--
Any suggestions?
I tried to change some values in pcnet_cs.c:
INT_MODULE_PARM(use_big_buf, 1); /* i tried 0 */
INT_MODULE_PARM(delay_output, 0); /* I tried 1 */
INT_MODULE_PARM(delay_time, 4); /* I tried 6 */
but no change helped...
bye,
rafael diniz
--
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
Engenharia da Computação -- Unicamp
Radio Muda, radiolivre.org, Centro de Mídia Independente, SubMídia, GPSL
Chave PGP: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x2FF86098
-> orkut sucks, e naum estou nessa porcaria <-
"Acreditar que um conhecimento pode ser vendido ou
comprado é uma forma sutil (e cruel) de perpetuar a ignorância."
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: pcnet_cs problems in ARM handheld
2005-04-11 16:22 pcnet_cs problems in ARM handheld rafael2k
@ 2005-04-11 19:57 ` Russell King
0 siblings, 0 replies; 2+ messages in thread
From: Russell King @ 2005-04-11 19:57 UTC (permalink / raw)
To: rafael2k; +Cc: dahinds, linux-kernel
On Mon, Apr 11, 2005 at 04:22:52PM +0000, rafael2k wrote:
> Hi David and others kernel developers,
> Thanx for your pcnet_cs driver! I use it since old days :-P
>
> I bought a IC-CARD+ pcnet_cs compatible pcmcia nic, and i'm using it on a
> StrongARM HP Jornada 710. My kernel is a 2.4.18-rmk3-hh10 and my pcmcia-cs
> version is 3.1.33
>
> From dmesg I got this messages:
>
> --
> jornada720_pcmcia_configure_socket(): config socket 0 vcc 50 vpp 0
> jornada720_pcmcia_configure_socket(): config socket 0 vcc 50 vpp 0
> eth0: NE2000 Compatible: io 0xc2800300, irq 114, hw_addr 00:80:C8:88:00:56
> eth0: interrupt(s) dropped!
> NETDEV WATCHDOG: eth0: transmit timed out
> eth0: Tx timed out, lost interrupt? TSR=0x3, ISR=0x96, t=39.
> NETDEV WATCHDOG: eth0: transmit timed out
> eth0: Tx timed out, lost interrupt? TSR=0x3, ISR=0x3, t=55.
> NETDEV WATCHDOG: eth0: transmit timed out
> eth0: Tx timed out, lost interrupt? TSR=0x3, ISR=0x3, t=49.
> NETDEV WATCHDOG: eth0: transmit timed out
> eth0: Tx timed out, lost interrupt? TSR=0x3, ISR=0x3, t=88.
> eth0: interrupt(s) dropped!
> NETDEV WATCHDOG: eth0: transmit timed out
> eth0: Tx timed out, lost interrupt? TSR=0x3, ISR=0x3, t=77.
This looks like a case of the old 2.4 interrupt handling problems
which got resolved by rewriting the ARM interrupt handling
infrastructure during 2.5.
The problem occurs because of the need to handle edge-triggered
interrupts (as is the case with Intel CPUs) differently from
level-triggered interrupts, especially when the peripherals are
designed to be used with level-triggered inputs.
In effect, you can end up with the situation where the device has
its interrupt asserted, but because the CPU doesn't see a change
of state, it "forgets" about the interrupt input.
I'm not aware of a solution for this problem with 2.4 kernels.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2005-04-11 19:58 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-04-11 16:22 pcnet_cs problems in ARM handheld rafael2k
2005-04-11 19:57 ` Russell King
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox