On Dec 02, Mathew Kanner wrote:
> On Dec 01, Maxime Henrion wrote:
> [snip]
> I believe that your patch should fix the problem. In general
> I see one of three strategies,
>
> 1)Your patch,
> 2)create a new snd_mtxcreate_chan for channels that sets the
> flags DUP_OK.
> 3)Fix lo
On Dec 01, Maxime Henrion wrote:
> Mathew Kanner wrote:
> [patch ripped]
> >
> > Maxime,
> > I think it would be better to isolate the changes (DUP_OK flag
> > and lock creation) to just the channel code, no need to touch every
> > driver.
>
> Yes, but to do this I'd need either to make t
Maxime Henrion wrote:
> Mathew Kanner wrote:
> [patch ripped]
>>
>> Maxime,
>> I think it would be better to isolate the changes (DUP_OK flag
>> and lock creation) to just the channel code, no need to touch every
>> driver.
>
> Yes, but to do this I'd need either to make the channel code use
> m
Mathew Kanner wrote:
[patch ripped]
>
> Maxime,
> I think it would be better to isolate the changes (DUP_OK flag
> and lock creation) to just the channel code, no need to touch every
> driver.
Yes, but to do this I'd need either to make the channel code use
mtx_init() directly, which
On Dec 01, Maxime Henrion wrote:
> Jesse Guardiani wrote:
> > Jesse Guardiani wrote:
> Index: isa/ad1816.c
> ===
> RCS file: /space2/ncvs/src/sys/dev/sound/isa/ad1816.c,v
> retrieving revision 1.29
> diff -u -p -r1.29 ad1816.c
> --- i
Jesse Guardiani wrote:
> Jesse Guardiani wrote:
>
> > I get this every time I `startx`. I didn't see it in
> > the archive either:
> >
> >
> > acquiring duplicate lock of same type: "pcm channel"
> > 1st pcm0:record:0 @ /usr/src/sys/d
Jesse Guardiani wrote:
> I get this every time I `startx`. I didn't see it in
> the archive either:
>
>
> acquiring duplicate lock of same type: "pcm channel"
> 1st pcm0:record:0 @ /usr/src/sys/dev/sound/pcm/dsp.c:144
> 2nd pcm0:virtual:0 @ /usr/src
I get this every time I `startx`. I didn't see it in
the archive either:
acquiring duplicate lock of same type: "pcm channel"
1st pcm0:record:0 @ /usr/src/sys/dev/sound/pcm/dsp.c:144
2nd pcm0:virtual:0 @ /usr/src/sys/dev/sound/pcm/dsp.c:146
Stack backtrace:
backtrace(c089b7e5,c3
ing2 while having xmms playing:
acquiring duplicate lock of same type: "pcm channel"
1st pcm0:record:0 @ /usr/src/sys/dev/sound/pcm/sound.c:191
2nd pcm0:play:0 @ /usr/src/sys/dev/sound/pcm/sound.c:191
Debugger("witness_lock")
Stopped at Debugger+0x5a: xchgl %ebx,in
Got thsi when opening gnomemeeting2 while having xmms playing:
acquiring duplicate lock of same type: "pcm channel"
1st pcm0:record:0 @ /usr/src/sys/dev/sound/pcm/sound.c:191
2nd pcm0:play:0 @ /usr/src/sys/dev/sound/pcm/sound.c:191
Debugger("witness_lock")
Stopped at D
Kris Kennaway wrote:
>
> bento found the following about 5 minutes after I upgraded it to 5.0.
>
> acquiring duplicate lock of same type: "system map"
> 1st system map @ ../../../vm/vm_map.c:2168
> 2nd system map @ ../../../vm/vm_kern.c:325
Thanks for the stack
On Sat, Jan 25, 2003 at 12:59:25PM -0600, Alan L. Cox wrote:
> Kris Kennaway wrote:
> >
> > bento found the following about 5 minutes after I upgraded it to 5.0.
> >
> > acquiring duplicate lock of same type: "system map"
> > 1st system map @ ..
bento found the following about 5 minutes after I upgraded it to 5.0.
acquiring duplicate lock of same type: "system map"
1st system map @ ../../../vm/vm_map.c:2168
2nd system map @ ../../../vm/vm_kern.c:325
Debugger("witness_lock")
Stopped at Debugger+0x55: xchgl %
--On 01 December 2002 10:26 +0100 Marc Recht
<[EMAIL PROTECTED]> wrote:
Hi!
I'm seeing this lately:
acquiring duplicate lock of same type: "pcm channel"
1st pcm0:record:0 @ /usr/src/sys/dev/sound/pcm/sound.c:191
2nd pcm0:play:0 @ /usr/src/sys/dev/sound/pcm/sound.c:
Hi!
I'm seeing this lately:
acquiring duplicate lock of same type: "pcm channel"
1st pcm0:record:0 @ /usr/src/sys/dev/sound/pcm/sound.c:191
2nd pcm0:play:0 @ /usr/src/sys/dev/sound/pcm/sound.c:191
"$FreeBSD: src/sys/dev/sound/pcm/sound.c,v 1.80 2002/11/26 18:16:27 cg Exp
make sure it isn't the cause?
Samba disable, rebooted, error didn't happens again. Samba started by hand,
'duplicate lock ...' error displays.
Jens
--
L i W W W i Jens Rehsack
LW W W
L i W W W W i nnnL
> searching archive yields this thread.
> >
> > 'Subject: /usr/src/sys/netinet/udp_usrreq.c:290'
> >
> > looks like I'm not the only one seeing this.
>
> This happens on my test machine directly after samba starts ...
Can you disable samba from starting just to make sure it isn't the cause?
T
Joel M. Baldwin wrote:
acquiring duplicate lock of same type: "inp"
1st inp @ ../../../netinet/udp_usrreq.c:290
2nd inp @ ../../../netinet/udp_usrreq.c:290
I get this every tims samba starts. Jeffery Hsu stated that its benign.
Lars
--
Lars Eggert <[EMAIL PROTECTED]>
Joel M. Baldwin wrote:
FreeBSD outel.org 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Thu Nov 7
05:13:19 PST 2002
[EMAIL PROTECTED]:/disk2/usr.src/sys/i386/compile/testGeneric.nonsmp i386
acquiring duplicate lock of same type: "inp"
1st inp @ ../../../netinet/udp_usrreq.c:2
FreeBSD outel.org 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Thu Nov 7
05:13:19 PST 2002
[EMAIL PROTECTED]:/disk2/usr.src/sys/i386/compile/testGeneric.nonsmp
i386
acquiring duplicate lock of same type: "inp"
1st inp @ ../../../netinet/udp_usrreq.c:290
2nd inp @ ../../../netinet/udp_us
I have seen these messages on my slow 266MHz dual Pentium II machine with
a kernel build with source from after Matt and Jake's commits. Is there
anyone interrested in it? It happened while doing a cvs -q update -PAd.
acquiring duplicate lock of same type: "PCPU KNOTE"
1s
Hi All,
Has anybody seen this message before?
CPU: Pentium III/Pentium III Xeon/Celeron (595.58-MHz 686-class CPU)
Origin = "GenuineIntel" Id = 0x686 Stepping = 6
Features=0x383f9ff
real memory = 134152192 (131008K bytes)
avail memory = 125829120 (122880K bytes)
acquiring dupl
22 matches
Mail list logo
