On Sun, 2 Nov 2003 [EMAIL PROTECTED] wrote:
> The obvious solution might be to change line 1161 of ffs_vfsops to
> pass vget() "curthread" rather than td. I assume there's a good
> reason why "thread0" is passed from boot(), but I can't see why
> that's of any use to the vnode locking.
Passing &t
On Sun, 2 Nov 2003 [EMAIL PROTECTED] wrote:
> >> For giggles I'm rolling back vfs_default.c back to 1.87 since its along
> >> the backtrace path.
> >
> >This didn't work so -CURRENT is fully broke.
> >
> >I'd suggest staying on 10/30 not before 4PM PST if you want to not crash
> >on shutdown.
> >
>> For giggles I'm rolling back vfs_default.c back to 1.87 since its along
>> the backtrace path.
>
>This didn't work so -CURRENT is fully broke.
>
>I'd suggest staying on 10/30 not before 4PM PST if you want to not crash
>on shutdown.
>
The patch worked for me. (Well, a slightly modified one: I
> I suspect I'll need to back up the whole thing to before the commit for
> the struct mount locking until jeff & kan can straighten things out.
>
> On Sun, 2 Nov 2003 [EMAIL PROTECTED] wrote:
>
> >
> >
> > >I can confirm the lockmgr panic on shutdown repo
>
>
> >I can confirm the lockmgr panic on shutdown reported by someone else
> >earlier (whose message I mistakenly deleted).
> >
> >It looks like swapper is trying to undo a lock from pagedaemon and runs
> >into trouble. This is probably related to the Giant
>I can confirm the lockmgr panic on shutdown reported by someone else
>earlier (whose message I mistakenly deleted).
>
>It looks like swapper is trying to undo a lock from pagedaemon and runs
>into trouble. This is probably related to the Giant pushdown of
>vm_pageout() that
c/sys/i386/i386/trap.c:1012
#15 0xc065d91d in Xint0x80_syscall () at {standard input}:144
On Sat, 1 Nov 2003, Doug White wrote:
> I can confirm the lockmgr panic on shutdown reported by someone else
> earlier (whose message I mistakenly deleted).
>
> It looks like swapper is tryi
I can confirm the lockmgr panic on shutdown reported by someone else
earlier (whose message I mistakenly deleted).
It looks like swapper is trying to undo a lock from pagedaemon and runs
into trouble. This is probably related to the Giant pushdown of
vm_pageout() that alc did last week.
I