From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: "Jürgen Groß" <jgross@suse.com>
Cc: Denis Efremov <efremov@linux.com>, Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org,
xen-devel <xen-devel@lists.xenproject.org>,
Roman Shaposhnik <roman@zededa.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: Kernel panic on 'floppy' module load, Xen HVM, since 4.19.143
Date: Wed, 30 Sep 2020 10:42:04 +0200 [thread overview]
Message-ID: <20200930084204.GK3962@mail-itl> (raw)
In-Reply-To: <5115e96f-f054-f720-b718-ceef1950f038@suse.com>
[-- Attachment #1: Type: text/plain, Size: 2137 bytes --]
On Tue, Sep 29, 2020 at 04:05:21PM +0200, Jürgen Groß wrote:
> On 29.09.20 14:41, Marek Marczykowski-Górecki wrote:
> > On Tue, Sep 29, 2020 at 03:27:43PM +0300, Denis Efremov wrote:
> > > Hi,
> > >
> > > On 9/28/20 12:36 PM, Marek Marczykowski-Górecki wrote:
> > > > On Mon, Sep 28, 2020 at 07:02:19AM +0200, Jürgen Groß wrote:
> > > > > On 27.09.20 13:14, Marek Marczykowski-Górecki wrote:
> > > > > > Hi all,
> > > > > >
> > > > > > I get kernel panic on 'floppy' module load. If I blacklist the module,
> > > > > > then everything works.
> > > > > > The issue happens in Xen HVM, other virtualization modes (PV, PVH) works
> > > > > > fine. PV dom0 works too. I haven't tried bare metal, but I assume it
> > > > > > works fine too.
> > > > >
> > > > > Could you please try bare metal?
> > > >
> > > > I don't have any hw with floppy controller at hand...
> > > > Booting on what I have, it works, loading floppy just says -ENODEV.
> > >
> > > I saw that the issue was bisected [1] to commit
> > > c330fb1ddc0a ("XEN uses irqdesc::irq_data_common::handler_data to store a
> > > per interrupt XEN data pointer which contains XEN specific information.")
> > >
> > > I have hardware, but I've never worked with Xen. It will take me some time
> > > to set it up and reproduce the problem. I think I will do it in a week.
> >
> > Can you try to boot 4.19.143 (or any other including that commit)
> > directly on the hardware and make sure floppy module is loaded? We do
> > know it's broken in Xen HVM, it would be interested to see if it works
> > without Xen. Even better if you could use the same kernel config:
> > https://gist.github.com/marmarek/1e6a359c9a99af3ed8fc16af0f36d8a6
>
> I think it is not directly related to floppy, but a more general problem
> for HVM guests.
>
> I'm suspecting an issue with legacy IRQs. Could you please try the
> attached patch?
Yes, this fixes the issue.
--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2020-09-30 8:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-27 11:14 Kernel panic on 'floppy' module load, Xen HVM, since 4.19.143 Marek Marczykowski-Górecki
2020-09-28 5:02 ` Jürgen Groß
2020-09-28 9:36 ` Marek Marczykowski-Górecki
2020-09-29 12:27 ` Denis Efremov
2020-09-29 12:41 ` Marek Marczykowski-Górecki
2020-09-29 14:05 ` Jürgen Groß
2020-09-30 8:42 ` Marek Marczykowski-Górecki [this message]
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=20200930084204.GK3962@mail-itl \
--to=marmarek@invisiblethingslab.com \
--cc=axboe@kernel.dk \
--cc=efremov@linux.com \
--cc=jgross@suse.com \
--cc=linux-block@vger.kernel.org \
--cc=roman@zededa.com \
--cc=tglx@linutronix.de \
--cc=xen-devel@lists.xenproject.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).