FS#63035 - nouveau 0000:01:00.0: DRM: base-2: timeout

Attached to Project: Arch Linux
Opened by Christian (offlinehoster) - Saturday, 29 June 2019, 08:19 GMT
Last edited by freswa (frederik) - Saturday, 22 February 2020, 21:47 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
since the latest 5.1.15-arch1-1-ARCH I got a lot of

[ 96.167672] nouveau 0000:01:00.0: DRM: base-0: timeout
[ 96.173660] nouveau 0000:01:00.0: DRM: base-1: timeout
[ 98.177212] nouveau 0000:01:00.0: DRM: base-0: timeout
[ 98.185083] nouveau 0000:01:00.0: DRM: base-1: timeout
[ 100.186729] nouveau 0000:01:00.0: DRM: base-0: timeout
[ 100.194488] nouveau 0000:01:00.0: DRM: base-1: timeout
[ 102.194580] nouveau 0000:01:00.0: DRM: base-0: timeout
[ 102.202486] nouveau 0000:01:00.0: DRM: base-1: timeout
[ 104.203327] nouveau 0000:01:00.0: DRM: base-0: timeout
[ 104.211558] nouveau 0000:01:00.0: DRM: base-1: timeout
…
[ 123.685624] nouveau 0000:01:00.0: DRM: core notifier timeout

The applications are not responding anymore. Mouse is not moving, just sometimes for 1 or 2 seconds. Than it is freezed again.

00:02.0 VGA compatible controller: Intel Corporation HD Graphics P530 (rev 06)
01:00.0 VGA compatible controller: NVIDIA Corporation GM107GLM [Quadro M2000M] (rev a2)


I did a downgrade by
pacman -U /var/cache/pacman/pkg/linux-5.1.14.arch1-1-x86_64.pkg.tar.xz

That seems to work currently.
This task depends upon

Closed by  freswa (frederik)
Saturday, 22 February 2020, 21:47 GMT
Reason for closing:  None
Additional comments about closing:  This seems pretty stalled to me. If it's still an issue, please fill a re-open request. Thank you :)
Comment by loqs (loqs) - Tuesday, 09 July 2019, 17:21 GMT
Is linux 5.2.arch2-1 in testing affected?
If so what is the full dmesg for a boot under affected kernel and from an unaffected kernel?
Are you willing to bisect between 5.1.14 and 5.1.15 to find the causal commit?
Have you reported the issue upstream?
Comment by Christian (offlinehoster) - Wednesday, 10 July 2019, 10:14 GMT
Hi, currently I'm running 5.1.16-arch1-1-ARCH works for me right now.

How can I report the issue upstream?
Comment by Christian (offlinehoster) - Wednesday, 10 July 2019, 11:28 GMT

Loading...