13 Oct
2014
13 Oct
'14
12:29 p.m.
The problem has occurred since motherboard was replaced (Gigabyte),
system was working well prior to this.
As soon as jackd is started via qjackctl I get many of the errors in
subject line above.
ps | grep jackd :
/usr/bin/jackd -t1000 -dalsa -dhw:VSL -r48000 -p128 -n2 -s -H -Xseq
Trying to run an application e.g. yoshimi, ardour3 I then get multiple
entries in the qjackctl message window :
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = yoshimi was not finished, state = Triggered
Kernel is stock debian modified for full preemption (not rt)
debian 3.14.4preempt #1 SMP PREEMPT
Interface:
usb 3-1: new high-speed USB device number 7 using ehci-pci
[364612.507648] usb 3-1: New USB device found, idVendor=194f, idProduct=0103
[364612.507652] usb 3-1: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[364612.507654] usb 3-1: Product: AudioBox 1818 VSL
[364612.507655] usb 3-1: Manufacturer: PreSonus
[364612.507656] usb 3-1: SerialNumber: 2209
lsusb
Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 011 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 010 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 009 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 007: ID 194f:0103 PreSonus Audio Electronics, Inc.
AudioBox 1818 VSL
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 004: ID 040b:0a68 Weltrend Semiconductor
Bus 008 Device 002: ID 046a:0021 Cherry GmbH CyMotion Expert Combo
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Interrupts:
CPU0 CPU1 CPU2 CPU3 CPU4 CPU5 CPU6 CPU7
0: 130 0 0 0 0 0 0 0 IR-IO-APIC-edge timer
1: 0 0 0 0 0 0 0 2 IR-IO-APIC-edge i8042
7: 1 0 0 0 0 0 0 0 IR-IO-APIC-edge
8: 8 8 5 4 4 12 9 15 IR-IO-APIC-edge rtc0
9: 0 0 0 0 0 0 0 0 IR-IO-APIC-fasteoi acpi
12: 1 0 0 0 1 0 0 2 IR-IO-APIC-edge i8042
17: 830241 830214 829782 831028 830196 830496 831329 840848
IR-IO-APIC-fasteoi ehci_hcd:usb3, ehci_hcd:usb5, ehci_hcd:usb6
18: 391461 392006 391735 392072 391747 391486
395291 417634 IR-IO-APIC-fasteoi ohci_hcd:usb8,ohci_hcd:usb9,
ohci_hcd:usb10, ohci_hcd:usb11
19: 319442 319430 319790 319565 319317 319829 320730 327699
IR-IO-APIC-fasteoi ahci
22: 0 0 0 0 0 0 0 1 IR-IO-APIC-fasteoi firewire_ohci
72: 0 0 0 0 0 0 0 0 IR-PCI-MSI-edge AMD-Vi
73: 48 49 49 48 49 49 48 49 IR-PCI-MSI-edge xhci_hcd
74: 733818 733886 733147 733825 734519 734499 741140 790575
IR-PCI-MSI-edge eth1
75: 0 0 0 0 0 0 0 0 IR-PCI-MSI-edge xhci_hcd
76: 0 0 0 0 0 0 0 0 IR-PCI-MSI-edge ahci
77: 0 0 1 0 0 0 1 1 IR-PCI-MSI-edge ahci
78: 15448840 15450773 15449909 15451237 15449687 15458353 15482710
15668009 IR-PCI-MSI-edge nouveau
NMI: 35721 35582 35689 35580 35621 35674 35740 35651 Non-maskable interrupts
LOC: 370545535 366577898 371254574 367825377 370125299 365645165
370470914 367806812 Local timer interrupts
SPU: 0 0 0 0 0 0 0 0 Spurious interrupts
PMI: 35721 35582 35689 35580 35621 35674 35740 35651 Performance
monitoring interrupts
IWI: 2097907 1222061 2103662 1296384 1868198 1098517 2039127 1317112 IRQ
work interrupts
RTR: 0 0 0 0 0 0 0 0 APIC ICR read retries
RES: 108086979 77504950 112037290 81816890 96000287 79564150
105873693 87064029 Rescheduling interrupts
CAL: 941 1009 1032 1038 1072 1095 1003 1041 Function call interrupts
TLB: 397622 365135 411737 385317 416611 300751 381127 326195 TLB shootdowns
THR: 0 0 0 0 0 0 0 0 Threshold APIC interrupts
MCE: 0 0 0 0 0 0 0 0 Machine check exceptions
MCP: 1220 1220 1220 1220 1220 1220 1220 1220 Machine check polls
ERR: 1
MIS: 0
I've tried different usb2 sockets but no change.
I tried using usb3 sockets but got a different error :
unexpected command completion code 0x11
Any help appreciated
Thanks
rob
13 Oct
13 Oct
12:48 p.m.
The message in the subject means that the driver logged some error
message repeatedly, and that the duplicates were suppressed.
The actual error message (before that) would be useful.
Regards,
Clemens
1:53 p.m.
On 13/10/14 11:48, Clemens Ladisch wrote:
The message in the subject means that the driver
logged some error
message repeatedly, and that the duplicates were suppressed.
The actual error message (before that) would be useful.
Regards,
Clemens
There isn't preceding message
from syslog :
Oct 13 11:47:46 debian dnsmasq[3465]: reading /etc/resolv.conf
Oct 13 11:47:46 debian dnsmasq[3465]: using nameserver 192.168.178.1#53
Oct 13 12:08:46 debian acpid: client connected from 8202[1001:1001]
Oct 13 12:08:46 debian acpid: 1 client rule loaded
Oct 13 12:17:01 debian /USR/SBIN/CRON[11997]: (root) CMD ( cd / &&
run-parts --report /etc/cron.hourly)
Oct 13 12:36:00 debian kernel: [371346.915918] retire_capture_urb: 13960
callbacks suppressed
Oct 13 12:36:05 debian kernel: [371351.975159] retire_capture_urb: 31944
callbacks suppressed
Oct 13 12:36:10 debian kernel: [371357.022838] retire_capture_urb: 32053
callbacks suppressed
Oct 13 12:36:15 debian kernel: [371362.089701] retire_capture_urb: 31962
callbacks suppressed
Oct 13 12:36:20 debian kernel: [371367.129415] retire_capture_urb: 32068
callbacks suppressed
Oct 13 12:36:25 debian kernel: [371372.203356] retire_capture_urb: 31613
callbacks suppressed
Oct 13 12:36:30 debian kernel: [371377.236139] retire_capture_urb: 31959
callbacks suppressed
Oct 13 12:36:35 debian kernel: [371382.319187] retire_capture_urb: 31742
callbacks suppressed
Oct 13 12:36:40 debian kernel: [371387.342876] retire_capture_urb: 32271
callbacks suppressed
Oct 13 12:36:46 debian kernel: [371392.432545] retire_capture_urb: 31773
callbacks suppressed
I forgot to mention kernel is started with threadirqs
10:30 p.m.
On 13/10/14 12:54, rob wrote:
On 13/10/14 11:48, Clemens Ladisch wrote:
I was using jackd2. I've now tried jackd1 which works without the
problem. Maybe something to do with dbus?
Thanks
rob
The message in the subject means that the driver
logged some error
message repeatedly, and that the duplicates were suppressed.
The actual error message (before that) would be useful.
Regards,
Clemens
There isn't preceding message
from syslog :
Oct 13 11:47:46 debian dnsmasq[3465]: reading /etc/resolv.conf
Oct 13 11:47:46 debian dnsmasq[3465]: using nameserver 192.168.178.1#53
Oct 13 12:08:46 debian acpid: client connected from 8202[1001:1001]
Oct 13 12:08:46 debian acpid: 1 client rule loaded
Oct 13 12:17:01 debian /USR/SBIN/CRON[11997]: (root) CMD ( cd / &&
run-parts --report /etc/cron.hourly)
Oct 13 12:36:00 debian kernel: [371346.915918] retire_capture_urb: 13960
callbacks suppressed
Oct 13 12:36:05 debian kernel: [371351.975159] retire_capture_urb: 31944
callbacks suppressed
Oct 13 12:36:10 debian kernel: [371357.022838] retire_capture_urb: 32053
callbacks suppressed
Oct 13 12:36:15 debian kernel: [371362.089701] retire_capture_urb: 31962
callbacks suppressed
Oct 13 12:36:20 debian kernel: [371367.129415] retire_capture_urb: 32068
callbacks suppressed
Oct 13 12:36:25 debian kernel: [371372.203356] retire_capture_urb: 31613
callbacks suppressed
Oct 13 12:36:30 debian kernel: [371377.236139] retire_capture_urb: 31959
callbacks suppressed
Oct 13 12:36:35 debian kernel: [371382.319187] retire_capture_urb: 31742
callbacks suppressed
Oct 13 12:36:40 debian kernel: [371387.342876] retire_capture_urb: 32271
callbacks suppressed
Oct 13 12:36:46 debian kernel: [371392.432545] retire_capture_urb: 31773
callbacks suppressed
I forgot to mention kernel is started with threadirqs
_______________________________________________
11:48 p.m.
On 13/10/14 21:31, rob wrote:
On 13/10/14 12:54, rob wrote:
I spoke too soon. Same error with jackd1, just takes sometime to start.
The qjackctl messages are different multiple
delay of 29465.000 usecs exceeds estimated spare time of 5224.000;
restart ...
Going to try kxstudio livedvd to see if it happens there.
rob
On 13/10/14 11:48, Clemens Ladisch wrote:
I was using jackd2. I've now tried jackd1 which works without the
problem. Maybe something to do with dbus?
Thanks
rob
The message in the subject means that the driver
logged some error
message repeatedly, and that the duplicates were suppressed.
The actual error message (before that) would be useful.
Regards,
Clemens
There isn't preceding message
from syslog :
Oct 13 11:47:46 debian dnsmasq[3465]: reading /etc/resolv.conf
Oct 13 11:47:46 debian dnsmasq[3465]: using nameserver 192.168.178.1#53
Oct 13 12:08:46 debian acpid: client connected from 8202[1001:1001]
Oct 13 12:08:46 debian acpid: 1 client rule loaded
Oct 13 12:17:01 debian /USR/SBIN/CRON[11997]: (root) CMD ( cd / &&
run-parts --report /etc/cron.hourly)
Oct 13 12:36:00 debian kernel: [371346.915918] retire_capture_urb: 13960
callbacks suppressed
Oct 13 12:36:05 debian kernel: [371351.975159] retire_capture_urb: 31944
callbacks suppressed
Oct 13 12:36:10 debian kernel: [371357.022838] retire_capture_urb: 32053
callbacks suppressed
Oct 13 12:36:15 debian kernel: [371362.089701] retire_capture_urb: 31962
callbacks suppressed
Oct 13 12:36:20 debian kernel: [371367.129415] retire_capture_urb: 32068
callbacks suppressed
Oct 13 12:36:25 debian kernel: [371372.203356] retire_capture_urb: 31613
callbacks suppressed
Oct 13 12:36:30 debian kernel: [371377.236139] retire_capture_urb: 31959
callbacks suppressed
Oct 13 12:36:35 debian kernel: [371382.319187] retire_capture_urb: 31742
callbacks suppressed
Oct 13 12:36:40 debian kernel: [371387.342876] retire_capture_urb: 32271
callbacks suppressed
Oct 13 12:36:46 debian kernel: [371392.432545] retire_capture_urb: 31773
callbacks suppressed
I forgot to mention kernel is started with threadirqs
_______________________________________________
17 Oct
17 Oct
3:36 p.m.
New subject: retire_capture_urb: 19662 callbacks suppressed [ADD.INFO]
On 13/10/14 22:48, rob wrote:
On 13/10/14 21:31, rob wrote:
KXstudio worked which should rule out hardware.
Interestingly going back to Debian, after a couple of KX sessions, the
problem disappeared for 2 days.
Today it started again. This time some further info appeared in syslog
which may be relevant:
] CPU: 1 PID: 135 Comm: irq/17-ehci_hcd Not tainted 3.14.4preempt #1
[194597.086617] Hardware name: Gigabyte Technology Co., Ltd. To be
filled by O.E.M./990FXA-UD5, BIOS FB 01/23/2013
[194597.086619] ffff880321b70ebc ffffffff814d0ea9 ffff880321b70e00
ffffffff810a2148
[194597.086622] ffff880321b70e00 0000000000000011 ffff880321b70e00
ffffffff810a25d5
[194597.086624] ffffffff810594cf ffff88031f4df270 ffff88031ed2a280
ffff880321b70e00
[194597.086626] Call Trace:
[194597.086632] [<ffffffff814d0ea9>] ? dump_stack+0x4a/0x75
[194597.086635] [<ffffffff810a2148>] ? __report_bad_irq+0x28/0xc0
[194597.086637] [<ffffffff810a25d5>] ? note_interrupt+0x1b5/0x210
[194597.086640] [<ffffffff810594cf>] ? __local_bh_enable_ip+0x3f/0xa0
[194597.086642] [<ffffffff810a08f0>] ? irq_thread_fn+0x40/0x40
[194597.086644] [<ffffffff810a0e15>] ? irq_thread+0x135/0x140
[194597.086646] [<ffffffff810a0970>] ? wake_threads_waitq+0x30/0x30
[194597.086647] [<ffffffff810a0ce0>] ? irq_thread_check_affinity+0xb0/0xb0
[194597.086650] [<ffffffff81075321>] ? kthread+0xc1/0xe0
[194597.086652] [<ffffffff81075260>] ? kthread_create_on_node+0x180/0x180
[194597.086654] [<ffffffff814de00c>] ? ret_from_fork+0x7c/0xb0
[194597.086656] [<ffffffff81075260>] ? kthread_create_on_node+0x180/0x180
[194597.086658] handlers:
[194597.086660] [<ffffffff810a0250>] irq_default_primary_handler
threaded [<ffffffffa000e520>] usb_hcd_irq [usbcore]
[194597.086677] [<ffffffff810a0250>] irq_default_primary_handler
threaded [<ffffffffa000e520>] usb_hcd_irq [usbcore]
[194597.086683] [<ffffffff810a0250>] irq_default_primary_handler
threaded [<ffffffffa000e520>] usb_hcd_irq [usbcore]
[194597.086687] Disabling IRQ #17
[194602.166921] retire_capture_urb: 31152 callbacks suppressed
[194607.193310] retire_capture_urb: 32400 callbacks suppressed
[194612.270351] retire_capture_urb: 31820 callbacks suppressed etc..
kernel is started with threadirqs
Thanks
rob
On 13/10/14 12:54, rob wrote:
I spoke too soon. Same error with jackd1, just takes sometime to start.
The qjackctl messages are different multiple
delay of 29465.000 usecs exceeds estimated spare time of 5224.000;
restart ...
Going to try kxstudio livedvd to see if it happens there.
rob On 13/10/14 11:48, Clemens Ladisch wrote:
I was using jackd2. I've now tried jackd1 which works without the
problem. Maybe something to do with dbus?
Thanks
rob
The message in the subject means that the driver
logged some error
message repeatedly, and that the duplicates were suppressed.
The actual error message (before that) would be useful.
Regards,
Clemens
There isn't preceding message
from syslog :
Oct 13 11:47:46 debian dnsmasq[3465]: reading /etc/resolv.conf
Oct 13 11:47:46 debian dnsmasq[3465]: using nameserver 192.168.178.1#53
Oct 13 12:08:46 debian acpid: client connected from 8202[1001:1001]
Oct 13 12:08:46 debian acpid: 1 client rule loaded
Oct 13 12:17:01 debian /USR/SBIN/CRON[11997]: (root) CMD ( cd / &&
run-parts --report /etc/cron.hourly)
Oct 13 12:36:00 debian kernel: [371346.915918] retire_capture_urb: 13960
callbacks suppressed
Oct 13 12:36:05 debian kernel: [371351.975159] retire_capture_urb: 31944
callbacks suppressed
Oct 13 12:36:10 debian kernel: [371357.022838] retire_capture_urb: 32053
callbacks suppressed
Oct 13 12:36:15 debian kernel: [371362.089701] retire_capture_urb: 31962
callbacks suppressed
Oct 13 12:36:20 debian kernel: [371367.129415] retire_capture_urb: 32068
callbacks suppressed
Oct 13 12:36:25 debian kernel: [371372.203356] retire_capture_urb: 31613
callbacks suppressed
Oct 13 12:36:30 debian kernel: [371377.236139] retire_capture_urb: 31959
callbacks suppressed
Oct 13 12:36:35 debian kernel: [371382.319187] retire_capture_urb: 31742
callbacks suppressed
Oct 13 12:36:40 debian kernel: [371387.342876] retire_capture_urb: 32271
callbacks suppressed
Oct 13 12:36:46 debian kernel: [371392.432545] retire_capture_urb: 31773
callbacks suppressed
I forgot to mention kernel is started with threadirqs
_______________________________________________
4:26 p.m.
New subject: retire_capture_urb: 19662 callbacks suppressed [ADD.INFO]
rob wrote:
] CPU: 1 PID: 135 Comm: irq/17-ehci_hcd Not tainted
3.14.4preempt #1
Some information before that is missing.
[194597.086635] [<ffffffff810a2148>] ?
__report_bad_irq+0x28/0xc0
[194597.086658] handlers:
[194597.086660] [<ffffffff810a0250>] irq_default_primary_handler threaded
[<ffffffffa000e520>] usb_hcd_irq [usbcore]
[194597.086687] Disabling IRQ #17
Anyway, there is an interrupt problem with the USB controller driver.
kernel is started with threadirqs
Then don't do that.
Regards,
Clemens
20 Oct
20 Oct
3:18 p.m.
New subject: retire_capture_urb: 19662 callbacks suppressed [ADD.INFO]
On 17/10/14 15:26, Clemens Ladisch wrote:
rob wrote:
] CPU: 1 PID: 135 Comm: irq/17-ehci_hcd Not
tainted 3.14.4preempt #1
Some information before that is missing.
Regards,
Clemens
This time more info, from when it started:
[161681.082023] irq 17: nobody cared (try booting with the "irqpoll" option)
[161681.082024] irq 17: nobody cared (try booting with the "irqpoll" option)
[161681.082027] CPU: 1 PID: 135 Comm: irq/17-ehci_hcd Not tainted
3.14.4preempt #1
[161681.082029] Hardware name: Gigabyte Technology Co., Ltd. To be
filled by O.E.M./990FXA-UD5, BIOS FB 01/23/2013
[161681.082030] ffff8803215f6cbc ffffffff814d0ea9 ffff8803215f6c00
ffffffff810a2148
[161681.082034] ffff8803215f6c00 0000000000000011 ffff8803215f6c00
ffffffff810a25d5
[161681.082038] ffffffff810594cf ffff88031f55a350 ffff8800c9496a00
ffff8803215f6c00
[161681.082042] Call Trace:
[161681.082049] [<ffffffff814d0ea9>] ? dump_stack+0x4a/0x75
[161681.082053] [<ffffffff810a2148>] ? __report_bad_irq+0x28/0xc0
[161681.082056] [<ffffffff810a25d5>] ? note_interrupt+0x1b5/0x210
[161681.082059] [<ffffffff810594cf>] ? __local_bh_enable_ip+0x3f/0xa0
[161681.082062] [<ffffffff810a08f0>] ? irq_thread_fn+0x40/0x40
[161681.082064] [<ffffffff810a0e15>] ? irq_thread+0x135/0x140
[161681.082067] [<ffffffff810a0970>] ? wake_threads_waitq+0x30/0x30
[161681.082069] [<ffffffff810a0ce0>] ? irq_thread_check_affinity+0xb0/0xb0
[161681.082073] [<ffffffff81075321>] ? kthread+0xc1/0xe0
[161681.082076] [<ffffffff81075260>] ? kthread_create_on_node+0x180/0x180
[161681.082079] [<ffffffff814de00c>] ? ret_from_fork+0x7c/0xb0
[161681.082081] [<ffffffff81075260>] ? kthread_create_on_node+0x180/0x180
[161681.082083] handlers:
[161681.082084] CPU: 0 PID: 134 Comm: irq/17-ehci_hcd Not tainted
3.14.4preempt #1
[161681.082085] Hardware name: Gigabyte Technology Co., Ltd. To be
filled by O.E.M./990FXA-UD5, BIOS FB 01/23/2013
[161681.082089] ffff8803215f6cbc ffffffff814d0ea9 ffff8803215f6c00
[161681.082106] [<ffffffff810a0250>] irq_default_primary_handler
threaded [<ffffffffa003c520>] usb_hcd_irq [usbcore]
[161681.082108] [<ffffffff810a0250>] irq_default_primary_handler
threaded [<ffffffffa003c520>] usb_hcd_irq [usbcore]
[161681.082112] ffffffff810a2148
[161681.082114] ffff8803215f6c00
[161681.082115] 0000000000000011
[161681.082115] ffff8803215f6c00
[161681.082116] ffffffff810a25d5
[161681.082116] ffffffff810594cf
[161681.082117] ffff88031f55aba0
[161681.082118] ffff88031f77a880
[161681.082118] ffff8803215f6c00
[161681.082119] Call Trace:
[161681.082122] [<ffffffff814d0ea9>] ? dump_stack+0x4a/0x75
[161681.082124] [<ffffffff810a2148>] ? __report_bad_irq+0x28/0xc0
[161681.082127] [<ffffffff810a25d5>] ? note_interrupt+0x1b5/0x210
[161681.082129] [<ffffffff810594cf>] ? __local_bh_enable_ip+0x3f/0xa0
[161681.082131] [<ffffffff810a08f0>] ? irq_thread_fn+0x40/0x40
[161681.082133] [<ffffffff810a0e15>] ? irq_thread+0x135/0x140
[161681.082135] [<ffffffff810a0970>] ? wake_threads_waitq+0x30/0x30
[161681.082137] [<ffffffff810a0ce0>] ? irq_thread_check_affinity+0xb0/0xb0
[161681.082139] [<ffffffff81075321>] ? kthread+0xc1/0xe0
[161681.082142] [<ffffffff810a0250>] irq_default_primary_handler
threaded [<ffffffffa003c520>] usb_hcd_irq [usbcore]
[161681.082147] [<ffffffff81075260>] ? kthread_create_on_node+0x180/0x180
[161681.082150] [<ffffffff814de00c>] ? ret_from_fork+0x7c/0xb0
[161681.082152] [<ffffffff81075260>] ? kthread_create_on_node+0x180/0x180
[161681.082153] handlers:
[161681.082154] Disabling IRQ #17
[161681.082156] [<ffffffff810a0250>] irq_default_primary_handler
threaded [<ffffffffa003c520>] usb_hcd_irq [usbcore]
[161681.082163] [<ffffffff810a0250>] irq_default_primary_handler
threaded [<ffffffffa003c520>] usb_hcd_irq [usbcore]
[161681.082167] [<ffffffff810a0250>] irq_default_primary_handler
threaded [<ffffffffa003c520>] usb_hcd_irq [usbcore]
[161681.082172] Disabling IRQ #17
[161686.185486] retire_capture_urb: 32252 callbacks suppressed
[161691.251977] retire_capture_urb: 31716 callbacks suppressed
[161696.292281] retire_capture_urb: 32256 callbacks suppressed
[161701.357044] retire_capture_urb: 32007 callbacks suppressed
[161706.398904] retire_capture_urb: 31990 callbacks suppressed
[161711.460623] retire_capture_urb: 31727 callbacks suppressed
[161716.505945] retire_capture_urb: 32069 callbacks suppressed
[161721.567620] retire_capture_urb: 31749 callbacks suppressed
rob
26 Oct
26 Oct
2:38 p.m.
New subject: retire_capture_urb: 19662 callbacks suppressed [ADD.INFO]
On 20/10/14 15:37, Clemens Ladisch wrote:
rob wrote:
Yes,
The asus motherboard that was replaced would only run xrun-free with
threadirqs, same kernel. The new board is xrun-free @ 256/2 without
threadirqs but stops working after roughly 24 hrs with threadirqs enabled.
Thanks
rob
This time more info
Well, does it work without threadirqs?
Regards,
Clemens
_______________________________________________
4007
days inactive
4020
days old
linux-audio-user@lists.linuxaudio.org
9 comments
2 participants
participants (2)
-
Clemens Ladisch -
rob