#18621 closed bug (fixed)

git operations hang the system

Reported by: jackburton Owned by: nobody
Priority: normal Milestone: R1/beta5
Component: Drivers/Disk/Virtio Version:
Keywords: Cc:
Blocked By: Blocking:
Platform: x86-64

Description

I created a new VM with haiku beta4 (x64) I'm using it to develop. After a while, doing any git operation (on haikuports repo) results in git hanging. If I try to kill the git process, the whole system sort of hangs (but I'm still able to move windows around).

I tried upgrading to master but the problem persists.

I'm using qemu/kvm on Ubuntu 22.04 with 2 vcpu and 4GB ram. I've tried different NIC drivers (e1000, virtio, rtl8169) but without changes.

It's hard to give more info since I cannot open anything while the system is hanged.

Attachments (1)

Schermata del 2023-10-06 18-46-02.png (44.0 KB ) - added by jackburton 14 months ago.

Download all attachments as: .zip

Change History (14)

comment:1 by korli, 14 months ago

qemu with "-serial stdio" will output the serial log, if the syslog to serial output is enabled. Please provide this log.

comment:2 by waddlesplash, 14 months ago

And if the syslog does not contain the relevant data, a KDL session may be needed to find what the system has deadlocked on.

comment:3 by jackburton, 14 months ago

I did a "git status" multiple times, and it worked correctly. Then I did a "git stash" and it hanged. I can launch new Terminals, move around windows, but Deskbar menu doesn't open, nor I can open any new Tracker window. Doing a "ls" in another terminal hangs as well.

Syslog doesn't show anything useful: slab memory manager: created area 0xffffffff8e801000 (9264) slab memory manager: created area 0xffffffff8f001000 (10536) slab memory manager: created area 0xffffffff8f801000 (10537) slab memory manager: created area 0xffffffff90001000 (10538) slab memory manager: created area 0xffffffff90801000 (10539) slab memory manager: created area 0xffffffff91001000 (10540) slab memory manager: created area 0xffffffff91801000 (10541) slab memory manager: created area 0xffffffff92001000 (10542) slab memory manager: created area 0xffffffff92801000 (10543) slab memory manager: created area 0xffffffff93001000 (10544) slab memory manager: created area 0xffffffff93801000 (10545) slab memory manager: created area 0xffffffff94001000 (10550) slab memory manager: created area 0xffffffff94801000 (10551) slab memory manager: created area 0xffffffff95001000 (10552)

Launching "kernel_debugger" in a terminal window hangs, as well, without entering kernel debugger. This keyboard doesn't have sysreq so I can't enter kernel debugger with ALT-SYSREQ-D.

Version 0, edited 14 months ago by jackburton (next)

comment:4 by jackburton, 14 months ago

I was able to launch two more terminals (I have three opened now), then opening one more terminal failed, and the first terminal started failing to update its window

comment:5 by jackburton, 14 months ago

Interestingly, this seems to happen only with haikuports repo, as now.

in reply to:  5 comment:6 by jackburton, 14 months ago

Replying to jackburton:

Interestingly, this seems to happen only with haikuports repo, as now.

It actually just happened with other repos, so no.

comment:7 by diver, 14 months ago

Does export DISABLE_ASLR=1 change anything?

by jackburton, 14 months ago

comment:8 by jackburton, 14 months ago

You mean in a terminal, before git commands ? Seems not to make any difference (see attachment)

comment:9 by jackburton, 14 months ago

Component: System/KernelDrivers/Disk/Virtio

Found the problem: it's related to the "virtio" emulated storage. I changed the disk to "SATA" and the problem went away.

comment:10 by waddlesplash, 14 months ago

Sounds related to #18286. IIRC there was an older bug that mmlr fixed a while back which could also cause this.

in reply to:  10 comment:11 by jackburton, 14 months ago

Replying to waddlesplash:

Sounds related to #18286. IIRC there was an older bug that mmlr fixed a while back which could also cause this.

The symptoms described in #18286 are identical to the ones I'm experiencing, so I'd say it's the same problem

comment:12 by korli, 13 months ago

Milestone: UnscheduledR1/beta5

comment:13 by waddlesplash, 13 months ago

Resolution: fixed
Status: newclosed

Fixed in hrev57330.

Note: See TracTickets for help on using tickets.