From: Al Viro <viro@zeniv.linux.org.uk>
To: Oliver Neukum <oneukum@suse.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
linux-kernel@vger.kernel.org, sndirsch@suse.com,
tzimmermann@suse.com
Subject: Re: 4f5368b5541a902f6596558b05f5c21a9770dd32 causes regression
Date: Wed, 25 Sep 2019 20:47:32 +0100 [thread overview]
Message-ID: <20190925194732.GM26530@ZenIV.linux.org.uk> (raw)
In-Reply-To: <1569439345.3084.5.camel@suse.com>
On Wed, Sep 25, 2019 at 09:22:25PM +0200, Oliver Neukum wrote:
> Hi,
>
> I am seeing a hard lockup during boot with this patch.
> I am using only the laptop's internal display.
> The last message I see is:
>
> kvm: disabled by BIOS
>
> Regards
> Oliver
Shocking as it might seem, most of us do not remember the
sha1 of commits by heart. So it's generally a good idea to
accompany such with something like "drm/kms: Catch mode_object
lifetime errors" (in this case) - makes life easier for folks
trying to decide whether to skip a particular piece of mail/thread
or look into it...
next prev parent reply other threads:[~2019-09-25 19:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-25 19:22 Oliver Neukum
2019-09-25 19:47 ` Al Viro [this message]
2019-09-25 19:48 ` Daniel Vetter
2019-09-30 12:46 ` Oliver Neukum
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=20190925194732.GM26530@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=oneukum@suse.com \
--cc=sndirsch@suse.com \
--cc=tzimmermann@suse.com \
/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
Powered by JetHome