Bug 100423

Summary: MMIO read of 00000000 FAULT at 022554 [ IBUS ]
Product: xorg Reporter: Bruno Pagani <bruno.n.pagani>
Component: Driver/nouveauAssignee: Nouveau Project <nouveau>
Status: RESOLVED MOVED QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: medium CC: adamos, alex-kas, bruno.n.pagani, egorr.berd, fixpoint.combinator, jean-louis
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
dmesg output none

Description Bruno Pagani 2017-03-27 20:42:44 UTC
Created attachment 130492 [details]
dmesg output

Hi there,

I’ve got a new laptop since a couple months, and I’m starting to configure it intensively and report bug. It’s an HP zBook Studio G3, with a Core i7-6700HQ with Intel HD graphics and a dedicated NVIDIA Corporation GM107GLM [Quadro M1000M] card. Amongst the issue I find in dmesg, there is those two lines that appear in red:

[   16.246988] nouveau 0000:01:00.0: priv: HUB0: 614900 00800000 (18408200)
[   16.248921] nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 022554 [ IBUS ]

I’ve attached the full dmesg.
Comment 1 gene 2017-04-07 13:37:01 UTC
I have similar issue on dell precision 5520 with 
Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz
Has nvidia maxwell (NV117) and 4k touch screen

I see these :


 nouveau 0000:01:00.0: fb: 4096 MiB GDDR5 
 nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 10ac08 [ IBUS ] 
 nouveau 0000:01:00.0: priv: HUB0: 10ecc0 ffffffff (1f40822c) 
 vga_switcheroo: enabled
 [TTM] Zone  kernel: Available graphics memory: 16334986 kiB 
 [TTM] Zone   dma32: Available graphics memory: 2097152 kiB 
 [TTM] Initializing pool allocator 
 [TTM] Initializing DMA pool allocator 
 nouveau 0000:01:00.0: DRM: VRAM: 4096 MiB 
 nouveau 0000:01:00.0: DRM: GART: 1048576 MiB 
 nouveau 0000:01:00.0: DRM: Pointer to TMDS table invalid 
 nouveau 0000:01:00.0: DRM: DCB version 4.0 
 nouveau 0000:01:00.0: DRM: Pointer to flat panel table invalid
Comment 2 Arthur Borsboom 2017-04-13 13:09:43 UTC
Same for: Intel i7-4710HQ + GM107M [GeForce GTX 850M]

[    1.950230] nouveau: detected PR support, will not use DSM
[    1.950384] nouveau 0000:01:00.0: NVIDIA GM107 (117110a2)
[    1.979948] nouveau 0000:01:00.0: bios: version 82.07.47.00.06
[    2.071839] nouveau 0000:01:00.0: fb: 2048 MiB DDR3
[    2.071853] nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 022554 [ IBUS ]
[    2.071913] nouveau 0000:01:00.0: priv: HUB0: 10ecc0 ffffffff (1840822c)
[    3.157435] nouveau 0000:01:00.0: DRM: VRAM: 2048 MiB
[    3.157436] nouveau 0000:01:00.0: DRM: GART: 1048576 MiB
[    3.157438] nouveau 0000:01:00.0: DRM: Pointer to TMDS table invalid
[    3.157438] nouveau 0000:01:00.0: DRM: DCB version 4.0
[    3.157439] nouveau 0000:01:00.0: DRM: Pointer to flat panel table invalid
[    3.227691] nouveau 0000:01:00.0: hwmon_device_register() is deprecated. Please convert the driver to use hwmon_device_register_with_info().
[    3.286804] nouveau 0000:01:00.0: DRM: MM: using COPY for buffer copies
[    3.286815] [drm] Initialized nouveau 1.3.1 20120801 for 0000:01:00.0 on minor 1
Comment 3 Johnny B. Goode 2017-05-02 13:47:01 UTC
Almost same for i7-6700, GM206 [GTX 950]
No touch screen, no hybrid graphics. Pure desktop. Intel 530 on chip but disabled in BIOS. Only one Asus Graphic Card.
Problem started on Kernel 4.10.x and is going on 4.11.0. Kernel 4.9.x is FAULT free. Different distributions Fedora 25, Gentoo.
------------------------------------

dmesg | grep -i nouveau
[    1.688288] fb: switching to nouveaufb from EFI VGA
[    1.689206] nouveau 0000:01:00.0: NVIDIA GM206 (126020a1)
[    1.787066] nouveau 0000:01:00.0: bios: version 84.06.3d.00.6f
[    1.787209] nouveau 0000:01:00.0: disp: dcb 15 type 8 unknown
[    1.787571] nouveau 0000:01:00.0: fb: 2048 MiB GDDR5
[    1.787585] nouveau 0000:01:00.0: bus: MMIO write of 80000136 FAULT at 10eb14 [ IBUS ]
[    1.794508] nouveau 0000:01:00.0: DRM: VRAM: 2048 MiB
[    1.794509] nouveau 0000:01:00.0: DRM: GART: 1048576 MiB
[    1.794512] nouveau 0000:01:00.0: DRM: TMDS table version 2.0
[    1.794513] nouveau 0000:01:00.0: DRM: DCB version 4.1
[    1.794515] nouveau 0000:01:00.0: DRM: DCB outp 00: 01000f02 00020030
[    1.794517] nouveau 0000:01:00.0: DRM: DCB outp 01: 02000f00 00000000
[    1.794518] nouveau 0000:01:00.0: DRM: DCB outp 02: 02811f66 04400010
[    1.794520] nouveau 0000:01:00.0: DRM: DCB outp 03: 02011f62 00020010
[    1.794522] nouveau 0000:01:00.0: DRM: DCB outp 04: 02022f72 00020020
[    1.794523] nouveau 0000:01:00.0: DRM: DCB outp 05: 04033f82 00020030
[    1.794525] nouveau 0000:01:00.0: DRM: DCB outp 15: 01df4ff8 00000000
[    1.794526] nouveau 0000:01:00.0: DRM: DCB conn 00: 00001030
[    1.794528] nouveau 0000:01:00.0: DRM: DCB conn 01: 00010146
[    1.794529] nouveau 0000:01:00.0: DRM: DCB conn 02: 00020261
[    1.794531] nouveau 0000:01:00.0: DRM: DCB conn 03: 02000331
[    1.794532] nouveau 0000:01:00.0: DRM: DCB conn 04: 00000470
[    1.794534] nouveau 0000:01:00.0: DRM: Pointer to flat panel table invalid
[    1.828756] nouveau 0000:01:00.0: DRM: unknown connector type 70
[    1.828775] nouveau 0000:01:00.0: DRM: failed to create encoder 1/8/0: -19
[    1.828778] nouveau 0000:01:00.0: DRM: Unknown-1 has no encoders, removing
[    1.934421] nouveau 0000:01:00.0: hwmon_device_register() is deprecated. Please convert the driver to use hwmon_device_register_with_info().
[    1.993646] nouveau 0000:01:00.0: DRM: MM: using COPY for buffer copies
[    2.072744] nouveau 0000:01:00.0: priv: GPC0: 419df4 00000000 (1c40820e)
[    2.072763] nouveau 0000:01:00.0: priv: GPC1: 419df4 00000000 (1c40820e)
[    2.174707] nouveau 0000:01:00.0: DRM: allocated 1600x1200 fb: 0x60000, bo ffff9b09ca6eb800
[    2.176838] fbcon: nouveaufb (fb0) is primary device
[    2.375660] nouveau 0000:01:00.0: fb0: nouveaufb frame buffer device
[    2.389828] [drm] Initialized nouveau 1.3.1 20120801 for 0000:01:00.0 on minor 0

Almost same, because my FAULT is at 10eb14 
------------------------------------

01:00.0 VGA compatible controller: NVIDIA Corporation GM206 [GeForce GTX 950] (rev a1) (prog-if 00 [VGA controller])
	Subsystem: ASUSTeK Computer Inc. Device 8555
	Flags: bus master, fast devsel, latency 0, IRQ 134
	Memory at de000000 (32-bit, non-prefetchable) [size=16M]
	Memory at 2fe0000000 (64-bit, prefetchable) [size=256M]
	Memory at 2ff0000000 (64-bit, prefetchable) [size=32M]
	I/O ports at e000 [size=128]
	Expansion ROM at 000c0000 [disabled] [size=128K]
	Capabilities: [60] Power Management version 3
	Capabilities: [68] MSI: Enable+ Count=1/1 Maskable- 64bit+
	Capabilities: [78] Express Legacy Endpoint, MSI 00
	Capabilities: [100] Virtual Channel
	Capabilities: [258] L1 PM Substates
	Capabilities: [128] Power Budgeting <?>
	Capabilities: [420] Advanced Error Reporting
	Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?>
	Capabilities: [900] #19
	Kernel driver in use: nouveau
	Kernel modules: nouveau
------------------------------------

xorg-x11-drv-nouveau-1.0.14-2.fc25.x86_64
libdrm-2.4.79-1.fc25.x86_64
and:
xf86-video-nouveau-1.0.13
libdrm-2.4.75

Should I open a new bug with "FAULT at 10eb14" or is it this same issue?
Comment 4 Bruno Pagani 2017-05-12 17:05:40 UTC
@gene, Johnny B. Goode: From what I know, the “at” value matters, because they have meanings. Though from one generation to another this could be different values for the same register.

Also, @Johnny, in your case it’s a write instead of a read, so I would definitively open another issue.
Comment 5 rosenp 2017-08-10 02:24:40 UTC
I've bisected the issue. It happens with this commit:

	
fb/gf100-: modify constructors to allow more customisation
Comment 6 Ilia Mirkin 2017-12-19 19:51:28 UTC
Looks like 22554 is no longer available on Maxwell. See where ltc reads it from for the new location. Needs to be split out of ramgk104 somehow.
Comment 7 Ben Skeggs 2017-12-19 22:49:36 UTC
(In reply to Ilia Mirkin from comment #6)
> Looks like 22554 is no longer available on Maxwell. See where ltc reads it
> from for the new location. Needs to be split out of ramgk104 somehow.

I have WIP patches in my Fermi reclocking code (I'll try and push before I leave for xmas break) that begin to address this.
Comment 8 Bruno Pagani 2018-01-28 21:34:05 UTC
There is a new one now (10ac08, in addition to 022554):
```
[   10.667586] nouveau 0000:01:00.0: enabling device (0006 -> 0007)
[   10.667788] nouveau 0000:01:00.0: NVIDIA GM107 (117310a2)
[   10.695951] nouveau 0000:01:00.0: bios: version 82.07.a9.00.0c
[   10.849391] nouveau 0000:01:00.0: fb: 4096 MiB GDDR5
[   10.849404] nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 022554 [ IBUS ]
[   10.851426] nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 10ac08 [ IBUS ]
[   11.937159] nouveau 0000:01:00.0: DRM: VRAM: 4096 MiB
[   11.937160] nouveau 0000:01:00.0: DRM: GART: 1048576 MiB
[   11.937163] nouveau 0000:01:00.0: DRM: TMDS table version 2.0
[   11.937164] nouveau 0000:01:00.0: DRM: DCB version 4.0
[   11.937165] nouveau 0000:01:00.0: DRM: DCB outp 01: 02811fa6 04420010
[   11.937167] nouveau 0000:01:00.0: DRM: DCB outp 02: 02011f62 04420010
[   11.937168] nouveau 0000:01:00.0: DRM: DCB outp 03: 08822fc6 04420010
[   11.937169] nouveau 0000:01:00.0: DRM: DCB outp 04: 08022f82 04420010
[   11.937170] nouveau 0000:01:00.0: DRM: DCB conn 01: 00010146
[   11.937171] nouveau 0000:01:00.0: DRM: DCB conn 02: 01000246
[   12.126552] nouveau 0000:01:00.0: DRM: MM: using COPY for buffer copies
[   12.233419] [drm] Initialized nouveau 1.3.1 20120801 for 0000:01:00.0 on minor 1

```

Should I open a new issue for this one?
Comment 9 Rhys Kidd 2018-01-29 12:30:27 UTC
(In reply to Bruno Pagani from comment #8)
> 
> Should I open a new issue for this one?

Yes please, where there appears a new register on differing hardware family.

It's an easy operation to merge bugs later on should they be due to the same underlying cause, but almost impossible to separate them out.
Comment 10 Bruno Pagani 2018-01-29 13:11:05 UTC
Done: https://bugs.freedesktop.org/show_bug.cgi?id=104835
Comment 11 Alex 2018-02-05 09:48:01 UTC
Hi folks,
I have the very similar issue about drm, bus read FAULT, etc. However, my problem is more severe than just red lines in dmesg.

I have ideapad 700 with HD Graphics 530 as the integrated and GeForce GTX 950M as the discrete card. I sit on gentoo with Linux-4.15.1.
The first point is that if I use nvidia drivers than my brightness buttons do not work (not visible for anything). Summing this up with the total no need of a powerful graphics I decided to go to the bumblebee just in case I will indeed need a better gpu in action. That is to fire up the discrete card on demand.

My problem is that upon starting some glx-aware program at the moment when bumblebee is trying to start a separate hidden X server with nouveau as the driver my primary X server restarts.
After this restart and in attempt to run some glx-aware program again I see X errors and nothing good. They boil down to the fact that drm cannot ecquire an access to card0 and card1 because of permission issues. Well, the primary X server now does not restart though.

I tried all what bumblebee guys suggest - no way. Also, everything is smooth with the nvidia driver in this config.

I think it is those red messages in dmesg are the primary indicator of my troubles.
Comment 12 Bruno Pagani 2018-02-05 15:13:08 UTC
@Alex You should not use Bumblebee with nouveau. Also your bug is similar to an old of mine: https://bugs.freedesktop.org/show_bug.cgi?id=98384. So part of your issue is that your system is likely not up-to-date.

But the correct solution is to not use nouveau with Bumblebee. And in any case, it has likely nothing to do with this issue. ;)
Comment 13 Alex 2018-02-05 15:41:42 UTC
@Bruno, thanks for the comment. I will check it out. Bumblebee: you see, I'm fine with intel, I do not need extreme speeds and I have 16GB in RAM ...
nvidia - I could manage to install it either globally or in bumblebee but it blocks the brightness control when used permanently - very weird, so only bumblebee would go.
Something went wrong with setting nouveau globally and I have given up. Will retry. But it will not suit me if the brightness keys are blocked ...
And yes, my system is nearly the tomorrow's version. It is up-to date. At least the kernel is the one released few days ago ...
Comment 14 Ilia Mirkin 2018-02-05 15:48:26 UTC
(In reply to Alex from comment #13)
> @Bruno, thanks for the comment. I will check it out. Bumblebee: you see, I'm
> fine with intel, I do not need extreme speeds and I have 16GB in RAM ...
> nvidia - I could manage to install it either globally or in bumblebee but it
> blocks the brightness control when used permanently - very weird, so only
> bumblebee would go.

With nouveau loaded (assuming things go properly), your GPU should suspend when not in use.
Comment 15 Bruno Pagani 2018-02-05 16:32:45 UTC
> Something when wrong with nouveau globaly

If you have a quite recent system, maybe you are affected by https://bugzilla.kernel.org/show_bug.cgi?id=156341.
Comment 16 Ladislav Michl 2018-02-25 21:06:24 UTC
Still exists in 4.16.0-rc2:
nouveau 0000:01:00.0: fb: 2048 MiB GDDR5
nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 022554 [ IBUS ]
nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 10ac08 [ IBUS ]
Machine is HP ZBook 17 G3, the rest (bootlogs, etc) can be found in BUG 100213 report.
Comment 17 Mikael T 2018-03-23 08:47:16 UTC
still there with 4.13.0-37 ubuntu on HP Spectre, Core i7 7500U, intel HD Graphics 620, GM108M (GeForce 940MX) :

nouveau 0000:01:00.0: NVIDIA GM108 (1180d0a2)        
nouveau 0000:01:00.0: bios: version 82.08.62.00.15   
nouveau 0000:01:00.0: fb: 2048 MiB GDDR5             
nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 612004 [ IBUS ]                                                                  
nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 10ac08 [ IBUS ]                                                                  
 nvme0n1: p1 p2 p3                                   
[drm] Memory usable by graphics device = 4096M
Comment 18 Bruno Pagani 2018-03-23 13:52:22 UTC
(In reply to Mikael T from comment #17)
> still there with 4.13.0-37 ubuntu on HP Spectre, Core i7 7500U, intel HD
> Graphics 620, GM108M (GeForce 940MX) :
> 
> nouveau 0000:01:00.0: NVIDIA GM108 (1180d0a2)
> nouveau 0000:01:00.0: bios: version 82.08.62.00.15
> nouveau 0000:01:00.0: fb: 2048 MiB GDDR5
> nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 612004 [ IBUS ]
> nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 10ac08 [ IBUS ]

Those are differents errors.
You should open a new bug report for the first one.
The second one is https://bugs.freedesktop.org/show_bug.cgi?id=104835.
Comment 19 boldingd 2018-10-29 07:22:15 UTC
I think I'm also seeing this with Fedora 29 Beta, I was also seeing errors with updated Fedora 28.

[    1.614055] nouveau: detected PR support, will not use DSM
[    1.614243] nouveau 0000:01:00.0: NVIDIA GM108 (118070a2)
[    1.629639] nouveau 0000:01:00.0: bios: version 82.08.3b.00.4b
[    1.714600] nouveau 0000:01:00.0: fb: 2048 MiB DDR3
[    1.714622] nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 6013d4 [ IBUS ]
[    1.729900] nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 10ac08 [ IBUS ]
[    2.372521] nouveau 0000:01:00.0: DRM: VRAM: 2048 MiB
[    2.372522] nouveau 0000:01:00.0: DRM: GART: 1048576 MiB
[    2.372526] nouveau 0000:01:00.0: DRM: Pointer to TMDS table invalid
[    2.372543] nouveau 0000:01:00.0: DRM: DCB version 4.0
[    2.373356] nouveau 0000:01:00.0: DRM: MM: using COPY for buffer copies
[    2.373363] [drm] Initialized nouveau 1.3.1 20120801 for 0000:01:00.0 on minor 1
[    8.044183] nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 619444 [ IBUS ]
[    9.126208] nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 619444 [ IBUS ]
[   93.901280] nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 6013d4 [ IBUS ]
[  101.777394] nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 6013d4 [ IBUS ]
[  112.733004] nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 6013d4 [ IBUS ]

I'm also on a laptop (Asus Zenbook UX303U) with hybrid graphics (Skylake GT2 [HD Graphics 520] (rev 07) / GM108M [GeForce 940M] (rev a2)).
Comment 20 Bruno Pagani 2018-10-29 12:16:51 UTC
(In reply to boldingd from comment #19)
> I think I'm also seeing this with Fedora 29 Beta, I was also seeing errors
> with updated Fedora 28.

No, yours are different issues.

> [    1.729900] nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at
> 10ac08 [ IBUS ]

This is https://bugs.freedesktop.org/show_bug.cgi?id=104835

> [    8.044183] nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at
> 619444 [ IBUS ]
> [    9.126208] nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at
> 619444 [ IBUS ]

I haven’t found any reference for this one. You might open a new bugreport for it.

> [    1.714622] nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at
> 6013d4 [ IBUS ]
> [   93.901280] nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at
> 6013d4 [ IBUS ]
> [  101.777394] nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at
> 6013d4 [ IBUS ]
> [  112.733004] nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at
> 6013d4 [ IBUS ]

This one also appears (and is briefly discussed) in https://bugs.freedesktop.org/show_bug.cgi?id=98386
Comment 21 Cameron 2018-12-05 15:09:31 UTC
From my dmesg.

[   12.189523] ax88179_178a 2-2:1.0 enp0s20f0u2: ax88179 - Link status is: 0
[   15.645518] ax88179_178a 2-2:1.0 enp0s20f0u2: ax88179 - Link status is: 1
[   29.886049] nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 6013d4 [ IBUS ]
[   57.810423] logitech-hidpp-device 0003:046D:4013.0009: HID++ 2.0 device connected.
[   60.146429] logitech-hidpp-device 0003:046D:4002.000A: HID++ 2.0 device connected.


I am also getting this error

kernel 4.19.5-1-default
openSUSE Tumbleweed
Comment 22 Bruno Pagani 2018-12-05 15:12:05 UTC
(In reply to Cameron from comment #21)
> From my dmesg.
> 
> [   12.189523] ax88179_178a 2-2:1.0 enp0s20f0u2: ax88179 - Link status is: 0
> [   15.645518] ax88179_178a 2-2:1.0 enp0s20f0u2: ax88179 - Link status is: 1
> [   29.886049] nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at
> 6013d4 [ IBUS ]
> [   57.810423] logitech-hidpp-device 0003:046D:4013.0009: HID++ 2.0 device
> connected.
> [   60.146429] logitech-hidpp-device 0003:046D:4002.000A: HID++ 2.0 device
> connected.
> 
> 
> I am also getting this error
> 
> kernel 4.19.5-1-default
> openSUSE Tumbleweed

No, as I said just above your post, this would be https://bugs.freedesktop.org/show_bug.cgi?id=98386

The hex value after “at” does matter. ;)
Comment 23 Cameron 2018-12-05 15:40:00 UTC
openSUSE Tumbleweed
Kernel 4.19.5-1-default

Getting these messages

Dec 05 07:35:28 flisk kernel: nouveau 0000:01:00.0: fb: 4096 MiB GDDR5
Dec 05 07:35:28 flisk kernel: nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 022554 [ IBUS ]
Dec 05 07:35:28 flisk kernel: fbcon: Taking over console
Dec 05 07:35:28 flisk kernel: nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 10ac08 [ IBUS ]
Dec 05 07:35:28 flisk kernel: usb 1-4: New USB device found, idVendor=8087, idProduct=0a2b, bcdDevice= 0.10
Dec 05 07:35:28 flisk kernel: usb 1-4: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Dec 05 07:35:28 flisk kernel: usb 3-1: New USB device found, idVendor=0424, idProduct=2137, bcdDevice=60.80
Dec 05 07:35:28 flisk kernel: usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Dec 05 07:35:28 flisk kernel: usb 3-1: Product: USB2137B
Dec 05 07:35:28 flisk kernel: usb 3-1: Manufacturer: SMSC
Dec 05 07:35:28 flisk kernel: hub 3-1:1.0: USB hub found
Dec 05 07:35:28 flisk kernel: hub 3-1:1.0: 7 ports detected
Dec 05 07:35:28 flisk kernel: vga_switcheroo: enabled
Dec 05 07:35:28 flisk kernel: [TTM] Zone  kernel: Available graphics memory: 16391158 kiB
Dec 05 07:35:28 flisk kernel: [TTM] Zone   dma32: Available graphics memory: 2097152 kiB
Dec 05 07:35:28 flisk kernel: [TTM] Initializing pool allocator
Dec 05 07:35:28 flisk kernel: [TTM] Initializing DMA pool allocator
Dec 05 07:35:28 flisk kernel: nouveau 0000:01:00.0: DRM: VRAM: 4096 MiB
Dec 05 07:35:28 flisk kernel: nouveau 0000:01:00.0: DRM: GART: 1048576 MiB
Dec 05 07:35:28 flisk kernel: nouveau 0000:01:00.0: DRM: Pointer to TMDS table invalid
Dec 05 07:35:28 flisk kernel: nouveau 0000:01:00.0: DRM: DCB version 4.0
Dec 05 07:35:28 flisk kernel: nouveau 0000:01:00.0: DRM: MM: using COPY for buffer copies
Dec 05 07:35:28 flisk kernel: [drm] Initialized nouveau 1.3.1 20120801 for 0000:01:00.0 on minor 1
Comment 24 joel.busch 2018-12-07 11:26:38 UTC
I'm getting one of these too on Fedora 28 KDE Plasma spin.

Acer Aspire VN7-592G/Aspire VN7-592G, BIOS V1.13 03/21/2018
Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
NVIDIA Corporation GM107M [GeForce GTX 960M] (rev a2)

$ cat /proc/version
Linux version 4.19.6-200.fc28.x86_64 (mockbuild@bkernel04.phx2.fedoraproject.org) (gcc version 8.2.1 20181105 (Red Hat 8.2.1-5) (GCC)) #1 SMP Sun Dec 2 18:03:32 UTC 2018

$ journalctl -b --no-hostname -o short-monotonic | grep nouveau
[    2.515464] kernel: nouveau: detected PR support, will not use DSM
[    2.515480] kernel: nouveau 0000:01:00.0: enabling device (0006 -> 0007)
[    2.515620] kernel: nouveau 0000:01:00.0: NVIDIA GM107 (1171b0a2)
[    2.537544] kernel: nouveau 0000:01:00.0: bios: version 82.07.80.00.2a
[    2.586306] kernel: nouveau 0000:01:00.0: fb: 2048 MiB GDDR5
[    2.586357] kernel: nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 022554 [ IBUS ]
[    2.599343] kernel: nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 10ac08 [ IBUS ]
[    3.260508] kernel: nouveau 0000:01:00.0: DRM: VRAM: 2048 MiB
[    3.260509] kernel: nouveau 0000:01:00.0: DRM: GART: 1048576 MiB
[    3.260511] kernel: nouveau 0000:01:00.0: DRM: Pointer to TMDS table invalid
[    3.260512] kernel: nouveau 0000:01:00.0: DRM: DCB version 4.0
[    3.261005] kernel: nouveau 0000:01:00.0: DRM: MM: using COPY for buffer copies
[    3.261011] kernel: [drm] Initialized nouveau 1.3.1 20120801 for 0000:01:00.0 on minor 1
[    7.846986] kernel: nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 619444 [ IBUS ]
Comment 25 Johnny B. Goode 2018-12-08 16:27:22 UTC
(In reply to Bruno Pagani from comment #4)
> @gene, Johnny B. Goode: From what I know, the “at” value matters, because
> they have meanings. Though from one generation to another this could be
> different values for the same register.
> 
> Also, @Johnny, in your case it’s a write instead of a read, so I would
> definitively open another issue.

In the end I opened 2 new issues with MMIO FAULT
#108980
#108982
Bug, in different variations, started in kernel 4.10 still exist. There is a thousands searchings for this bug in google.
Comment 26 Jan 2018-12-29 18:43:05 UTC
I have a similar issue with my NP900X5N laptop with Kaby Lake and 940MX card, on 4.20.0 and Kali Linux.

My output:
root@kali:/etc/modprobe.d# dmesg | grep nouveau  
[   35.888423] nouveau: detected PR support, will not use DSM
[   35.888447] nouveau 0000:01:00.0: enabling device (0006 -> 0007)
[   35.888582] nouveau 0000:01:00.0: NVIDIA GM108 (1180d0a2)
[   35.900141] nouveau 0000:01:00.0: bios: version 82.08.67.00.04
[   35.984081] nouveau 0000:01:00.0: fb: 2048 MiB DDR3
[   35.984104] nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 6013d4 [ IBUS ]
[   35.997510] nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 10ac08 [ IBUS ]
[   36.035684] nouveau 0000:01:00.0: DRM: VRAM: 2048 MiB
[   36.035686] nouveau 0000:01:00.0: DRM: GART: 1048576 MiB
[   36.035688] nouveau 0000:01:00.0: DRM: Pointer to TMDS table invalid
[   36.035690] nouveau 0000:01:00.0: DRM: DCB version 4.0
[   36.036798] nouveau 0000:01:00.0: DRM: MM: using COPY for buffer copies
[   36.036915] [drm] Initialized nouveau 1.3.1 20120801 for 0000:01:00.0 on minor 1
[   37.551790] nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 619444 [ IBUS ]
Comment 27 Bruno Pagani 2019-01-01 13:20:23 UTC
(In reply to Jan from comment #26)
> I have a similar issue with my NP900X5N laptop with Kaby Lake and 940MX
> card, on 4.20.0 and Kali Linux.
> 
> [   35.984104] nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 6013d4 [ IBUS ]

This is included in https://bugs.freedesktop.org/show_bug.cgi?id=98386. And apparently also https://bugs.freedesktop.org/show_bug.cgi?id=108980, which seems recently fixed.

> [   35.997510] nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 10ac08 [ IBUS ]

This one is https://bugs.freedesktop.org/show_bug.cgi?id=104835.

> [   37.551790] nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at
> 619444 [ IBUS ]

This is like https://bugs.freedesktop.org/show_bug.cgi?id=100423#c19, not sure if there is already an issue for it.
Comment 28 Jan 2019-01-01 22:01:08 UTC
Tonight I tried to see what happens if I generate a xorg.conf file and place it in /etc/X11/xorg.conf, as described here:
https://askubuntu.com/questions/4662/where-is-the-x-org-config-file-how-do-i-configure-x-there

When I do that X starts without the error cannot find framebuffer device. It starts with a backtrace list and then stops with:

'Segmentation fault at address 0x0.

Fatal sever error etc etc etc.

Hope this helps!
Comment 29 Pierre-Charles David 2019-04-29 14:58:00 UTC
FWIW, I also get this one (022554), along with two others (10ac08 and 6013d4).

The machine is an ASUS UX501V with an Intel HD Graphics 530 + NVIDIA GTX 960M (more details below). I'm running an up to date Debian 9.9 with a 4.19.28-2~bpo9+1 kernel (from stretch-backports). It is usually plugged to an external screen though HDMI (32" AOC Q3277PQU at 2560×1440).

% cat /proc/version
Linux version 4.19.0-0.bpo.4-amd64 (debian-kernel@lists.debian.org) (gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1)) #1 SMP Debian 4.19.28-2~bpo9+1 (2019-03-27)

% lspci
00:00.0 Host bridge: Intel Corporation Skylake Host Bridge/DRAM Registers (rev 07)
00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 07)
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06)
00:04.0 Signal processing controller: Intel Corporation Skylake Processor Thermal Subsystem (rev 07)
00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller (rev 31)
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H Thermal subsystem (rev 31)
00:15.0 Signal processing controller: Intel Corporation Sunrise Point-H Serial IO I2C Controller #0 (rev 31)
00:15.1 Signal processing controller: Intel Corporation Sunrise Point-H Serial IO I2C Controller #1 (rev 31)
00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI #1 (rev 31)
00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA Controller [AHCI mode] (rev 31)
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #2 (rev f1)
00:1c.2 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #3 (rev f1)
00:1c.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #5 (rev f1)
00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31)
00:1f.3 Audio device: Intel Corporation Sunrise Point-H HD Audio (rev 31)
00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31)
01:00.0 3D controller: NVIDIA Corporation GM107M [GeForce GTX 960M] (rev a2)
02:00.0 Unassigned class [ff00]: Alcor Micro Device 6621
03:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)

Details on the NVIDIA card:

01:00.0 3D controller: NVIDIA Corporation GM107M [GeForce GTX 960M] (rev a2)
	Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 127
	Region 0: Memory at dc000000 (32-bit, non-prefetchable) [size=16M]
	Region 1: Memory at b0000000 (64-bit, prefetchable) [size=256M]
	Region 3: Memory at c0000000 (64-bit, prefetchable) [size=32M]
	Region 5: I/O ports at e000 [size=128]
	Expansion ROM at dd000000 [disabled] [size=512K]
	Capabilities: <access denied>
	Kernel driver in use: nouveau
	Kernel modules: nouveau, nvidia_current_drm, nvidia_current


% journalctl -b --no-hostname -o short-monotonic | grep nouveau
[   25.822549] kernel: nouveau: detected PR support, will not use DSM
[   25.822749] kernel: nouveau 0000:01:00.0: NVIDIA GM107 (1171b0a2)
[   25.889243] kernel: nouveau 0000:01:00.0: bios: version 82.07.94.00.1a
[   26.462330] kernel: nouveau 0000:01:00.0: fb: 2048 MiB GDDR5
[   26.462343] kernel: nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 022554 [ IBUS ]
[   26.474851] kernel: nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 10ac08 [ IBUS ]
[   27.774265] kernel: nouveau 0000:01:00.0: DRM: VRAM: 2048 MiB
[   27.774266] kernel: nouveau 0000:01:00.0: DRM: GART: 1048576 MiB
[   27.774269] kernel: nouveau 0000:01:00.0: DRM: Pointer to TMDS table invalid
[   27.774271] kernel: nouveau 0000:01:00.0: DRM: DCB version 4.0
[   27.774883] kernel: nouveau 0000:01:00.0: DRM: MM: using COPY for buffer copies
[   27.774892] kernel: [drm] Initialized nouveau 1.3.1 20120801 for 0000:01:00.0 on minor 1
                       NVRM: nouveau, rivafb, nvidiafb or rivatv 
                       NVRM: nouveau, rivafb, nvidiafb or rivatv 
[   76.402068] kernel: nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 6013d4 [ IBUS ]
[   76.984544] /usr/lib/gdm3/gdm-x-session[1519]: (II) modeset(G0): [DRI2]   DRI driver: nouveau
[   76.984544] /usr/lib/gdm3/gdm-x-session[1519]: (II) modeset(G0): [DRI2]   VDPAU driver: nouveau
[   83.346751] kernel: nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 6013d4 [ IBUS ]

The last line is repeated hundreds of times.

It may be related, but am not sure: right after a boot, the graphics (e.g. GNOME Shell animations) are fast and smooth, but after a while (I think it's related to the machine going to sleep, and/or the screen being locked), it seems to go to a fallback non-accelerated mode. It's still usable, but even moving a simple terminal window is slow. Strangely, even in this degraded mode, scrolling full-screen pages is still smooth in Firefox, as is e.g. watching videos.
Comment 30 michal.dybczak 2019-09-08 08:46:24 UTC
This is concerning that after all this time (2,5 year) this issue is still here.

I have the same issue shown in journalctl. I believe it wasn't there from the start but showed a while ago. I don't see any problems on the frontend site, however.
I have a hybrid GPUs and currently use optimus-manager to switch between GPUs. Nouevau is making the switch (successfully).

Here is the bug:

nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 022554 [ IBUS ]

My laptop is:

System:    Host: alienware-PC Kernel: 5.2.13-1-MANJARO x86_64 bits: 64 compiler: gcc v: 9.1.0 Desktop: KDE Plasma 5.16.5 
           tk: Qt 5.13.0 wm: kwin_x11 dm: SDDM Distro: Manjaro Linux 
Machine:   Type: Laptop System: Alienware product: Alienware 17 R3 v: 1.7.0 serial: <filter> Chassis: type: 10 
           serial: <filter> 
           Mobo: Alienware model: 0GH72M v: A00 serial: <filter> UEFI: Alienware v: 1.7.0 date: 01/18/2019 
Battery:   ID-1: BAT1 charge: 95.8 Wh condition: 95.8/96.0 Wh (100%) volts: 17.3/15.0 model: COMPAL PABAS0241231 
           serial: <filter> status: Full 
CPU:       Topology: Quad Core model: Intel Core i7-6700HQ bits: 64 type: MT MCP arch: Skylake-S rev: 3 L2 cache: 6144 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 41488 
           Speed: 933 MHz min/max: 800/3500 MHz Core speeds (MHz): 1: 900 2: 900 3: 900 4: 900 5: 900 6: 900 7: 900 8: 900 
Graphics:  Device-1: Intel HD Graphics 530 vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:191b 
           Device-2: NVIDIA GM204M [GeForce GTX 970M] vendor: Dell driver: nouveau v: kernel bus ID: 01:00.0 
           chip ID: 10de:13d8 
           Display: x11 server: X.Org 1.20.5 driver: modesetting compositor: kwin_x11 tty: N/A 
           OpenGL: renderer: Mesa DRI Intel HD Graphics 530 (Skylake GT2) v: 4.5 Mesa 19.1.6 compat-v: 3.0 direct render: Yes 
Audio:     Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: Dell driver: snd_hda_intel v: kernel bus ID: 00:1f.3 
           chip ID: 8086:a170 
           Sound Server: ALSA v: k5.2.13-1-MANJARO 
Network:   Device-1: Qualcomm Atheros Killer E2400 Gigabit Ethernet driver: alx v: kernel port: d000 bus ID: 3b:00.0 
           chip ID: 1969:e0a1 
           IF: enp59s0 state: down mac: <filter> 
           Device-2: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter vendor: Bigfoot Networks driver: ath10k_pci 
           v: kernel port: d000 bus ID: 3c:00.0 chip ID: 168c:003e 
           IF: wlp60s0 state: up mac: <filter> 
           Device-3: Qualcomm Atheros type: USB driver: btusb bus ID: 1-5:4 chip ID: 0cf3:e300 
Drives:    Local Storage: total: 1.02 TiB used: 730.08 GiB (70.0%) 
           ID-1: /dev/sda vendor: Kingston model: SM2280S3G2120G size: 111.79 GiB speed: 6.0 Gb/s serial: <filter> 
           ID-2: /dev/sdb vendor: HGST (Hitachi) model: HTS721010A9E630 size: 931.51 GiB speed: 6.0 Gb/s serial: <filter> 
RAID:      Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci v: 3.0 bus ID: 00:17.0 chip ID: 8086.282a 
Partition: ID-1: / size: 38.32 GiB used: 30.85 GiB (80.5%) fs: ext4 dev: /dev/sda4 
           ID-2: /home size: 71.26 GiB used: 57.85 GiB (81.2%) fs: ext4 dev: /dev/sda2 
Sensors:   System Temperatures: cpu: 54.5 C mobo: N/A gpu: nouveau temp: 54 C 
           Fan Speeds (RPM): N/A 
Info:      Processes: 262 Uptime: 5m Memory: 7.66 GiB used: 2.53 GiB (33.0%) Init: systemd v: 243 Compilers: gcc: 9.1.0 
           clang: 8.0.1 Shell: bash v: 5.0.11 running in: konsole inxi: 3.0.36
Comment 31 Martin Peres 2019-12-04 09:25:51 UTC
-- 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/335.

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.