We have noticed that Socklet crashes when the sytem is rebooted with
the Ethernet cable disconnected. If the Ethernet cable is disconnected
after Socklet has been started, or if it is started by hand after
booting without the cable, it continues to run, however. Can anyone
give me any insight on why this is happening or how to work around it?
Will Parsons wrote:
We have noticed that Socklet crashes when the sytem is rebooted with
the Ethernet cable disconnected. If the Ethernet cable is disconnected
after Socklet has been started, or if it is started by hand after
booting without the cable, it continues to run, however. Can anyone
give me any insight on why this is happening or how to work around it?
What is happening is this. The Ethernet driver starts up and attempts
to auto-negotiate with the hub/switch/peer and can’t. It keeps trying
forever (or at least for a long time) - meanwhile, since the driver was
started in the background, and doesn’t register with Net until it has
finished auto-negotiation, Socklet fails to find any adapters, and
exits (it doesn’t usually crash, it exits).
2 solutions:
Rennie
What ethernet driver are you running and what version?
“Will Parsons” <wbp@alfa.eng.sun.com> wrote in message
news:blkcpk$leh$1@inn.qnx.com…
We have noticed that Socklet crashes when the sytem is rebooted with
the Ethernet cable disconnected. If the Ethernet cable is disconnected
after Socklet has been started, or if it is started by hand after
booting without the cable, it continues to run, however. Can anyone
give me any insight on why this is happening or how to work around it?
- Will P.
Rennie Allen <rallen@csical.com> wrote:
Will Parsons wrote:
We have noticed that Socklet crashes when the sytem is rebooted with
the Ethernet cable disconnected. If the Ethernet cable is disconnected
after Socklet has been started, or if it is started by hand after
booting without the cable, it continues to run, however. Can anyone
give me any insight on why this is happening or how to work around it?What is happening is this. The Ethernet driver starts up and attempts
to auto-negotiate with the hub/switch/peer and can’t. It keeps trying
forever (or at least for a long time) - meanwhile, since the driver was
started in the background, and doesn’t register with Net until it has
finished auto-negotiation, Socklet fails to find any adapters, and
exits (it doesn’t usually crash, it exits).2 solutions:
- Don’t leave cable unplugged or switch/hub turned off.
or- Fix the speed of the driver (so that it wont autoneg).
Rennie
Thank for the suggestion - I’ll give it a try.
-Will
Hugh Brown <hsbrown@qnx.com> wrote:
What ethernet driver are you running and what version?
“Will Parsons” <> wbp@alfa.eng.sun.com> > wrote in message
news:blkcpk$leh$> 1@inn.qnx.com> …
We have noticed that Socklet crashes when the sytem is rebooted with
the Ethernet cable disconnected. If the Ethernet cable is disconnected
after Socklet has been started, or if it is started by hand after
booting without the cable, it continues to run, however. Can anyone
give me any insight on why this is happening or how to work around it?
Net.ether82557 4.25D