Re: Sound broken on -current again...
Maxim Sobolev wrote: > John Baldwin wrote: > > > > The same is here (OPL3-SA driver on Toshiba Satellite Pro 445CDX notebook). > > > I found that after reverting the following deltas (jhb's 10 August commit) > > > sound starts working again: > > > > That's a rather large commit. Is this the ast() fixup? Is the process that > > has the sound device open hung? Is it stuck in a wait channel? If so, can you > > do a ps and find the wait channel? Is it chewing up large amounts of CPU time? > > Has it exited with a signal? > > Somebody tracked it down to kern_synch.c,v 1.154 and I'm confirming that reverting > this delta indeed fixes the problem. The process in question hangs and doesn't > respond to any signals (SIGKILL included). Following is the relevant piece of `ps > axl' output: > > UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND > 0 275 267 0 -8 0 41496 212 - R+v00:00,74 madplay /cdr > > Please note that even though madplay above is in the `RUN' state it doesn't consume > any CPU time. > > Please let me know if any additional information would be necessary. FYI: the same problem affects another my -current machine with sb16 card, with exactly the same symptoms, i.e. I hear 0.5 second or so of audio, then it halts and process hangs in the RUN state not responding to signals. -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sound broken on -current again...
John Baldwin wrote: > > The same is here (OPL3-SA driver on Toshiba Satellite Pro 445CDX notebook). > > I found that after reverting the following deltas (jhb's 10 August commit) > > sound starts working again: > > That's a rather large commit. Is this the ast() fixup? Is the process that > has the sound device open hung? Is it stuck in a wait channel? If so, can you > do a ps and find the wait channel? Is it chewing up large amounts of CPU time? > Has it exited with a signal? Somebody tracked it down to kern_synch.c,v 1.154 and I'm confirming that reverting this delta indeed fixes the problem. The process in question hangs and doesn't respond to any signals (SIGKILL included). Following is the relevant piece of `ps axl' output: UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND 0 275 267 0 -8 0 41496 212 - R+v00:00,74 madplay /cdr Please note that even though madplay above is in the `RUN' state it doesn't consume any CPU time. Please let me know if any additional information would be necessary. -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sound broken on -current again...
It seems John Baldwin wrote: > > In servalan.mailinglist.fbsd-current Maxim Sobolev writes: > >>I found that after reverting the following deltas (jhb's 10 August commit) > >>sound starts working again: > > > > [list of deltas deleted] > > > > I found much the same thing; specifically, the problematic change is this > > one: > > What wait channel is the process (xmms, mpg123, whatever) in? mpg123 hangs on sbwait Oh and btw the same commits seem to have broken USB too (at least on my VIA based board). -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sound broken on -current again...
In servalan.mailinglist.fbsd-current jhb writes:
>On 19-Aug-01 Richard Todd wrote:
>> In servalan.mailinglist.fbsd-current Maxim Sobolev writes:
>>>I found that after reverting the following deltas (jhb's 10 August commit)
>>>sound starts working again:
>>
>> [list of deltas deleted]
>>
>> I found much the same thing; specifically, the problematic change is this
>> one:
>What wait channel is the process (xmms, mpg123, whatever) in?
Looking at a core file from a known-buggy kernel that I'd forced to core
itself with ddb, I find for the madplay process:
(kgdb) proc 855
(kgdb) bt
#0 mi_switch () at ../../../kern/kern_synch.c:707
#1 0xc0273645 in msleep (ident=0xc13e0b00, mtx=0xc13d2800, priority=332,
wmesg=0xc042bcb4 "pcmwr", timo=1) at ../../../kern/kern_synch.c:466
#2 0xc01fcad8 in chn_sleep (c=0xc13d1680, str=0xc042bcb4 "pcmwr", timeout=1)
at ../../../dev/sound/pcm/channel.c:109
#3 0xc01fcd5c in chn_write (c=0xc13d1680, buf=0xc8f1af00)
at ../../../dev/sound/pcm/channel.c:259
#4 0xc01fef40 in dsp_write (i_dev=0xc13e0f00, buf=0xc8f1af00, flag=2359297)
at ../../../dev/sound/pcm/dsp.c:381
#5 0xc0243095 in spec_write (ap=0xc8f1ae90)
at ../../../fs/specfs/spec_vnops.c:289
#6 0xc0242dc9 in spec_vnoperate (ap=0xc8f1ae90)
at ../../../fs/specfs/spec_vnops.c:119
#7 0xc02b7c5f in vn_write (fp=0xc1623ec0, uio=0xc8f1af00, cred=0xc15c2600,
flags=0, p=0xc8e54100) at vnode_if.h:303
#8 0xc028c073 in dofilewrite (p=0xc8e54100, fp=0xc1623ec0, fd=3,
buf=0xbfbf8b74, nbyte=4608, offset=-1, flags=0) at ../../../sys/file.h:162
#9 0xc028bf26 in write (p=0xc8e54100, uap=0xc8f1af80)
at ../../../kern/sys_generic.c:334
#10 0xc03e2fc9 in syscall (frame={tf_fs = 47, tf_es = 47, tf_ds = 47,
tf_edi = -1077965964, tf_esi = 4608, tf_ebp = -1077937536,
tf_isp = -923684908, tf_ebx = -1077965964, tf_edx = 1103, tf_ecx = -411,
tf_eax = 4, tf_trapno = 0, tf_err = 2, tf_eip = 672022312, tf_cs = 31,
tf_eflags = 663, tf_esp = -1077966048, tf_ss = 47})
at ../../../i386/i386/trap.c:1128
#11 0xc03cce0d in syscall_with_err_pushed ()
so apparently it was waiting on 'pcmwr'.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Sound broken on -current again...
On 19-Aug-01 Richard Todd wrote: > In servalan.mailinglist.fbsd-current Maxim Sobolev writes: >>I found that after reverting the following deltas (jhb's 10 August commit) >>sound starts working again: > > [list of deltas deleted] > > I found much the same thing; specifically, the problematic change is this > one: What wait channel is the process (xmms, mpg123, whatever) in? -- John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sound broken on -current again...
On 19-Aug-01 Maxim Sobolev wrote: > On Sat, 18 Aug 2001 21:10:40 -0500, Daniel M . Kurry wrote: >> On Wed, Aug 15, 2001 at 07:01:46PM +0200, some SMTP stream spewed forth: >> > >> > One gets the first DMA buffer full, then the process hangs... >> >> Due to the lack of replies, I'll go ahead. >> >> I am seeing sound breakage also. >> My card is a >> Creative Labs SoundBlaster Live!. >> >> xmms will play a short (less than a second) spurt of audio and then stop >> responding. mpg123 will not play (any audio to the speakers) at all. >> >> I ran a buildworld today which apparently broke it. >> That puts the breakage between today and sometime less than 2 months >> ago. >> (I really cannot be more specific.) >> >> Suggestions gladly welcomed. >> >> >> > -Søren > > The same is here (OPL3-SA driver on Toshiba Satellite Pro 445CDX notebook). > I found that after reverting the following deltas (jhb's 10 August commit) > sound starts working again: That's a rather large commit. Is this the ast() fixup? Is the process that has the sound device open hung? Is it stuck in a wait channel? If so, can you do a ps and find the wait channel? Is it chewing up large amounts of CPU time? Has it exited with a signal? -- John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sound broken on -current again...
"SÜren Schmidt" wrote: > It seems Jim Bryant wrote: > > >Yups, reverting this, even in a newer kernel makes sound work again, > > >well the VIA support is still not sounding proberly, but it didn't > > >before as well so thats not related to this bogon... > > > > > Perhaps the bug in the chipset^wPCI-spec? > > > > >>>I dont think so, before the latest changes it worked just fine... > > >>> > > >>What's the problem? I didn't noticed anything. > > >> > > > It seems that there is either a slight pause, or random noise > > > between each DMA buffer played... > > > > > > -SÜren > > > > Was this chipset or motherboard-dependant? > > That particualar problem is dependend on the VIA 82c686[ab] I'd say, > but having no other sound HW right now, I really cant tell, I think > I've seen other sound HW with this problem too lately on the lists... > > > Like I said, I had no problems running SMP and with a SB/Live!-Value... > > > > Current as of yesterday morning [6-7AMish CDT], Tyan S1696DLUA motherboard, 2 >Pentium-II/333's, SB/Live! Value card. Did not produce > > thse issues. > > I'm pretty sure the problem with no sound due to jhb's commit mentioned > earlier hoses more than just the VIA chips... Yes, as I reported my OPL3-SA sound card was also affected by the same commit, so it is certainly not a VIA-specific. -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sound broken on -current again...
On 19 Aug, Søren Schmidt wrote: >> What's the problem? I didn't noticed anything. > > It seems that there is either a slight pause, or random noise > between each DMA buffer played... Verry strange... with a normal Aug 18 kernel and the VIA chipset I'm able to listen to xmms-played audio without noticing anything I didn't like (except there slipped in a song into the playlist I didn't like ;-)). Bye, Alexander. -- Loose bits sink chips. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sound broken on -current again...
It seems Jim Bryant wrote: > >Yups, reverting this, even in a newer kernel makes sound work again, > >well the VIA support is still not sounding proberly, but it didn't > >before as well so thats not related to this bogon... > > > Perhaps the bug in the chipset^wPCI-spec? > > >>>I dont think so, before the latest changes it worked just fine... > >>> > >>What's the problem? I didn't noticed anything. > >> > > It seems that there is either a slight pause, or random noise > > between each DMA buffer played... > > > > -Søren > > Was this chipset or motherboard-dependant? That particualar problem is dependend on the VIA 82c686[ab] I'd say, but having no other sound HW right now, I really cant tell, I think I've seen other sound HW with this problem too lately on the lists... > Like I said, I had no problems running SMP and with a SB/Live!-Value... > > Current as of yesterday morning [6-7AMish CDT], Tyan S1696DLUA motherboard, 2 >Pentium-II/333's, SB/Live! Value card. Did not produce > thse issues. I'm pretty sure the problem with no sound due to jhb's commit mentioned earlier hoses more than just the VIA chips... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sound broken on -current again...
On Sun, Aug 19, 2001 at 04:42:35PM -0500, some SMTP stream spewed forth: > > > Søren Schmidt wrote: > > > It seems Alexander Leidinger wrote: > > > >>On 19 Aug, Søren Schmidt wrote: > >> > >> > >Yups, reverting this, even in a newer kernel makes sound work again, > >well the VIA support is still not sounding proberly, but it didn't > >before as well so thats not related to this bogon... > > > Perhaps the bug in the chipset^wPCI-spec? > > >>>I dont think so, before the latest changes it worked just fine... > >>> > >>What's the problem? I didn't noticed anything. > >> > > > > It seems that there is either a slight pause, or random noise > > between each DMA buffer played... > > > > -Søren > > > Was this chipset or motherboard-dependant? With regard to the issues I mentioned earlier in this thread (that ~1 second of audio plays before the audio stops and I must kill xmms or mpg123), I am using Asus K7V Athlon 700 SoundBlaster Live! Platinum > Like I said, I had no problems running SMP and with a SB/Live!-Value... > > Current as of yesterday morning [6-7AMish CDT], Tyan S1696DLUA motherboard, 2 >Pentium-II/333's, SB/Live! Value card. Did not produce > thse issues. I have experienced this since the 17th. There have been no commits remotely near the sound system since then. gh > jim > -- > ET has one helluva sense of humor! > He's always anal-probing right-wing schizos! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sound broken on -current again...
Søren Schmidt wrote: > It seems Alexander Leidinger wrote: > >>On 19 Aug, Søren Schmidt wrote: >> >> >Yups, reverting this, even in a newer kernel makes sound work again, >well the VIA support is still not sounding proberly, but it didn't >before as well so thats not related to this bogon... > Perhaps the bug in the chipset^wPCI-spec? >>>I dont think so, before the latest changes it worked just fine... >>> >>What's the problem? I didn't noticed anything. >> > > It seems that there is either a slight pause, or random noise > between each DMA buffer played... > > -Søren Was this chipset or motherboard-dependant? Like I said, I had no problems running SMP and with a SB/Live!-Value... Current as of yesterday morning [6-7AMish CDT], Tyan S1696DLUA motherboard, 2 Pentium-II/333's, SB/Live! Value card. Did not produce thse issues. jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sound broken on -current again...
It seems Alexander Leidinger wrote: > On 19 Aug, Søren Schmidt wrote: > > >> > Yups, reverting this, even in a newer kernel makes sound work again, > >> > well the VIA support is still not sounding proberly, but it didn't > >> > before as well so thats not related to this bogon... > >> > >> Perhaps the bug in the chipset^wPCI-spec? > > > > I dont think so, before the latest changes it worked just fine... > > What's the problem? I didn't noticed anything. It seems that there is either a slight pause, or random noise between each DMA buffer played... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sound broken on -current again...
On 19 Aug, Søren Schmidt wrote: >> > Yups, reverting this, even in a newer kernel makes sound work again, >> > well the VIA support is still not sounding proberly, but it didn't >> > before as well so thats not related to this bogon... >> >> Perhaps the bug in the chipset^wPCI-spec? > > I dont think so, before the latest changes it worked just fine... What's the problem? I didn't noticed anything. Bye, Alexander. -- The best things in life are free, but the expensive ones are still worth a look. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sound broken on -current again...
> >> Revision ChangesPath > >> 1.154 +24 -4 src/sys/kern/kern_synch.c > > > > Yups, reverting this, even in a newer kernel makes sound work again, > > well the VIA support is still not sounding proberly, but it didn't > > before as well so thats not related to this bogon... > > Perhaps the bug in the chipset^wPCI-spec? I dont think so, before the latest changes it worked just fine... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sound broken on -current again...
On 19 Aug, Søren Schmidt wrote: >> Modified files: >> sys/kern kern_synch.c [...] >> Revision ChangesPath >> 1.154 +24 -4 src/sys/kern/kern_synch.c > > Yups, reverting this, even in a newer kernel makes sound work again, > well the VIA support is still not sounding proberly, but it didn't > before as well so thats not related to this bogon... Perhaps the bug in the chipset^wPCI-spec? Bye, Alexander. -- Speak softly and carry a cellular phone. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sound broken on -current again...
It seems Richard Todd wrote: > > I found much the same thing; specifically, the problematic change is this one: > > > jhb 2001/08/10 14:08:57 PDT > > Modified files: > sys/kern kern_synch.c > Log: > Work around a race between msleep() and endtsleep() where it was possible > for endtsleep() to be executing when msleep() resumed, for endtsleep() > to spin on sched_lock long enough for the other process to loop on > msleep() and sleep again resulting in endtsleep() waking up the "wrong" > msleep. > > Obtained from:BSD/OS > > Revision ChangesPath > 1.154 +24 -4 src/sys/kern/kern_synch.c Yups, reverting this, even in a newer kernel makes sound work again, well the VIA support is still not sounding proberly, but it didn't before as well so thats not related to this bogon... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sound broken on -current again...
In servalan.mailinglist.fbsd-current Maxim Sobolev writes: >I found that after reverting the following deltas (jhb's 10 August commit) >sound starts working again: [list of deltas deleted] I found much the same thing; specifically, the problematic change is this one: jhb 2001/08/10 14:08:57 PDT Modified files: sys/kern kern_synch.c Log: Work around a race between msleep() and endtsleep() where it was possible for endtsleep() to be executing when msleep() resumed, for endtsleep() to spin on sched_lock long enough for the other process to loop on msleep() and sleep again resulting in endtsleep() waking up the "wrong" msleep. Obtained from:BSD/OS Revision ChangesPath 1.154 +24 -4 src/sys/kern/kern_synch.c Kernels built from source immediately prior to this change work; kernels built from source immediately after this change have the sound-related problems mentioned in this thread. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sound broken on -current again...
My sound is broken as well. On both an SBLIVE card and a Yamaha OPL-SA chipset. The time frame for the breakage is definitely within the last 10 days as my previous world/kernel was from 8/5 and the current world is 8/16. On Sun, 19 Aug 2001, Maxim Sobolev wrote: > On Sat, 18 Aug 2001 21:10:40 -0500, Daniel M . Kurry wrote: > > On Wed, Aug 15, 2001 at 07:01:46PM +0200, some SMTP stream spewed forth: > > > > > > One gets the first DMA buffer full, then the process hangs... > > > > Due to the lack of replies, I'll go ahead. > > > > I am seeing sound breakage also. > > My card is a > > Creative Labs SoundBlaster Live!. > > > > xmms will play a short (less than a second) spurt of audio and then stop > > responding. mpg123 will not play (any audio to the speakers) at all. > > > > I ran a buildworld today which apparently broke it. > > That puts the breakage between today and sometime less than 2 months > > ago. > > (I really cannot be more specific.) > > > > Suggestions gladly welcomed. > > > > > > > -Søren > > The same is here (OPL3-SA driver on Toshiba Satellite Pro 445CDX notebook). > I found that after reverting the following deltas (jhb's 10 August commit) > sound starts working again: > > src/sys/i386/i386/sys_machdep.c,v 1.60 > src/sys/i386/i386/trap.c,v 1.198 > src/sys/i386/include/cpu.h,v 1.63 > src/sys/i386/isa/ipl.s,v 1.51 > src/sys/i386/isa/npx.c,v 1.108 > src/sys/kern/kern_clock.c,v 1.128 > src/sys/kern/kern_intr.c,v 1.61 > src/sys/kern/kern_lock.c,v 1.47 > src/sys/kern/kern_synch.c,v 1.155 > src/sys/kern/kern_timeout.c,v 1.69 > src/sys/kern/subr_prof.c,v 1.47 > src/sys/kern/subr_smp.c,v 1.157 > src/sys/kern/subr_trap.c,v 1.197 > src/sys/kern/subr_witness.c,v 1.82 > src/sys/posix4/ksched.c,v 1.14 > src/sys/sys/callout.h,v 1.21 > src/sys/sys/proc.h,v 1.174 > src/sys/sys/resourcevar.h,v 1.23 > > Please fix. > > -Maxim > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ 6bone: 3ffe:1ce3:7::b4ff:fe53:c297 Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sound broken on -current again...
On Sat, 18 Aug 2001 21:10:40 -0500, Daniel M . Kurry wrote: > On Wed, Aug 15, 2001 at 07:01:46PM +0200, some SMTP stream spewed forth: > > > > One gets the first DMA buffer full, then the process hangs... > > Due to the lack of replies, I'll go ahead. > > I am seeing sound breakage also. > My card is a > Creative Labs SoundBlaster Live!. > > xmms will play a short (less than a second) spurt of audio and then stop > responding. mpg123 will not play (any audio to the speakers) at all. > > I ran a buildworld today which apparently broke it. > That puts the breakage between today and sometime less than 2 months > ago. > (I really cannot be more specific.) > > Suggestions gladly welcomed. > > > > -Søren The same is here (OPL3-SA driver on Toshiba Satellite Pro 445CDX notebook). I found that after reverting the following deltas (jhb's 10 August commit) sound starts working again: src/sys/i386/i386/sys_machdep.c,v 1.60 src/sys/i386/i386/trap.c,v 1.198 src/sys/i386/include/cpu.h,v 1.63 src/sys/i386/isa/ipl.s,v 1.51 src/sys/i386/isa/npx.c,v 1.108 src/sys/kern/kern_clock.c,v 1.128 src/sys/kern/kern_intr.c,v 1.61 src/sys/kern/kern_lock.c,v 1.47 src/sys/kern/kern_synch.c,v 1.155 src/sys/kern/kern_timeout.c,v 1.69 src/sys/kern/subr_prof.c,v 1.47 src/sys/kern/subr_smp.c,v 1.157 src/sys/kern/subr_trap.c,v 1.197 src/sys/kern/subr_witness.c,v 1.82 src/sys/posix4/ksched.c,v 1.14 src/sys/sys/callout.h,v 1.21 src/sys/sys/proc.h,v 1.174 src/sys/sys/resourcevar.h,v 1.23 Please fix. -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sound broken on -current again...
This is pretty wierd... I'm running -current as of 7am this morning, and am listening to Black in Black in XMMS at this moment. SB-Live! Value, I am running SMP. Richard Todd wrote: > In servalan.mailinglist.fbsd-current Daniel M. Kurry writes: > > >>On Wed, Aug 15, 2001 at 07:01:46PM +0200, some SMTP stream spewed forth: >> >>>One gets the first DMA buffer full, then the process hangs... >>> > >>Due to the lack of replies, I'll go ahead. >> > >>I am seeing sound breakage also. >>My card is a >>Creative Labs SoundBlaster Live!. >> > >>xmms will play a short (less than a second) spurt of audio and then stop >>responding. mpg123 will not play (any audio to the speakers) at all. >> > >>I ran a buildworld today which apparently broke it. >>That puts the breakage between today and sometime less than 2 months >>ago. >>(I really cannot be more specific.) >> > > I'm seeing much the same thing, on an SMP box with onboard sbc0 (Vibra16X) > sound chip. Attempting to play sound with madplay gets about 2 seconds of > sound and then silence, with the madplay process in an unkillable kernel > wait. Oddly enough, the sbc0 interrupt thread continues to occasionally gather > a tick of CPU time, but apparently not enough to do anything useful. > > I'm busy doing binary-search on the CVS tree, checking out source from > different times and seeing if I can localize the commit that broke it. > My current results are that a kernel built from source as of > 2001/08/10 00:00 CDT (i.e. 2001/08/09 22:00:00 PDT) works, one built > from source as of 2001/08/10 15:52 PDT does not, so the bug is > somewhere in between there. I'm now trying to narrow this down further, > to a specific commit somewhere in that region. jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sound broken on -current again...
In servalan.mailinglist.fbsd-current Daniel M. Kurry writes: >On Wed, Aug 15, 2001 at 07:01:46PM +0200, some SMTP stream spewed forth: >> >> One gets the first DMA buffer full, then the process hangs... >Due to the lack of replies, I'll go ahead. >I am seeing sound breakage also. >My card is a >Creative Labs SoundBlaster Live!. >xmms will play a short (less than a second) spurt of audio and then stop >responding. mpg123 will not play (any audio to the speakers) at all. >I ran a buildworld today which apparently broke it. >That puts the breakage between today and sometime less than 2 months >ago. >(I really cannot be more specific.) I'm seeing much the same thing, on an SMP box with onboard sbc0 (Vibra16X) sound chip. Attempting to play sound with madplay gets about 2 seconds of sound and then silence, with the madplay process in an unkillable kernel wait. Oddly enough, the sbc0 interrupt thread continues to occasionally gather a tick of CPU time, but apparently not enough to do anything useful. I'm busy doing binary-search on the CVS tree, checking out source from different times and seeing if I can localize the commit that broke it. My current results are that a kernel built from source as of 2001/08/10 00:00 CDT (i.e. 2001/08/09 22:00:00 PDT) works, one built from source as of 2001/08/10 15:52 PDT does not, so the bug is somewhere in between there. I'm now trying to narrow this down further, to a specific commit somewhere in that region. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sound broken on -current again...
On Wed, Aug 15, 2001 at 07:01:46PM +0200, some SMTP stream spewed forth: > > One gets the first DMA buffer full, then the process hangs... Due to the lack of replies, I'll go ahead. I am seeing sound breakage also. My card is a Creative Labs SoundBlaster Live!. xmms will play a short (less than a second) spurt of audio and then stop responding. mpg123 will not play (any audio to the speakers) at all. I ran a buildworld today which apparently broke it. That puts the breakage between today and sometime less than 2 months ago. (I really cannot be more specific.) Suggestions gladly welcomed. > -Søren Daniel M. Kurry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
