Home/Support/Support Forum/Unexpected reboots of AnywhereUSB/14 with newest firmware?
Welcome to Digi Forum, where you can ask questions and receive answers from other members of the community.

Unexpected reboots of AnywhereUSB/14 with newest firmware?

0 votes
Hello,

we had an unexpected reboot of the AnywhereUSB/14.
We never had this problem in the past aand last week we updated to the newest firmware and also the drivers for the W2k8 server. Could it be that this is a bug in the newest firmware?

Is it possible to find out why the AnywhereUSB/14 rebooted? Any logs?
asked Jul 8, 2015 in USB by torsten.mueller New to the Community (1 point)

Please log in or register to answer this question.

1 Answer

0 votes
Telnet or SSH to the AWUSB/14 to get into the CLI then issue the "show panic" command. What's the result?
answered Jul 8, 2015 by jeremym Veteran of the Digi Community (1,687 points)
Hi jeremym,

thx for your response! I checked via telnet and the output is the following:


login: root
password:
#>
#> show panic

Boot(s) since last exception:    1  Number of exceptions detected:    0
Last fault was an exception.  ('show panic e')
('set panic c' to clear buffers)

Exception type: 0x52 (Assertion failed)
    Parameters: 0x000008ea 0x00000000 0x00000000 0x00000000

Occurred at: "net\netcx\netcx_server.cc" line 2282
Message:     0

Version: v1.81.1570  Flags: 0x0  Uptime: 24 seconds

epc    0x80254988 status 0x0000ff01 cause  0x00800000 errepc 0xd3c09a22
hi     0x00000000 lo     0x00000000 pc     0x800b61d4
r0     0x00000000 r1     0x00000001 r2     0x00000000 r3     0x000008ea
r4     0x00000052 r5     0x8034e2bf r6     0x8034e2d5 r7     0x000008ea
r8     0x00000000 r9     0x00000000 r10    0x00000000 r11    0x0000ff01
r12    0x00000044 r13    0x00003540 r14    0x808a04f8 r15    0x00000000
r16    0x80494d30 r17    0x80879f30 r18    0x00000044 r19    0x00000044
r20    0x00000000 r21    0x00000000 r22    0x00000000 r23    0x00000000
r24    0x00000000 r25    0x000000e3 r26    0x80001328 r27    0x8000020c
r28    0x803fee08 r29    0x808a0370 r30    0x808a0370 r31    0x800b61d4

Stack  0x808a0388        0x8023969c        0x80494d30        0x80879f30
       0x00000044        0x06000000        0x808a03a0        0x802384d0
       0x00000003        0x0000001f        0x80879f30        0x00000044
       0x808a04d8        0x8022f11c        0x00000000        0x00000000
       0x00000000        0x00000000        0x00000001        0xefefefef
       0x6d910210        0xfdee040a        0x00000000        0x00000000
       0x00000001        0x00000000        0x80000000        0x00000000
       0x00000000        0x00000000        0x00000000        0x00000000
       0x00000000        0x00000000        0x00000000        0x00000000
       0x00000000        0x00000000        0x00000000        0x00000000
       0x00000000        0x00000000        0x00000000        0x00000000
       0x00000000        0x00000000        0x00000000        0x00000000
       0x00000000        0x00000000        0x00000000        0x00000000
       0x00000000        0x00000000        0x00000000        0x00000000
       0x00000000        0x00000000        0x00000000        0x00000000
       0x00000000        0x00000000        0x00000000        0x00000000

#>
#> show panic e

Boot(s) since last exception:    1  Number of exceptions detected:    0
Last fault was an exception.
('set panic c' to clear buffers)

Exception type: 0x52 (Assertion failed)
    Parameters: 0x000008ea 0x00000000 0x00000000 0x00000000

Occurred at: "net\netcx\netcx_server.cc" line 2282
Message:     0

Version: v1.81.1570  Flags: 0x0  Uptime: 24 seconds

epc    0x80254988 status 0x0000ff01 cause  0x00800000 errepc 0xd3c09a22
hi     0x00000000 lo     0x00000000 pc     0x800b61d4
r0     0x00000000 r1     0x00000001 r2     0x00000000 r3     0x000008ea
r4     0x00000052 r5     0x8034e2bf r6     0x8034e2d5 r7     0x000008ea
r8     0x00000000 r9     0x00000000 r10    0x00000000 r11    0x0000ff01
r12    0x00000044 r13    0x00003540 r14    0x808a04f8 r15    0x00000000
r16    0x80494d30 r17    0x80879f30 r18    0x00000044 r19    0x00000044
r20    0x00000000 r21    0x00000000 r22    0x00000000 r23    0x00000000
r24    0x00000000 r25    0x000000e3 r26    0x80001328 r27    0x8000020c
r28    0x803fee08 r29    0x808a0370 r30    0x808a0370 r31    0x800b61d4

Stack  0x808a0388        0x8023969c        0x80494d30        0x80879f30
       0x00000044        0x06000000        0x808a03a0        0x802384d0
       0x00000003        0x0000001f        0x80879f30        0x00000044
       0x808a04d8        0x8022f11c        0x00000000        0x00000000
       0x00000000        0x00000000        0x00000001        0xefefefef
       0x6d910210        0xfdee040a        0x00000000        0x00000000
       0x00000001        0x00000000        0x80000000        0x00000000
       0x00000000        0x00000000        0x00000000        0x00000000
       0x00000000        0x00000000        0x00000000        0x00000000
       0x00000000        0x00000000        0x00000000        0x00000000
       0x00000000        0x00000000        0x00000000        0x00000000
       0x00000000        0x00000000        0x00000000        0x00000000
       0x00000000        0x00000000        0x00000000        0x00000000
       0x00000000        0x00000000        0x00000000        0x00000000
       0x00000000        0x00000000        0x00000000        0x00000000
       0x00000000        0x00000000        0x00000000        0x00000000

#>
#>


But.. Which useful information do I get from this stacktrace?
commented Jul 9, 2015 by torsten.mueller New to the Community (1 point)
It looks like you're using the Digi RealPort (serial-over-IP) driver.  This is only necessary if you're interfacing with the (DB9 RS232) serial port on the AWUSB/14, not if you're using the USB ports.  Are you actually using the serial port?  Or only using the USB ports?
commented Jul 9, 2015 by jeremym Veteran of the Digi Community (1,687 points)
Yes, we are only using USB ports. Can this cause the problem with the unexpected reboot? Can this have also other sideeffects?
Should we uninstall the RealPort driver?
commented Jul 10, 2015 by torsten.mueller New to the Community (1 point)
I suspect that, for some reason, the RealPort driver is conflicting.  While they SHOULD work well together, maybe there's a bug somewhere.  So, if you aren't using the serial port, I suggest uninstalling the RealPort driver to see if this helps.  Uninstall RealPort by right-clicking the AWUSB in the MultiPortSerial section of Device Manager then selecting Uninstall.
commented Jul 10, 2015 by jeremym Veteran of the Digi Community (1,687 points)
Ok, thanks!
I uninstalled the driver now and will see what happens.

The last unexpected reboot was last week (5 weeks after the first error), so it happens very rarely.
I will give feedback in a couple of weeks if the problem is now solved.
commented Aug 17, 2015 by torsten.mueller New to the Community (1 point)
Hello,
today, exactly 5 weeks after the last reboot, the hub rebootet again.

Below the stackstrace:


#> show panic e

Boot(s) since last exception:    1  Number of exceptions detected:    0
Last fault was an exception.
('set panic c' to clear buffers)

Exception type: 0x52 (Assertion failed)
    Parameters: 0x000008ea 0x00000000 0x00000000 0x00000000

Occurred at: "net\netcx\netcx_server.cc" line 2282
Message:     0

Version: v1.81.1570  Flags: 0x0  Uptime: 24 seconds

epc    0x802e1c1c status 0x0000ff01 cause  0x80800000 errepc 0xd3c09a22
hi     0x00000000 lo     0x00000000 pc     0x800b61d4
r0     0x00000000 r1     0x00000001 r2     0x00000000 r3     0x000008ea
r4     0x00000052 r5     0x8034e2bf r6     0x8034e2d5 r7     0x000008ea
r8     0x00000000 r9     0x00000000 r10    0x00000000 r11    0x0000ff01
r12    0x00000044 r13    0x00000000 r14    0x80879128 r15    0x00000000
r16    0x804917f0 r17    0x80858ba0 r18    0x00000044 r19    0x00000044
r20    0x00000000 r21    0x00000000 r22    0x00000000 r23    0x00000000
r24    0x00000000 r25    0x000000e3 r26    0x80001328 r27    0x8000020c
r28    0x803fee08 r29    0x80878fa0 r30    0x80878fa0 r31    0x800b61d4

Stack  0x80878fb8        0x8023969c        0x804917f0        0x80858ba0
       0x00000044        0x06000000        0x80878fd0        0x802384d0
       0x00000000        0x00000023        0x80858ba0        0x00000044
       0x80879108        0x8022f11c        0x00000000        0x00000000
       0x00000000        0x00000000        0x00000001        0xefefefef
       0x72bf0210        0xfdee040a        0x00000000        0x00000000
       0x00000001        0x00000000        0x00000000        0x00000008
       0x00000000        0x00000000        0x00000000        0x00000000
       0x00000000        0x00000000        0x00000000        0x00000000
       0x00000000        0x00000000        0x00000000        0x00000000
       0x00000000        0x00000000        0x00000000        0x00000000
       0x00000000        0x00000000        0x00000000        0x00000000
       0x00000000        0x00000000        0x00000000        0x00000000
       0x00000000        0x00000000        0x00000000        0x00000000
       0x00000000        0x00000000        0x00000000        0x00000000
       0x00000000        0x00000000        0x00000000        0x00000000


Isn´t it strange that this happens every 5 weeks?
Again it was not possible that the Windows 2008 R2 servers connected automatically to the hub, a reboot of the Windows server was needed. For that problem I created a other ticket: http://www.digi.com/support/forum/48970/disconnect-and-connect-anywhereusb-14-not-working
commented Sep 10, 2015 by torsten.mueller New to the Community (1 point)
It seems to be that disabling the RealPort feature of the hub solved the problem.
We have now a uptime of 50+ days without any problems.
commented Oct 30, 2015 by torsten.mueller New to the Community (1 point)
Excellent, thanks for the update!
commented Oct 30, 2015 by jeremym Veteran of the Digi Community (1,687 points)
...