All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Woody Suwalski <terraluna977@gmail.com>
Cc: hch@lst.de, "DRI mailing list" <dri-devel@lists.freedesktop.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"Christian König" <christian.koenig@amd.com>,
	"Deucher, Alexander" <alexander.deucher@amd.com>,
	"Pavel Machek" <pavel@ucw.cz>
Subject: Re: Regression in 5.4 kernel on 32-bit Radeon IBM T40
Date: Thu, 9 Jan 2020 15:14:36 +0100	[thread overview]
Message-ID: <20200109141436.GA22111@lst.de> (raw)
In-Reply-To: <400f6ce9-e360-0860-ca2a-fb8bccdcdc9b@gmail.com>

Hi Woody,

sorry for the late reply, I've been off to a vacation over the holidays.

On Sat, Dec 14, 2019 at 10:17:15PM -0500, Woody Suwalski wrote:
> Regression in 5.4 kernel on 32-bit Radeon IBM T40
> triggered by
> commit 33b3ad3788aba846fc8b9a065fe2685a0b64f713
> Author: Christoph Hellwig <hch@lst.de>
> Date:   Thu Aug 15 09:27:00 2019 +0200
>
> Howdy,
> The above patch has triggered a display problem on IBM Thinkpad T40, where 
> the screen is covered with a lots of random short black horizontal lines, 
> or distorted letters in X terms.
>
> The culprit seems to be that the dma_get_required_mask() is returning a 
> value 0x3fffffff
> which is smaller than dma_get_mask()0xffffffff.That results in 
> dma_addressing_limited()==0 in ttm_bo_device(), and using 40-bits dma 
> instead of 32-bits.

Which is the intended behavior assuming your system has 1GB of memory.
Does it?

> If I hardcode "1" as the last parameter to ttm_bo_device_init() in place of 
> a call to dma_addressing_limited(),the problem goes away.

I'll need some help from the drm / radeon / TTM maintainers if there are
any other side effects from not passing the need_dma32 paramters.
Obviously if the device doesn't have more than 32-bits worth of dram and
no DMA offset we can't feed unaddressable memory to the device.
Unfortunately I have a very hard time following the implementation of
the TTM pool if it does anything else in this case.

  parent reply	other threads:[~2020-01-09 14:14 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-15  3:17 Regression in 5.4 kernel on 32-bit Radeon IBM T40 Woody Suwalski
2019-12-15  3:17 ` Woody Suwalski
2019-12-15 16:04 ` Meelis Roos
2020-01-09 14:14 ` Christoph Hellwig [this message]
2020-01-09 15:12   ` Christian König
2020-01-09 15:12     ` Christian König
2020-01-09 22:40     ` Woody Suwalski
2020-01-09 22:40       ` Woody Suwalski
2020-01-10  2:40       ` Woody Suwalski
2020-01-10  2:40         ` Woody Suwalski
2020-03-14 22:06         ` Thomas Schwinge
2020-03-14 22:06           ` Thomas Schwinge
2020-02-22 16:16     ` Thomas Backlund
2020-02-22 16:16       ` Thomas Backlund
2020-09-16 22:15       ` Alex Deucher
2020-09-16 22:15         ` Alex Deucher

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=20200109141436.GA22111@lst.de \
    --to=hch@lst.de \
    --cc=alexander.deucher@amd.com \
    --cc=christian.koenig@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=terraluna977@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.