mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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, rodrigo.vivi@intel.com,
	airlied@redhat.com, sean@poorly.run
Subject: Re: udldrm does not recover from powersave? Re: udldrmfb: causes WARN in i915 on X60 (x86-32)
Date: Thu, 25 Feb 2021 18:07:26 +0100	[thread overview]
Message-ID: <20210225170726.GA31110@duo.ucw.cz> (raw)
In-Reply-To: <4fb31ea5-ef20-4752-4782-8d9f1afdf51d@suse.de>

[-- Attachment #1: Type: text/plain, Size: 1816 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?
> 
> Did it work before the regression?
> 
> For testing, could you please remove the fix and then do
> 
>   git revert 6eb0233ec2d0
> 
> This would restore the old version. Please report back on the
> results.

Ok, I went to 7f206cf3ec2b with 6eb0233ec2d0 reverted. That fails to
build:

drivers/usb/core/message.c: In function ‘usb_set_configuration’:
drivers/usb/core/message.c:2100:12: error: ‘struct device’ has no member named ‘dma_pfn_offset’
 2100 |   intf->dev.dma_pfn_offset = dev->dev.dma_pfn_offset;
      |            ^
drivers/usb/core/message.c:2100:38: error: ‘struct device’ has no member named ‘dma_pfn_offset’
 2100 |   intf->dev.dma_pfn_offset = dev->dev.dma_pfn_offset;
      |                                      ^
  CC      drivers/net/ethernet/intel/e1000e/param.o
make[3]: *** [scripts/Makefile.build:271: drivers/usb/core/message.o]
Error 1

So I tried to go to bad commit's parent:

git checkout 6eb0233ec2d0^
git log
commit cf141ae989e2ff119cd320326da5923b480d1641
    ARM/keystone: move the DMA offset handling under ifdef CONFIG_ARM_LPAE

But that resulted in lockup soon after "--setprovidersource" command
was isued.

Best regards,
									Pavel

-- 
http://www.livejournal.com/~pavelmachek

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  parent reply	other threads:[~2021-02-25 17:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-24 20:09 Pavel Machek
2021-02-25  8:11 ` Thomas Zimmermann
2021-02-25  9:53   ` udldrm does not recover from powersave? " Pavel Machek
2021-02-25 10:02     ` Thomas Zimmermann
2021-02-25 10:15       ` Pavel Machek
2021-02-25 17:07       ` Pavel Machek [this message]
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=20210225170726.GA31110@duo.ucw.cz \
    --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=rodrigo.vivi@intel.com \
    --cc=sean@poorly.run \
    --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

all inboxes | Powered by JetHome®