Nouveau Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 98386] New: [NVE7] bus: MMIO write of FAULT at [ IBUS ], Pointer to {TDMS, flat panel) table invalid
Date: Sat, 22 Oct 2016 16:32:51 +0000	[thread overview]
Message-ID: <bug-98386-8800@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 4509 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=98386

            Bug ID: 98386
           Summary: [NVE7] bus: MMIO write of FAULT at [ IBUS ], Pointer
                    to {TDMS,flat panel) table invalid
           Product: xorg
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: minor
          Priority: medium
         Component: Driver/nouveau
          Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
          Reporter: bruno.pagani-vYW+cPY1g1pg9hUCZPvPmw@public.gmane.org
        QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org

Hi, following https://bugzilla.freedesktop.org/show_bug.cgi?id=70354, I’m still
having some error messages in dmesg.

This is on first loading:
[  454.756165] MXM: GUID detected in BIOS
[  454.756253] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type
mismatch - Found [Buffer], ACPI requires [Package] (20160422/nsarguments-95)
[  454.756309] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type
mismatch - Found [Buffer], ACPI requires [Package] (20160422/nsarguments-95)
[  454.756430] pci 0000:02:00.0: optimus capabilities: enabled, status dynamic
power, hda bios codec supported
[  454.756432] VGA switcheroo: detected Optimus DSM method \_SB_.PCI0.PEG0.PEGP
handle
[  454.756433] nouveau: detected PR support, will not use DSM
[  454.756510] nouveau 0000:02:00.0: NVIDIA GK107 (0e7240a2)
[  454.775702] nouveau 0000:02:00.0: bios: version 80.07.b3.00.21
[  454.919182] nouveau 0000:02:00.0: fb: 2048 MiB GDDR5
[  454.919271] nouveau 0000:02:00.0: bus: MMIO write of 00000002 FAULT at
4188ac [ IBUS ]
[  454.989821] vga_switcheroo: enabled
[  454.989938] [TTM] Zone  kernel: Available graphics memory: 8169036 kiB
[  454.989939] [TTM] Zone   dma32: Available graphics memory: 2097152 kiB
[  454.989940] [TTM] Initializing pool allocator
[  454.989943] [TTM] Initializing DMA pool allocator
[  454.989951] nouveau 0000:02:00.0: DRM: VRAM: 2048 MiB
[  454.989951] nouveau 0000:02:00.0: DRM: GART: 1048576 MiB
[  454.989954] nouveau 0000:02:00.0: DRM: Pointer to TMDS table invalid
[  454.989956] nouveau 0000:02:00.0: DRM: DCB version 4.0
[  454.989957] nouveau 0000:02:00.0: DRM: Pointer to flat panel table invalid
[  455.191639] nouveau 0000:02:00.0: DRM: MM: using COPY for buffer copies
[  455.191647] [drm] Initialized nouveau 1.3.1 20120801 for 0000:02:00.0 on
minor 1
[  460.192102] nouveau 0000:02:00.0: DRM: evicting buffers...
[  460.192107] nouveau 0000:02:00.0: DRM: waiting for kernel channels to go
idle...
[  460.192139] nouveau 0000:02:00.0: DRM: suspending client object trees...
[  460.198135] nouveau 0000:02:00.0: DRM: suspending kernel object tree...

Note the following lines (that appear in red in my console):
[  454.919271] nouveau 0000:02:00.0: bus: MMIO write of 00000002 FAULT at
4188ac [ IBUS ]
[  454.989954] nouveau 0000:02:00.0: DRM: Pointer to TMDS table invalid
[  454.989957] nouveau 0000:02:00.0: DRM: Pointer to flat panel table invalid

And then, on subsequent uses of the card:
[  470.170765] nouveau 0000:02:00.0: DRM: resuming kernel object tree...
[  470.245180] nouveau 0000:02:00.0: bus: MMIO write of ffffff1f FAULT at
6013d4 [ IBUS ]
[  470.266559] nouveau 0000:02:00.0: DRM: resuming client object trees...
[  476.071701] nouveau 0000:02:00.0: DRM: evicting buffers...
[  476.071703] nouveau 0000:02:00.0: DRM: waiting for kernel channels to go
idle...
[  476.071732] nouveau 0000:02:00.0: DRM: suspending client object trees...
[  476.077132] nouveau 0000:02:00.0: DRM: suspending kernel object tree...

And again (can provide any amount you want, only the two hex chains change):
[ 6579.503383] nouveau 0000:02:00.0: DRM: resuming kernel object tree...
[ 6579.586496] nouveau 0000:02:00.0: bus: MMIO write of 8000001f FAULT at
6013d4 [ IBUS ]
[ 6579.607798] nouveau 0000:02:00.0: DRM: resuming client object trees...
[ 6585.210796] nouveau 0000:02:00.0: DRM: evicting buffers...
[ 6585.210798] nouveau 0000:02:00.0: DRM: waiting for kernel channels to go
idle...
[ 6585.210825] nouveau 0000:02:00.0: DRM: suspending client object trees...
[ 6585.216211] nouveau 0000:02:00.0: DRM: suspending kernel object tree...

Not sure if it has any consequences, but since it appears in red, I supposed it
was worth reporting.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 5886 bytes --]

[-- Attachment #2: Type: text/plain, Size: 154 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau

             reply	other threads:[~2016-10-22 16:32 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-22 16:32 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-98386-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2016-10-22 16:42   ` [Bug 98386] [NVE7] bus: MMIO write of FAULT at [ IBUS ], Pointer to {TDMS, flat panel) table invalid bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-10-22 16:53   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-10-22 16:54   ` [Bug 98386] [NVE7] bus: MMIO write of FAULT at [ IBUS ], Pointer to {TDMS, flat panel} " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-10-22 18:27   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-27 17:19   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-27 17:21   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-27 17:25   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-27 17:27   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-27 17:45   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-27 18:24   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-27 20:36   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-27 20:39   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-27 20:44   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-27 20:48   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-27 20:54   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-27 23:12   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-28 15:46   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-28 21:28   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-05-10 23:12   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-03-09 18:51   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-05-01 19:51   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-05-01 20:16   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-11-21 18:20   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-12-05 15:21   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-12-05 15:35   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-04  9:36   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-02-08  1:53   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-07-31  5:49   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  9:18   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-98386-8800@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox