KernelPanic (new non!-user help please)

[thl04]

Good morning all,

Code: [Select]

version
uname -r


Thanks, those are good to know.

latest Core version which will boot sucessfully on your box, maybe start with Core 9.0. If it will boot you will be very close to success.

I have continued investigating the archive and I can boot the following :
TinyCore 6.4.1,  7.2,  8.2.1 and, CorePlus 6.4.1,  8.2.1.

I can not boot CorePlus-current,  TinyCorePure64-10.1,  TinyCore10.1,  CorePlus9.0.

I have not investigated what changes were made but for now, for my humble needs, I guess that any of those 6 thro' 8 will be good to go

[jazzbiker]

Hi, thl04!
As You can boot successfully TC 6, now is the time to know exactly what is Your hardware. This will help to understand why TC 10 kernel is panicing.
For example, show the optput of

Code: [Select]

dmesg running

Code: [Select]

dmesg>dmesg.txtand posting the resulting file "dmesg.txt" in your working dir to the forum.

Maybe a few words on finding the disks mounted. All disks found while system start you can see in

Code: [Select]

cat /etc/fstabIf You connect some disk, You can run

Code: [Select]

sudo rebuildfstaband see the changes in /etc/fstab file.

Another way is to load util-linux extension, using Apps or console:

Code: [Select]

tce-load -wi util-linuxand look at

Code: [Select]

lsblk
Some hardware info can be obtained using lspci:

Code: [Select]

tce-load -wi pci-utils
lspci

[jazzbiker]

Ok, i think it will be appropriate to continue with TC 8.

[jazzbiker]

And to be more precise on Your processor

Code: [Select]

cat /proc/cpuinfo | grep "model name"
In general there are a lot of interesting files in /proc directory, You can investigate them using

Code: [Select]

cat /proc/<somefile>or install text mode file browser Midnigt Commander

Code: [Select]

tce-load -wi mc

[thl04]

and posting the resulting file "dmesg.txt" in your working dir to the forum.

Errr, it is a bit big !
As a test I tried to send it as a PM to myself (before I foul-up and clog the forum !)
and got the error message

"The message exceeds the maximum allowed length (20000 characters)."

is that to be expected
and should I still post it here ?

[Rich]

Hi thl04

Code: [Select]

dmesg > dmesg.txtThen 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: [Select]

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
So working kernel and not working ones differ in

Code: [Select]

+CONFIG_DRM_I915_CAPTURE_ERROR=y
+CONFIG_DRM_I915_COMPRESS_ERROR=y
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.

[jazzbiker]

Debian Stretch with Raspberry Pi Desktop
The Raspberry Pi Desktop OS for PC and Mac - based on Debian Stretch
Version:April 2019
Release date:2019-04-11
Kernel version:4.9

Not very recent kernel version for 2019 year.
I haven't found config of their kernel.

[thl04]

it would be a little hard for him.

Just a little above my pay grade at the moment* but watching with interest. Thanks for investigating, all very interesting.

[OT *the last time I did any compiling was with TCC when Kernighan & Ritchie were still in short trousers LOL! /OT]
 

He also reported many other distros with recent kernels fail,

Yes, very curious, I'll have another look at them later. Later because my three USBsticks are
(A) Raspberry (<-I think they have not udated the PC desktop since 2016)
(B) CP8.2.1
both working so I will keep them untouched,
and (C) corrupted and unwritable ! dont know what I did to it but I need more sticks now before I can experiment further !

I did some gooling on " i915 " and there were quite a few hits - including Kernel failures I think, but all from a few years ago and I didnt understand. ( My brain is still too full of Win***s and needs a defrag  I think )

[jazzbiker]

[OT *the last time I did any compiling was with TCC when Kernighan & Ritchie were still in short trousers LOL! /OT]

TurboC ? 2.0 was my first C.

[thl04]

TurboC ?

Tiny C Compiler.

Turbo was Borland I think ?* which was big and too expensive and I like small and free,,,guess why I am here

My ref to K&R was muddled by the mists of time and dyslexia ! I should have said PCC in that connection - there were two in those days : Portable C Compiler and Personal C Compiler I think.

[jazzbiker]

Unbelievable - pcc started in 70ties, latest release - 2014-12-10!
" About 50% of the frontend code and 80% of the backend code has been modified." So the rest are working for near a half of a century?
From the mailing list:
 2. 2019-05-17  [3] [Pcc] Porting pcc to arm/linux for Raspberry Pi       pcc-list  Pitr Kaye
Time to think on extension for TinyCore!