14528 2021-08-26 14:16:22 +0000 remove floppy controller from qemu 2026-04-30 15:35:14 +0000 1 1 10 QA/Testing Runtime Testing oeqa/runtime unspecified x86 Multiple RESOLVED WONTFIX Medium+ normal 5.99 1 richard.purdie unassigned akuster808 alexandre.belloni randy.macleod ross.burton sakib.sajal tgamblin --- --- No (bug/feature does not impact docs) oldest_to_newest 91274 0 richard.purdie 2021-08-26 14:16:22 +0000 Failure in parselogs.ParseLogsTest.test_parselogs in testimage. https://autobuilder.yoctoproject.org/typhoon/#/builders/109/builds/2800/steps/13/logs/stdio ----------------------- Central error: [ 6.403477] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4) *********************** [ 1.142512] uhci_hcd 0000:00:1d.1: UHCI Host Controller [ 1.143701] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3 [ 1.146046] uhci_hcd 0000:00:1d.1: irq 17, io base 0x0000c120 [ 1.401466] ata4: SATA link down (SStatus 0 SControl 300) [ 1.403368] ata5: SATA link down (SStatus 0 SControl 300) [ 1.404779] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 1.406640] ata1: SATA link down (SStatus 0 SControl 300) [ 1.407984] ata2: SATA link down (SStatus 0 SControl 300) [ 1.409744] ata6: SATA link down (SStatus 0 SControl 300) [ 6.402041] ata3.00: qc timeout (cmd 0xa1) [ 6.403477] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 6.713309] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 12.184408] ata3.00: ATAPI: QEMU DVD-ROM, 2.5+, max UDMA/100 [ 12.185005] hub 3-0:1.0: USB hub found [ 12.186590] ata3.00: applying bridge limits [ 12.187754] hub 3-0:1.0: 2 ports detected [ 12.190534] ata3.00: configured for UDMA/100 [ 12.192060] uhci_hcd 0000:00:1d.2: UHCI Host Controller [ 12.194467] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4 [ 12.196766] scsi 2:0:0:0: CD-ROM QEMU QEMU DVD-ROM 2.5+ PQ: 0 ANSI: 5 [ 12.197053] uhci_hcd 0000:00:1d.2: irq 18, io base 0x0000c140 *********************** 1 errors found in logs. Looks to be the same as: https://autobuilder.yoctoproject.org/typhoon/#/builders/109/builds/2777/steps/13/logs/stdio ----------------------- Central error: [ 23.008847] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4) *********************** [ 17.653191] i2c i2c-0: Memory type 0x07 not supported yet, not instantiating SPD [ 17.654208] device-mapper: ioctl: 4.43.0-ioctl (2020-10-01) initialised: dm-devel@redhat.com [ 17.903178] ata1: SATA link down (SStatus 0 SControl 300) [ 17.903924] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 17.905158] ata5: SATA link down (SStatus 0 SControl 300) [ 17.906119] ata6: SATA link down (SStatus 0 SControl 300) [ 17.907085] ata2: SATA link down (SStatus 0 SControl 300) [ 17.908007] ata4: SATA link down (SStatus 0 SControl 300) [ 17.919040] usb 1-1: new high-speed USB device number 2 using ehci-pci [ 23.008094] ata3.00: qc timeout (cmd 0xa1) [ 23.008847] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 23.325009] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 23.460602] input: PS/2 Generic Mouse as /devices/platform/i8042/serio1/input/input3 [ 23.461067] ata3.00: ATAPI: QEMU DVD-ROM, 2.5+, max UDMA/100 [ 23.461467] intel_pstate: CPU model not supported [ 23.462125] ata3.00: applying bridge limits [ 23.465032] sdhci: Secure Digital Host Controller Interface driver [ 23.465465] ata3.00: configured for UDMA/100 [ 23.466070] sdhci: Copyright(c) Pierre Ossman [ 23.466924] scsi 2:0:0:0: CD-ROM QEMU QEMU DVD-ROM 2.5+ PQ: 0 ANSI: 5 [ 23.467083] sdhci-pltfm: SDHCI platform and OF driver helper 91290 1 bruce.ashfield 2021-08-26 16:34:03 +0000 Sent to the list: commit c9028271e134493285c4f5e952fe9f482e079c7f (HEAD -> master) Author: Bruce Ashfield <bruce.ashfield@gmail.com> Date: Thu Aug 26 12:28:07 2021 -0400 parselogs.py: ignore intermittent CD/DVDROM identification failure We don't use the CD/DVD ROM drive in any of our tests, but it periodically fails discovery and that leads to a QA error: [ 6.403477] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4) The only way to disable the optical ROM drive in qemu is to use the '-nodefaults' option, which disables the CDROM (among other things). We can't be sure that none of our tests, or extended users are relying on default devices, so using that option is more of a risk than adding the message to our ignore list. To date, no one has sent a patch to just disable the optical drive (either in qemu or the BIOS), but that is something we could consider in the future. [YOCTO #14528] Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> 91334 2 richard.purdie 2021-09-03 08:09:11 +0000 This happened again: https://autobuilder.yoctoproject.org/typhoon/#/builders/72/builds/3960/steps/15/logs/stdio with the patch applied. Looking at the patch I think it needs to be for both qemux86 and qemux86-64 in the common section? 91335 3 richard.purdie 2021-09-03 08:24:07 +0000 I've sent a patch to move it to common section. 91368 4 randy.macleod 2021-09-09 14:47:25 +0000 RP thinks we should get qemu upstream to remove the floppy disk controller. The parse log issue has been fixe dbut keeping this defect for more work. 93228 5 akuster808 2022-05-05 14:52:39 +0000 is this the fix? https://git.yoctoproject.org/poky/commit/meta/recipes-devtools/qemu?h=master-next&id=42ed634570c6633e1bd2dd28c377a2c1fd1ba961 93231 6 ross.burton 2022-05-05 15:02:43 +0000 No, that's just PS/2 devices. 96095 7 randy.macleod 2023-07-26 21:22:05 +0000 Bulk move of 64 bugs to 4.3 M3 after a quick review. If a bug is actually fixed, please add a commit link and resolve it. -- Randy for YP bug team. 96480 8 tgamblin 2023-09-14 16:45:06 +0000 Moved to M4. 97052 9 randy.macleod 2023-10-30 15:29:08 +0000 Bulk move to 5.0 M1. -- Randy 97686 10 randy.macleod 2023-12-21 23:28:31 +0000 Bulk move of 52 5.0-M1 bugs to M2. 97993 11 randy.macleod 2024-01-25 14:28:45 +0000 Bulk move of bugs owned by "unassigned" from 5.0-M2 to 5.0-M3. 98287 12 randy.macleod 2024-02-22 19:53:20 +0000 Bulk move of bugs from 5.0-M3 to 5.99. The bugs in this list are all unassigned and are ones that I consider to be nice to do some time but not essential track from milestone to milestone in 5.0 or 5.1. We agreed on this bug handling approach in the YP bug review on Feb 22, 2024. If you disagree, please move back to a 5.[012...]-M* milestone. 105330 13 richard.purdie 2026-04-30 15:35:14 +0000 We stopped seeing that error and removing the FDC turns out to be quite tricky so we are unlikely to bother now.