search for: 100228

https://bugs.freedesktop.org/show_bug.cgi?id=100228 Bug ID: 100228 Summary: [NV137] unknown chipset (137000a1) Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Compo...

https://bugs.freedesktop.org/show_bug.cgi?id=104621 Bug ID: 104621 Summary: Nouveau prevents booting on Pascal Gpu Product: Mesa Version: 17.3 Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau Assignee: nouveau at

...gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.freedesktop.or | |g/show_bug.cgi?id=100228 Summary|xorg-server-1.19.3 crashes |[NV137/GP107] |when trying to enable HDMI |xorg-server-1.19.3 crashes |output |when trying to enable HDMI | |output --- Comment #15 from Rhys K...

https://bugs.freedesktop.org/show_bug.cgi?id=106793 Bug ID: 106793 Summary: [NV138] bus: MMIO read of 00000000 FAULT at 409800 [ TIMEOUT ] Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium

We've seen a number of power management and secboot issues with the Pascal-series mobile GPUs. Without a command line it is hard to debug remotely, but see, as one possible example: https://bugs.freedesktop.org/show_bug.cgi?id=100228 Can you try booting with a kernel command line that includes "nouveau.runpm=0" as a debugging step. On Mon, 17 Sep 2018 at 17:46, don fisher <hdf3 at comcast.net> wrote: > Alienware 17 r5 also with same graphics (GP106M and Intel 3e9b) does > boot from same disk. I look in...

https://bugs.freedesktop.org/show_bug.cgi?id=101764 Bug ID: 101764 Summary: [regression] eaa2c988033b breaks GTX1050TI (GP107 / NV137) Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau

https://bugs.freedesktop.org/show_bug.cgi?id=102275 Bug ID: 102275 Summary: Laptop bootup and suspend and wake issues Product: Mesa Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau

Hi, I recently added logs and another report from a ThinkPad P1 with a Quadro P2000 Mobile (GP107GLM) to issue #100228. That's with a very recent Linux kernel and current nouveau driver sources, all booted from an NFS-root setup, making it well reproducible. I can optionally boot into a similar NFS installation with the proprietary Nvidia driver, allowing me to capture MMIO traces as well. However, I'm n...

https://bugs.freedesktop.org/show_bug.cgi?id=107818 Bug ID: 107818 Summary: linux-4.18.5 every boot some drivers errors Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at

https://bugs.freedesktop.org/show_bug.cgi?id=102192 Bug ID: 102192 Summary: Dell XPS 15 9560: PU: 1 PID: 58 at drivers/gpu/drm/nouveau/nvkm/subdev/mmu/gf100.c:190 gf100_vm_flush+0x1b3/0x1c0 [nouveau] Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All)

https://bugs.freedesktop.org/show_bug.cgi?id=101553 Bug ID: 101553 Summary: [ 8.944203] nouveau 0000:01:00.0: DRM: failed to create kernel channel, -22 Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium

Hi, I am slightly stuck in a corner case I don't know how to debug. I have an optimus setup in a dell xps 9560 with a discrete gpu nvidia geforce 1050 (Pascal - NV130). I installed Fedora and if I do not boot with nouveau.modeset=0, then the computer crashes as soon as I try to start Xorg (I have disabled wayland). So, gdm starts but then as soon as I get into i3 or gnome, the computer

I do not know how to debug this situation. Nothing appears in /var/log/messages. I miss the serial port:-( I executed a journalctl -r, and saw an error: kernel: nouveau 00001:01:00.0; Refused to change power state, currently in D3 The last message before reboot was: kernel: watchdog: Bug: soft lockup - CPU#0 stuck for 22s! [ntpd:3265] I have a pair of these Alienware 13 laptops, and would be

https://bugs.freedesktop.org/show_bug.cgi?id=101573 Bug ID: 101573 Summary: GP107 crash with no HDMI connected on 4.12.rc6 Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at

https://bugs.freedesktop.org/show_bug.cgi?id=101782 Bug ID: 101782 Summary: GTX1050TI (GP107 / NV137): HDMI output not working Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau

...ution, it mostly boils down to testing and checking if there are > other issues left we didn't address yet. Understood. That's part of why I setup that infrastructure. > Also without knowing what > error message you are getting precisely Sorry, I thought the reference to issue #100228 was enough. I certainly got the exact same "bus: MMIO read of 00000000 FAULT at 409800" timeout and figured I better not file a duplicate. I realize messed up the upload of the kernel log to that issue. I just corrected that. So, current status on skeggsb/nouveau fails that way for me...

https://bugs.freedesktop.org/show_bug.cgi?id=101665 Bug ID: 101665 Summary: lspci blocks forever with a GP107M Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at