All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 199781] New: nouveau: cannot boot without nouveau.modeset=0 and cannot use HDMI output
Date: Mon, 21 May 2018 10:13:56 +0000	[thread overview]
Message-ID: <bug-199781-2300@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=199781

            Bug ID: 199781
           Summary: nouveau: cannot boot without nouveau.modeset=0 and
                    cannot use HDMI output
           Product: Drivers
           Version: 2.5
    Kernel Version: 4.16.x
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: blocking
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: frederic.epitre@orange.fr
        Regression: No

Created attachment 276083
  --> https://bugzilla.kernel.org/attachment.cgi?id=276083&action=edit
dmesg log of kernel entries

Hi,

I'm currently having an issue while trying to use my discrete card GTX1050TI on
my laptop Acer Predator PH317-51 under QubesOS with any kernel (e.g. 4.14+ and
4.16+, the current one is 4.16.9). In order to boot, I have to set
nouveau.modeset=0 but I cannot use my HDMI output because it is not detected
and it seems that the HDMI port is wired to the NVIDIA card. If I remove this
option in the grub conf, and I plug my second screen on the HDMI port, at the
boot process, I'm having error such as (full dmesg log is attached):

May 21 11:33:01 dom0 kernel: ------------[ cut here ]------------
May 21 11:33:01 dom0 kernel: nouveau 0000:01:00.0: timeout
May 21 11:33:01 dom0 kernel: WARNING: CPU: 2 PID: 77 at
/home/user/rpmbuild/BUILD/kernel-latest-4.16.9/linux-4.16.9/drivers/gpu/drm/nouveau/nvkm/engine/disp/sornv50.c:43
nv50_sor_power_wait+0x8b/0xa0 [nouveau]
May 21 11:33:01 dom0 kernel: Modules linked in: loop ebtable_filter ebtables
ip6table_filter ip6_tables snd_hda_codec_hdmi joydev dcdbas dell_wmi_descriptor
uvcvideo ath10k_pci btusb videobuf2_vmalloc btrtl iTCO_wdt videobuf2_memops
btbcm iTCO_vendor_support videobuf2_v4l2 hid_multitouch btintel ath10k_core
snd_hda_codec_realtek snd_hda_codec_generic videobuf2_common bluetooth videodev
mac80211 media snd_hda_intel ecdh_generic ath intel_rapl snd_hda_codec
x86_pkg_temp_thermal intel_powerclamp snd_hda_core coretemp snd_hwdep snd_seq
snd_seq_device intel_rapl_perf snd_pcm rtsx_pci_ms pcspkr cfg80211 acer_wmi
snd_timer sparse_keymap wmi_bmof intel_wmi_thunderbolt memstick idma64 i2c_i801
r8169 rfkill mii mei_me snd intel_lpss_pci tpm_crb tpm_tis mei
intel_pch_thermal intel_lpss soundcore tpm_tis_core pinctrl_sunrisepoint
May 21 11:33:01 dom0 kernel: pinctrl_intel tpm xenfs dm_thin_pool
dm_persistent_data libcrc32c dm_bio_prison dm_crypt rtsx_pci_sdmmc mmc_core
crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel nouveau i915
nvme mxm_wmi ttm i2c_algo_bit serio_raw drm_kms_helper nvme_core rtsx_pci
xhci_pci drm xhci_hcd i2c_hid wmi video xen_acpi_processor xen_privcmd
xen_pciback xen_blkback xen_gntalloc xen_gntdev xen_evtchn uinput
May 21 11:33:01 dom0 kernel: CPU: 2 PID: 77 Comm: kworker/2:1 Tainted: G     U 
W        4.16.9-1.pvops.qubes.x86_64 #1
May 21 11:33:01 dom0 kernel: Hardware name: Acer Predator PH317-51/Sienna_KLS,
BIOS V1.13 12/26/2017
May 21 11:33:01 dom0 kernel: Workqueue: pm pm_runtime_work
May 21 11:33:01 dom0 kernel: RIP: e030:nv50_sor_power_wait+0x8b/0xa0 [nouveau]
May 21 11:33:01 dom0 kernel: RSP: e02b:ffffc9000188fb90 EFLAGS: 00010282
May 21 11:33:01 dom0 kernel: RAX: 0000000000000000 RBX: ffff880180e8fa60 RCX:
0000000000000000
May 21 11:33:01 dom0 kernel: RDX: ffff88018629cd00 RSI: ffff880186296938 RDI:
ffff880186296938
May 21 11:33:01 dom0 kernel: RBP: ffff88017bf30c00 R08: 0000000000000000 R09:
00000000000007da
May 21 11:33:01 dom0 kernel: R10: ffffea0005fa6cc0 R11: 0000000000000001 R12:
ffff880179fb3d20
May 21 11:33:01 dom0 kernel: R13: 000000000061d804 R14: 00000012119b61c0 R15:
0000000000000000
May 21 11:33:01 dom0 kernel: FS:  0000000000000000(0000)
GS:ffff880186280000(0000) knlGS:0000000000000000
May 21 11:33:01 dom0 kernel: CS:  e033 DS: 0000 ES: 0000 CR0: 0000000080050033
May 21 11:33:01 dom0 kernel: CR2: 00005c557ebab0d8 CR3: 000000017cae2000 CR4:
0000000000042660
May 21 11:33:01 dom0 kernel: Call Trace:
May 21 11:33:01 dom0 kernel: nv50_sor_power+0x50/0x120 [nouveau]
May 21 11:33:01 dom0 kernel: nv50_disp_root_init_+0x63/0x80 [nouveau]
May 21 11:33:01 dom0 kernel: nvkm_oproxy_init+0x3c/0x60 [nouveau]
May 21 11:33:01 dom0 kernel: nvkm_object_init+0x3e/0x190 [nouveau]
May 21 11:33:01 dom0 kernel: nvkm_object_init+0xb1/0x190 [nouveau]
May 21 11:33:01 dom0 kernel: nvkm_object_init+0xb1/0x190 [nouveau]
May 21 11:33:01 dom0 kernel: nvkm_object_fini+0xa2/0x230 [nouveau]
May 21 11:33:01 dom0 kernel: ? pci_pm_runtime_resume+0xa0/0xa0
May 21 11:33:01 dom0 kernel: nouveau_do_suspend+0x199/0x2b0 [nouveau]
May 21 11:33:01 dom0 kernel: nouveau_pmops_runtime_suspend+0x54/0xb0 [nouveau]
May 21 11:33:01 dom0 kernel: pci_pm_runtime_suspend+0x57/0x160
May 21 11:33:01 dom0 kernel: ? pci_pm_runtime_resume+0xa0/0xa0
May 21 11:33:01 dom0 kernel: __rpm_callback+0xc7/0x200
May 21 11:33:01 dom0 kernel: rpm_callback+0x1f/0x70
May 21 11:33:01 dom0 kernel: ? pci_pm_runtime_resume+0xa0/0xa0
May 21 11:33:01 dom0 kernel: rpm_suspend+0x129/0x640
May 21 11:33:01 dom0 kernel: ? finish_task_switch+0x80/0x2a0
May 21 11:33:01 dom0 kernel: pm_runtime_work+0x6e/0x90
May 21 11:33:01 dom0 kernel: process_one_work+0x177/0x350
May 21 11:33:01 dom0 kernel: worker_thread+0x4d/0x3c0
May 21 11:33:01 dom0 kernel: kthread+0xf8/0x130
May 21 11:33:01 dom0 kernel: ? rescuer_thread+0x350/0x350
May 21 11:33:01 dom0 kernel: ? kthread_create_worker_on_cpu+0x70/0x70
May 21 11:33:01 dom0 kernel: ret_from_fork+0x35/0x40
May 21 11:33:01 dom0 kernel: Code: 41 5c 41 5d 41 5e c3 48 8b 7d 10 48 8b 5f 50
48 85 db 74 22 e8 17 bf 09 c1 48 89 da 48 89 c6 48 c7 c7 d5 2f 63 c0 e8 15 ec
b9 c0 <0f> 0b 5b 5d 41 5c 41 5d 41 5e c3 48 8b 5f 10 eb d8 0f 1f 40 00 
May 21 11:33:01 dom0 kernel: ---[ end trace d0a5d6934bf5bd19 ]---

And I finally end with a kernel panic. If I don't plug my second screen on the
HDMI port, I can boot but the Xserver crashes when trying to log in XFCE
session. I also tried to restrict the xrandr settings at the login session
without any success. Please note that it has nothing to do with QubesOS as I
tested and encountered the same problem with a fresh up to date Fedora 28.

If some of the developers of the nouveau driver can oriented me where to dig in
the source code, I would be please to learn and do some tests or patches, even
for helping in the future.

Thank you in advance for any help.
Frédéric

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2018-05-21 10:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-21 10:13 bugzilla-daemon [this message]
2018-05-21 12:43 ` [Bug 199781] nouveau: cannot boot without nouveau.modeset=0 and cannot use HDMI output bugzilla-daemon
2018-05-21 13:04 ` bugzilla-daemon
2018-05-21 13:05 ` bugzilla-daemon

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=bug-199781-2300@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.