dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <regressions@leemhuis.info>
To: bskeggs@redhat.com, Karol Herbst <kherbst@redhat.com>,
	Lyude Paul <lyude@redhat.com>
Cc: nouveau@lists.freedesktop.org,
	Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt>,
	regressions@lists.linux.dev, dri-devel@lists.freedesktop.org,
	airlied@redhat.com
Subject: Re: [REGRESSION] GM20B probe fails after commit 2541626cfb79
Date: Thu, 5 Jan 2023 13:28:49 +0100	[thread overview]
Message-ID: <c32ea02c-d706-ea2f-aa13-660b8db958ef@leemhuis.info> (raw)
In-Reply-To: <20221228144914.z7t7a4fdwvbblnak@wslaptop>

[adding Karol and Lyude to the list of recipients]

Hi, this is your Linux kernel regression tracker. Top-posting for once,
to make this easily accessible to everyone.

On 28.12.22 15:49, Diogo Ivo wrote:
> Hello,
> 
> Commit 2541626cfb79 breaks GM20B probe with
> the following kernel log:
Just wondering: is anyone looking on this? The report was posted more
than a week ago and didn't even get a single reply yet afaics. This of
course can happen at this time of the year, but I nevertheless thought a
quick status inquiry might be a good idea at this point.

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
If I did something stupid, please tell me, as explained on that page.

> [    2.153892] ------------[ cut here ]------------
> [    2.153897] WARNING: CPU: 1 PID: 36 at drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmgf100.c:273 gf100_vmm_valid+0x2c4/0x390
> [    2.153916] Modules linked in:
> [    2.153922] CPU: 1 PID: 36 Comm: kworker/u8:1 Not tainted 6.1.0+ #1
> [    2.153929] Hardware name: Google Pixel C (DT)
> [    2.153933] Workqueue: events_unbound deferred_probe_work_func
> [    2.153943] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
> [    2.153950] pc : gf100_vmm_valid+0x2c4/0x390
> [    2.153959] lr : gf100_vmm_valid+0xb4/0x390
> [    2.153966] sp : ffffffc009e134b0
> [    2.153969] x29: ffffffc009e134b0 x28: 0000000000000000 x27: ffffffc008fd44c8
> [    2.153979] x26: 00000000ffffffea x25: ffffffc0087b98d0 x24: ffffff8080f89038
> [    2.153987] x23: ffffff8081fadc08 x22: 0000000000000000 x21: 0000000000000000
> [    2.153995] x20: ffffff8080f8a000 x19: ffffffc009e13678 x18: 0000000000000000
> [    2.154003] x17: f37a8b93418958e6 x16: ffffffc009f0d000 x15: 0000000000000000
> [    2.154011] x14: 0000000000000002 x13: 000000000003a020 x12: ffffffc008000000
> [    2.154019] x11: 0000000102913000 x10: 0000000000000000 x9 : 0000000000000000
> [    2.154026] x8 : ffffffc009e136d8 x7 : ffffffc008fd44c8 x6 : ffffff80803d0f00
> [    2.154034] x5 : 0000000000000000 x4 : ffffff8080f88c00 x3 : 0000000000000010
> [    2.154041] x2 : 000000000000000c x1 : 00000000ffffffea x0 : 00000000ffffffea
> [    2.154050] Call trace:
> [    2.154053]  gf100_vmm_valid+0x2c4/0x390
> [    2.154061]  nvkm_vmm_map_valid+0xd4/0x204
> [    2.154069]  nvkm_vmm_map_locked+0xa4/0x344
> [    2.154076]  nvkm_vmm_map+0x50/0x84
> [    2.154083]  nvkm_firmware_mem_map+0x84/0xc4
> [    2.154094]  nvkm_falcon_fw_oneinit+0xc8/0x320
> [    2.154101]  nvkm_acr_oneinit+0x428/0x5b0
> [    2.154109]  nvkm_subdev_oneinit_+0x50/0x104
> [    2.154114]  nvkm_subdev_init_+0x3c/0x12c
> [    2.154119]  nvkm_subdev_init+0x60/0xa0
> [    2.154125]  nvkm_device_init+0x14c/0x2a0
> [    2.154133]  nvkm_udevice_init+0x60/0x9c
> [    2.154140]  nvkm_object_init+0x48/0x1b0
> [    2.154144]  nvkm_ioctl_new+0x168/0x254
> [    2.154149]  nvkm_ioctl+0xd0/0x220
> [    2.154153]  nvkm_client_ioctl+0x10/0x1c
> [    2.154162]  nvif_object_ctor+0xf4/0x22c
> [    2.154168]  nvif_device_ctor+0x28/0x70
> [    2.154174]  nouveau_cli_init+0x150/0x590
> [    2.154180]  nouveau_drm_device_init+0x60/0x2a0
> [    2.154187]  nouveau_platform_device_create+0x90/0xd0
> [    2.154193]  nouveau_platform_probe+0x3c/0x9c
> [    2.154200]  platform_probe+0x68/0xc0
> [    2.154207]  really_probe+0xbc/0x2dc
> [    2.154211]  __driver_probe_device+0x78/0xe0
> [    2.154216]  driver_probe_device+0xd8/0x160
> [    2.154221]  __device_attach_driver+0xb8/0x134
> [    2.154226]  bus_for_each_drv+0x78/0xd0
> [    2.154230]  __device_attach+0x9c/0x1a0
> [    2.154234]  device_initial_probe+0x14/0x20
> [    2.154239]  bus_probe_device+0x98/0xa0
> [    2.154243]  deferred_probe_work_func+0x88/0xc0
> [    2.154247]  process_one_work+0x204/0x40c
> [    2.154256]  worker_thread+0x230/0x450
> [    2.154261]  kthread+0xc8/0xcc
> [    2.154266]  ret_from_fork+0x10/0x20
> [    2.154273] ---[ end trace 0000000000000000 ]---
> [    2.154278] nouveau 57000000.gpu: pmu: map -22
> [    2.154285] nouveau 57000000.gpu: acr: one-time init failed, -22
> [    2.154559] nouveau 57000000.gpu: init failed with -22
> [    2.154564] nouveau: DRM-master:00000000:00000080: init failed with -22
> [    2.154574] nouveau 57000000.gpu: DRM-master: Device allocation failed: -22
> [    2.162905] nouveau: probe of 57000000.gpu failed with error -22
> 
> #regzbot introduced: 2541626cfb79
> 
> Thanks,
> 
> Diogo Ivo
> 
> 

#regzbot poke

  reply	other threads:[~2023-01-05 12:28 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-28 14:49 [REGRESSION] GM20B probe fails after commit 2541626cfb79 Diogo Ivo
2023-01-05 12:28 ` Thorsten Leemhuis [this message]
2023-01-13 13:19   ` Linux kernel regression tracking (Thorsten Leemhuis)
2023-01-14  3:27     ` Karol Herbst
2023-01-14 16:03       ` Diogo Ivo
2023-01-14 18:56         ` Karol Herbst
2023-01-14 15:58     ` Diogo Ivo
2023-02-03  9:13   ` Linux kernel regression tracking (#update)
2023-01-15 21:45 ` David Airlie
2023-01-16 12:24   ` Diogo Ivo
2023-01-18  1:28     ` Ben Skeggs
2023-01-18  8:42       ` [Nouveau] " Nicolas Chauvet
2023-01-20 11:34       ` Diogo Ivo
2023-01-27  6:00         ` Ben Skeggs
2023-01-27  9:03           ` Nicolas Chauvet
2023-01-27 10:48             ` Diogo Ivo
2023-01-27 10:39           ` Diogo Ivo
2023-01-29 22:36             ` Ben Skeggs
2023-01-30 13:54               ` Diogo Ivo
2023-01-30 16:05               ` Nicolas Chauvet
2023-01-17 15:55   ` [Nouveau] " Nicolas Chauvet

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=c32ea02c-d706-ea2f-aa13-660b8db958ef@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=airlied@redhat.com \
    --cc=bskeggs@redhat.com \
    --cc=diogo.ivo@tecnico.ulisboa.pt \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kherbst@redhat.com \
    --cc=lyude@redhat.com \
    --cc=nouveau@lists.freedesktop.org \
    --cc=regressions@lists.linux.dev \
    /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).