Bug 100659 - [nouveau] Certain errors on initializing GTX 1060 6GB
Summary: [nouveau] Certain errors on initializing GTX 1060 6GB
Status: RESOLVED INVALID
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/nouveau (show other bugs)
Version: git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Nouveau Project
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-04-12 07:50 UTC by Artem S. Tashkinov
Modified: 2017-04-12 09:27 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments

Description Artem S. Tashkinov 2017-04-12 07:50:55 UTC 
[   85.170719] [drm] Initialized
[   85.297953] nouveau 0000:01:00.0: NVIDIA GP106 (136000a1)
[   85.404652] nouveau 0000:01:00.0: bios: version 86.06.0e.00.28
[   85.405558] nouveau 0000:01:00.0: fb: 6144 MiB GDDR5
[   85.405562] nouveau 0000:01:00.0: priv: HUB0: 00d054 00000007 (1f408216)
[   85.407278] nouveau 0000:01:00.0: DRM: VRAM: 6144 MiB
[   85.407280] nouveau 0000:01:00.0: DRM: GART: 1048576 MiB
[   85.407283] nouveau 0000:01:00.0: DRM: BIT table 'A' not found
[   85.407284] nouveau 0000:01:00.0: DRM: BIT table 'L' not found
[   85.407286] nouveau 0000:01:00.0: DRM: TMDS table version 2.0
[   85.407287] nouveau 0000:01:00.0: DRM: DCB version 4.1
[   85.407289] nouveau 0000:01:00.0: DRM: DCB outp 00: 01000f42 04620030
[   85.407291] nouveau 0000:01:00.0: DRM: DCB outp 01: 04811f96 04600020
[   85.407293] nouveau 0000:01:00.0: DRM: DCB outp 02: 04011f92 04620020
[   85.407294] nouveau 0000:01:00.0: DRM: DCB outp 03: 04822f86 04600010
[   85.407295] nouveau 0000:01:00.0: DRM: DCB outp 04: 04022f82 04620010
[   85.407297] nouveau 0000:01:00.0: DRM: DCB outp 06: 02033f62 04620010
[   85.407298] nouveau 0000:01:00.0: DRM: DCB outp 07: 02844f76 04600020
[   85.407299] nouveau 0000:01:00.0: DRM: DCB outp 08: 02044f72 00020020
[   85.407301] nouveau 0000:01:00.0: DRM: DCB conn 00: 00001031
[   85.407302] nouveau 0000:01:00.0: DRM: DCB conn 01: 02000146
[   85.407304] nouveau 0000:01:00.0: DRM: DCB conn 02: 01000246
[   85.407305] nouveau 0000:01:00.0: DRM: DCB conn 03: 00010361
[   85.407306] nouveau 0000:01:00.0: DRM: DCB conn 04: 00020446
[   85.407308] nouveau 0000:01:00.0: DRM: Pointer to flat panel table invalid
[   85.470272] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[   85.470274] [drm] Driver supports precise vblank timestamp query.
[   85.488355] nouveau 0000:01:00.0: hwmon_device_register() is deprecated. Please convert the driver to use hwmon_device_register_with_info().
[   85.514327] nouveau 0000:01:00.0: DRM: failed to create kernel channel, -22
[   85.690271] nouveau 0000:01:00.0: DRM: allocated 1920x1080 fb: 0x60000, bo ffff9fabcb0a0c00
[   85.694638] fbcon: nouveaufb (fb0) is primary device
[   86.071445] nouveau 0000:01:00.0: fb0: nouveaufb frame buffer device
[   86.075582] [drm] Initialized nouveau 1.3.1 20120801 for 0000:01:00.0 on minor 0

I just wanted to know if these messages are safe to ignore or they are indeed something you might want to pay close attention to:

1. nouveau 0000:01:00.0: DRM: Pointer to flat panel table invalid
2. nouveau 0000:01:00.0: DRM: failed to create kernel channel, -22

I'm running:

Linux localhost.localdomain 4.10.9-200.fc25.x86_64 #1 SMP Mon Apr 10 14:48:16 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Comment 1 Artem S. Tashkinov 2017-04-12 08:10:54 UTC 
I didn't notice any immediate errors or problems.
Comment 2 Pierre Moreau 2017-04-12 09:27:34 UTC 
> nouveau 0000:01:00.0: DRM: Pointer to flat panel table invalid
This should be safe to ignore.

> nouveau 0000:01:00.0: DRM: failed to create kernel channel, -22
For acceleration support, you need at least Linux 4.12 as well as a recent (at least from 1st March 2017) version of linux-firmware (https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/).

Feel free to reopen if you are still experiencing the last issue after updating.

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.