rsdl 0.32 backport to 2.6.18.8 available & pre-built DebianEtch and Fedora 6 kernels
Hi all, A backported version of the RSDL 0.32 patch is now available at http://linux-dev.qc.ec.gc.ca for a 2.6.18.8 kernel. There are also a few 2.6.18/2.6.20 pre-built kernels available for both Debian Etch (x86_64) and Fedora 6 (x86_64). - vin - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
rsdl 0.32 backport to 2.6.18.8 available pre-built DebianEtch and Fedora 6 kernels
Hi all, A backported version of the RSDL 0.32 patch is now available at http://linux-dev.qc.ec.gc.ca for a 2.6.18.8 kernel. There are also a few 2.6.18/2.6.20 pre-built kernels available for both Debian Etch (x86_64) and Fedora 6 (x86_64). - vin - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Fwd: Backport RSDL v0.31: Updated RSDL 0.31 backport for 2.6.18.8 & Debian etch x86_64 RSDL 0.31 kernels availability
Hi all, Here is are the backported RSDL scheduler for a 2.6.18.8 kernel and now also for 2.6.19.7 kernel. This release includes the original backported 2.6.20.x RSDL 0.31 patch and also has few cleanups to remove unecessary debian make-kpkg files. This update also includes a small patch to both 2.6.18 and 2.6.19 kernels (http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.20.y.git;a=commit;h=d499ac7a3681e270074e880879d0e0a5ad0849fa). Would a new stable release of 2.6.18 and .19 including that patch be worth it? The provided kernels (only for Debian Etch x86_64) might be usefull to make load comparisons between Vanilla vs CK's RSDL scheduler. Althoug I've been able to backport properly RSDL to a 2.6.18 kernel I'm currently having a bug in the 2.6.19 backported patch. Help finding that bug would really be appreciated. 2.6.19 BUG in action picture available at http://linux-dev.qc.ec.gc.ca/kernel/debian/etch/x86_64/2.6.19/bug-2.6.19-rsdl-031.jpg Official CK RSDL patches available at: http://ck.kolivas.org/patches/staircase-deadline/ Latest CK RSDL 0.31 announcement: http://lkml.org/lkml/2007/3/16/173 Again, nice work CK! - 2.6.18.8 backport RSDL 0.31 patch (contains already Ingo's SMT scheduler fix): PATCH: http://linux-dev.qc.ec.gc.ca/kernel/rsdl/2.6.18.8-rsdl-0.31.patch CONFIG: http://linux-dev.qc.ec.gc.ca/kernel/debian/etch/x86_64/2.6.18/CONFIG-2.6.18-003 Notes: Didn't encountered any problems yet. 2.6.19.7 backport RSDL 0.31 patch (contains already Ingo's SMT scheduler fix): PATCH: http://linux-dev.qc.ec.gc.ca/kernel/rsdl/2.6.19.7-rsdl-0.31.patch CONFIG: http://linux-dev.qc.ec.gc.ca/kernel/debian/etch/x86_64/2.6.19/CONFIG-2.6.19-001 Notes: There is currently a bug in the backported 2.6.19 RSDL 0.31 kernel. I've attached a picture of the kernel BUG: call. Help to trace this bug would really be appreciated since I'm not that much a kernel hacker yet! Also note that libata PATA is not enabled and that GFS + DLM is enabled. 2.6.20.3 uses the official RSDL 0.31 from CK: CONFIG: http://linux-dev.qc.ec.gc.ca/kernel/debian/etch/x86_64/2.6.20/CONFIG-2.6.20-001 Notes: Uses the official RSDL 0.31 patch from CK. Libata PATA not enabled, GFS + DLM enabled, KVM enabled. Ingo's SMT scheduler fix (already included in stable 2.6.20.3): http://linux-dev.qc.ec.gc.ca/kernel/rsdl/fix_SMT_scheduler_bug.patch Pre-compiled Debian Etch 4.0 x86_64 kernels: 2.6.18.8 + SMT sched fix + RSDL 0.31: http://linux-dev.qc.ec.gc.ca/kernel/debian/etch/x86_64/2.6.18/linux-image-2.6.18.8-003-rsdl-0.31-amd64-envcan_2.6.18.8-003-rsdl-0.31_amd64.deb http://linux-dev.qc.ec.gc.ca/kernel/debian/etch/x86_64/2.6.18/linux-headers-2.6.18.8-003-rsdl-0.31-amd64-envcan_2.6.18.8-003-rsdl-0.31_amd64.deb 2.6.18.8 + SMT sched fix: http://linux-dev.qc.ec.gc.ca/kernel/debian/etch/x86_64/2.6.18/linux-image-2.6.18.8-003p1-amd64-envcan_2.6.18.8-003p1_amd64.deb http://linux-dev.qc.ec.gc.ca/kernel/debian/etch/x86_64/2.6.18/linux-headers-2.6.18.8-003p1-amd64-envcan_2.6.18.8-003p1_amd64.deb 2.6.18.8 (Vanilla): http://linux-dev.qc.ec.gc.ca/kernel/debian/etch/x86_64/2.6.18/linux-image-2.6.18.8-003-amd64-envcan_2.6.18.8-003_amd64.deb http://linux-dev.qc.ec.gc.ca/kernel/debian/etch/x86_64/2.6.18/linux-headers-2.6.18.8-003-amd64-envcan_2.6.18.8-003_amd64.deb 2.6.19.7 + SMT sched fix + RSDL 0.31: http://linux-dev.qc.ec.gc.ca/kernel/debian/etch/x86_64/2.6.19/linux-image-2.6.19.7-001-rsdl-0.31-amd64-envcan_2.6.19.7-001-rsdl-0.31_amd64.deb http://linux-dev.qc.ec.gc.ca/kernel/debian/etch/x86_64/2.6.19/linux-headers-2.6.19.7-001-rsdl-0.31-amd64-envcan_2.6.19.7-001-rsdl-0.31_amd64.deb 2.6.19.7 + SMT sched fix: http://linux-dev.qc.ec.gc.ca/kernel/debian/etch/x86_64/2.6.19/linux-image-2.6.19.7-001p1-amd64-envcan_2.6.19.7-001p1_amd64.deb http://linux-dev.qc.ec.gc.ca/kernel/debian/etch/x86_64/2.6.19/linux-headers-2.6.19.7-001p1-amd64-envcan_2.6.19.7-001p1_amd64.deb 2.6.20.3 + RSDL 0.31: http://linux-dev.qc.ec.gc.ca/kernel/debian/etch/x86_64/2.6.20/linux-image-2.6.20.3-001-rsdl-0.31-amd64-envcan_2.6.20.3-001-rsdl-0.31_amd64.deb http://linux-dev.qc.ec.gc.ca/kernel/debian/etch/x86_64/2.6.20/linux-headers-2.6.20.3-001-rsdl-0.31-amd64-envcan_2.6.20.3-001-rsdl-0.31_amd64.deb 2.6.20.3 (Vanilla) http://linux-dev.qc.ec.gc.ca/kernel/debian/etch/x86_64/2.6.20/linux-image-2.6.20.3-001-amd64-envcan_2.6.20.3-001_amd64.deb http://linux-dev.qc.ec.gc.ca/kernel/debian/etch/x86_64/2.6.20/linux-headers-2.6.20.3-001-amd64-envcan_2.6.20.3-001_amd64.deb Comments are welcomed! Vincent Fortier Informatique Environnement Canada - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Fwd: Backport RSDL v0.31: Updated RSDL 0.31 backport for 2.6.18.8 Debian etch x86_64 RSDL 0.31 kernels availability
Hi all, Here is are the backported RSDL scheduler for a 2.6.18.8 kernel and now also for 2.6.19.7 kernel. This release includes the original backported 2.6.20.x RSDL 0.31 patch and also has few cleanups to remove unecessary debian make-kpkg files. This update also includes a small patch to both 2.6.18 and 2.6.19 kernels (http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.20.y.git;a=commit;h=d499ac7a3681e270074e880879d0e0a5ad0849fa). Would a new stable release of 2.6.18 and .19 including that patch be worth it? The provided kernels (only for Debian Etch x86_64) might be usefull to make load comparisons between Vanilla vs CK's RSDL scheduler. Althoug I've been able to backport properly RSDL to a 2.6.18 kernel I'm currently having a bug in the 2.6.19 backported patch. Help finding that bug would really be appreciated. 2.6.19 BUG in action picture available at http://linux-dev.qc.ec.gc.ca/kernel/debian/etch/x86_64/2.6.19/bug-2.6.19-rsdl-031.jpg Official CK RSDL patches available at: http://ck.kolivas.org/patches/staircase-deadline/ Latest CK RSDL 0.31 announcement: http://lkml.org/lkml/2007/3/16/173 Again, nice work CK! - 2.6.18.8 backport RSDL 0.31 patch (contains already Ingo's SMT scheduler fix): PATCH: http://linux-dev.qc.ec.gc.ca/kernel/rsdl/2.6.18.8-rsdl-0.31.patch CONFIG: http://linux-dev.qc.ec.gc.ca/kernel/debian/etch/x86_64/2.6.18/CONFIG-2.6.18-003 Notes: Didn't encountered any problems yet. 2.6.19.7 backport RSDL 0.31 patch (contains already Ingo's SMT scheduler fix): PATCH: http://linux-dev.qc.ec.gc.ca/kernel/rsdl/2.6.19.7-rsdl-0.31.patch CONFIG: http://linux-dev.qc.ec.gc.ca/kernel/debian/etch/x86_64/2.6.19/CONFIG-2.6.19-001 Notes: There is currently a bug in the backported 2.6.19 RSDL 0.31 kernel. I've attached a picture of the kernel BUG: call. Help to trace this bug would really be appreciated since I'm not that much a kernel hacker yet! Also note that libata PATA is not enabled and that GFS + DLM is enabled. 2.6.20.3 uses the official RSDL 0.31 from CK: CONFIG: http://linux-dev.qc.ec.gc.ca/kernel/debian/etch/x86_64/2.6.20/CONFIG-2.6.20-001 Notes: Uses the official RSDL 0.31 patch from CK. Libata PATA not enabled, GFS + DLM enabled, KVM enabled. Ingo's SMT scheduler fix (already included in stable 2.6.20.3): http://linux-dev.qc.ec.gc.ca/kernel/rsdl/fix_SMT_scheduler_bug.patch Pre-compiled Debian Etch 4.0 x86_64 kernels: 2.6.18.8 + SMT sched fix + RSDL 0.31: http://linux-dev.qc.ec.gc.ca/kernel/debian/etch/x86_64/2.6.18/linux-image-2.6.18.8-003-rsdl-0.31-amd64-envcan_2.6.18.8-003-rsdl-0.31_amd64.deb http://linux-dev.qc.ec.gc.ca/kernel/debian/etch/x86_64/2.6.18/linux-headers-2.6.18.8-003-rsdl-0.31-amd64-envcan_2.6.18.8-003-rsdl-0.31_amd64.deb 2.6.18.8 + SMT sched fix: http://linux-dev.qc.ec.gc.ca/kernel/debian/etch/x86_64/2.6.18/linux-image-2.6.18.8-003p1-amd64-envcan_2.6.18.8-003p1_amd64.deb http://linux-dev.qc.ec.gc.ca/kernel/debian/etch/x86_64/2.6.18/linux-headers-2.6.18.8-003p1-amd64-envcan_2.6.18.8-003p1_amd64.deb 2.6.18.8 (Vanilla): http://linux-dev.qc.ec.gc.ca/kernel/debian/etch/x86_64/2.6.18/linux-image-2.6.18.8-003-amd64-envcan_2.6.18.8-003_amd64.deb http://linux-dev.qc.ec.gc.ca/kernel/debian/etch/x86_64/2.6.18/linux-headers-2.6.18.8-003-amd64-envcan_2.6.18.8-003_amd64.deb 2.6.19.7 + SMT sched fix + RSDL 0.31: http://linux-dev.qc.ec.gc.ca/kernel/debian/etch/x86_64/2.6.19/linux-image-2.6.19.7-001-rsdl-0.31-amd64-envcan_2.6.19.7-001-rsdl-0.31_amd64.deb http://linux-dev.qc.ec.gc.ca/kernel/debian/etch/x86_64/2.6.19/linux-headers-2.6.19.7-001-rsdl-0.31-amd64-envcan_2.6.19.7-001-rsdl-0.31_amd64.deb 2.6.19.7 + SMT sched fix: http://linux-dev.qc.ec.gc.ca/kernel/debian/etch/x86_64/2.6.19/linux-image-2.6.19.7-001p1-amd64-envcan_2.6.19.7-001p1_amd64.deb http://linux-dev.qc.ec.gc.ca/kernel/debian/etch/x86_64/2.6.19/linux-headers-2.6.19.7-001p1-amd64-envcan_2.6.19.7-001p1_amd64.deb 2.6.20.3 + RSDL 0.31: http://linux-dev.qc.ec.gc.ca/kernel/debian/etch/x86_64/2.6.20/linux-image-2.6.20.3-001-rsdl-0.31-amd64-envcan_2.6.20.3-001-rsdl-0.31_amd64.deb http://linux-dev.qc.ec.gc.ca/kernel/debian/etch/x86_64/2.6.20/linux-headers-2.6.20.3-001-rsdl-0.31-amd64-envcan_2.6.20.3-001-rsdl-0.31_amd64.deb 2.6.20.3 (Vanilla) http://linux-dev.qc.ec.gc.ca/kernel/debian/etch/x86_64/2.6.20/linux-image-2.6.20.3-001-amd64-envcan_2.6.20.3-001_amd64.deb http://linux-dev.qc.ec.gc.ca/kernel/debian/etch/x86_64/2.6.20/linux-headers-2.6.20.3-001-amd64-envcan_2.6.20.3-001_amd64.deb Comments are welcomed! Vincent Fortier Informatique Environnement Canada - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RSDL v0.29 backport to 2.6.18.8
Hello, again, I just saw that my 0.28 patch file was wrongly named 0.26 and that there is a new version 0.29 of RSDL that just came out... so here is the backported RSDL 0.29 to a 2.6.18.8 kernel. This does compile but I did not got the time to fully test it yet. > > Here is an update for RSDL to version 0.28 > > Full patch: > http://ck.kolivas.org/patches/staircase-deadline/2.6.20-sched- > rsdl-0.28.patch > > Series: > http://ck.kolivas.org/patches/staircase-deadline/2.6.20/ > > The patch to get you from 0.26 to 0.28: > http://ck.kolivas.org/patches/staircase-deadline/2.6.20/sched- > rsdl-0.26-0.28.patch > > A similar patch and directories will be made for 2.6.21-rc3 > without further announcement > Once again, thanx Con for this nice piece of code. Also note that this patch already includes a few other patches from 2.6.19+ kernel and there might also be other small pieces of code comming from a 2.6.19+ kernel: PATCH 1: http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.20.y.git;a=co mmit;h=ece8a684c75df215320b4155944979e3f78c5c93 PATCH 2: http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.20.y.git;a=co mmit;h=08c183f31bdbb709f177f6d3110d5f288ea33933 PATCH 3: Original RSDL patches (thnx again Con) http://ck.kolivas.org/patches/staircase-deadline/ Due to the project I'm currently working on, this will, in the next few weeks, help me out comparing heavy loads on a Debian Sarge/Etch 32/64 platform. Suggestions on benchmark tools would greatly be appreciated. Again, duno if this will be helpfull for anybody... but who knows! - vin sched-rsdl-0.29-backport-kernel-2.6.18.patch.gz Description: GNU Zip compressed data
RSDL v0.28 for 2.6.20 -> backport to 2.6.18.8
Hi all, > > Here is an update for RSDL to version 0.28 > > Full patch: > http://ck.kolivas.org/patches/staircase-deadline/2.6.20-sched- > rsdl-0.28.patch > > Series: > http://ck.kolivas.org/patches/staircase-deadline/2.6.20/ > > The patch to get you from 0.26 to 0.28: > http://ck.kolivas.org/patches/staircase-deadline/2.6.20/sched- > rsdl-0.26-0.28.patch > > A similar patch and directories will be made for 2.6.21-rc3 > without further announcement > First of all, thanx Con for this nice piece of code. I've been trying in the last few days to backport this new scheduler to a 2.6.18 kernel. After a lot of efforts I have finally been able to compile and run a RSDL patched 2.6.18.8 kernel on a x86_64 arch and actually my test PC booted 2-3 seconds faster with it compared to a vanilla 2.6.18.8 kernel. This patch includes a few other patches from 2.6.19+ kernel: PATCH 1: http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.20.y.git;a=co mmit;h=ece8a684c75df215320b4155944979e3f78c5c93 PATCH 2: http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.20.y.git;a=co mmit;h=08c183f31bdbb709f177f6d3110d5f288ea33933 PATCH 3: The patch to get you from 0.26 to 0.28: http://ck.kolivas.org/patches/staircase-deadline/2.6.20/sched-rsdl-0.26- 0.28.patch There might also be other small pieces of code comming from a 2.6.19+ kernel. Due to the project I'm currently working on, this will, in the next few weeks, help me out comparing heavy loads on a Debian Sarge/Etch 32/64 platform. Suggestions on benchmark tools would greatly be appreciated. Duno if this will be helpfull for anybody but I tought it would be nice to give it back to the lkml community. - vin sched-rsdl-0.26-backport-kernel-2.6.18.patch.gz Description: sched-rsdl-0.26-backport-kernel-2.6.18.patch.gz
RSDL v0.28 for 2.6.20 - backport to 2.6.18.8
Hi all, Here is an update for RSDL to version 0.28 Full patch: http://ck.kolivas.org/patches/staircase-deadline/2.6.20-sched- rsdl-0.28.patch Series: http://ck.kolivas.org/patches/staircase-deadline/2.6.20/ The patch to get you from 0.26 to 0.28: http://ck.kolivas.org/patches/staircase-deadline/2.6.20/sched- rsdl-0.26-0.28.patch A similar patch and directories will be made for 2.6.21-rc3 without further announcement First of all, thanx Con for this nice piece of code. I've been trying in the last few days to backport this new scheduler to a 2.6.18 kernel. After a lot of efforts I have finally been able to compile and run a RSDL patched 2.6.18.8 kernel on a x86_64 arch and actually my test PC booted 2-3 seconds faster with it compared to a vanilla 2.6.18.8 kernel. This patch includes a few other patches from 2.6.19+ kernel: PATCH 1: http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.20.y.git;a=co mmit;h=ece8a684c75df215320b4155944979e3f78c5c93 PATCH 2: http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.20.y.git;a=co mmit;h=08c183f31bdbb709f177f6d3110d5f288ea33933 PATCH 3: The patch to get you from 0.26 to 0.28: http://ck.kolivas.org/patches/staircase-deadline/2.6.20/sched-rsdl-0.26- 0.28.patch There might also be other small pieces of code comming from a 2.6.19+ kernel. Due to the project I'm currently working on, this will, in the next few weeks, help me out comparing heavy loads on a Debian Sarge/Etch 32/64 platform. Suggestions on benchmark tools would greatly be appreciated. Duno if this will be helpfull for anybody but I tought it would be nice to give it back to the lkml community. - vin sched-rsdl-0.26-backport-kernel-2.6.18.patch.gz Description: sched-rsdl-0.26-backport-kernel-2.6.18.patch.gz
RSDL v0.29 backport to 2.6.18.8
Hello, again, I just saw that my 0.28 patch file was wrongly named 0.26 and that there is a new version 0.29 of RSDL that just came out... so here is the backported RSDL 0.29 to a 2.6.18.8 kernel. This does compile but I did not got the time to fully test it yet. Here is an update for RSDL to version 0.28 Full patch: http://ck.kolivas.org/patches/staircase-deadline/2.6.20-sched- rsdl-0.28.patch Series: http://ck.kolivas.org/patches/staircase-deadline/2.6.20/ The patch to get you from 0.26 to 0.28: http://ck.kolivas.org/patches/staircase-deadline/2.6.20/sched- rsdl-0.26-0.28.patch A similar patch and directories will be made for 2.6.21-rc3 without further announcement Once again, thanx Con for this nice piece of code. Also note that this patch already includes a few other patches from 2.6.19+ kernel and there might also be other small pieces of code comming from a 2.6.19+ kernel: PATCH 1: http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.20.y.git;a=co mmit;h=ece8a684c75df215320b4155944979e3f78c5c93 PATCH 2: http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.20.y.git;a=co mmit;h=08c183f31bdbb709f177f6d3110d5f288ea33933 PATCH 3: Original RSDL patches (thnx again Con) http://ck.kolivas.org/patches/staircase-deadline/ Due to the project I'm currently working on, this will, in the next few weeks, help me out comparing heavy loads on a Debian Sarge/Etch 32/64 platform. Suggestions on benchmark tools would greatly be appreciated. Again, duno if this will be helpfull for anybody... but who knows! - vin sched-rsdl-0.29-backport-kernel-2.6.18.patch.gz Description: GNU Zip compressed data
Re: Sound 2.6.19: Soundcard driver often fail to load?
Le vendredi 23 février 2007, vous avez écrit : > At Wed, 21 Feb 2007 05:50:48 -0500, > Veronique & Vincent wrote: > > > > Hi, > > > > I'm currently running a 2.6.19 kernel and 2 times out of 3 the sound driver > > fails to load hence probing me a no sound device available in KDE. > > > > Could the snd-usb-audio interfere with the on-board sound driver? > > Yes, if you set index=0 module option to snd-intel8x0 driver and > nothing to snd-usb-audio, they may conflict according to the order of > loaded modules. Pass index=1 (or index=-2) to snd-usb-audio module > option to make the index order consistent. > Now there is a bug opened up at redhat: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=229227 I've ran into this info: http://www.lavrsen.dk/twiki/bin/view/PWC/FrequentlyAskedQuestionsPWC#modprobe_fails_with_FATAL_Error and did removed the index=X line associated with the pwc driver. This still create a problem from time to time. Seems like the index=X option is broken in the alsa driver (or maybie deprecated, remove, buggy, duno?). There is another way to fix the problem by using a /etc/asound.conf file (see http://alsa.opensrc.org/FAQ026) and removing the index=X entries from your mdoprobe.conf file Maybie the Fedora team should use the asound.conf configuration instead? > Takashi thnx! - vin - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Sound 2.6.19: Soundcard driver often fail to load?
Le vendredi 23 février 2007, vous avez écrit : At Wed, 21 Feb 2007 05:50:48 -0500, Veronique Vincent wrote: Hi, I'm currently running a 2.6.19 kernel and 2 times out of 3 the sound driver fails to load hence probing me a no sound device available in KDE. Could the snd-usb-audio interfere with the on-board sound driver? Yes, if you set index=0 module option to snd-intel8x0 driver and nothing to snd-usb-audio, they may conflict according to the order of loaded modules. Pass index=1 (or index=-2) to snd-usb-audio module option to make the index order consistent. Now there is a bug opened up at redhat: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=229227 I've ran into this info: http://www.lavrsen.dk/twiki/bin/view/PWC/FrequentlyAskedQuestionsPWC#modprobe_fails_with_FATAL_Error and did removed the index=X line associated with the pwc driver. This still create a problem from time to time. Seems like the index=X option is broken in the alsa driver (or maybie deprecated, remove, buggy, duno?). There is another way to fix the problem by using a /etc/asound.conf file (see http://alsa.opensrc.org/FAQ026) and removing the index=X entries from your mdoprobe.conf file Maybie the Fedora team should use the asound.conf configuration instead? Takashi thnx! - vin - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Boot time Bluetooth BUG: warning: (value > m) at hid-core.c:793
> > > > I've set up the hid-core.c to DEBUG mode... and it literally got pretty verbose... > > > thanks for the output. Is this really the full output? The important part > > - report descriptor dump - seems to be missing in the output (it should > > read something like "hid-core.c: report descriptor (size XY, read YZ) = > > ... some hexadecimal numbers". This should be output by the time the HID > > device is connected. The full dmesg with define DEBUG was included in the original message. Unless something else was needed? > Can I get something useful without a kernel recompile, with something > like evtest? I have users on Fedora hitting this too. It very likely is > a regression caused by the new unified HID. I was actually getting that on a stock FC6 kernel. The dmesg output comes from a recompiled vanilla 2.6.19.x with the exact same configuration BUT the modified define's in hid-core.c and a local version appended to the .config file. So this BUG does not only affect FC6 users but also the vanilla kernel. > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=227598 > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=228755 Good thing, I've added myself to the CC list of both. > > -- Pete > - vin - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Boot time Bluetooth BUG: warning: (value m) at hid-core.c:793
I've set up the hid-core.c to DEBUG mode... and it literally got pretty verbose... thanks for the output. Is this really the full output? The important part - report descriptor dump - seems to be missing in the output (it should read something like hid-core.c: report descriptor (size XY, read YZ) = ... some hexadecimal numbers. This should be output by the time the HID device is connected. The full dmesg with define DEBUG was included in the original message. Unless something else was needed? Can I get something useful without a kernel recompile, with something like evtest? I have users on Fedora hitting this too. It very likely is a regression caused by the new unified HID. I was actually getting that on a stock FC6 kernel. The dmesg output comes from a recompiled vanilla 2.6.19.x with the exact same configuration BUT the modified define's in hid-core.c and a local version appended to the .config file. So this BUG does not only affect FC6 users but also the vanilla kernel. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=227598 https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=228755 Good thing, I've added myself to the CC list of both. -- Pete - vin - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Fwd: RE: Boot time Bluetooth BUG: warning: (value > m) at hid-core.c:793
Hi again Marcel and Jiri, I've set up the hid-core.c to DEBUG mode... and it literally got pretty verbose... At line 2114 we finally get the BUG message (I've attached the full dmesg also...) : 2104 drivers/usb/input/hid-core.c: report (size 8) (unnumbered) 2105 drivers/usb/input/hid-core.c: report 0 (size 8) = 00 00 00 00 00 00 00 00 2106 hid-debug: input Keyboard.00e0 = 0 2107 hid-debug: input Keyboard.00e1 = 0 2108 hid-debug: input Keyboard.00e2 = 0 2109 hid-debug: input Keyboard.00e3 = 0 2110 hid-debug: input Keyboard.00e4 = 0 2111 hid-debug: input Keyboard.00e5 = 0 2112 hid-debug: input Keyboard.00e6 = 0 2113 hid-debug: input Keyboard.00e7 = 0 2114 BUG: warning at drivers/usb/input/hid-core.c:797/implement() 2115 [] dump_trace+0x69/0x1b6 2116 [] show_trace_log_lvl+0x18/0x2c 2117 [] show_trace+0xf/0x11 2118 [] dump_stack+0x15/0x17 2119 [] hid_output_report+0x1f8/0x2a3 2120 [] hid_submit_ctrl+0x55/0x214 2121 [] hid_submit_report+0x134/0x15f 2122 [] hiddev_ioctl+0x327/0x88a 2123 [] do_ioctl+0x4c/0x62 2124 [] vfs_ioctl+0x24a/0x25c 2125 [] sys_ioctl+0x4c/0x66 2126 [] sysenter_past_esp+0x56/0x79 2127 [] 0xb7f8c410 2128 === 2129 BUG: warning at drivers/usb/input/hid-core.c:797/implement() 2130 [] dump_trace+0x69/0x1b6 2131 [] show_trace_log_lvl+0x18/0x2c ... 2157 [] 0xb7f8c410 2158 === 2159 drivers/usb/input/hid-core.c: submitting ctrl urb: Set_Report wValue=0x0210 wIndex=0x wLength=7 2160 BUG: warning at drivers/usb/input/hid-core.c:797/implement() 2161 [] dump_trace+0x69/0x1b6 ... 2184 [] do_ioctl+0x4c/0x62 2185 [] vfs_ioctl+0x24a/0x25c 2186 [] sys_ioctl+0x4c/0x66 2187 [] sysenter_past_esp+0x56/0x79 2188 [] 0xb7f8c410 2189 === 2190 drivers/usb/input/hid-core.c: submitting ctrl urb: Set_Report wValue=0x0210 wIndex=0x wLength=7 2191 drivers/usb/input/hid-core.c: report (size 8) (unnumbered) 2192 drivers/usb/input/hid-core.c: report 0 (size 8) = 00 00 00 00 00 00 00 00 2193 hid-debug: input Keyboard.00e0 = 0 2194 hid-debug: input Keyboard.00e1 = 0 2195 hid-debug: input Keyboard.00e2 = 0 2196 hid-debug: input Keyboard.00e3 = 0 2197 hid-debug: input Keyboard.00e4 = 0 2198 hid-debug: input Keyboard.00e5 = 0 2199 hid-debug: input Keyboard.00e6 = 0 2200 hid-debug: input Keyboard.00e7 = 0 2201 drivers/usb/input/hid-core.c: report (size 7) (numbered) 2202 drivers/usb/input/hid-core.c: report 16 (size 6) = ff 80 80 01 00 00 2203 hid-debug: input Undefined.0001 = 1 2204 hid-debug: input c06a.8f60 = 1 2205 hid-debug: input c06a.8f60 = 1 2206 hid-debug: input ff00.0001 = 1 2207 BUG: warning at drivers/usb/input/hid-core.c:797/implement() 2208 [] dump_trace+0x69/0x1b6 2209 [] show_trace_log_lvl+0x18/0x2c 2210 [] show_trace+0xf/0x11 2211 [] dump_stack+0x15/0x17 2212 [] hid_output_report+0x1f8/0x2a3 2213 [] hid_submit_ctrl+0x55/0x214 2214 [] hid_submit_report+0x134/0x15f 2215 [] hiddev_ioctl+0x327/0x88a 2216 [] do_ioctl+0x4c/0x62 2217 [] vfs_ioctl+0x24a/0x25c 2218 [] sys_ioctl+0x4c/0x66 2219 [] sysenter_past_esp+0x56/0x79 2220 [] 0xb7f8c410 2221 === BUG: warning at drivers/usb/input/hid-core.c:797/implement() ... 2249 [] sysenter_past_esp+0x56/0x79 2250 [] 0xb7f8c410 2251 === 2252 drivers/usb/input/hid-core.c: submitting ctrl urb: Set_Report wValue=0x0210 wIndex=0x wLength=7 2253 drivers/usb/input/hid-core.c: report (size 7) (numbered) 2254 drivers/usb/input/hid-core.c: report 16 (size 6) = ff 80 00 00 30 00 2255 hid-debug: input ff00.0001 = 0 2256 hid-debug: input Button.0001 = 1 2257 drivers/usb/input/hid-core.c: report (size 7) (numbered) 2258 drivers/usb/input/hid-core.c: report 16 (size 6) = ff 81 80 01 00 00 2259 hid-debug: input ff00.0001 = 1 2260 hid-debug: input Button.0001 = 0 2261 Bluetooth: Core ver 2.11 2262 NET: Registered protocol family 31 2263 Bluetooth: HCI device and connection manager initialized 2264 Bluetooth: HCI socket layer initialized 2265 Bluetooth: L2CAP ver 2.8 2266 Bluetooth: L2CAP socket layer initialized 2267 Bluetooth: RFCOMM socket layer initialized 2268 Bluetooth: RFCOMM TTY layer initialized 2269 Bluetooth: RFCOMM ver 1.8 2270 usb 2-2.1: new full speed USB device using uhci_hcd and address 5 2271 drivers/usb/input/hid-core.c: report (size 8) (unnumbered) 2272 drivers/usb/input/hid-core.c: report 0 (size 8) = 00 00 00 00 00 00 00 00 2273 hid-debug: input Keyboard.00e0 = 0 2274 hid-debug: input Keyboard.00e1 = 0 2275 hid-debug: input Keyboard.00e2 = 0 2276 hid-debug: input Keyboard.00e3 = 0 2277 hid-debug: input Keyboard.00e4 = 0 2278 hid-debug: input Keyboard.00e5 = 0 2279 hid-debug: input Keyboard.00e6 = 0 2280 hid-debug: input Keyboard.00e7 = 0 2281 usb 2-2.1: configuration #1 chosen from 1 choice 2282 Bluetooth: HCI USB driver ver 2.9 2283 usbcore: registered new interface driver hci_usb 2284 drivers/usb/input/hid-core.c: report (size 7) (numbered) 2285 drivers/usb/input/hid-core.c: report 2 (size 6) = 00 00 00 00
Fwd: RE: Boot time Bluetooth BUG: warning: (value m) at hid-core.c:793
Hi again Marcel and Jiri, I've set up the hid-core.c to DEBUG mode... and it literally got pretty verbose... At line 2114 we finally get the BUG message (I've attached the full dmesg also...) : 2104 drivers/usb/input/hid-core.c: report (size 8) (unnumbered) 2105 drivers/usb/input/hid-core.c: report 0 (size 8) = 00 00 00 00 00 00 00 00 2106 hid-debug: input Keyboard.00e0 = 0 2107 hid-debug: input Keyboard.00e1 = 0 2108 hid-debug: input Keyboard.00e2 = 0 2109 hid-debug: input Keyboard.00e3 = 0 2110 hid-debug: input Keyboard.00e4 = 0 2111 hid-debug: input Keyboard.00e5 = 0 2112 hid-debug: input Keyboard.00e6 = 0 2113 hid-debug: input Keyboard.00e7 = 0 2114 BUG: warning at drivers/usb/input/hid-core.c:797/implement() 2115 [c0404c70] dump_trace+0x69/0x1b6 2116 [c0404dd5] show_trace_log_lvl+0x18/0x2c 2117 [c04053bc] show_trace+0xf/0x11 2118 [c04054b9] dump_stack+0x15/0x17 2119 [c0589a5b] hid_output_report+0x1f8/0x2a3 2120 [c0589b5b] hid_submit_ctrl+0x55/0x214 2121 [c0589ee7] hid_submit_report+0x134/0x15f 2122 [c058c955] hiddev_ioctl+0x327/0x88a 2123 [c0479198] do_ioctl+0x4c/0x62 2124 [c04793f8] vfs_ioctl+0x24a/0x25c 2125 [c0479456] sys_ioctl+0x4c/0x66 2126 [c0403de5] sysenter_past_esp+0x56/0x79 2127 [b7f8c410] 0xb7f8c410 2128 === 2129 BUG: warning at drivers/usb/input/hid-core.c:797/implement() 2130 [c0404c70] dump_trace+0x69/0x1b6 2131 [c0404dd5] show_trace_log_lvl+0x18/0x2c ... 2157 [b7f8c410] 0xb7f8c410 2158 === 2159 drivers/usb/input/hid-core.c: submitting ctrl urb: Set_Report wValue=0x0210 wIndex=0x wLength=7 2160 BUG: warning at drivers/usb/input/hid-core.c:797/implement() 2161 [c0404c70] dump_trace+0x69/0x1b6 ... 2184 [c0479198] do_ioctl+0x4c/0x62 2185 [c04793f8] vfs_ioctl+0x24a/0x25c 2186 [c0479456] sys_ioctl+0x4c/0x66 2187 [c0403de5] sysenter_past_esp+0x56/0x79 2188 [b7f8c410] 0xb7f8c410 2189 === 2190 drivers/usb/input/hid-core.c: submitting ctrl urb: Set_Report wValue=0x0210 wIndex=0x wLength=7 2191 drivers/usb/input/hid-core.c: report (size 8) (unnumbered) 2192 drivers/usb/input/hid-core.c: report 0 (size 8) = 00 00 00 00 00 00 00 00 2193 hid-debug: input Keyboard.00e0 = 0 2194 hid-debug: input Keyboard.00e1 = 0 2195 hid-debug: input Keyboard.00e2 = 0 2196 hid-debug: input Keyboard.00e3 = 0 2197 hid-debug: input Keyboard.00e4 = 0 2198 hid-debug: input Keyboard.00e5 = 0 2199 hid-debug: input Keyboard.00e6 = 0 2200 hid-debug: input Keyboard.00e7 = 0 2201 drivers/usb/input/hid-core.c: report (size 7) (numbered) 2202 drivers/usb/input/hid-core.c: report 16 (size 6) = ff 80 80 01 00 00 2203 hid-debug: input Undefined.0001 = 1 2204 hid-debug: input c06a.8f60 = 1 2205 hid-debug: input c06a.8f60 = 1 2206 hid-debug: input ff00.0001 = 1 2207 BUG: warning at drivers/usb/input/hid-core.c:797/implement() 2208 [c0404c70] dump_trace+0x69/0x1b6 2209 [c0404dd5] show_trace_log_lvl+0x18/0x2c 2210 [c04053bc] show_trace+0xf/0x11 2211 [c04054b9] dump_stack+0x15/0x17 2212 [c0589a5b] hid_output_report+0x1f8/0x2a3 2213 [c0589b5b] hid_submit_ctrl+0x55/0x214 2214 [c0589ee7] hid_submit_report+0x134/0x15f 2215 [c058c955] hiddev_ioctl+0x327/0x88a 2216 [c0479198] do_ioctl+0x4c/0x62 2217 [c04793f8] vfs_ioctl+0x24a/0x25c 2218 [c0479456] sys_ioctl+0x4c/0x66 2219 [c0403de5] sysenter_past_esp+0x56/0x79 2220 [b7f8c410] 0xb7f8c410 2221 === BUG: warning at drivers/usb/input/hid-core.c:797/implement() ... 2249 [c0403de5] sysenter_past_esp+0x56/0x79 2250 [b7f8c410] 0xb7f8c410 2251 === 2252 drivers/usb/input/hid-core.c: submitting ctrl urb: Set_Report wValue=0x0210 wIndex=0x wLength=7 2253 drivers/usb/input/hid-core.c: report (size 7) (numbered) 2254 drivers/usb/input/hid-core.c: report 16 (size 6) = ff 80 00 00 30 00 2255 hid-debug: input ff00.0001 = 0 2256 hid-debug: input Button.0001 = 1 2257 drivers/usb/input/hid-core.c: report (size 7) (numbered) 2258 drivers/usb/input/hid-core.c: report 16 (size 6) = ff 81 80 01 00 00 2259 hid-debug: input ff00.0001 = 1 2260 hid-debug: input Button.0001 = 0 2261 Bluetooth: Core ver 2.11 2262 NET: Registered protocol family 31 2263 Bluetooth: HCI device and connection manager initialized 2264 Bluetooth: HCI socket layer initialized 2265 Bluetooth: L2CAP ver 2.8 2266 Bluetooth: L2CAP socket layer initialized 2267 Bluetooth: RFCOMM socket layer initialized 2268 Bluetooth: RFCOMM TTY layer initialized 2269 Bluetooth: RFCOMM ver 1.8 2270 usb 2-2.1: new full speed USB device using uhci_hcd and address 5 2271 drivers/usb/input/hid-core.c: report (size 8) (unnumbered) 2272 drivers/usb/input/hid-core.c: report 0 (size 8) = 00 00 00 00 00 00 00 00 2273 hid-debug: input Keyboard.00e0 = 0 2274 hid-debug: input Keyboard.00e1 = 0 2275 hid-debug: input Keyboard.00e2 = 0 2276 hid-debug: input Keyboard.00e3 = 0 2277 hid-debug: input Keyboard.00e4 = 0 2278 hid-debug: input Keyboard.00e5 = 0 2279 hid-debug: input Keyboard.00e6 = 0 2280 hid-debug: input
