>Good news, please supply a dmesg before and after.
I've attached them. Both are GENERIC kernels, one booted
with ACPI ENABLED [default] and the other with ACPI
DISABLED.
Thanks for your help,
Peter Hofer
Copyright (c) 1992-2003 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988,
On Dec 03, Peter Hofer wrote:
> Mathew Kanner wrote:
>
> > I notice that your network cards, sound card and sio use IRQ
> >4, I also note that your aren't using acpi, what happens when you
> >enable it?
> >
> You're right, it was because of ACPI ;)
>
> I just compiled a GENERIC kernel and boo
Mathew Kanner wrote:
I notice that your network cards, sound card and sio use IRQ
4, I also note that your aren't using acpi, what happens when you
enable it?
You're right, it was because of ACPI ;)
I just compiled a GENERIC kernel and booted it with ACPI ENABLED.
The problem didn't occur
A quick tought; perhaps you need to remove irq 5 from pccard.conf
But...
> The problem also persists when I'm using my rl nic instead of the
> onboard bfe chip.
..maybe not.
Try it.
Dylan
On 3 Dec 2003 at 20:04, Peter Hofer wrote:
> Hi there,
>
> since I installed 5.2-BETA, I've got a very st
twork works again. There's no problem in receiving and sending
> data then.
>
> I was able to reproduce this with mpg123, it just stops playing and
> exits when data is being sent over the network.
And dmesg then says "pcm channel dead" ?
>
> The problem
Hi there,
since I installed 5.2-BETA, I've got a very strange problem. Always
when I'm listening to some music and start a network transfer, both
the music and the transfer stop after some time. Nothing is being
received or sent any more, and the following message appears a few
times:
bfe0: watchd
On Dec 03, Sean Chittenden wrote:
> > > Hello All,
> > > Please test this PCM patch. It creates seperate locking
> > > classes for PCM channels and should prevent the warning where
> > > multiple mutexes from the same class are held (as reported
> >
On Dec 03, Sean Chittenden wrote:
> > > Hello All,
> > > Please test this PCM patch. It creates seperate locking
> > > classes for PCM channels and should prevent the warning where
> > > multiple mutexes from the same class are held (as reported
> >
> > Hello All,
> > Please test this PCM patch. It creates seperate locking
> > classes for PCM channels and should prevent the warning where
> > multiple mutexes from the same class are held (as reported
> > recently). I believe this to be a good strategy as it
> Hello All,
> Please test this PCM patch. It creates seperate locking
> classes for PCM channels and should prevent the warning where
> multiple mutexes from the same class are held (as reported
> recently). I believe this to be a good strategy as it masks fewer
> erro
Hello All,
Please test this PCM patch. It creates seperate locking
classes for PCM channels and should prevent the warning where multiple
mutexes from the same class are held (as reported recently). I
believe this to be a good strategy as it masks fewer errors.
Thanks
Mathew Kanner <[EMAIL PROTECTED]> wrote:
> Hello All,
> Please test a pcm patch that releases the channel lock around
> calls to uio move. This is a more complete patch than the previous
> one as it also does the _read routine. I will ask the RE to commit
> this if I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 26 Nov 2003 19:32, Harald Schmalzbauer wrote:
> "it works"
>
> But I haven't had any problems before (besides some replay delay, thus
> asynch audio/video)
Yes, same here. It works, but I wasn't having problems before:
pcm0: port 0xc400
On Thu, 2003-11-27 at 02:54, Mathew Kanner wrote:
> Please test a pcm patch that releases the channel lock around
> calls to uio move. This is a more complete patch than the previous
> one as it also does the _read routine. I will ask the RE to commit
> this if I hear a couple of &q
On Wednesday 26 November 2003 19:54, Mathew Kanner wrote:
> Hello All,
> Please test a pcm patch that releases the channel lock around
> calls to uio move. This is a more complete patch than the previous
> one as it also does the _read routine. I will ask the RE to commit
>
Hello All,
Please test a pcm patch that releases the channel lock around
calls to uio move. This is a more complete patch than the previous
one as it also does the _read routine. I will ask the RE to commit
this if I hear a couple of "it works".
Pointed out by: Artur Poplawski
se a panic
> > >>> like this:
> > >
> > >>> Sleeping on "swread" with the following non-sleepable locks held:
> > >>> exclusive sleep mutex pcm0:play:0 (pcm channel) r = 0 (0xc1c3d740) locked @ \
> > >>>
> > &
wrote:
> >>
> >>> Hello,
> >>>
> >>> On a 5.1-RELEASE and 5.2-BETA machines I have been able to cause a panic
> >>> like this:
> >
> >>> Sleeping on "swread" with the follow
>>> On a 5.1-RELEASE and 5.2-BETA machines I have been able to cause a panic
>>> like this:
>
>>> Sleeping on "swread" with the following non-sleepable locks held:
>>> exclusive sleep mutex pcm0:play:0 (pcm channel) r =
E and 5.2-BETA machines I have been able to cause a panic
>> like this:
>> Sleeping on "swread" with the following non-sleepable locks held:
>> exclusive sleep mutex pcm0:play:0 (pcm channel) r = 0 (0xc1c3d740) locked @ \
>> /usr/src/sys/dev/sound/p
gt; Sleeping on "swread" with the following non-sleepable locks held:
> exclusive sleep mutex pcm0:play:0 (pcm channel) r = 0 (0xc1c3d740) locked @ \
> /usr/src/sys/dev/sound/pcm/dsp.c:146
> panic: sleeping thread (pid 583) owns a non-sleepable lock
> syncing disks, buff
vm_pageout_flush
vm_pageout_clean
vm_pageout_scan
vm_pageout
fork_exit
fork_trampoline
Sleeping on "swread" with the following non-sleepable locks held:
exclusive sleep mutex pcm0:play:0 (pcm channel) r = 0 (0xc1c3d740) locked @ \
/usr/src/sys/dev/sound/pcm/dsp.c:146
panic: sleep
Hi! I'm running a very recent -current(13 november) and am having
problems with audio.
I;m running on a Gigabyte 7VM400M Mother board, the boot message about
pcm is the following:
pcm0: port 0xe400-0xe4ff irq 11 at device 17.5 on pci0
pcm0:
This has worked on 5.1-RELEASE(but I did not
Hello Paolo,
See below.
On Oct 20, Paolo Pisati wrote:
> from my dmesg:
> [snip]
> exclusive sleep mutex pcm0:mixer (pcm mixer) r = 0 (0xc2d34540) locked @
> /usr/src/sys/dev/sound/pcm/mixer.c:322
Could you try deleting the snd_mtxlock and snd_mtxunlock in
mixer_hwv
On Mon, Oct 20, 2003 at 10:37:00AM -0700, Kris Kennaway wrote:
> Unfortunately none of the sound developers have been interested in
> looking at the locking problems in the code.
=(
> > acquiring duplicate lock of same type: "pcm channel"
> > 1st pcm0:record:0
; exclusive sleep mutex pcm0:mixer (pcm mixer) r = 0 (0xc2d34540) locked @
> /usr/src/sys/dev/sound/pcm/mixer.c:322
Unfortunately none of the sound developers have been interested in
looking at the locking problems in the code.
> acquiring duplicate lock of same type: "pcm channel"
from my dmesg:
[snip]
pcm0: port 0xb800-0xb8ff irq 5 at device 1.0 on pci2
pcm0: failed to enable memory mapping!
pcm0:
malloc() of "64" with the following non-sleepable locks held:
exclusive sleep mutex pcm0:mixer (pcm mixer) r = 0 (0xc2d34540) locked @
/usr/src/sys/dev/sound/pcm/m
dont
get those little lines and shit when music is playing i dono if i shot my
soundcard or if there still is a problem with the commit to ac97.c
% mixer
Mixer vol is currently set to 75:75
Mixer pcm is currently set to 75:75
Mixer speaker is currently set to 75:75
Mixer line is
On Sunday 24 August 2003 00:25, Harald Schmalzbauer wrote:
> Hi all,
>
> I can confirm something is wrongwith pcm.
> I have no sound output with todays kernel, the one some weeks ago I had no
> problems.
Ok, things are fine again.
I just cvsupped and saw that something AC97 rela
Harald Schmalzbauer wrote:
--Boundary-02=_Nn+R/bAN6Fk+pt3
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-Description: signed data
Content-Disposition: inline
Hi all,
I can confirm something is wrongwith pcm.
I have no sound output w
Hi all,
I can confirm something is wrongwith pcm.
I have no sound output with todays kernel, the one some weeks ago I had no
problems.
Here's my dmesg:
pcm0: port 0xd400-0xd43f irq 5 at device 13.0 on pci2
pcm0:
In /dev I have: dsp0.0 dsp0.1 dspW0.0 dspW0.1 dspr0.0 and mixer0
Cvs
order reversal
1st 0xc4021c40 pcm0 (sound softc) @ /usr/src/sys/dev/sound/pci/cmi.c:520
2nd 0xc402c4c0 pcm0:play:0 (pcm channel) @ /usr/src/sys/dev/sound/pcm/channel.c
:440
Stack backtrace:
backtrace(c03503c2,c402c4c0,c4045154,c03420f5,c03421cf) at backtrace+0x17
witness_lock(c402c4c0,8,c03421cf
> Is anything printed on the console (or the first vty)?
>
> > Andre Guibert de Bruet | Enterprise Software Consultant >
> > Silicon Landmark, LLC. | http://siliconlandmark.com/>
Nope. I get complete blackout - I'm unable to switch vtys, move mouse,
start a new process, etc. Just like a crash
Dear Sirs,
I have problems with my 5.1-Release and 5.1-STABLE boxes:
they freeze if I play anything different from audio CDs.
The cards are ESS 1938, options pcm is in the kernel.
If I try to run xmms/mpg123/KDE or any other application related
with artsd/esound/audiofile, the machines freeze
very recent -current.
>
> When I am watching movies in mplayer, I get on the console from time to time:
>
> lock order reversal
> 1st 0xc4021c40 pcm0 (sound softc) @ /usr/src/sys/dev/sound/pci/cmi.c:520
> 2nd 0xc402c4c0 pcm0:play:0 (pcm channel) @ /usr/src/sys/dev/sound/pcm/channel
On Thu, 7 Aug 2003 [EMAIL PROTECTED] wrote:
> I have problems with my 5.1-Release and 5.1-STABLE boxes:
> they freeze if I play anything different from audio CDs.
> The cards are ESS 1938, options pcm is in the kernel.
> If I try to run xmms/mpg123/KDE or any other application re
/-- Kris Kennaway wrote:
|
| LORs in the pcm system are reported quite regularly, but I haven't
| seen anyone working on the problem. Is there anyone who can look at
| the locking code used in this system and fix the problems? Perhaps
| this should be added to the 5.2 TODO list.
| =20
Hi!
I got a problem with the pcm driver - on the startup of whatever sound
application by whatever user - root, me, etc it freezes my machine.
I experienced this both on 5.1RElease and 5.1-STABLE(24.07.2003CVSUP). The card
is ESS 1938(SOLO-1) The thing happens over and over again. Here is what I
Looks like my mp3 playback tried to acquire UFS lockmgr lock with the pcm
lock held. Also, got a LoR w/ Giant through a page not present trap. Only
the backtrace() is hand-transcribed due to it not being in dmesg. My system
appears to be working fine and there was no crash.
dmesg
-
pcm0
tc) @
/usr/src/sys/dev/sound/isa/mss.c:179
2nd 0xc40bb180 pcm0:play:0 (pcm channel) @
/usr/src/sys/dev/sound/pcm/channel.c
:440
Stack backtrace:
backtrace(c03e3e7c,c40bb180,c405ced4,c03d57a5,c03d587f) at
backtrace+0x17
witness_lock(c40bb180,8,c03d587f,1b8,a) at witness_lock+0x697
_mtx_lock_flags(
sys/dev/sound/pci/cmi.c:520
> 2nd 0xc6209e80 pcm0:play:0 (pcm channel) @
> /local/usr.src/sys/dev/sound/pcm/channel.c:440
> Stack backtrace:
> backtrace(c04e759f,c6209e80,c61a9b54,c06a2127,c06a21a5) at backtrace+0x17
> witness_lock(c6209e80,8,c06a21a5,1b8,c61a9b00) at witness_lock+0x
Just thought I would report it:
lock order reversal
1st 0xc61f5940 pcm0 (sound softc) @ /local/usr.src/sys/dev/sound/pci/cmi.c:520
2nd 0xc6209e80 pcm0:play:0 (pcm channel) @
/local/usr.src/sys/dev/sound/pcm/channel.c:440
Stack backtrace:
backtrace(c04e759f,c6209e80,c61a9b54,c06a2127,c06a21a5
On Wed, 2003-02-26 at 01:49, Olivier Houchard wrote:
> > The pcm driver is compiled into the kernel, i haven't tested loading as
> > module.
> >
> > dmesg|grep pcm:
> > pcm0: port 0x9400-0x941f irq 5 at device 13.0 on pci0
> > pcm0:
> >
30: could sleep with "pcm0:play:0" locked from
/usr/src/sys/dev/sound/pcm/sound.c:191
When I attempt to play any sound now, an annoying high-pitched whine comes out
the speakers until the process is terminated, and the dmesg buffer is
overwritten by hundreds of instances of this unhel
a kernel built from 17:00 sources sound works, from 19:00 there is
> > only the sound of silence. Everything looks OK, xmms, mpg123 etc play,
> > but no sound.
> >
> > The pcm driver is compiled into the kernel, i haven't tested loading as
> > module.
>
> Coul
looks OK, xmms, mpg123 etc play,
> but no sound.
>
> The pcm driver is compiled into the kernel, i haven't tested loading as
> module.
>
> dmesg|grep pcm:
> pcm0: port 0x9400-0x941f irq 5 at device 13.0 on pci0
> pcm0:
>
> Soundcard: Soundblaster Live 1024! Pl
I believe the commit Feb 20 17:31:11 2003 UTC on
src/sys/dev/sound/pci/emu10k1.c broke something.
With a kernel built from 17:00 sources sound works, from 19:00 there is
only the sound of silence. Everything looks OK, xmms, mpg123 etc play,
but no sound.
The pcm driver is compiled into the
330: could sleep with "pcm0:play:0" locked from
/usr/src/sys/dev/sound/pcm/sound.c:191
When I attempt to play any sound now, an annoying high-pitched whine comes out
the speakers until the process is terminated, and the dmesg buffer is
overwritten by hundreds of instances of this unhelpful
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
lock order reversal
1st 0xc12602c0 pcm0:play:0 (pcm channel) @ ../../../dev/sound/pcm/sound.c:191
2nd 0xc1260440 pcm0 (sound cdev) @ ../../../dev/sound/pcm/sound.c:163
acquiring duplicate lock of same type: "pcm channel"
1st pcm0:record:0 @ ../../../dev/sound/pcm/dsp.c:328
2nd p
--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,
> Since rescent -CURRENT is stable enough, I have the chance to find
> out remaining pcm problem. My MP box no more has double fatal fault
> and turns into random sleep. The random sleep happens after pcm having
> its own problem.
>
> uname -av is
> FreeBSD car
On Sat, Dec 07, 2002 at 01:00:44AM +0800, Clive Lin wrote:
> Hi,
>
> Since rescent -CURRENT is stable enough, I have the chance to find
> out remaining pcm problem. My MP box no more has double fatal fault
> and turns into random sleep. The random sleep happens after pcm h
Hi,
Since rescent -CURRENT is stable enough, I have the chance to find
out remaining pcm problem. My MP box no more has double fatal fault
and turns into random sleep. The random sleep happens after pcm having
its own problem.
uname -av is
FreeBSD cartier.home 5.0-CURRENT FreeBSD 5.0
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
e.c
> sys/dev/sound/pcmac97.c channel.h mixer.c sound.c
> Log:
> (hopefully) fix build breakage some people are seeing
This fixed it, thanks!
--
Ray Kohler <[EMAIL PROTECTED]>
Jesus Saves,
Moses Invests,
But only Buddha pays Dividends.
To Unsubscribe: send mail to [E
Okay here a detailed description...
a) Install a minumum -current from snapshot CD (2 days old).
b) Add a cvsup-package without gui (i made before with pkg_create -b blah).
c) Get -current fom cvs repo (with cvsup...).
d) cd /usr/src && make buildworld (works fine)
e) copying my kernel-conf.
f
---
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Ray Kohler
> Sent: Tuesday, November 26, 2002 1:01 PM
> To: cameron grant
> Cc: [EMAIL PROTECTED]
> Subject: Re: cvs commit: src/sys/dev/sound/pcm buffer.c channel.c
> feeder.c feeder_fmt.c feeder_rate.c snd
On Tue, Nov 26, 2002 at 06:19:41AM +, cameron grant wrote:
> >I have no idea why, but this commit broke kernel building:
> >
> >cc -c -O -pipe -mcpu=athlon -Wall -Wredundant-decls -Wnested-externs
> >-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline
> >-Wcast-qual -fformat-ext
I have no idea why, but this commit broke kernel building:
cc -c -O -pipe -mcpu=athlon -Wall -Wredundant-decls -Wnested-externs
-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline
-Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I.
-I/usr/src/sys -I/usr/src/sys/dev -I/usr/src
> cg 2002/11/25 09:17:43 PST
>
> Modified files:
> sys/dev/sound/pcmbuffer.c channel.c feeder.c feeder_fmt.c
> feeder_rate.c sndstat.c sound.c sound.h vchan.c
>
> Log: various fixes to eliminate locking warnings
>
> Approved by: re
> Revi
.c:1307: could sleep with "pcm0" locked from
/usr/src/sys/dev/sound/pcm/sound.c:134
/usr/src/sys/vm/uma_core.c:1307: could sleep with "pcm0:fake" locked
from /usr/src/sys/dev/sound/pcm/channel.c:677
/usr/src/sys/vm/uma_core.c:1307: could sleep with "pcm0:play:0" locked
s not respond
to SIGKILL. I am then unable to use the pcm device until I reboot.
Second, I sometimes get panics while using mplayer, xine or xmms to play
audio, though this is less frequent than the unkillable process
condition. I've been unable to see any details of the panic (since it
happens wh
On 2002.07.02 17:56:28 +, Juan Francisco Rodriguez Hervella wrote:
> Im a bit corious about what's the meaning of "UMA".
>
> Thanks and sorry fot this simple question :)
UMA is the "Universal Memory Allocator", written by Jeff Roberson.
It's the memory manager and things like malloc(9) make
Martin Faxer escribió:
> On 2002.07.02 16:28:10 +, Michael Hostbaek wrote:
> > I have problems getting my sound card functioning under -CURRENT. (While
> > it was working perfect under -STABLE).
> >
> > I simply added 'device pcm' to the kernel config,
On 2002.07.02 16:28:10 +, Michael Hostbaek wrote:
> I have problems getting my sound card functioning under -CURRENT. (While
> it was working perfect under -STABLE).
>
> I simply added 'device pcm' to the kernel config, when booting on new
> kernel I get lots of err
I have problems getting my sound card functioning under -CURRENT. (While
it was working perfect under -STABLE).
I simply added 'device pcm' to the kernel config, when booting on new
kernel I get lots of errors like this:
port 0x1400-0x14ff irq 5 at device 8.0 on pci0
../../../vm/
>
> Looks like someone broke AC97 rate measurement in -CURRENT
>
> -STABLE measures AC97 rate well (about 55900). Current gives about
> 41000...
>
> Hardware is Compaq EXD C600 (-STABLE) and Compaq iPAQ C700 (-CURRENT)
> Both are i815 equipped with SoundMAX AC97 codec...
>
>Sincerely, Maxi
Looks like someone broke AC97 rate measurement in -CURRENT
-STABLE measures AC97 rate well (about 55900). Current gives about
41000...
Hardware is Compaq EXD C600 (-STABLE) and Compaq iPAQ C700 (-CURRENT)
Both are i815 equipped with SoundMAX AC97 codec...
Sincerely, Maxim M. Kazachek
Compiled the USB out of the kernel and have *much* better
responsiveness. I have a 4-port PCI USB OHCI controller card installed.
With both the USB and pcm modules unloaded the irq10 handler seems to
fall to 0% usage, but if I load snd_emu10k1.ko it pops right back up to
60% in top(1
x27;[EMAIL PROTECTED]'; [EMAIL PROTECTED]
> Subject: RE: pcm / mic
>
>
> > Hi,
> >
> > i cant record from /dev/dsp with the record device 'mic'. Is
> > there support
> > for the microphone input?
> >
>
> What sound card are you using?
&g
> Hi,
>
> i cant record from /dev/dsp with the record device 'mic'. Is
> there support
> for the microphone input?
>
What sound card are you using?
Scott
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Hi,
i cant record from /dev/dsp with the record device 'mic'. Is there support
for the microphone input?
Jan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
At 04:30 PM 4/15/2002 +0100, you wrote:
>--- John Angelmo <[EMAIL PROTECTED]> wrote:
> > I wonder how the pcm sound support is in 5.0?
>
>Hmm, I am using the emu10k1 aka Sound Blaster 1024 Live!, which has some
>locking problems, but apart from that I dont think ther
Hiten Pandya wrote:
> --- John Angelmo <[EMAIL PROTECTED]> wrote:
>
>>I wonder how the pcm sound support is in 5.0?
>
>
> Hmm, I am using the emu10k1 aka Sound Blaster 1024 Live!, which has some
> locking problems, but apart from that I dont think there
--- John Angelmo <[EMAIL PROTECTED]> wrote:
> I wonder how the pcm sound support is in 5.0?
Hmm, I am using the emu10k1 aka Sound Blaster 1024 Live!, which has some
locking problems, but apart from that I dont think there is any other
problems AFAIK. :)
> I didn't get it w
I wonder how the pcm sound support is in 5.0?
I didn't get it working in 4.5 but perhaps theres better support in 5.0
but I didn't find any info in NOTES
/John
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
ersal
Dec 15 16:47:54 mephisto kernel: 1st 0xc390e640 pcm0 @ ../../../dev/sound/pcm/so
und.c:132
Dec 15 16:47:54 mephisto kernel: 2nd 0xc390e500 pcm0:play:0 @ ../../../dev/sound
/pcm/sound.c:189
My X freezes very often in the last time , and I have to kill the server,
but somtimes the hole box freeze
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
> 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
>
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
All:
On one of my machines at work I run current and had been without "audio"
until
I found a posting where a user noted that enabling "APM" in the kernel
broke audio
Heh... I disabled apm/pmtimer and my PCM device works great While I
don't really care
about APM
In message <006501c0fa71$7fa71a40$0504020a@haveblue> "Cameron Grant" writes:
: while i've not tested either of these chips for a while (lack of slots,
: anyone know of a motherboard with ~20 pci and ~10 isa slots?) i can't think
: of any changes that might cause this except possibly the introducti
It seems Cameron Grant wrote:
> > I'm having problems with both an internal VIA'686 and a PCI base
> > ESS Solo1, both seem to loose interrupts. The interrupts doesn't
> > even show up in a vmstat -i / systat so something is definitly
> > wrong. BTW the exact same HW work just fine with -stable ?
> I'm having problems with both an internal VIA'686 and a PCI base
> ESS Solo1, both seem to loose interrupts. The interrupts doesn't
> even show up in a vmstat -i / systat so something is definitly
> wrong. BTW the exact same HW work just fine with -stable ?
while i've not tested either of these
I'm having problems with both an internal VIA'686 and a PCI base
ESS Solo1, both seem to loose interrupts. The interrupts doesn't
even show up in a vmstat -i / systat so something is definitly
wrong. BTW the exact same HW work just fine with -stable ?
Cameron ? anyone ?
-Søren
To Unsubscribe:
ot; musical phrase.
>
> The obvious answer would be to not run sync(8) :^)
>
> Likely, what you're seeing is the combo of the pcm driver being pretty
> sensitive to other interrupt activity and the ata driver turning off write
> caching by default.
Probably not, because t
er would be to not run sync(8) :^)
Likely, what you're seeing is the combo of the pcm driver being pretty
sensitive to other interrupt activity and the ata driver turning off write
caching by default.
- alex
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Tue, May 22, 2001 at 04:13:47PM +0200, Vallo Kallaste <[EMAIL PROTECTED]> wrote:
> I know that -current is very fragile to say at least, but what's
> specifically causing it?
Using simple
for ((i=1;i<=300;i++)); do sync; done
does the trick, my system spends more than 50% in system,
according
Hi
Playing mp3's with mpg123 has been quite satistfactory until now.
Today I've discovered that every execution of sync(8) distorts
music by means of "stretching" musical phrase. In example what
normally sounds like "How do" sounds now "Hhhooowww ddd"
with a bit of added noise or somethin
Current as of yesterday afternoon hangs trying to boot on my box with an
OPTi931 soundcard installed. It prints the probe, and then hangs. With
boot -v, the messages are
pcm0: at port 0x5
34-0x537,0x380-0x38b,0x220-0x22f,0xe0c-0xe0f irq 5 drq 0,1 on isa0
mss_init: opti_offset=2
Yanking the c
With a buildworld from two hours ago, i got the following message while
playing an MP3:
pcm1: play interrupt timeout, channel dead
After which the player process hangs. Interrupting (CTRL-C) and restarting
the player works. It happened only once so far, so I can't tell much more.
--
Theo van
> > This could be related to the entropy gathering by the random kthread. Have you
> > tried removing the random device from your kernel?
>
> yes, i've tried. no effect.
This seems to have fixed the problem for me, thanks! I'm using the
machine now and am getting no keyboard-related glitches in
On Fri, 9 Feb 2001, John Baldwin wrote:
> >> i have Ensoniq ES1371-based soundcard supported by pcm driver and
> >> experience some problems. the sound played is interruped by clicks and
> >> distorsions, and they appear more often when the disk activity is high.
>
On 09-Feb-01 Mike Holling wrote:
>> i have Ensoniq ES1371-based soundcard supported by pcm driver and
>> experience some problems. the sound played is interruped by clicks and
>> distorsions, and they appear more often when the disk activity is high.
>> during playb
> i have Ensoniq ES1371-based soundcard supported by pcm driver and
> experience some problems. the sound played is interruped by clicks and
> distorsions, and they appear more often when the disk activity is high.
> during playback the kernel generates messages like 'pcm0: hwptr
In message <[EMAIL PROTECTED]> Ilya Naumov writes:
: during playback the kernel generates messages like 'pcm0: hwptr went
: backwards 64 -> 32'. any ideas?
: FreeBSD 5.0-CURRENT #2: Thu Feb 8 18:19:26 MSK 2001
Interrupt latency in current really sucks right now.
Warner
To Unsubscribe: send ma
i have Ensoniq ES1371-based soundcard supported by pcm driver and
experience some problems. the sound played is interruped by clicks and
distorsions, and they appear more often when the disk activity is high.
during playback the kernel generates messages like 'pcm0: hwptr went
backwards 64
Hello,
Thank you for advices. Now I obtain same environment as of pre-devfs days.
From: Alex Kapranoff <[EMAIL PROTECTED]>
Date: Fri, 2 Feb 2001 15:29:09 +0300
> Yep. I have these in my /etc/rc.devfs:
> =
> ln -fs /dev/audio1.0 /dev/audio
> ln -fs /dev/dsp1.0 /dev/dsp
> ln -f
1 - 100 of 303 matches
Mail list logo
