Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Ethernet renew time

5 views
Skip to first unread message

J�rgen Thoma�

unread,
Nov 20, 2009, 7:49:55 AM11/20/09
to
Hello.

I have post this questions some time ago but I have recived no answers.

I have a board with an iMX31 CPU and an SMSC Ethernet controller running
with
WinCE5.0.
Is it possible to change the time too detect the insertion of the ethernet
cable. In the actual configuration it takes about 10 sec too detect the
cable. When I press RENEW it takes less than 1 sec. Is there a registry key
for the scanning period or is it a driver problem.

Best regards

J�rgen


Paul G. Tobey [ eMVP ]

unread,
Nov 20, 2009, 10:00:05 AM11/20/09
to

I'd say 'driver problem' is the first to check. It's probably waiting to
make sure that the connection is not intermittent before it notifies the
network stack that the cable has been connected. If it's actually the
network stack causing the delay, I'm pretty sure there is no adjustable
setting to change how long the detection and address request process takes.

Paul T.

"Jürgen Thomaß" wrote:

> Jürgen
>
>
> .
>

J�rgen Thoma�

unread,
Nov 23, 2009, 8:41:55 AM11/23/09
to
Hello.

Here are the debugmsg:
After disconnect the cable following msg displayed:

0x87da0400: LanSetInterfaceLinkStatus(00172D30/001734A0) - 0 0
0x87da0400: SetInterfaceLinkStatus(IF 6) -> disconnected
0x87bca400: [NOTIFY] HandleSystemEvent 6 none
0x87c68950: NotifyChange: Setting Event 479FAB92
0x87a06828: TEL_IOControl(0x1E735DC, 17039424, 0x4D070, 2900, 0x0, 0, 0x0)
0x87a06828: FTP_IOControl(0x1, 17039424, 0x4D070, 2900, 0x0, 0, 0x0)

and then, after 10 sec the following msg displayed and the icon is changed
too disconnect:

0x87e3f4a8: +IPNotifyClientsIPEvent
0x87e3f4a8: IPNotifyClientsIPEvent: PendingIPGetIPEventRequest 398830
0x87e3f4a8: IPNotifyClientsIPEvent: SetEvent
0x87e3f4a8: IPNotifyClientsIPEvent: remove old
0x87e3f4a8: +Smsc9118SetInformation[0x1010103]
0x87e3f4a8: [NOTIFY] HandleSystemEvent 6 none
0x87e3f4a8: IPAddAddrComplete: IF 0 ntecount 0, SAC 0
0x87e3f4a8: +Smsc9118SetInformation[0xfd010104]
0x87e3f4a8: MaskSize=6
0x87e3f4a8: PatternOffset=30(0x1e)
0x87e3f4a8: PatternSize=42
0x87e3f4a8: +Smsc9118SetInformation[0xfd010104]
0x87e3f4a8: MaskSize=1
0x87e3f4a8: PatternOffset=25(0x19)
0x87e3f4a8: PatternSize=6
0x87e3f4a8: PatternSize is smaller than 13 bytes.
0x87e3f4a8: MaskSize is smaller than 2 bytes.
0x87e3f4a8: No pattern is removed.
0x87c47264: ************DHCP MEDIA STATUS************
0x87c47264: SeqNo: 2
0x87c47264: MediaStatus: 11025
0x87c47264: Context: 3 - 4
0x87c47264: AdapterName: SMSC91181
0x87c47264: Media Status is: IP_MEDIA_DISCONNECT
0x87e3f4a8: *TakeNetDown: pDhcp 0x39aab0 IP 3C01A8C0!
0x87e3f4a8: +AfdAddInterface(Adapter SMSC91181 Nte 0x1881D0 Context 3, Flags
1 IPAddr 3C01A8C0 cDns 0 cWins 0)
0x87e3f4a8: -AfdAddInterface: fRet: 1
0x87c47264: IPDispatchDeviceControl returned Status 103
0x87c68950: NotifyChange: Setting Event A792EAEA
0x87c68950: NotifyChange: Setting Event 27BB3CEA
0x87c68950: NotifyChange: Setting Event C79D2026
0x87c68950: NotifyChange: Setting Event 47A0EF76
0x87bca400: +RDR:NetBIOSNotifyFunc: Lana 1, flags: 0x2
0x87bca400: +RDR:NetDownIndication, lana: 1
0x87e3f4a8: +RDR:NetCleanupFunc: Lana:1
0x87e3f4a8: +RDR:UnbindFromNet, lana: 1
0x87e3f4a8: -RDR:StopBrowserOnNet: Browser not started on lana 1
0x87e3f4a8: -RDR:Stopped redir on lana 1
0x87bca400: -RDR:NetBIOSNotifyFunc: Lana 1
0x87ad77b4: IPv6Hlp:: +++ OnChangeInterfaceInfo +++
0x87bcaa40: -RDR:RdrUIThread exiting
0x87e3f4a8: +RDR:UnbindFromNetbiosTransport
0x87e3f4a8: -RDR:UnbindFromNetbiosTransport
0x87e3f4a8: -RDR:UnbindFromNet
0x87e3f4a8: -RDR:NetCleanupFunc: Lana:1
0x87ad77b4: Ipv6hlp:: Could not open registry key (COMM\ConnectionSharing)
0x87ad77b4: Ipv6hlp:: Could not open registry key (COMM\ConnectionSharing)
0x87ad77b4: Ipv6hlp:: Could not open registry key (COMM\ConnectionSharing)
0x87ad77b4: Ipv6hlp:: Could not open registry key (COMM\ConnectionSharing)
0x87ad77b4: Ipv6hlp:: Could not open registry key (COMM\ConnectionSharing)
0x87ad77b4: IPv6hlp:: --- OnChangeInterfaceInfo ---
0x87ca8000: DestroyNTE(NTE 0018A520, Addr fe80::5efe:192.168.1.60) ->
invalid
0x87e3f4a8: [NOTIFY] HandleSystemEvent 6 none
0x87c68950: NotifyChange: Setting Event 479FAB92
0x87ca8000: Route RTE 0018C110 fe80::5efe:192.168.1.60/128 -> NCE 0018C0A0
removed
0x87ca8000: NetTableCleanup(NTE 0018A520, Addr fe80::5efe:192.168.1.60) ->
destroyed
0x87a06828: TEL_IOControl(0x1E735DC, 17039424, 0x4D070, 2900, 0x0, 0, 0x0)

I think the driver is not the problem, because the disconnection is detect
immediately.
Is there a way to speed up the detection time in the network stack?

Thanks

J�rgen

"Paul G. Tobey [eMVP]" <paultobey _at_ earthlink _dot_ net> schrieb im
Newsbeitrag news:15DCD79A-5628-46C0...@microsoft.com...


>
> I'd say 'driver problem' is the first to check. It's probably waiting to
> make sure that the connection is not intermittent before it notifies the
> network stack that the cable has been connected. If it's actually the
> network stack causing the delay, I'm pretty sure there is no adjustable
> setting to change how long the detection and address request process
takes.
>
> Paul T.
>

> "J�rgen Thoma�" wrote:
>
> > Hello.
> >
> > I have post this questions some time ago but I have recived no answers.
> >
> > I have a board with an iMX31 CPU and an SMSC Ethernet controller running
> > with
> > WinCE5.0.
> > Is it possible to change the time too detect the insertion of the
ethernet
> > cable. In the actual configuration it takes about 10 sec too detect the
> > cable. When I press RENEW it takes less than 1 sec. Is there a registry
key
> > for the scanning period or is it a driver problem.
> >
> > Best regards
> >

> > J�rgen
> >
> >
> > .
> >


Paul G. Tobey [ eMVP ]

unread,
Nov 24, 2009, 3:10:01 PM11/24/09
to
Those are the debug messages for the wrong case. You want to quickly detect
*connect*, not disconnect, right? Although the relative times at which those
operations occur is interesting, I don't think that you can generalize from
the disconnect case to the connect case and there might be useful
information in the connect case. If the connect case is the same, you're out
of luck unless you have the NDIS source and can read through it and see
what's causing the delay.

Paul T.

Paul T.

"Jürgen Thomaß" wrote:

> Jürgen


>
> "Paul G. Tobey [eMVP]" <paultobey _at_ earthlink _dot_ net> schrieb im
> Newsbeitrag news:15DCD79A-5628-46C0...@microsoft.com...
> >
> > I'd say 'driver problem' is the first to check. It's probably waiting to
> > make sure that the connection is not intermittent before it notifies the
> > network stack that the cable has been connected. If it's actually the
> > network stack causing the delay, I'm pretty sure there is no adjustable
> > setting to change how long the detection and address request process
> takes.
> >
> > Paul T.
> >

> > "Jürgen Thomaß" wrote:
> >
> > > Hello.
> > >
> > > I have post this questions some time ago but I have recived no answers.
> > >
> > > I have a board with an iMX31 CPU and an SMSC Ethernet controller running
> > > with
> > > WinCE5.0.
> > > Is it possible to change the time too detect the insertion of the
> ethernet
> > > cable. In the actual configuration it takes about 10 sec too detect the
> > > cable. When I press RENEW it takes less than 1 sec. Is there a registry
> key
> > > for the scanning period or is it a driver problem.
> > >
> > > Best regards
> > >

> > > Jürgen
> > >
> > >
> > > .
> > >
>
>
> .
>

0 new messages