All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 76475] [NVE7] fails to load due to unknown opcode 0x80 (incorrect vbios)
Date: Sun, 23 Mar 2014 17:52:02 +0000	[thread overview]
Message-ID: <bug-76475-8800-i8APZkue9N@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-76475-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


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

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

--- Comment #8 from Ilia Mirkin <imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org> ---
OK, as best I can tell from the mmiotrace, it's using the ACPI method[1].
Further, your acpi dump indeed contains a _DSM method, as well as a _ROM
method, which should be used to get at the ROM. Unfortunately, it would appear
that evaluating _DSM fails for you:

[    2.920235] ACPI Warning: \_SB_.PCI0.PEG0.GFX0._DSM: Argument #4 type
mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
[    2.920300] ACPI: \_SB_.PCI0.PEG0.GFX0: failed to evaluate _DSM

Why it's failing to evaluate the DSM is, unfortunately, beyond my knowledge of
how these things work. The failure did not seem present in earlier versions (at
least not as vocally), although it still didn't find the ACPI ROM back then
either. I don't know if that acpi warning is what actually cause it, or if
there's something else.

At the top of nouveau_acpi.c:nouveau_acpi_rom_supported, there's a check for
dsm_detected or optimus_detected. Try removing that check entirely and let it
just try to grab the ROM from ACPI no matter what. I think that dsm_detected
might not be getting set even if the earlier _DSM call had succeeded.

[1] Here is what I'm seeing. The other things are identifiable as the PRAMIN
and PROM methods. I'm assuming that the maps of random-seeming memory are
actually it reading out the ACPI rom.

[0] 1248.299066 MMIO32 R 0x619f04 0x007ffe09 PDISPLAY.VGA.ROM_WINDOW => { BASE
= 0x7ffe0000 | ENABLE | TARGET = VRAM }
[0] 1248.299087 MMIO32 R 0x022438 0x00000002 PUNITS.DESIGN_PART_COUNT => 0x2
[0] 1248.299105 MMIO32 R 0x022554 0x00000000 PUNITS.HW_MC_DISABLE_MASK => 0
[0] 1248.299123 MMIO32 R 0x100800 0x00000002 PFFB.PART_CONFIG => { PART_COUNT =
0x2 | MEM_SPLIT_PART = 0 }
[0] 1248.299139 MMIO32 R 0x11020c 0x00000400 PBFB[0].MEM_AMOUNT => 0x40000000
[0] 1248.299158 MMIO32 R 0x11120c 0x00000400 PBFB[0x1].MEM_AMOUNT => 0x40000000
[0] 1248.299177 MMIO32 R 0x001700 0x00007ff0 PBUS.HOST_MEM.PMEM => { OFFSET =
0x7ff00000 | TARGET = VRAM }
[0] 1248.299188, MEM8 7ffe0000 => ef
[0] 1248.299197, MEM8 7ffe0001 => be
SLEEP 0.212000ms
[0] 1248.299409 MMIO32 R 0x619f04 0x007ffe09 PDISPLAY.VGA.ROM_WINDOW => { BASE
= 0x7ffe0000 | ENABLE | TARGET = VRAM }
[0] 1248.299423, MEM16 7ffe0000 => beef
[0] 1248.299442 MMIO32 R 0x101000 0x9f408480 PSTRAPS.STRAPS0_PRIMARY => { VALUE
= { RAMCFG = 0 | CRYSTAL = 0 | DEVICE_ID_0_3 = 0x1 | BAR1_SIZE = 25
6MB | ROM_TYPE = SPI | FP_CONFIG = 0xf | DEVICE_ID_4 = 0x1 | DEVICE_ID_5 = 0 |
0x80 } | OVERRIDE_ENABLE }
[0] 1248.299483 MMIO32 R 0x088050 0x00000001 PPCI.ROM_SHADOW_ENABLE => 0x1
[0] 1248.299505 MMIO32 W 0x088050 0x00000000 PPCI.ROM_SHADOW_ENABLE <= 0
[0] 1248.299524 MMIO32 R 0x088050 0x00000000 PPCI.ROM_SHADOW_ENABLE => 0
[0] 1248.299540 MMIO32 R 0x300000 0x00000000 PROM[0] => 0
                                             PROM[0x1] => 0
                                             PROM[0x2] => 0
                                             PROM[0x3] => 0
[0] 1248.299557 MMIO32 W 0x088050 0x00000001 PPCI.ROM_SHADOW_ENABLE <= 0x1
MAP 1248.299831 6 0xde759000 0xffffc900040ba000 0x1000 0x0 0
SLEEP 0.304000ms
UNMAP 1248.309290 6 0x0 0
MAP 1248.309326 7 0xde75a000 0xffffc900040bc000 0x1000 0x0 0
SLEEP 4.378000ms
UNMAP 1248.309595 7 0x0 0
MAP 1248.309828 8 0xde75a000 0xffffc900040be000 0x1000 0x0 0
SLEEP 0.472000ms
UNMAP 1248.317354 8 0x0 0
MAP 1248.317361 9 0xde75b000 0xffffc900040fa000 0x1000 0x0 0
SLEEP 2.454000ms
UNMAP 1248.317627 9 0x0 0

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

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

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

_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau

  parent reply	other threads:[~2014-03-23 17:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-22  9:19 [Bug 76475] New: Nouveau fails to load due to unknown opcode 0x80 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-76475-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2014-03-22  9:20   ` [Bug 76475] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-22  9:20   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-22 13:23   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-22 13:29   ` [Bug 76475] [NVE7] fails to load due to unknown opcode 0x80 (incorrect vbios) bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-22 19:10   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-22 19:10   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-22 19:12   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-22 21:40   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-23 17:52   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2014-03-26 22:50   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-26 23:06   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-27 11:07   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-27 11:08   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-27 11:19   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-28  3:25   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-28 11:25   ` 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-76475-8800-i8APZkue9N@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.