Paladin crashes into KDL

[roiredxsoto]

Good day,

Haiku installed on real hardware.

Expected behavior:

• Launch Paladin
• Work on a Project

Actual behavior:

• Launch Paladin
• Jump to KDL, need to reboot ( 'save-report' not working in KDL)

This started to happen just a moment ago, with the last hrev54278.

Attached is syslog

[roiredxsoto]

Syslog

[X512]

Can you take photo of KDL?

[X512]

hrev54278

Can be related to mmlr changes. Something can be broken because all patches was not applied.

[mmlr]

I can't seem to reproduce this. Can you share more details? Is this on x86_gcc2 or on x86_64 and are you opening a specific project or just launching the app?

Replying to X512:

hrev54278

Can be related to mmlr changes. Something can be broken because all patches was not applied.

The changes are all standalone, I tested them individually. The ones that weren't applied are related to MADV_FREE and some cleanups, they shouldn't matter in this context.

[mmlr]

I can't reproduce on a freshly downloaded nightly of hrev54278 x86_64 either.

From the syslog I see that it's x86_64. The syslog doesn't include a full boot and it doesn't contain information about any KDLs (fatal ones cannot be written back to the file in any case, they can only end up there if you can exit from KDL and the system is in a state where it can still write). So the syslog here is of limited use, maybe syslog.old contains more.

It does however state:

KERN: bfs: Oh no, value 3146359 not found in fragments of node 221184..., inode 5479

That doesn't sound healthy. It looks like there's a problem with some of the BFS structures, maybe the KDL is related to that? You can try running checkfs on the volume, but be aware that it may remove things it cannot open (for any reason, actual corruption or just by running out of memory), so make sure to back anything up that you still need.

[roiredxsoto]

20200612-Syslog.old

[roiredxsoto]

Good day, Added a syslog.old of 20200612, this syslog.old was produced just right now, so it's fresh. Just launching Paladin produces the trip to KDL, while before issue appeared when picking a project. And there is no response from KDL yet; I mean, I can type, nothing appears on the screen, and in the end still can't save a report. I also took a pic of the KDL that I will post later as it's on the phone.

It did work without issues before. Which makes it weirder.

The system is installed on an USB3 pendrive, 128 GB, in UEFI mode and runs on a Ryzen 5 1600 with 24 GB RAM. I presume memory is not an issue here. I did deactivate Virtual Memory and ran the checkfs on the System partition after doing so (I do this -virtual memory- the moment I install Haiku on anything).

I will do the checkfs and report any issues later. I don't recall any issue when I did it when deactivating the Virtual Memory though.

Whatever info you need let me know, I will try to provide it as soon as I can.

Thanks. Regards, RR

[roiredxsoto]

This is the outcome of "checkfs /Haiku":

        6526 nodes checked,
        0 blocks not allocated,
        0 blocks already set,
        0 blocks could be freed

        files           4091
        directories     2159
        attributes      160
        attr. dirs      107
        indices         9

        direct block runs               6453 (3.07 GiB)
        indirect block runs             3 (in 1 array blocks, 228.19 MiB)
        double indirect block runs      0 (in 0 array blocks, 0 bytes)

Seems fine, right?

[X512]

I also took a pic of the KDL that I will post later as it's on the phone.

It is hard to understand what is happening without KDL photo. It should contain error message and stack trace.

[roiredxsoto]

Picture of KDL. Launch Paladin and this is what is gotten

[roiredxsoto]

Replying to X512:

I also took a pic of the KDL that I will post later as it's on the phone.

It is hard to understand what is happening without KDL photo. It should contain error message and stack trace.

Added the pic, X512, if you need I carry some test procedure in order to gather more info, just let me know. Thanks. Regards, RR

[X512]

Problem seems to be in FAT file system. Can you check FAT volume in Windows?

[X512]

Crash happens here: ​https://git.haiku-os.org/haiku/tree/src/add-ons/kernel/file_systems/fat/dlist.c#n147.

[roiredxsoto]

Replying to X512:

Problem seems to be in FAT file system. Can you check FAT volume in Windows?

Ok. will do and report. FAT file system is a "shared" drive and didn't present any issue until lately. It's true that I had issues with the partition as before was NTFS, then changed to FAT. Maybe issue is related to that?

Edited:

• I just wanted to do some test before booting windows and check the filesystem. I unmounted the FAT volume and launch Paladin. This time, everything went fine. Paladin launched without issues, can create new projects or open those that I'm working on. So certainly it was related to the mounted FAT partition.
• I will check the filesystem in Windows and then report properly.

Thanks again X512! Regards, RR