On Fri, Sep 10, 2010 at 6:57 PM, Yuri Pankov wrote:
> Nevermind me. That's what I thought why I was getting the same gpart behavior
> switching between kernels, with and without DEBUG_LOCKS. Sorry about that.
>
> Same here, gpart hangs on:
> 3826 gpart CALL __sysctl(0x7fffa250,0x3,0,0x7fff
Nevermind me. That's what I thought why I was getting the same gpart behavior
switching between kernels, with and without DEBUG_LOCKS. Sorry about that.
Same here, gpart hangs on:
3826 gpartCALL __sysctl(0x7fffa250,0x3,0,0x7fffa268,0,0)
3826 gpartSCTL "kern.geom.confxml"
Yuri
Xin LI delphij.net> writes:
>
>
> Hi,
>
> On a brand new system I'm trying to allocate new GPT partition with:
>
> gpart create -s gpt ada0
> gpart add -t freebsd-zfs ada0
> And gpart hangs with "g_waitfor_event" with "g_event" spinning 100% of CPU.
>
> Any thoughts? The system is FreeBSD/a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
On a brand new system I'm trying to allocate new GPT partition with:
gpart create -s gpt ada0
gpart add -t freebsd-zfs ada0
And gpart hangs with "g_waitfor_event" with "g_event" spinning 100% of CPU.
Any thoughts? The system is FreeBSD/amd64
