KVM不响应按键

问题描述

KVM可以看到OS界面,键盘、软键盘都没有响应

dmesg日志

~ # dmesg 
[   71.285227] device-mapper: ioctl: dmsetup[2916]: dm-0 (mmcblksp) is created successfully
[   71.757128] device-mapper: ioctl: dmsetup[2923]: dm-0 (mmcblksp) is removed successfully
[   71.964754] device-mapper: ioctl: dmsetup[2929]: dm-0 (mmcblksp) is created successfully
[   82.358535] 68,2026-05-19 11:51:37,3170,bt_probe,781,bt use LPC!
[   82.366405] 69,2026-05-19 11:51:37,3170,bt_probe,806,bt init ok!
[   90.179493] usbcore: registered new interface driver cdc_ether
[   90.432952] usbcore: registered new interface driver rndis_host
[   91.182107] [I2C-08-RT<-5|-5>] M<0x21|0x1|0x0|1|10> L<1|1|0> C<1|0|1> E<0x801|0x0|0x0|0x1> I<0x0|0x710|0x0>
[   91.415574] [I2C-08-RT<-5|-5>] M<0x21|0x1|0x0|1|10> L<1|1|0> C<1|0|1> E<0x801|0x0|0x0|0x1> I<0x0|0x710|0x0>
[   91.656767] [I2C-08-RT<-5|-5>] M<0x21|0x1|0x0|1|10> L<1|1|0> C<1|0|1> E<0x801|0x0|0x0|0x1> I<0x0|0x710|0x0>
[   91.879542] [I2C-08-RT<-5|-5>] M<0x47|0x1|0x0|1|10> L<1|1|0> C<1|0|1> E<0x801|0x0|0x0|0x1> I<0x0|0x710|0x0>
[   92.089249] [I2C-08-RT<-5|-5>] M<0x47|0x1|0x0|1|10> L<1|1|0> C<1|0|1> E<0x801|0x0|0x0|0x1> I<0x0|0x710|0x0>
[   92.308551] [I2C-08-RT<-5|-5>] M<0x47|0x1|0x0|1|10> L<1|1|0> C<1|0|1> E<0x801|0x0|0x0|0x1> I<0x0|0x710|0x0>
[   96.488322] usb device-0: command connect. function count 2 
[   96.700026] usb device-0: attach driver 
[   96.700069] usb device-0: gadget bind 
[   96.700083] usb device-0: Bind speed 2.0 
[   97.550325] [I2C-08-RT<-5|-5>] M<0x47|0x1|0x0|1|10> L<1|1|0> C<1|0|1> E<0x801|0x0|0x0|0x1> I<0x0|0x710|0x0>
[   97.743038] [I2C-08-RT<-5|-5>] M<0x21|0x1|0x0|1|10> L<1|1|0> C<1|0|1> E<0x801|0x0|0x0|0x1> I<0x0|0x710|0x0>
[   99.118578] 70,2026-05-19 11:51:54,ISR,sysctrl_rst_int_handle,436,Receive subsys_rst_irq(41), int_reg(0x13c) int_sts(0x77b)!
[  104.525869] 71,2026-05-19 11:51:59,ISR,sysctrl_rst_int_handle,436,Receive subsys_rst_irq(42), int_reg(0x13c) int_sts(0x77f)!
[  104.537096] 72,2026-05-19 11:51:59,ISR,sysctrl_rst_int_handle,436,Receive subsys_rst_irq(41), int_reg(0x13c) int_sts(0x17b)!
[  111.210726] 73,2026-05-19 11:52:06,2769,mctp_reset,1477,reset mctp ok!
[  111.228755] 74,2026-05-19 11:52:06,2769,mctp_dereset,1501,dereset mctp ok!
[  157.589420] [I2C-08-RT<-5|-5>] M<0x47|0x1|0x0|1|10> L<1|1|0> C<1|0|1> E<0x801|0x0|0x0|0x1> I<0x0|0x710|0x0>
[  157.791492] [I2C-08-RT<-5|-5>] M<0x21|0x1|0x0|1|10> L<1|1|0> C<1|0|1> E<0x801|0x0|0x0|0x1> I<0x0|0x710|0x0>
[  207.851359] 75,2026-05-19 11:53:42,2772,mctp_reset,1477,reset mctp ok!
[  207.860588] 76,2026-05-19 11:53:42,2772,mctp_dereset,1501,dereset mctp ok!
[  217.660730] [I2C-08-RT<-5|-5>] M<0x47|0x1|0x0|1|10> L<1|1|0> C<1|0|1> E<0x801|0x0|0x0|0x1> I<0x0|0x710|0x0>
[  217.864464] [I2C-08-RT<-5|-5>] M<0x21|0x1|0x0|1|10> L<1|1|0> C<1|0|1> E<0x801|0x0|0x0|0x1> I<0x0|0x710|0x0>
[  244.899966] edma: 1851, host is registered.
[  259.712885] usb device-0: command disconnect 
[  259.712908] usb device-0: detach driver
[  259.716040] usb device-0: gadget disconnect 
[  259.716063] usb device-0: reset configuration. gadget state <0> 
[  259.716077] usb device-0: gadget unbind 
[  259.716105] dwc3 8800000.dwc3: request ffff30987f011c00 was not queued to ep1in
[  259.723415] dwc3 8800000.dwc3: request ffff30987f011600 was not queued to ep2in
[  260.442527] usb device-0: command connect. function count 2 
[  260.659978] usb device-0: attach driver 
[  260.660017] usb device-0: gadget bind 
[  260.660030] usb device-0: Bind speed 2.0 
[  273.975971] usb device-0: command disconnect 
[  273.975991] usb device-0: detach driver
[  273.979077] usb device-0: gadget disconnect 
[  273.979100] usb device-0: reset configuration. gadget state <0> 
[  273.979115] usb device-0: gadget unbind 
[  273.979147] dwc3 8800000.dwc3: request ffff30987c872480 was not queued to ep1in
[  273.986458] dwc3 8800000.dwc3: request ffff30987c872780 was not queued to ep2in
[  274.702952] usb device-0: command connect. function count 2 
[  274.919995] usb device-0: attach driver 
[  274.920037] usb device-0: gadget bind 
[  274.920051] usb device-0: Bind speed 2.0 
[  275.819096] usb device-0: command disconnect 
[  275.819118] usb device-0: detach driver
[  275.822345] usb device-0: gadget disconnect 
[  275.822367] usb device-0: reset configuration. gadget state <0> 
[  275.822381] usb device-0: gadget unbind 
[  275.822409] dwc3 8800000.dwc3: request ffff30987f011a80 was not queued to ep1in
[  275.829717] dwc3 8800000.dwc3: request ffff30987f011300 was not queued to ep2in
[  276.542621] usb device-0: command connect. function count 2 
[  276.760031] usb device-0: attach driver 
[  276.760072] usb device-0: gadget bind 
[  276.760086] usb device-0: Bind speed 2.0 
[  277.633637] usb device-0: command disconnect 
[  277.633658] usb device-0: detach driver
[  277.636763] usb device-0: gadget disconnect 
[  277.636787] usb device-0: reset configuration. gadget state <0> 
[  277.636801] usb device-0: gadget unbind 
[  277.636831] dwc3 8800000.dwc3: request ffff30987f011e40 was not queued to ep1in
[  277.644139] dwc3 8800000.dwc3: request ffff30987f011cc0 was not queued to ep2in
[  277.723961] [I2C-08-RT<-5|-5>] M<0x47|0x1|0x0|1|10> L<1|1|0> C<1|0|1> E<0x801|0x0|0x0|0x1> I<0x0|0x710|0x0>
[  277.928356] [I2C-08-RT<-5|-5>] M<0x21|0x1|0x0|1|10> L<1|1|0> C<1|0|1> E<0x801|0x0|0x0|0x1> I<0x0|0x710|0x0>
[  278.362521] usb device-0: command connect. function count 2 
[  278.579990] usb device-0: attach driver 
[  278.580030] usb device-0: gadget bind 
[  278.580043] usb device-0: Bind speed 2.0 
[  279.471231] usb device-0: command disconnect 
[  279.471252] usb device-0: detach driver
[  279.473713] usb device-0: gadget disconnect 
[  279.473732] usb device-0: reset configuration. gadget state <0> 
[  279.473746] usb device-0: gadget unbind 
[  279.473776] dwc3 8800000.dwc3: request ffff30984e70c240 was not queued to ep1in
[  279.481082] dwc3 8800000.dwc3: request ffff30984e70c9c0 was not queued to ep2in
[  280.190873] usb device-0: command connect. function count 2 
[  280.409988] usb device-0: attach driver 
[  280.410026] usb device-0: gadget bind 
[  280.410039] usb device-0: Bind speed 2.0 
[  281.332771] usb device-0: command disconnect 
[  281.332792] usb device-0: detach driver
[  281.335937] usb device-0: gadget disconnect 
[  281.335960] usb device-0: reset configuration. gadget state <0> 
[  281.335975] usb device-0: gadget unbind 
[  281.336003] dwc3 8800000.dwc3: request ffff30984e70c0c0 was not queued to ep1in
[  281.343309] dwc3 8800000.dwc3: request ffff30984e70c3c0 was not queued to ep2in
[  282.072470] usb device-0: command connect. function count 2 
[  282.289998] usb device-0: attach driver 
[  282.290038] usb device-0: gadget bind 
[  282.290054] usb device-0: Bind speed 2.0 
[  337.774619] [I2C-08-RT<-5|-5>] M<0x47|0x1|0x0|1|10> L<1|1|0> C<1|0|1> E<0x801|0x0|0x0|0x1> I<0x0|0x710|0x0>
[  337.977552] [I2C-08-RT<-5|-5>] M<0x21|0x1|0x0|1|10> L<1|1|0> C<1|0|1> E<0x801|0x0|0x0|0x1> I<0x0|0x710|0x0>
[  397.861862] [I2C-08-RT<-5|-5>] M<0x47|0x1|0x0|1|10> L<1|1|0> C<1|0|1> E<0x801|0x0|0x0|0x1> I<0x0|0x710|0x0>
[  398.068233] [I2C-08-RT<-5|-5>] M<0x21|0x1|0x0|1|10> L<1|1|0> C<1|0|1> E<0x801|0x0|0x0|0x1> I<0x0|0x710|0x0>
[  457.915728] [I2C-08-RT<-5|-5>] M<0x47|0x1|0x0|1|10> L<1|1|0> C<1|0|1> E<0x801|0x0|0x0|0x1> I<0x0|0x710|0x0>
[  458.120612] [I2C-08-RT<-5|-5>] M<0x21|0x1|0x0|1|10> L<1|1|0> C<1|0|1> E<0x801|0x0|0x0|0x1> I<0x0|0x710|0x0>
[  517.971467] [I2C-08-RT<-5|-5>] M<0x47|0x1|0x0|1|10> L<1|1|0> C<1|0|1> E<0x801|0x0|0x0|0x1> I<0x0|0x710|0x0>
[  518.165479] [I2C-08-RT<-5|-5>] M<0x21|0x1|0x0|1|10> L<1|1|0> C<1|0|1> E<0x801|0x0|0x0|0x1> I<0x0|0x710|0x0>
[  578.031192] [I2C-08-RT<-5|-5>] M<0x47|0x1|0x0|1|10> L<1|1|0> C<1|0|1> E<0x801|0x0|0x0|0x1> I<0x0|0x710|0x0>
[  578.223358] [I2C-08-RT<-5|-5>] M<0x21|0x1|0x0|1|10> L<1|1|0> C<1|0|1> E<0x801|0x0|0x0|0x1> I<0x0|0x710|0x0>
[  638.119087] [I2C-08-RT<-5|-5>] M<0x47|0x1|0x0|1|10> L<1|1|0> C<1|0|1> E<0x801|0x0|0x0|0x1> I<0x0|0x710|0x0>
[  638.312104] [I2C-08-RT<-5|-5>] M<0x21|0x1|0x0|1|10> L<1|1|0> C<1|0|1> E<0x801|0x0|0x0|0x1> I<0x0|0x710|0x0>
[  698.151177] [I2C-08-RT<-5|-5>] M<0x47|0x1|0x0|1|10> L<1|1|0> C<1|0|1> E<0x801|0x0|0x0|0x1> I<0x0|0x710|0x0>
[  698.344066] [I2C-08-RT<-5|-5>] M<0x21|0x1|0x0|1|10> L<1|1|0> C<1|0|1> E<0x801|0x0|0x0|0x1> I<0x0|0x510|0x0>
[  758.184176] [I2C-08-RT<-5|-5>] M<0x47|0x1|0x0|1|10> L<1|1|0> C<1|0|1> E<0x801|0x0|0x0|0x1> I<0x0|0x710|0x0>
[  758.389889] [I2C-08-RT<-5|-5>] M<0x21|0x1|0x0|1|10> L<1|1|0> C<1|0|1> E<0x801|0x0|0x0|0x1> I<0x0|0x510|0x0>
[ 9098.823562] 77,2026-05-19 14:21:53,ISR,sysctrl_rst_int_handle,436,Receive subsys_rst_irq(42), int_reg(0x13c) int_sts(0x407f)!
[ 9099.489271] 78,2026-05-19 14:21:54,ISR,sysctrl_rst_int_handle,436,Receive subsys_rst_irq(41), int_reg(0x13c) int_sts(0x477b)!
[ 9100.261876] 79,2026-05-19 14:21:55,2771,mctp_reset,1477,reset mctp ok!
[ 9100.269995] 80,2026-05-19 14:21:55,2771,mctp_dereset,1501,dereset mctp ok!
[ 9104.898599] 81,2026-05-19 14:21:59,ISR,sysctrl_rst_int_handle,436,Receive subsys_rst_irq(42), int_reg(0x13c) int_sts(0x477f)!
[ 9104.909905] 82,2026-05-19 14:21:59,ISR,sysctrl_rst_int_handle,436,Receive subsys_rst_irq(41), int_reg(0x13c) int_sts(0x417b)!
[ 9114.019956] edma: 1862, host is lost.
[ 9188.944376] 83,2026-05-19 14:23:23,2870,mctp_reset,1477,reset mctp ok!
[ 9188.956567] 84,2026-05-19 14:23:23,2870,mctp_dereset,1501,dereset mctp ok!
[ 9188.982733] 85,2026-05-19 14:23:23,2870,mctp_reset,1477,reset mctp ok!
[ 9188.992026] 86,2026-05-19 14:23:23,2870,mctp_dereset,1501,dereset mctp ok!
[ 9222.179954] edma: 1851, host is registered.

app日志报错

2026-05-19 14:41:03.631989 unknown_service ERROR: km_api.lua(176): Get keyboard state fail, usb_id=0, fn_id=0, ret=22 [repeated 58 times in 420s from 2026-05-19 14:34:03.381555 to 2026-05-19 14:41:03.631989]
2026-05-19 14:41:08.285590 unknown_service ERROR: agent.lua(214): check kvm message content failed, cmd_type:0204, ret:1000002 [repeated 74 times in 430s from 2026-05-19 14:33:58.738726 to 2026-05-19 14:41:08.285590]

可以参考 KVM常见问题定位指南 | 文档中心 | openUBMC

问题设备有was not queued日志,且现象是必现的,是否需要优先排查硬件?

非bmc问题,参考文档中解决方案需要联系芯片SDK团队进行定位分析

答案内容由AI生成,仅供参考:
根据您提供的回答内容,其中没有明确标有“问题总结”、“解决方案”或“结论”字样的章节。因此,返回空内容。

点击此处查看详细分析解答

根据您提供的Context中的信息,针对“KVM不响应按键”的问题,以下是基于知识库的详细分析与排查指引:

1. 问题状态确认

您描述的问题“KVM可以看到OS界面,键盘、软键盘都没有响应”,在知识库中是一个已知的、已记录的主题(Topic ID 6241)。这与知识库中描述的“KVM is a system that displays an OS interface but is unresponsive to keyboard and soft keyboard inputs”以及“OS refers to the operating system that the device has successfully booted into, which may be relevant to troubleshooting KVM issues”完全吻合。

2. 核心故障线索

根据您提供的dmesg日志和app日志报错,知识库中的信息指向了以下几个关键点:

  • KVM服务与代理异常Agent_Lua组件在处理KVM消息时报告了失败。您日志中的 agent.lua(214): check kvm message content failed, cmd_type:0204, ret:1000002 错误,正是该问题的直接体现。
  • 键盘状态获取失败:日志中的 km_api.lua(176): Get keyboard state fail, usb_id=0, fn_id=0, ret=22 错误,表明系统无法获取键盘状态。知识库中提到的“Keyboard is a peripheral device configured by USB Device-0”和“The physical keyboard connected to the KVM is not responding to input”与此现象高度一致。
  • USB设备连接中断:您的dmesg日志中有大量关于usb device-0disconnectattachconnect 记录,这表明与KVM键盘/鼠标功能相关的USB设备连接不稳定或存在频繁的重置。知识库说明“KVM功能使用四个USB2.0端口中的两个连接虚拟键盘和鼠标”,因此USB连接的频繁中断是导致输入无响应的直接硬件线索。
  • 输入与显示问题区分:知识库指出,通过“Key Mouse Response(系统接受键盘和鼠标输入的能力)”可以区分问题是“图像冻结”还是“输入设备故障”。您的情况(能看到OS界面但无法输入)明确属于输入设备故障或连接/处理失败,而非单纯的视频显示问题。

3. 排查与解决方向

结合知识库中的信息,建议您从以下几个方面进行排查:

  • 检查KVM服务配置

    • 确认LocalKvmEnabled属性是否被意外禁用。此属性用于控制本地KVM功能,其配置错误会导致输入设备无响应。
    • 检查Virtual Console Startup Disable Local KVM设置。如果虚拟控制台启动时禁用了本地KVM,可能会与当前会话冲突。
    • 检查KVM服务端口配置。知识库提到“KVM Service runs on port 2198”,并且“Setting Virtual Console Port to 1, 7, or 11 results in failure to open KVM”。确保端口配置正确且未被防火墙(Iptables)规则错误拦截(如知识库中提到的“Iptables handles port forwarding for KVM and removes it when KVM is disabled”)。
  • 检查硬件与驱动状态

    • 检查KVM dvmbm 功能:知识库指出“The KVM dvmbm feature is disabled in this configuration”。请确认此功能是否已启用。
    • 检查 hibmc_drm 驱动:知识库提到“The hibmc_drm driver is required for the KVM interface to render properly; its absence causes display issues”。虽然当前问题偏重输入,但驱动异常也可能间接影响整个KVM功能的稳定性。
    • 参考社区用户Vyasa的建议:“Vyasa suggests checking KVM hardware for abnormalities”,对相关硬件连接(特别是与USB相关的部分)进行物理检查。
  • 参考社区经验

    • 用户TuHuaNeng “confirmed experiencing the same KVM input failure during BIOS boot”,表明此问题并非个例。
    • 用户Huanting 曾就类似的KVM信号问题提出过追问,表明这是一个需要持续关注的故障点。