Re: [LAD] Patching linux 2.6.26.3
Jussi Laako wrote: > Rui Nuno Capela wrote: >> just tested 2.6.23.3-rt3 here with NO_HZ not set in my (old) pentium4 >> desktop. >> >> it just confirmed that NO_HZ is not the culprit here. midi events are >> still being delivered *completely* out of time and the funny thing is >> it just gets somewhat better whenever you hit the pc-keyboard keys. >> however, it all gets back to badness once you stop pressing any key >> (eg. shift-key) >> >> another funny thing goes that on a core2 duo T7200 laptop (x86_64) the >> same kernel config it runs all fine (NO_HZ=y) > > I'm kind of wondering what these have in > /sys/devices/system/clocksource/clocksource0/current_clocksource > a) on the desktop ([EMAIL PROTECTED]), where midi timing delivery is completely broken: # uname -a Linux gamma 2.6.26.3-rt3 #1 SMP PREEMPT RT Sat Aug 23 19:34:05 WEST 2008 i686 i686 i386 GNU/Linux # cat /sys/devices/system/clocksource/clocksource0/current_clocksource tsc b) on the laptop ([EMAIL PROTECTED]), where midi seems to work fine: # uname -a Linux zeta 2.6.26.3-rt3 #1 SMP PREEMPT RT Sat Aug 23 19:14:58 WEST 2008 x86_64 x86_64 x86_64 GNU/Linux # cat /sys/devices/system/clocksource/clocksource0/current_clocksource hpet least to say, audio (ie. jackd) works fine on both cases. i've also tried to set the clocksource to hpet in a) and got no change in midi/tty brokenness. byee -- rncbc aka Rui Nuno Capela [EMAIL PROTECTED] ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
Re: [LAD] Patching linux 2.6.26.3
> On Mon, Aug 25, 2008 at 03:39:27PM +0930, Jonathan Woithe wrote: > > > On Mon, Aug 25, 2008 at 01:12:55PM +1000, porl sheean wrote: > > > > i've just finished compiling the 2.6.26.3 kernel with the readltime > > > > patch from above, and i am having no problems with a firewire saffire > > > > pro card using ffado. i haven't tried midi though, so i can't comment > > > > there. i can't remember if i set the kernel tickless or not though > > > > sorry. > > > > porl > > > Does ffado use juju or the old firewire stack? > > The old firewire stack, via libraw1394 versions 1.2.0, 1.3.0 or 2.0.0. > > And there haven't been issues with the old stack in recent kernels? i.e. > 2.6.25, 2.6.26 ... I haven't noticed any but then again my recent firewire work has been almost exclusively with ffado. > (It's possible the camcorder issues we've had are specific to something > with current debian kernels.) I don't think I've used my DV camera with 2.6.25 or 2.6.26 - I'd have to check. I did do some transfers around March but that would have been under 2.6.24 at the latest. Regards jonathan ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
Re: [LAD] Patching linux 2.6.26.3
On Mon, Aug 25, 2008 at 03:39:27PM +0930, Jonathan Woithe wrote: > > On Mon, Aug 25, 2008 at 01:12:55PM +1000, porl sheean wrote: > > > i've just finished compiling the 2.6.26.3 kernel with the readltime > > > patch from above, and i am having no problems with a firewire saffire > > > pro card using ffado. i haven't tried midi though, so i can't comment > > > there. i can't remember if i set the kernel tickless or not though > > > sorry. > > > porl > > Does ffado use juju or the old firewire stack? > The old firewire stack, via libraw1394 versions 1.2.0, 1.3.0 or 2.0.0. And there haven't been issues with the old stack in recent kernels? i.e. 2.6.25, 2.6.26 ... (It's possible the camcorder issues we've had are specific to something with current debian kernels.) -Eric Rz. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
Re: [LAD] Patching linux 2.6.26.3
> On Mon, Aug 25, 2008 at 01:12:55PM +1000, porl sheean wrote: > > i've just finished compiling the 2.6.26.3 kernel with the readltime > > patch from above, and i am having no problems with a firewire saffire > > pro card using ffado. i haven't tried midi though, so i can't comment > > there. i can't remember if i set the kernel tickless or not though > > sorry. > > > > porl > > Does ffado use juju or the old firewire stack? The old firewire stack, via libraw1394 versions 1.2.0, 1.3.0 or 2.0.0. Regards jonathan ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
Re: [LAD] Patching linux 2.6.26.3
On Mon, Aug 25, 2008 at 01:12:55PM +1000, porl sheean wrote: > i've just finished compiling the 2.6.26.3 kernel with the readltime > patch from above, and i am having no problems with a firewire saffire > pro card using ffado. i haven't tried midi though, so i can't comment > there. i can't remember if i set the kernel tickless or not though > sorry. > > porl Does ffado use juju or the old firewire stack? -Eric Rz. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
Re: [LAD] Patching linux 2.6.26.3
i've just finished compiling the 2.6.26.3 kernel with the readltime patch from above, and i am having no problems with a firewire saffire pro card using ffado. i haven't tried midi though, so i can't comment there. i can't remember if i set the kernel tickless or not though sorry. porl 2008/8/25 Jonathan Woithe <[EMAIL PROTECTED]>: > Hi > >> Am Freitag, 22. August 2008 schrieb Robin Gareus: >> > Rui Nuno Capela wrote: >> > > however, didn't had the time to check whether NOHZ is at stake. i'm >> > > certainly going back to 2.6.25.x-rt where things are still sane and >> > > pleasant for a while. >> > I'll forward this email to LAT. MIDI with 2.6.26 MIDI has not been >> > mentioned there. >> >> USB-sticks don't work here either on 2.6.26... I will go back to <2.6.26 as >> soon as time permits. > > I've been running a tickless 2.6.26 (NOT 2.6.26.3, and not RT) and USB > sticks have been fine for me. > >> What about firewire? has anyone been seeing issues with audio devices or >> hard drives? > > My ffado installation seems to be operating fine under tickless 2.6.26 > (again though, 2.6.26.3 and/or RT patches not yet tested). > > Regards > jonathan > ___ > Linux-audio-dev mailing list > Linux-audio-dev@lists.linuxaudio.org > http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev > ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
Re: [LAD] Patching linux 2.6.26.3
Hi > Am Freitag, 22. August 2008 schrieb Robin Gareus: > > Rui Nuno Capela wrote: > > > however, didn't had the time to check whether NOHZ is at stake. i'm > > > certainly going back to 2.6.25.x-rt where things are still sane and > > > pleasant for a while. > > I'll forward this email to LAT. MIDI with 2.6.26 MIDI has not been > > mentioned there. > > USB-sticks don't work here either on 2.6.26... I will go back to <2.6.26 as > soon as time permits. I've been running a tickless 2.6.26 (NOT 2.6.26.3, and not RT) and USB sticks have been fine for me. > What about firewire? has anyone been seeing issues with audio devices or > hard drives? My ffado installation seems to be operating fine under tickless 2.6.26 (again though, 2.6.26.3 and/or RT patches not yet tested). Regards jonathan ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
Re: [LAD] Patching linux 2.6.26.3
Rui Nuno Capela wrote: > just tested 2.6.23.3-rt3 here with NO_HZ not set in my (old) pentium4 > desktop. > > it just confirmed that NO_HZ is not the culprit here. midi events are > still being delivered *completely* out of time and the funny thing is it > just gets somewhat better whenever you hit the pc-keyboard keys. > however, it all gets back to badness once you stop pressing any key (eg. > shift-key) > > another funny thing goes that on a core2 duo T7200 laptop (x86_64) the > same kernel config it runs all fine (NO_HZ=y) I'm kind of wondering what these have in /sys/devices/system/clocksource/clocksource0/current_clocksource BR, - Jussi ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
Re: [LAD] Patching linux 2.6.26.3
The good news is that they seem to be tackling these problems. We might see a much more RT-enabled linux in the future. I was quite optmistic after reading that blog. In the meantime, looks like we should not touch 2.6.26, not even with a bargepole. Victor >> http://kerneltrap.org/Linux/Removing_the_Big_Kernel_Lock mentions TTY >> drivers being a problem, actually "a long and difficult task".. >> ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
Re: [LAD] Patching linux 2.6.26.3
Robin Gareus wrote: > Rui Nuno Capela wrote: >> Robin Gareus wrote: >>> Rui Nuno Capela wrote: Tim Goetze wrote: > [Tim Goetze] > >> [victor] >>> I was told to revert to 2.6.24.17 (not possible in my specific >>> case, but there you go), in this list. Or to join the tuner's list. >> http://www.kernel.org/pub/linux/kernel/projects/rt/patch-2.6.26.3-rt2.bz2 >> >> >> worked for me. Applied cleanly and compiled well after turning off >> some RCU-related preemption options that caused compilation errors, >> but I was in no mood to find out the exact how and why. So far, it >> has collected a few hours of solid uptime too, but I haven't done >> any latency measuring. > Update: on my laptop, the patched 2.6.26.3 kernel boots into an > endless list of tracebacks on the console. On the main box, USB > MIDI input is only read as soon as a key is pressed on the USB > keyboard (the one with the letters, not the MIDI one ...). USB MIDI > out is broken, too. So it's back to the old version. > ah, it seems i'm not alone. >>> hehe , nice try. We won't let you go that easily ;) >>> i'm currently recovering myself from schock after returning from vacation and while trying 2.6.26.x-rt for the rentrýe it all seemed to work fine except omg... midi timing is a wreck, specially wrt.alsa sequencer. event delivery is completely fubar. i mean, completely. true showstopper, whatever :( cacophony seems to be the right word to express what it is. however, didn't had the time to check whether NOHZ is at stake. i'm certainly going back to 2.6.25.x-rt where things are still sane and pleasant for a while. btw, having NOHZ=y (aka tickless kernel) has been the norm here, since its inception >>> CONFIG_NO_HZ=y - same norm here; with good results iff it works. >>> >> just tested 2.6.23.3-rt3 here with NO_HZ not set in my (old) pentium4 >> desktop. > >> it just confirmed that NO_HZ is not the culprit here. midi events are >> still being delivered *completely* out of time and the funny thing is it >> just gets somewhat better whenever you hit the pc-keyboard keys. >> however, it all gets back to badness once you stop pressing any key (eg. >> shift-key) > >> another funny thing goes that on a core2 duo T7200 laptop (x86_64) the >> same kernel config it runs all fine (NO_HZ=y) > > > http://kerneltrap.org/Linux/Removing_the_Big_Kernel_Lock mentions TTY > drivers being a problem, actually "a long and difficult task".. > ah. and more fun to the party: if the pc-keyboard is abused in way above said, to let midi delivery work miserably, it just stops working at all. you'll end with a dead pc-keyboard, something like its key-buffer gets fed up and can't get drained anymore. seeya -- rncbc aka Rui Nuno Capela [EMAIL PROTECTED] ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
Re: [LAD] Patching linux 2.6.26.3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Rui Nuno Capela wrote: > Robin Gareus wrote: >> Rui Nuno Capela wrote: >>> Tim Goetze wrote: [Tim Goetze] > [victor] >> I was told to revert to 2.6.24.17 (not possible in my specific >> case, but there you go), in this list. Or to join the tuner's list. > http://www.kernel.org/pub/linux/kernel/projects/rt/patch-2.6.26.3-rt2.bz2 > > > worked for me. Applied cleanly and compiled well after turning off > some RCU-related preemption options that caused compilation errors, > but I was in no mood to find out the exact how and why. So far, it > has collected a few hours of solid uptime too, but I haven't done > any latency measuring. Update: on my laptop, the patched 2.6.26.3 kernel boots into an endless list of tracebacks on the console. On the main box, USB MIDI input is only read as soon as a key is pressed on the USB keyboard (the one with the letters, not the MIDI one ...). USB MIDI out is broken, too. So it's back to the old version. >>> ah, it seems i'm not alone. >> >> hehe , nice try. We won't let you go that easily ;) >> >>> i'm currently recovering myself from schock after returning from >>> vacation and while trying 2.6.26.x-rt for the rentrýe it all seemed >>> to work fine except omg... midi timing is a wreck, specially wrt.alsa >>> sequencer. event delivery is completely fubar. i mean, completely. >>> true showstopper, whatever :( >> >>> cacophony seems to be the right word to express what it is. >> >>> however, didn't had the time to check whether NOHZ is at stake. i'm >>> certainly going back to 2.6.25.x-rt where things are still sane and >>> pleasant for a while. >> >>> btw, having NOHZ=y (aka tickless kernel) has been the norm here, >>> since its inception >> >> CONFIG_NO_HZ=y - same norm here; with good results iff it works. >> > > just tested 2.6.23.3-rt3 here with NO_HZ not set in my (old) pentium4 > desktop. > > it just confirmed that NO_HZ is not the culprit here. midi events are > still being delivered *completely* out of time and the funny thing is it > just gets somewhat better whenever you hit the pc-keyboard keys. > however, it all gets back to badness once you stop pressing any key (eg. > shift-key) > > another funny thing goes that on a core2 duo T7200 laptop (x86_64) the > same kernel config it runs all fine (NO_HZ=y) > http://kerneltrap.org/Linux/Removing_the_Big_Kernel_Lock mentions TTY drivers being a problem, actually "a long and difficult task".. 2c, robin -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkixWYkACgkQeVUk8U+VK0KoDgCgrFy2K9eamJrZUOHbG3m4ZuIz ypgAn36etP4eo/+I0mbnAO4BbX8kajgA =B1I0 -END PGP SIGNATURE- ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
Re: [LAD] Patching linux 2.6.26.3
Robin Gareus wrote: > Rui Nuno Capela wrote: >> Tim Goetze wrote: >>> [Tim Goetze] >>> [victor] > I was told to revert to 2.6.24.17 (not possible in my specific > case, but there you go), in this list. Or to join the tuner's list. http://www.kernel.org/pub/linux/kernel/projects/rt/patch-2.6.26.3-rt2.bz2 worked for me. Applied cleanly and compiled well after turning off some RCU-related preemption options that caused compilation errors, but I was in no mood to find out the exact how and why. So far, it has collected a few hours of solid uptime too, but I haven't done any latency measuring. >>> Update: on my laptop, the patched 2.6.26.3 kernel boots into an >>> endless list of tracebacks on the console. On the main box, USB MIDI >>> input is only read as soon as a key is pressed on the USB keyboard >>> (the one with the letters, not the MIDI one ...). USB MIDI out is >>> broken, too. So it's back to the old version. >>> >> ah, it seems i'm not alone. > > hehe , nice try. We won't let you go that easily ;) > >> i'm currently recovering myself from schock after returning from >> vacation and while trying 2.6.26.x-rt for the rentrýe it all seemed to >> work fine except omg... midi timing is a wreck, specially wrt.alsa >> sequencer. event delivery is completely fubar. i mean, completely. true >> showstopper, whatever :( > >> cacophony seems to be the right word to express what it is. > >> however, didn't had the time to check whether NOHZ is at stake. i'm >> certainly going back to 2.6.25.x-rt where things are still sane and >> pleasant for a while. > >> btw, having NOHZ=y (aka tickless kernel) has been the norm here, since >> its inception > > CONFIG_NO_HZ=y - same norm here; with good results iff it works. > just tested 2.6.23.3-rt3 here with NO_HZ not set in my (old) pentium4 desktop. it just confirmed that NO_HZ is not the culprit here. midi events are still being delivered *completely* out of time and the funny thing is it just gets somewhat better whenever you hit the pc-keyboard keys. however, it all gets back to badness once you stop pressing any key (eg. shift-key) another funny thing goes that on a core2 duo T7200 laptop (x86_64) the same kernel config it runs all fine (NO_HZ=y) byee -- rncbc aka Rui Nuno Capela [EMAIL PROTECTED] ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
Re: [LAD] Patching linux 2.6.26.3
On Fri, Aug 22, 2008 at 07:43:23PM +0200, Arnold Krille wrote: > Am Freitag, 22. August 2008 schrieb Robin Gareus: > > Rui Nuno Capela wrote: > > > however, didn't had the time to check whether NOHZ is at stake. i'm > > > certainly going back to 2.6.25.x-rt where things are still sane and > > > pleasant for a while. > > I'll forward this email to LAT. MIDI with 2.6.26 MIDI has not been > > mentioned there. > > USB-sticks don't work here either on 2.6.26... I will go back to <2.6.26 as > soon as time permits. What about firewire? has anyone been seeing issues with audio devices or hard drives? I know there have been some problems with miniDV camcorders in most recent kernels. -Eric Rz. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
Re: [LAD] Patching linux 2.6.26.3
Am Freitag, 22. August 2008 schrieb Robin Gareus: > Rui Nuno Capela wrote: > > however, didn't had the time to check whether NOHZ is at stake. i'm > > certainly going back to 2.6.25.x-rt where things are still sane and > > pleasant for a while. > I'll forward this email to LAT. MIDI with 2.6.26 MIDI has not been > mentioned there. USB-sticks don't work here either on 2.6.26... I will go back to <2.6.26 as soon as time permits. Arnold -- visit http://www.arnoldarts.de/ --- Hi, I am a .signature virus. Please copy me into your ~/.signature and send me to all your contacts. After a month or so log in as root and do a "rm -rf /". Or ask your administrator to do so... signature.asc Description: This is a digitally signed message part. ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
Re: [LAD] Patching linux 2.6.26.3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Rui Nuno Capela wrote: > Tim Goetze wrote: >> [Tim Goetze] >> >>> [victor] I was told to revert to 2.6.24.17 (not possible in my specific case, but there you go), in this list. Or to join the tuner's list. >>> http://www.kernel.org/pub/linux/kernel/projects/rt/patch-2.6.26.3-rt2.bz2 >>> >>> worked for me. Applied cleanly and compiled well after turning off >>> some RCU-related preemption options that caused compilation errors, >>> but I was in no mood to find out the exact how and why. So far, it >>> has collected a few hours of solid uptime too, but I haven't done any >>> latency measuring. >> Update: on my laptop, the patched 2.6.26.3 kernel boots into an >> endless list of tracebacks on the console. On the main box, USB MIDI >> input is only read as soon as a key is pressed on the USB keyboard >> (the one with the letters, not the MIDI one ...). USB MIDI out is >> broken, too. So it's back to the old version. >> > > ah, it seems i'm not alone. hehe , nice try. We won't let you go that easily ;) > i'm currently recovering myself from schock after returning from > vacation and while trying 2.6.26.x-rt for the rentr�e it all seemed to > work fine except omg... midi timing is a wreck, specially wrt.alsa > sequencer. event delivery is completely fubar. i mean, completely. true > showstopper, whatever :( > > cacophony seems to be the right word to express what it is. > > however, didn't had the time to check whether NOHZ is at stake. i'm > certainly going back to 2.6.25.x-rt where things are still sane and > pleasant for a while. > > btw, having NOHZ=y (aka tickless kernel) has been the norm here, since > its inception CONFIG_NO_HZ=y - same norm here; with good results iff it works. I'll forward this email to LAT. MIDI with 2.6.26 MIDI has not been mentioned there. Since there's more of you LAD's compiling your own kernel that does not work, what about posting .config, version/patchset and compiler info before we all run into the same walls. - We're planning something like this with http://wiki.linuxaudio.org/wiki/kernel/ Does anyone know of similar projects? How in your opinion can LAO best supplement [rt] kernel bug tracking? There's 2.6.26-rtX testing packages from various distributions eg: http://linux.ilmainen.net/musix/temp/ or at http://guests.goto10.org/~krgn/files/ more at LAT - none of which is stable at the moment. robin -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkiu6E4ACgkQeVUk8U+VK0ItUwCguWgCtuPlnZoQQHVIDpVJRtvt suYAoKkv8JvmehvEOtKq81ameZnxw7yn =DXcK -END PGP SIGNATURE- ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
Re: [LAD] Patching linux 2.6.26.3
Tim Goetze wrote: > [Tim Goetze] > >> [victor] >>> I was told to revert to 2.6.24.17 (not possible in my specific >>> case, but there you go), in this list. Or to join the tuner's list. >> http://www.kernel.org/pub/linux/kernel/projects/rt/patch-2.6.26.3-rt2.bz2 >> >> worked for me. Applied cleanly and compiled well after turning off >> some RCU-related preemption options that caused compilation errors, >> but I was in no mood to find out the exact how and why. So far, it >> has collected a few hours of solid uptime too, but I haven't done any >> latency measuring. > > Update: on my laptop, the patched 2.6.26.3 kernel boots into an > endless list of tracebacks on the console. On the main box, USB MIDI > input is only read as soon as a key is pressed on the USB keyboard > (the one with the letters, not the MIDI one ...). USB MIDI out is > broken, too. So it's back to the old version. > ah, it seems i'm not alone. i'm currently recovering myself from schock after returning from vacation and while trying 2.6.26.x-rt for the rentrée it all seemed to work fine except omg... midi timing is a wreck, specially wrt.alsa sequencer. event delivery is completely fubar. i mean, completely. true showstopper, whatever :( cacophony seems to be the right word to express what it is. however, didn't had the time to check whether NOHZ is at stake. i'm certainly going back to 2.6.25.x-rt where things are still sane and pleasant for a while. btw, having NOHZ=y (aka tickless kernel) has been the norm here, since its inception byee -- rncbc aka Rui Nuno Capela [EMAIL PROTECTED] ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
Re: [LAD] Patching linux 2.6.26.3
[Tim Goetze] >[victor] >>I was told to revert to 2.6.24.17 (not possible in my specific >>case, but there you go), in this list. Or to join the tuner's list. > >http://www.kernel.org/pub/linux/kernel/projects/rt/patch-2.6.26.3-rt2.bz2 > >worked for me. Applied cleanly and compiled well after turning off >some RCU-related preemption options that caused compilation errors, >but I was in no mood to find out the exact how and why. So far, it >has collected a few hours of solid uptime too, but I haven't done any >latency measuring. Update: on my laptop, the patched 2.6.26.3 kernel boots into an endless list of tracebacks on the console. On the main box, USB MIDI input is only read as soon as a key is pressed on the USB keyboard (the one with the letters, not the MIDI one ...). USB MIDI out is broken, too. So it's back to the old version. Cheers, Tim ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
Re: [LAD] Patching linux 2.6.26.3
[victor] >I was told to revert to 2.6.24.17 (not possible in my specific >case, but there you go), in this list. Or to join the tuner's list. http://www.kernel.org/pub/linux/kernel/projects/rt/patch-2.6.26.3-rt2.bz2 worked for me. Applied cleanly and compiled well after turning off some RCU-related preemption options that caused compilation errors, but I was in no mood to find out the exact how and why. So far, it has collected a few hours of solid uptime too, but I haven't done any latency measuring. Cheers, Tim ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
Re: [LAD] Patching linux 2.6.26.3
I was told to revert to 2.6.24.17 (not possible in my specific case, but there you go), in this list. Or to join the tuner's list. Victor - Original Message - From: "Julien Claassen" <[EMAIL PROTECTED]> To: "Linux-Audio-Dev" Sent: Wednesday, August 20, 2008 8:10 PM Subject: [LAD] Patching linux 2.6.26.3 > Hi all! > I'm trying to patch the linux kernel version 2.6.26.3 with the rt-patch. > But > there's only a patch for 2.6.26. It's not working very well. Because some > changes were already taken into the kernel. Which command should I use to > do > the patch properly. Or should I stop patching all together? Or is there > another experimental place to get newer rt-patches. > Thanks and kindest regards > Julien > > > Music was my first love and it will be my last (John Miles) > > FIND MY WEB-PROJECT AT: > http://ltsb.sourceforge.net > the Linux TextBased Studio guide > === AND MY PERSONAL PAGES AT: === > http://www.juliencoder.de > ___ > Linux-audio-dev mailing list > Linux-audio-dev@lists.linuxaudio.org > http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
[LAD] Patching linux 2.6.26.3
Hi all! I'm trying to patch the linux kernel version 2.6.26.3 with the rt-patch. But there's only a patch for 2.6.26. It's not working very well. Because some changes were already taken into the kernel. Which command should I use to do the patch properly. Or should I stop patching all together? Or is there another experimental place to get newer rt-patches. Thanks and kindest regards Julien Music was my first love and it will be my last (John Miles) FIND MY WEB-PROJECT AT: http://ltsb.sourceforge.net the Linux TextBased Studio guide === AND MY PERSONAL PAGES AT: === http://www.juliencoder.de ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
