From: Michael Tokarev <1423528@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1423528] Re: setting unsupported timeout for i6300esb watchdog causes hw reset
Date: Sat, 08 Aug 2020 07:48:44 -0000 [thread overview]
Message-ID: <159687292447.21733.1943716827123045705.malone@chaenomeles.canonical.com> (raw)
In-Reply-To: 20150219122612.20987.32403.malonedeb@gac.canonical.com
There's nothing changed in i6300esb about this issue. I can reproduce it
exactly the same way with current qemu 5.1-tobe
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1423528
Title:
setting unsupported timeout for i6300esb watchdog causes hw reset
Status in QEMU:
Incomplete
Bug description:
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778291
Version: 2.1
systemd utilizes existing watchdog hardware and set's a 10min timer on reboot.
The i6300esb under qemu doesn't like such a timeout, and immediately resets the hardware:
The last message one gets is
[ 9.402243] i6300esb: Unexpected close, not stopping watchdog!
The linked bug report contains information how this bug can easily be reproduced.
With any image using a recent enough systemd as PID 1 you should be able to reproduce it by running
qemu-system-x86_64 -curses -enable-kvm -device i6300esb -watchdog-
action reset -hda <image with systemd>
I'm uncertain if this is a qemu or kernel/driver bug. If the latter, please re-assign the bug as necessary.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1423528/+subscriptions
next prev parent reply other threads:[~2020-08-08 8:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-19 12:26 [Qemu-devel] [Bug 1423528] [NEW] setting unsupported timeout for i6300esb watchdog causes hw reset Michael Biebl
2020-08-07 17:56 ` [Bug 1423528] " Thomas Huth
2020-08-08 7:48 ` Michael Tokarev [this message]
2020-08-08 8:13 ` Michael Tokarev
2021-05-04 5:44 ` Thomas Huth
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=159687292447.21733.1943716827123045705.malone@chaenomeles.canonical.com \
--to=1423528@bugs.launchpad.net \
--cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).