Re: 2.4.4 Sound corruption

From: Charl P. Botha (c.p.botha@its.tudelft.nl)
Date: Sun Apr 29 2001 - 18:29:15 EST


FWIW, I have established that my sound broke between 2.4.4-pre5 and
2.4.4-pre6. I.e. in pre5 it works and in pre6 it doesn't, same .config. If
anyone has any clues, I'd be glad to know.

On Sun, Apr 29, 2001 at 04:55:01PM +0200, Charl P. Botha wrote:
> 2.4.4 has broken sound here in a very strange way. I have a debian testing
> system, Abit KT7 (thus VIA KT133 chipset) and SB PC128 (es1371-based) sound
> card.
>
> Up until 2.4.3 everything was fine. Now, however, when I send _anything_ to
> /dev/dsp, I get continuous high-pitched beeping (nothing remotely resembling
> what the sound card should be doing).
>
> The strange thing is that when I cause hard disk activity (find / -name "*")
> the correct sound is produced in time with hard disc accesses (I have tried
> this with DMA enabled and disabled on the drive, same results). Also, when I
> switch desktops (icewm, XFree86 4.0.2, Nvidia 0.9.767 drivers) the correct
> sound is (very) momentarily produced (almost non-detectibly). After these
> periods of lucidity, the sound card returns to its high-pitched cacophony.
>
> I have attached copies of both /proc/interrupts and /proc/pci. If anyone
> requires more information, please say the word. I am not subscribed to this
> list.
>
> Best regards,
>
> --
> charl p. botha | computer graphics and cad/cam
> http://cpbotha.net/ | http://www.cg.its.tudelft.nl/

> CPU0
> 0: 320161 XT-PIC timer
> 1: 19658 XT-PIC keyboard
> 2: 0 XT-PIC cascade
> 8: 1 XT-PIC rtc
> 9: 0 XT-PIC usb-uhci, usb-uhci
> 10: 272660 XT-PIC nvidia
> 11: 93973 XT-PIC eth0, es1371
> 12: 42760 XT-PIC PS/2 Mouse
> 14: 39388 XT-PIC ide0
> 15: 5 XT-PIC ide1
> NMI: 0
> ERR: 0

> PCI devices found:
> Bus 0, device 0, function 0:
> Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] (rev 3).
> Prefetchable 32 bit memory at 0xd8000000 [0xdbffffff].
> Bus 0, device 1, function 0:
> PCI bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP] (rev 0).
> Master Capable. No bursts. Min Gnt=12.
> Bus 0, device 7, function 0:
> ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 34).
> Bus 0, device 7, function 1:
> IDE interface: VIA Technologies, Inc. Bus Master IDE (rev 16).
> Master Capable. Latency=32.
> I/O at 0xd000 [0xd00f].
> Bus 0, device 7, function 2:
> USB Controller: VIA Technologies, Inc. UHCI USB (rev 16).
> IRQ 9.
> Master Capable. Latency=32.
> I/O at 0xd400 [0xd41f].
> Bus 0, device 7, function 3:
> USB Controller: VIA Technologies, Inc. UHCI USB (#2) (rev 16).
> IRQ 9.
> Master Capable. Latency=32.
> I/O at 0xd800 [0xd81f].
> Bus 0, device 7, function 4:
> Host bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 48).
> IRQ 11.
> Bus 0, device 8, function 0:
> Multimedia video controller: Brooktree Corporation Bt878 (rev 17).
> IRQ 9.
> Master Capable. Latency=32. Min Gnt=16.Max Lat=40.
> Prefetchable 32 bit memory at 0xde000000 [0xde000fff].
> Bus 0, device 8, function 1:
> Multimedia controller: Brooktree Corporation Bt878 (rev 17).
> IRQ 9.
> Master Capable. Latency=32. Min Gnt=4.Max Lat=255.
> Prefetchable 32 bit memory at 0xde001000 [0xde001fff].
> Bus 0, device 9, function 0:
> Ethernet controller: Accton Technology Corporation SMC2-1211TX (rev 16).
> IRQ 11.
> Master Capable. Latency=32. Min Gnt=32.Max Lat=64.
> I/O at 0xdc00 [0xdcff].
> Non-prefetchable 32 bit memory at 0xde002000 [0xde0020ff].
> Bus 0, device 13, function 0:
> Multimedia audio controller: Ensoniq ES1371 [AudioPCI-97] (rev 8).
> IRQ 11.
> Master Capable. Latency=32. Min Gnt=12.Max Lat=128.
> I/O at 0xe000 [0xe03f].
> Bus 1, device 0, function 0:
> VGA compatible controller: nVidia Corporation NV11 (rev 161).
> IRQ 10.
> Master Capable. Latency=248. Min Gnt=5.Max Lat=1.
> Non-prefetchable 32 bit memory at 0xdc000000 [0xdcffffff].
> Prefetchable 32 bit memory at 0xd0000000 [0xd7ffffff].

-- 
charl p. botha      | computer graphics and cad/cam 
http://cpbotha.net/ | http://www.cg.its.tudelft.nl/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Mon Apr 30 2001 - 21:00:23 EST