On Sun, May 03, 2020 at 10:04:04AM -0600, Ian Lepore wrote:
> That LOR site hasn't been updated in years. Many many years.
If someone wants to help me set up a page on the wiki, let me know.
(I have too much on my plate to do it myself.)
mcl
___
freebs
On Sat, 2020-05-02 at 20:36 +0200, Kurt Jaeger wrote:
> Hi!
>
> > > > I am compiling some packages with poudriere on 13-current kernel. I
> > > > noticed some strange messages printed into the terminal and dmesg:
> > > >
> > > > lock order reversal:
> > >
> > > [...]
> > > > Are those the debug
On 03/05/2020 15:00, Niclas Zeising wrote:
On 2020-05-02 20:36, Kurt Jaeger wrote:
I don't know, either 8-} bz@ is in Cc:, so he'll probably know what
to do.
How do I know if I have got a backtrace?
Are those errors:
pid 43297 (conftest), jid 5, uid 0: exited on signal 11
related or it's
On 2020-05-02 20:36, Kurt Jaeger wrote:
Hi!
I am compiling some packages with poudriere on 13-current kernel. I
noticed some strange messages printed into the terminal and dmesg:
lock order reversal:
[...]
Are those the debug messages that aren't visible on non-current kernel
and should they
On 02/05/2020 10:08, Grzegorz Junka wrote:
I am compiling some packages with poudriere on 13-current kernel. I
noticed some strange messages printed into the terminal and dmesg:
lock order reversal:
1st 0xf8010ca78250 zfs (zfs) @ /usr/src-13/sys/kern/vfs_mount.c:1005
2nd 0xf8010cd372
Hi!
> > > I am compiling some packages with poudriere on 13-current kernel. I
> > > noticed some strange messages printed into the terminal and dmesg:
> > >
> > > lock order reversal:
> > [...]
> > > Are those the debug messages that aren't visible on non-current kernel
> > > and should they be r
On 02/05/2020 10:54, Kurt Jaeger wrote:
Hi!
I am compiling some packages with poudriere on 13-current kernel. I
noticed some strange messages printed into the terminal and dmesg:
lock order reversal:
[...]
Are those the debug messages that aren't visible on non-current kernel
and should th
Hi!
> I am compiling some packages with poudriere on 13-current kernel. I
> noticed some strange messages printed into the terminal and dmesg:
>
> lock order reversal:
[...]
> Are those the debug messages that aren't visible on non-current kernel
> and should they be reported?
Yes, they should b
On Mon, 26 Feb 2018 08:42:14 +0200 "Andriy Gapon" said
On 26/02/2018 07:18, Jon Brawn wrote:
> Wotcha!
>
> So, I’ve been using FreeBSD 12-CURRENT at various svn releases for a while
> now, and I get quite a few “lock order reversal” dumps. The one I’ve got
> on my screen at the moment is for
On 26/02/2018 07:18, Jon Brawn wrote:
> Wotcha!
>
> So, I’ve been using FreeBSD 12-CURRENT at various svn releases for a while
> now, and I get quite a few “lock order reversal” dumps. The one I’ve got on
> my screen at the moment is for ufs / bufwait / ufs:
>
> root@brax:/usr/src/stand # lock
On Wed, 22 Feb 2017 21:06:32 -0600, Benjamin Kaduk wrote:
> Hi Jeffrey,
>
> Thank you for your enthusiasm in reporting these.
> Unfortunately, it is very likely that these two are "well-known" and
> believed to be harmless, so you have not discovered something
> terribly exciting.
>
> An old
Hi Jeffrey,
Thank you for your enthusiasm in reporting these.
Unfortunately, it is very likely that these two are "well-known" and
believed to be harmless, so you have not discovered something
terribly exciting.
An old and no-longer particularly maintained listing of these and
other LORs is at: h
This one at boot:
#0 to #10
bufwait
/usr/src/sys/kern/vfs_bio.c:3500
dirhash
/usr/src/sys/ufs/ufs/ufs_dirhash.c:201
r313487 12.0-CURRENT Feb 13 2017
1200020 FWIW
both the above and the below reports...
On Wed, 22 Feb 2017 15:37:21 -0800 (PST), "Jeffrey Bouquet"
wrote:
> #0 #16 follow:
I see this LOR often too.
I thought maybe this is happening because of my Virtual Box setting :) (?!?)
On 5/21/16, Will Brokenbourgh wrote:
> On 05/16/16 00:44, Bjoern A. Zeeb wrote:
>>> On 15 May 2016, at 07:44 , Kurt Jaeger wrote:
>>>
>>> Hi!
>>>
I am seeing 'lock order reversal' errors d
On 05/16/16 00:44, Bjoern A. Zeeb wrote:
On 15 May 2016, at 07:44 , Kurt Jaeger wrote:
Hi!
I am seeing 'lock order reversal' errors during boot on 11-CURRENT -
r298793. A sample error:
lock order reversal:
1st 0xf8011280d068 ufs (ufs) @ /usr/src/sys/kern/vfs_subr.c:2498
2nd 0xfe
> On 15 May 2016, at 07:44 , Kurt Jaeger wrote:
>
> Hi!
>
>> I am seeing 'lock order reversal' errors during boot on 11-CURRENT -
>> r298793. A sample error:
>>
>> lock order reversal:
>> 1st 0xf8011280d068 ufs (ufs) @ /usr/src/sys/kern/vfs_subr.c:2498
>> 2nd 0xfe01ca539400 bufwait
Hi!
> I am seeing 'lock order reversal' errors during boot on 11-CURRENT -
> r298793. A sample error:
>
> lock order reversal:
> 1st 0xf8011280d068 ufs (ufs) @ /usr/src/sys/kern/vfs_subr.c:2498
> 2nd 0xfe01ca539400 bufwait (bufwait) @
> /usr/src/sys/ufs/ffs/ffs_vnops.c:263
> 3rd
On Wed, 24 Feb 2016, Eax Melanhovich wrote:
> Hello.
>
> Yesterday I built a kernel and world using master branch (6a8922d3) of
> FreeBSD GitHub repository (a mirror of SVN as I understand?). Today I
> got a "lock order reversal" report:
>
> http://i.imgur.com/jDZ4A3O.png
>
> According to this FAQ
John Baldwin wrote on 08.06.2012 18:45:
On Friday, June 08, 2012 4:21:34 am Ruslan Mahmatkhanov wrote:
Ruslan Mahmatkhanov wrote on 08.06.2012 12:10:
Good day,
After updating to yesterdays -current, I got this on boot:
lock order reversal:
1st 0xfe0007b04c38 ufs (ufs) @ /usr/src/sys/kern/
Am 08.06.2012 10:10, schrieb Ruslan Mahmatkhanov:
> Good day,
>
> After updating to yesterdays -current, I got this on boot:
>
> lock order reversal:
> 1st 0xfe0007b04c38 ufs (ufs) @ /usr/src/sys/kern/vfs_mount.c:1254
> 2nd 0xfe0007ed9478 devfs (devfs) @ /usr/src/sys/kern/vfs_subr.c:215
On Friday, June 08, 2012 4:21:34 am Ruslan Mahmatkhanov wrote:
> Ruslan Mahmatkhanov wrote on 08.06.2012 12:10:
> > Good day,
> >
> > After updating to yesterdays -current, I got this on boot:
> >
> > lock order reversal:
> > 1st 0xfe0007b04c38 ufs (ufs) @ /usr/src/sys/kern/vfs_mount.c:1254
> >
Ruslan Mahmatkhanov wrote on 08.06.2012 12:10:
Good day,
After updating to yesterdays -current, I got this on boot:
lock order reversal:
1st 0xfe0007b04c38 ufs (ufs) @ /usr/src/sys/kern/vfs_mount.c:1254
2nd 0xfe0007ed9478 devfs (devfs) @ /usr/src/sys/kern/vfs_subr.c:2158
KDB: stack back
Thanks, K. Macy
Ok
Sorry to disturb
K. Macy wrote:
When WITNESS support was added to lockmgr locks a number of
longstanding LORs were exposed in the process. I can't comment on
whether or not they'll be fixed or the warnings will some day be
silenced.
On Tue, Sep 6, 2011 at 2:58 PM, Vadim Deni
When WITNESS support was added to lockmgr locks a number of
longstanding LORs were exposed in the process. I can't comment on
whether or not they'll be fixed or the warnings will some day be
silenced.
On Tue, Sep 6, 2011 at 2:58 PM, Vadim Denisov wrote:
> I install current on last week
> I have s
On Tue, Dec 7, 2010 at 9:18 AM, Julian Elischer wrote:
> On 12/7/10 3:41 AM, Attilio Rao wrote:
>>
>> 2010/12/7 Erik Cederstrand:
>>>
>>> Den 07/12/2010 kl. 10.20 skrev Garrett Cooper:
>>>
On Dec 7, 2010, at 12:26 AM, Mehmet Erol
Sanliturk wrote:
> A Dmesg.TXT is attached havin
On 12/7/10 3:41 AM, Attilio Rao wrote:
2010/12/7 Erik Cederstrand:
Den 07/12/2010 kl. 10.20 skrev Garrett Cooper:
On Dec 7, 2010, at 12:26 AM, Mehmet Erol Sanliturk
wrote:
A Dmesg.TXT is attached having a lock order reversal .
The mount LOR is well known.
I see that this is the stand
2010/12/7 Erik Cederstrand :
>
> Den 07/12/2010 kl. 10.20 skrev Garrett Cooper:
>
>> On Dec 7, 2010, at 12:26 AM, Mehmet Erol Sanliturk
>> wrote:
>>
>>> A Dmesg.TXT is attached having a lock order reversal .
>>
>> The mount LOR is well known.
>
> I see that this is the standard response to lot
Den 07/12/2010 kl. 10.20 skrev Garrett Cooper:
> On Dec 7, 2010, at 12:26 AM, Mehmet Erol Sanliturk
> wrote:
>
>> A Dmesg.TXT is attached having a lock order reversal .
>
>The mount LOR is well known.
I see that this is the standard response to lot's of LOR reports. It seems to
be one o
On Dec 7, 2010, at 12:26 AM, Mehmet Erol Sanliturk
wrote:
> A Dmesg.TXT is attached having a lock order reversal .
The mount LOR is well known. The duplicate lock held WITNESS warning with
em(4) might be of interest though.
Thanks,
-Garrett___
fr
On 9 Jun 2010, at 12:58, John Baldwin wrote:
> On Wednesday 09 June 2010 3:51:52 am Bernd Walter wrote:
>> Got this during installworld (source on NFS, destination UFS on CF-card)
>> Source is current checked out yesterday.
>>
>> lock order reversal:
>> 1st 0xc28b85b4 bufwait (bufwait) @
>> /da
On Wednesday 09 June 2010 3:51:52 am Bernd Walter wrote:
> Got this during installworld (source on NFS, destination UFS on CF-card)
> Source is current checked out yesterday.
>
> lock order reversal:
> 1st 0xc28b85b4 bufwait (bufwait) @
> /data/builder/c13-2010-06-07/head/sys/kern/vfs_bio.c:2575
On Jun 9, 2010, at 12:51 AM, Bernd Walter wrote:
> Got this during installworld (source on NFS, destination UFS on CF-card)
> Source is current checked out yesterday.
>
> lock order reversal:
> 1st 0xc28b85b4 bufwait (bufwait) @
> /data/builder/c13-2010-06-07/head/sys/kern/vfs_bio.c:2575
> 2nd 0
On Sun, Nov 30, 2003 at 07:46:55PM -0500, [EMAIL PROTECTED] wrote:
> Is this a known issue on 5.2 beta 6 sup'ed nov 29/03?
Yes, it's reported on a daily basis and is harmless.
Kris
pgp0.pgp
Description: PGP signature
On Thu, Nov 27, 2003 at 10:00:54PM -0500, Mikhail Teterin wrote:
> > On Thu, Nov 27, 2003 at 07:16:05PM -0500, Mikhail Teterin wrote:
> > > It did not crash or anything, but the following is printed on
> > > console now (addresses ommitted):
> > >
> > > lock order reversal
> > >1st ... UMA l
> On Thu, Nov 27, 2003 at 07:16:05PM -0500, Mikhail Teterin wrote:
> > It did not crash or anything, but the following is printed on
> > console now (addresses ommitted):
> >
> > lock order reversal
> > 1st ... UMA lock (UMA lock) @ /usr/src/sys/vm/uma_core.c:1201
> > 2nd ... system
On Tue, Nov 25, 2003 at 07:05:36PM -0600, John wrote:
> i was just looking through my daily reports from my new 5.2 beta box and
> found this in dmesg.
> lock order reversal
> 1st 0xc08f7ce0 UMA lock (UMA lock) @ /usr/src/sys/vm/uma_core.c:1201
> 2nd 0xc1031100 system map (system map) @ /usr/src
On Thu, Jul 10, 2003 at 11:58:14AM +0200, Gordon Bergling wrote:
> Hi,
>
> getting this on a -current from 'Jul 6 23:16:01 CEST 2003'.
> I'll recieve this error a few minutes ago directly after booting the
> system. No user where logged in this time.
FAQ..it's harmless
Kris
pgp0.pgp
Descr
On Mon, Jul 07, 2003 at 02:26:43PM +0400, Andrew Kolchoogin wrote:
> lock order reversal
> 1st 0xc2f4b128 vm object (vm object) @ vm/vm_object.c:432
> 2nd 0xc082f110 system map (system map) @ vm/vm_kern.c:325
This is known to be harmless.
Kris
pgp0.pgp
Description: PGP signature
On Wed, 12 Mar 2003, John Baldwin wrote:
> It's holding the lock across bus_setup_intr(). You can try the
> following patch:
>
> Index: if_tl.c
> ===
> RCS file: /usr/cvs/src/sys/pci/if_tl.c,v
> retrieving revision 1.74
> diff -u -r1
On 12-Mar-2003 Tod McQuillin wrote:
>
> Running -current from March 11 on a dual cpu compaq 5100, there are some
> warnings in the dmesg about the tl ethernet interface.
>
> Here are the warnings:
>
> malloc() of "128" with the following non-sleepablelocks held:
> exclusive sleep mutex tl0 (net
Craig Rodrigues wrote:
> On Tue, Jan 28, 2003 at 07:04:07PM -0600, Sean Kelly wrote:
> > I just noticed this during bootup. It is repeatable.
>
> See:
> http://news.gw.com/freebsd.current/30547
That's a "turn your head and cough" patch. It admits the code
is broken, and leaves it broken. It als
On Tue, Jan 28, 2003 at 07:04:07PM -0600, Sean Kelly wrote:
> I just noticed this during bootup. It is repeatable.
See:
http://news.gw.com/freebsd.current/30547
--
Craig Rodrigues
http://home.attbi.com/~rodrigc
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsub
Hello,
I've seen this very same message on one of my -current testboxes. While
we're on the topic of LORs, I've also come across the following:
Jan 27 00:44:57 largo kernel: lock order reversal
Jan 27 00:44:57 largo kernel: 1st 0xc6708314 inp (inp)
@../../../netinet/tcp_input.c:641
Jan 27 00:44:
Kris Kennaway wrote:
On Mon, Jan 06, 2003 at 06:56:39PM +0100, Ulrich Spoerlein wrote:
>On 2003/01/05-00:25:17 leafy wrote:
>
>
>>lock order reversal
>>Jan 5 00:19:15 leafy kernel: 1st 0xc26b05c0 process lock (process lock)
>>@/usr/src/sys/kern/kern_descrip.c:2099 Jan 5 00:19:15 leafy kernel:
On Mon, Jan 06, 2003 at 06:56:39PM +0100, Ulrich Spoerlein wrote:
> On 2003/01/05-00:25:17 leafy wrote:
>
> >lock order reversal
> >Jan 5 00:19:15 leafy kernel: 1st 0xc26b05c0 process lock (process lock)
> >@/usr/src/sys/kern/kern_descrip.c:2099 Jan 5 00:19:15 leafy kernel: 2nd
> >0xc2667e34 fil
On 2003/01/05-00:25:17 leafy wrote:
>lock order reversal
>Jan 5 00:19:15 leafy kernel: 1st 0xc26b05c0 process lock (process lock)
>@/usr/src/sys/kern/kern_descrip.c:2099 Jan 5 00:19:15 leafy kernel: 2nd
>0xc2667e34 filedesc structure (filedesc structure) @
>/usr/src/sys/kern/kern_descrip.c:2106
On Sun, Aug 18, 2002 at 05:27:13PM -0700, Alex Zepeda wrote:
> Should I set debug.witness_ddb to 1 and get a trace from it? Or has this
> one already been seen?
It already fell over in exec, here's what it said:
GNU gdb 5.2.0 (FreeBSD) 20020627
Copyright 2002 Free Software Foundation, Inc.
GD
> No setuid executables ... it's a mystery to me how one encounters this
> code path when running netscape :-(
Hmmm, after patch about FILEDESC_LOCK (1.139), my netscape can run
correctly. (@_@)
--
Jun Kuriyama <[EMAIL PROTECTED]> // IMG SRC, Inc.
<[EMAIL PROTECTED]> // FreeBSD P
On Tue, Apr 23, 2002 at 01:20:07AM +0900, Jun Kuriyama wrote:
> At Mon, 22 Apr 2002 11:09:26 -0500,
> Jacques A. Vidrine <[EMAIL PROTECTED]> wrote:
> > I'm curious ... could you send the output of
> >
> > pkg_info -L linux-netscape-navigator-4.79 | xargs ls -l
>
> Attached.
No setuid executa
> I have no idea about this. I'm portupgrade'ing linux_base,
> linux-netscape-* port and I'll try this again.
Hmm, I can reproduce this even after upgrading related ports...
--
Jun Kuriyama <[EMAIL PROTECTED]> // IMG SRC, Inc.
<[EMAIL PROTECTED]> // FreeBSD Project
To Unsubscrib
At Mon, 22 Apr 2002 11:09:26 -0500,
Jacques A. Vidrine <[EMAIL PROTECTED]> wrote:
> I'm curious ... could you send the output of
>
> pkg_info -L linux-netscape-navigator-4.79 | xargs ls -l
Attached.
> Also, does `/compat/linux/bin/sh' blow up for you?
No, I can invoke this without problem..
On Mon, Apr 22, 2002 at 10:35:49PM +0900, Jun Kuriyama wrote:
> A kern_descrip.c is updated by tanimura after your r1.137. Could you
> try with r1.138?
Just updated to today's -CURRENT. I still cannot reproduce the issue.
I'm curious ... could you send the output of
pkg_info -L linux-netsc
On Mon, Apr 22, 2002 at 11:28:41AM +0900, Jun Kuriyama wrote:
>
> Today's -current kernel. This happend when I invoke linux-netscape.
Does it happen every time? I cannot reproduce it.
What is odd is that fdcheckstd() is only called when exec'ing a
set[ug]id executable -- any idea what set[ug]
At Mon, 22 Apr 2002 07:32:39 -0500,
Jacques A. Vidrine <[EMAIL PROTECTED]> wrote:
> Does it happen every time? I cannot reproduce it.
Yes.
> What is odd is that fdcheckstd() is only called when exec'ing a
> set[ug]id executable -- any idea what set[ug]id program is being
> exec'd here?
I have
> and the sound cracks/stops playing for the fraction of a second. seems
> like it happens more often during disk or network activity ( i mount
> /usr/ports via nfs, and when i build a port it happens all the time). the
> soundcard is a sblive. i searched the archive for this problem, but didnt
>
On Wed, Nov 21, 2001 at 09:37:43AM +, Simon Dick wrote:
> I get the following lock order reversal when playing mp3s on my Vaio
> PCG-F807K laptop:
> lock order reversal
> 1st 0xc399a840 pcm0:play:0 @
>/usr/src/sys/modules/sound/pcm/../../../dev/sound/pcm/dsp.c:936
> 2nd 0xc399ad80 pcm0 @
>
Is there a good , current description of how & why the various mutexe's
& conditon variables are used for somewhere?? I see what they are doing
in the code, but would like to get the big picture of why they are used
in one place (and not another type)..
Thanks,
Glenn G.
> I'm not agai
:>:This is due to the sx worker locks not using MTX_NOWITNESS with the pool
:>:mutex
:>:changes. It's not a problem though.
:>:
:>:--
:>:
:>:John Baldwin <[EMAIL PROTECTED]> <>< http://www.FreeBSD.org/~jhb/
:>
:> Would it make sense for me to add a new MTX flag that disables certain
:>
On 14-Nov-01 Matthew Dillon wrote:
>
>:On 14-Nov-01 David Wolfskill wrote:
>:> Built & booted today's -CURRENT; saw the following on the console & in
>:> /var/log/messages:
>:>
>:> Nov 14 08:59:25 localhost /boot/kernel/kernel: lock order reversal
>:> Nov 14 08:59:25 localhost /boot/kernel/kern
:On 14-Nov-01 David Wolfskill wrote:
:> Built & booted today's -CURRENT; saw the following on the console & in
:> /var/log/messages:
:>
:> Nov 14 08:59:25 localhost /boot/kernel/kernel: lock order reversal
:> Nov 14 08:59:25 localhost /boot/kernel/kernel: 1st 0xc0427980 dev_pager
:> create @ /us
On 14-Nov-01 David Wolfskill wrote:
> Built & booted today's -CURRENT; saw the following on the console & in
> /var/log/messages:
>
> Nov 14 08:59:25 localhost /boot/kernel/kernel: lock order reversal
> Nov 14 08:59:25 localhost /boot/kernel/kernel: 1st 0xc0427980 dev_pager
> create @ /usr/src/s
On Fri, Oct 19, 2001 at 01:02:50PM -0700, John Baldwin wrote:
>
> On 19-Oct-01 Wilko Bulte wrote:
> > Fresh -current kernel on an DS10 Alpha box:
>
> I have untested patches to fix this. Unfortunately they involve fixing the
> locking in teh clock code and I've only done i386 and alpha so far,
On 19-Oct-01 Wilko Bulte wrote:
> Fresh -current kernel on an DS10 Alpha box:
I have untested patches to fix this. Unfortunately they involve fixing the
locking in teh clock code and I've only done i386 and alpha so far, but the
same changes need to be replicated into all the otehr arch's. Alt
On 27-Jun-01 Makoto MATSUSHITA wrote:
>
> matusita> lock order reversal
> matusita> 1st 0xc5d2043c process lock @ ../../vm/vm_glue.c:487
> matusita> 2nd 0xc05a9ec0 lockmgr interlock @ ../../kern/kern_lock.c:239
>
> I've caught tracelog of this reversal, with debug.witness_ddb=1.
> Here's cons
matusita> lock order reversal
matusita> 1st 0xc5d2043c process lock @ ../../vm/vm_glue.c:487
matusita> 2nd 0xc05a9ec0 lockmgr interlock @ ../../kern/kern_lock.c:239
I've caught tracelog of this reversal, with debug.witness_ddb=1.
Here's console log:
lock order reversal
1st 0xc5e3cfdc process
I got same backtrace.
Additional daemons: syslogdlock order reversal
1st 0xc044fc80 mntvnode @ ../../ufs/ffs/ffs_vfsops.c:1007
2nd 0xcb1ef8ac vnode interlock @ ../../ufs/ffs/ffs_vfsops.c:1016
Debugger("witness_lock")
Stopped at Debugger+0x44: pushl %ebx
db> trace
Debugger(c038c22e) at
tacho> lock order reversal
tacho> 1st 0xc03f0140 mntvnode @ /usr/src/sys/ufs/ffs/ffs_vfsops.c:1007
tacho> 2nd 0xcaec972c vnode interlock @ /usr/src/sys/ufs/ffs/ffs_vfsops.c:1016
matusita> Exactly the same kernel message was here.
ddb trace output is as follows.
db> trace
Debugger(c02bd5ae) a
On 22-Jun-01 Makoto MATSUSHITA wrote:
>
> jhb> Can you turn on WITNESS_DDB in your kenrel config file (or set
> jhb> the debug.witness_ddb loader tunable/sysctl before you get this
> jhb> reversal) and get a backtrace from ddb?
>
> Yes; I turned 'debug.witness_ddb' on now. I'll send a ddb 'trac
jhb> Can you turn on WITNESS_DDB in your kenrel config file (or set
jhb> the debug.witness_ddb loader tunable/sysctl before you get this
jhb> reversal) and get a backtrace from ddb?
Yes; I turned 'debug.witness_ddb' on now. I'll send a ddb 'trace'
output if next time lock-order-reversal is happe
On 22-Jun-01 Makoto MATSUSHITA wrote:
>
> kuriyama> I got message below with WITNESS option. Is this safe to ignore?
>
> I've found another WITNESS message (5-current CVSuped Jun/18/2001):
>
> lock order reversal
> 1st 0xc5d2043c process lock @ ../../vm/vm_glue.c:487
> 2nd 0xc05a9ec0 lockmg
kuriyama> I got message below with WITNESS option. Is this safe to ignore?
I've found another WITNESS message (5-current CVSuped Jun/18/2001):
lock order reversal
1st 0xc5d2043c process lock @ ../../vm/vm_glue.c:487
2nd 0xc05a9ec0 lockmgr interlock @ ../../kern/kern_lock.c:239
***
Revision
On 21-Jun-01 Jun Kuriyama wrote:
>
> Another message is reported:
>
> lock order reversal
> 1st 0xc043ad20 dev_pager create @ ../../vm/device_pager.c:142
> 2nd 0xc0459840 vm @ ../../vm/vm_kern.c:186
Thanks, I'll try and look at this in a bit. I have a big set of locking
changes to the pager
tacho> lock order reversal
tacho> 1st 0xc03f0140 mntvnode @ /usr/src/sys/ufs/ffs/ffs_vfsops.c:1007
tacho> 2nd 0xcaec972c vnode interlock @ /usr/src/sys/ufs/ffs/ffs_vfsops.c:1016
Exactly the same kernel message was here. Revision ID is:
galtvalion % grep FreeBSD: src/sys/ufs/ffs/ffs_vnops.c
ff
Another message is reported:
lock order reversal
1st 0xc043ad20 dev_pager create @ ../../vm/device_pager.c:142
2nd 0xc0459840 vm @ ../../vm/vm_kern.c:186
--
Jun Kuriyama <[EMAIL PROTECTED]> // IMG SRC, Inc.
<[EMAIL PROTECTED]> // FreeBSD Project
To Unsubscribe: send mail to [E
On 28-Feb-01 Michael Reifenberger wrote:
> Hi,
> with -current sources (as of -now) I get during startup:
>
> lock order reversal
> 1st vnode interlock last acquired @ ../../kern/vfs_vnops.c:625
> 2nd 0xc0306840 mntvnode @ ../../ufs/ffs/ffs_vfsops.c:940
> 3rd 0xcbd20a0c vnode interlock @ ../.
On Tue, Jan 30, 2001 at 01:56:26PM +0200, John Hay wrote:
> Booting with a kernel built from today's source (with devfs also in),
> I see this lock order reversal message:
>
> ###
> Routing daemons:.
> Doing IPv6 network setup:add net :::0.0.0.0: gateway ::1
>
76 matches
Mail list logo
