search for: 10003000

...t gmail.com> wrote: > > [ 0.000000] Linux version 5.6.10-zotac (root at saux) (gcc version 9.3.0 (SAUX Aarch64)) #1 SMP PREEMPT Tue May 5 22:16:40 CEST 2020 > > [ 0.000000] Machine model: NVIDIA Jetson TX2 Developer Kit > > [...] > > > [ 3.965934] tegra-pcie 10003000.pcie: Adding to iommu group 5 > > [ 3.966435] tegra-pcie 10003000.pcie: 4x1, 1x1 configuration > > [ 3.968057] tegra-pcie 10003000.pcie: probing port 0, using 4 lanes > > [ 3.970121] tegra-pcie 10003000.pcie: probing port 1, using 0 lanes > > [ 3.972183] tegra-pc...

...Milan Bu?ka <milan.buska at gmail.com> wrote: > [ 0.000000] Linux version 5.6.10-zotac (root at saux) (gcc version 9.3.0 (SAUX Aarch64)) #1 SMP PREEMPT Tue May 5 22:16:40 CEST 2020 > [ 0.000000] Machine model: NVIDIA Jetson TX2 Developer Kit [...] > [ 3.965934] tegra-pcie 10003000.pcie: Adding to iommu group 5 > [ 3.966435] tegra-pcie 10003000.pcie: 4x1, 1x1 configuration > [ 3.968057] tegra-pcie 10003000.pcie: probing port 0, using 4 lanes > [ 3.970121] tegra-pcie 10003000.pcie: probing port 1, using 0 lanes > [ 3.972183] tegra-pcie 10003000.pcie: pr...

...> > [ 0.000000] Linux version 5.6.10-zotac (root at saux) (gcc version 9.3.0 (SAUX Aarch64)) #1 SMP PREEMPT Tue May 5 22:16:40 CEST 2020 > > > [ 0.000000] Machine model: NVIDIA Jetson TX2 Developer Kit > > > > [...] > > > > > [ 3.965934] tegra-pcie 10003000.pcie: Adding to iommu group 5 > > > [ 3.966435] tegra-pcie 10003000.pcie: 4x1, 1x1 configuration > > > [ 3.968057] tegra-pcie 10003000.pcie: probing port 0, using 4 lanes > > > [ 3.970121] tegra-pcie 10003000.pcie: probing port 1, using 0 lanes > > > [...

...> > [ 0.000000] Linux version 5.6.10-zotac (root at saux) (gcc version 9.3.0 (SAUX Aarch64)) #1 SMP PREEMPT Tue May 5 22:16:40 CEST 2020 > > > [ 0.000000] Machine model: NVIDIA Jetson TX2 Developer Kit > > > > [...] > > > > > [ 3.965934] tegra-pcie 10003000.pcie: Adding to iommu group 5 > > > [ 3.966435] tegra-pcie 10003000.pcie: 4x1, 1x1 configuration > > > [ 3.968057] tegra-pcie 10003000.pcie: probing port 0, using 4 lanes > > > [ 3.970121] tegra-pcie 10003000.pcie: probing port 1, using 0 lanes > > > [...

Hi to all. I'm experimenting with running a https://www.zotac.com/us/product/graphics_card/geforce%C2%AE-gt-710-1gb-pcie-x-1 card on an Nvidia Jetson TX2 arm64 device. Possible? Linux kernel aarch64 5.6.10. Because Nvidia did not list drivers for this architecture, I'm experimenting with a nouveau driver. The Jetson TX2 has a default driver for the host1x framebuffer for output from the

...554] io scheduler noop registered [ 8.922559] io scheduler deadline registered [ 8.922661] io scheduler cfq registered (default) [ 8.922666] io scheduler mq-deadline registered [ 8.922669] io scheduler kyber registered [ 8.922748] io scheduler bfq registered [ 8.926709] tegra-pcie 10003000.pcie: 4x1, 1x1 configuration [ 8.926736] tegra-pcie 10003000.pcie: Failed to get supply 'dvdd-pex': -517 [ 8.927206] ipmi message handler version 39.2 [ 8.930002] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [ 8.931212] console [ttyS0] disabled [ 8.931241] 3100000....

...uV [ 2.396019] max77686-rtc max77620-rtc: registered as rtc0 [ 2.411115] random: fast init done [ 3.664208] random: crng init done [ 3.959266] VDD_1V8_AP: supplied by VDD_1V8 [ 3.962047] tegra-xusb-padctl 3520000.padctl: failed to read calibration fuse: -517 [ 3.965934] tegra-pcie 10003000.pcie: Adding to iommu group 5 [ 3.966435] tegra-pcie 10003000.pcie: 4x1, 1x1 configuration [ 3.968057] tegra-pcie 10003000.pcie: probing port 0, using 4 lanes [ 3.970121] tegra-pcie 10003000.pcie: probing port 1, using 0 lanes [ 3.972183] tegra-pcie 10003000.pcie: probing port 2, using...

Thanks to Thierry for finding this - applying index e14643615698..00eeaaffeae5 100644 --- a/drivers/gpu/drm/nouveau/nvkm/engine/device/base.c +++ b/drivers/gpu/drm/nouveau/nvkm/engine/device/base.c @@ -2369,7 +2369,7 @@ nv13b_chipset = { .imem = gk20a_instmem_new, .ltc = gp100_ltc_new, .mc = gp10b_mc_new, - .mmu = gf100_mmu_new, + .mmu = gp10b_mmu_new,

...418] io scheduler noop registered [ 8.634423] io scheduler deadline registered [ 8.634523] io scheduler cfq registered (default) [ 8.634528] io scheduler mq-deadline registered [ 8.634532] io scheduler kyber registered [ 8.634614] io scheduler bfq registered [ 8.638596] tegra-pcie 10003000.pcie: 4x1, 1x1 configuration [ 8.638622] tegra-pcie 10003000.pcie: Failed to get supply 'dvdd-pex': -517 [ 8.639104] ipmi message handler version 39.2 [ 8.641894] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [ 8.643058] console [ttyS0] disabled [ 8.643086] 3100000....

...600] io scheduler noop registered [ 8.617606] io scheduler deadline registered [ 8.617714] io scheduler cfq registered (default) [ 8.617718] io scheduler mq-deadline registered [ 8.617722] io scheduler kyber registered [ 8.617805] io scheduler bfq registered [ 8.621804] tegra-pcie 10003000.pcie: 4x1, 1x1 configuration [ 8.621829] tegra-pcie 10003000.pcie: Failed to get supply 'dvdd-pex': -517 [ 8.622295] ipmi message handler version 39.2 [ 8.625086] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [ 8.626267] console [ttyS0] disabled [ 8.626294] 3100000....

...point, while troubleshooting with a user, I was logged in remotely while the user was working on the desktop when it became completely unresponsive. /var/log/messages had nouveau messages like: kernel: nouveau: evo channel stalled kernel: nouveau 0000:01:00.0: disp: chid 1 mthd 0000 data 00000000 10003000 00000000 kernel: nouveau 0000:01:00.0: DRM: base-1: timeout kernel: nouveau 0000:01:00.0: DRM: core notifier timeout Those messages might be meaningless, but they are abundant in the logs. For grins before rebooting, I attempted to stop and start GDM. Both operations seemed successful, I verified...