Re: sound driver breakage/megapatch

2001-04-20 Thread Cameron Grant

 Apr 19 15:09:31 zorba /boot/kernel/kernel: pcm0: play interrupt timeout,
channel dead
 Apr 19 15:19:00 zorba /boot/kernel/kernel: pcm0: play interrupt timeout,
channel dead

can anyone suffering from this problem confirm that the hardware is
generating interrupts?

use 'systat -vm 1' to watch while you try to play sound.

-cg



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: sound driver breakage/megapatch

2001-04-20 Thread Szilveszter Adam

Hello,

When was this megapatch? I have a kernel  world from evening of 18th CEST,
and my SB 64 AWE rocks as usual. I even figured out, how to play Shoutcast
streams with mpg123 which enabled me to listen to my favourite radio on the
console:-) Doing it right now:-)

-- 
Regards:

Szilveszter ADAM
Szeged University
Szeged Hungary

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: sound driver breakage/megapatch

2001-04-20 Thread Daniel

No, it's not generating interrupts.

On Fri, 20 Apr 2001, Cameron Grant wrote:

 Date: Fri, 20 Apr 2001 17:06:58 +0100
 From: Cameron Grant [EMAIL PROTECTED]
 To: Scott Hazen Mueller [EMAIL PROTECTED], [EMAIL PROTECTED]
 Subject: Re: sound driver breakage/megapatch

  Apr 19 15:09:31 zorba /boot/kernel/kernel: pcm0: play interrupt timeout,
 channel dead
  Apr 19 15:19:00 zorba /boot/kernel/kernel: pcm0: play interrupt timeout,
 channel dead

 can anyone suffering from this problem confirm that the hardware is
 generating interrupts?

 use 'systat -vm 1' to watch while you try to play sound.

 -cg



 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with "unsubscribe freebsd-current" in the body of the message




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: sound driver breakage/megapatch

2001-04-20 Thread Scott Hazen Mueller

 Apr 19 15:09:31 zorba /boot/kernel/kernel: pcm0: play interrupt timeout,
channel dead
 Apr 19 15:19:00 zorba /boot/kernel/kernel: pcm0: play interrupt timeout,
channel dead

can anyone suffering from this problem confirm that the hardware is
generating interrupts?

use 'systat -vm 1' to watch while you try to play sound.

Oh, sorry - yes, I can...  I watched the pcm interrupt (irq 9 on my box)
increment using vmstat -i.  I had seen something in the archives about that
not happening.

   \scott


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: sound driver breakage/megapatch

2001-04-20 Thread Cameron Grant


 Oh, sorry - yes, I can...  I watched the pcm interrupt (irq 9 on my box)
 increment using vmstat -i.  I had seen something in the archives about
that
 not happening.

is there any other device using irq 9?

-cg



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: sound driver breakage/megapatch

2001-04-20 Thread Scott Hazen Mueller

 Oh, sorry - yes, I can...  I watched the pcm interrupt (irq 9 on my box)
 increment using vmstat -i.  I had seen something in the archives about
that
 not happening.

is there any other device using irq 9?

vmstat -i

interrupt  total  rate
stray irq0  10
stray irq6  10
stray irq7  10
stray irq15 10
ata0 irq14  212797
ata1 irq15  40
atkbd0 irq1  75692
psm0 irq12  27669   10
fdc0 irq6   10
clk irq0   272328  100
ep0 irq5   122422   44
Total  451276  165

[Sound driver is currently not loaded.  Putting the .ko files into
loader.conf.local hangs the system during boot?  Dunno if this is a clue or
no.]

grep "irq.*9" /var/log/messages

Apr 16 09:46:07 zorba /boot/kernel/kernel: pci0: NeoMagic MagicMedia 256AV SVGA 
controller at 8.0 irq 9
Apr 16 09:46:07 zorba /boot/kernel/kernel: pcm0: NeoMagic 256AV mem 
0xfec0-0xfecf,0xfe00-0xfe3f irq 9 at device 8.1 on pci0
Apr 17 10:01:53 zorba /boot/kernel/kernel: pci0: NeoMagic MagicMedia 256AV SVGA 
controller at 8.0 irq 9
Apr 17 10:01:53 zorba /boot/kernel/kernel: pcm0: NeoMagic 256AV mem 
0xfec0-0xfecf,0xfe00-0xfe3f irq 9 at device 8.1 on pci0
Apr 18 10:10:45 zorba /boot/kernel/kernel: pci0: NeoMagic MagicMedia 256AV SVGA 
controller at 8.0 irq 9
Apr 18 10:10:45 zorba /boot/kernel/kernel: pcm0: NeoMagic 256AV mem 
0xfec0-0xfecf,0xfe00-0xfe3f irq 9 at device 8.1 on pci0
Apr 19 14:44:30 zorba /boot/kernel/kernel: pcm0: NeoMagic 256AV mem 
0xfec0-0xfecf,0xfe00-0xfe3f irq 9 at device 8.1 on pci0
Apr 19 15:31:00 zorba /boot/kernel/kernel: pcm0: NeoMagic 256AV mem 
0xfec0-0xfecf,0xfe00-0xfe3f irq 9 at device 8.1 on pci0
Apr 19 15:53:00 zorba /boot/kernel/kernel: pcm0: NeoMagic 256AV mem 
0xfec0-0xfecf,0xfe00-0xfe3f irq 9 at device 8.1 on pci0
Apr 19 18:47:21 zorba /boot/kernel/kernel: pcm0: NeoMagic 256AV mem 
0xfec0-0xfecf,0xfe00-0xfe3f irq 9 at device 8.1 on pci0

I'm pretty sure not.

   \scott


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: sound driver breakage/megapatch

2001-04-20 Thread Daniel

I'm sorry, I was wrong, I have the same problem that Scott:

# vmstat -i
interrupt  total  rate
stray irq0  10
stray irq6  10
stray irq7  10
ata0 irq14 337983   15
ata1 irq15 200
fdc0 irq6   10
atkbd0 irq1 462472
psm0 irq12  229981
clk irq0  2185682   99
rtc irq8  2797782  128
sio1 irq3  251802   11
ed1 irq11   317241
Total 5674242  259

# dmesg |grep "irq 9"
pcm0: Yamaha DS-1E (YMF744) mem 0xfedf-0xfedf7fff irq 9 at device 9.0 on pci0

daniel.-

On Fri, 20 Apr 2001, Daniel wrote:

 Date: Fri, 20 Apr 2001 17:40:45 -0300 (ART)
 From: Daniel [EMAIL PROTECTED]
 To: Cameron Grant [EMAIL PROTECTED]
 Cc: Scott Hazen Mueller [EMAIL PROTECTED], [EMAIL PROTECTED]
 Subject: Re: sound driver breakage/megapatch

 No, it's not generating interrupts.

 On Fri, 20 Apr 2001, Cameron Grant wrote:

  Date: Fri, 20 Apr 2001 17:06:58 +0100
  From: Cameron Grant [EMAIL PROTECTED]
  To: Scott Hazen Mueller [EMAIL PROTECTED], [EMAIL PROTECTED]
  Subject: Re: sound driver breakage/megapatch
 
   Apr 19 15:09:31 zorba /boot/kernel/kernel: pcm0: play interrupt timeout,
  channel dead
   Apr 19 15:19:00 zorba /boot/kernel/kernel: pcm0: play interrupt timeout,
  channel dead
 
  can anyone suffering from this problem confirm that the hardware is
  generating interrupts?
 
  use 'systat -vm 1' to watch while you try to play sound.
 
  -cg
 
 
 
  To Unsubscribe: send mail to [EMAIL PROTECTED]
  with "unsubscribe freebsd-current" in the body of the message
 
 


 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with "unsubscribe freebsd-current" in the body of the message





To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: sound driver breakage/megapatch

2001-04-19 Thread User

On Thu, Apr 19, 2001 at 04:02:18PM -0700, Scott Hazen Mueller wrote:
 It looks like the recent sound driver megapatch broke (at least) the Neomagic
 256AV driver.  With a cvsup from yesterday, trying to do play mp3 files got
 trash that was vaguely recognizable as a seriously distorted version of the
 original piece.  I did some trolling of the cvsweb and decided to roll back to
 a fixed date (2001.03.24.00.00.00) before the megapatch.  I've rebuilt the
 .ko files and unloaded/reloaded them; I now have working sound.
 
 The failing sound also generated this error
 
 Apr 19 15:09:31 zorba /boot/kernel/kernel: pcm0: play interrupt timeout, channel dead
 Apr 19 15:19:00 zorba /boot/kernel/kernel: pcm0: play interrupt timeout, channel dead
 
 The probe message "before" (removing megapatch) -
 
 Apr 19 15:31:00 zorba /boot/kernel/kernel: pcm0: NeoMagic 256AV mem 
0xfec0-0xfecf,0xfe00-0xfe3f irq 9 at device 8.1 on pci0
 
 The probe message "after" (removing megapatch) -
 
 Apr 19 15:53:00 zorba /boot/kernel/kernel: pcm0: NeoMagic 256AV mem 
0xfec0-0xfecf,0xfe00-0xfe3f irq 9 at device 8.1 on pci0
 
 And, somewhere in here, "hwintr went backwards" went away.
 
 Hope this helps.
Same thing here with Creative AWE64 PnP ISA sound card. 

pcm1: play interrupt timeout, channel dead
pcm1: play interrupt timeout, channel dead

sbc0: Creative SB AWE64 at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on 
isa0
pcm1: SB16 DSP 4.16 on sbc0

FreeBSD enia.bastun.net 5.0-CURRENT FreeBSD 5.0-CURRENT #19: Thu Apr 19 19:40:03 EEST 
2001 [EMAIL PROTECTED]:/usr/src/sys/compile/ENIA  i386

Boris Georgiev

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: sound driver breakage/megapatch

2001-04-19 Thread Daniel

I have the same problem on a Sony VAIO PCG-XG38 running -current

pcm0: Yamaha DS-1E (YMF744) mem 0xfedf-0xfedf7fff irq 9 at device 9.0 on pci0

daniel.-

On Thu, 19 Apr 2001, Scott Hazen Mueller wrote:

 Date: Thu, 19 Apr 2001 16:02:18 -0700 (PDT)
 From: Scott Hazen Mueller [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Subject: sound driver breakage/megapatch

 It looks like the recent sound driver megapatch broke (at least) the Neomagic
 256AV driver.  With a cvsup from yesterday, trying to do play mp3 files got
 trash that was vaguely recognizable as a seriously distorted version of the
 original piece.  I did some trolling of the cvsweb and decided to roll back to
 a fixed date (2001.03.24.00.00.00) before the megapatch.  I've rebuilt the
 .ko files and unloaded/reloaded them; I now have working sound.

 The failing sound also generated this error

 Apr 19 15:09:31 zorba /boot/kernel/kernel: pcm0: play interrupt timeout, channel dead
 Apr 19 15:19:00 zorba /boot/kernel/kernel: pcm0: play interrupt timeout, channel dead

 The probe message "before" (removing megapatch) -

 Apr 19 15:31:00 zorba /boot/kernel/kernel: pcm0: NeoMagic 256AV mem 
0xfec0-0xfecf,0xfe00-0xfe3f irq 9 at device 8.1 on pci0

 The probe message "after" (removing megapatch) -

 Apr 19 15:53:00 zorba /boot/kernel/kernel: pcm0: NeoMagic 256AV mem 
0xfec0-0xfecf,0xfe00-0xfe3f irq 9 at device 8.1 on pci0

 And, somewhere in here, "hwintr went backwards" went away.

 Hope this helps.

   \scott


 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with "unsubscribe freebsd-current" in the body of the message






To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message