Bug #1936

In single user mode installworld gets stuck

Added by sepherosa almost 4 years ago. Updated over 3 years ago.

Status:ClosedStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Target version:-

Description

2.9-DEVELOPMENT DragonFly v2.9.1.270.ge88a1-DEVELOPMENT

hammerfs mounted w/ nohistory

In single user mode installworld gets stuck at random place. This
happens on real boxes w/ ahci and w/ nata. This also happens in
virtual machines.
Pressing ctl-z and then running 'fg', could get installworld out of
stuck state, however, it still could get stuck later on.

In contrast, in normal mode, installworld will not get stuck as far as
I have tested.

Best Regards,
sephe

History

#1 Updated by ftigeot almost 4 years ago

On Fri, Dec 17, 2010 at 11:03:00AM +0800, Sepherosa Ziehau wrote:
> 2.9-DEVELOPMENT DragonFly v2.9.1.270.ge88a1-DEVELOPMENT
>
> hammerfs mounted w/ nohistory
>
> In single user mode installworld gets stuck at random place. This
> happens on real boxes w/ ahci and w/ nata. This also happens in
> virtual machines.
> Pressing ctl-z and then running 'fg', could get installworld out of
> stuck state, however, it still could get stuck later on.
>
> In contrast, in normal mode, installworld will not get stuck as far as
> I have tested.

Some signal issue perhaps ?

I have seen exactly the same behaviour with kaffe on NetBSD. The patch
in this PR fixed the problem:
http://gnats.netbsd.org/cgi-bin/query-pr-single.pl?number=44222

#2 Updated by sepherosa almost 4 years ago

On Fri, Dec 17, 2010 at 11:03 AM, Sepherosa Ziehau <> wrote:
> 2.9-DEVELOPMENT DragonFly v2.9.1.270.ge88a1-DEVELOPMENT
>
> hammerfs mounted w/ nohistory
>
> In single user mode installworld gets stuck at random place.  This
> happens on real boxes w/ ahci and w/ nata.  This also happens in
> virtual machines.
> Pressing ctl-z and then running 'fg', could get installworld out of
> stuck state, however, it still could get stuck later on.
>
> In contrast, in normal mode, installworld will not get stuck as far as
> I have tested.

This no longer happens on master; don't know which commit fixes it though.

Best Regards,
sephe

#3 Updated by tuxillo over 3 years ago

Confirmed it's fixed (although the commit couldn't be tracked)

Also available in: Atom PDF