ikvm gadget usb_ep_queue error when the hostOS reboot
Subsystems (2)
Hi Jae,
The bmc serial port will print an usb_ep_queue errors when reboot the hostOS.
I can reproduce it by the following steps:
1, Login the bmc webpage ,open the kvm webpage.
2, reboot the host OS
3, Bmc Serial port will print error messages:
[ 680.786134] aspeed-video 1e700000.video: Timed out; first mode detect [ 681.846125] aspeed-video 1e700000.video: Timed out when stopping streaming [ 682.356106] aspeed-video 1e700000.video: Timed out; first mode detect [ 682.377294] configfs-gadget gadget: usb_ep_queue error on int endpoint -108 [ 682.896212] aspeed-video 1e700000.video: Timed out; first mode detect [ 684.917892] configfs-gadget gadget: usb_ep_queue error on int endpoint -108 [ 685.426159] aspeed-video 1e700000.video: Timed out; first mode detect
4, It will stop the error output when the hostOS start to bootup.[ 739.598840] configfs-gadgetgadget: high-speed config #1: c [ 739.629961] aspeed_vhub 1e6a0000.usb-vhub: status direction mismatch
Does this output make sense?
Best,
Xiuzhi
------------------ Original ------------------
From: "jae.hyun.yoo";<[email protected]>; Date: Jun 1, 2019 To: "xiuzhi"<[email protected]>; "openbmc"<[email protected]>; "eajames"<[email protected]>; "joel"<[email protected]>; "andrew"<[email protected]>;
Subject: Re: [PATCH dev-5.1 4/4] media: aspeed: add a workaround to fix asilicon bug (Jae Hyun Yoo)
Quoted 12 lines · xiuzhi
Hi Jae,
I tested this patch ,it works on 1680*1050,but I found an issue:The ikvm webpage will be black screen when you reboot the host after switching solution between 1680*1050 and 800*600 on chrome browser (my chrome version is 65).
you can reproduce it:
1, Set host screen solution to 1680*1050 and save it . ikvm webpage works 2,Set host screen solution to 800*600 and save it. ikvm webpage works
3,Reset host screen solution to 1680*1050 and save it,
4,reboot the host,
5, the ikvm webpage is black screen when boot to Centos GUI
Hi Xiuzhi,
Checked that the issue isn't related this patch. Actually, that is caused by the first patch of this patch series. Since the patch removes source buffer allocation before mode detection, remaining allocation logic should be changed accordingly, otherwise it can't allocate buffers and eventually causes the issue. I'll fix the first patch in the next spin. In the meantime, you can apply below quick fix on top of what you tested the issue.
Thanks,
Jae
(quoted diff) +0 -0
b/drivers/media/platform/aspeed-video.c
index c2d4a2e6f20f..034f2f436d76 100644
drivers/media/platform/aspeed-video.c +0 -0
@@ -865,20 +865,14 @@ static void aspeed_video_set_resolution(struct
aspeed_video *video)
size *= 4;
- if (size == video->srcs[0].size / 2) {
- aspeed_video_write(video, VE_SRC1_ADDR,
- video->srcs[0].dma + size);
- } else if (size == video->srcs[0].size) {
- if (!aspeed_video_alloc_buf(video, &video->srcs[1], size))
- goto err_mem;
-
- aspeed_video_write(video, VE_SRC1_ADDR, video->srcs[1].dma);
- } else {
- aspeed_video_free_buf(video, &video->srcs[0]);
+ if (size != video->srcs[0].size) {
+ if (video->srcs[0].size)
+ aspeed_video_free_buf(video, &video->srcs[0]);
+ if (video->srcs[1].size)
+ aspeed_video_free_buf(video, &video->srcs[1]);
if (!aspeed_video_alloc_buf(video, &video->srcs[0], size))
goto err_mem;
-
if (!aspeed_video_alloc_buf(video, &video->srcs[1], size))
goto err_mem;Quoted 10 lines · xiuzhi
Hi Jae,
The bmc serial port will print anusb_ep_queueerrors when reboot
the hostOS.
I can reproduce it by the following steps:
1, Login the bmc webpage ,open the kvm webpage.
2, reboot the host OS
3, Bmc Serial port will print error messages:
[ 680.786134] aspeed-video 1e700000.video: Timed out; first mode detect [ 681.846125] aspeed-video 1e700000.video: Timed out when stopping streaming [ 682.356106] aspeed-video 1e700000.video: Timed out; first mode detect
Looks like you didn't apply this patch:
https://lists.ozlabs.org/pipermail/openbmc/2019-May/016177.html
Quoted 1 line
[ 682.377294] configfs-gadget gadget:
usb_ep_queueerror on int endpoint -108
This is expected because ikvm service will keep sending keyboard and mouse events to host but host disconnects the usb connection while host rebooting. This message is ignorable but if you want to disable printing out of this message in the case, use this:
https://github.com/Intel-BMC/openbmc/blob/intel/meta-openbmc-mods/meta-common/recipes-kernel/linux/linux-aspeed/0049-Suppress-excessive-HID-gadget-error-logs.patch
Thanks,
Jae
Quoted 76 lines
[ 682.896212] aspeed-video 1e700000.video: Timed out; first mode detect
[ 684.917892] configfs-gadget gadget:usb_ep_queueerror on int endpoint -108
[ 685.426159] aspeed-video 1e700000.video: Timed out; first mode detect
4, It will stop the error output when the hostOS start to bootup.[ 739.598840] configfs-gadgetgadget: high-speed config #1: c
[ 739.629961]aspeed_vhub1e6a0000.usb-vhub: status direction
mismatchDoes this output make sense?
Best,
Xiuzhi
------------------ Original ------------------
*From: * "jae.hyun.yoo";<[email protected]>;
*Date: * Jun 1, 2019
*To: * "xiuzhi"<[email protected]>; "openbmc"<[email protected]>; "eajames"<[email protected]>; "joel"<[email protected]>; "andrew"<[email protected]>; *Subject: * Re: [PATCH dev-5.1 4/4] media: aspeed: add a workaround to fix asilicon bug (Jae Hyun Yoo)Quoted 12 lines · xiuzhi
Hi Jae,
I tested this patch ,it works on 1680*1050,but I found an issue:The ikvm webpage will be black screen when you reboot the host after switching solution between 1680*1050 and 800*600 on chrome browser (my chrome version is 65).
you can reproduce it:
1, Set host screen solution to 1680*1050 and save it . ikvm webpage works 2,Set host screen solution to 800*600 and save it. ikvm webpage works 3,Reset host screen solution to 1680*1050 and save it, 4,reboot the host,
5, the ikvm webpage is black screen when boot to Centos GUIHi Xiuzhi,
Checked that the issue isn't related this patch. Actually, that is caused by the first patch of this patch series. Since the patch removes source buffer allocation before mode detection, remaining allocation logic should be changed accordingly, otherwise it can't allocate buffers and eventually causes the issue. I'll fix the first patch in the next spin. In the meantime, you can apply below quick fix on top of what you tested the issue.
Thanks,
Jaedrivers/media/platform/aspeed-video.c +5
-11@@ -865,20 +865,14 @@ static void aspeed_video_set_resolution(struct aspeed_video *video) size *= 4; - if (size == video->srcs[0].size / 2) { - aspeed_video_write(video, VE_SRC1_ADDR, - video->srcs[0].dma + size); - } else if (size == video->srcs[0].size) { - if (!aspeed_video_alloc_buf(video, &video->srcs[1], size)) - goto err_mem; - - aspeed_video_write(video, VE_SRC1_ADDR, video->srcs[1].dma); - } else { - aspeed_video_free_buf(video, &video->srcs[0]); + if (size != video->srcs[0].size) { + if (video->srcs[0].size) + aspeed_video_free_buf(video, &video->srcs[0]); + if (video->srcs[1].size) + aspeed_video_free_buf(video, &video->srcs[1]); if (!aspeed_video_alloc_buf(video, &video->srcs[0], size)) goto err_mem; - if (!aspeed_video_alloc_buf(video, &video->srcs[1], size)) goto err_mem;