https://bugzilla.kernel.org/show_bug.cgi?id=204181
--- Comment #32 from Sergey Kondakov (virtuous...@gmail.com) ---
Just got exactly the same 0010:amdgpu_vm_update_directories+0xe7/0x260
dereference immediately on login even with PageFlip & TearFree disabled and
ShadowPrimary NOT enabled. Even
https://bugs.freedesktop.org/show_bug.cgi?id=110674
--- Comment #114 from ReddestDream ---
5. Tom B., it is probably worth getting a full dmesg with your two monitors in
on a relatively new 5.2.x kernel using at least: amdgpu.dc_log=1 drm.debug=0x1e
log_buf_len=2M
And anything else you might
https://bugs.freedesktop.org/show_bug.cgi?id=110674
--- Comment #113 from ReddestDream ---
4.
> Given that two different versions of the code produce the same result, my
> hunch is that the problem is B. The card is not in a state where it's able to
> receive power changes.
Something to
https://bugs.freedesktop.org/show_bug.cgi?id=110674
--- Comment #112 from ReddestDream ---
More ideas:
3. Looking through the crash in sehellion's comment 45:
gfx_v9_0_ring_test_ring+0x19e/0x230 [amdgpu]
amdgpu_ring_test_helper+0x1e/0x90 [amdgpu]
gfx_v9_0_hw_fini+0x299/0x690 [amdgpu]
https://bugs.freedesktop.org/show_bug.cgi?id=110674
--- Comment #111 from ReddestDream ---
A few other ideas to ponder:
1. Looking into DPM, I found this commit for 5.1-rc1 that looks interesting:
https://github.com/torvalds/linux/commit/7ca881a8651bdeffd99ba8e0010160f9bf60673e
Looks like it
On Fri, Aug 16, 2019 at 5:11 PM Christoph Hellwig wrote:
>
> On Mon, Aug 12, 2019 at 12:42:30PM -0700, Ralph Campbell wrote:
> >
> > On 8/10/19 4:13 AM, Christoph Hellwig wrote:
> >> On something vaguely related to this patch:
> >>
> >> You use the NVIF_VMM_PFNMAP_V0_V* defines from
Hi Daniel,
On Sat, Aug 17, 2019 at 02:30:08AM +0300, Laurent Pinchart wrote:
> On Wed, Aug 14, 2019 at 07:02:29PM +0200, Daniel Vetter wrote:
> > On Wed, Aug 14, 2019 at 04:30:57PM +0300, Laurent Pinchart wrote:
> >> On Wed, Aug 14, 2019 at 03:03:29PM +0200, Daniel Vetter wrote:
> >>> On Thu, Aug
Hi Daniel,
On Wed, Aug 14, 2019 at 07:02:29PM +0200, Daniel Vetter wrote:
> On Wed, Aug 14, 2019 at 04:30:57PM +0300, Laurent Pinchart wrote:
> > On Wed, Aug 14, 2019 at 03:03:29PM +0200, Daniel Vetter wrote:
> >> On Thu, Aug 08, 2019 at 09:36:31PM +0300, Laurent Pinchart wrote:
> >>> On Thu, Aug
https://bugs.freedesktop.org/show_bug.cgi?id=110674
--- Comment #110 from ReddestDream ---
> 1. The functions in vega20_ppt.c are used with this new patch so that answers
> my question from earlier, that's what this file is for and why it contains
> similar/identical functions.
I was hoping
On Sat, 2019-06-29 at 17:39 +0200, Daniel Vetter wrote:
> On Fri, Jun 28, 2019 at 7:24 PM Sean Paul wrote:
> > On Fri, Jun 14, 2019 at 08:17:23AM +0200, Daniel Vetter wrote:
> > > Only dynamic mode objects, i.e. those which are refcounted and
> > > have a free
> > > callback, can be added while
https://bugs.freedesktop.org/show_bug.cgi?id=22
--- Comment #19 from Brian Schott ---
I haven't had a lot of time to work on this, but I do have one more data point:
Mesa 19.1.4 has no corruption in Dolphin but still requires the nodcc
workaround with kernel 5.2.6.
--
You are receiving
https://bugs.freedesktop.org/show_bug.cgi?id=110674
--- Comment #109 from Tom B ---
Created attachment 145080
--> https://bugs.freedesktop.org/attachment.cgi?id=145080=edit
dmesg with amdgpu.dpm=2
> Tom B., did you try booting with amdgpu.dpm=1 or amdgpu.dpm=2 (default is
> generally -1 for
From: Colin Ian King
Currently the pointer init_data is dereferenced on the assignment
of fw_info before init_data is sanity checked to see if it is null.
Fix te potential null pointer dereference on init_data by only
performing dereference after it is null checked.
Addresses-Coverity:
https://bugs.freedesktop.org/show_bug.cgi?id=111412
--- Comment #3 from Alfie Day ---
Created attachment 145079
--> https://bugs.freedesktop.org/attachment.cgi?id=145079=edit
lspci
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=111412
--- Comment #2 from Alfie Day ---
trek00 from IRC found this bug report:
https://bugs.freedesktop.org/show_bug.cgi?id=104412#c14
which mentions running these commands, which seems to work and enable 4k60 over
HDMI.
xrandr --newmode "mymode"
On Fri, 2019-08-16 at 21:29 +, Patchwork wrote:
> == Series Details ==
>
> Series: drm/connector: Allow max possible encoders to attach to a
> connector (rev2)
> URL : https://patchwork.freedesktop.org/series/62743/
> State : warning
>
> == Summary ==
>
> $ dim sparse origin/drm-tip
>
https://bugs.freedesktop.org/show_bug.cgi?id=111412
--- Comment #1 from Alfie Day ---
Someone on IRC said I should mention I was able to achieve 4k 60hz with a
DisplayPort cable to the monitor (sadly this doesn't get me 4k 60hz on my TV,
which only has HDMI)
--
You are receiving this mail
https://bugs.freedesktop.org/show_bug.cgi?id=111412
Bug ID: 111412
Summary: 4k 60hz unavailable RX 560 over HDMI
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Kernel is the dmesg from the kernel I run on a daily basis.
On 8/16/19, Laurent Pinchart wrote:
> Hi Randy,
>
> On Thu, Aug 15, 2019 at 08:10:03PM -0700, Randy Dunlap wrote:
>> [adding mailing lists etc. with Nathaniel's test info]
>>
>> On 8/15/19 7:21 PM, Nathaniel Russell wrote:
>> > Well i
On 8/16/19 10:28 AM, Jason Gunthorpe wrote:
On Fri, Aug 16, 2019 at 10:21:41AM -0700, Dan Williams wrote:
We can do a get_dev_pagemap inside the page_walk and touch the pgmap,
or we can do the 'device mutex && retry' pattern and touch the pgmap
in the driver, under that lock.
However in all
On Fri, Aug 16, 2019 at 09:47:54PM +0200, Uwe Kleine-König wrote:
> On Fri, Aug 16, 2019 at 10:51:57AM -0700, Matthias Kaehlcke wrote:
> > Hi Uwe,
> >
> > On Fri, Aug 16, 2019 at 06:51:48PM +0200, Uwe Kleine-König wrote:
> > > On Tue, Jul 09, 2019 at 12:00:05PM -0700, Matthias Kaehlcke wrote:
> >
https://bugs.freedesktop.org/show_bug.cgi?id=110674
--- Comment #108 from ReddestDream ---
> Booting with amdgpu.dpm=0 on 5.2.7 works.
Tom B., did you try booting with amdgpu.dpm=1 or amdgpu.dpm=2 (default is
generally -1 for automatic)? Seems like one of those might enable the new
experimental
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #105 from magist3r ---
(In reply to reject5514 from comment #103)
> I have this problem on Archlinux 5.2.8-arch1-1-ARCH when connected 2
> monitors(1920x1080 @ 60Hz) and amdgpu.ppfeaturemask=0x option
> enabled. Patch didn't
https://bugzilla.kernel.org/show_bug.cgi?id=204599
Evgeny Shvits (tony.da...@gmail.com) changed:
What|Removed |Added
Regression|No |Yes
https://bugzilla.kernel.org/show_bug.cgi?id=204599
--- Comment #4 from Evgeny Shvits (tony.da...@gmail.com) ---
Created attachment 284469
--> https://bugzilla.kernel.org/attachment.cgi?id=284469=edit
dmesg 5.2.8 after clean boot
run "darktable" application what use OpenCL
--
You are
Hi Bharath,
Thanks for taking the time to try to fix this report.
However, this doesn't look right.
On Fri, 2019-08-16 at 23:30 +0530, Bharath Vedartham wrote:
> This patch fixes a memory leak bug reported by syzbot. Link to the
> bug is given at [1].
>
> A local variable name is used to hold
On Fri, Aug 16, 2019 at 4:14 AM Wen He wrote:
>
> Add optional property node 'arm,malidp-arqos-value' for the Mali DP500.
> This property describe the ARQoS levels of DP500's QoS signaling.
>
> Signed-off-by: Wen He
> ---
> change in v3:
> - correction the describe of the node
>
>
From: Dhinakaran Pandiyan
Currently we restrict the number of encoders that can be linked to
a connector to 3, increase it to match the maximum number of encoders
that can be initialized(32).
To more effiently do that lets switch from an array of encoder ids to
bitmask.
Also removing the
On Fri, Aug 16, 2019 at 10:51:57AM -0700, Matthias Kaehlcke wrote:
> Hi Uwe,
>
> On Fri, Aug 16, 2019 at 06:51:48PM +0200, Uwe Kleine-König wrote:
> > On Tue, Jul 09, 2019 at 12:00:05PM -0700, Matthias Kaehlcke wrote:
> > > Backlight brightness curves can have different shapes. The two main
> > >
https://bugzilla.kernel.org/show_bug.cgi?id=204599
--- Comment #3 from Evgeny Shvits (tony.da...@gmail.com) ---
Created attachment 284467
--> https://bugzilla.kernel.org/attachment.cgi?id=284467=edit
dmidecode
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=204599
--- Comment #2 from Evgeny Shvits (tony.da...@gmail.com) ---
Created attachment 284465
--> https://bugzilla.kernel.org/attachment.cgi?id=284465=edit
dmesg hang on 5.2.2
--
You are receiving this mail because:
You are watching the assignee of
https://bugzilla.kernel.org/show_bug.cgi?id=204599
--- Comment #1 from Evgeny Shvits (tony.da...@gmail.com) ---
Created attachment 284463
--> https://bugzilla.kernel.org/attachment.cgi?id=284463=edit
dmesg with hang on 5.2.8 kernel
--
You are receiving this mail because:
You are watching the
https://bugzilla.kernel.org/show_bug.cgi?id=204599
Bug ID: 204599
Summary: amdgpu: RX 560 randomly hangs with kernel >= 5.1
Product: Drivers
Version: 2.5
Kernel Version: 5.2.8
Hardware: x86-64
OS: Linux
Tree:
Quoting Daniel Vetter (2019-08-16 20:07:24)
> On Fri, Aug 16, 2019 at 9:02 PM Koenig, Christian
> wrote:
> >
> > Am 16.08.19 um 17:21 schrieb Chris Wilson:
> > > Currently dma_fence_signal() tries to avoid the spinlock and only takes
> > > it if absolutely required to walk the callback list.
https://bugs.freedesktop.org/show_bug.cgi?id=111244
--- Comment #27 from mib...@gmx.at ---
fwiw downgrading to 5.1.16 seems to fix the issue here too
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
Hi Laurent.
On Fri, Aug 16, 2019 at 09:39:05PM +0300, Laurent Pinchart wrote:
> Hi Sam,
>
> On Fri, Aug 16, 2019 at 07:31:05PM +0200, Sam Ravnborg wrote:
> > Hi Laurent
> >
> > Thanks for beating me on this!
> >
> > On Fri, Aug 16, 2019 at 03:22:27PM +0300, Laurent Pinchart wrote:
> > >
Hi all
On Fri, Aug 16, 2019 at 03:22:26PM +0300, Laurent Pinchart wrote:
> Hello,
>
> The patch series "[PATCH v4 0/9] DRM panel drivers for omapdrm" added
> new DRM panel drivers for a set of panels used on OMAP platforms, with
> the omapdrm and omapfb2 drivers. Both those drivers contain
>
Am 16.08.19 um 20:59 schrieb Brian Welty:
> ttm_bo_pipeline_move needlessly duplicates code. Refactor this to
> instead call ttm_bo_move_accel_cleanup.
>
> Signed-off-by: Brian Welty
At least of hand that looks valid to me, Reviewed-by: Christian König
for now.
Regards,
Christian.
>
> ---
>
On Fri, Aug 16, 2019 at 9:02 PM Koenig, Christian
wrote:
>
> Am 16.08.19 um 17:21 schrieb Chris Wilson:
> > Currently dma_fence_signal() tries to avoid the spinlock and only takes
> > it if absolutely required to walk the callback list. However, to allow
> > for some users to surreptitiously
Am 16.08.19 um 17:21 schrieb Chris Wilson:
> Currently dma_fence_signal() tries to avoid the spinlock and only takes
> it if absolutely required to walk the callback list. However, to allow
> for some users to surreptitiously insert lazy signal callbacks that
> do not depend on enabling the
ttm_bo_pipeline_move needlessly duplicates code. Refactor this to
instead call ttm_bo_move_accel_cleanup.
Signed-off-by: Brian Welty
---
Builds but otherwise currently untested.
Came across this duplication and thought would see if others cared
to see it cleaned up this way or not.
On Fri, Aug 16, 2019 at 4:31 PM Corentin Labbe
wrote:
> On Wed, Aug 14, 2019 at 07:49:27PM +0200, Daniel Vetter wrote:
> > On Wed, Aug 14, 2019 at 04:50:33PM +0200, Corentin Labbe wrote:
> > > Hello
> > >
> > > Since lot of release (at least since 4.19), I hit the following error
> > > message:
Hi Sam,
On Fri, Aug 16, 2019 at 07:31:05PM +0200, Sam Ravnborg wrote:
> Hi Laurent
>
> Thanks for beating me on this!
>
> On Fri, Aug 16, 2019 at 03:22:27PM +0300, Laurent Pinchart wrote:
> > Standard DRM panel drivers for several panels used by omapfb2 are now
> > available. Their module name
https://bugs.freedesktop.org/show_bug.cgi?id=104602
--- Comment #22 from Marek Olšák ---
Connor, the hardware manages the scratch buffer alloc/dealloc. You don't have
to allocate more than one.
The problem with Civ VI is that VGPR indexing has never been properly
implemented for gfx9 in LLVM.
This patch fixes a memory leak bug reported by syzbot. Link to the
bug is given at [1].
A local variable name is used to hold the copied user buffer string
using strndup_user. strndup_user allocates memory using
kmalloc_track_caller in memdup_user. This kmalloc allocation needs to be
followed by
On Fri, Aug 16, 2019 at 04:54:18PM +0100, Daniel Thompson wrote:
> On 07/08/2019 21:15, Matthias Kaehlcke wrote:
> > On Tue, Jul 09, 2019 at 12:00:05PM -0700, Matthias Kaehlcke wrote:
> > > Backlight brightness curves can have different shapes. The two main
> > > types are linear and non-linear
Hi Uwe,
On Fri, Aug 16, 2019 at 06:51:48PM +0200, Uwe Kleine-König wrote:
> On Tue, Jul 09, 2019 at 12:00:05PM -0700, Matthias Kaehlcke wrote:
> > Backlight brightness curves can have different shapes. The two main
> > types are linear and non-linear curves. The human eye doesn't
> > perceive
Hi Laurent
Thanks for beating me on this!
On Fri, Aug 16, 2019 at 03:22:27PM +0300, Laurent Pinchart wrote:
> Standard DRM panel drivers for several panels used by omapfb2 are now
> available. Their module name clashes with the modules from
> drivers/gpu/drm/omapdrm/displays/, part of the
On Fri, Aug 16, 2019 at 5:24 AM Jason Gunthorpe wrote:
>
> On Thu, Aug 15, 2019 at 08:54:46PM -0700, Dan Williams wrote:
>
> > > However, this means we cannot do any processing of ZONE_DEVICE pages
> > > outside the driver lock, so eg, doing any DMA map that might rely on
> > >
On Wed, Aug 14, 2019 at 10:20:23PM +0200, Daniel Vetter wrote:
> Just a bit of paranoia, since if we start pushing this deep into
> callchains it's hard to spot all places where an mmu notifier
> implementation might fail when it's not allowed to.
>
> Inspired by some confusion we had discussing
On Tue, Jul 09, 2019 at 12:00:05PM -0700, Matthias Kaehlcke wrote:
> Backlight brightness curves can have different shapes. The two main
> types are linear and non-linear curves. The human eye doesn't
> perceive linearly increasing/decreasing brightness as linear (see
> also 88ba95bedb79
On Fri, Aug 16, 2019 at 4:38 PM Jason Gunthorpe wrote:
>
> On Fri, Aug 16, 2019 at 04:11:34PM +0200, Daniel Vetter wrote:
> > Also, aside from this patch (which is prep for the next) and some
> > simple reordering conflicts they're all independent. So if there's no
> > way to paint this bikeshed
The pull request you sent on Fri, 16 Aug 2019 14:21:56 +1000:
> git://anongit.freedesktop.org/drm/drm tags/drm-fixes-2019-08-16
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/ec037ac244c070f9eedcdf5cdb23bd817e7b8cf4
Thank you!
--
Deet-doot-dot, I am a bot.
Am 16.08.19 um 17:21 schrieb Chris Wilson:
> Before we notify the fence signal callback, we remove the cb from the
> list. However, since we are processing the entire list from underneath
> the spinlock, we do not need to individual delete each element, but can
> simply reset the link and the
On 2019-08-15 8:54 p.m., Jason Gunthorpe wrote:
> On Thu, Aug 15, 2019 at 08:52:56PM +, Yang, Philip wrote:
>> hmm_range_fault may return NULL pages because some of pfns are equal to
>> HMM_PFN_NONE. This happens randomly under memory pressure. The reason is
>> for swapped out page pte path,
On 07/08/2019 21:15, Matthias Kaehlcke wrote:
On Tue, Jul 09, 2019 at 12:00:05PM -0700, Matthias Kaehlcke wrote:
Backlight brightness curves can have different shapes. The two main
types are linear and non-linear curves. The human eye doesn't
perceive linearly increasing/decreasing brightness
czw., 8 sie 2019 o 10:17 Bartosz Golaszewski napisał(a):
>
> śr., 24 lip 2019 o 10:25 Bartosz Golaszewski napisał(a):
> >
> > From: Bartosz Golaszewski
> >
> > While working on my other series related to gpio-backlight[1] I noticed
> > that we could simplify the driver if we made the only user
Currently dma_fence_signal() tries to avoid the spinlock and only takes
it if absolutely required to walk the callback list. However, to allow
for some users to surreptitiously insert lazy signal callbacks that
do not depend on enabling the signaling mechanism around every fence,
we always need to
Before we notify the fence signal callback, we remove the cb from the
list. However, since we are processing the entire list from underneath
the spinlock, we do not need to individual delete each element, but can
simply reset the link and the entire list.
Signed-off-by: Chris Wilson
Cc: Daniel
On Fri, Aug 16, 2019 at 11:31:45AM -0300, Jason Gunthorpe wrote:
> On Fri, Aug 16, 2019 at 02:26:25PM +0200, Michal Hocko wrote:
> > On Fri 16-08-19 09:19:06, Jason Gunthorpe wrote:
> > > On Fri, Aug 16, 2019 at 10:10:29AM +0200, Michal Hocko wrote:
> > > > On Thu 15-08-19 17:13:23, Jason
On Fri, Aug 16, 2019 at 04:11:34PM +0200, Daniel Vetter wrote:
> Also, aside from this patch (which is prep for the next) and some
> simple reordering conflicts they're all independent. So if there's no
> way to paint this bikeshed here (technicolor perhaps?) then I'd like
> to get at least the
On Wed, Aug 14, 2019 at 07:49:27PM +0200, Daniel Vetter wrote:
> On Wed, Aug 14, 2019 at 04:50:33PM +0200, Corentin Labbe wrote:
> > Hello
> >
> > Since lot of release (at least since 4.19), I hit the following error
> > message:
> > DMA-API: cacheline tracking ENOMEM, dma-debug disabled
> >
>
On Fri, Aug 16, 2019 at 02:26:25PM +0200, Michal Hocko wrote:
> On Fri 16-08-19 09:19:06, Jason Gunthorpe wrote:
> > On Fri, Aug 16, 2019 at 10:10:29AM +0200, Michal Hocko wrote:
> > > On Thu 15-08-19 17:13:23, Jason Gunthorpe wrote:
> > > > On Thu, Aug 15, 2019 at 09:35:26PM +0200, Michal Hocko
https://bugs.freedesktop.org/show_bug.cgi?id=110674
--- Comment #107 from ReddestDream ---
> Booting with amdgpu.dpm=0 on 5.2.7 works.
> It is a DPM issue of some kind so although my earlier tests showed that
> hard_min_level was set correctly, it still could be an issue elsewhere in the
>
https://bugs.freedesktop.org/show_bug.cgi?id=110361
emersion changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
On Fri, Aug 16, 2019 at 2:12 PM Jason Gunthorpe wrote:
>
> On Fri, Aug 16, 2019 at 08:20:55AM +0200, Daniel Vetter wrote:
> > On Fri, Aug 16, 2019 at 3:00 AM Jason Gunthorpe wrote:
> > > On Thu, Aug 15, 2019 at 10:49:31PM +0200, Daniel Vetter wrote:
> > > > On Thu, Aug 15, 2019 at 10:27 PM Jason
On Thu, 15 Aug 2019, Randy Dunlap wrote:
> On 8/15/19 6:15 PM, Nathaniel Russell wrote:
>> I would really like help with the kernel error with my uvcvideo driver.
>>
>
> Hi again.
>
> What makes you think that the problem is related to the uvcvideo driver?
> Does some previous kernel version
-next-20190816
for you to fetch changes up to 0b936e6122738f4cf474d1f3ff636cba0edc8b94:
drm: rcar-du: lvds: Fix bridge_to_rcar_lvds (2019-08-16 15:50:27 +0300)
- R-Car DU fixes
- Misc. DRM cleanups
On Fri, Aug 16, 2019 at 04:20:46PM +0300, Tomi Valkeinen wrote:
> On 16/08/2019 15:22, Laurent Pinchart wrote:
> > Standard DRM panel drivers for several panels used by omapfb2 are now
> > available. Their module name clashes with the modules from
> > drivers/gpu/drm/omapdrm/displays/, part of the
https://bugs.freedesktop.org/show_bug.cgi?id=109380
--- Comment #6 from emersion ---
Related bug about Chamelium not having all ports plugged in:
https://bugs.freedesktop.org/show_bug.cgi?id=110940
--
You are receiving this mail because:
You are the assignee for the
On 16/08/2019 15:22, Laurent Pinchart wrote:
drm_panel-based drivers for the ACX565AKM, LB035Q02, LS037V7DW01,
NL8048HL11, TD028TTEC1 and TD043MTEA1 are available, remove the
omapdrm-specific drivers.
Signed-off-by: Laurent Pinchart
---
drivers/gpu/drm/omapdrm/displays/Kconfig | 38 -
On 16/08/2019 15:22, Laurent Pinchart wrote:
Standard DRM panel drivers for several panels used by omapfb2 are now
available. Their module name clashes with the modules from
drivers/gpu/drm/omapdrm/displays/, part of the deprecated omapfb2 fbdev
Shouldn't that path be
https://bugs.freedesktop.org/show_bug.cgi?id=110674
--- Comment #106 from Tom B ---
Booting with amdgpu.dpm=0 on 5.2.7 works.
Performance is poor and as expected I cannot get any information about power
states because /sys/kernel/debug/dri/0/amdgpu_pm_info doesn't exist. I'm
guessing it runs at
https://bugs.freedesktop.org/show_bug.cgi?id=110674
--- Comment #105 from Tom B ---
> Also, I considered that both of my monitors have audio out support. I wonder
> if audio initialization might be the missing piece to the puzzle, the thing
> that interrupts/changes the state of the card and
/media.git tags/du-fixes-20190816
vi
for you to fetch changes up to a53358a31c989c360ea59536d28762b9d2d68d19:
drm: rcar_lvds: Fix dual link mode operations (2019-08-16 15:53:28 +0300)
This fixes a bug introduced in v5.3, I'm thus sending it as a fix for
the current kernel release candidate. If it's
On 8/15/19 9:13 PM, Petr Vandrovec wrote:
> Vlastimil Babka wrote on 8/15/2019 7:32 AM:
>>
>> Does the issue still happen with rc4? Could you apply the 3 attached
>> patches (work in progress), configure-enable CONFIG_DEBUG_PAGEALLOC and
>> CONFIG_PAGE_OWNER and boot kernel with debug_pagealloc=on
https://bugs.freedesktop.org/show_bug.cgi?id=107459
emersion changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
On Fri 16-08-19 09:19:06, Jason Gunthorpe wrote:
> On Fri, Aug 16, 2019 at 10:10:29AM +0200, Michal Hocko wrote:
> > On Thu 15-08-19 17:13:23, Jason Gunthorpe wrote:
> > > On Thu, Aug 15, 2019 at 09:35:26PM +0200, Michal Hocko wrote:
> > >
> > > > > The last detail is I'm still unclear what a GFP
On Fri, Aug 16, 2019 at 12:47:15PM +0300, Laurent Pinchart wrote:
> On Fri, Aug 16, 2019 at 08:23:54AM +0200, Daniel Vetter wrote:
> > On Fri, Aug 16, 2019 at 6:48 AM Sam Ravnborg wrote:
> > > > Hi all,
> > > >
> > > > After merging the drm-misc tree, today's linux-next build (x86_64
> > > >
Hello,
The patch series "[PATCH v4 0/9] DRM panel drivers for omapdrm" added
new DRM panel drivers for a set of panels used on OMAP platforms, with
the omapdrm and omapfb2 drivers. Both those drivers contain
omap-specific panel drivers, which the new DRM panel drivers aims to
replace for omapdrm.
Standard DRM panel drivers for several panels used by omapfb2 are now
available. Their module name clashes with the modules from
drivers/gpu/drm/omapdrm/displays/, part of the deprecated omapfb2 fbdev
driver. As omapfb2 can only be compiled when the omapdrm driver is
disabled, and the DRM panel
drm_panel-based drivers for the ACX565AKM, LB035Q02, LS037V7DW01,
NL8048HL11, TD028TTEC1 and TD043MTEA1 are available, remove the
omapdrm-specific drivers.
Signed-off-by: Laurent Pinchart
---
drivers/gpu/drm/omapdrm/displays/Kconfig | 38 -
drivers/gpu/drm/omapdrm/displays/Makefile |
On Fri, Aug 16, 2019 at 10:10:29AM +0200, Michal Hocko wrote:
> On Thu 15-08-19 17:13:23, Jason Gunthorpe wrote:
> > On Thu, Aug 15, 2019 at 09:35:26PM +0200, Michal Hocko wrote:
> >
> > > > The last detail is I'm still unclear what a GFP flags a blockable
> > > > invalidate_range_start() should
On Fri, Aug 16, 2019 at 08:20:55AM +0200, Daniel Vetter wrote:
> On Fri, Aug 16, 2019 at 3:00 AM Jason Gunthorpe wrote:
> > On Thu, Aug 15, 2019 at 10:49:31PM +0200, Daniel Vetter wrote:
> > > On Thu, Aug 15, 2019 at 10:27 PM Jason Gunthorpe wrote:
> > > > On Thu, Aug 15, 2019 at 10:16:43PM
Quoting Maxime Ripard (2019-08-16 12:32:01)
> Hi Daniel, Dave,
>
> Here's this week drm-misc-next PR.
>
> Maxime
>
> drm-misc-next-2019-08-16:
> drm-misc-next for 5.4:
>
> UAPI Changes:
>
> Cross-subsystem Changes:
>
> Core Changes:
> - dma-buf: add reservation_object_fences helper, relax
Hi Daniel, Dave,
Here's this week drm-misc-next PR.
Maxime
drm-misc-next-2019-08-16:
drm-misc-next for 5.4:
UAPI Changes:
Cross-subsystem Changes:
Core Changes:
- dma-buf: add reservation_object_fences helper, relax
reservation_object_add_shared_fence, remove
https://bugs.freedesktop.org/show_bug.cgi?id=110674
--- Comment #104 from Tom B ---
I did get very similar crashing when I was running HDMI + DP at different
refresh rates ( see https://bugs.freedesktop.org/show_bug.cgi?id=110510 ). I
switched to DP + DP because HDMI+DP wasn't stable, it could
https://bugs.freedesktop.org/show_bug.cgi?id=110674
--- Comment #103 from Peter Hercek ---
I boot in BIOS mode and I'm still getting these errors. Though they are rare in
my case with the "better" kernels (around once a week).
Just a note: There were tearing errors in windows drivers of Radeon
Configure the display Quality of service (QoS) levels priority if the
optional property node "arm,malidp-aqros-value" is defined in DTS file.
QoS signaling using AQROS and AWQOS AXI interface signals, the AQROS is
driven from the "RQOS" register, so needed to program the RQOS register
to avoid
https://bugs.freedesktop.org/show_bug.cgi?id=110674
--- Comment #102 from Tom B ---
> Grasping at straws a bit here, but it occurred to me that maybe Linux kernel
> testing on Radeon VII was done on an early VBIOS that didn't have full UEFI
> support yet. We know that AMD had to issue a VBIOS
Hi Randy,
On Thu, Aug 15, 2019 at 08:10:03PM -0700, Randy Dunlap wrote:
> [adding mailing lists etc. with Nathaniel's test info]
>
> On 8/15/19 7:21 PM, Nathaniel Russell wrote:
> > Well i surpressed the uvcvideo driver and you are right Randy it
> > definitely is not the uvcvideo driver. There
Hello,
On Fri, Aug 16, 2019 at 08:23:54AM +0200, Daniel Vetter wrote:
> On Fri, Aug 16, 2019 at 6:48 AM Sam Ravnborg wrote:
> > > Hi all,
> > >
> > > After merging the drm-misc tree, today's linux-next build (x86_64
> > > allmodconfig) produced this warning:
> > >
> > > warning: same module
The devfreq opp table needs to be removed when unloading the driver to
free the memory associated with it.
Signed-off-by: Steven Price
---
drivers/gpu/drm/panfrost/panfrost_devfreq.c | 6 ++
drivers/gpu/drm/panfrost/panfrost_devfreq.h | 1 +
drivers/gpu/drm/panfrost/panfrost_drv.c | 5
The hardware has a set of '_NEXT' registers that can hold a second job
while the first is executing. Make use of these registers to enqueue a
second job per slot.
Signed-off-by: Steven Price
---
Note that this is based on top of Rob Herring's "per FD address space"
patch[1].
[1]
If there is no regulator defined for the GPU then still control the
frequency using the supplied clock.
Some boards have clock control but no (direct) control of the regulator.
For example the HiKey960 uses a mailbox protocol to a MCU to control
frequencies and doesn't directly control the
Hi Daniel, Dave,
after some pretty slow cycles we finally have a bit more exciting work
ready for upstream.
Most importantly per-process address spaces on GPUs that are capable of
providing proper isolation has finished baking. This is the base for
our softpin implementation, which allows us to
https://bugs.freedesktop.org/show_bug.cgi?id=109380
--- Comment #5 from Arek Hiler ---
https://patchwork.freedesktop.org/patch/324290/
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
On 14/08/2019 05:48, Wei Yongjun wrote:
> Add the missing unlock before return from function
> panfrost_mmu_map_fault_addr()
> in the error handling case.
>
> Fixes: 187d2929206e ("drm/panfrost: Add support for GPU heap allocations")
> Signed-off-by: Wei Yongjun
Well spotted.
Reviewed-by:
On Thu 15-08-19 22:16:43, Daniel Vetter wrote:
> On Thu, Aug 15, 2019 at 9:35 PM Michal Hocko wrote:
[...]
> > > The last detail is I'm still unclear what a GFP flags a blockable
> > > invalidate_range_start() should use. Is GFP_KERNEL OK?
> >
> > I hope I will not make this muddy again ;)
> >
On Thu 15-08-19 15:15:09, Andrew Morton wrote:
> On Thu, 15 Aug 2019 10:44:29 +0200 Michal Hocko wrote:
>
> > > I continue to struggle with this. It introduces a new kernel state
> > > "running preemptibly but must not call schedule()". How does this make
> > > any sense?
> > >
> > > Perhaps
1 - 100 of 108 matches
Mail list logo
