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 108980] GF117: MMIO write of 0000001f FAULT at 6013d4 [ IBUS ]
Date: Sun, 09 Dec 2018 04:59:24 +0000	[thread overview]
Message-ID: <bug-108980-8800-DWvMqb2Mnd@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-108980-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


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

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

--- Comment #5 from Ilia Mirkin <imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org> ---
This is quite confusing. It would appear it's happening in volt's oneinit
function:

[   17.475047] kernel: nouveau 0000:08:00.0: volt: init running...
[   17.475749] kernel: nouveau 0000:08:00.0: volt: one-time init running...
[   17.476499] kernel: nouveau 0000:08:00.0: volt: couldn't find speedo value,
volting not possible
[   17.476513] kernel: nouveau 0000:08:00.0: bus: MMIO write of ffff881f FAULT
at 6013d4 [ IBUS ]
[   17.477150] kernel: nouveau 0000:08:00.0: volt: one-time init completed in
668us
[   17.478504] kernel: nouveau 0000:08:00.0: volt: current voltage unknown
[   17.479174] kernel: nouveau 0000:08:00.0: volt: init completed in 3426us

However nothing in there could cause that... of course the notification only
comes in later (via interrupt servicing), so it may not be directly correlated
to these messages.

Auditing the other common suspects, nothing in the bios will try to use any of
the IO/etc commands which generally trigger these.

AHA! I have a theory.

devinit's preinit calls nvkm_lockvgac(). Can you try commenting that out?

drivers/gpu/drm/nouveau/nvkm/subdev/devinit/base.c:nvkm_devinit_preinit -- just
comment out the call to "nvkm_lockvgac".

If that doesn't help, then I'm out of ideas, and we have to take more of a
shotgun approach -- add a

WARN() at the top of drivers/gpu/drm/nouveau/nvkm/engine/disp/vga.c:nvkm_wrport
and rdport, and see who's calling them. No one should be on a GF117, I believe.

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

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

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

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

  parent reply	other threads:[~2018-12-09  4:59 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-08 14:49 [Bug 108980] New: GF117: MMIO write of 0000001f FAULT at 6013d4 [ IBUS ] bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-108980-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2018-12-08 17:07   ` [Bug 108980] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-12-08 18:19   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-12-09  4:02   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-12-09  4:04   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-12-09  4:59   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2018-12-09  9:19   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-12-09 15:35   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-12-09 17:03   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-12-12  2:43   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-12-12 18:12   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-12-13  4:08   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-12-13  4:55   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-12-13 18:09   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-12-13 18:14   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-12-13 18:19   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-04-21  6:00   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-09-03 16:20   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  9:47   ` 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-108980-8800-DWvMqb2Mnd@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