panic: lockmgr: locking against myself
Debugger("panic")
Stopped at Debugger+0x37: movl$0,in_Debugger
db> trace
Debugger(c024333b) at Debugger+0x37
panic(c0242560,c3337df8,c32f4ed8,c76bd2c0,14d) at panic+0x74
lockmgr(c3337e20,12,c029f320,c6c90a20) at lockmgr+0x20b
cluster_wbuild(c76bd2c0
Ah, yes, some of us were just discussing this in a small mailing list.
Hopefully Kirk will pick up on it soon. Ah well.. someone else gets to be
the brunt of it for a change :-). Kirk doesn't have an SMP box so he
didn't see the bug.
I have tentitively tracked the problem do
* Warner Losh ([EMAIL PROTECTED]) [990627 09:02]:
> In message <[EMAIL PROTECTED]> "Justin T. Gibbs" writes:
> : The hope is to provide a consistent interface across
> : all *BSDs which is why I've addressed this to all of the *BSD projects.
>
> More generally, I'd like to identify areas where th
Matthew Dillon wrote:
> Ah, yes, some of us were just discussing this in a small mailing list.
> Hopefully Kirk will pick up on it soon. Ah well.. someone else gets to b
e
> the brunt of it for a change :-). Kirk doesn't have an SMP box so he
> didn't see the bug.
>
> I
/usr/src/release/texts/HARDWARE.TXT
or
http://www.etla.net/~n_hibma/usb
Nick
On Sat, 26 Jun 1999, Vince Gonzalez wrote:
> On Sat, Jun 26, 1999 at 04:11:28PM +0200, Nick Hibma wrote:
> >
> > Project status of the USB project:
>
> Is a list of currently supported devices av
In message <[EMAIL PROTECTED]>, Peter Wemm writes:
>Speaking of SMP and simple locks, I'd like to turn on the debugging
>simplelocks that keep a reference count and check before switching to make
>sure that a process doesn't sleep holding a lock. This is a pretty
>fundamental sanity check and wo
Matthew Dillon wrote:
> Ah, yes, some of us were just discussing this in a small mailing list.
> Hopefully Kirk will pick up on it soon. Ah well.. someone else gets to b
e
> the brunt of it for a change :-). Kirk doesn't have an SMP box so he
> didn't see the bug.
>
> I
On Sun, 27 Jun 1999, Peter Wemm wrote:
> Matthew Dillon wrote:
> > Ah, yes, some of us were just discussing this in a small mailing list.
> > Hopefully Kirk will pick up on it soon. Ah well.. someone else gets to b
> e
> > the brunt of it for a change :-). Kirk doesn't have an S
Doug Rabson wrote:
> On Sun, 27 Jun 1999, Peter Wemm wrote:
>
> > Matthew Dillon wrote:
> > > Ah, yes, some of us were just discussing this in a small mailing list
.
> > > Hopefully Kirk will pick up on it soon. Ah well.. someone else gets
to b
> > e
> > > the brunt of i
On Sun, 27 Jun 1999, Peter Wemm wrote:
> Doug Rabson wrote:
> > On Sun, 27 Jun 1999, Peter Wemm wrote:
> >
> > > Matthew Dillon wrote:
> > > > Ah, yes, some of us were just discussing this in a small mailing list
> .
> > > > Hopefully Kirk will pick up on it soon. Ah well.. someone
Doug Rabson wrote:
> On Sun, 27 Jun 1999, Peter Wemm wrote:
>
> > Doug Rabson wrote:
> > > On Sun, 27 Jun 1999, Peter Wemm wrote:
> > >
> > > > Matthew Dillon wrote:
> > > > > Ah, yes, some of us were just discussing this in a small mailing
list
> > .
> > > > > Hopefully Kirk wi
* Warner Losh ([EMAIL PROTECTED]) [990627 09:02]:
[Excuse my posting this to multiple lists, but I cannot let this go unnoticed]
> In message <[EMAIL PROTECTED]> Allen Briggs writes:
> : Ideally, there should be no more unnecessary divergence of the APIs--it
> : would also be nice to work toward
* Peter Wemm ([EMAIL PROTECTED]) [990627 09:02]:
> Bruce Evans wrote:
> > >>Why have splr semantics? That is, it raises to splsoftclock if current
> > >>priority is lower, else doesn't fiddle with it.
> >
> > splsoftclock() has always had spllower() semantics, and its main users
> > (kern_clock.c
Kirk,
It seems that the recent changes made by Kirk McKusick to the locking
mechanism in many files had some side effects.
A kernel as of this afternoon kept giving the following panic when
compiling a kernel, with the compile and source dir NFS mounted:
lockmgr: pid , not exclusive lock holde
From: Nick Hibma <[EMAIL PROTECTED]>
Subject: lockmgr panics
Date: Sun, 27 Jun 1999 14:15:06 +0200 (CEST)
Message-ID: <[EMAIL PROTECTED]>
hibma> lockmgr: pid , not exclusive lock holder -2 unlocking
Did you really get that message? if the unlocking process is
pid -2(LK_KERNPROC), we can unlock,
Seigo Tanimura wrote:
> From: Nick Hibma <[EMAIL PROTECTED]>
> Subject: lockmgr panics
> Date: Sun, 27 Jun 1999 14:15:06 +0200 (CEST)
> Message-ID: <[EMAIL PROTECTED]>
>
> hibma> lockmgr: pid , not exclusive lock holder -2 unlocking
>
>
> Did you really get that message? if the unlocking proces
:It seems to me the main problem (so far) is the buftimelock..
:
:simple_lock(&buftimelock);
:bp->b_lock.lk_wmesg = buf_wmesg;
:bp->b_lock.lk_prio = PRIBIO + 4;
:bp->b_lock.lk_timo = 0;
:return (lockmgr(&(bp)->b_lock, locktype, &buftimelock, curproc));
:
:
> Did you really get that message? if the unlocking process is
> pid -2(LK_KERNPROC), we can unlock, as in:
> lockmgr: pid -2, not exclusive lock holder 48 unlocking
This looks like it, yes. Must have made a typo.
Nick
--
e-Mail: [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROT
:In the long term, we probably need an spl-aware simplelock or maybe the
:cunning no-cost interrupt thread scheme which BSDi are using.
:
:--
:Doug RabsonMail: [EMAIL PROTECTED]
:Nonlinear Systems Ltd. Phone: +44 181 442 9037
I really like the idea
Hi folks,
I've just committed a change to inetd that will effectively turn TCP
Wrapping off for anyone who has an installed /etc/rc.conf that specifies
an inetd_flags value, as well as anyone who makes world without running
mergemaster to update /etc/defaults/rc.conf .
This will not be a proble
On Sat, 26 Jun 1999 11:57:17 -0400, Mikhail Teterin wrote:
> I'd, probably, put a symlink from the old location to the new one...
That's something you could do on your own machines, but I sincerely hope
we _don't_ do that to installworld and future releases.
Ciao,
Sheldon.
To Unsubscribe: s
On Sat, 26 Jun 1999 22:50:31 +0200, FreeBSD mailing lists wrote:
> Hi, I just wondered if it was a problem with my installation or in
> general, but is anyone else here having problems with ports being
> dependant on glib12.2 and ports installing glib12.3 instead?
Try mailing [EMAIL PROTECTED]
On Fri, Jun 25, 1999 at 11:35:04PM -0700, Alex Zepeda wrote:
> I've tried numerous times (updating the kernel, buildworld, etc) to get
> gdb to work, but so far it seems like ELF coredumps are broken (course
> this could be a C++ issue too):
It was fixed several weeks ago, at least in 4.0.
--
Mike Smith wrote:
> Someone else wrote:
> > I am not fond of the new defaults/rc.conf system. Used to be when I
> > wanted to modify something in rc.conf, I opened it up and changed the
> > value. Now I have to extract a line from defaults/rc.conf, put it in
> > rc.conf, and change it -- unless
A nice semi-solution to this problem of having to copy lines from
defaults/rc.conf would be a good curses-based rc.conf configuration tool.
It could read in a definition file (or this information could be embedded
into comments in defaults/rc.conf), present a list of configuration knobs
and thei
:
:But that doesn't fix the UP problem where cluster_wbuild() tries to
:recursively re-lock a buf that the current process already owns. I have a
:few ideas about that one though, I just don't understand the clustering
:well enough yet to fix it.
Ok, I just hit this testing the lockmgr chang
"Brian W. Buchanan" wrote:
>
> A nice semi-solution to this problem of having to copy lines from
> defaults/rc.conf would be a good curses-based rc.conf configuration tool.
Yes, this would be an excellent idea. However to save you time, I'll
expound the 3 different areas of argument that
Matthew Dillon wrote:
> :
> :But that doesn't fix the UP problem where cluster_wbuild() tries to
> :recursively re-lock a buf that the current process already owns. I have a
> :few ideas about that one though, I just don't understand the clustering
> :well enough yet to fix it.
>
> Ok, I jus
Please forgive me if this is a naive question, but could this problem also
relate to why starting netscape now panic's my system? I have a UP celeron
300a system and with the most recent -current I can boot fine, startx fine,
but as soon as I try to start netscape the system locks and rebo
Doug wrote:
> Please forgive me if this is a naive question, but could this problem a
lso
> relate to why starting netscape now panic's my system? I have a UP celeron
> 300a system and with the most recent -current I can boot fine, startx fine,
> but as soon as I try to start netscape th
Peter Wemm wrote:
>
> Doug wrote:
> > Please forgive me if this is a naive question, but could this problem a
> lso
> > relate to why starting netscape now panic's my system? I have a UP celeron
> > 300a system and with the most recent -current I can boot fine, startx fine,
> > but as s
> Hey Folks,
>
> I'm new to contributing to FreeBSD but not to working with kernels
> etc. I'm thinking of adding a new framing type to PPP which is described in
> the latest Transactions on Networking. Who do I talk to about this kind
> of stuff?
Me I guess - if you're thinking of addin
On Sun, 27 Jun 1999, Doug wrote:
> *nod* I will just hang out in windows for a while and check my commit
> mail. If it doesn't get fixed by the time I am ready to go back to beating
> on my serial console project, I'll do just that.
Hah, well some of us aren't quite that lucky :)
I manage
- Original Message -
From: Chris Moody <[EMAIL PROTECTED]>
To: Questions FreeBSD <[EMAIL PROTECTED]>
Sent: Sunday, June 27, 1999 6:14 PM
Subject: libstdc++.so.2
> Hello everyone,
>
> I spent several hours last night installing the Current version of FreeBSD
> over the internet, for some
This is going to sound like I'm attacking sheldon, but I'm not since he's
already stated that the got approval for this change from Jordan.
Sheldon Hearn wrote:
> Inetd now takes command-line options to enable wrapping. This was a
> decision taken with the approval of our release engine
On Mon, 28 Jun 1999, Peter Wemm wrote:
> Doug wrote:
> > Please forgive me if this is a naive question, but could this problem a
> lso
> > relate to why starting netscape now panic's my system? I have a UP celeron
> > 300a system and with the most recent -current I can boot fine, startx f
I'm getting the following repeatable panic since the introduction of
the changed lockmgr code:
(kgdb) bt
#0 Debugger (msg=0xc025d4fb "panic") at ../../i386/i386/db_interface.c:324
#1 0xc0153268 in panic (fmt=0xc0265de0 "nfs_strategy: buffer %p not locked") at
../../kern/kern_shutdown.c:450
#2
As most of you know by now, ctm is back, but ftp of ctm is temporarily
still broken. If you want something, tell me and I'll stick it in
http://www.freebsd.org/~chuckr. It's short of room there too, so don't
ask for what you don't need.
Thanks, I'll try not to post about ctm on current anymore.
:Yep, I was aware of this before, but I didn't rip it out since I didn't
:know what Kirk's intentions were. I'm assuming he's got his experience
:with making the BSD/OS vfs reentrant in mind, so I don't want to break
:anything that gets closer to that. A seperate test and then lock would
:not be
On your next ``make world'', you will need to change any "user.group"
specifications in /etc/newsyslog.conf to "user:group".
--
-- David([EMAIL PROTECTED] -or- [EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
This in current as of Saturday. The attached patch to
i386/i386/userconfig.c fixes the problem.:
Regards
--
Peter Holm | mailto:[EMAIL PROTECTED] | http://login.dknet.dk/~pho/
-[ Member of the BSD-Dk User Group / http://www.bsd-dk.dk/ ] -
*** userconfig.c~ Sun Jun 27 18:39:23 1999
---
Chris Moody wrote:
> - Original Message -
> From: Chris Moody <[EMAIL PROTECTED]>
> To: Questions FreeBSD <[EMAIL PROTECTED]>
> Sent: Sunday, June 27, 1999 6:14 PM
> Subject: libstdc++.so.2
>
> > Hello everyone,
> >
> > I spent several hours last night installing the Current version of Fr
42 matches
Mail list logo
