amdgpu UBSAN warnings in 6.10.0-rc5

2024-06-30 Thread Jeff Layton
bff63d0 [8.774859] [8.774864] ---[ end trace ]--- It looks like "count" probably needs to be clamped to ARRAY_SIZE(header->gpio_pin) in bios_parser_get_gpio_pin_info ? dmesg is attached. There are couple of other warnings in there too after the UBSAN one, but this one

Re: WARNING in allocate_mst_payload

2023-11-21 Thread Jeff Layton
gt; connection and maybe individually connect them for a test if possible. > > Regards, > Christian. > > Am 21.11.23 um 14:01 schrieb Jeff Layton: > > I have a recurring problem where my workstation tries to put the monitor > > to sleep, which triggers a warning down in t

WARNING in allocate_mst_payload

2023-11-21 Thread Jeff Layton
I have a recurring problem where my workstation tries to put the monitor to sleep, which triggers a warning down in the depths of the video card driver. When I return to the machine the monitor is black, but not in powersave mode and all of the windows on my desktop have been shuffled off to the se

DPMS problems with radeon card and dual monitor setup

2023-10-02 Thread Jeff Layton
00011 R11: 0246 R12: 7ffe0a955040 [ 4125.634141] R13: c03864bc R14: 000a R15: 56075466b960 [ 4125.634156] [ 4125.634159] ---[ end trace 0000 ]--- Thanks, -- Jeff Layton

Re: [PATCH v2 35/47] nfsd: dynamically allocate the nfsd-reply shrinker

2023-07-24 Thread Jeff Layton
ntrol *sc) > { > - struct nfsd_net *nn = container_of(shrink, > - struct nfsd_net, nfsd_reply_cache_shrinker); > + struct nfsd_net *nn = shrink->private_data; > > return atomic_read(&nn->num_drc_entries); > } > @@ -342,8 +344,

Re: [PATCH v2 34/47] nfsd: dynamically allocate the nfsd-client shrinker

2023-07-24 Thread Jeff Layton
+ shrinker_register(nn->nfsd_client_shrinker); > + > return 0; > > err_shrinker: > @@ -8228,7 +8232,7 @@ nfs4_state_shutdown_net(struct net *net) > struct list_head *pos, *next, reaplist; > struct nfsd_net *nn = net_generic(net, nfsd_net_id); > > - unregister_shrinker(&nn->nfsd_client_shrinker); > + shrinker_unregister(nn->nfsd_client_shrinker); > cancel_work(&nn->nfsd_shrinker_work); > cancel_delayed_work_sync(&nn->laundromat_work); > locks_end_grace(&nn->nfsd4_manager); Acked-by: Jeff Layton

Re: [PATCH v2] drm: use mgr->dev in drm_dbg_kms in drm_dp_add_payload_part2

2023-06-20 Thread Jeff Layton
. Thanks, Jeff On Wed, 2023-04-19 at 16:54 -0400, Lyude Paul wrote: > Reviewed-by: Lyude Paul > > Thanks! > > On Wed, 2023-04-19 at 07:24 -0400, Jeff Layton wrote: > > I've been experiencing some intermittent crashes down in the display > > driver code. The

Re: [PATCH v2] drm: use mgr->dev in drm_dbg_kms in drm_dp_add_payload_part2

2023-04-27 Thread Jeff Layton
On Wed, 2023-04-19 at 16:54 -0400, Lyude Paul wrote: > Reviewed-by: Lyude Paul > > Thanks! > > On Wed, 2023-04-19 at 07:24 -0400, Jeff Layton wrote: > > I've been experiencing some intermittent crashes down in the display > > driver code. The symptoms are us

Re: [PATCH v2] drm: use mgr->dev in drm_dbg_kms in drm_dp_add_payload_part2

2023-04-22 Thread Jeff Layton
On Wed, 2023-04-19 at 16:21 +0300, Jani Nikula wrote: > On Wed, 19 Apr 2023, Jeff Layton wrote: > > I've been experiencing some intermittent crashes down in the display > > driver code. The symptoms are ususally a line like this in dmesg: > > > > amdgpu

[PATCH v2] drm: use mgr->dev in drm_dbg_kms in drm_dp_add_payload_part2

2023-04-19 Thread Jeff Layton
ch to using mgr->dev instead of state->dev since "state" can be NULL in some cases. Link: https://bugzilla.redhat.com/show_bug.cgi?id=2184855 Suggested-by: Jani Nikula Signed-off-by: Jeff Layton --- drivers/gpu/drm/display/drm_dp_mst_topology.c | 2 +- 1 file changed, 1 ins

Re: [PATCH] drm: make drm_dp_add_payload_part2 gracefully handle NULL state pointer

2023-04-17 Thread Jeff Layton
On Mon, 2023-04-17 at 10:58 +, Lin, Wayne wrote: > [AMD Official Use Only - General] > > > > > -Original Message- > > From: Jani Nikula > > Sent: Monday, April 17, 2023 6:30 PM > > To: Jeff Layton ; Lyude Paul ; Lin, > > Wayne ; Alex Deu

Re: [PATCH] drm: make drm_dp_add_payload_part2 gracefully handle NULL state pointer

2023-04-17 Thread Jeff Layton
On Mon, 2023-04-17 at 13:29 +0300, Jani Nikula wrote: > On Mon, 17 Apr 2023, Jeff Layton wrote: > > On Mon, 2023-04-17 at 11:44 +0300, Jani Nikula wrote: > > > On Fri, 14 Apr 2023, Lyude Paul wrote: > > > > On Fri, 2023-04-14 at 13:35 +0300, Jani Nikula wrote: >

Re: [PATCH] drm: make drm_dp_add_payload_part2 gracefully handle NULL state pointer

2023-04-17 Thread Jeff Layton
On Mon, 2023-04-17 at 11:44 +0300, Jani Nikula wrote: > On Fri, 14 Apr 2023, Lyude Paul wrote: > > On Fri, 2023-04-14 at 13:35 +0300, Jani Nikula wrote: > > > On Fri, 14 Apr 2023, Jeff Layton wrote: > > > > On Fri, 2023-04-14 at 04:40 +, Lin,

Re: [PATCH] drm: make drm_dp_add_payload_part2 gracefully handle NULL state pointer

2023-04-14 Thread Jeff Layton
essage, my proposed patch did prevent the box from oopsing, so I'd really like to see it go in unless it's just categorically wrong for the caller to pass down a NULL state pointer to drm_dp_add_payload_part2. > > -Original Message- > > From: Alex Deucher > > Se

Re: [PATCH] drm: make drm_dp_add_payload_part2 gracefully handle NULL state pointer

2023-04-13 Thread Jeff Layton
On Thu, 2023-04-13 at 15:31 +0300, Jani Nikula wrote: > On Thu, 13 Apr 2023, Jeff Layton wrote: > > I've been experiencing some intermittent crashes down in the display > > driver code. The symptoms are ususally a line like this in dmesg: > > > > amdgpu

[PATCH] drm: make drm_dp_add_payload_part2 gracefully handle NULL state pointer

2023-04-13 Thread Jeff Layton
real bug is probably in the caller of this function, which is passing it a NULL state pointer, but this patch at least keeps my machine from oopsing when this occurs. Link: https://bugzilla.redhat.com/show_bug.cgi?id=2184855 Signed-off-by: Jeff Layton --- drivers/gpu/drm/display/drm_dp_mst_topol

Re: NULL pointer dereference in drm_dp_add_payload_part2+0xca/0x100

2023-04-12 Thread Jeff Layton
On Sat, 2023-04-08 at 07:46 -0400, Jeff Layton wrote: > I've hit some repeated crashes in drm_dp_add_payload_part2. Here's one > from this morning that occurred not long after booting the machine. I > hadn't even logged in yet -- it was still at a gdm prompt: > >

NULL pointer dereference in drm_dp_add_payload_part2+0xca/0x100

2023-04-08 Thread Jeff Layton
ng like this? drm_dbg_kms(state ? state->dev : NULL, "Part 1 of payload creation for %s failed, skipping part 2\n", I think that would at least prevent this problem from crashing the machine. Thanks, -- Jeff Layton

Re: [fs/lock] 0064b3d9f9: BUG:kernel_NULL_pointer_dereference,address

2022-07-26 Thread Jeff Layton
9f96f .config > make HOSTCC=clang-15 CC=clang-15 ARCH=i386 olddefconfig prepare > modules_prepare bzImage modules > make HOSTCC=clang-15 CC=clang-15 ARCH=i386 > INSTALL_MOD_PATH= modules_install > cd > find lib/ | cpio -o -H newc --quiet | gzip > modules.cgz > > > git clone https://github.com/intel/lkp-tests.git > cd lkp-tests > bin/lkp qemu -k -m modules.cgz job-script # job-script is > attached in this email > > # if come across any failure that blocks the test, > # please remove ~/.lkp and /lkp dir to run from a clean state. > > > -- Jeff Layton

Re: softlockup in v5.15.12 in dcn20_post_unlock_program_front_end

2022-01-03 Thread Jeff Layton
On Sun, 2022-01-02 at 09:30 -0500, Jeff Layton wrote: > I'm seeing a reproducible softlockup on amdgpu on v5.15.12: > > [ 861.656146] [drm:dc_dmub_srv_wait_idle [amdgpu]] *ERROR* Error waiting for > DMUB idle: status=3 > [ 861.914848] [drm:dc_dmub_srv_wait_idle [amdgpu]] *

softlockup in v5.15.12 in dcn20_post_unlock_program_front_end

2022-01-02 Thread Jeff Layton
ules: amdgpu I'm able to test patches if it helps. Let me know if you want other info as well. Thanks! -- Jeff Layton

WARNING: CPU: 5 PID: 69 at drivers/gpu/drm/ttm/ttm_bo.c:139 ttm_bo_move_to_lru_tail+0x376/0x500 [ttm]

2021-03-04 Thread Jeff Layton
q_exit_rcu+0x13e/0x190 [ 147.868011] ---[ end trace 595bd7e9298cfe26 ]--- Is this a known bug? Is there a patch that fixes it? I'd be happy to test it since it's making testing in VMs difficult right now. Thanks, -- Jeff Layton ___ dri-de

Re: [PATCH 03/34] net/ceph: convert put_page() to put_user_page*()

2019-08-02 Thread Jeff Layton
t; - } > + put_user_pages_dirty_lock(pages, num_pages, dirty); > kvfree(pages); > } > EXPORT_SYMBOL(ceph_put_page_vector); This patch looks sane enough. Assuming that the earlier patches are OK: Acked-by: Jeff Layton ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel

Re: system_nrt_wq, system suspend, and the freezer

2012-02-16 Thread Jeff Layton
On Thu, 16 Feb 2012 08:29:51 -0800 Tejun Heo wrote: > Hello, > > On Thu, Feb 16, 2012 at 10:27:28AM -0500, Jeff Layton wrote: > > These should all be freezable and we might even be able to get away > > with WQ_UNBOUND for some of these. > > In general, I would

Re: system_nrt_wq, system suspend, and the freezer

2012-02-16 Thread Jeff Layton
above should be > converted to the new workqueue? > > Thanks, > > Alan Stern > > -- > To unsubscribe from this list: send the line "unsubscribe linux-cifs" in > the body of a message to majord...@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html -- Jeff Layton ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel

system_nrt_wq, system suspend, and the freezer

2012-02-16 Thread Jeff Layton
On Thu, 16 Feb 2012 08:29:51 -0800 Tejun Heo wrote: > Hello, > > On Thu, Feb 16, 2012 at 10:27:28AM -0500, Jeff Layton wrote: > > These should all be freezable and we might even be able to get away > > with WQ_UNBOUND for some of these. > > In general, I would

system_nrt_wq, system suspend, and the freezer

2012-02-16 Thread Jeff Layton
ove should be > converted to the new workqueue? > > Thanks, > > Alan Stern > > -- > To unsubscribe from this list: send the line "unsubscribe linux-cifs" in > the body of a message to majordomo at vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html -- Jeff Layton