On Fri, 07 Jul 2017 13:54:09 +0200, Felix Miata wrote:
Takashi Iwai composed on 2017-07-07 08:28 (UTC+0200):
On Fri, 07 Jul 2017 03:29:38 +0200, Felix Miata wrote:
Takashi Iwai composed on 2017-07-06 21:10 (UTC+0200):
On Thu, 06 Jul 2017 18:38:03 +0200 Felix Miata wrote:
TW/Plasma/4.11.3 http://fm.no-ip.com/Tmp/SUSE/Factory/xorg.0.log-gx780-stwk5-20170706.txt http://fm.no-ip.com/Tmp/SUSE/Factory/jrnl-gx780-stwk5.txt
42.3/TDE/4.4.73 http://fm.no-ip.com/Tmp/SUSE/Factory/xorg.0.log-gx780-s423-20170706.txt http://fm.no-ip.com/Tmp/SUSE/Factory/jrnl-gx780-s423.txt
Do you mean kernel WARNING, not segfault, right?
I'm not a programmer. I mean any blocks in dmesg or journal that go between [ "cut here ]------------" and "---[ end trace" with "Call Trace" and 30+ lines of addresses, code strings and more.
That's no segfault. It's merely a stack trace triggered by kernel warning. Please remember at the next time for avoiding confusion.
Is it or is it not a problem routinely finding these warnings in dmesg & journal?
No, segfault is an incorrect word. segfault is no generic word meaning a random error message at all.
00:02.0 VGA compatible controller [0300]: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e12] (rev 03) Subsystem: Dell Device [1028:0420] Kernel driver in use: i915 Kernel modules: i915 00:02.1 Display controller [0380]: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e13] (rev 03)
I see errors in dmesg, but don't see evidence of trouble. Are these kernel or DRM problems that need fixing? Anything look like a bug already reported?
The symptom looks very same as the issue you already reported.
Unless you mean 12 months ago https://lists.opensuse.org/opensuse-factory/2016-07/msg00192.html or 5 months ago https://lists.opensuse.org/opensuse-kernel/2017-02/msg00002.html and https://bugzilla.opensuse.org/show_bug.cgi?id=1025655 (dup'd to 1022181, fixed 5 months ago) I have no idea what report you refer to.
This one: http://www.spinics.net/lists/intel-gfx/msg100776.html
I have a more than a dozen multiboot machines running TW and various "Distributions". The one that instigated this thread (gx780) has almost no relationship to that one (g5eas). g5eas was 42.2 with NVidia video and TDE. A year ago's and this thread for host gx780 are Intel video TW with Plasma and 42.3 with TDE.
It's a tad old stuff and if the TW kernel still shows the problem,
What do you mean by old stuff? Host gx780 (this thread) is my second newest machine, and the newest I ever use for testing.
The kernel warning comes from i915 Intel graphics driver, and that Intel device is old. It's not about Nvidia at all.v
it's likely not fixable soonish in drm-kmp for Leap 42.3. If the issue wasn't seen in 42.2, you can simply uninstall drm-kmp to go back to 4.4.x kernel DRM stack. If it works better for you, keep it uninstalled, and add lock to zypper, for example.
KMP??? gx780's TW and 42.3 installations have no package named *kmp* installed. AFAIK, no package named *kmp* is installed on any of my machines. All are real hardware installations.
If you're using Nvidia binary-driver, Never ever.
then drm-kmp is excluded. Other
than that, drm-kmp is automatically installed on Leap 42.3 on bare metals. No package *drm-kmp* exists on TW that I can find, much less find installed anywhere here. I tried two slighty older Eagle Lake Intel Video machines in addition to the Q45 Eagle Lake gx780: a Q43 Eagle Lake host gx760 and a G41 Eagle Lake host big41.
drm-kmp is 42.3 only. But you mentioned that you have no drm-kmp on 42.3, and it's already strange. Either you overlooked it, or something wrong in your 42.3 setup / installation. But no need to follow up about it, as I'm not interested in it. For TW problem, please continue / chasing the fix in the upstream. It's basically a problem to be addressed in the upstream. We basically just follow the upstream development. Once when it's fixed in the upstream, you can ping us to take the fix into TW and/or Leap. That'd be highly appreciated. thanks, Takashi -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org