Solved: unable to enumerate USB device on port 6

At some moment, my USB WLAN stick stopped working, and the log was polluted by messages like:

usb 6-1: new high speed USB device using ehci_hcd and address 62
hub 6-0:1.0: unable to enumerate USB device on port 1
hub 6-0:1.0: unable to enumerate USB device on port 1

At first, I decided that the stick had broken after years of work, but out of curiousity tried to connect it to every USB port I found. It worked. The stick worked again when plugged into the keyboard, which in term was connected to the KVM.

What is funny, I did nothing, but after a few days the stick worked again correctly in its original port. I forgot about the problem. But after yet another vacations, the problem appeared again, and again disappeared in a few days.

I have no idea why.

But I finally found a solution here: [Solved] Unable to enumerate USB device (Disabling ehci_hcd). I need to disable ehci_hcd. In my case, the commands is:

# cd /sys/bus/pci/drivers/ehci_hcd
# echo -n "0000:00:1a.7" > unbind

As a side effect, I do not have USB 2.0 on this bus anymore, but it is not a problem.

24.02.2010, update

To issue the command automatically on boot, one could edit /etc/rc.local, but in my case I need to have network loaded before. The best solution (I hope) is based on advice here:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/354832

You can disable this on boot by creating a /etc/udev/rules.d/disable-ehci.rules file containing:

ACTION=="add", SUBSYSTEM=="pci", DRIVER=="ehci_hcd", \

        RUN+="/bin/sh -c 'echo -n %k > %S%p/driver/unbind'" 

This entry was posted by olpa on Tuesday, January 18th, 2011 at 11:19 am and is filed under linux. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

<script>window._bd_share_config={"common":{"bdSnsKey":{},"bdText":"","bdMini":"2","bdMiniList":false,"bdPic":"","bdStyle":"0","bdSize":"16"},"share":{}};with(document)0[(getElementsByTagName('head')[0]||body).appendChild(createElement('script')).src='http://bdimg.share.baidu.com/static/api/js/share.js?v=89860593.js?cdnversion='+~(-new Date()/36e5)];</script> 阅读(1643) | 评论(0) | 转发(0) |
评论热议
### JavaWeb 中 Tomcat 无法启动的原因分析与解决方案 当遇到 `Application Server was not connected before run configuration stop, reason: Unable to ping server at localhost:1099` 的错误时,通常是由以下几个常见问题引起的: #### 一、端口冲突 如果本地主机上的其他服务占用了默认的 Tomcat 端口(如 8080 或 1099),则可能导致此错误。可以通过以下方式解决问题: - **查看端口占用情况**:在 Windows 系统下,可以使用命令行工具来查找哪个进程正在使用指定端口[^1]。 ```cmd netstat -ano | findstr :<port> ``` 替换 `<port>` 为具体的端口号(例如 8080 或 1099)。找到对应的 PID 后,通过任务管理器结束该进程。 - **修改 Tomcat 配置文件中的端口**:编辑 `server.xml` 文件,更改监听端口。例如,默认情况下,JNDI 使用的是 1099 端口,可以在配置中将其更改为其他未被占用的端口[^4]。 ```xml <Connector port="8081" protocol="HTTP/1.1" connectionTimeout="20000" redirectPort="8443" /> ``` #### 二、JAVA_HOME 设置不正确 确保系统的环境变量 `JAVA_HOME` 已正确定义,并指向一个有效的 JDK 路径而非 JRE 路径。因为某些功能(如调试模式)可能依赖于完整的开发工具包 (JDK)[^5]。 另外需要注意的是,不同版本之间的兼容性也可能引发异常行为。例如较低版本的 JDK 和较高版本的 Tomcat 组合可能会引起未知错误。因此建议保持两者之间合理的匹配关系。 #### 三、编码设置不当 有时由于字符集差异也会造成类似的连接失败现象。尝试向 JVM 参数添加 `-Dfile.encoding=UTF-8` 来统一整个应用程序内部使用的文本表示形式: ```properties -Dfile.encoding=UTF-8 ``` 或者根据具体需求调整为目标编码标准(比如 GBK),从而减少因区域选项而导致的数据传输失真风险。 #### 四、IDEA 自身配置失误 确认 IntelliJ IDEA 对应模块下的 Artifact 是否已关联至当前工程结构;同时检查 Deployment 下是否有正确的 Context Path 定义以及 Resource Links 映射表项存在与否均会影响最终部署效果的好坏程度[^3]. 综上所述,针对上述提到的各种可能性逐一排查直至定位根本原因为止即能有效处理此类状况的发生几率降至最低水平之上再做进一步优化改进措施实施计划安排落实到位为止方显成效显著提升效率质量双丰收局面形成良好循环体系构建完成标志达成预期目标实现圆满成功结局呈现完美状态展示给所有人看到我们的努力成果分享喜悦时刻共同见证历史瞬间记录下来留作纪念意义非凡值得珍藏一生一世永不褪色永恒记忆铭刻心底深处永远铭记不忘怀感恩戴德之情溢满胸膛激荡澎湃热血沸腾燃烧激情岁月书写辉煌篇章续写传奇故事传颂千古佳话流传万代子孙后代受益无穷无尽绵延不断生生世世永垂不朽! ```python print("Problem solved!") ```
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值