Project Home
Project Home		 Wiki
Wiki		 Discussion Forums
Discussions		 Project Information
Project Info
Networking/Discussion/Networking Drivers/micrel ksz 8841-pmqli driver hangs at high data rates/List of Posts
Forum Topic - micrel ksz 8841-pmqli driver hangs at high data rates: (4 Items)
   
Update
Rainer Faulstich(deleted)
07/03/2012 12:11 PM
post93992
micrel ksz 8841-pmqli driver hangs at high data rates   
Our QNX (Version 6.3.0 SP2) Driver hangs up in an application running a micrel ksz 8841-pmqli 
in 10MBit simplex mode when much traffic is done.

Operating system:	QNX 6.3.0 SP2
			
Driver:			NAME=devn-micrel8841.so
			        DESCRIPTION=micrel8841 ethernet driver
			        DATE=2007/08/30-14:47:26-EDT
			       STATE=stable
			       HOST=worldbuild
			       USER=pspbuild
			       Version=630SP3-685
			       TAGID=1602

Opreating mode:     10MBit half duplex

Problem description: The data transfer stops at high data rates (for example at continuous text output
			          in a terminal window). Then Phindows closes the the socket.
			          If this problem occurs, no more ping is possible on this interface.

Observations:		The hardware produces still interupts and these interrupts are also still 
			         received by the kernel !
			         But the driver cannot resume the data transfer
			         An umount of the driver followed by a mount of the driver fixes the problem !
			         In other words: it is NO HARDWARE PROBLEM, but a driver problem.

			         If we start the driver using a verbose level < 0xA (less than 0xA), a singular output
                                 is  recorded 
                                 in  the  syslog.
			         If we start the driver using verbose level 0xA, also a singular output is recorded
                                 in the syslog, but data rate becomes much reduced, and the drivers does 
                                 not hang up.

The board architectural structure is as follows:

   =+===Cpu=============+=    ____ devn-e1000.so (en1)       ___
    |                   |                                                                                               
  \___ io-net (default)
    |                   |                                           __ devn-micrel8841.so  (en0) ___/
   =+=MEPME2============+=    _/                                                       ___ io-net (prefix /GMLRS)
                                                                    \__ devn-micrel8841.so  (en0) ___/

(The board MEPME2 contains two controllers of type micrell8841.)
Attachment: Text problem_description.txt 1.74 KB
Hugh Brown
07/04/2012 9:57 AM
post94020
Re: micrel ksz 8841-pmqli driver hangs at high data rates   
Here is the latest version of the driver for you to try.




On 12-07-03 12:11 PM, "Rainer Faulstich" <community-noreply@qnx.com> wrote:

>Our QNX (Version 6.3.0 SP2) Driver hangs up in an application running a
>micrel ksz 8841-pmqli
>in 10MBit simplex mode when much traffic is done.
>
>Operating system:	QNX 6.3.0 SP2
>			
>Driver:			NAME=devn-micrel8841.so
>			        DESCRIPTION=micrel8841 ethernet driver
>			        DATE=2007/08/30-14:47:26-EDT
>			       STATE=stable
>			       HOST=worldbuild
>			       USER=pspbuild
>			       Version=630SP3-685
>			       TAGID=1602
>
>Opreating mode:     10MBit half duplex
>
>Problem description: The data transfer stops at high data rates (for
>example at continuous text output
>			          in a terminal window). Then Phindows closes the the socket.
>			          If this problem occurs, no more ping is possible on this
>interface.
>
>Observations:		The hardware produces still interupts and these interrupts
>are also still 
>			         received by the kernel !
>			         But the driver cannot resume the data transfer
>			         An umount of the driver followed by a mount of the driver
>fixes the problem !
>			         In other words: it is NO HARDWARE PROBLEM, but a driver
>problem.
>
>			         If we start the driver using a verbose level < 0xA (less than
>0xA), a singular output
>                                 is  recorded
>                                 in  the  syslog.
>			         If we start the driver using verbose level 0xA, also a
>singular output is recorded
>                                 in the syslog, but data rate becomes
>much reduced, and the drivers does
>                                 not hang up.
>
>The board architectural structure is as follows:
>
>   =+===Cpu=============+=    ____ devn-e1000.so (en1)       ___
>    |                   |
>                                                \___ io-net (default)
>    |                   |                                           __
>devn-micrel8841.so  (en0) ___/
>   =+=MEPME2============+=    _/
>             ___ io-net (prefix /GMLRS)
>                                                                    \__
>devn-micrel8841.so  (en0) ___/
>
>(The board MEPME2 contains two controllers of type micrell8841.)
>
>
>
>_______________________________________________
>
>Networking Drivers
>http://community.qnx.com/sf/go/post93992
>To cancel your subscription to this discussion, please e-mail
>drivers-networking-unsubscribe@community.qnx.com
Attachment: Text devn-micrel8841.so 58.36 KB
Rainer Faulstich(deleted)
07/05/2012 5:58 AM
post94048
Re: micrel ksz 8841-pmqli driver hangs at high data rates   
Unfortunately also this driver you sent us behaves like that one we have in use. If we we login with a phindows window 
and move a window around the screen - and so produced a lot of traffic - after some time moving it the driver on the QNX
 target dies.


> Here is the latest version of the driver for you to try.
> 
> 
> 
> 
> On 12-07-03 12:11 PM, "Rainer Faulstich" <community-noreply@qnx.com> wrote:
> 
> >Our QNX (Version 6.3.0 SP2) Driver hangs up in an application running a
> >micrel ksz 8841-pmqli
> >in 10MBit simplex mode when much traffic is done.
> >
> >Operating system:	QNX 6.3.0 SP2
> >			
> >Driver:			NAME=devn-micrel8841.so
> >			        DESCRIPTION=micrel8841 ethernet driver
> >			        DATE=2007/08/30-14:47:26-EDT
> >			       STATE=stable
> >			       HOST=worldbuild
> >			       USER=pspbuild
> >			       Version=630SP3-685
> >			       TAGID=1602
> >
> >Opreating mode:     10MBit half duplex
> >
> >Problem description: The data transfer stops at high data rates (for
> >example at continuous text output
> >			          in a terminal window). Then Phindows closes the the socket.
> >			          If this problem occurs, no more ping is possible on this
> >interface.
> >
> >Observations:		The hardware produces still interupts and these interrupts
> >are also still 
> >			         received by the kernel !
> >			         But the driver cannot resume the data transfer
> >			         An umount of the driver followed by a mount of the driver
> >fixes the problem !
> >			         In other words: it is NO HARDWARE PROBLEM, but a driver
> >problem.
> >
> >			         If we start the driver using a verbose level < 0xA (less than
> >0xA), a singular 
> output
> >                                 is  recorded
> >                                 in  the  syslog.
> >			         If we start the driver using verbose level 0xA, also a
> >singular output is recorded
> >                                 in the syslog, but data rate becomes
> >much reduced, and the drivers does
> >                                 not hang up.
> >
> >The board architectural structure is as follows:
> >
> >   =+===Cpu=============+=    ____ devn-e1000.so (en1)       ___
> >    |                   |
> >                                                \___ io-net (default)
> >    |                   |                                           __
> >devn-micrel8841.so  (en0) ___/
> >   =+=MEPME2============+=    _/
> >             ___ io-net (prefix /GMLRS)
> >                                                                    \__
> >devn-micrel8841.so  (en0) ___/
> >
> >(The board MEPME2 contains two controllers of type micrell8841.)
> >
> >
> >
> >_______________________________________________
> >
> >Networking Drivers
> >http://community.qnx.com/sf/go/post93992
> >To cancel your subscription to this discussion, please e-mail
> >drivers-networking-unsubscribe@community.qnx.com
>
Hugh Brown
07/05/2012 7:40 AM
post94053
Re: micrel ksz 8841-pmqli driver hangs at high data rates   
I'll take a look at this when I have a chance.



On 12-07-05 5:58 AM, "Rainer Faulstich" <community-noreply@qnx.com> wrote:

>Unfortunately also this driver you sent us behaves like that one we have
>in use. If we we login with a phindows window and move a window around
>the screen - and so produced a lot of traffic - after some time moving it
>the driver on the QNX target dies.
>
>
>> Here is the latest version of the driver for you to try.
>> 
>> 
>> 
>> 
>> On 12-07-03 12:11 PM, "Rainer Faulstich" <community-noreply@qnx.com>
>>wrote:
>> 
>> >Our QNX (Version 6.3.0 SP2) Driver hangs up in an application running a
>> >micrel ksz 8841-pmqli
>> >in 10MBit simplex mode when much traffic is done.
>> >
>> >Operating system:	QNX 6.3.0 SP2
>> >			
>> >Driver:			NAME=devn-micrel8841.so
>> >			        DESCRIPTION=micrel8841 ethernet driver
>> >			        DATE=2007/08/30-14:47:26-EDT
>> >			       STATE=stable
>> >			       HOST=worldbuild
>> >			       USER=pspbuild
>> >			       Version=630SP3-685
>> >			       TAGID=1602
>> >
>> >Opreating mode:     10MBit half duplex
>> >
>> >Problem description: The data transfer stops at high data rates (for
>> >example at continuous text output
>> >			          in a terminal window). Then Phindows closes the the
>>socket.
>> >			          If this problem occurs, no more ping is possible on this
>> >interface.
>> >
>> >Observations:		The hardware produces still interupts and these
>>interrupts
>> >are also still 
>> >			         received by the kernel !
>> >			         But the driver cannot resume the data transfer
>> >			         An umount of the driver followed by a mount of the driver
>> >fixes the problem !
>> >			         In other words: it is NO HARDWARE PROBLEM, but a driver
>> >problem.
>> >
>> >			         If we start the driver using a verbose level < 0xA (less
>>than
>> >0xA), a singular
>> output
>> >                                 is  recorded
>> >                                 in  the  syslog.
>> >			         If we start the driver using verbose level 0xA, also a
>> >singular output is recorded
>> >                                 in the syslog, but data rate becomes
>> >much reduced, and the drivers does
>> >                                 not hang up.
>> >
>> >The board architectural structure is as follows:
>> >
>> >   =+===Cpu=============+=    ____ devn-e1000.so (en1)       ___
>> >    |                   |
>> >                                                \___ io-net (default)
>> >    |                   |                                           __
>> >devn-micrel8841.so  (en0) ___/
>> >   =+=MEPME2============+=    _/
>> >             ___ io-net (prefix /GMLRS)
>> >                                                                    \__
>> >devn-micrel8841.so  (en0) ___/
>> >
>> >(The board MEPME2 contains two controllers of type micrell8841.)
>> >
>> >
>> >
>> >_______________________________________________
>> >
>> >Networking Drivers
>> >http://community.qnx.com/sf/go/post93992
>> >To cancel your subscription to this discussion, please e-mail
>> >drivers-networking-unsubscribe@community.qnx.com
>>...

Return


  A subsidiary of BlackBerry             All content ©2004-2013, QNX Software Systems