<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>
Hello,<div><br></div><div>OS: CentOS 5.8 64-bit</div><div>Kernel: 2.6.33</div><div><br></div><div>I've been happily running a single entropykey in a production server that has over 300 days of uptime with the key.</div><div><br></div><div>Today, however, the entropykey appears to have caused the entire server to lockup and produced quite a few errors.</div><div><br></div><div>Here are some snippets, I won't copy/paste them all since it just repeats itself thousands of times.</div><div><br></div><div>Hopefully someone has some ideas as to why this would happen all of a sudden after over 300 days of it working fine.</div><div><br></div><div><br></div><div>Thank you</div><div><br></div><div><div>Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: over-current change on port 1</div><div>Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: over-current change on port 2</div><div>Sep 21 23:27:30 localhost kernel: Clocksource tsc unstable (delta = -114471865715 ns)</div><div>Sep 21 23:27:30 localhost kernel: Switching to clocksource hpet</div><div>Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: connect-debounce failed, port 2 disabled</div><div>Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: over-current change on port 1</div><div>Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: connect-debounce failed, port 1 disabled</div><div>Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: over-current change on port 2</div><div>Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: over-current change on port 1</div><div>Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: over-current change on port 2</div><div>Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: connect-debounce failed, port 2 disabled</div><div>Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: over-current change on port 1</div><div>Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: connect-debounce failed, port 1 disabled</div><div>Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: over-current change on port 2</div><div>Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: over-current change on port 1</div><div>Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: over-current change on port 2</div><div>Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: connect-debounce failed, port 2 disabled</div><div>Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: over-current change on port 1</div><div>Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: connect-debounce failed, port 1 disabled</div><div>Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: over-current change on port 2</div><div>Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: over-current change on port 1</div><div>Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: over-current change on port 2</div><div>Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: connect-debounce failed, port 2 disabled</div><div>Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: over-current change on port 1</div><div>Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: connect-debounce failed, port 1 disabled</div><div>Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: over-current change on port 2</div><div>Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: over-current change on port 1</div><div>Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: over-current change on port 2</div><div>Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: connect-debounce failed, port 2 disabled</div><div>Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: over-current change on port 1</div><div>Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: connect-debounce failed, port 1 disabled</div><div>Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: over-current change on port 2</div><div>Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: over-current change on port 1</div><div>Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: over-current change on port 2</div><div>Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: connect-debounce failed, port 2 disabled</div><div>Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: over-current change on port 1</div><div>Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: connect-debounce failed, port 1 disabled</div><div>Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: over-current change on port 2</div><div>Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: over-current change on port 1</div><div>Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: over-current change on port 2</div><div>Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: connect-debounce failed, port 2 disabled</div><div>Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: over-current change on port 1</div></div><div>Sep 21 23:27:30 localhost ekeyd: Detaching entropy key /dev/entropykey/M.9oQltLJzFBSQFD (M/ 9oQltLJzFBSQFD)</div><div><div>Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: connect-debounce failed, port 2 disabled</div><div>Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: over-current change on port 1</div><div>Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: connect-debounce failed, port 1 disabled</div><div>Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: over-current change on port 2</div><div>Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: over-current change on port 1</div><div>Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: over-current change on port 2</div><div>Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: connect-debounce failed, port 2 disabled</div><div>Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: over-current change on port 1</div><div>Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: connect-debounce failed, port 1 disabled</div><div>Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: over-current change on port 2</div><div>Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: over-current change on port 1</div><div>Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: over-current change on port 2</div><div>Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: connect-debounce failed, port 2 disabled</div><div>Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: over-current change on port 1</div><div>Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: connect-debounce failed, port 1 disabled</div><div>Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: over-current change on port 2</div><div>Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: over-current change on port 1</div><div>Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: over-current change on port 2</div><div>Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: connect-debounce failed, port 2 disabled</div><div>Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: over-current change on port 1</div><div>Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: connect-debounce failed, port 1 disabled</div><div>Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: over-current change on port 2</div><div>Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: over-current change on port 1</div><div>Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: over-current change on port 2</div><div>Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: connect-debounce failed, port 2 disabled</div><div>Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: over-current change on port 1</div><div>Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: connect-debounce failed, port 1 disabled</div><div>Sep 21 23:27:30 localhost kernel: hub 5-0:1.0: over-current change on port 2</div><div>Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: over-current change on port 1</div><div>Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: over-current change on port 2</div><div>Sep 21 23:27:30 localhost kernel: hub 6-0:1.0: connect-debounce failed, port 2 disabled</div></div><div><div>Sep 21 23:27:30 localhost kernel: INFO: task ekeyd:615 blocked for more than 120 seconds.</div><div>Sep 21 23:27:30 localhost kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.</div><div>Sep 21 23:27:30 localhost kernel: ekeyd D 0000000000000000 0 615 1 0x00000004</div><div>Sep 21 23:27:30 localhost kernel: ffff88063fae81d0 0000000000000086 0000000000000000 ffff88063deafc00</div><div>Sep 21 23:27:30 localhost kernel: ffff88063f90a150 ffff88063fae8440 0000000550429ec5 0000000550429ec6</div><div>Sep 21 23:27:30 localhost kernel: ffff88063deafdf8 0000000000000202 0000000000000000 0000000000000000</div><div>Sep 21 23:27:30 localhost kernel: Call Trace:</div><div>Sep 21 23:27:30 localhost kernel: [<ffffffffa00068b4>] ? usb_kill_urb+0x9b/0xb9 [usbcore]</div><div>Sep 21 23:27:30 localhost kernel: [<ffffffff81041d29>] ? autoremove_wake_function+0x0/0x2e</div><div>Sep 21 23:27:30 localhost kernel: [<ffffffffa0007659>] ? usb_start_wait_urb+0x7e/0xb3 [usbcore]</div><div>Sep 21 23:27:30 localhost kernel: [<ffffffffa00078cd>] ? usb_control_msg+0x114/0x137 [usbcore]</div><div>Sep 21 23:27:30 localhost kernel: [<ffffffffa012e3c9>] ? acm_ctrl_msg+0x4c/0x5a [cdc_acm]</div><div>Sep 21 23:27:30 localhost kernel: [<ffffffffa012e5cb>] ? acm_port_down+0x4b/0x167 [cdc_acm]</div><div>Sep 21 23:27:30 localhost kernel: [<ffffffff81163f64>] ? tty_ldisc_flush+0x2f/0x3a</div><div>Sep 21 23:27:30 localhost kernel: [<ffffffff81164d92>] ? tty_port_close_start+0x15c/0x16c</div><div>Sep 21 23:27:30 localhost kernel: [<ffffffffa012e8a2>] ? acm_tty_close+0x73/0x91 [cdc_acm]</div><div>Sep 21 23:27:30 localhost kernel: [<ffffffff8115eb3d>] ? tty_release+0x247/0x530</div><div>Sep 21 23:27:30 localhost kernel: [<ffffffff8108d224>] ? unmap_region+0xf0/0x131</div><div>Sep 21 23:27:30 localhost kernel: [<ffffffff8109e9fd>] ? __fput+0xe8/0x1ab</div><div>Sep 21 23:27:30 localhost kernel: [<ffffffff8109c3ee>] ? filp_close+0x5e/0x66</div><div>Sep 21 23:27:30 localhost kernel: [<ffffffff8109d428>] ? sys_close+0x7e/0xb7</div><div>Sep 21 23:27:30 localhost kernel: [<ffffffff81001d6b>] ? system_call_fastpath+0x16/0x1b</div></div> </div></body>
</html>