From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org Subject: [Bug 98386] [NVE7] bus: MMIO write of FAULT at [ IBUS ], Pointer to {TDMS, flat panel) table invalid Date: Sat, 22 Oct 2016 16:53:37 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0207200917==" Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: nouveau-bounces-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org Sender: "Nouveau" To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org List-Id: nouveau.vger.kernel.org --===============0207200917== Content-Type: multipart/alternative; boundary="14771552161.3F515d3d.3277"; charset="UTF-8" --14771552161.3F515d3d.3277 Date: Sat, 22 Oct 2016 16:53:36 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D98386 --- Comment #2 from bruno.pagani-vYW+cPY1g1pg9hUCZPvPmw@public.gmane.org --- (In reply to Ilia Mirkin from comment #1) > (In reply to bruno.pagani from comment #0) > > [ 454.919271] nouveau 0000:02:00.0: bus: MMIO write of 00000002 FAULT = at > > 4188ac [ IBUS ] >=20 > That's bad. >=20 > 4188ac =3D PGRAPH.GPC_BROADCAST.FFB.PART_CONFIG >=20 > I believe we do this here: >=20 > drm/nouveau/nvkm/engine/gr/gk104.c: nvkm_wr32(device, GPC_BCAST(0x08a= c), > nvkm_rd32(device, 0x100800)); >=20 > > [ 470.245180] nouveau 0000:02:00.0: bus: MMIO write of ffffff1f FAULT = at > > 6013d4 [ IBUS ] >=20 > That's bad too. This is related to the legacy 0x3d4 VGA IO port (which st= ill > has to be used for various display-related things). Unless you've skimped= on > the dmesg, you don't have any DCB entries and it may be reasonable to > believe you don't have a display block at all. (I assume there are no > outputs wired up to the NVIDIA GPU?) In that case, we should probably tra= ck > down where we're trying to do this from and skip it. Based on the location > in the logs, probably something VBIOS- or other early-init-related. >=20 > Unfortunately I don't have any actual debugging steps for you. Perhaps Ben > will. Indeed, this is an Optimus laptop with no output wired to the NVIDIA GPU. Also, now that you mention it, the second hex chain is indeed always 6013d4= on following attempts (only the first hex chain changes). Will wait for Ben requests of information/debug trial then.=E2=80=AF;) --=20 You are receiving this mail because: You are the assignee for the bug.= --14771552161.3F515d3d.3277 Date: Sat, 22 Oct 2016 16:53:36 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Comment= # 2 on bug 98386<= /a> from brun= o.pagani@ens-lyon.org 
(In reply to Ilia Mirkin from comment #1)
> (In reply to bruno.pagani from comment #0)
> > [  454.919271] nouveau 0000:02:00.0: bus: MMIO write of 00000002 =
FAULT at
> > 4188ac [ IBUS ]
>=20
> That's bad.
>=20
> 4188ac =3D PGRAPH.GPC_BROADCAST.FFB.PART_CONFIG
>=20
> I believe we do this here:
>=20
> drm/nouveau/nvkm/engine/gr/gk104.c:     nvkm_wr32(device, GPC_BCAST(0x=
08ac),
> nvkm_rd32(device, 0x100800));
>=20
> > [  470.245180] nouveau 0000:02:00.0: bus: MMIO write of ffffff1f =
FAULT at
> > 6013d4 [ IBUS ]
>=20
> That's bad too. This is related to the legacy 0x3d4 VGA IO port (which=
 still
> has to be used for various display-related things). Unless you've skim=
ped on
> the dmesg, you don't have any DCB entries and it may be reasonable to
> believe you don't have a display block at all. (I assume there are no
> outputs wired up to the NVIDIA GPU?) In that case, we should probably =
track
> down where we're trying to do this from and skip it. Based on the loca=
tion
> in the logs, probably something VBIOS- or other early-init-related.
>=20
> Unfortunately I don't have any actual debugging steps for you. Perhaps=
 Ben
> will.

Indeed, this is an Optimus laptop with no output wired to the NVIDIA GPU.

Also, now that you mention it, the second hex chain is indeed always 6013d4=
 on
following attempts (only the first hex chain changes).

Will wait for Ben requests of information/debug trial then.=E2=80=AF;)

You are receiving this mail because:
  • You are the assignee for the bug.
= --14771552161.3F515d3d.3277-- --===============0207200917== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KTm91dmVhdSBt YWlsaW5nIGxpc3QKTm91dmVhdUBsaXN0cy5mcmVlZGVza3RvcC5vcmcKaHR0cHM6Ly9saXN0cy5m cmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9ub3V2ZWF1Cg== --===============0207200917==--