Re: Tiny Core v17.0 upgrade issues

[Stefann]

Today 14:00 still running on TC15 after 3days.
I leave it running, go on 8day travel.

Note, I realised that instead of logging to usb-stick on 2nd system I can simply do that to the ram-disk of the 2nd system.
When logging on the live-system logging to ram-disk was not an option because it was not readable after a crash. Now I log via the network to the 2nd system there is no reason to avoid its ram-disk.
That means I can do logging at debug-level without causing excessive flashdisk writes when I re-setup the thing in "crash mode on TC17" when I'm back

For those interested, my full crashlog.
Initial log-entries are less precise maintained than later entries as at the beginning I did not know it would be this structural.

Code: [Select]

mon march 16: start around 12:00 //full TC17
Tue march 17: crashed in morning without yesterday data, so 24:00 latest
Tue march 17: start around 13:00 //full TC17
Wed march 18: crashed in morning without yesterday data, so 24:00 latest
Wed march 18: start around 23:00 //TC17 core & vmlinuz but no apps, add logging

Fri march 20: crashed in morning without yesterday data, so 24:00 latest // no logging due to mount mistake
Fri march 20: start around 14:00 //TC17 core & vmlinuz but  no apps, no X10 interface on usb because usb port used for logging on usb-stick
mon march 23: manual stop around 9:00 // no crash after 4 days
mon march 23: start with full TC17 and P1 & X10 interface 8:30 // X10 interface installed again, check that it still crashes
mon march 23: crash, no logging 22:00 - 23:00 // no logging because usb-slot used by X10 interface, not available for logging usb stick
tue march 24: restart with usbcore.autosuspend=-1 bootcode around 9:00 // usbcore.autosuspend=-1 bootcode
tue march 24: manual stop around 12:00
multiple manual start/stop due to install of home battery
Wed march 25: restart with usbcore.autosuspend=-1 bootcode around 20:00 // usbcore.autosuspend=-1 bootcode
Fri march 27: manual stop for maintenance 10:00; 38hr crash-free run
Fri march 27: restart with usbcore.autosuspend=-1 bootcode around 14:20 // usbcore.autosuspend=-1 bootcode
Sat march 28: crash around 9:00 //after 19hrs
Sat march 28: restart with usbcore.autosuspend=-1 bootcode around 13:30 // introduced serious logging, *.notice
Mon march 30: manual stop around 14:00 // 48hr run without issues
Mon march 30: restart under TC15, no extra bootcode around 17:00
Thu april 02: still running on TC15. Leaving for a 8 day travel

[Stefann]

OK... I'm back
System has been running on TC15 without any glitch for 12 days on TC15 without issue.
--> that proofs that it is TC related

Stats sofar:
TC15
- including usb-serial-6.6.8-tinycore.tcz
- "per second reading" of serial interface
- multiple month of running without issue
- rechecked last 2 weeks, 12days without issue ending with manual stop

TC17
- including usb-serial-6.18.2-tinycore.tcz
- "per second reading" of serial interface
3x crash after about 15hrs of runtime

TC17
- including usbcore.autosuspend=-1 bootcode
- including usb-serial-6.18.2-tinycore.tcz
- "per second reading" of serial interface
1x crash after about 19hrs of runtime
2x still running after >38hrs but manual stopped for reason of maintenance

I just started the thing:
TC17
- WITHOUT recompile or relink of application
- WITHOUT usbcore.autosuspend=-1 bootcode // try to get it to crash within a day
- including usb-serial-6.18.2-tinycore.tcz
- "per second reading" of serial interface
- rsyslog logging at debug level (*.*), writing over network to Ramdisk of 2nd computer (avoid flash-wear)

Note: on "logging" I'm a bit disappointed.
- I now see very detailed logging from my application
- but litterally zero kernel logging (maybe a bit at startup but that has been rotated away)
- I would have expected that "debug level" (which I think is included in *.*) would give me kernel things per second

So: any tips on getting more kernel logging are welcome
I'm writing to a Ramdisk so "overload of logging" is not a problem.

[Stefann]

Wel...
after 3 days of running in "crash mode" it did not crash.
I stopped the thing manually.

I had a tiny "hunge"... I did a full recompile of my application when I went back to TC15.
So... I grabbed the executable from the backup I made before upgrading and started that.

We'll see how this goes.
For the record, I did NOT reboot TC17

so... (recent) history:
sat april 11 TC17, 15:30
- WITHOUT recompile or relink of application
- WITHOUT usbcore.autosuspend=-1 bootcode // try to get it to crash within a day
- including usb-serial-6.18.2-tinycore.tcz
- "per second reading" of serial interface
- rsyslog logging at debug level (*.*), writing over network to Ramdisk of 2nd computer (avoid flash-wear)

tue april 14 16:20, manual stop, no crash over 3 days

tue april 14 16:23, start again under TC17
- using executeble as compiled on TC 15 march15, same executable that crashed earlier
- no reboot of TC17
- WITHOUT usbcore.autosuspend=-1 bootcode // try to get it to crash within a day
- including usb-serial-6.18.2-tinycore.tcz
- "per second reading" of serial interface
- rsyslog logging at debug level (*.*), writing over network to Ramdisk of 2nd computer (avoid flash-wear)

proof I donot have  usbcore.autosuspend=-1 bootcode

Code: [Select]

tc@huis:/krubo/work$ showbootcodes
BOOT_IMAGE=/tce/boot/vmlinuz17 quiet  host=huis cron tz=CET-1CEST,M3.5.0,M10.5.0/3 waitusb=5:UUID="a6f362cf-6c77-4fb7-bb05-76724d3b8113" tce=UUID="a6f362cf-6c77-4fb7-bb05-76724d3b8113"  initrd=/tce/boot/core17.gz
proof of release running:

Code: [Select]

tc@huis:/krubo/work$ uname -a
Linux huis 6.18.2-tinycore #1 SMP Sat Dec 20 21:06:22 UTC 2025 i686 GNU/Linux
proof of version of executable:

Code: [Select]

tc@huis:/krubo/work$ ls -l krubo
-rwxr-xr-x    1 tc       staff       242508 Mar 14 16:33 krubo