[Nvidia Quadro P1000] Live USB freezes or cannot complete install when nouveau driver is loaded (crashing in gp100/gf100 code)

This archive contains the data gathered by sosreport from a live session when nouveau is blacklisted.

You may have to `sudo tar xvf sosreport-ubuntu-20190328033617.tar.xz` to be able to extract it.

This is the dmesg I get when booting with 19.04 beta and the default parameters (i.e. nouveau activated) on this device.

Just to make sure, I updated the BIOS of this device from 1.4.2 to 1.7.0. However, the same problems arise. Please find dmesg from an updated BIOS with nouveau drivers activated (i.e. default mode)

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1822026

please try mainline build of 5.1-rc from

http://kernel.ubuntu.com/~kernel-ppa/mainline/

upstream actually suggested earlier to disable nouveau modeset by default, so that it would have to be explicitly enabled if needed.. and it usually isn't, since it's more or less just getting in the way when trying to get the system installed with the NVIDIA driver

sorry, 5.1 won't help either, it's apparently a bug in the firmware and the only way to "fix" it is to use nouveau.modeset=0

This bug was fixed in the package linux - 5.0.0-11.12

---------------
linux (5.0.0-11.12) disco; urgency=medium

  * linux: 5.0.0-11.12 -proposed tracker (LP: #1824383)

  * hns3: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1]
    (LP: #1824194)
    - net: hns3: fix for not calculating tx bd num correctly

  * disco: unable to use iptables/enable ufw under -virtual kernel
    (LP: #1823862)
    - [Packaging] add bpfilter to linux-modules

  * Make shiftfs a module rather than built-in (LP: #1824354)
    - [Config] CONFIG_SHIFT_FS=m

  * shiftfs: chown sets untranslated ids in lower fs (LP: #1824350)
    - SAUCE: shiftfs: use translated ids when chaning lower fs attrs

  * [Hyper-V] KVP daemon fails to start on first boot of disco VM (LP: #1820063)
    - [Packaging] bind hv_kvp_daemon startup to hv_kvp device

linux (5.0.0-10.11) disco; urgency=medium

  * linux: 5.0.0-10.11 -proposed tracker (LP: #1823936)

  * Apparmor enforcement failure in lxc selftests (LP: #1823379)
    - SAUCE: apparmor: Restore Y/N in /sys for apparmor's "enabled"

  * systemd cause kernel trace "BUG: unable to handle kernel paging request at
    6db23a14" on Cosmic i386 (LP: #1813244)
    - openvswitch: fix flow actions reallocation

linux (5.0.0-9.10) disco; urgency=medium

  * linux: 5.0.0-9.10 -proposed tracker (LP: #1823228)

  * Packaging resync (LP: #1786013)
    - [Packaging] resync git-ubuntu-log
    - [Packaging] update helper scripts
    - [Packaging] resync retpoline extraction

  * Huawei Hi1822 NIC has poor performance (LP: #1820187)
    - net-next/hinic: replace disable_irq_nosync/enable_irq

  * Add uid shifting overlay filesystem (shiftfs) (LP: #1823186)
    - shiftfs: uid/gid shifting bind mount
    - shiftfs: rework and extend
    - shiftfs: support some btrfs ioctls
    - [Config] enable shiftfs

  * Cannot boot or install - have to use nomodeset (LP: #1821820)
    - Revert "drm/i915/fbdev: Actually configure untiled displays"

  * Disco update: v5.0.6 upstream stable release (LP: #1823060)
    - netfilter: nf_tables: fix set double-free in abort path
    - dccp: do not use ipv6 header for ipv4 flow
    - genetlink: Fix a memory leak on error path
    - gtp: change NET_UDP_TUNNEL dependency to select
    - ipv6: make ip6_create_rt_rcu return ip6_null_entry instead of NULL
    - mac8390: Fix mmio access size probe
    - mISDN: hfcpci: Test both vendor & device ID for Digium HFC4S
    - net: aquantia: fix rx checksum offload for UDP/TCP over IPv6
    - net: datagram: fix unbounded loop in __skb_try_recv_datagram()
    - net/packet: Set __GFP_NOWARN upon allocation in alloc_pg_vec
    - net: phy: meson-gxl: fix interrupt support
    - net: rose: fix a possible stack overflow
    - net: stmmac: fix memory corruption with large MTUs
    - net-sysfs: call dev_hold if kobject_init_and_add success
    - net: usb: aqc111: Extend HWID table by QNAP device
    - packets: Always register packet sk in the same order
    - rhashtable: Still do rehash when we get EEXIST
    - sctp: get sctphdr by offset in sctp_compute_cksum
    - sctp: use memdup_user instead of vmemdup_user
    - tcp: do not use ipv6 header for ipv4 flow
    - tipc: allow servic...

The commit will be reverted due to 1824677, so reopening until a patch with a smaller impact will be applied

For Optimus platforms like this one, nouveau.runpm=0 should be sufficient.

Is this bug still valid?

I think I've seen a couple of users successfully using P1000 recently.

right, should be tested on eoan at least, disco can't be fixed anymore

Confirmed still not working with 19.10 (linux 5.3.0-18-generic) on the Precision 7530. It's actually even worse: now, I can't even boot. I'm just shown a black screen.

If I select the Safe graphics boot option, I can boot properly.

Editing the default boot command line to include `nouveau.modeset=0` works, but editing it to put `nouveau.runpm=0` instead fails (black screen).

I assume this is fixed in focal, as there haven't been reports saying otherwise