From: Pavel Machek <pavel@ucw.cz>
To: Thomas Zimmermann <tzimmermann@suse.de>
Cc: intel-gfx@lists.freedesktop.org,
kernel list <linux-kernel@vger.kernel.org>,
dri-devel@lists.freedesktop.org, airlied@redhat.com
Subject: [Intel-gfx] udldrm does not recover from powersave? Re: udldrmfb: causes WARN in i915 on X60 (x86-32)
Date: Thu, 25 Feb 2021 10:53:22 +0100 [thread overview]
Message-ID: <20210225095322.GA5089@amd> (raw)
In-Reply-To: <452585d5-9d18-f5a8-9d6b-6d39aa037480@suse.de>
[-- Attachment #1.1: Type: text/plain, Size: 548 bytes --]
Hi!
> >This is in -next, but I get same behaviour on 5.11; and no, udl does
>
> Thanks for reporting. We are in the process of fixing the issue. The latest
> patch is at [1].
>
Thank you, that fixes the DMA issue, and I can use the udl.
...for a while. Then screensaver blanks laptop screen, udl screen
blanks too. Upon hitting a key, internal screen shows up, udl does
not.
I try rerunning xrandr ... --auto, but could not recover it.
Any ideas?
Best regards,
Pavel
--
http://www.livejournal.com/~pavelmachek
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2021-02-25 9:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 20:09 [Intel-gfx] udldrmfb: causes WARN in i915 on X60 (x86-32) Pavel Machek
2021-02-25 8:11 ` Thomas Zimmermann
2021-02-25 9:53 ` Pavel Machek [this message]
2021-02-25 10:02 ` [Intel-gfx] udldrm does not recover from powersave? " Thomas Zimmermann
2021-02-25 10:15 ` Pavel Machek
2021-02-25 17:07 ` Pavel Machek
2021-02-26 8:48 ` Thomas Zimmermann
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=20210225095322.GA5089@amd \
--to=pavel@ucw.cz \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tzimmermann@suse.de \
/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).