Alfred Perlstein [EMAIL PROTECTED] writes:
What exactly is broken about dumps for you on ata?
Well, after you told me that call dumpsys is no longer kosher (when
did that happen, and where was it documented?), I tried 'call doadump':
# Debugger(manual escape to debugger)
Stopped at
On Fri, Feb 14, 2003 at 12:23:48PM +0100, Dag-Erling Smorgrav wrote:
What exactly is broken about dumps for you on ata?
Well, after you told me that call dumpsys is no longer kosher (when
did that happen, and where was it documented?), I tried 'call doadump':
# Debugger(manual escape to
* Dag-Erling Smorgrav [EMAIL PROTECTED] [030214 03:23] wrote:
Alfred Perlstein [EMAIL PROTECTED] writes:
What exactly is broken about dumps for you on ata?
Well, after you told me that call dumpsys is no longer kosher (when
did that happen, and where was it documented?), I tried 'call
On Fri, 2003-02-14 at 21:53, Dag-Erling Smorgrav wrote:
Alfred Perlstein [EMAIL PROTECTED] writes:
What exactly is broken about dumps for you on ata?
Well, after you told me that call dumpsys is no longer kosher (when
did that happen, and where was it documented?), I tried 'call doadump':
In message [EMAIL PROTECTED], Dag-Erling Smorgrav writes:
Makes me want to get my Norwegian Sword [tm] and make a short trip to
Denmark.
I my be reading my email out of order here, but I guess you changed
your mind and tried to bury use with boatloads of useless asterix
('*') instead ? :-)
It
On Friday, 14 February 2003 at 12:23:48 +0100, Dag-Erling Smorgrav wrote:
Alfred Perlstein [EMAIL PROTECTED] writes:
What exactly is broken about dumps for you on ata?
Well, after you told me that call dumpsys is no longer kosher (when
did that happen, and where was it documented?), I tried
cd0: 33.000MB/s transfers
cd0: Attempt to query device size failed: NOT READY, Medium not present - tray open
lock order reversal
1st 0xc6998a54 process lock (process lock) @ /usr/src/sys/kern/kern_descrip.c:2104
2nd 0xc6944234 filedesc structure (filedesc structure) @
/usr/src/sys/kern
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
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 also
Hi,
I am seeingthis from a kernel cvsup'd a few days ago:
login: lock order reversal
1st 0xc060ad20 arp mutex (arp mutex) @ /usr/src/sys/netinet/if_ether.c:151
2nd 0xc339097c radix node head (radix node head) @ /usr/src/sys/net/route.c:549
Thanks.
--
Craig Rodrigues
http
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
lock order reversal
1st 0xc03bbde0 arp mutex (arp mutex) @ ../../../netinet/if_ether.c:151
2nd 0xc6149e7c radix node head (radix node head) @ ../../../net/route.c:549
Debugger(witness_lock)
Stopped at Debugger+0x55: xchgl %ebx,in_Debugger.0
db trace
Debugger(c031e895,c6149e7c,c033b2a0
Fri, Dec 06, 2002 at 23:07:36, netch (Valentin Nechayev) wrote about no psm
interrupt; lock order reversal:
VN 5.0-RC of 2002.12.05.12.00.00-UTC
VN Bigger problem that it can't obtain interrupts from PS/2 mouse,
VN hence mouse fails to work. systat shows no int 12 issued at all.
ACPI
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: 2nd
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 filedesc
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
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
struc\
ture) @ /usr/src/sys/kern/kern_descrip.c:2106
The kernel is only about 40 mins
Hello...
tl0: device timeout
lock order reversal
1st 0xc0331020 ifnet (ifnet) @ /usr/src/sys/net/if.c:1181
2nd 0xc2576ab8 tl0 (network driver) @ /usr/src/sys/pci/if_tl.c:2067
Driver is loaded via kld module from /boot/loader.conf.
To get interface up I need to unload and load module again
Hi all,
In a cursory search of the mailing list archives I didn't find this LOR
reported. I apologize if it's a repeat.
lock order reversal
1st 0xc0b9e800 pcm0:play:0 (pcm channel) @ /usr/src/sys/dev/sound/pcm/dsp.c:150
2nd 0xc051ebe0 Giant (Giant) @ /usr/src/sys/kern/kern_synch.c:314
dmesg
Just had this lock order reversal on a late-november kernel. Haven't seen
it mentioned before.
Dec 16 19:07:15 epsilon kernel: rl0: promiscuous mode enabled
Dec 16 19:07:15 epsilon kernel: lock order reversal
Dec 16 19:07:15 epsilon kernel: 1st 0xc0429cc0 bpf global lock (bpf global lock
On Friday, 6 December 2002 at 15:27:29 -0600, Dan Nelson wrote:
I haven't seen this one reported yet.
FreeBSD dan.emsphone.com 5.0-RC FreeBSD 5.0-RC #228: Thu Dec 5 17:28:33 CST 2002
[EMAIL PROTECTED]:/usr/src/sys/i386/compile/DANSMP i386
lock order reversal
1st 0xc2d454b0 vnode
5.0-RC of 2002.12.05.12.00.00-UTC
Lock order reversal without panic:
lock order reversal
1st 0xc2e30708 vnode interlock (vnode interlock) @
/var/HEAD/src/sys/kern/vfs_subr.c:939
2nd 0xc033c3c0 vm page queue mutex (vm page queue mutex) @
/var/HEAD/src/sys/vm/vm_kern.c:424
Bigger problem
I got this overnight on the gohan cluster. Machine is still in DDB if
further debugging is necessary.
Kris
login: lock order reversal
1st 0xc577212c vnode interlock (vnode interlock) @
/local0/src-client/sys/kern/vfs_subr.c:939
2nd 0xc046a560 vm page queue mutex (vm page queue mutex
I haven't seen this one reported yet.
FreeBSD dan.emsphone.com 5.0-RC FreeBSD 5.0-RC #228: Thu Dec 5 17:28:33 CST 2002
[EMAIL PROTECTED]:/usr/src/sys/i386/compile/DANSMP i386
lock order reversal
1st 0xc2d454b0 vnode interlock (vnode interlock) @ ../../../ufs/ffs/ffs_snapshot.c:1876
2nd
Hello,
while removing all local packages related to XFree86, I've had the following
message :
lock order reversal
1st 0xc49eaa68 vnode interlock (vnode interlock)
@/files3/src/sys/nfsclient/nfs_vnops.c:2629
2nd 0xc05398a0 vm page queue mutex (vm page queue mutex) @
/files3/src/sys/vm
PROTECTED] Network Associates Laboratories
On Sun, 17 Nov 2002, Joel M. Baldwin wrote:
running dnet on a SMP kernel causes the kernel to panic.
lock order reversal
1st 0xc2c803e8 process lock (process lock) @
../../../kern/kern_fork.c:571
2nd 0xc03cfce0 proctree (proctree
Lars Eggert wrote:
lock order reversal
1st 0xc6f47a68 vnode interlock (vnode interlock) @
/usr/src/sys/nfsclient/nfs_vnops.c:2629
2nd 0xc04b8640 vm page queue mutex (vm page queue mutex) @
/usr/src/sys/vm/vm_kern.c:424
Still present on yesterday's -current.
Lars
--
Lars Eggert [EMAIL
Alex Zepeda wrote:
I see this on a fairly regular basis (at least once per 24 hour period):
lock order reversal
1st 0xc0490ca0 spechash (spechash) @ ../../../kern/vfs_subr.c:2748
2nd 0xc1ed2818 vnode interlock (vnode interlock) @
../../../kern/vfs_subr.c:2751
Dunno if it's any help
lock order reversal
1st 0xc6f47a68 vnode interlock (vnode interlock) @
/usr/src/sys/nfsclient/nfs_vnops.c:2629
2nd 0xc04b8640 vm page queue mutex (vm page queue mutex) @
/usr/src/sys/vm/vm_kern.c:424
Debugger(witness_lock)
Stopped at Debugger+0x5a: xchgl %ebx,in_Debugger.0
db trace
lock order reversal
1st 0xc791bc00 pipe mutex (pipe mutex) @ /usr/src/sys/kern/sys_pipe.c:465
2nd 0xc04974e0 sigio lock (sigio lock) @ /usr/src/sys/kern/kern_sig.c:2156
Debugger(witness_lock)
Stopped at Debugger+0x5a: xchgl %ebx,in_Debugger.0
db trace
Debugger(c0440ebb,c04974e0
/uma_core.c:1307: could sleep with rl0 locked from
../../../pci/if_rl.c:872
lock order reversal
1st 0xc0f3b1c0 rl0 (network driver) @ ../../../pci/if_rl.c:872
2nd 0xc038a0e0 allproc (allproc) @ ../../../kern/kern_fork.c:316
../../../vm/uma_core.c:1307: could sleep with rl0 locked from
../../../pci
How recent is your kernel? I thought I'd fixed this in recent current
(at least the could sleep with rl0 part).
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
today's source code
David
- Original Message -
From: M. Warner Losh [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Tuesday, October 22, 2002 10:20 AM
Subject: Re: rl driver lock order reversal
How recent is your kernel? I thought I'd fixed this in recent current
In message: 00bd01c27972$5eea20f0$ef01a8c0@davidwnt
David Xu [EMAIL PROTECTED] writes:
: today's source code
Looks like I've not committed it. :-(. Also looks like p4 told me
there were no diffs for reasons unknown...
This removes the lock around the attach routine. It isn't
On 21 Oct, Lars Eggert wrote:
lock order reversal
1st 0xc791bc00 pipe mutex (pipe mutex) @ /usr/src/sys/kern/sys_pipe.c:465
2nd 0xc04974e0 sigio lock (sigio lock) @ /usr/src/sys/kern/kern_sig.c:2156
I've been complaining about that one for ages. I think I know how I
want to attack
- Original Message -
From: M. Warner Losh [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Tuesday, October 22, 2002 10:40 AM
Subject: Re: rl driver lock order reversal
In message: 00bd01c27972$5eea20f0$ef01a8c0@davidwnt
David Xu [EMAIL PROTECTED] writes
On Mon, 21 Oct 2002, Lars Eggert wrote:
lock order reversal
1st 0xc791bc00 pipe mutex (pipe mutex) @ /usr/src/sys/kern/sys_pipe.c:465
2nd 0xc04974e0 sigio lock (sigio lock) @ /usr/src/sys/kern/kern_sig.c:2156
It strikes me that, for better or for worse, the reported reversal is
the right
On 21 Oct, Robert Watson wrote:
On Mon, 21 Oct 2002, Lars Eggert wrote:
lock order reversal
1st 0xc791bc00 pipe mutex (pipe mutex) @ /usr/src/sys/kern/sys_pipe.c:465
2nd 0xc04974e0 sigio lock (sigio lock) @ /usr/src/sys/kern/kern_sig.c:2156
It strikes me that, for better
Just got this from a 17th October kernel, it does not look like it's been
reported before.
lock order reversal
1st 0xc21f5250 vnode interlock (vnode interlock) @ /usr/src/sys/kern/vfs_subr.c:945
2nd 0xc0409e80 vm page queue mutex (vm page queue mutex) @
/usr/src/sys/vm/vm_kern.c:424
Gavin
With a kernel from late 2 Oct 2002:
lock order reversal
1st 0xc048db40 spechash (spechash) @ ../../../kern/vfs_subr.c:2743
2nd 0xc1efede0 vnode interlock (vnode interlock) @
../../../kern/vfs_subr.c:2746
- alex
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current
Hi!
I always get a bunch of .. could sleep with... and lock order reversal messages.
There appear in various parts of the kernel.The locks: pcm, xl, drm. The reversals:
spec_vnops, vfs_subr, if_xl, sys_pipe. And this was only a quick glance through the
logs. IIRC these are considered harmful
Hi,
I recently did a tcpdump on my xl0 interface (Etherlink XL)
on my -current setup.
This message showed up in the console:
lock order reversal
1st 0xc0553780 bpf global lock (bpf global lock) @ /usr/src/sys/net/bpf.c:378
2nd 0xc129dbd4 xl0 (network driver) @ /usr/src/sys/pci/if_xl.c:2905
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.
GDB
../../../vm/uma_core.c:1332: could sleep with process lock locked from
../../../kern/kern_exec.c:360
lock order reversal
1st 0xc25bb160 process lock (process lock) @
../../../kern/kern_exec.c:360
2nd 0xc03eee00 filelist lock (filelist lock) @
../../../kern/kern_descrip.c:1113
../../../vm
displayed after /etc/motd and immediately after the serial
console gets the panic:
Starting background filesystem checks
Mon Jul 22 18:57:46 EDT 2002
lock order reversal
1st 0xc034aee0 sysctl sysctllock (sysctl sysctllock) @
/usr/src/sys/kern/kern_sysctl.c:1181
2nd 0xc03179e0 Giant (Giant) @ /usr
On 7 Jul, Don Lewis wrote:
This error showed up in my logs this morning while I was building some
ports on a uni-processor box. I'm running a version of -current from
July 7 about 1 AM PDT.
Jul 7 07:47:09 scratch kernel: lock order reversal
Jul 7 07:47:09 scratch kernel: 1st 0xcabf7980
On 11 Jul, Don Lewis wrote:
On 7 Jul, Don Lewis wrote:
Jul 7 07:47:09 scratch kernel: lock order reversal
Jul 7 07:47:09 scratch kernel: 1st 0xcabf7980 pipe mutex (pipe mutex) @
/usr/src/sys/kern/sys_pipe.c:451
Jul 7 07:47:09 scratch kernel: 2nd 0xc0474300 sigio lock (sigio lock
This error showed up in my logs this morning while I was building some
ports on a uni-processor box. I'm running a version of -current from
July 7 about 1 AM PDT.
Jul 7 07:47:09 scratch kernel: lock order reversal
Jul 7 07:47:09 scratch kernel: 1st 0xcabf7980 pipe mutex (pipe mutex) @
/usr
lock order reversal
1st 0xc9c48d98 sis0 (network driver) @ /usr.current/src/sys/pci/if_sis.c:804
2nd 0xc0328600 allproc (allproc) @ /usr.current/src/sys/kern/kern_fork.c:309
Is this a problem ?
-Arun
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current
I just got this in dmesg:
lock order reversal
1st 0xdaa8ce2c process lock (process lock) @ /usr/src/sys/kern/kern_exec.c:316
2nd 0xc0424d60 filelist lock (filelist lock) @ /usr/src/sys/kern/kern_descrip.c:1112
What other information is needed to debug this?
To Unsubscribe: send mail
Here is a message of lock order reversal (just fresh current):
lock order reversal
1st 0xe853eb18 process lock (process lock) @ ../../../kern/kern_exec.c:316
2nd 0xc0324400 filelist lock (filelist lock) @ ../../../kern/kern_descrip.c:1112
--
Jun Kuriyama [EMAIL PROTECTED] // IMG SRC, Inc
With yesterday's -current:
lock order reversal
1st 0xcc5987a4 DIRHASH (UMA zone) @
/usr/Local/src-current/sys/vm/uma_core.c:297
2nd 0xc76c2224 PCPU 256 (UMA cpu) @
/usr/Local/src-current/sys/vm/uma_core.c:1630
FYI.
--
We have known freedom's price. We have shown freedom's power
On Sun, 5 May 2002, Doug Barton wrote:
With yesterday's -current:
lock order reversal
1st 0xcc5987a4 DIRHASH (UMA zone) @
/usr/Local/src-current/sys/vm/uma_core.c:297
2nd 0xc76c2224 PCPU 256 (UMA cpu) @
/usr/Local/src-current/sys/vm/uma_core.c:1630
FYI.
Here's another from
On Sun, 5 May 2002, Doug Barton wrote:
With yesterday's -current:
lock order reversal
1st 0xcc5987a4 DIRHASH (UMA zone) @
/usr/Local/src-current/sys/vm/uma_core.c:297
2nd 0xc76c2224 PCPU 256 (UMA cpu) @
/usr/Local/src-current/sys/vm/uma_core.c:1630
I see the same one when I run
I'm seeing this reversal:
lock order reversal
1st 0xc8b01664 DIRHASH (UMA zone) @ ../../../vm/uma_core.c:527
2nd 0xc042a724 PCPU KMAP ENTRY (UMA cpu) @ ../../../vm/uma_core.c:1301
Is this known?
--
Jonathan Mini [EMAIL PROTECTED]
http://www.haikugeek.com
He who is not aware of his
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 no
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
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
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 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 executables ...
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
Today's -current kernel. This happend when I invoke linux-netscape.
lock order reversal
1st 0xe7fdf134 filedesc structure (filedesc structure) @
../../../kern/kern_descrip.c:1531
2nd 0xc0321ca0 filelist lock (filelist lock) @ ../../../kern/kern_descrip.c:1092
recursed on non-recursive lock
On Sat, 13 Apr 2002, Terry Lambert wrote:
Rasmus Skaarup wrote:
2) When logged in as root, and su'd to a non-root user, I cannot ssh to a
4.5-STABLE machine.. It just hangs. But when logged in as non-root, it
works fine. Is this somekind of security feature? :-)
Pretty much. The user
Rasmus Skaarup wrote:
On Sat, 13 Apr 2002, Terry Lambert wrote:
Rasmus Skaarup wrote:
2) When logged in as root, and su'd to a non-root user, I cannot ssh to a
4.5-STABLE machine.. It just hangs. But when logged in as non-root, it
works fine. Is this somekind of security feature? :-)
, and su'd to a non-root user, I cannot ssh to a
4.5-STABLE machine.. It just hangs. But when logged in as non-root, it
works fine. Is this somekind of security feature? :-)
3) lock order reversal when for instance doing a cvsup
Apr 13 12:16:58 laptop kernel: lock order reversal
Apr 13 12:16:58
Rasmus Skaarup wrote:
2) When logged in as root, and su'd to a non-root user, I cannot ssh to a
4.5-STABLE machine.. It just hangs. But when logged in as non-root, it
works fine. Is this somekind of security feature? :-)
Pretty much. The user it attempts to log you in as is still
root,
Today's -current kernel.
lock order reversal
1st 0xe322f024 DIRHASH (UMA zone) @ ../../../vm/uma_core.c:269
2nd 0xc081da94 PCPU 256 (UMA cpu) @ ../../../vm/uma_core.c:1265
--
Jun Kuriyama [EMAIL PROTECTED] // IMG SRC, Inc.
[EMAIL PROTECTED] // FreeBSD Project
To Unsubscribe
This is probably a known lock order reversals, but
I haven't seen it reported on the mailing list.
lock order reversal
1st 0xc403d720 PCPU 4096 (UMA cpu) @ /usr/src/sys/vm/uma_core.c:1179
2nd 0xc403d664 4096 (UMA zone) @ /usr/src/sys/vm/uma_core.c:614
3rd 0xc082a720 PCPU KMAP ENTRY (UMA cpu
I get this when starting mpg123 about 50% of the time:
lock order reversal
1st 0xc8e22f40 pcm0:play:0 @
/usr/src/sys/modules/sound/pcm/../../../dev/sound/pcm/dsp.c:150
2nd 0xc8e24380 pcm0 @
/usr/src/sys/modules/sound/pcm/../../../dev/sound/pcm/sound.c:134
-current as of yesterday, using
I got this message on today's -current:
lock order reversal
1st 0xc036afc0 allproc @ ../../../kern/vfs_syscalls.c:452
2nd 0xc7ecce34 filedesc structure @ ../../../kern/vfs_syscalls.c:457
--
Jun Kuriyama [EMAIL PROTECTED] // IMG SRC, Inc.
To Unsubscribe: send mail to [EMAIL PROTECTED
In noticed this lock order reversal while shutting down the system to
single-user in order to make installworld of my cvsup of today. I then
tried again with the new world and the l.o.r. was still there.
lock order reversal
1st 0xc0409dc0 allproc @ ../../../kern/vfs_syscalls.c:452
2nd
In noticed this lock order reversal while shutting down the system to
single-user in order to make installworld of my cvsup of today. I then
tried again with the new world and the l.o.r. was still there.
lock order reversal
1st 0xc0409dc0 allproc @ ../../../kern/vfs_syscalls.c:452
2nd
* Emiel Kollof ([EMAIL PROTECTED]) wrote:
exclusive (sleep mutex) Giant (0xc0462c00) locked @
/usr/src/sys/i386/i386/trap.c:1102
panic: system call pwrite returning with mutex(s) held
Hmm, erm, go kick Alfred really hard. :) This function locks Giant and then
doesn't ever unlock
* Emiel Kollof [EMAIL PROTECTED] [020116 13:29] wrote:
* Emiel Kollof ([EMAIL PROTECTED]) wrote:
exclusive (sleep mutex) Giant (0xc0462c00) locked @
/usr/src/sys/i386/i386/trap.c:1102
panic: system call pwrite returning with mutex(s) held
Hmm, erm, go kick Alfred really hard.
* Alfred Perlstein [EMAIL PROTECTED] [020116 13:30] wrote:
* Emiel Kollof [EMAIL PROTECTED] [020116 13:29] wrote:
* Emiel Kollof ([EMAIL PROTECTED]) wrote:
exclusive (sleep mutex) Giant (0xc0462c00) locked @
/usr/src/sys/i386/i386/trap.c:1102
panic: system call pwrite returning
* Alfred Perlstein ([EMAIL PROTECTED]) wrote:
It would help if someone cc'd me on these. :P
Fix should be in now.
Great! Thanks! Remind me to buy you a beer if I ever get to meet you in
real life :-)
Right.. cvsup it is...
Cheers,
Emiel
--
If you can survive death, you can probably
config
I also had some strange panics and these messages appear once in a while:
lock order reversal 1st 0xc185e934 filedesc structure @
/usr/src/sys/kern/kern_descrip.c:925
2nd 0xc0419b00 Giant @ /usr/src/sys/kern/kern_descrip.c:959
The panics moan about a kernel trap and some mutex stuff
fine if I leave options NETATALK out of my config
I also had some strange panics and these messages appear once in a while:
lock order reversal 1st 0xc185e934 filedesc structure @
/usr/src/sys/kern/kern_descrip.c:925
2nd 0xc0419b00 Giant @ /usr/src/sys/kern/kern_descrip.c:959
This one is due
* John Baldwin ([EMAIL PROTECTED]) wrote:
The panics moan about a kernel trap and some mutex stuff involving
Giant. It only happens when I start Samba.
Having the actual panic messages would be very helpful here.
Hmm, I will proceed to crash my machine again and have a go in hand
* John Baldwin ([EMAIL PROTECTED]) wrote:
lock order reversal 1st 0xc185e934 filedesc structure @
/usr/src/sys/kern/kern_descrip.c:925
2nd 0xc0419b00 Giant @ /usr/src/sys/kern/kern_descrip.c:959
This one is due to not releasing the filedesc lock when grabbing Giant to free
oldofile
On 16-Jan-02 Emiel Kollof wrote:
* John Baldwin ([EMAIL PROTECTED]) wrote:
lock order reversal 1st 0xc185e934 filedesc structure @
/usr/src/sys/kern/kern_descrip.c:925
2nd 0xc0419b00 Giant @ /usr/src/sys/kern/kern_descrip.c:959
This one is due to not releasing the filedesc lock when
* John Baldwin ([EMAIL PROTECTED]) wrote:
/var: lost blocks 62 files 8
No, that's softupdates stuff. I think releasing filedesc is ok this case,
but usually I would recode it to move malloc's and free's around to avoid
having to drop and reacquire locks.
Ah right... Good to know...
In message [EMAIL PROTECTED], Emiel Kollof writes:
Oh, on another note, is someone working at that netatalk breakage? Who
do I have to discipline for that? :-)
Could you try the following patch in src/sys/netatalk? The problem
was caused by the -fno-common compiler option that was added to
the
* Ian Dowse ([EMAIL PROTECTED]) wrote:
Oh, on another note, is someone working at that netatalk breakage? Who
do I have to discipline for that? :-)
Could you try the following patch in src/sys/netatalk? The problem
was caused by the -fno-common compiler option that was added to
the kernel
* Emiel Kollof ([EMAIL PROTECTED]) wrote:
This compiles for me, but I haven't checked that it actually works.
I will test it. (run netatalk and transfer some files to and fro)
It compiled, and after making a connection with Appletalk with one of my
macs, file transfers went off without a
Hello everybody,
I'm getting a lock order reversal from pcm over last days,
which look like this:
Dec 15 16:47:54 mephisto kernel: lock order reversal
Dec 15 16:47:54 mephisto kernel: 1st 0xc390e640 pcm0 @
../../../dev/sound/pcm/sound.c:132
Dec 15 16:47:54 mephisto kernel: 2nd 0xc390e500 pcm0
Hello everybody,
over the last few days I get this lock order reversal
and also my box freezes somtimes. I don't know if there
is a connection but I think it might be of interest.
If not ignore this mail ...
This I see in /var/log/messages:
Dec 15 16:47:54 mephisto kernel: lock order reversal
hi,
i'm running -current as of november 10th. when i'm playing sound over the
dsp i sometimes get:
lock order reversal
1st 0xc19aea00 pcm0 @
/usr/src/sys/modules/sound/pcm/../../../dev/sound/pcm/sound.c:132
2nd 0xc19ae8c0 pcm0:play:0 @
/usr/src/sys/modules/sound/pcm/../../../dev/sound/pcm
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
find
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 @
/usr/src/sys/modules/sound/pcm/../../../dev/sound/pcm/sound.c:132
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 @
/usr
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/sys/vm
: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
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/kernel: 1st
::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
:
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
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, but
Fresh -current kernel on an DS10 Alpha box:
System shutdown time has arrived
Writing entropy file:.
lock order reversal
1st 0xfc7574b0 clk @ ../../../alpha/alpha/clock.c:702
2nd 0xfc7526b0 callout @ ../../../kern/kern_timeout.c:225
witness_lock
Stopped at Debugger+0x34
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.
On Mon, 24 Sep 2001, Wilko Bulte wrote:
I did notice that the default Alpha beep is of a much higher frequency
than the x86 one. Any relation? (long shot... I suppose)
This bug is well known (including by your mailbox). From mail sent to
your mailbox:
% From [EMAIL PROTECTED] Mon Jun 18
101 - 200 of 235 matches
Mail list logo
