Sorry. I pasted wrong logs.

GL_VERSION should be "3.0 Mesa 17.0.7" instead.

(In reply to Shih-Yuan Lee from com=
ment #3)
> Using DRI_PRIME=3D0 is just to switch between In=
tel and AMD Graphics.
> Of course, we can omit it completely.
>=20
> The system halt issue happens when executing `DRI_PRIME=3D1 glxgears -=
info`.
>=20
> u@u:~$ DRI_PRIME=3D1 glxgears -info
> Running synchronized to the vertical refresh.  The framerate should be
> approximately the same as the monitor refresh rate.
> GL_RENDERER   =3D Gallium 0.4 on AMD HAINAN (DRM 2.46.0, LLVM 3.8.0)
> GL_VERSION    =3D 3.0 Mesa 11.2.0
> GL_VENDOR     =3D X.Org
> ...
> u@u:~$ DRI_PRIME=3D0 glxgears -info
> Running synchronized to the vertical refresh.  The framerate should be
> approximately the same as the monitor refresh rate.
> GL_RENDERER   =3D Mesa DRI Intel(R) Kabylake GT1.5=20
> GL_VERSION    =3D 3.0 Mesa 11.2.0
> GL_VENDOR     =3D Intel Open Source Technology Center
> ...
>=20
> (In reply to Michel D=C3=A4nzer from comment #1)
> > Please attach the corresponding dmesg output.
> >=20
> > (In reply to Shih-Yuan Lee from comment #0)
> > > While I am doing the tests with AC plugged in by `DRI_PRIME=
=3D1 glxgears
> > > -info` and `DRI_PRIME=3D0 glxgears -info`, the system halts =
and then is forced
> > > to shutdown automatically.
> >=20
> > To clarify, DRI_PRIME=3D1 glxgears works, the problem only occurs=
 with
> > DRI_PRIME=3D0 glxgears?