All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Steve Sakoman" <steve@sakoman.com>
To: openembedded-core@lists.openembedded.org
Subject: [OE-core][dunfell 14/19] parselogs: ignore floppy error on qemu-system-x86 at boot stage
Date: Fri, 23 Apr 2021 03:58:56 -1000	[thread overview]
Message-ID: <982236ed40f7e1fb912d52155495286fa1ca4757.1619186107.git.steve@sakoman.com> (raw)
In-Reply-To: <cover.1619186107.git.steve@sakoman.com>

From: Yanfei Xu <yanfei.xu@windriver.com>

We can disable floppy drive by BIOS on a hardware, but an empty floppy
drive is connected by default on qemu-system-x86. Linux usually detect
the device and modprode the matched floppy.ko at the boot stage. Due to
we don't specify a floppy deivce in qemu boot arguments, then the errors
about floppy reading comes out.

It is harmless and normal, so we could ignore this error message on
qemux86.

Seen if kernel-modules is included in the image which pulls in the
relavent kernel module.

https://lists.gnu.org/archive/html/qemu-devel/2021-04/msg01402.html

Signed-off-by: Yanfei Xu <yanfei.xu@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
(cherry picked from commit 3359f23ee9351c70997d5e0a17d17d1e47d59623)
Signed-off-by: Steve Sakoman <steve@sakoman.com>
---
 meta/lib/oeqa/runtime/cases/parselogs.py | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/meta/lib/oeqa/runtime/cases/parselogs.py b/meta/lib/oeqa/runtime/cases/parselogs.py
index a1791b5cca..f703927660 100644
--- a/meta/lib/oeqa/runtime/cases/parselogs.py
+++ b/meta/lib/oeqa/runtime/cases/parselogs.py
@@ -88,6 +88,8 @@ qemux86_common = [
     'tsc: HPET/PMTIMER calibration failed',
     "modeset(0): Failed to initialize the DRI2 extension",
     "glamor initialization failed",
+    "blk_update_request: I/O error, dev fd0, sector 0 op 0x0:(READ)",
+    "floppy: error",
 ] + common_errors
 
 ignore_errors = {
-- 
2.25.1


  parent reply	other threads:[~2021-04-23 14:00 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-23 13:58 [OE-core][dunfell 00/19] Patch review Steve Sakoman
2021-04-23 13:58 ` [OE-core][dunfell 01/19] wpa-supplicant: fix CVE-2021-30004 Steve Sakoman
2021-04-23 13:58 ` [OE-core][dunfell 02/19] Revert "externalsrc: Detect code changes in submodules" Steve Sakoman
2021-04-23 13:58 ` [OE-core][dunfell 03/19] externalsrc: Detect code changes in submodules Steve Sakoman
2021-04-23 13:58 ` [OE-core][dunfell 04/19] oeqa/selftest: Hardcode test assumptions about heartbeat event timings Steve Sakoman
2021-04-23 13:58 ` [OE-core][dunfell 05/19] oeqa/selftest: Ensure packages classes are set correctly for maintainers test Steve Sakoman
2021-04-23 13:58 ` [OE-core][dunfell 06/19] insane: clean up some more warning messages Steve Sakoman
2021-04-23 13:58 ` [OE-core][dunfell 07/19] sanity: Add error check for '%' in build path Steve Sakoman
2021-04-23 13:58 ` [OE-core][dunfell 08/19] sanity: Further improve directory sanity tests Steve Sakoman
2021-04-23 13:58 ` [OE-core][dunfell 09/19] lib/oe/terminal: Fix tmux new-session on older tmux versions (<1.9) Steve Sakoman
2021-04-23 13:58 ` [OE-core][dunfell 10/19] pseudo: Upgrade to add trailing slashes ignore path fix Steve Sakoman
2021-04-23 13:58 ` [OE-core][dunfell 11/19] kmod: do not symlink config.guess/config.sub during autoreconf Steve Sakoman
2021-04-23 13:58 ` [OE-core][dunfell 12/19] libtool: make sure autoheader run before automake Steve Sakoman
2021-04-23 13:58 ` [OE-core][dunfell 13/19] groff: not ship /usr/bin/grap2graph Steve Sakoman
2021-04-23 13:58 ` Steve Sakoman [this message]
2021-04-23 13:58 ` [OE-core][dunfell 15/19] ca-certificates: Fix openssl runtime cert dependencies Steve Sakoman
2021-04-23 13:58 ` [OE-core][dunfell 16/19] linux-yocto/5.4: update to v5.4.109 Steve Sakoman
2021-04-23 13:58 ` [OE-core][dunfell 17/19] linux-yocto/5.4: update to v5.4.111 Steve Sakoman
2021-04-23 13:59 ` [OE-core][dunfell 18/19] linux-yocto/5.4: update to v5.4.112 Steve Sakoman
2021-04-23 13:59 ` [OE-core][dunfell 19/19] linux-yocto/5.4: fix arm defconfig warnings Steve Sakoman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=982236ed40f7e1fb912d52155495286fa1ca4757.1619186107.git.steve@sakoman.com \
    --to=steve@sakoman.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.