Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 12 Oct 2010 00:56:13 +0300
From:      Andriy Gapon <avg@icyb.net.ua>
To:        "Sam Fourman Jr." <sfourman@gmail.com>
Cc:        FreeBSD Current <current@freebsd.org>
Subject:   Re: -current under Xen
Message-ID:  <4CB387FD.2030101@icyb.net.ua>
In-Reply-To: <AANLkTikWR=O8BJbPWvzaopvNcMW2ju=KAOyGFP%2BPGhZR@mail.gmail.com>
References:  <4CA0184B.7030506@freebsd.org> <AANLkTikWR=O8BJbPWvzaopvNcMW2ju=KAOyGFP%2BPGhZR@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
on 11/10/2010 19:46 Sam Fourman Jr. said the following:
> On Sun, Sep 26, 2010 at 11:06 PM, Julian Elischer <julian@freebsd.org> wrote:
>>  After bruce C gave me the hint of kern.eventtimer.periodic=1, I was able to
>> boot -current on my vps
>> at rootbsd.com, but it hangs on reboot.. some time before the unmounts as
>> the
>> file systems need to be cleaned on the next successful boot.
>> Has anyone had any experience with this?
>>
>> unfortunately I can't yet tell you the version of Xen in use there.
>>
> 
> For what it is worth, I have the same shutdown issues on real hardware
> using 9 CURRENT

Breaking into ddb at that point and examining stacks of all threads[*] would
greatly help to pinpoint the issue.

[*] or forcing a dump for postmortem examination with kgdb.


-- 
Andriy Gapon



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4CB387FD.2030101>