Tiny Core Base > Corepure64

Corepure64 won't boot on HP thin client

(1/4) > >>

FlyingDutchman:
Hi,

I'm running tiny core linux, corepure64 for a few years now without issue. I started at release 9 and upgraded through the years to releases 10, 11 and 12. However, release 13 won't boot on my system. I compared the on screen messages during startup and on release 13, halfway during boot I see the message "Freeing initrd memory: 12492K". I don't see that message in release 11 or 12. Then 2 segfaults follow and after that, the whole system freezes and a power cycle is the only option.

I don't think initrd memory is supposed to be freed, but I'm not sure. Any thoughts what is happening here? Or what a trigger might be to free initrd memory?

Sorry I can't include the logs; as the system doesn't boot to a CLI, I can't access them. I do have screenshots of the startup messages attached.

System information:
- HP Thin client t5550 (Via nano u3500 processor, 1 GB memory)
- Grub bootloader
- running Corepure64

Regards.

Juanito:
Have you checked the md5sum for corepure64.gz and vmlinuz64?

Edit: from a successful boot:
--- Code: ---$ dmesg | grep -i initrd
Freeing initrd memory: 12492K
--- End code ---

FlyingDutchman:
Hi,

Yes, I checked the md5 sums and these are correct. I also tried using "modules64.gz" and "rootfs64.gz" instead of "corepure64.gz"; same result.

BTW: it seems I'm on the wrong track with the "freeing initrd memory" message. Also in release 11 this message exists, only on a different moment in the startup sequence.

So, I really have no clue why the system won't start. Any thoughts what I can do to debug this?

Juanito:
google suggests:
--- Quote ---The solution is to add "udevchilds=64 udevtimeout=600" kernel boot codes
--- End quote ---

curaga:
The segfault says it was in libc.so. So it looks like a bug in libc given udev has not changed, and probably something that only triggers on a Via cpu too.

Tracking down libc bugs on a system that won't finish boot in the first place is going to be difficult. I would approach it by running 12.x, setting up a 13.x chroot, and then trying debug approaches with a debug-built libc.

It may be easier if you try searching the libc bugzilla and see if someone else has already reported it? Though Via users may be a bit rare, so there's a chance you're the first.

Navigation

[0] Message Index

[#] Next page