RE: Problem with Via Rhine- Kernel 2.4.18

RE: Problem with Via Rhine- Kernel 2.4.18

[O'Riordan, Kevin]

That's the exact same problem I'm having with my VT6102 chip, and apparently
people are having with the VT86C100A. Roger Luethi posted a few patches back
in May which fixed the problem and a new patch just a few days ago against
2.4.19-rc1(and against 2.4.19-rc2 as well I'd say as the via-rhine driver
hasn't changed between them). I'll forward that mail on to you.

-----Original Message-----
From: Joseph Wenninger [mailto:kernel@jowenn.at] 
Sent: 17 July 2002 09:35
To: linux-kernel@vger.kernel.org
Subject: Problem with Via Rhine- Kernel 2.4.18

Hi 
 
I'm new to the linux kernel, so please be patient. 
 
I have a P4 notebook with a via chipset and a mobile P4. In Windows XP my 
built in network device works without problems. In linux the device hangs a 
after some time of >90kB/s datatransfers. I have to completely reset my 
notebook to get it working again 
 
I'm not sure if it is a hardware or a kernel problem. How can I debug this 
to find out if it is a kernel bug and where it is ? 
 
I have to use pci=biosirq, otherwise the kernel warns me, that it can't 
change the interupts for my devcies. 
 
 
At bootup the device identifies itself as  
via-rhine.c:v1.10-LK1.1.13  Nov-17-2001  Written by Donald Becker 
  http://www.scyld.com/network/via-rhine.html 
eth0: VIA VT6102 Rhine-II at 0xd000, 00:40:45:07:ba:06, IRQ 11. 
eth0: MII PHY found at address 1, status 0x786d advertising 05e1 Link 0021. 
 
When it stops working I get a lot of messages like: 
kernel eth0: Transmit timed out, status 0000, PHY status 786d, resetting... 
kernel eth0: Reset did not  complete in 10ms. 
 
Another message I quite often get is: 
mtrr: no more MTRRs available 
 
 
I'm thankfull for any help 
 
Kind regards 
Joseph Wenninger 

Re: Problem with Via Rhine- Kernel 2.4.18

[Roger Luethi]

> in May which fixed the problem and a new patch just a few days ago against
> 2.4.19-rc1(and against 2.4.19-rc2 as well I'd say as the via-rhine driver

Actually, the patch is against Jeff's public tree, which is somewhat
different from what's in rc1, against which I guess the patch will succeed
with offsets (rejecting the changelog portion, which is okay).

You can also try the ac kernel. Alan has the Rhine changes merged since
2.4.19-rc1-ac6.

Roger

RE: Problem with Via Rhine- Kernel 2.4.18

[O'Riordan, Kevin]

Tried it against 2.4.19-rc1, and it worked fine for me. Came up with one
hunk failed, but that was in the comments section at the beginning so didn't
matter, the rest of the hunks succeeded at offsets.

-----Original Message-----
From: Roger Luethi [mailto:rl@hellgate.ch] 
Sent: 17 July 2002 15:35
To: O'Riordan, Kevin
Cc: 'Joseph Wenninger'; linux-kernel@vger.kernel.org
Subject: Re: Problem with Via Rhine- Kernel 2.4.18

> in May which fixed the problem and a new patch just a few days ago against
> 2.4.19-rc1(and against 2.4.19-rc2 as well I'd say as the via-rhine driver

Actually, the patch is against Jeff's public tree, which is somewhat
different from what's in rc1, against which I guess the patch will succeed
with offsets (rejecting the changelog portion, which is okay).

You can also try the ac kernel. Alan has the Rhine changes merged since
2.4.19-rc1-ac6.

Roger

Problem with Via Rhine- Kernel 2.4.18

[Joseph Wenninger]

[-- Attachment #1: Type: text/plain, Size: 1216 bytes --]

Hi 
 
I'm new to the linux kernel, so please be patient. 
 
I have a P4 notebook with a via chipset and a mobile P4. In Windows XP my 
built in network device works without problems. In linux the device hangs a 
after some time of >90kB/s datatransfers. I have to completely reset my 
notebook to get it working again 
 
I'm not sure if it is a hardware or a kernel problem. How can I debug this 
to find out if it is a kernel bug and where it is ? 
 
I have to use pci=biosirq, otherwise the kernel warns me, that it can't 
change the interupts for my devcies. 
 
 
At bootup the device identifies itself as  
via-rhine.c:v1.10-LK1.1.13  Nov-17-2001  Written by Donald Becker 
  http://www.scyld.com/network/via-rhine.html 
eth0: VIA VT6102 Rhine-II at 0xd000, 00:40:45:07:ba:06, IRQ 11. 
eth0: MII PHY found at address 1, status 0x786d advertising 05e1 Link 0021. 
 
When it stops working I get a lot of messages like: 
kernel eth0: Transmit timed out, status 0000, PHY status 786d, resetting... 
kernel eth0: Reset did not  complete in 10ms. 
 
Another message I quite often get is: 
mtrr: no more MTRRs available 
 
 
I'm thankfull for any help 
 
Kind regards 
Joseph Wenninger