On 10/7/07, Bill Unruh <unruh@xxxxxxxxxxxxxx> wrote: > On Sun, 7 Oct 2007, Morten Guldager wrote: > > > On 10/7/07, Rene Herman <rene.herman@xxxxxxxxxxxx> wrote: > >> On 10/06/2007 07:43 PM, Morten Guldager wrote: > >> > >>> On my kubuntu system the soundcard, soon or later, refuses to play > >>> anything but the first approx. 0.1 second of the sample repeated over and > >>> over again. > >> > >> That sounds like the IRQ stops firing. > > > > Funny thing, I have seen the same behavior on my mom's windows thing. > > It was a interrupt problem... > > > > I have noticed that when the sound is broken, the interrupts does not > > count any longer too. > > I assume you mean that /proc/interrupts entry does not increase anymore. Exactly! > So > Yes, it certainly sounds like the interrupts are broken. Whether this is > something in the sound card driver, or a hardware fault on your machine is > hard to say. What happens if you unload and then reload the sound card > driver, instead of rebooting. I have tried that. I have rmmod'ed the whole stack of sound modules and insmod'ed them all again. That did not make the sound working again. > By rebooting do you mean switch off the power to the computer, or just a > software reboot? A software reboot is enough. > >>> To fix this situation its not enough simply to logout and in again, I > >>> have to reboot the system. > >> > >> Is it a pattern where the first time takes long, and than it happens faster > >> each time? If so, I'd start suspecting heat. > > > > Don't think so. The machine runs 24/7. No powercycles, just a simple > > reboot now and then. (to get that darn music back. My old machine ran > > for years without other reboots than kernel upgrades. Even my > > girlfriends windows2000 runs more stable!) > > Well, sound is hardly a kernel crash or instability. True. But I do reboot more often then she does. And she bugs me on that account. > >>> I have tried an other soundcard, but that did not help. > > What do you mean "that does not help"? You removed this soundcard and > installed a totally different brand of soundcard? You left this one in and > used some other eg onboard soundcard? I started using the onboard thing. That were unstable, so I installed an old one instead. Ofcourse I cannot unplug the on-motherbard "soundcard". > >> I see. That certainly points to a system global problem and not so much one > >> with alsa specifically. Is the slot/card on a shared IRQ with something > >> else, and if so, are you able to correlate some action on/from that other > >> device and your sound crapping out? > > > > Initially I used the sound system on the motherboard, now its a PCI thing. > > You had the same problem with both? Oh yes :-( > > mogul@linuxine:/proc/asound$ cat cards > > 0 [AudioPCI ]: ENS1371 - Ensoniq AudioPCI > > Ensoniq AudioPCI ENS1371 at 0xac00, irq 25 > > > > Here is the interrupt list: > > > > mogul@linuxine:~$ cat /proc/interrupts > > CPU0 CPU1 > > 0: 41848540 0 IO-APIC-edge timer > > 1: 93805 0 IO-APIC-edge i8042 > > 6: 5 0 IO-APIC-edge floppy > > 7: 0 0 IO-APIC-edge parport0 > > 8: 23 0 IO-APIC-edge rtc > > 9: 0 0 IO-APIC-fasteoi acpi > > 12: 614137 0 IO-APIC-edge i8042 > > 14: 237512 0 IO-APIC-edge ide0 > > 15: 551212 1956428 IO-APIC-edge ide1 > > 18: 697954 0 IO-APIC-fasteoi uhci_hcd:usb1, eth0 > > 19: 30 0 IO-APIC-fasteoi uhci_hcd:usb2 > > 20: 1209 0 IO-APIC-fasteoi uhci_hcd:usb3, libata, > > ehci_hcd:usb5 > > 21: 100001 0 IO-APIC-fasteoi uhci_hcd:usb4 > > 22: 0 0 IO-APIC-fasteoi libata > > 23: 0 0 IO-APIC-fasteoi libata > > 24: 24429478 0 IO-APIC-fasteoi nvidia > > 25: 2500176 0 IO-APIC-fasteoi Ensoniq AudioPCI > > NMI: 0 0 > > LOC: 41844808 41846704 > > ERR: 0 > > MIS: 0 > > > > Looks like irq25, and alone there. > > > >>> Synaptic told me that alsa-base is version 1.0.13-3 > >>> The system is a Intel dual-core thing, if that does matter. > >>> How do I debug this? What do you need to know to help me here? > > You could of course try alsa 1.0.15 instead. Make sure you have your > kernel-source installed in /usr/src for your current kernel, and have gcc > installed, download the alsa-drvers go into the directory and do > ./configure > make > make install > > which should install the new drivers. But if I do have an interrupt problem in the machine, then I won't fix anything with a new alsa, wouldt I? I found a few of these in /var/log/messages: Oct 1 20:13:48 linuxine kernel: [ 720.753330] [__report_bad_irq+36/128] __report_bad_irq+0x24/0x80 Oct 1 20:13:48 linuxine kernel: [ 720.753354] [note_interrupt+606/656] note_interrupt+0x25e/0x290 Oct 1 20:13:48 linuxine kernel: [ 720.753378] [<f888af32>] usb_hcd_irq+0x22/0x60 [usbcore] Oct 1 20:13:48 linuxine kernel: [ 720.753405] [handle_IRQ_event+48/96] handle_IRQ_event+0x30/0x60 Oct 1 20:13:48 linuxine kernel: [ 720.753422] [handle_fasteoi_irq+193/240] handle_fasteoi_irq+0xc1/0xf0 Oct 1 20:13:48 linuxine kernel: [ 720.753440] [do_IRQ+64/128] do_IRQ+0x40/0x80 Oct 1 20:13:48 linuxine kernel: [ 720.753459] [common_interrupt+35/48] common_interrupt+0x23/0x30 Oct 1 20:13:48 linuxine kernel: [ 720.753496] [__do_softirq+91/256] __do_softirq+0x5b/0x100 Oct 1 20:13:48 linuxine kernel: [ 720.753524] [do_softirq+85/96] do_softirq+0x55/0x60 Oct 1 20:13:48 linuxine kernel: [ 720.753533] [do_IRQ+69/128] do_IRQ+0x45/0x80 Oct 1 20:13:48 linuxine kernel: [ 720.753552] [common_interrupt+35/48] common_interrupt+0x23/0x30 Oct 1 20:13:48 linuxine kernel: [ 720.753587] [mwait_idle_with_hints+70/96] mwait_idle_with_hints+0x46/0x60 Oct 1 20:13:48 linuxine kernel: [ 720.753607] [cpu_idle+73/208] cpu_idle+0x49/0xd0 Oct 1 20:13:48 linuxine kernel: [ 720.753621] [start_kernel+869/1056] start_kernel+0x365/0x420 Oct 1 20:13:48 linuxine kernel: [ 720.753631] [unknown_bootoption+0/608] unknown_bootoption+0x0/0x260 Oct 1 20:13:48 linuxine kernel: [ 720.753665] ======================= I don't understand much, but it looks like something with interrupts too. At the moment I am trying the "irqpoll" kernel option... time will show then. -- /Morten %-) ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Alsa-user mailing list Alsa-user@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/alsa-user
