From: Phillip Susi <phill@thesusis.net>
To: xen-devel@lists.xenproject.org
Subject: Xen Virtual Keyboard modalias breaking uevents
Date: Thu, 29 Apr 2021 15:08:21 -0400 [thread overview]
Message-ID: <87o8dw52jc.fsf@vps.thesusis.net> (raw)
So I have finally drilled down to the modalias for the Xen Virtual
Keyboard driver being so long ( over 2KB ) that it causes an -ENOMEM
when trying to add it to the environment for uevents. This causes
coldplug to fail, which causes the script doing coldplug as part of the
debian-installer init to fail, which causes a kernel panic when init
exits, which then for reasons I have yet to understand, causes the Xen
domU to reboot.
Why is this modalias so huge? Can we pare it down, or or is there
another solution to get uevents working on this device again? Maybe the
environment block size needs to be increased? I don't know.
next reply other threads:[~2021-04-29 19:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-29 19:08 Phillip Susi [this message]
2021-04-29 20:10 ` Xen Virtual Keyboard modalias breaking uevents Phillip Susi
2021-04-29 22:29 ` Dmitry Torokhov
2021-04-30 0:11 ` Phillip Susi
2021-04-30 0:35 ` Dmitry Torokhov
2021-04-30 0:57 ` Phillip Susi
2021-04-30 13:16 ` Phillip Susi
2021-05-06 14:36 ` [PATCH] Xen Keyboard: don't advertise every key known to man Phillip Susi
2021-05-06 20:26 ` Dmitry Torokhov
2021-05-18 16:20 ` Phillip Susi
2021-05-18 17:13 ` Phillip Susi
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=87o8dw52jc.fsf@vps.thesusis.net \
--to=phill@thesusis.net \
--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).