Opened 8 weeks ago

Last modified 7 weeks ago

#15123 new bug

KDL on unpacking LibreOffice tarball

Reported by: diver Owned by: nobody
Priority: normal Milestone: Unscheduled
Component: System/Kernel Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All

Description

hrev53209 x86_64 in VMware Fusion.

Kernel panics when I try to build LO using haikuporter libreoffice. Sometimes it goes through without crashing but unpacked source code is incomplete (missing many folders).

Attachments (3)

kdl.png (110.6 KB) - added by diver 8 weeks ago.
kdl2.png (151.4 KB) - added by diver 8 weeks ago.
kdl3.png (138.7 KB) - added by diver 7 weeks ago.

Download all attachments as: .zip

Change History (12)

Changed 8 weeks ago by diver

Attachment: kdl.png added

comment:1 Changed 8 weeks ago by diver

Another crash:

Changed 8 weeks ago by diver

Attachment: kdl2.png added

comment:2 Changed 8 weeks ago by diver

After reboot checksum of a tarball is wrong, so it looks like it gets corrupted. Could it be related to hrev53159? My /data partition is NVMe virtual disk.

comment:3 Changed 7 weeks ago by diver

Yet another crash:

Changed 7 weeks ago by diver

Attachment: kdl3.png added

comment:4 Changed 7 weeks ago by diver

checkfs /data after freezes Haiku while checking.

comment:5 Changed 7 weeks ago by diver

When I switched NVME to IDE in VM settings and reformatted the volume to BFS the crashes went away.

comment:6 Changed 7 weeks ago by waddlesplash

Looks like some kind of disk corruption so that's not surprising. Next time this happens please see if it occurs on IDE first, instead of just reformatting without even retesting.

comment:7 Changed 7 weeks ago by waddlesplash

I also note that the NVMe driver is not designed for non-NVMe latencies. I.e., using the NVMe driver on a drive that is really backed by a spinning disk will lead to *worse* CPU usage and access times than using IDE.

comment:8 Changed 7 weeks ago by pulkomandy

Summary: [kenel] panics on unpacking LibreOffice tarballKDL on unpacking LibreOffice tarball

comment:9 Changed 7 weeks ago by diver

VMware NVMe disk image in on a (non-NVMe) Samsung SSD EVO 860 1TB here.

Well I switched back this image in VM settings from IDE to NVMe, reformatted it and tried to unpack libreoffice translation tarball and again it wasn't unpacked completely. Running checkfs crashed to KDL with the same back trace as in the description (which was continuable).

I'm guessing this is something with nvme driver as I can't reproduce it with ata one. Or perhaps BFS driver doesn't play well with it.

wget https://github.com/LibreOffice/translations/archive/libreoffice-6.2.5.1.tar.gz
tar xzfv libreoffice-6.2.5.1.tar.gz

After unpacking check translations-libreoffice-6.2.5.1/source there should be 125 folders. If there are less it is possible that bfs has just been corrupted.

Note: See TracTickets for help on using tickets.