<html style="direction: ltr;">
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<style type="text/css">body p { margin-bottom: 0cm; margin-top: 0pt; } </style>
</head>
<body style="direction: ltr;"
bidimailui-detected-decoding-type="latin-charset" bgcolor="#FFFFFF"
text="#000000">
<div class="moz-cite-prefix">Hello Steve,<br>
<br>
Just a guess looking at the history : it seems the usb port was
too much drained so it disconnected the key.<br>
<br>
option 1 : the ekey hardware has failed<br>
option 2 : the usb port power has failed<br>
<br>
<a class="moz-txt-link-freetext" href="http://fixunix.com/hardware/541619-usb-error-did-i-fry-my-box.html">http://fixunix.com/hardware/541619-usb-error-did-i-fry-my-box.html</a><br>
<br>
Trying another usb port.<br>
<br>
side note : I cannot figure out why the tsc failed and switched to
the hpet ? is this a signal of a motherboard failure ? Or a linux
kernel problem after 300 days ?<br>
<br>
Best regards,<br>
<br>
Guillaume<br>
<br>
On 22/09/2012 09:02, steve willing wrote:<br>
</div>
<blockquote cite="mid:SNT141-W557FD3933D6DB28E171FFF87980@phx.gbl"
type="cite">
<pre wrap="">
Hello,
OS: CentOS 5.8 64-bit
Kernel: 2.6.33
I've been happily running a single entropykey in a production server that has over 300 days of uptime with the key.
Today, however, the entropykey appears to have caused the entire server to lockup and produced quite a few errors.
Here are some snippets, I won't copy/paste them all since it just repeats itself thousands of times.
Hopefully someone has some ideas as to why this would happen all of a sudden after over 300 days of it working fine.
Thank you
Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: over-current change on port 1
Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: over-current change on port 2
Sep 21 23:27:30 localhost kernel: Clocksource tsc unstable (delta = -114471865715 ns)
Sep 21 23:27:30 localhost kernel: Switching to clocksource hpet
Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: connect-debounce failed, port 2 disabled
Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: over-current change on port 1
Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: connect-debounce failed, port 1 disabled
Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: over-current change on port 2
Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: over-current change on port 1
Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: over-current change on port 2
Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: connect-debounce failed, port 2 disabled
Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: over-current change on port 1
Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: connect-debounce failed, port 1 disabled
Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: over-current change on port 2
Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: over-current change on port 1
Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: over-current change on port 2
Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: connect-debounce failed, port 2 disabled
Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: over-current change on port 1
Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: connect-debounce failed, port 1 disabled
Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: over-current change on port 2
Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: over-current change on port 1
Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: over-current change on port 2
Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: connect-debounce failed, port 2 disabled
Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: over-current change on port 1
Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: connect-debounce failed, port 1 disabled
Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: over-current change on port 2
Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: over-current change on port 1
Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: over-current change on port 2
Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: connect-debounce failed, port 2 disabled
Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: over-current change on port 1
Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: connect-debounce failed, port 1 disabled
Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: over-current change on port 2
Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: over-current change on port 1
Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: over-current change on port 2
Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: connect-debounce failed, port 2 disabled
Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: over-current change on port 1
Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: connect-debounce failed, port 1 disabled
Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: over-current change on port 2
Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: over-current change on port 1
Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: over-current change on port 2
Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: connect-debounce failed, port 2 disabled
Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: over-current change on port 1
Sep 21 23:27:30 localhost ekeyd: Detaching entropy key /dev/entropykey/M.9oQltLJzFBSQFD (M/ 9oQltLJzFBSQFD)
Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: connect-debounce failed, port 2 disabled
Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: over-current change on port 1
Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: connect-debounce failed, port 1 disabled
Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: over-current change on port 2
Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: over-current change on port 1
Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: over-current change on port 2
Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: connect-debounce failed, port 2 disabled
Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: over-current change on port 1
Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: connect-debounce failed, port 1 disabled
Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: over-current change on port 2
Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: over-current change on port 1
Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: over-current change on port 2
Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: connect-debounce failed, port 2 disabled
Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: over-current change on port 1
Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: connect-debounce failed, port 1 disabled
Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: over-current change on port 2
Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: over-current change on port 1
Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: over-current change on port 2
Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: connect-debounce failed, port 2 disabled
Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: over-current change on port 1
Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: connect-debounce failed, port 1 disabled
Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: over-current change on port 2
Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: over-current change on port 1
Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: over-current change on port 2
Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: connect-debounce failed, port 2 disabled
Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: over-current change on port 1
Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: connect-debounce failed, port 1 disabled
Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: over-current change on port 2
Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: over-current change on port 1
Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: over-current change on port 2
Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: connect-debounce failed, port 2 disabled
Sep 21 23:27:30 localhost kernel: INFO: task ekeyd:615 blocked for more than 120 seconds.
Sep 21 23:27:30 localhost kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Sep 21 23:27:30 localhost kernel: ekeyd D 0000000000000000 0 615 1 0x00000004
Sep 21 23:27:30 localhost kernel: ffff88063fae81d0 0000000000000086 0000000000000000 ffff88063deafc00
Sep 21 23:27:30 localhost kernel: ffff88063f90a150 ffff88063fae8440 0000000550429ec5 0000000550429ec6
Sep 21 23:27:30 localhost kernel: ffff88063deafdf8 0000000000000202 0000000000000000 0000000000000000
Sep 21 23:27:30 localhost kernel: Call Trace:
Sep 21 23:27:30 localhost kernel: [<ffffffffa00068b4>] ? usb_kill_urb+0x9b/0xb9 [usbcore]
Sep 21 23:27:30 localhost kernel: [<ffffffff81041d29>] ? autoremove_wake_function+0x0/0x2e
Sep 21 23:27:30 localhost kernel: [<ffffffffa0007659>] ? usb_start_wait_urb+0x7e/0xb3 [usbcore]
Sep 21 23:27:30 localhost kernel: [<ffffffffa00078cd>] ? usb_control_msg+0x114/0x137 [usbcore]
Sep 21 23:27:30 localhost kernel: [<ffffffffa012e3c9>] ? acm_ctrl_msg+0x4c/0x5a [cdc_acm]
Sep 21 23:27:30 localhost kernel: [<ffffffffa012e5cb>] ? acm_port_down+0x4b/0x167 [cdc_acm]
Sep 21 23:27:30 localhost kernel: [<ffffffff81163f64>] ? tty_ldisc_flush+0x2f/0x3a
Sep 21 23:27:30 localhost kernel: [<ffffffff81164d92>] ? tty_port_close_start+0x15c/0x16c
Sep 21 23:27:30 localhost kernel: [<ffffffffa012e8a2>] ? acm_tty_close+0x73/0x91 [cdc_acm]
Sep 21 23:27:30 localhost kernel: [<ffffffff8115eb3d>] ? tty_release+0x247/0x530
Sep 21 23:27:30 localhost kernel: [<ffffffff8108d224>] ? unmap_region+0xf0/0x131
Sep 21 23:27:30 localhost kernel: [<ffffffff8109e9fd>] ? __fput+0xe8/0x1ab
Sep 21 23:27:30 localhost kernel: [<ffffffff8109c3ee>] ? filp_close+0x5e/0x66
Sep 21 23:27:30 localhost kernel: [<ffffffff8109d428>] ? sys_close+0x7e/0xb7
Sep 21 23:27:30 localhost kernel: [<ffffffff81001d6b>] ? system_call_fastpath+0x16/0x1b
_______________________________________________
EntropyKey-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:EntropyKey-users@lists.simtec.co.uk">EntropyKey-users@lists.simtec.co.uk</a>
<a class="moz-txt-link-freetext" href="http://lists.simtec.co.uk/cgi-bin/mailman/listinfo/entropykey-users">http://lists.simtec.co.uk/cgi-bin/mailman/listinfo/entropykey-users</a>
</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Cordialement, Best regards,
Guillaume
Tiebogos (by L'Oreal), parce que je le 'veau' bien.
Vision without action is a daydream.
Action without vision is a nightmare. -- Japanese Proverb</pre>
</body>
</html>