| Summary: | Nouveau produces soft lockups | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | xorg | Reporter: | celelibi | ||||||
| Component: | Driver/nouveau | Assignee: | Nouveau Project <nouveau> | ||||||
| Status: | RESOLVED MOVED | QA Contact: | Xorg Project Team <xorg-team> | ||||||
| Severity: | normal | ||||||||
| Priority: | medium | CC: | Bastha.oleng, fdsfgs, peter | ||||||
| Version: | unspecified | ||||||||
| Hardware: | Other | ||||||||
| OS: | All | ||||||||
| Whiteboard: | |||||||||
| i915 platform: | i915 features: | ||||||||
| Attachments: |
|
||||||||
Created attachment 129216 [details]
acpidump -z -o acpidump.txt
Based on your acpidump for an Alienware 15 R3/0GY3V1, BIOS 1.0.8 11/12/2016 with GTX 1070, I found this in ssdt6.dsl:
Method (PGOF, 1, Serialized)
{
...
If (((\_SB.GGIV (0x01030009) == Zero) || (OSYS == 0x07D9)))
{
...
}
Else
{
LKDS (PIOF)
}
...
}
This is a common pattern that is known to give issues. The "LKDS" part seems to cause issues, so you want to force the other code path. As OSYS is 2009 (set in DSDT), try booting with:
acpi_osi=! acpi_osi="Windows 2009"
See also https://bugzilla.kernel.org/show_bug.cgi?id=156341
I'm not sure what it means, but this works around the issue as well. -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/issues/316. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
Created attachment 128914 [details] dmesg log from boot to bug Nouveau driver seems to produce soft lockups. The most notable effect is that some syscalls "hangs", the whole system become very slow and this kind f message appear in every terminals: NMI watchdog: BUG: soft lockup - CPU#6 stuck for 23s! [kworker/6:2:324] This seems related to power management, since adding the option runpm=0 doesn't produce the lockups. This bug can be triggered by many things, including running commands like lspci. I attach the dmesg log from boot up to the bug.