On Wed, 19 Dec 2018 20:17:42 +0100 Michael Mueller <mimu@xxxxxxxxxxxxx> wrote: > Make sure the debug feature and its allocated resources get > released upon unsuccessful architecture initialization. > > A related indication of the issue will be reported as kernel > message. > > Signed-off-by: Michael Mueller <mimu@xxxxxxxxxxxxx> > Reviewed-by: Cornelia Huck <cohuck@xxxxxxxxxx> > Reviewed-by: Pierre Morel <pmorel@xxxxxxxxxxxxx> > Reviewed-by: David Hildenbrand <david@xxxxxxxxxx> > Message-Id: <20181130143215.69496-2-mimu@xxxxxxxxxxxxx> > Signed-off-by: Christian Borntraeger <borntraeger@xxxxxxxxxx> > --- > Documentation/kmsg/s390/kvm | 12 ++++++++++++ > arch/s390/kvm/kvm-s390.c | 17 ++++++++++++++--- > 2 files changed, 26 insertions(+), 3 deletions(-) > create mode 100644 Documentation/kmsg/s390/kvm > > diff --git a/Documentation/kmsg/s390/kvm b/Documentation/kmsg/s390/kvm > new file mode 100644 > index 000000000000..76ffe2012254 > --- /dev/null > +++ b/Documentation/kmsg/s390/kvm > @@ -0,0 +1,12 @@ > +/*? > + * Text: "Failed to register FLIC rc=%d\n" > + * Severity: Error > + * Parameter: > + * @1: return code of the FLIC registration call > + * Description: > + * The registration of the FLIC (Floating Interrupt Controller Interface) > + * was not successful. > + * User action: > + * If this problem persists after a reload of the kvm kernel module, gather > + * Linux debug data and contact your support organization. > + */ Hm, it seems that the kmsg stuff crept in there again...
