similar to: Kernel panic on nouveau during boot on NVIDIA NV118 (GM108)

It looks similiar to this one: https://bugs.freedesktop.org/show_bug.cgi?id=101322 please provide a dmesg booted with "nouveau.debug=debug" as well 2017-06-02 12:01 GMT+02:00 Chris Chiu <chiu at endlessm.com>: > We are working with new desktop that have the NVIDIA NV118 > chipset. > > During boot, the display becomes unusable at the point where the > nouveau driver

On Fri, Jun 2, 2017 at 4:01 AM, Chris Chiu <chiu at endlessm.com> wrote: > We are working with new desktop that have the NVIDIA NV118 > chipset. > > During boot, the display becomes unusable at the point where the > nouveau driver loads. We have reproduced on 4.8, 4.11 and linux > master (4.12-rc3). To save digging into the attachment, here is the crash: nouveau

https://bugs.freedesktop.org/show_bug.cgi?id=101322 Bug ID: 101322 Summary: GM108/NV118: 0 MiB DDR3 and boot crash in gf100_ltc_oneinit_tag_ram Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component:

https://bugs.freedesktop.org/show_bug.cgi?id=102860 Bug ID: 102860 Summary: Nvidia 940MX (NV118, GM108) is reported as a NV117, GM107 Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: minor Priority: medium Component:

From: Chris Chiu <chiu at endlessm.com> This new graphics card was failing to initialize with nouveau due to an "unknown chipset" error. Copy the GP106 configuration and rename for GP107/NV137. We don't know for certain that this is fully correct, but brief desktop testing suggests this is working fine. Signed-off-by: Chris Chiu <chiu at endlessm.com> Signed-off-by:

Nouveau driver shows unknown chipset (136000a1) for GTX 1060, so it only gives VGA resolution on screen. Use the same chipset as nv134 then it shows FullHD. This commit copies fields from nv134_chipset to nv136_chipset for GTX 1060. Signed-off-by: Chris Chiu <chiu at endlessm.com> --- drivers/gpu/drm/nouveau/nvkm/engine/device/base.c | 29 +++++++++++++++++++++++ 1 file changed, 29

Actually GM108 is not one of the recognized chips. Someone needs to go through and check that its goldens didn't change. Nobody's done that. See https://bugs.freedesktop.org/show_bug.cgi?id=89558 On Thu, Mar 31, 2016 at 4:57 PM, Pierre Moreau <pierre.morrow at free.fr> wrote: > Hello, > > Acceleration support for GM107 was merged in kernel 4.1, and modesetting > support

https://bugs.freedesktop.org/show_bug.cgi?id=107479 Bug ID: 107479 Summary: GM108: MMIO read of 00000000 FAULT at 612004 [ IBUS ] Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau

https://bugs.freedesktop.org/show_bug.cgi?id=89558 Bug ID: 89558 Summary: Unknown chipset error for GeForce 840M Product: xorg Version: unspecified Hardware: Other OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at

https://bugs.freedesktop.org/show_bug.cgi?id=95188 Bug ID: 95188 Summary: GeForce 840M (GM108) troubles Product: xorg Version: git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at lists.freedesktop.org

Is there anything I can do in this regard? /smo On 2016-03-31 23:12, Pierre Moreau wrote: > Oh, hum, GM108 is NV118 and not NV108 which is Gk208… My bad! > > SMF from the bug report seemed to have some working setup, and since he didn't > pinged back, I guess it's working nicely. But some more checking might still be > needed? > > On 04:59 PM - Mar 31 2016, Ilia

I believe what's missing at this point is a mmiotrace of the NVIDIA driver to make sure that there's nothing different about this GPU. If you can make one (see https://wiki.ubuntu.com/X/MMIOTracing for a guide - should end up ~100MB uncompressed), please send a compressed one to mmio.dumps at gmail.com or make available some other way. On Tue, Feb 14, 2017 at 2:34 PM, Daniel Drake

Hi, all, Is the Xen currently compatible with the InfiniBand? I found some information about the Smart I/O module, but it was posted in 2006. Is the module still maintained? Or, are there any up-to-date alternatives for that? Many thanks, Chiu _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

https://bugs.freedesktop.org/show_bug.cgi?id=107959 Bug ID: 107959 Summary: System hangs up when loading nouveau for NVIDIA MX150 card Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component:

Since quirk_nvidia_hda() was added there's now two nvidia device functions on any laptops with nvidia GPUs: the HDA controller, and the GPU itself. Unfortunately this has the sideaffect of breaking quirk_reset_lenovo_thinkpad_50_nvgpu() since pci_reset_function() was using pci_parent_bus_reset() to reset the GPU's respective PCI bus, and pci_parent_bus_reset() does not work on busses which

On 38+ Intel-based Asus products, the nvidia GPU becomes unusable after S3 suspend/resume. The affected products include multiple generations of nvidia GPUs and Intel SoCs. After resume, nouveau logs many errors such as: fifo: fault 00 [READ] at 0000005555555000 engine 00 [GR] client 04 [HUB/FE] reason 4a [] on channel -1 [007fa91000 unknown] DRM: failed to idle channel 0 [DRM]

The BGL (Boost Graph Library) defines tie(), which is exactly what the tie() defined in STLExtras.h. The header files of GBL use boost::tie(), and other boost libraries use boost::tie() too. How to resolve the ambiguity for compiler? -- Tzu-Chien Chiu, 3D Graphics Hardware Architect <URL:http://www.csie.nctu.edu.tw/~jwchiu>

From: Lukas Wunner <lukas at wunner.de> The integrated HDA controller on Nvidia GPUs can be hidden with a bit in the GPU's config space. Information about this scheme was provided by NVIDIA on their forums. Many laptops now ship with this device hidden, meaning that Linux users of affected platforms (where the HDMI connector comes off the NVIDIA GPU) cannot use HDMI audio

i set up a samba on redhat with a 192.168.x.x ip and and alias of a real ip. on the lan i have win nt and win 2k with real ip that can access the samba without difficulty, but when the win 98/me workstations, with 192.168.x.x ip's, try to connect to the samba, it would be either very slow, or saying that the lan is busy, or cannot connect at all. then, in the samba, i'll see the log

On Fri, Aug 24, 2018 at 11:42 PM, Peter Wu <peter at lekensteyn.nl> wrote: > Are these systems also affected through runtime power management? For > example: > > modprobe nouveau # should enable runtime PM > sleep 6 # wait for runtime suspend to kick in > lspci -s1: # runtime resume by reading PCI config space > > On laptops from