I've never figured out how to tell important lock order reversal
notices from unimportant ones. So I mostly report only unfamiliar
ones. (But I normally do not do poudriere bulk builds with a
debug kernel in use.)
During a poudriere bulk that is using USE_TMPFS=all it reported:
lock order
On 2020-Dec-19, at 03:09, Hans Petter Selasky wrote:
> Please test:
>
> https://svnweb.freebsd.org/changeset/base/368799
> https://svnweb.freebsd.org/changeset/base/368801
>
> --HPS
I grabbed a debug -r368803 kernel from artifacts (first arm64
snapshot available containing the above 2
Please test:
https://svnweb.freebsd.org/changeset/base/368799
https://svnweb.freebsd.org/changeset/base/368801
--HPS
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail
[I managed to not cc the primary person that I intended but to cc the secondary
person.
So this resend just adds jmg and removes hps.]
On 2020-Dec-18, at 22:27, Mark Millard wrote:
> The following is from head -r368500's artifact kernel from:
>
>
The following is from head -r368500's artifact kernel from:
https://artifact.ci.freebsd.org/snapshot/13.0-CURRENT/r368500/arm64/aarch64/kernel.txz
but the same sort of material showed for -r368000 .
(I was attempting a bisect for a different issue but
the debug kernels did not fail for what I
On a recent CURRENT bos acting as poudriere host, we face after a crash
under heavy load and extensive swap usage now this lock order reversal
warning on the console:
lock order reversal:
1st 0xf8007bdd9e00 zfs (zfs, lockmgr) @
/usr/src/sys/kern/vfs_mount.c:1018 2nd 0xf8034abfc070 devfs
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
___
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 re
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
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
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 ar
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
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?
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 0xf8010cd37250 devfs (devfs) @
/usr/src-13/sys/kern
On 2020-Apr-30, at 18:30, Mark Millard wrote:
> Using artifact.ci's head -r360311 debug-kernel materials:
>
> https://artifact.ci.freebsd.org/snapshot/head/r360311/powerpc/powerpc/kernel*.txz
>
> I got the following notice:
>
> lock order reversal:
> 1st 0x1cbb68
Using artifact.ci's head -r360311 debug-kernel materials:
https://artifact.ci.freebsd.org/snapshot/head/r360311/powerpc/powerpc/kernel*.txz
I got the following notice:
lock order reversal:
1st 0x1cbb680 PROC (UMA zone) @ /usr/src/sys/vm/uma_core.c:4387
2nd 0x113c99c kernelpmap (kernelpmap
On Mon, 26 Feb 2018 08:42:14 +0200 "Andriy Gapon" <a...@freebsd.org> 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
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:
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 order reversal:
1st 0xfd0003ec17e8 ufs (ufs
Mar 24 14:25:16 kernel: lock order reversal:
Mar 24 14:25:16 kernel: 1st 0xc09cf6dc ufs (ufs) @
/usr/src/sys/kern/vfs_mount.c:1277
Mar 24 14:25:16 kernel: 2nd 0xc0100a30 devfs (devfs) @
/usr/src/sys/ufs/ffs/ffs_softdep.c:1908
Mar 24 14:25:16 kernel: stack backtrace:
Mar 24 14:25:16 kernel
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
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:
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"
#0 #16 follow:
jotted down :
1. ufs /usr/src/sys/kern/vfs_syscalls.c:3364
2. bufwait /usr/src/sys/ufs/ffs/ffs_vnops.c:280
3. ufs /usr/src/sys/kern/vfs_subr.c:2600
[ took roxterm out of the xinitrc, system stable seems more than yesterday...
too
early to tell, which is/was a 2nd issue... put
Cc: freebsd-current@freebsd.org
Subject: Re: New Lock Order Reversal in 12.0?
On Mon, Jan 09, 2017 at 02:31:39AM +, Anindya Mukherjee wrote:
> Hi Ben,
>
> Thanks for your reply, and yes, I did notice #238. I should say at this point
> that I'm a newbie when it comes to kernel
On Mon, Jan 09, 2017 at 02:31:39AM +, Anindya Mukherjee wrote:
> Hi Ben,
>
> Thanks for your reply, and yes, I did notice #238. I should say at this point
> that I'm a newbie when it comes to kernel code and am trying to learn about
> it (hence current).
Understood. It's good that you are
From: Benjamin Kaduk [ka...@mit.edu]
Sent: January 8, 2017 4:47 PM
To: Anindya Mukherjee
Cc: freebsd-current@freebsd.org
Subject: Re: New Lock Order Reversal in 12.0?
On Mon, Jan 09, 2017 at 12:32:28AM +, Anindya Mukherjee wrote:
> Hi, I'm running 12.0-current and noticed a LOR mess
t; root@triskelion:~ # uname -a
> FreeBSD triskelion 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r311461: Thu Jan 5
> 22:46:38 UTC 2017
> r...@releng3.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64
> root@triskelion:~ # freebsd-version
> 12.0-CURRENT
>
>
> WIT
: Thu Jan 5
22:46:38 UTC 2017 r...@releng3.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC
amd64
root@triskelion:~ # freebsd-version
12.0-CURRENT
WITNESS report:
lock order reversal:
1st 0xf8002e8049a0 ufs (ufs) @ /usr/src/sys/kern/vfs_subr.c:2598
2nd 0xfe01e7ce9b40 bufwait (bufwait
eu> 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/s
On 05/16/16 00:44, Bjoern A. Zeeb wrote:
On 15 May 2016, at 07:44 , Kurt Jaeger <li...@opsec.eu> 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_
> On 15 May 2016, at 07:44 , Kurt Jaeger <li...@opsec.eu> wrote:
>
> Hi!
>
>> I am seeing 'lock order reversal' errors during boot on 11-CURRENT -
>> r298793. A sample error:
>>
>> lock order reversal:
>> 1st 0xf8011280d068 ufs (
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/ff
Greetings,
My first post here so please be gentle.
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
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.imgu
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 it could be a sign of a deadlock:
https://www.f
Hi
On r278909 (and probably earlier) I get the following when I run
poweroff (retyped from a video of it I had to record, since it
disappears very quickly):
Syncing disks, vnodes remaining...4 1 0 0 done
All buffers synced.
lock order reversal:
1st 0xf80014d4d060 ufs (ufs) 0 /usr/src/sys
On Wed, Feb 18, 2015 at 9:53 AM, Damjan Jovanovic damjan@gmail.com wrote:
Hi
On r278909 (and probably earlier) I get the following when I run
poweroff (retyped from a video of it I had to record, since it
disappears very quickly):
Hi Damjan,
This is a known LOR.
Thanks!
On Sat, 19 Apr 2014, R. Tyler Croy wrote:
I've noticed this as of late on my i386 -CURRENT Thinkpad T43 when I perform
some file operations, but an exact reproduction case I've not yet stumbled
upon:
Apr 20 01:29:32 lemon kernel: lock order reversal:
Apr 20 01:29:32 lemon kernel: 1st
I've noticed this as of late on my i386 -CURRENT Thinkpad T43 when I
perform some file operations, but an exact reproduction case I've not
yet stumbled upon:
Apr 20 01:29:32 lemon kernel: lock order reversal:
Apr 20 01:29:32 lemon kernel: 1st 0xc5832358 bufwait (bufwait) @
/usr/home/tyler
Hi,
these represent machine lockups, if not false positives.
http://www.freebsd.org/cgi/query-pr.cgi?pr=182139cat=
jb
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail
I got these messages on 10 head, rev.254235, during 'filesystem full' condition.
Yuri
= log =
lock order reversal:
1st 0xff80f7432470 bufwait (bufwait) @ /usr/src/sys/kern/vfs_bio.c:3054
2nd 0xfe00075b5600 dirhash (dirhash) @
/usr/src/sys/ufs/ufs/ufs_dirhash.c:284
KDB: stack
WITNESS.
Thanks,
--
Davide
On Mon, 19 Aug 2013, Yuri wrote:
I got these messages on 10 head, rev.254235, during 'filesystem full'
condition.
Yuri
= log =
lock order reversal:
1st 0xff80f7432470 bufwait (bufwait) @ /usr/src/sys/kern/vfs_bio.c:3054
2nd 0xfe00075b5600 dirhash
Hello-
I am running 10.0-CURRENT #0 r252098 on a beaglebone and I am getting the
occasional LOR when reading/writing in an nfs mount
lock order reversal:
1st 0xc1c0a150 newnfs (newnfs) @ /usr/src/sys/kern/vfs_syscalls.c:4064
2nd 0xc6a5e278 bufwait (bufwait) @ /usr/src/sys/kern/vfs_bio.c:2311
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
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 backtrace:
db_trace_self_wrapper
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
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
2nd
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:2158
KDB
BF freebsd9b3# mount_smbfs -I smbhost -U xxx -W domain //smbhost/xxx /mnt
BF Password:
BF mount_smbfs: unable to open connection: syserr = No such file or directory
BF and displays the following kernel messages:
BF smb_co_lock: recursive lock for object 1
BF lock order reversal:
BF 1st
Hello !
After upgrading my system from 8.2 to 9.0-BETA3 I now see this error message
during boot :
lock order reversal:
1st 0xc536e8d8 ufs (ufs) @ /usr/src/sys/kern/vfs_subr.c:2134
2nd 0xde0077b4 bufwait (bufwait) @ /usr/src/sys/ufs/ffs/ffs_vnops.c:260
3rd 0xc7b088d8 ufs (ufs) @ /usr/src/sys
Hello !
Just did a new build of world kernel, and the error message have changed a
bit :
lock order reversal:
1st 0xddf0c4cc bufwait (bufwait) @ /usr/src/sys/kern/vfs_bio.c:2658
2nd 0xc4996200 dirhash (dirhash) @ /usr/src/sys/ufs/ufs/ufs_dirhash.c:284
KDB: stack backtrace
On Sat, 8 Oct 2011, Roar Pettersen wrote:
Hello !
Just did a new build of world kernel, and the error message have changed a
bit :
lock order reversal:
1st 0xddf0c4cc bufwait (bufwait) @ /usr/src/sys/kern/vfs_bio.c:2658
2nd 0xc4996200 dirhash (dirhash) @ /usr/src/sys/ufs/ufs/ufs_dirhash.c
/mnt
Password:
mount_smbfs: unable to open connection: syserr = No such file or directory
and displays the following kernel messages:
smb_co_lock: recursive lock for object 1
lock order reversal:
1st 0xc2ef4608 smb_vc (smb_vc) @
/usr/src/sys/modules/smbfs/../../netsmb/smb_conn.c:325
2nd
I install current on last week
I have some messages in dmesg -a:
lock order reversal:
1st 0xc81ba278 ufs (ufs) @ /usr/src/sys/ufs/ffs/ffs_snapshot.c:425
2nd 0xe0f566d0 bufwait (bufwait) @ /usr/src/sys/kern/vfs_bio.c:2658
3rd 0xc7d89168 ufs (ufs) @ /usr/src/sys/ufs/ffs/ffs_snapshot.c:546
KDB
on last week
I have some messages in dmesg -a:
lock order reversal:
1st 0xc81ba278 ufs (ufs) @ /usr/src/sys/ufs/ffs/ffs_snapshot.c:425
2nd 0xe0f566d0 bufwait (bufwait) @ /usr/src/sys/kern/vfs_bio.c:2658
3rd 0xc7d89168 ufs (ufs) @ /usr/src/sys/ufs/ffs/ffs_snapshot.c:546
KDB: stack backtrace
Denisov m...@vadimdenisov.ru wrote:
I install current on last week
I have some messages in dmesg -a:
lock order reversal:
1st 0xc81ba278 ufs (ufs) @ /usr/src/sys/ufs/ffs/ffs_snapshot.c:425
2nd 0xe0f566d0 bufwait (bufwait) @ /usr/src/sys/kern/vfs_bio.c:2658
3rd 0xc7d89168 ufs (ufs) @ /usr/src/sys
A Dmesg.TXT is attached having a lock order reversal message .
Thank you very much .
Mehmet Erol Sanliturk
Copyright (c) 1992-2010 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights
On Dec 7, 2010, at 12:26 AM, Mehmet Erol Sanliturk m.e.sanlit...@gmail.com
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
Den 07/12/2010 kl. 10.20 skrev Garrett Cooper:
On Dec 7, 2010, at 12:26 AM, Mehmet Erol Sanliturk m.e.sanlit...@gmail.com
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
2010/12/7 Erik Cederstrand e...@cederstrand.dk:
Den 07/12/2010 kl. 10.20 skrev Garrett Cooper:
On Dec 7, 2010, at 12:26 AM, Mehmet Erol Sanliturk m.e.sanlit...@gmail.com
wrote:
A Dmesg.TXT is attached having a lock order reversal .
The mount LOR is well known.
I see
On 12/7/10 3:41 AM, Attilio Rao wrote:
2010/12/7 Erik Cederstrande...@cederstrand.dk:
Den 07/12/2010 kl. 10.20 skrev Garrett Cooper:
On Dec 7, 2010, at 12:26 AM, Mehmet Erol Sanliturkm.e.sanlit...@gmail.com
wrote:
A Dmesg.TXT is attached having a lock order reversal .
The mount LOR
:
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 of the most-reported errors on CURRENT (and it's certainly a
loud one), but I think a lot of people waste time
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 0xc343f000 dirhash (dirhash) @
/data/builder/c13-2010-06-07
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
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 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) @
/data/builder
getting the following LOR at boot and wonder if it is
related?
lock order reversal:
1st 0xc0424d28 pf task mtx (pf task mtx) @
/usr/src/sys/contrib/pf/net/pf.c:6929
2nd 0xf800011954f8 radix node head (radix node head) @
/usr/src/sys/net/route.c:360
KDB: stack backtrace:
_witness_debugger
ruleset has worked fine for me for several years on this and other
systems. I'm getting the following LOR at boot and wonder if it is
related?
lock order reversal:
1st 0xc0424d28 pf task mtx (pf task mtx) @
/usr/src/sys/contrib/pf/net/pf.c:6929
2nd 0xf800011954f8 radix node head (radix
management hardware on board which might interfere.
Can this flags=0 be made the default or would that interfere with USB
keyboard and headless configurations?
2. LOCK ORDER REVERSAL
I let the machine buildworld, build a kernel and cvsup ports+doc at
the same time through screen. Both buildworld
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
Is this a known issue on 5.2 beta 6 sup'ed nov 29/03?
lock order reveral
1st 0xc2121b58 vm object (vm object) @ /usr/src/sys/vm/swap_pager.c:1323
2nd 0xc0987b00 swap_pager swhash (swap_pager swhash) @
/usr/src/sys/vm/swap_pager.c:1838
3rd 0xc1036948 vm object (vm object) @
Checked the archive and didn't see this one listed yet:
lock order reversal
1st 0xc4047134 filedesc structure (filedesc structure)[EMAIL
PROTECTED]/usr/src/sys/kern/sys_
generic.c:896
2nd 0xc0956a80 Giant (Giant)[EMAIL PROTECTED]/usr/src/sys/fs/specfs/spec_vnops.c:377
Stack backtrace
On Fri, Nov 28, 2003 at 04:37:49PM -0500, Jesse Guardiani wrote:
Checked the archive and didn't see this one listed yet:
lock order reversal
?1st?0xc4047134?filedesc?structure?(filedesc?structure)[EMAIL
PROTECTED]/usr/src/sys/kern/sys_
generic.c:896
?2nd?0xc0956a80?Giant?(Giant)[EMAIL
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/sys
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 map (system map) @ /usr/src/sys/vm/vm_map.c:2210
Stack backtrace
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 map (system
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 lock (UMA lock
:01'
# ngctl shutdown vif0:
lock order reversal
1st 0xc0765d8c turnstile chain (turnstile chain) @
/usr/src/sys/kern/subr_turnstile.c:370
2nd 0xc079a500 sio (sio) @ /usr/src/sys/dev/sio/sio.c:3203
Stack backtrace:
backtrace(c070794e,c079a500,c07502c0,c07502c0,c0719757) at backtrace+0x17
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/sys/vm/vm_map.c:2210
Stack backtrace:
lock order reversal
1st
Got this earlier tonight on a box of mine... was testing a possible upgrade
from 4.8 to 5.1 on a box to act as my router...
dc0: promiscuous mode enabled
Oct 26 20:32:37 router kernel: dc0: promiscuous mode enabled
lock order reversal
1st 0xc05a4600 bpf global lock (bpf global lock) @
/usr/src
Hi,
I just cvsup'd and noticed the following:
Starting sshd.
lock order reversal
1st 0xc2ee3998 inp (inp) @ /usr/src/sys/netinet/udp_usrreq.c:1042
2nd 0xc094876c div (div) @ /usr/src/sys/netinet/ip_divert.c:225
Stack backtrace:
backtrace(c08643de,c094876c,c087b2de,c087b2de,c086b1c6
Hi,
I am seeing an occasional kernel panic. I think it
is related to natd and ip_divert
Fatal trap 3: breakpoint instruction fault while in kernel mode
instruction pointer = 0x8:0xc07e6c24
stack pointer = 0x10:0xce7026c4
frame pointer = 0x10:0xce7026d0
code segment
I've got a lock order reversal.
#uname -a
FreeBSD barleycoren.oikumene.gcd.org 5.1-CURRENT FreeBSD 5.1-CURRENT #1:
Tue Sep 23 21:37:42 JST 2003
[EMAIL PROTECTED]:/build/usr/src/sys/BARLEYCOREN i386
Oct 11 18:14:53 barleycoren kernel: 1st 0xc082f060 system map (system map)
@ /usr/src/sys/vm
Has anyone seen this before?
Sep 5 15:06:02 rdaver kernel: lock order reversal
Sep 5 15:06:02 rdaver kernel: 1st 0xcf33ba34 filedesc structure (filedesc structure)
@ kern/sys_generic.c:895
Sep 5 15:06:02 rdaver kernel: 2nd 0xc054c640 Giant (Giant) @
fs/specfs/spec_vnops.c:372
I've been
Dear colleagues,
===
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
Stack backtrace:
backtrace(c04eacec,c082f110,c04fb2fa,c04fb2fa,c04fb1a2) at backtrace+0x17
witness_lock(c082f110,8,c04fb1a2,145,c082f0b0
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
Is the following a known problem?
(occured while running python2.3 using kse)
lock order reversal
1st 0xc03c3c40 smp rendezvous (smp rendezvous) @ /usr/src/sys/kern/subr_smp.c:3
13
2nd 0xc03c00c0 sched lock (sched lock) @ /usr/src/sys/i386/i386/sys_machdep.c:2
92
Stack backtrace:
backtrace
Hi,
under a recent -CURRENT I get this:
---
lock order reversal
1st 0xc2e475c8 vm object (vm object) @ /usr/src/sys/vm/vm_object.c:432
2nd 0xc082f110 system map (system map) @ /usr/src/sys/vm/vm_kern.c:328
Stack backtrace
Has anyone come across this before?
dc0: promiscuous mode enabled
Jun 20 09:56:15 router kernel: dc0: promiscuous mode enabled
lock order reversal
1st 0xc05a0100 bpf global lock (bpf global lock) @
/usr/src/sys/net/bpf.c:375
2nd 0xc1f5d7bc dc0 (network driver) @ /usr/src/sys/pci/if_dc.c:3543
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.74
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 (network
-current/src/sys/pci/if_tl.c:1146
malloc() of PROC with the following non-sleepablelocks held:
exclusive sleep mutex tl0 (network driver) r = 0 (0xc4017aa8) locked @
/usr/src/5-current/src/sys/pci/if_tl.c:1146
lock order reversal
1st 0xc4017aa8 tl0 (network driver) @ /usr/src/5-current/src/sys/pci
Good day ladies and gents
Cvsupping and rebuilding a 5.0 current box to release Monday
resulted in the following curiousness:
lock order reversal
1st 0xc1190068 process lock (process lock) @
/usr/src/sys/kern/kern_descrip.c:2
112
2nd 0xc11ac934 filedesc structure (filedesc structure
On Sat, Feb 15, 2003 at 11:30:09AM +1030, Greg 'groggy' Lehey wrote:
It is becoming increasingly clear to me that the majority of FreeBSD
developers don't really care if their code works, as long as they get
the credit (and / or paycheck) for committing it.
I think that's unnecessarily
Thanks to Paul Saab's work on fixing twe(4) I was able to get a
crash dump from my box and figure out why my filedesc locking patch
was panic'ing. kevent_close was dereferencing the proc's filedesc
pointer during close, that doesn't work so well when you need to
do what I had to do. :)
The gist
At 3:04 AM -0800 2/14/03, Alfred Perlstein wrote:
* Dag-Erling Smorgrav [EMAIL PROTECTED] [030214 02:52] wrote:
Alfred Perlstein [EMAIL PROTECTED] writes:
Thanks to Paul Saab's work on fixing twe(4) I was able to
get a crash dump from my box
How? I can't get a crash dump in
Alfred Perlstein [EMAIL PROTECTED] writes:
Thanks to Paul Saab's work on fixing twe(4) I was able to get a
crash dump from my box
How? I can't get a crash dump in -CURRENT, even on a plain jane ata
disk, and it's been months since I last managed to get one.
DES
--
Dag-Erling Smorgrav -
* Dag-Erling Smorgrav [EMAIL PROTECTED] [030214 02:52] wrote:
Alfred Perlstein [EMAIL PROTECTED] writes:
Thanks to Paul Saab's work on fixing twe(4) I was able to get a
crash dump from my box
How? I can't get a crash dump in -CURRENT, even on a plain jane ata
disk, and it's been months
1 - 100 of 235 matches
Mail list logo