Re: [LAU] hdsp not happy with recent kernels

From: <peter@email-addr-hidden>
Date: Mon Sep 17 2012 - 16:25:58 EEST

> On 09/15/2012 01:25 PM, peter@email-addr-hidden wrote:

>> so, avoiding the irq conflict by unloading firewire modules doesn't solve
>> the problem. mrph.
> Argh, that seemed like a good lead...
> What does "cat /proc/interrupts" show? I think the interrupt count for
each cpu should increment. Does it?

for a kernel under which jack fails:
root@email-addr-hidden:/home/plutek# cat /proc/interrupts
           CPU0 CPU1 CPU2 CPU3
  0: 43 0 0 0 IO-APIC-edge timer
1: 9 0 0 0 IO-APIC-edge i8042
8: 1 0 0 0 IO-APIC-edge rtc0
9: 734 0 0 0 IO-APIC-fasteoi acpi
 12: 2502 0 0 0 IO-APIC-edge i8042
16: 28 0 0 0 IO-APIC-fasteoi mmc0,
ehci_hcd:usb1
 17: 0 0 0 0 IO-APIC-fasteoi
rtlwifi
 19: 1 0 0 0 IO-APIC-fasteoi
firewire_ohci, snd_hdsp
 23: 1855 0 0 0 IO-APIC-fasteoi
ehci_hcd:usb2
 40: 939 0 0 0 PCI-MSI-edge eth0
41: 14407 0 0 0 PCI-MSI-edge ahci
42: 341 0 0 0 PCI-MSI-edge
snd_hda_intel
 43: 3975 0 0 0 PCI-MSI-edge i915
NMI: 12 2 13 3 Non-maskable interrupts
LOC: 22030 9369 22762 8398 Local timer interrupts
SPU: 0 0 0 0 Spurious interrupts
PMI: 12 2 13 3 Performance monitoring
interrupts
IWI: 0 0 0 0 IRQ work interrupts
RES: 1012 1465 1348 1568 Rescheduling interrupts
CAL: 636 665 426 753 Function call
interrupts
TLB: 552 534 338 386 TLB shootdowns
TRM: 0 0 0 0 Thermal event
interrupts
THR: 0 0 0 0 Threshold APIC
interrupts
MCE: 0 0 0 0 Machine check
exceptions
MCP: 57 57 57 59 Machine check polls
ERR: 0
MIS: 0

and for the kernel under which jack runs fine:
root@email-addr-hidden:/home/plutek# cat /proc/interrupts
           CPU0 CPU1 CPU2 CPU3
  0: 124 0 0 0 IO-APIC-edge timer
  1: 8 0 0 0 IO-APIC-edge i8042
  8: 1 0 0 0 IO-APIC-edge rtc0
  9: 731 0 0 0 IO-APIC-fasteoi acpi
 12: 2501 0 0 0 IO-APIC-edge i8042
 16: 159 0 0 0 IO-APIC-fasteoi
ehci_hcd:usb1, mmc0, mei
 17: 0 0 0 0 IO-APIC-fasteoi rtlwifi
 19: 0 0 0 0 IO-APIC-fasteoi snd_hdsp
 23: 484 0 0 0 IO-APIC-fasteoi
ehci_hcd:usb2
 40: 240 0 0 0 PCI-MSI-edge eth0
 41: 5 0 0 0 PCI-MSI-edge
firewire_ohci
 42: 11334 0 0 0 PCI-MSI-edge ahci
 43: 503 0 0 0 PCI-MSI-edge
snd_hda_intel
 44: 2171 0 0 0 PCI-MSI-edge i915
NMI: 0 0 0 0 Non-maskable interrupts
LOC: 18709 15972 13871 12078 Local timer interrupts
SPU: 0 0 0 0 Spurious interrupts
PMI: 0 0 0 0 Performance monitoring
interrupts
IWI: 0 0 0 0 IRQ work interrupts
RES: 12558 5658 12784 13897 Rescheduling interrupts
CAL: 162 195 300 249 Function call interrupts
TLB: 320 538 365 855 TLB shootdowns
TRM: 0 0 0 0 Thermal event interrupts
THR: 0 0 0 0 Threshold APIC interrupts
MCE: 0 0 0 0 Machine check exceptions
MCP: 2 2 2 2 Machine check polls
ERR: 0
MIS: 0

not sure what you mean by "the interrupt count for each cpu should
increment", but i don't think i'm seeing anything that looks like that.

> Sorry, don't quite know where to go from here, looks like something for
kernel gurus in lkml...
> -- Fernando

well, we'll see if anything comes out of the above first.... i'm kinda
busy this week to engage a discussion with a bunch of kernel devs!

thanks again... cheers!
.pltk.

_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@email-addr-hidden
http://lists.linuxaudio.org/listinfo/linux-audio-user
Received on Mon Sep 17 20:15:01 2012

This archive was generated by hypermail 2.1.8 : Mon Sep 17 2012 - 20:15:01 EEST