pcnet driver problem in QNX 6.2.1

QNX Newsgroups (Archives) qdn.public.ddk.network
1

We’ve got a custom PC that uses an AMD PCNet chip.

Under QNX 6.1.0a, the network interface work fine under heavy loads.
Under QNX 6.2.1, the network quits working after a few minutes under the
same load.

In the release notes for QNX 6.2.0, it says this crashing is a known
issue. The problem was not mentioned in the 6.2.1 release notes.

Has anyone else experienced this problem with version 6.2.1?
Is there a fix in the works?
It’s a little late to pick a new ethernet chip.

Thanks,
Ben

2

What is the output from nicinfo when it stops working. Does either the
Tx or Rx count still continue to increment? The output from ‘pci -v’
would also help.

Previously, Ben Gardner wrote in qdn.public.ddk.network:

We’ve got a custom PC that uses an AMD PCNet chip.

Under QNX 6.1.0a, the network interface work fine under heavy loads.
Under QNX 6.2.1, the network quits working after a few minutes under the
same load.

In the release notes for QNX 6.2.0, it says this crashing is a known
issue. The problem was not mentioned in the 6.2.1 release notes.

Has anyone else experienced this problem with version 6.2.1?
Is there a fix in the works?
It’s a little late to pick a new ethernet chip.

Thanks,
Ben

3

Ben Gardner <bgardner@spam.wabtec.com> wrote:

We’ve got a custom PC that uses an AMD PCNet chip.

Under QNX 6.1.0a, the network interface work fine under heavy loads.
Under QNX 6.2.1, the network quits working after a few minutes under the
same load.

In the release notes for QNX 6.2.0, it says this crashing is a known
issue. The problem was not mentioned in the 6.2.1 release notes.

Has anyone else experienced this problem with version 6.2.1?
Is there a fix in the works?
It’s a little late to pick a new ethernet chip.

The 6.2.1 pcnet driver has a bug whereby it doesn’t work at 100Mbps.
(It could potentially fail at 10 also, but less likely).

This has been fixed in patch B.

Dave

4

Any idea when patch B will be available?
I have 6.2.1 PE, but I haven’t seen any patches in the ‘product updates’
area…

Thanks,
Ben

David Donohoe wrote:

The 6.2.1 pcnet driver has a bug whereby it doesn’t work at 100Mbps.
(It could potentially fail at 10 also, but less likely).

This has been fixed in patch B.

Dave

5

Is this related to the same buffer underflow problem that was in the ppc
PCNet driver at 6.1.0? The last time I had to deal with this chip, burst
transfers were turned off on the PCI interface of the chip and the transmit
was allowed to fall behind, causing the chip to stop reading the Tx
descriptors and stall the ethernet.
Is the PCNet driver source available? I seem to remember the network-ddk
had the PCNet driver as example code.

Paul

“Ben Gardner” <bgardner@spam.wabtec.com> wrote in message
news:be5dio$ptq$1@inn.qnx.com…

Any idea when patch B will be available?
I have 6.2.1 PE, but I haven’t seen any patches in the ‘product updates’
area…

Thanks,
Ben

David Donohoe wrote:
The 6.2.1 pcnet driver has a bug whereby it doesn’t work at 100Mbps.
(It could potentially fail at 10 also, but less likely).

This has been fixed in patch B.

Dave

6

Patch B is available for download through myQNX.

Regards,
Barry F.

Ben Gardner <bgardner@spam.wabtec.com> wrote in message
news:be5dio$ptq$1@inn.qnx.com…

Any idea when patch B will be available?
I have 6.2.1 PE, but I haven’t seen any patches in the ‘product updates’
area…

Thanks,
Ben

David Donohoe wrote:
The 6.2.1 pcnet driver has a bug whereby it doesn’t work at 100Mbps.
(It could potentially fail at 10 also, but less likely).

This has been fixed in patch B.

Dave

7

Thanks. I found it in the Beta section.

OS Support wrote:

Patch B is available for download through myQNX.

Regards,
Barry F.

Ben Gardner <> bgardner@spam.wabtec.com> > wrote in message
news:be5dio$ptq$> 1@inn.qnx.com> …

Any idea when patch B will be available?
I have 6.2.1 PE, but I haven’t seen any patches in the ‘product updates’
area…

Thanks,
Ben

David Donohoe wrote:

The 6.2.1 pcnet driver has a bug whereby it doesn’t work at 100Mbps.
(It could potentially fail at 10 also, but less likely).

This has been fixed in patch B.

Dave