David Malone writes:
> > > This may be my fault, as I made some changes recently that assumed that
> > > the mbuf allocator grabbed giant when needed. I'll check the code path
> > > you've mentioned to see if it grabs giant now, but I suspect that I just
> > > need to move the giant grabbing b
> > This may be my fault, as I made some changes recently that assumed that
> > the mbuf allocator grabbed giant when needed. I'll check the code path
> > you've mentioned to see if it grabs giant now, but I suspect that I just
> > need to move the giant grabbing back where it was before.
> This
> <118>/etc/rc: INFO: nfsd depends on mountd, which will be forced to start.
> <118>Starting mountd.
> <118>Starting nfsd.
> panic: mutex Giant not owned at ../../../vm/vm_kern.c:315
> P
>
> Debugger(c04ec67c,c0586b60,c04ebdc3,c8cddb2c,1) at Debugger+0x54
>
On Wed, 28 May 2003, David Malone wrote:
> On Wed, May 28, 2003 at 10:06:14AM -0400, Robert Watson wrote:
> > I haven't seen this panic previously; a lack of Giant coming out of the
> > socket code is a bit surprising to me, but I think is unlikely to be a
> > result of our local MAC tweaks.
>
>
On Wed, May 28, 2003 at 10:06:14AM -0400, Robert Watson wrote:
> I haven't seen this panic previously; a lack of Giant coming out of the
> socket code is a bit surprising to me, but I think is unlikely to be a
> result of our local MAC tweaks.
This may be my fault, as I made some changes recently
cts
[EMAIL PROTECTED] Network Associates Laboratories
<118>a.out ldconfig path: /usr/lib/aout /usr/lib/compat/aout
/usr/X11R6/lib/aout
<118>/etc/rc: INFO: nfsd depends on mountd, which will be forced to start.
<118>Starting mountd.
<118>Starting nfsd.
panic: mutex Giant
Hello
When i try to create an RAID array with atacontol I get the following
panic when the rebuild is complete.
The problem seems to be that exit1 requires that giant is held but it
isn't. I have no idea where it should be aquired so it will be released
again.
#0 doadump () at /data/FreeBSD/CUR
I just got this on one of the alpha package build machines
Kris
panic: mutex Giant not owned at /local0/src-client/sys/vm/vm_kern.c:312
db_print_backtrace() at db_print_backtrace+0x18
panic() at panic+0x104
_mtx_assert() at _mtx_assert+0xb4
kmem_malloc() at kmem_malloc+0x50
page_alloc() at
On 16-Aug-01 John Baldwin wrote:
>
> On 16-Aug-01 David O'Brien wrote:
>># uname -a
>> FreeBSD phuong.nuxi.com 5.0-CURRENT FreeBSD 5.0-CURRENT #12: Sun Jul 15
>> 19:07:45 PDT 2001
>> [EMAIL PROTECTED]:/files/Current/sys/alpha/compile/DS20 alpha
>
> Looks like a trapsignal() in trap() is be
On 16-Aug-01 David O'Brien wrote:
># uname -a
> FreeBSD phuong.nuxi.com 5.0-CURRENT FreeBSD 5.0-CURRENT #12: Sun Jul 15
> 19:07:45 PDT 2001
> [EMAIL PROTECTED]:/files/Current/sys/alpha/compile/DS20 alpha
Looks like a trapsignal() in trap() is being called w/o Giant. I'll look at it.
Try t
On Wed, 15 Aug 2001, David O'Brien wrote:
> panic: mutex Giant not owned at ../../../kern/vfs_subr.c:2363
> ...
> #7 0xfc3d6090 in panic (
> fmt=0xfc5a9096 "mutex %s not owned at %s:%d")
> at ../../../kern/kern_shutdown.c:600
> #8 0xf
# uname -a
FreeBSD phuong.nuxi.com 5.0-CURRENT FreeBSD 5.0-CURRENT #12: Sun Jul 15 19:07:45 PDT
2001 [EMAIL PROTECTED]:/files/Current/sys/alpha/compile/DS20 alpha
panic: mutex Giant not owned at ../../../kern/vfs_subr.c:2363
#0 0xfc3d5c80 in dumpsys () at ../../../kern
12 matches
Mail list logo
