On 4/24/20 6:48 PM, Xi Ruoyao via blfs-dev wrote:
On 2020-04-24 14:00 -0500, Douglas R. Reno via blfs-dev wrote:
On 4/24/20 9:52 AM, Xi Ruoyao via blfs-dev wrote:
In mesa-20.x the default dri driver for Intel Gen8+ (Broadwell and later)
iGPUs
has been changed to "iris" gallium driver, instead of the old "i965" driver.

I've added "iris" to GALLIUM_DRV in mesa instruction.  If you encounter any
problem with it you can add "MESA_LOADER_DRIVER_OVERRIDE=i965" to
/etc/profile,
to switch back to old i965 driver.

And, for Ice Lake and upcoming new generation of Intel CPUs libva-intel-
driver
won't work.  intel-media-driver is necessary for libva on Ice Lake.  It
depends
on intel-gmmlib.  I tried it on my laptop and it works (playing videos with
gstreamer and gstreamer-vaapi, and 1080p online videos on bilibili.com with
epiphany, gstreamer, and gstreamer-vaapi).
When trying to get this to work with mesa-20.0.5 on my system, trying to
launch Plasma resulted in a SIGABRT:

Core was generated by `/opt/kf5/bin/kwin_x11 -session
10504f4f48000158481520300000187340003_1587753581'.
Program terminated with signal SIGABRT, Aborted.
#0  raise (sig=<optimized out>) at ../sysdeps/unix/sysv/linux/raise.c:50
50      ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
[Current thread is 1 (Thread 0x7f34ddfed700 (LWP 27335))]
(gdb) bt
#0  raise (sig=<optimized out>) at ../sysdeps/unix/sysv/linux/raise.c:50
#1  0x00007f34f8224134 in KCrash::defaultCrashHandler(int) () at
/opt/kf5/lib/libKF5Crash.so.5
#2  0x00007f34f6a126e0 in <signal handler called> () at /lib/libc.so.6
#3  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#4  0x00007f34f69fc53b in __GI_abort () at abort.c:79
#5  0x00007f34f6f77a29 in  () at /opt/qt5/lib/libQt5Core.so.5
#6  0x00007f34e47f0b09 in
QtPrivate::QFunctorSlotObject<KWin::X11StandalonePlatform::createOpenGLSafePoi
nt(KWin::Platform::OpenGLSafePoint)::{lambda()#1},
0, QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase*,
QObject*, void**, bool*) () at
/opt/kf5-5.67.0/lib/plugins/org.kde.kwin.platforms/KWinX11Platform.so
#7  0x00007f34f71b45d3 in  () at /opt/qt5/lib/libQt5Core.so.5
#8  0x00007f34f71b7fba in QTimer::timeout(QTimer::QPrivateSignal) () at
/opt/qt5/lib/libQt5Core.so.5
#9  0x00007f34f71aca15 in QObject::event(QEvent*) () at
/opt/qt5/lib/libQt5Core.so.5
#10 0x00007f34f7c0661f in QApplicationPrivate::notify_helper(QObject*,
QEvent*) () at /opt/qt5/lib/libQt5Widgets.so.5
#11 0x00007f34f7c0f2b0 in QApplication::notify(QObject*, QEvent*) () at
/opt/qt5/lib/libQt5Widgets.so.5
#12 0x00007f34f7181632 in QCoreApplication::notifyInternal2(QObject*,
QEvent*) () at /opt/qt5/lib/libQt5Core.so.5
#13 0x00007f34f71d4900 in QTimerInfoList::activateTimers() () at
/opt/qt5/lib/libQt5Core.so.5
#14 0x00007f34f71d2dcf in
QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)
() at /opt/qt5/lib/libQt5Core.so.5
#15 0x00007f34f718034b in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at
/opt/qt5/lib/libQt5Core.so.5
#16 0x00007f34f6fae7ae in QThread::exec() () at /opt/qt5/lib/libQt5Core.so.5
#17 0x00007f34f6faf77d in  () at /opt/qt5/lib/libQt5Core.so.5
#18 0x00007f34f855def7 in start_thread (arg=<optimized out>) at
pthread_create.c:477
#19 0x00007f34f6ad423f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Apr 24 13:42:10 POOH /usr/libexec/gdm-x-session[27226]: Freeze in OpenGL
initialization detected
Apr 24 13:42:10 POOH /usr/libexec/gdm-x-session[27226]: Unable to start
Dr. Konqi
Apr 24 13:42:10 POOH /usr/libexec/gdm-x-session[27226]: Re-raising
signal for core dump handling.
Apr 24 13:42:10 POOH /usr/libexec/gdm-x-session[27169]: Service ":1.48"
unregistered

I did build Mesa with iris support as we have it in the book now,
however I'm hesitant to release the update to Mesa-20.0.5 unless we
decide to revert this (or if there is a fix available upstream, I'll go
look for that next). After exporting MESA_LOADER_DRIVER_OVERRIDE=i965 in
a file in /etc/profile.d, I was able to get Plasma to start again. If we
decide to revert it, I'll have to redo my stats.

This system is Skylake-based (which is one generation after Broadwell)
and uses Intel HD Graphics 530 as it's GPU. The kernel I have in use is
5.5.3. The CPU in use is a Core i5-6600k.
I have an i5-6500 but unfortunately it's in my office, where I can't reach now
(because of the stupid COVID).

Do you have any suggestions and am I missing anything? i965 seems to
work well for me in this case, but as I understand, it won't for newer
Intel CPUs?
I searched mesa repo and nothing useful is found.  Someone suggests that xf86-
video-intel is "bad" and should not be used for iGPUs later than year 2006.
Maybe it's guilty.

By the way, what version of Mesa did you use when adding this, Xi?
Since 19.x (used MESA_LOADER_DRIVER_OVERRIDE=iris, in 19.x i965 was the
default).  With mesa-20.0.0 some applications crash occasionally, but fixed with
20.0.1.  On 20.0.1-20.0.5 everything seems fine.

So I think we should report the issue to
https://gitlab.freedesktop.org/mesa/mesa/-/issues, and revert the change for
now.

I'll go ahead and revert the change for now. We can revisit it later :)

I'm going to put a comment in the book about it with a link to this mail. Some further testing done involved running TWM and running 'glxgears', where glxgears crashed as well.

I did notice some problems upstream (see the mesa-dev list and the 20.0.5 announcement replies), but none of them seem related to Iris at all...

--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to