General TC > General TC Talk

KernelPanic (new non!-user help please)

<< < (14/17) > >>

Rich:
Hi thl04

--- Code: ---dmesg > dmesg.txt
--- End code ---
Then attach the  dmesg.txt  file to your next post by clicking  Attachments and other options  and then the  Choose  button to
select the file.

thl04:
That is a good idea! Thanks,
I have topped and tailed it with TC version number for my future reference.

jazzbiker:
Hi, all topic readers and writers!

Let me say a few words on the thl04's problem with his dc5800 HP Compaq.
According to specs, this box utilizes internal Intel GMA3100 series graphics, it is driven by i915 kernel module.
I conclude, that the issue is graphics-related because with vga=791 screen becomes black during boot, and without this parameter the booter can see kernel messages about kernel panic.
And let's take into consideration that problem is absent for 4.8.17 and present for 4.14.10 and 4.19.10 kernels.
So I've done

--- Code: ---tc@box:/tmp$ diff config-4.8.17-tinycore config-4.14.10-tinycore | grep -i i915
 CONFIG_DRM_I915=m
-# CONFIG_DRM_I915_PRELIMINARY_HW_SUPPORT is not set
+# CONFIG_DRM_I915_ALPHA_SUPPORT is not set
+CONFIG_DRM_I915_CAPTURE_ERROR=y
+CONFIG_DRM_I915_COMPRESS_ERROR=y
 CONFIG_DRM_I915_USERPTR=y
-# CONFIG_DRM_I915_GVT is not set
 # drm/i915 Debugging
 # CONFIG_DRM_I915_WERROR is not set
 # CONFIG_DRM_I915_DEBUG is not set
+# CONFIG_DRM_I915_SW_FENCE_DEBUG_OBJECTS is not set
+# CONFIG_DRM_I915_SW_FENCE_CHECK_DAG is not set
+# CONFIG_DRM_I915_SELFTEST is not set
+# CONFIG_DRM_I915_LOW_LEVEL_TRACEPOINTS is not set
+# CONFIG_DRM_I915_DEBUG_VBLANK_EVADE is not set
tc@box:/tmp$ diff config-4.8.17-tinycore config-4.19.10-tinycore | grep -i i915
 CONFIG_DRM_I915=m
-# CONFIG_DRM_I915_PRELIMINARY_HW_SUPPORT is not set
+# CONFIG_DRM_I915_ALPHA_SUPPORT is not set
+CONFIG_DRM_I915_CAPTURE_ERROR=y
+CONFIG_DRM_I915_COMPRESS_ERROR=y
 CONFIG_DRM_I915_USERPTR=y
-# CONFIG_DRM_I915_GVT is not set
 # drm/i915 Debugging
 # CONFIG_DRM_I915_WERROR is not set
 # CONFIG_DRM_I915_DEBUG is not set
+# CONFIG_DRM_I915_SW_FENCE_DEBUG_OBJECTS is not set
+# CONFIG_DRM_I915_SW_FENCE_CHECK_DAG is not set
+# CONFIG_DRM_I915_DEBUG_GUC is not set
+# CONFIG_DRM_I915_SELFTEST is not set
+# CONFIG_DRM_I915_LOW_LEVEL_TRACEPOINTS is not set
+# CONFIG_DRM_I915_DEBUG_VBLANK_EVADE is not set
 CONFIG_SND_HDA_I915=y

--- End code ---
So working kernel and not working ones differ in

--- Code: ---+CONFIG_DRM_I915_CAPTURE_ERROR=y
+CONFIG_DRM_I915_COMPRESS_ERROR=y

--- End code ---
The other cause may be that i915 module changed after 4.8.17.
If it was not changed, then thl04 needs to recompile the 4.19.10 kernel, and seems that it would be a little hard for him.
How can we know, was i915 module changed since 4.8.17?

jazzbiker:
Or maybe firmware-i915 can in some way help?

curaga:
He also reported many other distros with recent kernels fail, so it's very unlikely it's those two options.

Navigation

[0] Message Index

[#] Next page

[*] Previous page