From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paul Kocialkowski Subject: Re: regression? no hdmi output on tegra124 (kernel 4.12) Date: Sun, 09 Jul 2017 19:26:51 +0300 Message-ID: <1499617611.1355.3.camel@paulk.fr> References: <97b04d3a-a969-a23b-9414-4937dd2f2ef6@nvidia.com> <1499615706.1355.1.camel@paulk.fr> Mime-Version: 1.0 Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="=-qc3V0W0AWYOD8fSnsIqv" Return-path: In-Reply-To: <1499615706.1355.1.camel-W9ppeneeCTY@public.gmane.org> Sender: linux-tegra-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Jon Hunter , Anthony Eden , linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Thierry Reding , Mikko Perttunen List-Id: linux-tegra@vger.kernel.org --=-qc3V0W0AWYOD8fSnsIqv Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Le dimanche 09 juillet 2017 =C3=A0 18:55 +0300, Paul Kocialkowski a =C3=A9c= rit : > Le vendredi 07 juillet 2017 =C3=A0 14:28 +0100, Jon Hunter a =C3=A9crit : > > On 05/07/17 21:31, Anthony Eden wrote: > > > I no longer have any HDMI output from either my Jetson TK1 > > > (tegra124-jetson-tk1) or Acer Chromebook 13 CB5-311 > > > (tegra124-nyan-big) in Linux 4.12. In 4.11 I had no problem > > > starting > > > up X server. > > >=20 > > > Lightdm tries to start on boot and /var/log/Xorg.0.log contains: > > >=20 > > > ... > > >=20 > > > [ 10.723] (II) modesetting: Driver for Modesetting Kernel > > > Drivers: kms > > > [ 10.723] (II) modeset(0): using drv /dev/dri/card0 > > > [ 10.724] (II) modeset(0): Creating default Display subsection > > > in > > > Screen section > > > "Default Screen Section" for depth/fbbpp 24/32 > > > [ 10.724] (=3D=3D) modeset(0): Depth 24, (=3D=3D) framebuffer bpp = 32 > > > [ 10.724] (=3D=3D) modeset(0): RGB weight 888 > > > [ 10.724] (=3D=3D) modeset(0): Default visual is TrueColor > > > [ 10.724] (II) Loading sub module "glamoregl" > > > [ 10.724] (II) LoadModule: "glamoregl" > > > [ 10.724] (II) Loading /usr/lib/xorg/modules/libglamoregl.so > > > [ 10.726] (II) Module glamoregl: vendor=3D"X.Org Foundation" > > > [ 10.726] compiled for 1.19.3, module version =3D 1.0.0 > > > [ 10.726] ABI class: X.Org ANSI C Emulation, version 0.4 > > > [ 10.726] (II) glamor: OpenGL accelerated X.org driver based. > > > [ 10.920] (II) glamor: EGL version 1.4 (DRI2): > > > [ 10.924] (II) modeset(0): glamor initialized > > > [ 10.924] (WW) modeset(0): No outputs definitely connected, > > > trying again... > > > [ 10.925] (WW) modeset(0): Unable to find connected outputs - > > > setting 1024x768 initial framebuffer > > > [ 10.925] (=3D=3D) modeset(0): Using gamma correction (1.0, 1.0, > > > 1.0) > > > [ 10.925] (EE) modeset(0): No modes. > > > [ 10.957] (II) UnloadModule: "modesetting" > > > [ 10.957] (II) UnloadSubModule: "glamoregl" > > > [ 10.957] (II) Unloading glamoregl > > > [ 10.957] (EE) Screen(s) found, but none have a usable > > > configuration. > > > [ 10.957] (EE) > > > Fatal server error: > > > [ 10.957] (EE) no screens found(EE) > > > [ 10.957] (EE) > > > Please consult the The X.Org Foundation support > > > at http://wiki.x.org > > > for help. > > > [ 10.957] (EE) Please also check the log file at > > > "/var/log/Xorg.0.log" for additional information. > > > [ 10.957] (EE) > > > [ 10.957] (EE) Server terminated with error (1). Closing log > > > file. > > >=20 > > > ... > > >=20 > > > I am running the ArchLinuxARM linux-armv7 kernel (.config is > > > attached), along with the ALARM userspace. > > >=20 > > > I've attached dmesg's from my Jetson TK1 and Chromebook. How can I > > > help to debug this further? > >=20 > > Thanks for the report. I am seeing this too. Bisect is point to the > > following commit, hopefully, Thierry and Mikko can comment ... > >=20 > > commit 404bfb78daf3bedafb0bfab24947059575cbea3d > > Author: Mikko Perttunen > > Date: Wed Dec 14 13:16:14 2016 +0200 > >=20 > > gpu: host1x: Add IOMMU support >=20 > Thanks! I have investigated a bit further and can pinpoint it to > iommu_attach_device returning -ENODEV in drivers/gpu/host1x/dev.c's > host1x_probe. >=20 > I'll keep investigating to find out what's going on with the IOMMU > code. I have a fix for it now and display is back to life. Hooray! Will submit the patch ASAP, I'm not sure it's the exactly right way to do it, but it does work. Cheers, --=20 Paul Kocialkowski, developer of free digital technology and hardware support Website: https://www.paulk.fr/ Coding blog: https://code.paulk.fr/ Git repositories: https://git.paulk.fr/ https://git.code.paulk.fr/ --=-qc3V0W0AWYOD8fSnsIqv Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEAbcMXZQMtj1fphLChP3B6o/ulQwFAlliWUsACgkQhP3B6o/u lQyYcw//VETEAY99hL5ymJOk8k7ygJTqngq5EFaNwtn31MFd9pfwUw/Diao+bal5 0QhXAC4tskfL5BpZNmG0LnAE/hys27dYETS9Z+pe8CM5Tay1fotukGYLIKOy301X v/f84KwELkCn5epFw9QyLDlVOhdQyt6x0JcVWuQXEaFzNgwi5l1WjyXJbRx4cQgA C0IpAw6RTx+N0doWs61krAXZ63Y7JdqCKQqaV0Sv4y/bSssC7KNiXCs230S7EhSi DGFz8iBAT/xYl0qhKo3In4KJnh+YnHqcCGRtJdnstTdLkjApcbb/V/DNzGgQlVWa lboS00+fI++Ya9Iox+3ZgrAFDyX2GwPDPDcua3WZfrCnyw9I4QnbxK6YDU0eoOJ3 4yyuGV+QHiBMtm8DbnccH3PInLDtatmeYltGJ1h+Jsas46wM8zTqnzh5JZ/3g/o7 N7xkL0HlaCS3xou0PSPzzQk33iZy8pY/v8X4VlHlZIXQCyZIZCzHWNn0mnoBbyHq pD0HqeAQ4tyTf5XX+eDJw4LL2WL+fBJus2EgpBG6BYuqOD0bOut4R2dkbJOVae9f 5Ki+erOMx6qR/KsM3GB7OALvQxG/o059kBhoRzrXkThMkOYq8PsdLKF3EbXUq9em ZUvzcdsvt2CZOPwXUudrp7WurADCk5+e8qgzSP7IUOAydUIO0dM= =cbJo -----END PGP SIGNATURE----- --=-qc3V0W0AWYOD8fSnsIqv--