Bug 1399086 - nouveau 0000:01:00.0: DRM: Pointer to flat panel table invalid [NEEDINFO]
Summary: nouveau 0000:01:00.0: DRM: Pointer to flat panel table invalid
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 24
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-28 09:24 UTC by danielemi
Modified: 2019-01-09 12:54 UTC (History)
27 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-04-28 17:10:31 UTC
Type: Bug
jforbes: needinfo?


Attachments (Terms of Use)
system logs output (20.15 KB, application/zip)
2016-11-28 09:24 UTC, danielemi
no flags Details
last logs (19.95 KB, application/x-xz)
2017-01-23 23:38 UTC, danielemi
no flags Details

Description danielemi 2016-11-28 09:24:22 UTC
Created attachment 1225214 [details]
system logs output

Description of problem:

In my Acer Aspire V5-573G (i7-4500U, Intel VGA + Nvidia Geforce 720m), after few seconds of boot load, the boot halts with this error: "DRM: Pointer to flat panel table invalid". This is a blocking error in Fedora 24; instead, it happens but it is a non-blocking in version 25.

dmesg output:
[1.616204] nouveau 0000:01:00.0: enabling device (0006 -> 0007)
[1.616336] nouveau 0000:01:00.0: NVIDIA GF117 (0d7000a2)
[1.632909] nouveau 0000:01:00.0: bios: version 75.17.5e.00.01
[1.716593] nouveau 0000:01:00.0: fb: 2048 MiB DDR3
[2.358262] nouveau 0000:01:00.0: DRM: VRAM: 2048 MiB
[2.358263] nouveau 0000:01:00.0: DRM: GART: 1048576 MiB
[2.358266] nouveau 0000:01:00.0: DRM: Pointer to TMDS table invalid
[2.358272] nouveau 0000:01:00.0: DRM: DCB version 4.0
[2.358273] nouveau 0000:01:00.0: DRM: Pointer to flat panel table invalid
[2.484770] nouveau 0000:01:00.0: DRM: MM: using COPY0 for buffer copies
[2.484777] [drm] Initialized nouveau 1.3.1 20120801 for 0000:01:00.0 on minor 1
[8.177172] nouveau 0000:01:00.0: DRM: evicting buffers...
[8.177173] nouveau 0000:01:00.0: DRM: waiting for kernel channels to go idle...
[8.177266] nouveau 0000:01:00.0: DRM: suspending client object trees...
[8.177519] nouveau 0000:01:00.0: DRM: suspending kernel object tree...
[37.890018] nouveau 0000:01:00.0: DRM: resuming kernel object tree...
[37.996374] nouveau 0000:01:00.0: DRM: resuming client object trees...
[44.018840] nouveau 0000:01:00.0: DRM: evicting buffers...
[44.018844] nouveau 0000:01:00.0: DRM: waiting for kernel channels to go idle...
[44.018880] nouveau 0000:01:00.0: DRM: suspending client object trees...
[44.019138] nouveau 0000:01:00.0: DRM: suspending kernel object tree...

lspci output:
00:02.0 VGA compatible controller [0300]: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09)
01:00.0 3D controller [0302]: NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] [10de:1140] (rev a1)

lsmod output:
uvcvideo               90112  0
videobuf2_vmalloc      16384  1 uvcvideo
videobuf2_memops       16384  1 videobuf2_vmalloc
videobuf2_v4l2         24576  1 uvcvideo
videobuf2_core         40960  2 uvcvideo,videobuf2_v4l2
videodev              172032  3 uvcvideo,videobuf2_core,videobuf2_v4l2
media                  40960  2 uvcvideo,videodev
video                  40960  3 acer_wmi,nouveau,i915
drm_kms_helper        151552  2 nouveau,i915
drm                   344064  13 nouveau,i915,ttm,drm_kms_helper


Steps to Reproduce:
1. Boot Fedora in Acer Aspire V5-573G
2. 
3.

Comment 1 danielemi 2017-01-23 23:38:05 UTC
Created attachment 1243778 [details]
last logs

Just attached the last logs, the complete one.

Comment 2 danielemi 2017-01-23 23:52:58 UTC
for your knowledge, these days also this error started appearing:

https://bugzilla.redhat.com/show_bug.cgi?id=1415853

Comment 3 imbacen 2017-02-13 08:57:05 UTC
Same error on my Lenovo Y50 on F25, I suspect my screen is sometimes black when coming out of suspend because of this (but can't confirm this yet, need to try and ssh in when it happens..).

01:00.0 3D controller: NVIDIA Corporation GM107M [GeForce GTX 960M] (rev a2)


[    4.296524] nouveau: detected PR support, will not use DSM
[    4.296543] nouveau 0000:01:00.0: enabling device (0006 -> 0007)
[    4.296836] nouveau 0000:01:00.0: NVIDIA GM107 (1171b0a2)
[    4.318939] nouveau 0000:01:00.0: bios: version 82.07.7c.00.0c
[    4.428635] nouveau 0000:01:00.0: fb: 4096 MiB GDDR5
[    4.428692] nouveau 0000:01:00.0: priv: HUB0: 10ecc0 ffffffff (1e40822c)
[    4.482482] nouveau 0000:01:00.0: DRM: VRAM: 4096 MiB
[    4.482483] nouveau 0000:01:00.0: DRM: GART: 1048576 MiB
[    4.482484] nouveau 0000:01:00.0: DRM: Pointer to TMDS table invalid
[    4.482485] nouveau 0000:01:00.0: DRM: DCB version 4.0
[    4.482486] nouveau 0000:01:00.0: DRM: Pointer to flat panel table invalid
[    4.607622] nouveau 0000:01:00.0: DRM: MM: using COPY for buffer copies
[    4.607626] [drm] Initialized nouveau 1.3.1 20120801 for 0000:01:00.0 on minor 1

mxm_wmi                16384  1 nouveau
ttm                    94208  1 nouveau
i2c_algo_bit           16384  2 nouveau,i915
drm_kms_helper        151552  2 nouveau,i915
drm                   339968  12 nouveau,i915,ttm,drm_kms_helper
video                  40960  3 nouveau,i915,ideapad_laptop
wmi                    16384  3 mxm_wmi,nouveau,ideapad_laptop

Comment 4 Justin M. Forbes 2017-04-11 14:52:16 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 24 kernel bugs.

Fedora 25 has now been rebased to 4.10.9-100.fc24.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 26, and are still experiencing this issue, please change the version to Fedora 26.

If you experience different issues, please open a new bug report for those.

Comment 5 Justin M. Forbes 2017-04-28 17:10:31 UTC
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and attach the 
relevant data from the latest kernel you are running and any data that might have been requested previously.


Note You need to log in before you can comment on or make changes to this bug.