On Friday 26 August 2005 10:49, Jeff Garzik wrote:
> Denis Vlasenko wrote:
> > May be a known problem. A buglet in MII common code.
> > Via-rhine maintainer knows about it, as does Jeff.
>
> You don't speak for me, sir.
>
> I know of no such problem. Please submit a report and/or patch.
From:
On Fri, 26 Aug 2005 03:49:25 -0400, Jeff Garzik wrote:
> Denis Vlasenko wrote:
> >May be a known problem. A buglet in MII common code.
> >Via-rhine maintainer knows about it, as does Jeff.
>
> You don't speak for me, sir.
>
> I know of no such problem. Please submit a report and/or patch.
I
On Friday 26 August 2005 06:43, Patrick Draper wrote:
> On 8/23/05, Denis Vlasenko <[EMAIL PROTECTED]> wrote:
> > >Since it happens less than once a day, why not just add a code
> > >to reset the NIC completely in this case, like it is
> > >typically done in tx_timeout handlers of many NICs, and
On Friday 26 August 2005 06:43, Patrick Draper wrote:
On 8/23/05, Denis Vlasenko [EMAIL PROTECTED] wrote:
Since it happens less than once a day, why not just add a code
to reset the NIC completely in this case, like it is
typically done in tx_timeout handlers of many NICs, and forget about
On Friday 26 August 2005 10:49, Jeff Garzik wrote:
Denis Vlasenko wrote:
May be a known problem. A buglet in MII common code.
Via-rhine maintainer knows about it, as does Jeff.
You don't speak for me, sir.
I know of no such problem. Please submit a report and/or patch.
From: Denis
On Wed, 2005-08-24 at 11:50 -0400, Lee Revell wrote:
> On Tue, 2005-08-23 at 12:21 +0300, Denis Vlasenko wrote:
> > My suggestion was, and still is:
Never mind, I misread the original post. This workaround is probably OK
if you only do the reset when this error condition arises.
Lee
-
To
On Tue, 2005-08-23 at 12:21 +0300, Denis Vlasenko wrote:
> My suggestion was, and still is:
>
> >Since it happens less than once a day, why not just add a code
> >to reset the NIC completely in this case, like it is
> >typically done in tx_timeout handlers of many NICs, and forget about
> it?
>
On Tue, 2005-08-23 at 12:21 +0300, Denis Vlasenko wrote:
My suggestion was, and still is:
Since it happens less than once a day, why not just add a code
to reset the NIC completely in this case, like it is
typically done in tx_timeout handlers of many NICs, and forget about
it?
Do you
On Wed, 2005-08-24 at 11:50 -0400, Lee Revell wrote:
On Tue, 2005-08-23 at 12:21 +0300, Denis Vlasenko wrote:
My suggestion was, and still is:
Never mind, I misread the original post. This workaround is probably OK
if you only do the reset when this error condition arises.
Lee
-
To
[CCing maintaner]
On Monday 22 August 2005 20:29, Udo van den Heuvel wrote:
> Hello,
>
> It appears that the VIA Rhine chipset has some sort of bug which shows
> up in both the standard Linux VIA-Rhine driver and the Rhinefet driver
> that VIA itself provides.
>
> The difference is that the
[CCing maintaner]
On Monday 22 August 2005 20:29, Udo van den Heuvel wrote:
Hello,
It appears that the VIA Rhine chipset has some sort of bug which shows
up in both the standard Linux VIA-Rhine driver and the Rhinefet driver
that VIA itself provides.
The difference is that the connection
Hello,
It appears that the VIA Rhine chipset has some sort of bug which shows
up in both the standard Linux VIA-Rhine driver and the Rhinefet driver
that VIA itself provides.
The difference is that the connection is dropped in case of the standard
Linux driver for VIA Rhine but that the
Hello,
It appears that the VIA Rhine chipset has some sort of bug which shows
up in both the standard Linux VIA-Rhine driver and the Rhinefet driver
that VIA itself provides.
The difference is that the connection is dropped in case of the standard
Linux driver for VIA Rhine but that the
On Sunday 07 August 2005 21:02, Udo van den Heuvel wrote:
> Hello,
>
> In january of this year I mentioned a problem with the Linux kernel
> driver for VIA Rhine ethernet chips. (see http://lkml.org/lkml/2005/1/15/47)
> In the mean time this bug was reproduced quite a number of times on my
>
On Sunday 07 August 2005 21:02, Udo van den Heuvel wrote:
Hello,
In january of this year I mentioned a problem with the Linux kernel
driver for VIA Rhine ethernet chips. (see http://lkml.org/lkml/2005/1/15/47)
In the mean time this bug was reproduced quite a number of times on my
Fedora
Hello,
In january of this year I mentioned a problem with the Linux kernel
driver for VIA Rhine ethernet chips. (see http://lkml.org/lkml/2005/1/15/47)
In the mean time this bug was reproduced quite a number of times on my
Fedora Core 3 (then)/4 (now) box (a VIA CL6000).
An alternative driver by
Hello,
In january of this year I mentioned a problem with the Linux kernel
driver for VIA Rhine ethernet chips. (see http://lkml.org/lkml/2005/1/15/47)
In the mean time this bug was reproduced quite a number of times on my
Fedora Core 3 (then)/4 (now) box (a VIA CL6000).
An alternative driver by
Hello,
Did anyone make progress in the case of the VIA Rhine ethernet bug?
It gives messages like:
Apr 8 18:51:08 epia kernel: eth1: Oversized Ethernet frame spanned multiple
buffers, entry 0x9 length 0 status 0600!
Apr 8 18:51:08 epia kernel: eth1: Oversized Ethernet frame cca77090 vs
Hello,
Did anyone make progress in the case of the VIA Rhine ethernet bug?
It gives messages like:
Apr 8 18:51:08 epia kernel: eth1: Oversized Ethernet frame spanned multiple
buffers, entry 0x9 length 0 status 0600!
Apr 8 18:51:08 epia kernel: eth1: Oversized Ethernet frame cca77090 vs
On Sat, 15 Jan 2005 12:43:33 +0100, Udo van den Heuvel <[EMAIL PROTECTED]>
wrote:
> Hello,
>
> On my firewall (VIA EPIA CL-6000 with VIA Rhine network chips running FC3
> and custom kernels) I see messages like:
>
> Jan 13 19:35:46 epia kernel: eth1: Oversized Ethernet frame spanned multiple
>
On Sat, 15 Jan 2005 12:43:33 +0100, Udo van den Heuvel [EMAIL PROTECTED]
wrote:
Hello,
On my firewall (VIA EPIA CL-6000 with VIA Rhine network chips running FC3
and custom kernels) I see messages like:
Jan 13 19:35:46 epia kernel: eth1: Oversized Ethernet frame spanned multiple
buffers,
Hello,
> -Original Message-
> From: Luc Saillard [mailto:[EMAIL PROTECTED]
> Sent: maandag 17 januari 2005 16:46
> To: Marcelo Tosatti
> Cc: Udo van den Heuvel; linux-kernel@vger.kernel.org
> Subject: Re: VIA Rhine ethernet driver bug
>
>
> On Mon, Jan 1
Hello,
-Original Message-
From: Luc Saillard [mailto:[EMAIL PROTECTED]
Sent: maandag 17 januari 2005 16:46
To: Marcelo Tosatti
Cc: Udo van den Heuvel; linux-kernel@vger.kernel.org
Subject: Re: VIA Rhine ethernet driver bug
On Mon, Jan 17, 2005 at 10:04:27AM -0200, Marcelo
On Mon, Jan 17, 2005 at 10:04:27AM -0200, Marcelo Tosatti wrote:
> On Sat, Jan 15, 2005 at 12:43:33PM +0100, Udo van den Heuvel wrote:
> > On my firewall (VIA EPIA CL-6000 with VIA Rhine network chips running FC3
> > and custom kernels) I see messages like:
>
> What kernel version are you using?
On Sat, Jan 15, 2005 at 12:43:33PM +0100, Udo van den Heuvel wrote:
> Hello,
>
> On my firewall (VIA EPIA CL-6000 with VIA Rhine network chips running FC3
> and custom kernels) I see messages like:
>
> Jan 13 19:35:46 epia kernel: eth1: Oversized Ethernet frame spanned multiple
> buffers, entry
On Sat, Jan 15, 2005 at 12:43:33PM +0100, Udo van den Heuvel wrote:
Hello,
On my firewall (VIA EPIA CL-6000 with VIA Rhine network chips running FC3
and custom kernels) I see messages like:
Jan 13 19:35:46 epia kernel: eth1: Oversized Ethernet frame spanned multiple
buffers, entry 0x4
On Mon, Jan 17, 2005 at 10:04:27AM -0200, Marcelo Tosatti wrote:
On Sat, Jan 15, 2005 at 12:43:33PM +0100, Udo van den Heuvel wrote:
On my firewall (VIA EPIA CL-6000 with VIA Rhine network chips running FC3
and custom kernels) I see messages like:
What kernel version are you using? Its
Hello,
On VIA-Rhine ethernet chips that give errors like:
Jan 13 19:35:46 epia kernel: eth1: Oversized Ethernet frame spanned multiple
buffers, entry 0x4 length 0 status 0600!
(for all 16 entries)
Setting the mtu to a lower value than 1500 appears to help (tested at 500,
and 1000 is in
Hello,
On VIA-Rhine ethernet chips that give errors like:
Jan 13 19:35:46 epia kernel: eth1: Oversized Ethernet frame spanned multiple
buffers, entry 0x4 length 0 status 0600!
(for all 16 entries)
Setting the mtu to a lower value than 1500 appears to help (tested at 500,
and 1000 is in
Hello,
On my firewall (VIA EPIA CL-6000 with VIA Rhine network chips running FC3
and custom kernels) I see messages like:
Jan 13 19:35:46 epia kernel: eth1: Oversized Ethernet frame spanned multiple
buffers, entry 0x4 length 0 status 0600!
Jan 13 19:35:46 epia kernel: eth1: Oversized
Hello,
On my firewall (VIA EPIA CL-6000 with VIA Rhine network chips running FC3
and custom kernels) I see messages like:
Jan 13 19:35:46 epia kernel: eth1: Oversized Ethernet frame spanned multiple
buffers, entry 0x4 length 0 status 0600!
Jan 13 19:35:46 epia kernel: eth1: Oversized
31 matches
Mail list logo
