On Sun, Sep 23, 2001 at 08:49:29PM +0200, Wilko Bulte wrote:
> Is there any reason to assume that specifying CPUTYPE ev56 has any
> influence on the lock order reversal?
No that I know of. I used to run a -CURRENT DS20 with CPUTYPE=ev56.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsu
On Mon, Sep 24, 2001 at 01:06:47PM +0800, Donny Lee wrote:
>
> Hi there,
>
> anyone out there has this problem?
Are you even reading this list?
Kris
PGP signature
Donny Lee wrote:
>
> Hi there,
>
> anyone out there has this problem?
>
> a new made world and kernel from last night (09/22) cvsup,
> and is unable to cvsup again tonight (09/23).
>
> [donny@sys]/usr/src> cvsup
> /usr/libexec/ld-elf.so.1: /usr/lib/libutil.so.3: Undefined symbol
> "__stdoutp"
Hi there,
anyone out there has this problem?
a new made world and kernel from last night (09/22) cvsup,
and is unable to cvsup again tonight (09/23).
[donny@sys]/usr/src> cvsup
/usr/libexec/ld-elf.so.1: /usr/lib/libutil.so.3: Undefined symbol
"__stdoutp"
5.0-c, with cvsup 16.1e.
--
// Donny
In message <[EMAIL PROTECTED]> Peter Jeremy writes:
: I have an old -CURRENT system[1] that can't do a buildworld any more,
: even with the latest bsd.{prog,lib}.mk changes (1.101 and 1.98). I
: delete /usr/obj before the buildworld, which writes off the above
: scenarios. Is anyone else seeing
On 2001-Sep-21 10:45:42 +0300, Ruslan Ermilov <[EMAIL PROTECTED]> wrote:
>Also, this error may only be caused if:
>
>1. The previous ``buildworld'' installed new headers in
>${WORLDTMP}/usr/include.
>
>2. The next ``buildworld'' was run with -DNOCLEAN.
>(Only in this case ${WORLDTMP}/usr
Mark Murray wrote:
> >
> > After compiling a new kernel, installing it, when my laptop
> > tries to mount its drive, it panics with this message:
> >
> > panic: lock (sleep mutex) vnode interlock not locked @
> > ../../../kern/vfs_default.c:460
> >
> > which is:
> >
> > if (ap->a_flags
On Thu, Sep 20, 2001 at 07:40:52PM +0200, Wilko Bulte wrote:
> On Wed, Sep 19, 2001 at 01:32:28PM -0700, John Baldwin wrote:
> >
> > On 19-Sep-01 Wilko Bulte wrote:
> > > On Tue, Sep 18, 2001 at 03:01:25PM -0700, John Baldwin wrote:
>
> ...
>
> > >> p_flag to p_sflag which changed its locking s
My rc.devfs has:
ln -fs /dev/psm0 /dev/mouse
My rc.conf has:
moused_port="/dev/mouse"
Unfortunately, this doesn't work because rc.syscons (which starts moused) is
run before rc.devfs, i.e. before the symlink is created. Could rc.devfs not be
moved up in rc so this does work?
Why? I'd
>
> After compiling a new kernel, installing it, when my laptop
> tries to mount its drive, it panics with this message:
>
> panic: lock (sleep mutex) vnode interlock not locked @
> ../../../kern/vfs_default.c:460
>
> which is:
>
> if (ap->a_flags & LK_INTERLOCK)
>mtx_unlock(&ap
Hi all,
Here's another one from src-cur.4972.gz. It's repeatable.
---
# ps -ae
lock order reversal
1st 0xc7fe4d08 process lock @ ../../../kern/kern_proc.c:215
2nd 0xc03e6620 Giant @ ../../../kern/subr_trap.c:98
exclusive (sleep mut
Hello,
After compiling a new kernel, installing it, when my laptop
tries to mount its drive, it panics with this message:
panic: lock (sleep mutex) vnode interlock not locked @
../../../kern/vfs_default.c:460
which is:
if (ap->a_flags & LK_INTERLOCK)
mtx_unlock(&ap->a_vp->v_int
On 23 Sep, Munehiro Matsuda wrote:
> Hi,
>
> I got following panic with recent -current (src-cur.4972.gz):
>
> recursed on non-recursive lock (sleep mutex) process lock @
>../../../i386/i386/trap.c:807
> first acquired @ ../../../kern/subr_trap.c:100
> panic: recurse
>
> syncing disks... panic
Hi,
I got following panic with recent -current (src-cur.4972.gz):
recursed on non-recursive lock (sleep mutex) process lock @
../../../i386/i386/trap.c:807
first acquired @ ../../../kern/subr_trap.c:100
panic: recurse
syncing disks... panic: bremfree: bp 0xc3bbd5ec not locked
System rebooted
14 matches
Mail list logo
