* 2.6.33-rc6: Reported regressions from 2.6.32 @ 2010-02-01 0:18 Rafael J. Wysocki 2010-02-01 0:19 ` [Bug #14791] Something has been broken in the network stack this week Rafael J. Wysocki ` (25 more replies) 0 siblings, 26 replies; 76+ messages in thread From: Rafael J. Wysocki @ 2010-02-01 0:18 UTC (permalink / raw) To: Linux Kernel Mailing List Cc: Adrian Bunk, Andrew Morton, Linus Torvalds, Natalie Protasevich, Kernel Testers List, Network Development, Linux ACPI, Linux PM List, Linux SCSI List, Linux Wireless List, DRI This message contains a list of some regressions from 2.6.32, for which there are no fixes in the mainline I know of. If any of them have been fixed already, please let me know. If you know of any other unresolved regressions from 2.6.32, please let me know either and I'll add them to the list. Also, please let me know if any of the entries below are invalid. Each entry from the list will be sent additionally in an automatic reply to this message with CCs to the people involved in reporting and handling the issue. Listed regressions statistics: Date Total Pending Unresolved ---------------------------------------- 2010-02-01 85 26 21 2010-01-24 75 29 23 2010-01-10 55 33 21 2009-12-29 36 34 27 Unresolved regressions ---------------------- Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15202 Subject : lockdep warning during elevator_switch Submitter : Hugh Dickins <hugh.dickins@tiscali.co.uk> Date : 2010-01-31 23:55 (1 days old) References : http://marc.info/?l=linux-kernel&m=126498212613051&w=4 Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15200 Subject : NFS problems in 2.6.33-rc6: Unknown error 526 Submitter : J.A. Magallón <jamagallon@ono.com> Date : 2010-01-31 22:46 (1 days old) References : http://marc.info/?l=linux-kernel&m=126497800408928&w=4 Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15199 Subject : sata_nv and no /dev files Submitter : Bartłomiej Zimoń <uzi18@o2.pl> Date : 2010-01-31 23:45 (1 days old) References : http://marc.info/?l=linux-kernel&m=126498153112488&w=4 Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15196 Subject : kmem_cache_create: duplicate cache ccid2_h Submitter : Heinz Diehl <htd@fancy-poultry.org> Date : 2010-01-30 18:33 (2 days old) References : http://marc.info/?l=linux-kernel&m=126487640324942&w=4 Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15192 Subject : netperf ~50% regression with 2.6.33-rc1, bisect to 1b9508f Submitter : Lin Ming <ming.m.lin@intel.com> Date : 2010-01-25 10:03 (7 days old) First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1b9508f6831e10d53256825de8904caa22d1ca2c References : http://marc.info/?l=linux-kernel&m=126441481427331&w=4 Handled-By : Mike Galbraith <efault@gmx.de> Peter Zijlstra <peterz@infradead.org> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15144 Subject : HDA Intel Audio hang on boot Submitter : Sid Boyce <sboyce@blueyonder.co.uk> Date : 2010-01-15 1:24 (17 days old) References : http://marc.info/?l=linux-kernel&m=126351866722507&w=4 Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15142 Subject : "INFO: possible circular locking dependency detected" Submitter : Matti Aarnio <matti.aarnio--kernel-bugzilla@zmailer.org> Date : 2010-01-25 13:38 (7 days old) Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15139 Subject : e1000: transmit queue 0 timed out Submitter : Alexander Beregalov <a.beregalov@gmail.com> Date : 2010-01-23 15:37 (9 days old) References : http://marc.info/?l=linux-netdev&m=126426149306083&w=4 Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15138 Subject : evdev regression on macbook Submitter : Guillaume Chazarain <guichaz@gmail.com> Date : 2010-01-23 18:53 (9 days old) References : http://marc.info/?l=linux-kernel&m=126427286219235&w=4 Handled-By : Dmitry Torokhov <dmitry.torokhov@gmail.com> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15125 Subject : hung task - jbd2/dm-1-8 (during raid rebuild) Submitter : Michael Breuer <mbreuer@majjas.com> Date : 2010-01-10 21:47 (22 days old) References : http://marc.info/?l=linux-kernel&m=126316012025978&w=4 Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15124 Subject : PCI host bridge windows ignored (works with pci=use_crs) Submitter : Jeff Garrett <jeff@jgarrett.org> Date : 2010-01-13 5:37 (19 days old) References : http://marc.info/?l=linux-kernel&m=126336296600307&w=4 Handled-By : Yinghai Lu <yinghai@kernel.org> Bjorn Helgaas <bjorn.helgaas@hp.com> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15119 Subject : iwl_bg_scan_completed: WARN on scan complete Submitter : Alex Zhavnerchik <alex.vizor@gmail.com> Date : 2010-01-24 12:27 (8 days old) Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15114 Subject : X.org hang with [drm:i915_gem_do_execbuffer] *ERROR* in dmesg Submitter : Matej Laitl <strohel@gmail.com> Date : 2010-01-23 19:54 (9 days old) Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15076 Subject : System panic under load with clockevents_program_event Submitter : okias <d.okias@gmail.com> Date : 2010-01-17 13:03 (15 days old) Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15043 Subject : Display goes off with i915.powersave=1 after suspend-resume Submitter : Soeren Sonnenburg <sonne@debian.org> Date : 2010-01-10 20:09 (22 days old) References : http://marc.info/?l=linux-kernel&m=126315457519505&w=4 Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15036 Subject : soft lockup in dmesg after suspend/resume Submitter : ykzhao <yakui.zhao@intel.com> Date : 2010-01-04 5:36 (28 days old) References : http://marc.info/?l=linux-kernel&m=126258356202722&w=4 Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15025 Subject : Oops in ext4 driver Submitter : Steinar H. Gunderson <sgunderson@bigfoot.com> Date : 2010-01-10 13:09 (22 days old) Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14999 Subject : possible circular locking dependency detected in rfkill at suspend Submitter : Christian Casteyde <casteyde.christian@free.fr> Date : 2010-01-06 21:52 (26 days old) Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14950 Subject : tbench regression with 2.6.33-rc1 Submitter : Lin Ming <ming.m.lin@intel.com> Date : 2009-12-25 11:11 (38 days old) References : http://marc.info/?l=linux-kernel&m=126174044213172&w=4 Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14937 Subject : WARNING: at kernel/lockdep.c:2830 Submitter : Grant Wilson <grant.wilson@zen.co.uk> Date : 2009-12-27 13:35 (36 days old) References : http://marc.info/?l=linux-kernel&m=126192220404829&w=4 Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14792 Subject : Misdetection of the TV output Submitter : Santi <santi@agolina.net> Date : 2009-12-12 13:28 (51 days old) First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=27dfaf4f5825a119305db1bc63bef30ed400e376 Handled-By : Zhao Yakui <yakui.zhao@intel.com> Regressions with patches ------------------------ Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15198 Subject : Radeon KMS regression Submitter : Kevin Winchester <kjwinchester@gmail.com> Date : 2010-01-30 17:18 (2 days old) First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=42590a75019a50012f25a962246498dead428433 References : http://marc.info/?l=linux-kernel&m=126487191019612&w=4 Handled-By : FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp> Patch : http://patchwork.kernel.org/patch/75023/ Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15195 Subject : kernel BUG at include/net/netns/generic.h:41, pfkey_create+0x36/0x18b [af_key] Submitter : Luca Tettamanti <kronos.it@gmail.com> Date : 2010-01-30 13:23 (2 days old) References : http://marc.info/?l=linux-netdev&m=126485785004775&w=4 Handled-By : Alexey Dobriyan <adobriyan@gmail.com> Patch : http://patchwork.kernel.org/patch/75891/ Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15039 Subject : leds_alix2: can't allocate I/O for GPIO Submitter : Arnd Hannemann <hannemann@nets.rwth-aachen.de> Date : 2010-01-07 10:26 (25 days old) References : http://marc.info/?l=linux-kernel&m=126286001106257&w=4 Handled-By : Daniel Mack <daniel@caiaq.de> Patch : http://patchwork.kernel.org/patch/72006/ Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14949 Subject : drm_vm.c:drm_mmap: possible circular locking dependency detected Submitter : Borislav Petkov <petkovbb@googlemail.com> Date : 2009-12-26 9:45 (37 days old) References : http://marc.info/?l=linux-kernel&m=126182073616279&w=4 Handled-By : Eric W. Biederman <ebiederm@aristanetworks.com> Patch : http://patchwork.kernel.org/patch/70461/ Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14791 Subject : Something has been broken in the network stack this week Submitter : Delete This Account <speedyboyinovator@hotmail.com> Date : 2009-12-12 13:06 (51 days old) Handled-By : Ben Hutchings <ben@decadent.org.uk> Patch : http://patchwork.kernel.org/patch/72073/ For details, please visit the bug entries and follow the links given in references. As you can see, there is a Bugzilla entry for each of the listed regressions. There also is a Bugzilla entry used for tracking the regressions from 2.6.32, unresolved as well as resolved, at: http://bugzilla.kernel.org/show_bug.cgi?id=14885 Please let me know if there are any Bugzilla entries that should be added to the list in there. Thanks, Rafael ^ permalink raw reply [flat|nested] 76+ messages in thread
* [Bug #14791] Something has been broken in the network stack this week 2010-02-01 0:18 2.6.33-rc6: Reported regressions from 2.6.32 Rafael J. Wysocki @ 2010-02-01 0:19 ` Rafael J. Wysocki 2010-02-01 0:46 ` Ben Hutchings 2010-02-01 0:22 ` [Bug #14937] WARNING: at kernel/lockdep.c:2830 Rafael J. Wysocki ` (24 subsequent siblings) 25 siblings, 1 reply; 76+ messages in thread From: Rafael J. Wysocki @ 2010-02-01 0:19 UTC (permalink / raw) To: Linux Kernel Mailing List Cc: Kernel Testers List, Ben Hutchings, David S. Miller, Delete This Account This message has been generated automatically as a part of a report of recent regressions. The following bug entry is on the current list of known regressions from 2.6.32. Please verify if it still should be listed and let me know (either way). Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14791 Subject : Something has been broken in the network stack this week Submitter : Delete This Account <speedyboyinovator@hotmail.com> Date : 2009-12-12 13:06 (51 days old) Handled-By : Ben Hutchings <ben@decadent.org.uk> Patch : http://patchwork.kernel.org/patch/72073/ ^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: [Bug #14791] Something has been broken in the network stack this week 2010-02-01 0:19 ` [Bug #14791] Something has been broken in the network stack this week Rafael J. Wysocki @ 2010-02-01 0:46 ` Ben Hutchings 0 siblings, 0 replies; 76+ messages in thread From: Ben Hutchings @ 2010-02-01 0:46 UTC (permalink / raw) To: Rafael J. Wysocki Cc: Linux Kernel Mailing List, Kernel Testers List, David S. Miller [-- Attachment #1: Type: text/plain, Size: 897 bytes --] On Mon, 2010-02-01 at 01:19 +0100, Rafael J. Wysocki wrote: > This message has been generated automatically as a part of a report > of recent regressions. > > The following bug entry is on the current list of known regressions > from 2.6.32. Please verify if it still should be listed and let me know > (either way). > > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14791 > Subject : Something has been broken in the network stack this week > Submitter : Delete This Account <speedyboyinovator@hotmail.com> > Date : 2009-12-12 13:06 (51 days old) > Handled-By : Ben Hutchings <ben@decadent.org.uk> > Patch : http://patchwork.kernel.org/patch/72073/ Dave has accepted the patch but hasn't pushed it out yet. I expect that it will be in 2.6.33-rc7. Ben. -- Ben Hutchings Unix is many things to many people, but it's never been everything to anybody. [-- Attachment #2: This is a digitally signed message part --] [-- Type: application/pgp-signature, Size: 828 bytes --] ^ permalink raw reply [flat|nested] 76+ messages in thread
* [Bug #14937] WARNING: at kernel/lockdep.c:2830 2010-02-01 0:18 2.6.33-rc6: Reported regressions from 2.6.32 Rafael J. Wysocki 2010-02-01 0:19 ` [Bug #14791] Something has been broken in the network stack this week Rafael J. Wysocki @ 2010-02-01 0:22 ` Rafael J. Wysocki 2010-02-01 0:22 ` [Bug #14792] Misdetection of the TV output Rafael J. Wysocki ` (23 subsequent siblings) 25 siblings, 0 replies; 76+ messages in thread From: Rafael J. Wysocki @ 2010-02-01 0:22 UTC (permalink / raw) To: Linux Kernel Mailing List; +Cc: Kernel Testers List, Grant Wilson This message has been generated automatically as a part of a report of recent regressions. The following bug entry is on the current list of known regressions from 2.6.32. Please verify if it still should be listed and let me know (either way). Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14937 Subject : WARNING: at kernel/lockdep.c:2830 Submitter : Grant Wilson <grant.wilson@zen.co.uk> Date : 2009-12-27 13:35 (36 days old) References : http://marc.info/?l=linux-kernel&m=126192220404829&w=4 ^ permalink raw reply [flat|nested] 76+ messages in thread
* [Bug #14792] Misdetection of the TV output 2010-02-01 0:18 2.6.33-rc6: Reported regressions from 2.6.32 Rafael J. Wysocki 2010-02-01 0:19 ` [Bug #14791] Something has been broken in the network stack this week Rafael J. Wysocki 2010-02-01 0:22 ` [Bug #14937] WARNING: at kernel/lockdep.c:2830 Rafael J. Wysocki @ 2010-02-01 0:22 ` Rafael J. Wysocki 2010-02-01 0:22 ` [Bug #15036] soft lockup in dmesg after suspend/resume Rafael J. Wysocki ` (22 subsequent siblings) 25 siblings, 0 replies; 76+ messages in thread From: Rafael J. Wysocki @ 2010-02-01 0:22 UTC (permalink / raw) To: Linux Kernel Mailing List Cc: Kernel Testers List, Adam Jackson, Eric Anholt, Santi, Zhao Yakui This message has been generated automatically as a part of a report of recent regressions. The following bug entry is on the current list of known regressions from 2.6.32. Please verify if it still should be listed and let me know (either way). Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14792 Subject : Misdetection of the TV output Submitter : Santi <santi@agolina.net> Date : 2009-12-12 13:28 (51 days old) First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=27dfaf4f5825a119305db1bc63bef30ed400e376 Handled-By : Zhao Yakui <yakui.zhao@intel.com> ^ permalink raw reply [flat|nested] 76+ messages in thread
* [Bug #15036] soft lockup in dmesg after suspend/resume 2010-02-01 0:18 2.6.33-rc6: Reported regressions from 2.6.32 Rafael J. Wysocki ` (2 preceding siblings ...) 2010-02-01 0:22 ` [Bug #14792] Misdetection of the TV output Rafael J. Wysocki @ 2010-02-01 0:22 ` Rafael J. Wysocki 2010-02-01 0:22 ` [Bug #14950] tbench regression with 2.6.33-rc1 Rafael J. Wysocki ` (21 subsequent siblings) 25 siblings, 0 replies; 76+ messages in thread From: Rafael J. Wysocki @ 2010-02-01 0:22 UTC (permalink / raw) To: Linux Kernel Mailing List; +Cc: Kernel Testers List, ykzhao, Zou, Nanhai This message has been generated automatically as a part of a report of recent regressions. The following bug entry is on the current list of known regressions from 2.6.32. Please verify if it still should be listed and let me know (either way). Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15036 Subject : soft lockup in dmesg after suspend/resume Submitter : ykzhao <yakui.zhao@intel.com> Date : 2010-01-04 5:36 (28 days old) References : http://marc.info/?l=linux-kernel&m=126258356202722&w=4 ^ permalink raw reply [flat|nested] 76+ messages in thread
* [Bug #14950] tbench regression with 2.6.33-rc1 2010-02-01 0:18 2.6.33-rc6: Reported regressions from 2.6.32 Rafael J. Wysocki ` (3 preceding siblings ...) 2010-02-01 0:22 ` [Bug #15036] soft lockup in dmesg after suspend/resume Rafael J. Wysocki @ 2010-02-01 0:22 ` Rafael J. Wysocki 2010-02-01 7:57 ` Mike Galbraith 2010-02-01 0:22 ` [Bug #14949] drm_vm.c:drm_mmap: possible circular locking dependency detected Rafael J. Wysocki ` (20 subsequent siblings) 25 siblings, 1 reply; 76+ messages in thread From: Rafael J. Wysocki @ 2010-02-01 0:22 UTC (permalink / raw) To: Linux Kernel Mailing List; +Cc: Kernel Testers List, Lin Ming, Mike Galbraith This message has been generated automatically as a part of a report of recent regressions. The following bug entry is on the current list of known regressions from 2.6.32. Please verify if it still should be listed and let me know (either way). Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14950 Subject : tbench regression with 2.6.33-rc1 Submitter : Lin Ming <ming.m.lin@intel.com> Date : 2009-12-25 11:11 (38 days old) References : http://marc.info/?l=linux-kernel&m=126174044213172&w=4 ^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: [Bug #14950] tbench regression with 2.6.33-rc1 2010-02-01 0:22 ` [Bug #14950] tbench regression with 2.6.33-rc1 Rafael J. Wysocki @ 2010-02-01 7:57 ` Mike Galbraith 2010-02-02 20:45 ` Rafael J. Wysocki 0 siblings, 1 reply; 76+ messages in thread From: Mike Galbraith @ 2010-02-01 7:57 UTC (permalink / raw) To: Rafael J. Wysocki Cc: Linux Kernel Mailing List, Kernel Testers List, Lin Ming On Mon, 2010-02-01 at 01:22 +0100, Rafael J. Wysocki wrote: > This message has been generated automatically as a part of a report > of recent regressions. > > The following bug entry is on the current list of known regressions > from 2.6.32. Please verify if it still should be listed and let me know > (either way). Yes, it should remain open. Looking for places to trim overhead without injuring other things. The regression is a moving target on my HW. -Mike ^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: [Bug #14950] tbench regression with 2.6.33-rc1 2010-02-01 7:57 ` Mike Galbraith @ 2010-02-02 20:45 ` Rafael J. Wysocki 0 siblings, 0 replies; 76+ messages in thread From: Rafael J. Wysocki @ 2010-02-02 20:45 UTC (permalink / raw) To: Mike Galbraith; +Cc: Linux Kernel Mailing List, Kernel Testers List, Lin Ming On Monday 01 February 2010, Mike Galbraith wrote: > On Mon, 2010-02-01 at 01:22 +0100, Rafael J. Wysocki wrote: > > This message has been generated automatically as a part of a report > > of recent regressions. > > > > The following bug entry is on the current list of known regressions > > from 2.6.32. Please verify if it still should be listed and let me know > > (either way). > > Yes, it should remain open. Looking for places to trim overhead without > injuring other things. The regression is a moving target on my HW. Thanks for the update. Rafael ^ permalink raw reply [flat|nested] 76+ messages in thread
* [Bug #14949] drm_vm.c:drm_mmap: possible circular locking dependency detected 2010-02-01 0:18 2.6.33-rc6: Reported regressions from 2.6.32 Rafael J. Wysocki ` (4 preceding siblings ...) 2010-02-01 0:22 ` [Bug #14950] tbench regression with 2.6.33-rc1 Rafael J. Wysocki @ 2010-02-01 0:22 ` Rafael J. Wysocki 2010-02-01 18:01 ` Borislav Petkov 2010-02-01 0:22 ` [Bug #15039] leds_alix2: can't allocate I/O for GPIO Rafael J. Wysocki ` (19 subsequent siblings) 25 siblings, 1 reply; 76+ messages in thread From: Rafael J. Wysocki @ 2010-02-01 0:22 UTC (permalink / raw) To: Linux Kernel Mailing List Cc: Kernel Testers List, Borislav Petkov, DRI, Eric W. Biederman This message has been generated automatically as a part of a report of recent regressions. The following bug entry is on the current list of known regressions from 2.6.32. Please verify if it still should be listed and let me know (either way). Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14949 Subject : drm_vm.c:drm_mmap: possible circular locking dependency detected Submitter : Borislav Petkov <petkovbb@googlemail.com> Date : 2009-12-26 9:45 (37 days old) References : http://marc.info/?l=linux-kernel&m=126182073616279&w=4 Handled-By : Eric W. Biederman <ebiederm@aristanetworks.com> Patch : http://patchwork.kernel.org/patch/70461/ ^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: [Bug #14949] drm_vm.c:drm_mmap: possible circular locking dependency detected 2010-02-01 0:22 ` [Bug #14949] drm_vm.c:drm_mmap: possible circular locking dependency detected Rafael J. Wysocki @ 2010-02-01 18:01 ` Borislav Petkov 2010-02-02 20:46 ` Rafael J. Wysocki 0 siblings, 1 reply; 76+ messages in thread From: Borislav Petkov @ 2010-02-01 18:01 UTC (permalink / raw) To: Rafael J. Wysocki Cc: Linux Kernel Mailing List, Kernel Testers List, DRI, Eric W. Biederman On Mon, Feb 1, 2010 at 1:22 AM, Rafael J. Wysocki <rjw@sisk.pl> wrote: > This message has been generated automatically as a part of a report > of recent regressions. > > The following bug entry is on the current list of known regressions > from 2.6.32. Please verify if it still should be listed and let me know > (either way). > > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14949 > Subject : drm_vm.c:drm_mmap: possible circular locking dependency detected > Submitter : Borislav Petkov <petkovbb@googlemail.com> > Date : 2009-12-26 9:45 (37 days old) > References : http://marc.info/?l=linux-kernel&m=126182073616279&w=4 > Handled-By : Eric W. Biederman <ebiederm@aristanetworks.com> > Patch : http://patchwork.kernel.org/patch/70461/ Yes, this is fixed. -- Regards/Gruss, Boris ^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: [Bug #14949] drm_vm.c:drm_mmap: possible circular locking dependency detected 2010-02-01 18:01 ` Borislav Petkov @ 2010-02-02 20:46 ` Rafael J. Wysocki 2010-02-02 20:58 ` Borislav Petkov 0 siblings, 1 reply; 76+ messages in thread From: Rafael J. Wysocki @ 2010-02-02 20:46 UTC (permalink / raw) To: Borislav Petkov Cc: Linux Kernel Mailing List, Kernel Testers List, DRI, Eric W. Biederman On Monday 01 February 2010, Borislav Petkov wrote: > On Mon, Feb 1, 2010 at 1:22 AM, Rafael J. Wysocki <rjw@sisk.pl> wrote: > > This message has been generated automatically as a part of a report > > of recent regressions. > > > > The following bug entry is on the current list of known regressions > > from 2.6.32. Please verify if it still should be listed and let me know > > (either way). > > > > > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14949 > > Subject : drm_vm.c:drm_mmap: possible circular locking dependency detected > > Submitter : Borislav Petkov <petkovbb@googlemail.com> > > Date : 2009-12-26 9:45 (37 days old) > > References : http://marc.info/?l=linux-kernel&m=126182073616279&w=4 > > Handled-By : Eric W. Biederman <ebiederm@aristanetworks.com> > > Patch : http://patchwork.kernel.org/patch/70461/ > > Yes, this is fixed. Do you mean "fixed" as "the fix is in the Linus' tree" or "fixed" as "the patch fixed it for me"? Rafael ^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: [Bug #14949] drm_vm.c:drm_mmap: possible circular locking dependency detected 2010-02-02 20:46 ` Rafael J. Wysocki @ 2010-02-02 20:58 ` Borislav Petkov 2010-02-02 21:12 ` Rafael J. Wysocki 2010-02-03 2:18 ` Greg KH 0 siblings, 2 replies; 76+ messages in thread From: Borislav Petkov @ 2010-02-02 20:58 UTC (permalink / raw) To: Rafael J. Wysocki Cc: Linux Kernel Mailing List, Kernel Testers List, DRI, Eric W. Biederman, Greg KH (Adding Greg to Cc:) On Tue, Feb 02, 2010 at 09:46:45PM +0100, Rafael J. Wysocki wrote: > On Monday 01 February 2010, Borislav Petkov wrote: > > On Mon, Feb 1, 2010 at 1:22 AM, Rafael J. Wysocki <rjw@sisk.pl> wrote: > > > This message has been generated automatically as a part of a report > > > of recent regressions. > > > > > > The following bug entry is on the current list of known regressions > > > from 2.6.32. Please verify if it still should be listed and let me know > > > (either way). > > > > > > > > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14949 > > > Subject : drm_vm.c:drm_mmap: possible circular locking dependency detected > > > Submitter : Borislav Petkov <petkovbb@googlemail.com> > > > Date : 2009-12-26 9:45 (37 days old) > > > References : http://marc.info/?l=linux-kernel&m=126182073616279&w=4 > > > Handled-By : Eric W. Biederman <ebiederm@aristanetworks.com> > > > Patch : http://patchwork.kernel.org/patch/70461/ > > > > Yes, this is fixed. > > Do you mean "fixed" as "the fix is in the Linus' tree" or "fixed" as "the > patch fixed it for me"? Rather the second one, i.e. it fixes it for me. The patch is named sysfs-cache-the-last-sysfs_dirent-to-improve-readdir-scalability-v2.patch and is "stuck" in Greg's tree. Judging by the quilt series¹, the patch is slated for submission after 2.6.33. This late in the game for .32, I'm guessing maybe a stable backport after .33 is out? [1] http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/patches/series -- Regards/Gruss, Boris. ^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: [Bug #14949] drm_vm.c:drm_mmap: possible circular locking dependency detected 2010-02-02 20:58 ` Borislav Petkov @ 2010-02-02 21:12 ` Rafael J. Wysocki 2010-02-03 2:18 ` Greg KH 1 sibling, 0 replies; 76+ messages in thread From: Rafael J. Wysocki @ 2010-02-02 21:12 UTC (permalink / raw) To: Borislav Petkov Cc: Linux Kernel Mailing List, Kernel Testers List, DRI, Eric W. Biederman, Greg KH On Tuesday 02 February 2010, Borislav Petkov wrote: > (Adding Greg to Cc:) > > On Tue, Feb 02, 2010 at 09:46:45PM +0100, Rafael J. Wysocki wrote: > > On Monday 01 February 2010, Borislav Petkov wrote: > > > On Mon, Feb 1, 2010 at 1:22 AM, Rafael J. Wysocki <rjw@sisk.pl> wrote: > > > > This message has been generated automatically as a part of a report > > > > of recent regressions. > > > > > > > > The following bug entry is on the current list of known regressions > > > > from 2.6.32. Please verify if it still should be listed and let me know > > > > (either way). > > > > > > > > > > > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14949 > > > > Subject : drm_vm.c:drm_mmap: possible circular locking dependency detected > > > > Submitter : Borislav Petkov <petkovbb@googlemail.com> > > > > Date : 2009-12-26 9:45 (37 days old) > > > > References : http://marc.info/?l=linux-kernel&m=126182073616279&w=4 > > > > Handled-By : Eric W. Biederman <ebiederm@aristanetworks.com> > > > > Patch : http://patchwork.kernel.org/patch/70461/ > > > > > > Yes, this is fixed. > > > > Do you mean "fixed" as "the fix is in the Linus' tree" or "fixed" as "the > > patch fixed it for me"? > > Rather the second one, i.e. it fixes it for me. The patch is named > > sysfs-cache-the-last-sysfs_dirent-to-improve-readdir-scalability-v2.patch > > and is "stuck" in Greg's tree. Judging by the quilt series¹, the patch > is slated for submission after 2.6.33. This late in the game for .32, > I'm guessing maybe a stable backport after .33 is out? I guess so. Thanks! Rafael ^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: [Bug #14949] drm_vm.c:drm_mmap: possible circular locking dependency detected 2010-02-02 20:58 ` Borislav Petkov 2010-02-02 21:12 ` Rafael J. Wysocki @ 2010-02-03 2:18 ` Greg KH 1 sibling, 0 replies; 76+ messages in thread From: Greg KH @ 2010-02-03 2:18 UTC (permalink / raw) To: Borislav Petkov, Rafael J. Wysocki, Linux Kernel Mailing List, Kernel Testers List, DRI, Eric W. Biederman On Tue, Feb 02, 2010 at 09:58:57PM +0100, Borislav Petkov wrote: > (Adding Greg to Cc:) > > On Tue, Feb 02, 2010 at 09:46:45PM +0100, Rafael J. Wysocki wrote: > > On Monday 01 February 2010, Borislav Petkov wrote: > > > On Mon, Feb 1, 2010 at 1:22 AM, Rafael J. Wysocki <rjw@sisk.pl> wrote: > > > > This message has been generated automatically as a part of a report > > > > of recent regressions. > > > > > > > > The following bug entry is on the current list of known regressions > > > > from 2.6.32. Please verify if it still should be listed and let me know > > > > (either way). > > > > > > > > > > > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14949 > > > > Subject : drm_vm.c:drm_mmap: possible circular locking dependency detected > > > > Submitter : Borislav Petkov <petkovbb@googlemail.com> > > > > Date : 2009-12-26 9:45 (37 days old) > > > > References : http://marc.info/?l=linux-kernel&m=126182073616279&w=4 > > > > Handled-By : Eric W. Biederman <ebiederm@aristanetworks.com> > > > > Patch : http://patchwork.kernel.org/patch/70461/ > > > > > > Yes, this is fixed. > > > > Do you mean "fixed" as "the fix is in the Linus' tree" or "fixed" as "the > > patch fixed it for me"? > > Rather the second one, i.e. it fixes it for me. The patch is named > > sysfs-cache-the-last-sysfs_dirent-to-improve-readdir-scalability-v2.patch > > and is "stuck" in Greg's tree. Judging by the quilt series??, the patch > is slated for submission after 2.6.33. This late in the game for .32, > I'm guessing maybe a stable backport after .33 is out? > > [1] http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/patches/series I'll mark it for stable, I'd prefer to wait for .33 to come out before sending it in. thanks, greg k-h ^ permalink raw reply [flat|nested] 76+ messages in thread
* [Bug #15039] leds_alix2: can't allocate I/O for GPIO 2010-02-01 0:18 2.6.33-rc6: Reported regressions from 2.6.32 Rafael J. Wysocki ` (5 preceding siblings ...) 2010-02-01 0:22 ` [Bug #14949] drm_vm.c:drm_mmap: possible circular locking dependency detected Rafael J. Wysocki @ 2010-02-01 0:22 ` Rafael J. Wysocki 2010-02-01 0:22 ` [Bug #14999] possible circular locking dependency detected in rfkill at suspend Rafael J. Wysocki ` (18 subsequent siblings) 25 siblings, 0 replies; 76+ messages in thread From: Rafael J. Wysocki @ 2010-02-01 0:22 UTC (permalink / raw) To: Linux Kernel Mailing List Cc: Kernel Testers List, Arnd Hannemann, Daniel Mack This message has been generated automatically as a part of a report of recent regressions. The following bug entry is on the current list of known regressions from 2.6.32. Please verify if it still should be listed and let me know (either way). Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15039 Subject : leds_alix2: can't allocate I/O for GPIO Submitter : Arnd Hannemann <hannemann@nets.rwth-aachen.de> Date : 2010-01-07 10:26 (25 days old) References : http://marc.info/?l=linux-kernel&m=126286001106257&w=4 Handled-By : Daniel Mack <daniel@caiaq.de> Patch : http://patchwork.kernel.org/patch/72006/ ^ permalink raw reply [flat|nested] 76+ messages in thread
* [Bug #14999] possible circular locking dependency detected in rfkill at suspend 2010-02-01 0:18 2.6.33-rc6: Reported regressions from 2.6.32 Rafael J. Wysocki ` (6 preceding siblings ...) 2010-02-01 0:22 ` [Bug #15039] leds_alix2: can't allocate I/O for GPIO Rafael J. Wysocki @ 2010-02-01 0:22 ` Rafael J. Wysocki 2010-02-01 0:22 ` [Bug #15025] Oops in ext4 driver Rafael J. Wysocki ` (17 subsequent siblings) 25 siblings, 0 replies; 76+ messages in thread From: Rafael J. Wysocki @ 2010-02-01 0:22 UTC (permalink / raw) To: Linux Kernel Mailing List Cc: Kernel Testers List, Christian Casteyde, Eric W. Biederman, Linus Torvalds, Tejun Heo This message has been generated automatically as a part of a report of recent regressions. The following bug entry is on the current list of known regressions from 2.6.32. Please verify if it still should be listed and let me know (either way). Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14999 Subject : possible circular locking dependency detected in rfkill at suspend Submitter : Christian Casteyde <casteyde.christian@free.fr> Date : 2010-01-06 21:52 (26 days old) ^ permalink raw reply [flat|nested] 76+ messages in thread
* [Bug #15025] Oops in ext4 driver 2010-02-01 0:18 2.6.33-rc6: Reported regressions from 2.6.32 Rafael J. Wysocki ` (7 preceding siblings ...) 2010-02-01 0:22 ` [Bug #14999] possible circular locking dependency detected in rfkill at suspend Rafael J. Wysocki @ 2010-02-01 0:22 ` Rafael J. Wysocki 2010-02-01 0:22 ` [Bug #15076] System panic under load with clockevents_program_event Rafael J. Wysocki ` (16 subsequent siblings) 25 siblings, 0 replies; 76+ messages in thread From: Rafael J. Wysocki @ 2010-02-01 0:22 UTC (permalink / raw) To: Linux Kernel Mailing List; +Cc: Kernel Testers List, Steinar H. Gunderson This message has been generated automatically as a part of a report of recent regressions. The following bug entry is on the current list of known regressions from 2.6.32. Please verify if it still should be listed and let me know (either way). Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15025 Subject : Oops in ext4 driver Submitter : Steinar H. Gunderson <sgunderson@bigfoot.com> Date : 2010-01-10 13:09 (22 days old) ^ permalink raw reply [flat|nested] 76+ messages in thread
* [Bug #15076] System panic under load with clockevents_program_event 2010-02-01 0:18 2.6.33-rc6: Reported regressions from 2.6.32 Rafael J. Wysocki ` (8 preceding siblings ...) 2010-02-01 0:22 ` [Bug #15025] Oops in ext4 driver Rafael J. Wysocki @ 2010-02-01 0:22 ` Rafael J. Wysocki 2010-02-01 7:15 ` okias 2010-02-01 0:22 ` [Bug #15043] Display goes off with i915.powersave=1 after suspend-resume Rafael J. Wysocki ` (15 subsequent siblings) 25 siblings, 1 reply; 76+ messages in thread From: Rafael J. Wysocki @ 2010-02-01 0:22 UTC (permalink / raw) To: Linux Kernel Mailing List; +Cc: Kernel Testers List, okias This message has been generated automatically as a part of a report of recent regressions. The following bug entry is on the current list of known regressions from 2.6.32. Please verify if it still should be listed and let me know (either way). Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15076 Subject : System panic under load with clockevents_program_event Submitter : okias <d.okias@gmail.com> Date : 2010-01-17 13:03 (15 days old) ^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: [Bug #15076] System panic under load with clockevents_program_event 2010-02-01 0:22 ` [Bug #15076] System panic under load with clockevents_program_event Rafael J. Wysocki @ 2010-02-01 7:15 ` okias 2010-02-02 20:44 ` Rafael J. Wysocki 0 siblings, 1 reply; 76+ messages in thread From: okias @ 2010-02-01 7:15 UTC (permalink / raw) To: Rafael J. Wysocki; +Cc: Linux Kernel Mailing List, Kernel Testers List Still valid. But reproduction without HIGHMEM is minimal, but still annoying. 2010/2/1, Rafael J. Wysocki <rjw@sisk.pl>: > This message has been generated automatically as a part of a report > of recent regressions. > > The following bug entry is on the current list of known regressions > from 2.6.32. Please verify if it still should be listed and let me know > (either way). > > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15076 > Subject : System panic under load with clockevents_program_event > Submitter : okias <d.okias@gmail.com> > Date : 2010-01-17 13:03 (15 days old) > > > -- Jabber/XMPP: okias@isgeek.info SIP VoIP: sip:17474537254@proxy01.sipphone.com ^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: [Bug #15076] System panic under load with clockevents_program_event 2010-02-01 7:15 ` okias @ 2010-02-02 20:44 ` Rafael J. Wysocki 0 siblings, 0 replies; 76+ messages in thread From: Rafael J. Wysocki @ 2010-02-02 20:44 UTC (permalink / raw) To: okias; +Cc: Linux Kernel Mailing List, Kernel Testers List On Monday 01 February 2010, okias wrote: > Still valid. But reproduction without HIGHMEM is minimal, but still annoying. Thanks for the update. Rafael ^ permalink raw reply [flat|nested] 76+ messages in thread
* [Bug #15043] Display goes off with i915.powersave=1 after suspend-resume 2010-02-01 0:18 2.6.33-rc6: Reported regressions from 2.6.32 Rafael J. Wysocki ` (9 preceding siblings ...) 2010-02-01 0:22 ` [Bug #15076] System panic under load with clockevents_program_event Rafael J. Wysocki @ 2010-02-01 0:22 ` Rafael J. Wysocki 2010-02-04 20:08 ` Soeren Sonnenburg 2010-02-01 0:22 ` [Bug #15114] X.org hang with [drm:i915_gem_do_execbuffer] *ERROR* in dmesg Rafael J. Wysocki ` (14 subsequent siblings) 25 siblings, 1 reply; 76+ messages in thread From: Rafael J. Wysocki @ 2010-02-01 0:22 UTC (permalink / raw) To: Linux Kernel Mailing List; +Cc: Kernel Testers List, Soeren Sonnenburg This message has been generated automatically as a part of a report of recent regressions. The following bug entry is on the current list of known regressions from 2.6.32. Please verify if it still should be listed and let me know (either way). Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15043 Subject : Display goes off with i915.powersave=1 after suspend-resume Submitter : Soeren Sonnenburg <sonne@debian.org> Date : 2010-01-10 20:09 (22 days old) References : http://marc.info/?l=linux-kernel&m=126315457519505&w=4 ^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: [Bug #15043] Display goes off with i915.powersave=1 after suspend-resume 2010-02-01 0:22 ` [Bug #15043] Display goes off with i915.powersave=1 after suspend-resume Rafael J. Wysocki @ 2010-02-04 20:08 ` Soeren Sonnenburg 2010-02-04 20:42 ` Rafael J. Wysocki 0 siblings, 1 reply; 76+ messages in thread From: Soeren Sonnenburg @ 2010-02-04 20:08 UTC (permalink / raw) To: Rafael J. Wysocki; +Cc: Linux Kernel Mailing List, Kernel Testers List [-- Attachment #1: Type: text/plain, Size: 815 bytes --] On Mon, 2010-02-01 at 01:22 +0100, Rafael J. Wysocki wrote: > This message has been generated automatically as a part of a report > of recent regressions. > > The following bug entry is on the current list of known regressions > from 2.6.32. Please verify if it still should be listed and let me know > (either way). > > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15043 > Subject : Display goes off with i915.powersave=1 after suspend-resume > Submitter : Soeren Sonnenburg <sonne@debian.org> > Date : 2010-01-10 20:09 (22 days old) > References : http://marc.info/?l=linux-kernel&m=126315457519505&w=4 yes still exists in current git. Soeren -- For the one fact about the future of which we can be certain is that it will be utterly fantastic. -- Arthur C. Clarke, 1962 [-- Attachment #2: This is a digitally signed message part --] [-- Type: application/pgp-signature, Size: 836 bytes --] ^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: [Bug #15043] Display goes off with i915.powersave=1 after suspend-resume 2010-02-04 20:08 ` Soeren Sonnenburg @ 2010-02-04 20:42 ` Rafael J. Wysocki 2010-02-05 19:29 ` Jesse Barnes 0 siblings, 1 reply; 76+ messages in thread From: Rafael J. Wysocki @ 2010-02-04 20:42 UTC (permalink / raw) To: Soeren Sonnenburg Cc: Linux Kernel Mailing List, Kernel Testers List, dri-devel On Thursday 04 February 2010, Soeren Sonnenburg wrote: > On Mon, 2010-02-01 at 01:22 +0100, Rafael J. Wysocki wrote: > > This message has been generated automatically as a part of a report > > of recent regressions. > > > > The following bug entry is on the current list of known regressions > > from 2.6.32. Please verify if it still should be listed and let me know > > (either way). > > > > > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15043 > > Subject : Display goes off with i915.powersave=1 after suspend-resume > > Submitter : Soeren Sonnenburg <sonne@debian.org> > > Date : 2010-01-10 20:09 (22 days old) > > References : http://marc.info/?l=linux-kernel&m=126315457519505&w=4 > > yes still exists in current git. Thanks for the update. Rafael ^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: [Bug #15043] Display goes off with i915.powersave=1 after suspend-resume 2010-02-04 20:42 ` Rafael J. Wysocki @ 2010-02-05 19:29 ` Jesse Barnes 2010-02-06 5:11 ` Soeren Sonnenburg 0 siblings, 1 reply; 76+ messages in thread From: Jesse Barnes @ 2010-02-05 19:29 UTC (permalink / raw) To: Rafael J. Wysocki Cc: Soeren Sonnenburg, Linux Kernel Mailing List, Kernel Testers List, dri-devel On Thu, 4 Feb 2010 21:42:02 +0100 "Rafael J. Wysocki" <rjw@sisk.pl> wrote: > On Thursday 04 February 2010, Soeren Sonnenburg wrote: > > On Mon, 2010-02-01 at 01:22 +0100, Rafael J. Wysocki wrote: > > > This message has been generated automatically as a part of a > > > report of recent regressions. > > > > > > The following bug entry is on the current list of known > > > regressions from 2.6.32. Please verify if it still should be > > > listed and let me know (either way). > > > > > > > > > Bug-Entry : > > > http://bugzilla.kernel.org/show_bug.cgi?id=15043 > > > Subject : Display goes off with i915.powersave=1 > > > after suspend-resume Submitter : Soeren Sonnenburg > > > <sonne@debian.org> Date : 2010-01-10 20:09 (22 > > > days old) References : > > > http://marc.info/?l=linux-kernel&m=126315457519505&w=4 > > > > yes still exists in current git. > > Thanks for the update. Just updated the corresponding FDO bug (https://bugs.freedesktop.org/show_bug.cgi?id=24314). There are some hw bugs related to FBC handling on 945GM though, so we may have to disable it on some machines. -- Jesse Barnes, Intel Open Source Technology Center ^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: [Bug #15043] Display goes off with i915.powersave=1 after suspend-resume 2010-02-05 19:29 ` Jesse Barnes @ 2010-02-06 5:11 ` Soeren Sonnenburg 2010-02-06 5:53 ` Soeren Sonnenburg 0 siblings, 1 reply; 76+ messages in thread From: Soeren Sonnenburg @ 2010-02-06 5:11 UTC (permalink / raw) To: Jesse Barnes Cc: Rafael J. Wysocki, Linux Kernel Mailing List, Kernel Testers List, dri-devel [-- Attachment #1: Type: text/plain, Size: 1476 bytes --] On Fri, 2010-02-05 at 11:29 -0800, Jesse Barnes wrote: > On Thu, 4 Feb 2010 21:42:02 +0100 > "Rafael J. Wysocki" <rjw@sisk.pl> wrote: > > > On Thursday 04 February 2010, Soeren Sonnenburg wrote: > > > On Mon, 2010-02-01 at 01:22 +0100, Rafael J. Wysocki wrote: > > > > This message has been generated automatically as a part of a > > > > report of recent regressions. > > > > > > > > The following bug entry is on the current list of known > > > > regressions from 2.6.32. Please verify if it still should be > > > > listed and let me know (either way). > > > > > > > > > > > > Bug-Entry : > > > > http://bugzilla.kernel.org/show_bug.cgi?id=15043 > > > > Subject : Display goes off with i915.powersave=1 > > > > after suspend-resume Submitter : Soeren Sonnenburg > > > > <sonne@debian.org> Date : 2010-01-10 20:09 (22 > > > > days old) References : > > > > http://marc.info/?l=linux-kernel&m=126315457519505&w=4 > > > > > > yes still exists in current git. > > > > Thanks for the update. > > Just updated the corresponding FDO bug > (https://bugs.freedesktop.org/show_bug.cgi?id=24314). There are some > hw bugs related to FBC handling on 945GM though, so we may have to > disable it on some machines. FYI: With the patch from #14897 it was working for the last day and a half at least... Soeren -- For the one fact about the future of which we can be certain is that it will be utterly fantastic. -- Arthur C. Clarke, 1962 [-- Attachment #2: This is a digitally signed message part --] [-- Type: application/pgp-signature, Size: 836 bytes --] ^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: [Bug #15043] Display goes off with i915.powersave=1 after suspend-resume 2010-02-06 5:11 ` Soeren Sonnenburg @ 2010-02-06 5:53 ` Soeren Sonnenburg 0 siblings, 0 replies; 76+ messages in thread From: Soeren Sonnenburg @ 2010-02-06 5:53 UTC (permalink / raw) To: Jesse Barnes Cc: Rafael J. Wysocki, Linux Kernel Mailing List, Kernel Testers List, dri-devel [-- Attachment #1: Type: text/plain, Size: 1743 bytes --] On Sat, 2010-02-06 at 06:11 +0100, Soeren Sonnenburg wrote: > On Fri, 2010-02-05 at 11:29 -0800, Jesse Barnes wrote: > > On Thu, 4 Feb 2010 21:42:02 +0100 > > "Rafael J. Wysocki" <rjw@sisk.pl> wrote: > > > > > On Thursday 04 February 2010, Soeren Sonnenburg wrote: > > > > On Mon, 2010-02-01 at 01:22 +0100, Rafael J. Wysocki wrote: > > > > > This message has been generated automatically as a part of a > > > > > report of recent regressions. > > > > > > > > > > The following bug entry is on the current list of known > > > > > regressions from 2.6.32. Please verify if it still should be > > > > > listed and let me know (either way). > > > > > > > > > > > > > > > Bug-Entry : > > > > > http://bugzilla.kernel.org/show_bug.cgi?id=15043 > > > > > Subject : Display goes off with i915.powersave=1 > > > > > after suspend-resume Submitter : Soeren Sonnenburg > > > > > <sonne@debian.org> Date : 2010-01-10 20:09 (22 > > > > > days old) References : > > > > > http://marc.info/?l=linux-kernel&m=126315457519505&w=4 > > > > > > > > yes still exists in current git. > > > > > > Thanks for the update. > > > > Just updated the corresponding FDO bug > > (https://bugs.freedesktop.org/show_bug.cgi?id=24314). There are some > > hw bugs related to FBC handling on 945GM though, so we may have to > > disable it on some machines. > > FYI: With the patch from #14897 it was working for the last day and a > half at least... Just after I wrote that email it was happening again. So I take that back. Flickering and display -> off just happened with that patch. Soeren -- For the one fact about the future of which we can be certain is that it will be utterly fantastic. -- Arthur C. Clarke, 1962 [-- Attachment #2: This is a digitally signed message part --] [-- Type: application/pgp-signature, Size: 836 bytes --] ^ permalink raw reply [flat|nested] 76+ messages in thread
* [Bug #15114] X.org hang with [drm:i915_gem_do_execbuffer] *ERROR* in dmesg 2010-02-01 0:18 2.6.33-rc6: Reported regressions from 2.6.32 Rafael J. Wysocki ` (10 preceding siblings ...) 2010-02-01 0:22 ` [Bug #15043] Display goes off with i915.powersave=1 after suspend-resume Rafael J. Wysocki @ 2010-02-01 0:22 ` Rafael J. Wysocki 2010-02-01 0:22 ` [Bug #15119] iwl_bg_scan_completed: WARN on scan complete Rafael J. Wysocki ` (13 subsequent siblings) 25 siblings, 0 replies; 76+ messages in thread From: Rafael J. Wysocki @ 2010-02-01 0:22 UTC (permalink / raw) To: Linux Kernel Mailing List; +Cc: Kernel Testers List, Matej Laitl This message has been generated automatically as a part of a report of recent regressions. The following bug entry is on the current list of known regressions from 2.6.32. Please verify if it still should be listed and let me know (either way). Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15114 Subject : X.org hang with [drm:i915_gem_do_execbuffer] *ERROR* in dmesg Submitter : Matej Laitl <strohel@gmail.com> Date : 2010-01-23 19:54 (9 days old) ^ permalink raw reply [flat|nested] 76+ messages in thread
* [Bug #15119] iwl_bg_scan_completed: WARN on scan complete 2010-02-01 0:18 2.6.33-rc6: Reported regressions from 2.6.32 Rafael J. Wysocki ` (11 preceding siblings ...) 2010-02-01 0:22 ` [Bug #15114] X.org hang with [drm:i915_gem_do_execbuffer] *ERROR* in dmesg Rafael J. Wysocki @ 2010-02-01 0:22 ` Rafael J. Wysocki 2010-02-01 0:22 ` [Bug #15124] PCI host bridge windows ignored (works with pci=use_crs) Rafael J. Wysocki ` (12 subsequent siblings) 25 siblings, 0 replies; 76+ messages in thread From: Rafael J. Wysocki @ 2010-02-01 0:22 UTC (permalink / raw) To: Linux Kernel Mailing List; +Cc: Kernel Testers List, Alex Zhavnerchik This message has been generated automatically as a part of a report of recent regressions. The following bug entry is on the current list of known regressions from 2.6.32. Please verify if it still should be listed and let me know (either way). Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15119 Subject : iwl_bg_scan_completed: WARN on scan complete Submitter : Alex Zhavnerchik <alex.vizor@gmail.com> Date : 2010-01-24 12:27 (8 days old) ^ permalink raw reply [flat|nested] 76+ messages in thread
* [Bug #15124] PCI host bridge windows ignored (works with pci=use_crs) 2010-02-01 0:18 2.6.33-rc6: Reported regressions from 2.6.32 Rafael J. Wysocki ` (12 preceding siblings ...) 2010-02-01 0:22 ` [Bug #15119] iwl_bg_scan_completed: WARN on scan complete Rafael J. Wysocki @ 2010-02-01 0:22 ` Rafael J. Wysocki 2010-02-01 5:40 ` Yinghai Lu 2010-02-01 0:22 ` [Bug #15139] e1000: transmit queue 0 timed out Rafael J. Wysocki ` (11 subsequent siblings) 25 siblings, 1 reply; 76+ messages in thread From: Rafael J. Wysocki @ 2010-02-01 0:22 UTC (permalink / raw) To: Linux Kernel Mailing List Cc: Kernel Testers List, Bjorn Helgaas, Jeff Garrett, Linux PCI, Yinghai Lu This message has been generated automatically as a part of a report of recent regressions. The following bug entry is on the current list of known regressions from 2.6.32. Please verify if it still should be listed and let me know (either way). Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15124 Subject : PCI host bridge windows ignored (works with pci=use_crs) Submitter : Jeff Garrett <jeff@jgarrett.org> Date : 2010-01-13 5:37 (19 days old) References : http://marc.info/?l=linux-kernel&m=126336296600307&w=4 Handled-By : Yinghai Lu <yinghai@kernel.org> Bjorn Helgaas <bjorn.helgaas@hp.com> ^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: [Bug #15124] PCI host bridge windows ignored (works with pci=use_crs) 2010-02-01 0:22 ` [Bug #15124] PCI host bridge windows ignored (works with pci=use_crs) Rafael J. Wysocki @ 2010-02-01 5:40 ` Yinghai Lu 2010-02-02 20:42 ` Rafael J. Wysocki 0 siblings, 1 reply; 76+ messages in thread From: Yinghai Lu @ 2010-02-01 5:40 UTC (permalink / raw) To: Rafael J. Wysocki Cc: Linux Kernel Mailing List, Kernel Testers List, Bjorn Helgaas, Jeff Garrett, Linux PCI On 01/31/2010 04:22 PM, Rafael J. Wysocki wrote: > This message has been generated automatically as a part of a report > of recent regressions. > > The following bug entry is on the current list of known regressions > from 2.6.32. Please verify if it still should be listed and let me know > (either way). > > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15124 > Subject : PCI host bridge windows ignored (works with pci=use_crs) > Submitter : Jeff Garrett <jeff@jgarrett.org> > Date : 2010-01-13 5:37 (19 days old) > References : http://marc.info/?l=linux-kernel&m=126336296600307&w=4 > Handled-By : Yinghai Lu <yinghai@kernel.org> > Bjorn Helgaas <bjorn.helgaas@hp.com> > should be closed. YH ^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: [Bug #15124] PCI host bridge windows ignored (works with pci=use_crs) 2010-02-01 5:40 ` Yinghai Lu @ 2010-02-02 20:42 ` Rafael J. Wysocki 2010-02-02 20:50 ` Jeff Garrett 2010-02-02 20:55 ` Bjorn Helgaas 0 siblings, 2 replies; 76+ messages in thread From: Rafael J. Wysocki @ 2010-02-02 20:42 UTC (permalink / raw) To: Yinghai Lu Cc: Linux Kernel Mailing List, Kernel Testers List, Bjorn Helgaas, Jeff Garrett, Linux PCI On Monday 01 February 2010, Yinghai Lu wrote: > On 01/31/2010 04:22 PM, Rafael J. Wysocki wrote: > > This message has been generated automatically as a part of a report > > of recent regressions. > > > > The following bug entry is on the current list of known regressions > > from 2.6.32. Please verify if it still should be listed and let me know > > (either way). > > > > > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15124 > > Subject : PCI host bridge windows ignored (works with pci=use_crs) > > Submitter : Jeff Garrett <jeff@jgarrett.org> > > Date : 2010-01-13 5:37 (19 days old) > > References : http://marc.info/?l=linux-kernel&m=126336296600307&w=4 > > Handled-By : Yinghai Lu <yinghai@kernel.org> > > Bjorn Helgaas <bjorn.helgaas@hp.com> > > > > should be closed. Is there a fix in the Linus' tree? Rafael ^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: [Bug #15124] PCI host bridge windows ignored (works with pci=use_crs) 2010-02-02 20:42 ` Rafael J. Wysocki @ 2010-02-02 20:50 ` Jeff Garrett 2010-02-02 21:13 ` Rafael J. Wysocki 2010-02-02 20:55 ` Bjorn Helgaas 1 sibling, 1 reply; 76+ messages in thread From: Jeff Garrett @ 2010-02-02 20:50 UTC (permalink / raw) To: Rafael J. Wysocki Cc: Yinghai Lu, Linux Kernel Mailing List, Kernel Testers List, Bjorn Helgaas, Linux PCI On Tue, Feb 02, 2010 at 09:42:58PM +0100, Rafael J. Wysocki wrote: > On Monday 01 February 2010, Yinghai Lu wrote: > > On 01/31/2010 04:22 PM, Rafael J. Wysocki wrote: > > > This message has been generated automatically as a part of a report > > > of recent regressions. > > > > > > The following bug entry is on the current list of known regressions > > > from 2.6.32. Please verify if it still should be listed and let me know > > > (either way). > > > > > > > > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15124 > > > Subject : PCI host bridge windows ignored (works with pci=use_crs) > > > Submitter : Jeff Garrett <jeff@jgarrett.org> > > > Date : 2010-01-13 5:37 (19 days old) > > > References : http://marc.info/?l=linux-kernel&m=126336296600307&w=4 > > > Handled-By : Yinghai Lu <yinghai@kernel.org> > > > Bjorn Helgaas <bjorn.helgaas@hp.com> > > > > > > > should be closed. > > Is there a fix in the Linus' tree? > > Rafael Yes, it is fixed by commit e8e06eae4ffd683931b928f460c11c40cd3f7fd8 -Jeff ^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: [Bug #15124] PCI host bridge windows ignored (works with pci=use_crs) 2010-02-02 20:50 ` Jeff Garrett @ 2010-02-02 21:13 ` Rafael J. Wysocki 0 siblings, 0 replies; 76+ messages in thread From: Rafael J. Wysocki @ 2010-02-02 21:13 UTC (permalink / raw) To: Jeff Garrett Cc: Yinghai Lu, Linux Kernel Mailing List, Kernel Testers List, Bjorn Helgaas, Linux PCI On Tuesday 02 February 2010, Jeff Garrett wrote: > On Tue, Feb 02, 2010 at 09:42:58PM +0100, Rafael J. Wysocki wrote: > > On Monday 01 February 2010, Yinghai Lu wrote: > > > On 01/31/2010 04:22 PM, Rafael J. Wysocki wrote: > > > > This message has been generated automatically as a part of a report > > > > of recent regressions. > > > > > > > > The following bug entry is on the current list of known regressions > > > > from 2.6.32. Please verify if it still should be listed and let me know > > > > (either way). > > > > > > > > > > > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15124 > > > > Subject : PCI host bridge windows ignored (works with pci=use_crs) > > > > Submitter : Jeff Garrett <jeff@jgarrett.org> > > > > Date : 2010-01-13 5:37 (19 days old) > > > > References : http://marc.info/?l=linux-kernel&m=126336296600307&w=4 > > > > Handled-By : Yinghai Lu <yinghai@kernel.org> > > > > Bjorn Helgaas <bjorn.helgaas@hp.com> > > > > > > > > > > should be closed. > > > > Is there a fix in the Linus' tree? > > > > Rafael > > Yes, it is fixed by commit e8e06eae4ffd683931b928f460c11c40cd3f7fd8 Thanks, closing. Rafael ^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: [Bug #15124] PCI host bridge windows ignored (works with pci=use_crs) 2010-02-02 20:42 ` Rafael J. Wysocki 2010-02-02 20:50 ` Jeff Garrett @ 2010-02-02 20:55 ` Bjorn Helgaas 2010-02-02 21:15 ` Rafael J. Wysocki 1 sibling, 1 reply; 76+ messages in thread From: Bjorn Helgaas @ 2010-02-02 20:55 UTC (permalink / raw) To: Rafael J. Wysocki Cc: Yinghai Lu, Linux Kernel Mailing List, Kernel Testers List, Jeff Garrett, Linux PCI On Tuesday 02 February 2010 01:42:58 pm Rafael J. Wysocki wrote: > On Monday 01 February 2010, Yinghai Lu wrote: > > On 01/31/2010 04:22 PM, Rafael J. Wysocki wrote: > > > This message has been generated automatically as a part of a report > > > of recent regressions. > > > > > > The following bug entry is on the current list of known regressions > > > from 2.6.32. Please verify if it still should be listed and let me know > > > (either way). > > > > > > > > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15124 > > > Subject : PCI host bridge windows ignored (works with pci=use_crs) > > > Submitter : Jeff Garrett <jeff@jgarrett.org> > > > Date : 2010-01-13 5:37 (19 days old) > > > References : http://marc.info/?l=linux-kernel&m=126336296600307&w=4 > > > Handled-By : Yinghai Lu <yinghai@kernel.org> > > > Bjorn Helgaas <bjorn.helgaas@hp.com> > > > > > > > should be closed. > > Is there a fix in the Linus' tree? Yes. The regression was caused by the addition of arch/x86/pci/intel_bus.c. Jeff's patch: http://lkml.org/lkml/2010/1/27/449 is in Linus' tree as commit e8e06eae4ffd68, and Jeff confirmed that it works for him. Bjorn ^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: [Bug #15124] PCI host bridge windows ignored (works with pci=use_crs) 2010-02-02 20:55 ` Bjorn Helgaas @ 2010-02-02 21:15 ` Rafael J. Wysocki 0 siblings, 0 replies; 76+ messages in thread From: Rafael J. Wysocki @ 2010-02-02 21:15 UTC (permalink / raw) To: Bjorn Helgaas Cc: Yinghai Lu, Linux Kernel Mailing List, Kernel Testers List, Jeff Garrett, Linux PCI On Tuesday 02 February 2010, Bjorn Helgaas wrote: > On Tuesday 02 February 2010 01:42:58 pm Rafael J. Wysocki wrote: > > On Monday 01 February 2010, Yinghai Lu wrote: > > > On 01/31/2010 04:22 PM, Rafael J. Wysocki wrote: > > > > This message has been generated automatically as a part of a report > > > > of recent regressions. > > > > > > > > The following bug entry is on the current list of known regressions > > > > from 2.6.32. Please verify if it still should be listed and let me know > > > > (either way). > > > > > > > > > > > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15124 > > > > Subject : PCI host bridge windows ignored (works with pci=use_crs) > > > > Submitter : Jeff Garrett <jeff@jgarrett.org> > > > > Date : 2010-01-13 5:37 (19 days old) > > > > References : http://marc.info/?l=linux-kernel&m=126336296600307&w=4 > > > > Handled-By : Yinghai Lu <yinghai@kernel.org> > > > > Bjorn Helgaas <bjorn.helgaas@hp.com> > > > > > > > > > > should be closed. > > > > Is there a fix in the Linus' tree? > > Yes. The regression was caused by the addition of arch/x86/pci/intel_bus.c. > > Jeff's patch: http://lkml.org/lkml/2010/1/27/449 is in Linus' tree as > commit e8e06eae4ffd68, and Jeff confirmed that it works for him. Thanks, closed. Rafael ^ permalink raw reply [flat|nested] 76+ messages in thread
* [Bug #15139] e1000: transmit queue 0 timed out 2010-02-01 0:18 2.6.33-rc6: Reported regressions from 2.6.32 Rafael J. Wysocki ` (13 preceding siblings ...) 2010-02-01 0:22 ` [Bug #15124] PCI host bridge windows ignored (works with pci=use_crs) Rafael J. Wysocki @ 2010-02-01 0:22 ` Rafael J. Wysocki 2010-02-01 0:22 ` [Bug #15125] hung task - jbd2/dm-1-8 (during raid rebuild) Rafael J. Wysocki ` (10 subsequent siblings) 25 siblings, 0 replies; 76+ messages in thread From: Rafael J. Wysocki @ 2010-02-01 0:22 UTC (permalink / raw) To: Linux Kernel Mailing List; +Cc: Kernel Testers List, Alexander Beregalov This message has been generated automatically as a part of a report of recent regressions. The following bug entry is on the current list of known regressions from 2.6.32. Please verify if it still should be listed and let me know (either way). Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15139 Subject : e1000: transmit queue 0 timed out Submitter : Alexander Beregalov <a.beregalov@gmail.com> Date : 2010-01-23 15:37 (9 days old) References : http://marc.info/?l=linux-netdev&m=126426149306083&w=4 ^ permalink raw reply [flat|nested] 76+ messages in thread
* [Bug #15125] hung task - jbd2/dm-1-8 (during raid rebuild) 2010-02-01 0:18 2.6.33-rc6: Reported regressions from 2.6.32 Rafael J. Wysocki ` (14 preceding siblings ...) 2010-02-01 0:22 ` [Bug #15139] e1000: transmit queue 0 timed out Rafael J. Wysocki @ 2010-02-01 0:22 ` Rafael J. Wysocki 2010-02-01 0:42 ` Michael Breuer 2010-02-01 0:22 ` [Bug #15138] evdev regression on macbook Rafael J. Wysocki ` (9 subsequent siblings) 25 siblings, 1 reply; 76+ messages in thread From: Rafael J. Wysocki @ 2010-02-01 0:22 UTC (permalink / raw) To: Linux Kernel Mailing List; +Cc: Kernel Testers List, Michael Breuer This message has been generated automatically as a part of a report of recent regressions. The following bug entry is on the current list of known regressions from 2.6.32. Please verify if it still should be listed and let me know (either way). Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15125 Subject : hung task - jbd2/dm-1-8 (during raid rebuild) Submitter : Michael Breuer <mbreuer@majjas.com> Date : 2010-01-10 21:47 (22 days old) References : http://marc.info/?l=linux-kernel&m=126316012025978&w=4 ^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: [Bug #15125] hung task - jbd2/dm-1-8 (during raid rebuild) 2010-02-01 0:22 ` [Bug #15125] hung task - jbd2/dm-1-8 (during raid rebuild) Rafael J. Wysocki @ 2010-02-01 0:42 ` Michael Breuer 2010-02-01 17:39 ` Michael Breuer 0 siblings, 1 reply; 76+ messages in thread From: Michael Breuer @ 2010-02-01 0:42 UTC (permalink / raw) To: Rafael J. Wysocki; +Cc: Linux Kernel Mailing List, Kernel Testers List On 1/31/2010 7:22 PM, Rafael J. Wysocki wrote: > This message has been generated automatically as a part of a report > of recent regressions. > > The following bug entry is on the current list of known regressions > from 2.6.32. Please verify if it still should be listed and let me know > (either way). > > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15125 > Subject : hung task - jbd2/dm-1-8 (during raid rebuild) > Submitter : Michael Breuer<mbreuer@majjas.com> > Date : 2010-01-10 21:47 (22 days old) > References : http://marc.info/?l=linux-kernel&m=126316012025978&w=4 > > Yup. Hit it again on 2.6.33-rc5. ^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: [Bug #15125] hung task - jbd2/dm-1-8 (during raid rebuild) 2010-02-01 0:42 ` Michael Breuer @ 2010-02-01 17:39 ` Michael Breuer 2010-02-02 20:42 ` Rafael J. Wysocki 0 siblings, 1 reply; 76+ messages in thread From: Michael Breuer @ 2010-02-01 17:39 UTC (permalink / raw) To: Rafael J. Wysocki; +Cc: Linux Kernel Mailing List, Kernel Testers List On 1/31/2010 7:42 PM, Michael Breuer wrote: > On 1/31/2010 7:22 PM, Rafael J. Wysocki wrote: >> This message has been generated automatically as a part of a report >> of recent regressions. >> >> The following bug entry is on the current list of known regressions >> from 2.6.32. Please verify if it still should be listed and let me know >> (either way). >> >> >> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15125 >> Subject : hung task - jbd2/dm-1-8 (during raid rebuild) >> Submitter : Michael Breuer<mbreuer@majjas.com> >> Date : 2010-01-10 21:47 (22 days old) >> References : http://marc.info/?l=linux-kernel&m=126316012025978&w=4 >> > Yup. Hit it again on 2.6.33-rc5. > -- > To unsubscribe from this list: send the line "unsubscribe > linux-kernel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ I was not able to recreate this in rc6. ^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: [Bug #15125] hung task - jbd2/dm-1-8 (during raid rebuild) 2010-02-01 17:39 ` Michael Breuer @ 2010-02-02 20:42 ` Rafael J. Wysocki 0 siblings, 0 replies; 76+ messages in thread From: Rafael J. Wysocki @ 2010-02-02 20:42 UTC (permalink / raw) To: Michael Breuer; +Cc: Linux Kernel Mailing List, Kernel Testers List On Monday 01 February 2010, Michael Breuer wrote: > On 1/31/2010 7:42 PM, Michael Breuer wrote: > > On 1/31/2010 7:22 PM, Rafael J. Wysocki wrote: > >> This message has been generated automatically as a part of a report > >> of recent regressions. > >> > >> The following bug entry is on the current list of known regressions > >> from 2.6.32. Please verify if it still should be listed and let me know > >> (either way). > >> > >> > >> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15125 > >> Subject : hung task - jbd2/dm-1-8 (during raid rebuild) > >> Submitter : Michael Breuer<mbreuer@majjas.com> > >> Date : 2010-01-10 21:47 (22 days old) > >> References : http://marc.info/?l=linux-kernel&m=126316012025978&w=4 > >> > > Yup. Hit it again on 2.6.33-rc5. > I was not able to recreate this in rc6. Thanks, closed then. Rafael ^ permalink raw reply [flat|nested] 76+ messages in thread
* [Bug #15138] evdev regression on macbook 2010-02-01 0:18 2.6.33-rc6: Reported regressions from 2.6.32 Rafael J. Wysocki ` (15 preceding siblings ...) 2010-02-01 0:22 ` [Bug #15125] hung task - jbd2/dm-1-8 (during raid rebuild) Rafael J. Wysocki @ 2010-02-01 0:22 ` Rafael J. Wysocki 2010-02-01 0:22 ` [Bug #15142] "INFO: possible circular locking dependency detected" Rafael J. Wysocki ` (8 subsequent siblings) 25 siblings, 0 replies; 76+ messages in thread From: Rafael J. Wysocki @ 2010-02-01 0:22 UTC (permalink / raw) To: Linux Kernel Mailing List Cc: Kernel Testers List, Dmitry Torokhov, Guillaume Chazarain This message has been generated automatically as a part of a report of recent regressions. The following bug entry is on the current list of known regressions from 2.6.32. Please verify if it still should be listed and let me know (either way). Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15138 Subject : evdev regression on macbook Submitter : Guillaume Chazarain <guichaz@gmail.com> Date : 2010-01-23 18:53 (9 days old) References : http://marc.info/?l=linux-kernel&m=126427286219235&w=4 Handled-By : Dmitry Torokhov <dmitry.torokhov@gmail.com> ^ permalink raw reply [flat|nested] 76+ messages in thread
* [Bug #15142] "INFO: possible circular locking dependency detected" 2010-02-01 0:18 2.6.33-rc6: Reported regressions from 2.6.32 Rafael J. Wysocki ` (16 preceding siblings ...) 2010-02-01 0:22 ` [Bug #15138] evdev regression on macbook Rafael J. Wysocki @ 2010-02-01 0:22 ` Rafael J. Wysocki 2010-02-01 0:22 ` [Bug #15144] HDA Intel Audio hang on boot Rafael J. Wysocki ` (7 subsequent siblings) 25 siblings, 0 replies; 76+ messages in thread From: Rafael J. Wysocki @ 2010-02-01 0:22 UTC (permalink / raw) To: Linux Kernel Mailing List; +Cc: Kernel Testers List, Matti Aarnio This message has been generated automatically as a part of a report of recent regressions. The following bug entry is on the current list of known regressions from 2.6.32. Please verify if it still should be listed and let me know (either way). Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15142 Subject : "INFO: possible circular locking dependency detected" Submitter : Matti Aarnio <matti.aarnio--kernel-bugzilla@zmailer.org> Date : 2010-01-25 13:38 (7 days old) ^ permalink raw reply [flat|nested] 76+ messages in thread
* [Bug #15144] HDA Intel Audio hang on boot 2010-02-01 0:18 2.6.33-rc6: Reported regressions from 2.6.32 Rafael J. Wysocki ` (17 preceding siblings ...) 2010-02-01 0:22 ` [Bug #15142] "INFO: possible circular locking dependency detected" Rafael J. Wysocki @ 2010-02-01 0:22 ` Rafael J. Wysocki 2010-02-01 2:01 ` Sid Boyce 2010-02-01 0:22 ` [Bug #15192] netperf ~50% regression with 2.6.33-rc1, bisect to 1b9508f Rafael J. Wysocki ` (6 subsequent siblings) 25 siblings, 1 reply; 76+ messages in thread From: Rafael J. Wysocki @ 2010-02-01 0:22 UTC (permalink / raw) To: Linux Kernel Mailing List; +Cc: Kernel Testers List, Sid Boyce, Takashi Iwai This message has been generated automatically as a part of a report of recent regressions. The following bug entry is on the current list of known regressions from 2.6.32. Please verify if it still should be listed and let me know (either way). Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15144 Subject : HDA Intel Audio hang on boot Submitter : Sid Boyce <sboyce@blueyonder.co.uk> Date : 2010-01-15 1:24 (17 days old) References : http://marc.info/?l=linux-kernel&m=126351866722507&w=4 ^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: [Bug #15144] HDA Intel Audio hang on boot 2010-02-01 0:22 ` [Bug #15144] HDA Intel Audio hang on boot Rafael J. Wysocki @ 2010-02-01 2:01 ` Sid Boyce 2010-02-01 6:43 ` Takashi Iwai 0 siblings, 1 reply; 76+ messages in thread From: Sid Boyce @ 2010-02-01 2:01 UTC (permalink / raw) To: Rafael J. Wysocki Cc: Linux Kernel Mailing List, Kernel Testers List, Takashi Iwai On 01/02/10 00:22, Rafael J. Wysocki wrote: > This message has been generated automatically as a part of a report > of recent regressions. > > The following bug entry is on the current list of known regressions > from 2.6.32. Please verify if it still should be listed and let me know > (either way). > > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15144 > Subject : HDA Intel Audio hang on boot > Submitter : Sid Boyce <sboyce@blueyonder.co.uk> > Date : 2010-01-15 1:24 (17 days old) > References : http://marc.info/?l=linux-kernel&m=126351866722507&w=4 > > > Still not fixed in 2.6.33-rc6. Takashi wrote that the fix was scheduled for 2.6.33-rc6, but it did not appear. I have gone back to using the workaround with 2.6.33-rc6. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks ^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: [Bug #15144] HDA Intel Audio hang on boot 2010-02-01 2:01 ` Sid Boyce @ 2010-02-01 6:43 ` Takashi Iwai 2010-02-02 20:40 ` Rafael J. Wysocki 2010-02-14 20:29 ` Sid Boyce 0 siblings, 2 replies; 76+ messages in thread From: Takashi Iwai @ 2010-02-01 6:43 UTC (permalink / raw) To: sboyce; +Cc: Rafael J. Wysocki, Linux Kernel Mailing List, Kernel Testers List At Mon, 01 Feb 2010 02:01:21 +0000, Sid Boyce wrote: > > On 01/02/10 00:22, Rafael J. Wysocki wrote: > > This message has been generated automatically as a part of a report > > of recent regressions. > > > > The following bug entry is on the current list of known regressions > > from 2.6.32. Please verify if it still should be listed and let me know > > (either way). > > > > > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15144 > > Subject : HDA Intel Audio hang on boot > > Submitter : Sid Boyce <sboyce@blueyonder.co.uk> > > Date : 2010-01-15 1:24 (17 days old) > > References : http://marc.info/?l=linux-kernel&m=126351866722507&w=4 > > > > > > > > Still not fixed in 2.6.33-rc6. Takashi wrote that the fix was scheduled > for 2.6.33-rc6, but it did not appear. It just slipped from rc6 due to my busy load. The pull request was sent yesterday. Takashi ^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: [Bug #15144] HDA Intel Audio hang on boot 2010-02-01 6:43 ` Takashi Iwai @ 2010-02-02 20:40 ` Rafael J. Wysocki 2010-02-03 2:37 ` Sid Boyce 2010-02-14 20:29 ` Sid Boyce 1 sibling, 1 reply; 76+ messages in thread From: Rafael J. Wysocki @ 2010-02-02 20:40 UTC (permalink / raw) To: Takashi Iwai; +Cc: sboyce, Linux Kernel Mailing List, Kernel Testers List On Monday 01 February 2010, Takashi Iwai wrote: > At Mon, 01 Feb 2010 02:01:21 +0000, > Sid Boyce wrote: > > > > On 01/02/10 00:22, Rafael J. Wysocki wrote: > > > This message has been generated automatically as a part of a report > > > of recent regressions. > > > > > > The following bug entry is on the current list of known regressions > > > from 2.6.32. Please verify if it still should be listed and let me know > > > (either way). > > > > > > > > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15144 > > > Subject : HDA Intel Audio hang on boot > > > Submitter : Sid Boyce <sboyce@blueyonder.co.uk> > > > Date : 2010-01-15 1:24 (17 days old) > > > References : http://marc.info/?l=linux-kernel&m=126351866722507&w=4 > > > > > > > > > > > > > Still not fixed in 2.6.33-rc6. Takashi wrote that the fix was scheduled > > for 2.6.33-rc6, but it did not appear. > > It just slipped from rc6 due to my busy load. > The pull request was sent yesterday. Linus has already merged it, so I've closed the bug. Rafael ^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: [Bug #15144] HDA Intel Audio hang on boot 2010-02-02 20:40 ` Rafael J. Wysocki @ 2010-02-03 2:37 ` Sid Boyce 0 siblings, 0 replies; 76+ messages in thread From: Sid Boyce @ 2010-02-03 2:37 UTC (permalink / raw) To: Rafael J. Wysocki Cc: Takashi Iwai, Linux Kernel Mailing List, Kernel Testers List On 02/02/10 20:40, Rafael J. Wysocki wrote: > On Monday 01 February 2010, Takashi Iwai wrote: >> At Mon, 01 Feb 2010 02:01:21 +0000, >> Sid Boyce wrote: >>> >>> On 01/02/10 00:22, Rafael J. Wysocki wrote: >>>> This message has been generated automatically as a part of a report >>>> of recent regressions. >>>> >>>> The following bug entry is on the current list of known regressions >>>> from 2.6.32. Please verify if it still should be listed and let me know >>>> (either way). >>>> >>>> >>>> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15144 >>>> Subject : HDA Intel Audio hang on boot >>>> Submitter : Sid Boyce <sboyce@blueyonder.co.uk> >>>> Date : 2010-01-15 1:24 (17 days old) >>>> References : http://marc.info/?l=linux-kernel&m=126351866722507&w=4 >>>> >>>> >>>> >>> >>> Still not fixed in 2.6.33-rc6. Takashi wrote that the fix was scheduled >>> for 2.6.33-rc6, but it did not appear. >> >> It just slipped from rc6 due to my busy load. >> The pull request was sent yesterday. > > Linus has already merged it, so I've closed the bug. > > Rafael > I added the line to hda_intel.c in 2.6.33-rc6 as I had oopses in 2.6.33-rc6-git1 that I haven't yet captured. SND_PCI_QUIRK(0x1043, 0x829c, "ASUS", 0), /* nvidia */ The problem was still there. I shall have a further look later today. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks ^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: [Bug #15144] HDA Intel Audio hang on boot 2010-02-01 6:43 ` Takashi Iwai 2010-02-02 20:40 ` Rafael J. Wysocki @ 2010-02-14 20:29 ` Sid Boyce 2010-02-14 21:50 ` Rafael J. Wysocki 2010-02-15 7:12 ` yTakashi Iwai 1 sibling, 2 replies; 76+ messages in thread From: Sid Boyce @ 2010-02-14 20:29 UTC (permalink / raw) To: Takashi Iwai Cc: Rafael J. Wysocki, Linux Kernel Mailing List, Kernel Testers List On 01/02/10 06:43, Takashi Iwai wrote: > At Mon, 01 Feb 2010 02:01:21 +0000, > Sid Boyce wrote: >> >> On 01/02/10 00:22, Rafael J. Wysocki wrote: >>> This message has been generated automatically as a part of a report >>> of recent regressions. >>> >>> The following bug entry is on the current list of known regressions >>> from 2.6.32. Please verify if it still should be listed and let me know >>> (either way). >>> >>> >>> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15144 >>> Subject : HDA Intel Audio hang on boot >>> Submitter : Sid Boyce <sboyce@blueyonder.co.uk> >>> Date : 2010-01-15 1:24 (17 days old) >>> References : http://marc.info/?l=linux-kernel&m=126351866722507&w=4 >>> >>> >>> >> >> Still not fixed in 2.6.33-rc6. Takashi wrote that the fix was scheduled >> for 2.6.33-rc6, but it did not appear. > > It just slipped from rc6 due to my busy load. > The pull request was sent yesterday. > > > Takashi > Up to 2.6.33-rc8 still needs the work around in /etc/modprobe.d/50-sound.conf, so the kernel blacklist fix does not work. # less /etc/modprobe.d/50-sound.conf options slots=snd-hda-intel # 9LTX.vLXC8EvZgR7:MCP55 High Definition Audio alias snd-card-0 snd-hda-intel options snd-hda-intel enable_msi=0 Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks ^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: [Bug #15144] HDA Intel Audio hang on boot 2010-02-14 20:29 ` Sid Boyce @ 2010-02-14 21:50 ` Rafael J. Wysocki 2010-02-15 7:12 ` yTakashi Iwai 1 sibling, 0 replies; 76+ messages in thread From: Rafael J. Wysocki @ 2010-02-14 21:50 UTC (permalink / raw) To: sboyce; +Cc: Takashi Iwai, Linux Kernel Mailing List, Kernel Testers List On Sunday 14 February 2010, Sid Boyce wrote: > On 01/02/10 06:43, Takashi Iwai wrote: > > At Mon, 01 Feb 2010 02:01:21 +0000, > > Sid Boyce wrote: > >> > >> On 01/02/10 00:22, Rafael J. Wysocki wrote: > >>> This message has been generated automatically as a part of a report > >>> of recent regressions. > >>> > >>> The following bug entry is on the current list of known regressions > >>> from 2.6.32. Please verify if it still should be listed and let me know > >>> (either way). > >>> > >>> > >>> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15144 > >>> Subject : HDA Intel Audio hang on boot > >>> Submitter : Sid Boyce <sboyce@blueyonder.co.uk> > >>> Date : 2010-01-15 1:24 (17 days old) > >>> References : http://marc.info/?l=linux-kernel&m=126351866722507&w=4 > >>> > >>> > >>> > >> > >> Still not fixed in 2.6.33-rc6. Takashi wrote that the fix was scheduled > >> for 2.6.33-rc6, but it did not appear. > > > > It just slipped from rc6 due to my busy load. > > The pull request was sent yesterday. > > > > > > Takashi > > > > Up to 2.6.33-rc8 still needs the work around in > /etc/modprobe.d/50-sound.conf, so the kernel blacklist fix does not work. > > # less /etc/modprobe.d/50-sound.conf > > options slots=snd-hda-intel > # 9LTX.vLXC8EvZgR7:MCP55 High Definition Audio > alias snd-card-0 snd-hda-intel > options snd-hda-intel enable_msi=0 Thanks for the update. I'll be sending a summary regression report later today with a follow-up message regarding this bug. You won't need to reply to that one. Rafael ^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: [Bug #15144] HDA Intel Audio hang on boot 2010-02-14 20:29 ` Sid Boyce 2010-02-14 21:50 ` Rafael J. Wysocki @ 2010-02-15 7:12 ` yTakashi Iwai 2010-02-15 12:46 ` Sid Boyce 1 sibling, 1 reply; 76+ messages in thread From: yTakashi Iwai @ 2010-02-15 7:12 UTC (permalink / raw) To: sboyce; +Cc: Rafael J. Wysocki, Linux Kernel Mailing List At Sun, 14 Feb 2010 20:29:01 +0000, Sid Boyce wrote: > > On 01/02/10 06:43, Takashi Iwai wrote: > > At Mon, 01 Feb 2010 02:01:21 +0000, > > Sid Boyce wrote: > >> > >> On 01/02/10 00:22, Rafael J. Wysocki wrote: > >>> This message has been generated automatically as a part of a report > >>> of recent regressions. > >>> > >>> The following bug entry is on the current list of known regressions > >>> from 2.6.32. Please verify if it still should be listed and let me know > >>> (either way). > >>> > >>> > >>> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15144 > >>> Subject : HDA Intel Audio hang on boot > >>> Submitter : Sid Boyce <sboyce@blueyonder.co.uk> > >>> Date : 2010-01-15 1:24 (17 days old) > >>> References : http://marc.info/?l=linux-kernel&m=126351866722507&w=4 > >>> > >>> > >>> > >> > >> Still not fixed in 2.6.33-rc6. Takashi wrote that the fix was scheduled > >> for 2.6.33-rc6, but it did not appear. > > > > It just slipped from rc6 due to my busy load. > > The pull request was sent yesterday. > > > > > > Takashi > > > > Up to 2.6.33-rc8 still needs the work around in > /etc/modprobe.d/50-sound.conf, so the kernel blacklist fix does not work. Check the kernel message. Don't you have a message like "hda_intel: msi for device 1043:829c set to 0"? Otherwise give alsa-info.sh again. But, essentially this is a problem of your mobo and Linux MSI handling, not exactly a driver issue, IMO... I guess the problem will go away if you remove your another sound card on the PCI slot. Or maybe it'd work even by moving to another slot... Takashi ^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: [Bug #15144] HDA Intel Audio hang on boot 2010-02-15 7:12 ` yTakashi Iwai @ 2010-02-15 12:46 ` Sid Boyce 2010-02-15 12:53 ` Takashi Iwai 0 siblings, 1 reply; 76+ messages in thread From: Sid Boyce @ 2010-02-15 12:46 UTC (permalink / raw) To: yTakashi Iwai; +Cc: Rafael J. Wysocki, Linux Kernel Mailing List [-- Attachment #1: Type: text/plain, Size: 3042 bytes --] On 15/02/10 07:12, yTakashi Iwai wrote: > At Sun, 14 Feb 2010 20:29:01 +0000, > Sid Boyce wrote: >> >> On 01/02/10 06:43, Takashi Iwai wrote: >>> At Mon, 01 Feb 2010 02:01:21 +0000, >>> Sid Boyce wrote: >>>> >>>> On 01/02/10 00:22, Rafael J. Wysocki wrote: >>>>> This message has been generated automatically as a part of a report >>>>> of recent regressions. >>>>> >>>>> The following bug entry is on the current list of known regressions >>>>> from 2.6.32. Please verify if it still should be listed and let me know >>>>> (either way). >>>>> >>>>> >>>>> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15144 >>>>> Subject : HDA Intel Audio hang on boot >>>>> Submitter : Sid Boyce <sboyce@blueyonder.co.uk> >>>>> Date : 2010-01-15 1:24 (17 days old) >>>>> References : http://marc.info/?l=linux-kernel&m=126351866722507&w=4 >>>>> >>>>> >>>>> >>>> >>>> Still not fixed in 2.6.33-rc6. Takashi wrote that the fix was scheduled >>>> for 2.6.33-rc6, but it did not appear. >>> >>> It just slipped from rc6 due to my busy load. >>> The pull request was sent yesterday. >>> >>> >>> Takashi >>> >> >> Up to 2.6.33-rc8 still needs the work around in >> /etc/modprobe.d/50-sound.conf, so the kernel blacklist fix does not work. > > Check the kernel message. Don't you have a message like "hda_intel: > msi for device 1043:829c set to 0"? Otherwise give alsa-info.sh > again. > No mention of it - 2.6.33-rc8. tindog:~ # dmesg|grep 1043 tindog:~ # grep 1043 /var/log/boot.msg tindog:~ # grep 1043 /var/log/messages tindog:~ # The patch seems to be addressing the wrong device, alsa-info.sh shows it as Subsystem: 1043:81f6 Subsystem Id: 0x104381f6 Components : 'HDA:11d4198b,104381f6,00100300' tindog:/usr/src/linux-2.6.33-rc8 # grep 1043 ./sound/pci/hda/hda_intel.c SND_PCI_QUIRK(0x1043, 0x813d, "ASUS P5AD2", POS_FIX_LPIB), SND_PCI_QUIRK(0x1043, 0x1262, "ASUS W5Fm", 0x103), SND_PCI_QUIRK(0x1043, 0x81f2, "ASUS", 0), /* Athlon64 X2 + nvidia */ SND_PCI_QUIRK(0x1043, 0x829c, "ASUS", 0), /* nvidia */ I shall change the 0x81f2 to 0x81f6 and test. > But, essentially this is a problem of your mobo and Linux MSI > handling, not exactly a driver issue, IMO... > I think you are correct, could be the motherboard or BIOS. I have tried a number of BIOS versions with the same result. I am about to change to a Asus Crosshair III motherboard in a few days when the memory arrives. It also wouldn't boot if I have kgdb enabled in .config, I get a stream of Traces with "Tainted". > I guess the problem will go away if you remove your another sound card > on the PCI slot. Or maybe it'd work even by moving to another > slot... > It's the on-board sound. Before the work around I had to disable it in the BIOS and use the USB sound card. > > Takashi > Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks [-- Attachment #2: alsa-info-tindog.txt --] [-- Type: text/plain, Size: 83986 bytes --] upload=true&script=true&cardinfo= !!################################ !!ALSA Information Script v 0.4.58 !!################################ !!Script ran on: Mon Feb 15 12:13:10 UTC 2010 !!Linux Distribution !!------------------ Welcome to openSUSE 11.3 "Teal" Milestone 1 - Kernel \r (\l). openSUSE 11.3 Milestone 1 (x86_64) LSB_VERSION="core-2.0-noarch:core-3.2-noarch:core-4.0-noarch:core-2.0-x86_64:core-3.2-x86_64:core-4.0-x86_64" !!DMI Information !!--------------- Manufacturer: System manufacturer Product Name: System Product Name !!Kernel Information !!------------------ Kernel release: 2.6.33-rc8-smp Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !!------------ Driver version: 1.0.21 Library version: 1.0.22 Utilities version: 1.0.22 !!Loaded ALSA modules !!------------------- snd_usb_audio snd_usb_audio snd_hda_intel !!Sound Servers on this system !!---------------------------- Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes ESound Daemon: Installed - Yes (/usr/bin/esd) Running - No aRts: Installed - Yes (/opt/kde3/bin/artsd) Running - No Jack: Installed - Yes (/usr/local/bin/jackd) Running - No !!Soundcards recognised by ALSA !!----------------------------- 0 [Q9000 ]: USB-Audio - QuickCam Pro 9000 Logitech, Inc. QuickCam Pro 9000 at usb-0000:00:0a.1-4, high speed 1 [Aureon51MkII ]: USB-Audio - Aureon5.1MkII TerraTec Aureon5.1MkII at usb-0000:00:0a.0-3, full speed 2 [NVidia ]: HDA-Intel - HDA NVidia HDA NVidia at 0xfe020000 irq 20 !!PCI Soundcards installed in the system !!-------------------------------------- 00:0e.1 Audio device: nVidia Corporation MCP55 High Definition Audio (rev a2) !!Advanced information - PCI Vendor/Device/Susbsystem ID's !!-------------------------------------------------------- 00:0e.1 0403: 10de:0371 (rev a2) Subsystem: 1043:81f6 -- 01:00.0 0300: 10de:0402 (rev a1) (prog-if 00 [VGA controller]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- !!Modprobe options (Sound related) !!-------------------------------- snd-hda-intel: enable_msi=0 !!Loaded sound module options !!-------------------------- !!Module: snd_usb_audio async_unlink : Y device_setup : 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 enable : Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y id : (null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null) ignore_ctl_error : N index : -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1 nrpacks : 8 pid : -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1 vid : -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1 !!Module: snd_usb_audio async_unlink : Y device_setup : 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 enable : Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y id : (null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null) ignore_ctl_error : N index : -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1 nrpacks : 8 pid : -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1 vid : -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1 !!Module: snd_hda_intel bdl_pos_adj : 32,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1 enable : Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y enable_msi : 0 id : (null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null) index : -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1 model : (null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null) patch : (null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null) position_fix : 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 power_save : 0 power_save_controller : Y probe_mask : -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1 probe_only : N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N single_cmd : N !!HDA-Intel Codec information !!--------------------------- --startcollapse-- Codec: Analog Devices AD1988B Address: 0 Function Id: 0x1 Vendor Id: 0x11d4198b Subsystem Id: 0x104381f6 Revision Id: 0x100300 No Modem Function Group found Default PCM: rates [0x7ff]: 8000 11025 16000 22050 32000 44100 48000 88200 96000 176400 192000 bits [0xe]: 16 20 24 formats [0x1]: PCM Default Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Default Amp-Out caps: ofs=0x27, nsteps=0x27, stepsize=0x05, mute=0 GPIO: io=2, o=0, i=0, unsolicited=1, wake=0 IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[1]: enable=0, dir=0, wake=0, sticky=0, data=1, unsol=0 Node 0x02 [Audio Output] wcaps 0x30311: Stereo Digital Control: name="IEC958 Playback Con Mask", index=0, device=0 Control: name="IEC958 Playback Pro Mask", index=0, device=0 Control: name="IEC958 Playback Default", index=0, device=0 Control: name="IEC958 Playback Switch", index=0, device=0 Control: name="IEC958 Default PCM Playback Switch", index=0, device=0 Device: name="AD198x Digital", type="SPDIF", device=1 Converter: stream=0, channel=0 Digital: Enabled Digital category: 0x0 PCM: rates [0x7e0]: 44100 48000 88200 96000 176400 192000 bits [0xe]: 16 20 24 formats [0x5]: PCM AC3 Delay: 3 samples Connection: 1 0x1d Node 0x03 [Audio Output] wcaps 0x405: Stereo Amp-Out Amp-Out caps: ofs=0x27, nsteps=0x27, stepsize=0x05, mute=0 Amp-Out vals: [0x27 0x27] Converter: stream=0, channel=0 Power states: D0 D3 Power: setting=D0, actual=D0 Node 0x04 [Audio Output] wcaps 0x405: Stereo Amp-Out Control: name="Front Playback Volume", index=0, device=0 Device: name="AD198x Analog", type="Audio", device=0 Amp-Out caps: ofs=0x27, nsteps=0x27, stepsize=0x05, mute=0 Amp-Out vals: [0x27 0x27] Converter: stream=5, channel=0 Power states: D0 D3 Power: setting=D0, actual=D0 Node 0x05 [Audio Output] wcaps 0x405: Stereo Amp-Out Control: name="Center Playback Volume", index=0, device=0 Control: name="LFE Playback Volume", index=0, device=0 Amp-Out caps: ofs=0x27, nsteps=0x27, stepsize=0x05, mute=0 Amp-Out vals: [0x27 0x27] Converter: stream=5, channel=0 Power states: D0 D3 Power: setting=D0, actual=D0 Node 0x06 [Audio Output] wcaps 0x405: Stereo Amp-Out Control: name="Surround Playback Volume", index=0, device=0 Amp-Out caps: ofs=0x27, nsteps=0x27, stepsize=0x05, mute=0 Amp-Out vals: [0x27 0x27] Converter: stream=5, channel=0 Power states: D0 D3 Power: setting=D0, actual=D0 Node 0x07 [Audio Input] wcaps 0x130391: Stereo Digital Control: name="IEC958 Capture Switch", index=0, device=0 Control: name="IEC958 Capture Default", index=0, device=0 Device: name="AD198x Digital", type="SPDIF", device=1 Converter: stream=0, channel=0 SDI-Select: 0 Digital: Digital category: 0x0 PCM: rates [0x7e0]: 44100 48000 88200 96000 176400 192000 bits [0xe]: 16 20 24 formats [0x5]: PCM AC3 Unsolicited: tag=00, enabled=0 Delay: 3 samples Connection: 1 0x1c Node 0x08 [Audio Input] wcaps 0x100501: Stereo Device: name="AD198x Analog", type="Audio", device=0 Converter: stream=1, channel=0 SDI-Select: 0 Power states: D0 D3 Power: setting=D0, actual=D0 Connection: 1 0x0c Node 0x09 [Audio Input] wcaps 0x100501: Stereo Converter: stream=0, channel=0 SDI-Select: 0 Power states: D0 D3 Power: setting=D0, actual=D0 Connection: 1 0x0d Node 0x0a [Audio Output] wcaps 0x405: Stereo Amp-Out Control: name="Side Playback Volume", index=0, device=0 Amp-Out caps: ofs=0x27, nsteps=0x27, stepsize=0x05, mute=0 Amp-Out vals: [0x27 0x27] Converter: stream=5, channel=0 Power states: D0 D3 Power: setting=D0, actual=D0 Node 0x0b [Audio Selector] wcaps 0x300301: Stereo Digital Connection: 3 0x08* 0x09 0x0f Node 0x0c [Audio Selector] wcaps 0x30010d: Stereo Amp-Out Control: name="Capture Volume", index=0, device=0 Control: name="Capture Switch", index=0, device=0 Amp-Out caps: ofs=0x27, nsteps=0x36, stepsize=0x05, mute=1 Amp-Out vals: [0x35 0x35] Connection: 10 0x38 0x39* 0x3a 0x3b 0x3c 0x18 0x24 0x25 0x3d 0x20 Node 0x0d [Audio Selector] wcaps 0x30010d: Stereo Amp-Out Control: name="Capture Volume", index=1, device=0 Control: name="Capture Switch", index=1, device=0 Amp-Out caps: ofs=0x27, nsteps=0x36, stepsize=0x05, mute=1 Amp-Out vals: [0xaa 0xaa] Connection: 10 0x38 0x39* 0x3a 0x3b 0x3c 0x18 0x24 0x25 0x3d 0x20 Node 0x0e [Audio Selector] wcaps 0x30010d: Stereo Amp-Out Control: name="Capture Volume", index=2, device=0 Control: name="Capture Switch", index=2, device=0 Amp-Out caps: ofs=0x27, nsteps=0x36, stepsize=0x05, mute=1 Amp-Out vals: [0xab 0xab] Connection: 10 0x38 0x39* 0x3a 0x3b 0x3c 0x18 0x24 0x25 0x3d 0x20 Node 0x0f [Audio Input] wcaps 0x100501: Stereo Converter: stream=0, channel=0 SDI-Select: 0 Power states: D0 D3 Power: setting=D0, actual=D0 Connection: 1 0x0e Node 0x10 [Beep Generator Widget] wcaps 0x70000c: Mono Amp-Out Amp-Out caps: ofs=0x0f, nsteps=0x0f, stepsize=0x0b, mute=1 Amp-Out vals: [0x00] Node 0x11 [Pin Complex] wcaps 0x40018d: Stereo Amp-Out Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-Out vals: [0x00 0x00] Pincap 0x0000373f: IN OUT HP Detect Trigger ImpSense Vref caps: HIZ 50 GRD 80 100 Pin Default 0x02214130: [Jack] HP Out at Ext Front Conn = 1/8, Color = Green DefAssociation = 0x3, Sequence = 0x0 Misc = NO_PRESENCE Pin-ctls: 0xc0: OUT HP VREF_HIZ Unsolicited: tag=00, enabled=0 Connection: 1 0x22 Node 0x12 [Pin Complex] wcaps 0x40018d: Stereo Amp-Out Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-Out vals: [0x00 0x00] Pincap 0x0000373f: IN OUT HP Detect Trigger ImpSense Vref caps: HIZ 50 GRD 80 100 Pin Default 0x01014010: [Jack] Line Out at Ext Rear Conn = 1/8, Color = Green DefAssociation = 0x1, Sequence = 0x0 Pin-ctls: 0x40: OUT VREF_HIZ Unsolicited: tag=00, enabled=0 Connection: 1 0x29 Node 0x13 [Pin Complex] wcaps 0x40010c: Mono Amp-Out Amp-Out caps: ofs=0x1f, nsteps=0x1f, stepsize=0x05, mute=1 Amp-Out vals: [0x00] Pincap 0x00000010: OUT Pin Default 0x511711f0: [N/A] Speaker at Int Rear Conn = Analog, Color = Black DefAssociation = 0xf, Sequence = 0x0 Misc = NO_PRESENCE Pin-ctls: 0x40: OUT Connection: 1 0x2d Node 0x14 [Pin Complex] wcaps 0x40018d: Stereo Amp-Out Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-Out vals: [0x80 0x80] Pincap 0x0000373f: IN OUT HP Detect Trigger ImpSense Vref caps: HIZ 50 GRD 80 100 Pin Default 0x02a1912e: [Jack] Mic at Ext Front Conn = 1/8, Color = Pink DefAssociation = 0x2, Sequence = 0xe Misc = NO_PRESENCE Pin-ctls: 0x24: IN VREF_80 Unsolicited: tag=00, enabled=0 Connection: 1 0x2b Node 0x15 [Pin Complex] wcaps 0x40018d: Stereo Amp-Out Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-Out vals: [0x80 0x80] Pincap 0x00003737: IN OUT Detect Trigger ImpSense Vref caps: HIZ 50 GRD 80 100 Pin Default 0x01813021: [Jack] Line In at Ext Rear Conn = 1/8, Color = Blue DefAssociation = 0x2, Sequence = 0x1 Pin-ctls: 0x20: IN VREF_HIZ Unsolicited: tag=00, enabled=0 Connection: 1 0x2c Node 0x16 [Pin Complex] wcaps 0x40018d: Stereo Amp-Out Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-Out vals: [0x00 0x00] Pincap 0x00003737: IN OUT Detect Trigger ImpSense Vref caps: HIZ 50 GRD 80 100 Pin Default 0x01011012: [Jack] Line Out at Ext Rear Conn = 1/8, Color = Black DefAssociation = 0x1, Sequence = 0x2 Pin-ctls: 0x40: OUT VREF_HIZ Unsolicited: tag=00, enabled=0 Connection: 1 0x2a Node 0x17 [Pin Complex] wcaps 0x40098d: Stereo Amp-Out R/L Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-Out vals: [0x80 0x80] Pincap 0x00003737: IN OUT Detect Trigger ImpSense Vref caps: HIZ 50 GRD 80 100 Pin Default 0x01a19020: [Jack] Mic at Ext Rear Conn = 1/8, Color = Pink DefAssociation = 0x2, Sequence = 0x0 Pin-ctls: 0x24: IN VREF_80 Unsolicited: tag=00, enabled=0 Connection: 1 0x26 Node 0x18 [Pin Complex] wcaps 0x400001: Stereo Pincap 0x00000020: IN Pin Default 0x99331122: [Fixed] CD at Int ATAPI Conn = ATAPI, Color = Black DefAssociation = 0x2, Sequence = 0x2 Misc = NO_PRESENCE Pin-ctls: 0x20: IN Node 0x19 [Power Widget] wcaps 0x500500: Mono Power states: D0 D3 Power: setting=D0, actual=D0 Connection: 2 0x20 0x21 Node 0x1a [Pin Complex] wcaps 0x400000: Mono Pincap 0x00000020: IN Pin Default 0x91f711f0: [Fixed] Other at Int Rear Conn = Analog, Color = Black DefAssociation = 0xf, Sequence = 0x0 Misc = NO_PRESENCE Pin-ctls: 0x20: IN Node 0x1b [Pin Complex] wcaps 0x40030d: Stereo Digital Amp-Out Control: name="IEC958 Playback Volume", index=0, device=0 Amp-Out caps: ofs=0x27, nsteps=0x27, stepsize=0x05, mute=1 Amp-Out vals: [0x00 0x00] Pincap 0x00000010: OUT Pin Default 0x0145f1f0: [Jack] SPDIF Out at Ext Rear Conn = Optical, Color = Other DefAssociation = 0xf, Sequence = 0x0 Misc = NO_PRESENCE Pin-ctls: 0x40: OUT Connection: 1 0x02 Node 0x1c [Pin Complex] wcaps 0x40020b: Stereo Digital Amp-In Control: name="IEC958 Capture Volume", index=0, device=0 Amp-In caps: ofs=0x17, nsteps=0x1f, stepsize=0x05, mute=1 Amp-In vals: [0x97 0x97] Pincap 0x00000020: IN Pin Default 0x41c5f1f0: [N/A] SPDIF In at Ext Rear Conn = Optical, Color = Other DefAssociation = 0xf, Sequence = 0x0 Misc = NO_PRESENCE Pin-ctls: 0x20: IN Node 0x1d [Audio Mixer] wcaps 0x200303: Stereo Digital Amp-In Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-In vals: [0x00 0x00] [0x80 0x80] Connection: 2 0x01 0x0b Node 0x1e [Audio Mixer] wcaps 0x200103: Stereo Amp-In Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-In vals: [0x00 0x00] [0x00 0x00] Connection: 2 0x36 0x21 Node 0x1f [Volume Knob Widget] wcaps 0x600080: Mono Volume-Knob: delta=1, steps=63, direct=0, val=0 Unsolicited: tag=00, enabled=0 Connection: 0 Node 0x20 [Audio Mixer] wcaps 0x20010b: Stereo Amp-In Control: name="CD Playback Volume", index=0, device=0 Control: name="CD Playback Switch", index=0, device=0 Control: name="Front Mic Playback Volume", index=0, device=0 Control: name="Front Mic Playback Switch", index=0, device=0 Control: name="Line Playback Volume", index=0, device=0 Control: name="Line Playback Switch", index=0, device=0 Control: name="Mic Playback Volume", index=0, device=0 Control: name="Mic Playback Switch", index=0, device=0 Amp-In caps: ofs=0x17, nsteps=0x1f, stepsize=0x05, mute=1 Amp-In vals: [0x19 0x19] [0x1f 0x1f] [0x80 0x80] [0x80 0x80] [0x1d 0x1d] [0x80 0x80] [0x1e 0x1e] [0x80 0x80] Connection: 8 0x39 0x33 0x38 0x3d 0x34 0x3b 0x18 0x1a Node 0x21 [Audio Selector] wcaps 0x30010d: Stereo Amp-Out Control: name="Analog Mix Playback Volume", index=0, device=0 Control: name="Analog Mix Playback Switch", index=0, device=0 Amp-Out caps: ofs=0x1f, nsteps=0x1f, stepsize=0x05, mute=1 Amp-Out vals: [0x19 0x19] Connection: 1 0x20 Node 0x22 [Audio Mixer] wcaps 0x200103: Stereo Amp-In Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-In vals: [0x00 0x00] [0x00 0x00] Connection: 2 0x37 0x21 Node 0x23 [Vendor Defined Widget] wcaps 0xf00100: Mono Connection: 18 0x11* 0x12 0x13 0x14 0x15 0x16 0x17 0x18 0x24 0x25 0x38 0x39 0x3a 0x3b 0x3c 0x3d 0x20 0x21 Node 0x24 [Pin Complex] wcaps 0x40098d: Stereo Amp-Out R/L Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-Out vals: [0x00 0x00] Pincap 0x00000037: IN OUT Detect Trigger ImpSense Pin Default 0x01016011: [Jack] Line Out at Ext Rear Conn = 1/8, Color = Orange DefAssociation = 0x1, Sequence = 0x1 Pin-ctls: 0x40: OUT Unsolicited: tag=00, enabled=0 Connection: 1 0x27 Node 0x25 [Pin Complex] wcaps 0x40018d: Stereo Amp-Out Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-Out vals: [0x00 0x00] Pincap 0x00000037: IN OUT Detect Trigger ImpSense Pin Default 0x01012014: [Jack] Line Out at Ext Rear Conn = 1/8, Color = Grey DefAssociation = 0x1, Sequence = 0x4 Pin-ctls: 0x40: OUT Unsolicited: tag=00, enabled=0 Connection: 1 0x28 Node 0x26 [Audio Mixer] wcaps 0x200103: Stereo Amp-In Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-In vals: [0x80 0x80] [0x80 0x80] Connection: 2 0x32 0x21 Node 0x27 [Audio Mixer] wcaps 0x200103: Stereo Amp-In Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-In vals: [0x00 0x00] [0x00 0x00] Connection: 2 0x05 0x21 Node 0x28 [Audio Mixer] wcaps 0x200103: Stereo Amp-In Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-In vals: [0x00 0x00] [0x00 0x00] Connection: 2 0x0a 0x21 Node 0x29 [Audio Mixer] wcaps 0x200103: Stereo Amp-In Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-In vals: [0x00 0x00] [0x00 0x00] Connection: 2 0x04 0x21 Node 0x2a [Audio Mixer] wcaps 0x200103: Stereo Amp-In Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-In vals: [0x00 0x00] [0x00 0x00] Connection: 2 0x06 0x21 Node 0x2b [Audio Mixer] wcaps 0x200103: Stereo Amp-In Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-In vals: [0x80 0x80] [0x80 0x80] Connection: 2 0x30 0x21 Node 0x2c [Audio Mixer] wcaps 0x200103: Stereo Amp-In Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-In vals: [0x80 0x80] [0x80 0x80] Connection: 2 0x31 0x21 Node 0x2d [Audio Mixer] wcaps 0x200100: Mono Connection: 1 0x1e Node 0x2e [Vendor Defined Widget] wcaps 0xf00000: Mono Node 0x2f [Vendor Defined Widget] wcaps 0xf00100: Mono Connection: 6 0x11* 0x12 0x14 0x15 0x16 0x17 Node 0x30 [Audio Selector] wcaps 0x300101: Stereo Connection: 3 0x03* 0x04 0x06 Node 0x31 [Audio Selector] wcaps 0x300101: Stereo Connection: 2 0x04* 0x0a Node 0x32 [Audio Selector] wcaps 0x300101: Stereo Connection: 2 0x05* 0x04 Node 0x33 [Audio Selector] wcaps 0x300101: Stereo Connection: 3 0x3a* 0x25 0x24 Node 0x34 [Audio Selector] wcaps 0x300101: Stereo Connection: 3 0x3c* 0x25 0x24 Node 0x35 [Vendor Defined Widget] wcaps 0xf00000: Mono Node 0x36 [Audio Selector] wcaps 0x300101: Stereo Connection: 3 0x03 0x04* 0x06 Node 0x37 [Audio Selector] wcaps 0x300101: Stereo Connection: 3 0x03 0x04* 0x06 Node 0x38 [Audio Selector] wcaps 0x30010d: Stereo Amp-Out Amp-Out caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0 Amp-Out vals: [0x00 0x00] Connection: 1 0x11 Node 0x39 [Audio Selector] wcaps 0x30010d: Stereo Amp-Out Control: name="Front Mic Boost", index=0, device=0 Amp-Out caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0 Amp-Out vals: [0x00 0x00] Connection: 1 0x14 Node 0x3a [Audio Selector] wcaps 0x30010d: Stereo Amp-Out Amp-Out caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0 Amp-Out vals: [0x00 0x00] Connection: 1 0x15 Node 0x3b [Audio Selector] wcaps 0x30010d: Stereo Amp-Out Amp-Out caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0 Amp-Out vals: [0x00 0x00] Connection: 1 0x16 Node 0x3c [Audio Selector] wcaps 0x30010d: Stereo Amp-Out Control: name="Mic Boost", index=0, device=0 Amp-Out caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0 Amp-Out vals: [0x03 0x03] Connection: 1 0x17 Node 0x3d [Audio Selector] wcaps 0x30010d: Stereo Amp-Out Amp-Out caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0 Amp-Out vals: [0x00 0x00] Connection: 1 0x12 --endcollapse-- !!ALSA Device nodes !!----------------- crw-rw-rw-+ 1 root audio 116, 4 Feb 14 19:58 /dev/snd/controlC0 crw-rw-rw-+ 1 root audio 116, 7 Feb 14 19:58 /dev/snd/controlC1 crw-rw-rw-+ 1 root audio 116, 13 Feb 14 19:58 /dev/snd/controlC2 crw-rw-rw-+ 1 root audio 116, 12 Feb 14 19:58 /dev/snd/hwC2D0 crw-rw-rw-+ 1 root audio 116, 3 Feb 14 20:01 /dev/snd/pcmC0D0c crw-rw-rw-+ 1 root audio 116, 6 Feb 14 20:01 /dev/snd/pcmC1D0c crw-rw-rw-+ 1 root audio 116, 5 Feb 14 20:01 /dev/snd/pcmC1D0p crw-rw-rw-+ 1 root audio 116, 11 Feb 14 20:01 /dev/snd/pcmC2D0c crw-rw-rw-+ 1 root audio 116, 10 Feb 14 20:01 /dev/snd/pcmC2D0p crw-rw-rw-+ 1 root audio 116, 9 Feb 14 20:01 /dev/snd/pcmC2D1c crw-rw-rw-+ 1 root audio 116, 8 Feb 14 20:01 /dev/snd/pcmC2D1p crw-rw-rw-+ 1 root audio 116, 14 Feb 14 19:59 /dev/snd/seq crw-rw-rw-+ 1 root audio 116, 2 Feb 14 19:58 /dev/snd/timer /dev/snd/by-id: total 0 drwxr-xr-x 2 root root 80 Feb 14 19:58 . drwxr-xr-x 4 root root 340 Feb 14 19:59 .. lrwxrwxrwx 1 root root 12 Feb 14 19:58 usb-046d_0990_7BBC20E7-02 -> ../controlC0 lrwxrwxrwx 1 root root 12 Feb 14 19:58 usb-0ccd_USB_Audio-00 -> ../controlC1 /dev/snd/by-path: total 0 drwxr-xr-x 2 root root 100 Feb 14 19:58 . drwxr-xr-x 4 root root 340 Feb 14 19:59 .. lrwxrwxrwx 1 root root 12 Feb 14 19:58 pci-0000:00:0a.0-usb-0:3:1.0 -> ../controlC1 lrwxrwxrwx 1 root root 12 Feb 14 19:58 pci-0000:00:0a.1-usb-0:4:1.2 -> ../controlC0 lrwxrwxrwx 1 root root 12 Feb 14 19:58 pci-0000:00:0e.1 -> ../controlC2 !!ALSA configuration files !!------------------------ !!User specific config file (~/.asoundrc) defaults.pcm.rate_converter "samplerate" !!System wide config file (/etc/asound.conf) # PulseAudio plugin configuration # Let's create a virtual device "pulse" for mixer and PCM pcm.pulse { type pulse } ctl.pulse { type pulse } # Let's make it the default! pcm.!default { type pulse } ctl.!default { type pulse } !!Aplay/Arecord output !!------------ APLAY **** List of PLAYBACK Hardware Devices **** card 1: Aureon51MkII [Aureon5.1MkII], device 0: USB Audio [USB Audio] Subdevices: 0/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 0: AD198x Analog [AD198x Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 1: AD198x Digital [AD198x Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 ARECORD **** List of CAPTURE Hardware Devices **** card 0: Q9000 [QuickCam Pro 9000], device 0: USB Audio [USB Audio] Subdevices: 0/1 Subdevice #0: subdevice #0 card 1: Aureon51MkII [Aureon5.1MkII], device 0: USB Audio [USB Audio] Subdevices: 0/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 0: AD198x Analog [AD198x Analog] Subdevices: 2/3 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 Subdevice #2: subdevice #2 card 2: NVidia [HDA NVidia], device 1: AD198x Digital [AD198x Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 !!Amixer output !!------------- !!-------Mixer controls for card 0 [Q9000] Card hw:0 'Q9000'/'Logitech, Inc. QuickCam Pro 9000 at usb-0000:00:0a.1-4, high speed' Mixer name : 'USB Mixer' Components : 'USB046d:0990' Controls : 2 Simple ctrls : 1 Simple mixer control 'Mic',0 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum Capture channels: Mono Limits: Capture 0 - 3072 Mono: Capture 141 [5%] [18.55dB] [on] !!-------Mixer controls for card 1 [Aureon51MkII] Card hw:1 'Aureon51MkII'/'TerraTec Aureon5.1MkII at usb-0000:00:0a.0-3, full speed' Mixer name : 'USB Mixer' Components : 'USB0ccd:0028' Controls : 13 Simple ctrls : 5 Simple mixer control 'Master',0 Capabilities: pvolume pvolume-joined pswitch pswitch-joined penum Playback channels: Mono Limits: Playback 0 - 255 Mono: Playback 241 [95%] [-2.69dB] [on] Simple mixer control 'Line',0 Capabilities: pvolume cvolume pswitch pswitch-joined cswitch cswitch-joined cswitch-exclusive penum Capture exclusive group: 0 Playback channels: Front Left - Front Right Capture channels: Front Left - Front Right Limits: Playback 0 - 255 Capture 0 - 128 Front Left: Playback 191 [75%] [35.81dB] [off] Capture 0 [0%] [0.00dB] [off] Front Right: Playback 191 [75%] [35.81dB] [off] Capture 0 [0%] [0.00dB] [off] Simple mixer control 'Mic',0 Capabilities: pvolume pvolume-joined cvolume cvolume-joined pswitch pswitch-joined cswitch cswitch-joined cswitch-exclusive penum Capture exclusive group: 0 Playback channels: Mono Capture channels: Mono Limits: Playback 0 - 255 Capture 0 - 128 Mono: Playback 42 [16%] [7.87dB] [on] Capture 12 [9%] [2.23dB] [off] Simple mixer control 'Mic Capture',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [off] Simple mixer control 'IEC958 In',0 Capabilities: cswitch cswitch-joined cswitch-exclusive penum Capture exclusive group: 0 Capture channels: Mono Mono: Capture [off] !!-------Mixer controls for card 2 [NVidia] Card hw:2 'NVidia'/'HDA NVidia at 0xfe020000 irq 20' Mixer name : 'Analog Devices AD1988B' Components : 'HDA:11d4198b,104381f6,00100300' Controls : 46 Simple ctrls : 25 Simple mixer control 'Master',0 Capabilities: pvolume pvolume-joined pswitch pswitch-joined penum Playback channels: Mono Limits: Playback 0 - 39 Mono: Playback 39 [100%] [0.00dB] [on] Simple mixer control 'Headphone',0 Capabilities: pswitch penum Playback channels: Front Left - Front Right Mono: Front Left: Playback [on] Front Right: Playback [on] Simple mixer control 'PCM',0 Capabilities: pvolume penum Playback channels: Front Left - Front Right Limits: Playback 0 - 255 Mono: Front Left: Playback 255 [100%] [0.00dB] Front Right: Playback 255 [100%] [0.00dB] Simple mixer control 'Front',0 Capabilities: pvolume pswitch penum Playback channels: Front Left - Front Right Limits: Playback 0 - 39 Mono: Front Left: Playback 39 [100%] [0.00dB] [on] Front Right: Playback 39 [100%] [0.00dB] [on] Simple mixer control 'Front Mic',0 Capabilities: pvolume pswitch penum Playback channels: Front Left - Front Right Limits: Playback 0 - 31 Mono: Front Left: Playback 25 [81%] [3.00dB] [on] Front Right: Playback 25 [81%] [3.00dB] [on] Simple mixer control 'Front Mic Boost',0 Capabilities: volume penum Playback channels: Front Left - Front Right Capture channels: Front Left - Front Right Limits: 0 - 3 Front Left: 0 [0%] Front Right: 0 [0%] Simple mixer control 'Surround',0 Capabilities: pvolume pswitch penum Playback channels: Front Left - Front Right Limits: Playback 0 - 39 Mono: Front Left: Playback 39 [100%] [0.00dB] [on] Front Right: Playback 39 [100%] [0.00dB] [on] Simple mixer control 'Center',0 Capabilities: pvolume pvolume-joined pswitch pswitch-joined penum Playback channels: Mono Limits: Playback 0 - 39 Mono: Playback 39 [100%] [0.00dB] [on] Simple mixer control 'LFE',0 Capabilities: pvolume pvolume-joined pswitch pswitch-joined penum Playback channels: Mono Limits: Playback 0 - 39 Mono: Playback 39 [100%] [0.00dB] [on] Simple mixer control 'Side',0 Capabilities: pvolume pswitch penum Playback channels: Front Left - Front Right Limits: Playback 0 - 39 Mono: Front Left: Playback 39 [100%] [0.00dB] [on] Front Right: Playback 39 [100%] [0.00dB] [on] Simple mixer control 'Line',0 Capabilities: pvolume pswitch penum Playback channels: Front Left - Front Right Limits: Playback 0 - 31 Mono: Front Left: Playback 31 [100%] [12.00dB] [on] Front Right: Playback 31 [100%] [12.00dB] [on] Simple mixer control 'CD',0 Capabilities: pvolume pswitch penum Playback channels: Front Left - Front Right Limits: Playback 0 - 31 Mono: Front Left: Playback 30 [97%] [10.50dB] [on] Front Right: Playback 30 [97%] [10.50dB] [on] Simple mixer control 'Mic',0 Capabilities: pvolume pswitch penum Playback channels: Front Left - Front Right Limits: Playback 0 - 31 Mono: Front Left: Playback 29 [94%] [9.00dB] [on] Front Right: Playback 29 [94%] [9.00dB] [on] Simple mixer control 'Mic Boost',0 Capabilities: volume penum Playback channels: Front Left - Front Right Capture channels: Front Left - Front Right Limits: 0 - 3 Front Left: 3 [100%] Front Right: 3 [100%] Simple mixer control 'IEC958',0 Capabilities: pvolume cvolume pswitch pswitch-joined cswitch cswitch-joined penum Playback channels: Front Left - Front Right Capture channels: Front Left - Front Right Limits: Playback 0 - 39 Capture 0 - 31 Front Left: Playback 0 [0%] [-58.50dB] [on] Capture 23 [74%] [0.00dB] [off] Front Right: Playback 0 [0%] [-58.50dB] [on] Capture 23 [74%] [0.00dB] [off] Simple mixer control 'IEC958 Default PCM',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Simple mixer control 'IEC958 Playback Source',0 Capabilities: enum Items: 'PCM' 'ADC1' 'ADC2' 'ADC3' Item0: 'PCM' Simple mixer control 'Mono',0 Capabilities: pswitch penum Playback channels: Front Left - Front Right Mono: Front Left: Playback [on] Front Right: Playback [on] Simple mixer control 'Capture',0 Capabilities: cvolume cswitch penum Capture channels: Front Left - Front Right Limits: Capture 0 - 54 Front Left: Capture 53 [98%] [21.00dB] [on] Front Right: Capture 53 [98%] [21.00dB] [on] Simple mixer control 'Capture',1 Capabilities: cvolume cswitch penum Capture channels: Front Left - Front Right Limits: Capture 0 - 54 Front Left: Capture 42 [78%] [4.50dB] [off] Front Right: Capture 42 [78%] [4.50dB] [off] Simple mixer control 'Capture',2 Capabilities: cvolume cswitch penum Capture channels: Front Left - Front Right Limits: Capture 0 - 54 Front Left: Capture 43 [80%] [6.00dB] [off] Front Right: Capture 43 [80%] [6.00dB] [off] Simple mixer control 'Analog Mix',0 Capabilities: pvolume pswitch penum Playback channels: Front Left - Front Right Limits: Playback 0 - 31 Mono: Front Left: Playback 25 [81%] [-9.00dB] [on] Front Right: Playback 25 [81%] [-9.00dB] [on] Simple mixer control 'Input Source',0 Capabilities: cenum Items: 'Front Mic' 'Line' 'Mic' 'CD' 'Mix' Item0: 'Front Mic' Simple mixer control 'Input Source',1 Capabilities: cenum Items: 'Front Mic' 'Line' 'Mic' 'CD' 'Mix' Item0: 'Front Mic' Simple mixer control 'Input Source',2 Capabilities: cenum Items: 'Front Mic' 'Line' 'Mic' 'CD' 'Mix' Item0: 'Front Mic' !!Alsactl output !!------------- --startcollapse-- state.Q9000 { control.1 { comment.access 'read write' comment.type BOOLEAN comment.count 1 iface MIXER name 'Mic Capture Switch' value true } control.2 { comment.access 'read write' comment.type INTEGER comment.count 1 comment.range '0 - 3072' comment.dbmin 1800 comment.dbmax 3000 iface MIXER name 'Mic Capture Volume' value 141 } } state.Aureon51MkII { control.1 { comment.access 'read write' comment.type BOOLEAN comment.count 1 iface MIXER name 'Mic Playback Switch' value true } control.2 { comment.access 'read write' comment.type INTEGER comment.count 1 comment.range '0 - 255' comment.dbmin 0 comment.dbmax 4781 iface MIXER name 'Mic Playback Volume' value 42 } control.3 { comment.access 'read write' comment.type BOOLEAN comment.count 1 iface MIXER name 'Line Playback Switch' value false } control.4 { comment.access 'read write' comment.type INTEGER comment.count 2 comment.range '0 - 255' comment.dbmin 0 comment.dbmax 4781 iface MIXER name 'Line Playback Volume' value.0 191 value.1 191 } control.5 { comment.access 'read write' comment.type BOOLEAN comment.count 1 iface MIXER name 'Master Playback Switch' value true } control.6 { comment.access 'read write' comment.type INTEGER comment.count 1 comment.range '0 - 255' comment.dbmin -4787 comment.dbmax -6 iface MIXER name 'Master Playback Volume' value 241 } control.7 { comment.access 'read write' comment.type BOOLEAN comment.count 1 iface MIXER name 'Mic Capture Switch' value false } control.8 { comment.access 'read write' comment.type INTEGER comment.count 1 comment.range '0 - 128' comment.dbmin 0 comment.dbmax 2381 iface MIXER name 'Mic Capture Volume' value 12 } control.9 { comment.access 'read write' comment.type BOOLEAN comment.count 1 iface MIXER name 'Mic Capture' value false } control.10 { comment.access 'read write' comment.type BOOLEAN comment.count 1 iface MIXER name 'Line Capture Switch' value false } control.11 { comment.access 'read write' comment.type INTEGER comment.count 2 comment.range '0 - 128' comment.dbmin 0 comment.dbmax 2381 iface MIXER name 'Line Capture Volume' value.0 0 value.1 0 } control.12 { comment.access 'read write' comment.type BOOLEAN comment.count 1 iface MIXER name 'IEC958 In Capture Switch' value true } control.13 { comment.access 'read write' comment.type ENUMERATED comment.count 1 comment.item.0 Mic comment.item.1 Line comment.item.2 'IEC958 In' iface MIXER name 'Capture Source' value Mic } } state.NVidia { control.1 { comment.access 'read write' comment.type INTEGER comment.count 2 comment.range '0 - 39' comment.dbmin -5850 comment.dbmax 0 iface MIXER name 'Front Playback Volume' value.0 39 value.1 39 } control.2 { comment.access 'read write' comment.type INTEGER comment.count 2 comment.range '0 - 39' comment.dbmin -5850 comment.dbmax 0 iface MIXER name 'Surround Playback Volume' value.0 39 value.1 39 } control.3 { comment.access 'read write' comment.type INTEGER comment.count 1 comment.range '0 - 39' comment.dbmin -5850 comment.dbmax 0 iface MIXER name 'Center Playback Volume' value 39 } control.4 { comment.access 'read write' comment.type INTEGER comment.count 1 comment.range '0 - 39' comment.dbmin -5850 comment.dbmax 0 iface MIXER name 'LFE Playback Volume' value 39 } control.5 { comment.access 'read write' comment.type INTEGER comment.count 2 comment.range '0 - 39' comment.dbmin -5850 comment.dbmax 0 iface MIXER name 'Side Playback Volume' value.0 39 value.1 39 } control.6 { comment.access 'read write' comment.type BOOLEAN comment.count 2 iface MIXER name 'Front Playback Switch' value.0 true value.1 true } control.7 { comment.access 'read write' comment.type BOOLEAN comment.count 2 iface MIXER name 'Surround Playback Switch' value.0 true value.1 true } control.8 { comment.access 'read write' comment.type BOOLEAN comment.count 1 iface MIXER name 'Center Playback Switch' value true } control.9 { comment.access 'read write' comment.type BOOLEAN comment.count 1 iface MIXER name 'LFE Playback Switch' value true } control.10 { comment.access 'read write' comment.type BOOLEAN comment.count 2 iface MIXER name 'Side Playback Switch' value.0 true value.1 true } control.11 { comment.access 'read write' comment.type BOOLEAN comment.count 2 iface MIXER name 'Headphone Playback Switch' value.0 true value.1 true } control.12 { comment.access 'read write' comment.type BOOLEAN comment.count 2 iface MIXER name 'Mono Playback Switch' value.0 true value.1 true } control.13 { comment.access 'read write' comment.type INTEGER comment.count 2 comment.range '0 - 31' comment.dbmin -3450 comment.dbmax 1200 iface MIXER name 'CD Playback Volume' value.0 30 value.1 30 } control.14 { comment.access 'read write' comment.type BOOLEAN comment.count 2 iface MIXER name 'CD Playback Switch' value.0 true value.1 true } control.15 { comment.access 'read write' comment.type INTEGER comment.count 2 comment.range '0 - 31' comment.dbmin -3450 comment.dbmax 1200 iface MIXER name 'Front Mic Playback Volume' value.0 25 value.1 25 } control.16 { comment.access 'read write' comment.type BOOLEAN comment.count 2 iface MIXER name 'Front Mic Playback Switch' value.0 true value.1 true } control.17 { comment.access 'read write' comment.type INTEGER comment.count 2 comment.range '0 - 31' comment.dbmin -3450 comment.dbmax 1200 iface MIXER name 'Line Playback Volume' value.0 31 value.1 31 } control.18 { comment.access 'read write' comment.type BOOLEAN comment.count 2 iface MIXER name 'Line Playback Switch' value.0 true value.1 true } control.19 { comment.access 'read write' comment.type INTEGER comment.count 2 comment.range '0 - 31' comment.dbmin -3450 comment.dbmax 1200 iface MIXER name 'Mic Playback Volume' value.0 29 value.1 29 } control.20 { comment.access 'read write' comment.type BOOLEAN comment.count 2 iface MIXER name 'Mic Playback Switch' value.0 true value.1 true } control.21 { comment.access 'read write' comment.type INTEGER comment.count 2 comment.range '0 - 31' comment.dbmin -4650 comment.dbmax 0 iface MIXER name 'Analog Mix Playback Volume' value.0 25 value.1 25 } control.22 { comment.access 'read write' comment.type BOOLEAN comment.count 2 iface MIXER name 'Analog Mix Playback Switch' value.0 true value.1 true } control.23 { comment.access 'read write' comment.type INTEGER comment.count 2 comment.range '0 - 3' comment.dbmin 0 comment.dbmax 3000 iface MIXER name 'Front Mic Boost' value.0 0 value.1 0 } control.24 { comment.access 'read write' comment.type INTEGER comment.count 2 comment.range '0 - 3' comment.dbmin 0 comment.dbmax 3000 iface MIXER name 'Mic Boost' value.0 3 value.1 3 } control.25 { comment.access 'read write' comment.type INTEGER comment.count 2 comment.range '0 - 54' comment.dbmin -5850 comment.dbmax 2250 iface MIXER name 'Capture Volume' value.0 53 value.1 53 } control.26 { comment.access 'read write' comment.type BOOLEAN comment.count 2 iface MIXER name 'Capture Switch' value.0 true value.1 true } control.27 { comment.access 'read write' comment.type INTEGER comment.count 2 comment.range '0 - 54' comment.dbmin -5850 comment.dbmax 2250 iface MIXER name 'Capture Volume' index 1 value.0 42 value.1 42 } control.28 { comment.access 'read write' comment.type BOOLEAN comment.count 2 iface MIXER name 'Capture Switch' index 1 value.0 false value.1 false } control.29 { comment.access 'read write' comment.type INTEGER comment.count 2 comment.range '0 - 54' comment.dbmin -5850 comment.dbmax 2250 iface MIXER name 'Capture Volume' index 2 value.0 43 value.1 43 } control.30 { comment.access 'read write' comment.type BOOLEAN comment.count 2 iface MIXER name 'Capture Switch' index 2 value.0 false value.1 false } control.31 { comment.access 'read write' comment.type ENUMERATED comment.count 1 comment.item.0 'Front Mic' comment.item.1 Line comment.item.2 Mic comment.item.3 CD comment.item.4 Mix iface MIXER name 'Input Source' value 'Front Mic' } control.32 { comment.access 'read write' comment.type ENUMERATED comment.count 1 comment.item.0 'Front Mic' comment.item.1 Line comment.item.2 Mic comment.item.3 CD comment.item.4 Mix iface MIXER name 'Input Source' index 1 value 'Front Mic' } control.33 { comment.access 'read write' comment.type ENUMERATED comment.count 1 comment.item.0 'Front Mic' comment.item.1 Line comment.item.2 Mic comment.item.3 CD comment.item.4 Mix iface MIXER name 'Input Source' index 2 value 'Front Mic' } control.34 { comment.access 'read write' comment.type INTEGER comment.count 2 comment.range '0 - 39' comment.dbmin -5850 comment.dbmax 0 iface MIXER name 'IEC958 Playback Volume' value.0 0 value.1 0 } control.35 { comment.access 'read write' comment.type ENUMERATED comment.count 1 comment.item.0 PCM comment.item.1 ADC1 comment.item.2 ADC2 comment.item.3 ADC3 iface MIXER name 'IEC958 Playback Source' value PCM } control.36 { comment.access 'read write' comment.type INTEGER comment.count 2 comment.range '0 - 31' comment.dbmin -3450 comment.dbmax 1200 iface MIXER name 'IEC958 Capture Volume' value.0 23 value.1 23 } control.37 { comment.access read comment.type IEC958 comment.count 1 iface MIXER name 'IEC958 Playback Con Mask' value '0fff000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000' } control.38 { comment.access read comment.type IEC958 comment.count 1 iface MIXER name 'IEC958 Playback Pro Mask' value '0f00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000' } control.39 { comment.access 'read write' comment.type IEC958 comment.count 1 iface MIXER name 'IEC958 Playback Default' value '0400000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000' } control.40 { comment.access 'read write' comment.type BOOLEAN comment.count 1 iface MIXER name 'IEC958 Playback Switch' value true } control.41 { comment.access 'read write' comment.type BOOLEAN comment.count 1 iface MIXER name 'IEC958 Default PCM Playback Switch' value true } control.42 { comment.access 'read write' comment.type BOOLEAN comment.count 1 iface MIXER name 'IEC958 Capture Switch' value false } control.43 { comment.access read comment.type IEC958 comment.count 1 iface MIXER name 'IEC958 Capture Default' value '0400000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000' } control.44 { comment.access 'read write' comment.type INTEGER comment.count 1 comment.range '0 - 39' comment.dbmin -5850 comment.dbmax 0 iface MIXER name 'Master Playback Volume' value 39 } control.45 { comment.access 'read write' comment.type BOOLEAN comment.count 1 iface MIXER name 'Master Playback Switch' value true } control.46 { comment.access 'read write user' comment.type INTEGER comment.count 2 comment.range '0 - 255' comment.tlv '0000000100000008ffffec1400000014' comment.dbmin -5100 comment.dbmax 0 iface MIXER name 'PCM Playback Volume' value.0 255 value.1 255 } } --endcollapse-- !!All Loaded Modules !!------------------ Module vboxnetadp vboxnetflt vboxdrv nvidia bluetooth hwmon_vid af_packet uinput snd_pcm_oss snd_mixer_oss snd_seq ipv6 fuse btrfs crc32c libcrc32c loop dm_mod i2c_dev snd_hda_codec_analog arc4 ecb rtl8187 snd_hda_intel mac80211 snd_hda_codec snd_usb_audio led_class snd_hwdep uvcvideo parport_pc cfg80211 snd_usb_lib ppdev kvm_amd videodev ohci1394 snd_pcm snd_rawmidi rfkill v4l1_compat usbhid snd_timer r8169 snd_seq_device v4l2_compat_ioctl32 eeprom_93cx6 hid kvm ieee1394 parport mii snd floppy pcspkr k8temp sg edac_core asus_atk0110 button soundcore snd_page_alloc i2c_nforce2 forcedeth i2c_core ohci_hcd rtc_cmos ehci_hcd rtc_core rtc_lib sd_mod crc_t10dif usbcore ext3 mbcache jbd edd jfs xfs exportfs fan ide_pci_generic ata_generic pata_acpi pata_amd ahci pata_jmicron sata_nv libata scsi_mod amd74xx ide_core thermal processor !!Sysfs Files !!----------- /sys/class/sound/hwC2D0/init_pin_configs: 0x11 0x02214130 0x12 0x01014010 0x13 0x511711f0 0x14 0x02a1912e 0x15 0x01813021 0x16 0x01011012 0x17 0x01a19020 0x18 0x99331122 0x1a 0x91f711f0 0x1b 0x0145f1f0 0x1c 0x41c5f1f0 0x24 0x01016011 0x25 0x01012014 /sys/class/sound/hwC2D0/driver_pin_configs: /sys/class/sound/hwC2D0/user_pin_configs: /sys/class/sound/hwC2D0/init_verbs: !!ALSA/HDA dmesg !!------------------ wlan0: direct probe to AP 00:1b:9e:82:66:27 timed out ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:708: cannot submit urb (err = -27) ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 wlan0: direct probe to AP 00:1b:9e:82:66:27 (try 1) -- kmemleak: 2 new suspected memory leaks (see /sys/kernel/debug/kmemleak) ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 kmemleak: 1 new suspected memory leaks (see /sys/kernel/debug/kmemleak) ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 php[689] general protection ip:7f630d9b4138 sp:3021837def99698f error:0 in ld-2.11.1.so[7f630d99e000+1f000] ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:708: cannot submit urb (err = -27) ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 php[30161] general protection ip:7fe2b4b0b138 sp:e439f331bc02c843 error:0 in ld-2.11.1.so[7fe2b4af5000+1f000] ^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: [Bug #15144] HDA Intel Audio hang on boot 2010-02-15 12:46 ` Sid Boyce @ 2010-02-15 12:53 ` Takashi Iwai 2010-02-15 13:51 ` Sid Boyce 0 siblings, 1 reply; 76+ messages in thread From: Takashi Iwai @ 2010-02-15 12:53 UTC (permalink / raw) To: sboyce; +Cc: Rafael J. Wysocki, Linux Kernel Mailing List At Mon, 15 Feb 2010 12:46:35 +0000, Sid Boyce wrote: > > On 15/02/10 07:12, yTakashi Iwai wrote: > > At Sun, 14 Feb 2010 20:29:01 +0000, > > Sid Boyce wrote: > >> > >> On 01/02/10 06:43, Takashi Iwai wrote: > >>> At Mon, 01 Feb 2010 02:01:21 +0000, > >>> Sid Boyce wrote: > >>>> > >>>> On 01/02/10 00:22, Rafael J. Wysocki wrote: > >>>>> This message has been generated automatically as a part of a report > >>>>> of recent regressions. > >>>>> > >>>>> The following bug entry is on the current list of known regressions > >>>>> from 2.6.32. Please verify if it still should be listed and let me know > >>>>> (either way). > >>>>> > >>>>> > >>>>> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15144 > >>>>> Subject : HDA Intel Audio hang on boot > >>>>> Submitter : Sid Boyce <sboyce@blueyonder.co.uk> > >>>>> Date : 2010-01-15 1:24 (17 days old) > >>>>> References : http://marc.info/?l=linux-kernel&m=126351866722507&w=4 > >>>>> > >>>>> > >>>>> > >>>> > >>>> Still not fixed in 2.6.33-rc6. Takashi wrote that the fix was scheduled > >>>> for 2.6.33-rc6, but it did not appear. > >>> > >>> It just slipped from rc6 due to my busy load. > >>> The pull request was sent yesterday. > >>> > >>> > >>> Takashi > >>> > >> > >> Up to 2.6.33-rc8 still needs the work around in > >> /etc/modprobe.d/50-sound.conf, so the kernel blacklist fix does not work. > > > > Check the kernel message. Don't you have a message like "hda_intel: > > msi for device 1043:829c set to 0"? Otherwise give alsa-info.sh > > again. > > > No mention of it - 2.6.33-rc8. > tindog:~ # dmesg|grep 1043 > tindog:~ # grep 1043 /var/log/boot.msg > tindog:~ # grep 1043 /var/log/messages > tindog:~ # > The patch seems to be addressing the wrong device, alsa-info.sh shows > it as > Subsystem: 1043:81f6 > Subsystem Id: 0x104381f6 > Components : 'HDA:11d4198b,104381f6,00100300' > > tindog:/usr/src/linux-2.6.33-rc8 # grep 1043 ./sound/pci/hda/hda_intel.c > SND_PCI_QUIRK(0x1043, 0x813d, "ASUS P5AD2", POS_FIX_LPIB), > SND_PCI_QUIRK(0x1043, 0x1262, "ASUS W5Fm", 0x103), > SND_PCI_QUIRK(0x1043, 0x81f2, "ASUS", 0), /* Athlon64 X2 + nvidia */ > SND_PCI_QUIRK(0x1043, 0x829c, "ASUS", 0), /* nvidia */ > > I shall change the 0x81f2 to 0x81f6 and test. Yes, please. And update the bugzilla with the correct alsa-info.sh output, too. > > But, essentially this is a problem of your mobo and Linux MSI > > handling, not exactly a driver issue, IMO... > > > I think you are correct, could be the motherboard or BIOS. I have tried > a number of BIOS versions with the same result. I am about to change to > a Asus Crosshair III motherboard in a few days when the memory arrives. > It also wouldn't boot if I have kgdb enabled in .config, I get a stream > of Traces with "Tainted". > > > I guess the problem will go away if you remove your another sound card > > on the PCI slot. Or maybe it'd work even by moving to another > > slot... > > > It's the on-board sound. Before the work around I had to disable it in > the BIOS and use the USB sound card. Hm, then I must I have checking really a different alsa-info.sh. thanks, Takashi ^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: [Bug #15144] HDA Intel Audio hang on boot 2010-02-15 12:53 ` Takashi Iwai @ 2010-02-15 13:51 ` Sid Boyce 2010-02-15 16:08 ` Takashi Iwai 0 siblings, 1 reply; 76+ messages in thread From: Sid Boyce @ 2010-02-15 13:51 UTC (permalink / raw) To: Takashi Iwai; +Cc: Rafael J. Wysocki, Linux Kernel Mailing List On 15/02/10 12:53, Takashi Iwai wrote: > At Mon, 15 Feb 2010 12:46:35 +0000, > Sid Boyce wrote: >> >> On 15/02/10 07:12, yTakashi Iwai wrote: >>> At Sun, 14 Feb 2010 20:29:01 +0000, >>> Sid Boyce wrote: >>>> >>>> On 01/02/10 06:43, Takashi Iwai wrote: >>>>> At Mon, 01 Feb 2010 02:01:21 +0000, >>>>> Sid Boyce wrote: >>>>>> >>>>>> On 01/02/10 00:22, Rafael J. Wysocki wrote: >>>>>>> This message has been generated automatically as a part of a report >>>>>>> of recent regressions. >>>>>>> >>>>>>> The following bug entry is on the current list of known regressions >>>>>>> from 2.6.32. Please verify if it still should be listed and let me know >>>>>>> (either way). >>>>>>> >>>>>>> >>>>>>> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15144 >>>>>>> Subject : HDA Intel Audio hang on boot >>>>>>> Submitter : Sid Boyce <sboyce@blueyonder.co.uk> >>>>>>> Date : 2010-01-15 1:24 (17 days old) >>>>>>> References : http://marc.info/?l=linux-kernel&m=126351866722507&w=4 >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> Still not fixed in 2.6.33-rc6. Takashi wrote that the fix was scheduled >>>>>> for 2.6.33-rc6, but it did not appear. >>>>> >>>>> It just slipped from rc6 due to my busy load. >>>>> The pull request was sent yesterday. >>>>> >>>>> >>>>> Takashi >>>>> >>>> >>>> Up to 2.6.33-rc8 still needs the work around in >>>> /etc/modprobe.d/50-sound.conf, so the kernel blacklist fix does not work. >>> >>> Check the kernel message. Don't you have a message like "hda_intel: >>> msi for device 1043:829c set to 0"? Otherwise give alsa-info.sh >>> again. >>> >> No mention of it - 2.6.33-rc8. >> tindog:~ # dmesg|grep 1043 >> tindog:~ # grep 1043 /var/log/boot.msg >> tindog:~ # grep 1043 /var/log/messages >> tindog:~ # >> The patch seems to be addressing the wrong device, alsa-info.sh shows >> it as >> Subsystem: 1043:81f6 >> Subsystem Id: 0x104381f6 >> Components : 'HDA:11d4198b,104381f6,00100300' >> >> tindog:/usr/src/linux-2.6.33-rc8 # grep 1043 ./sound/pci/hda/hda_intel.c >> SND_PCI_QUIRK(0x1043, 0x813d, "ASUS P5AD2", POS_FIX_LPIB), >> SND_PCI_QUIRK(0x1043, 0x1262, "ASUS W5Fm", 0x103), >> SND_PCI_QUIRK(0x1043, 0x81f2, "ASUS", 0), /* Athlon64 X2 + nvidia */ >> SND_PCI_QUIRK(0x1043, 0x829c, "ASUS", 0), /* nvidia */ >> >> I shall change the 0x81f2 to 0x81f6 and test. > > Yes, please. And update the bugzilla with the correct alsa-info.sh > output, too. > >>> But, essentially this is a problem of your mobo and Linux MSI >>> handling, not exactly a driver issue, IMO... >>> >> I think you are correct, could be the motherboard or BIOS. I have tried >> a number of BIOS versions with the same result. I am about to change to >> a Asus Crosshair III motherboard in a few days when the memory arrives. >> It also wouldn't boot if I have kgdb enabled in .config, I get a stream >> of Traces with "Tainted". >> >>> I guess the problem will go away if you remove your another sound card >>> on the PCI slot. Or maybe it'd work even by moving to another >>> slot... >>> >> It's the on-board sound. Before the work around I had to disable it in >> the BIOS and use the USB sound card. > > Hm, then I must I have checking really a different alsa-info.sh. > I went back and checked the first alsa-info.txt I sent. My mistake this end, using ssh into that box, used scp to copy it to this box and inadvertently provided the wrong alsa-info.txt which was the one (1043:829c) for this box where email lives. Sincere apologies for the mixup. > > thanks, > The change works, it should be "0x1043, 0x81f6" instead of 0x829c. > Takashi > Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks ^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: [Bug #15144] HDA Intel Audio hang on boot 2010-02-15 13:51 ` Sid Boyce @ 2010-02-15 16:08 ` Takashi Iwai 0 siblings, 0 replies; 76+ messages in thread From: Takashi Iwai @ 2010-02-15 16:08 UTC (permalink / raw) To: sboyce; +Cc: Rafael J. Wysocki, Linux Kernel Mailing List At Mon, 15 Feb 2010 13:51:26 +0000, Sid Boyce wrote: > > On 15/02/10 12:53, Takashi Iwai wrote: > > At Mon, 15 Feb 2010 12:46:35 +0000, > > Sid Boyce wrote: > >> > >> On 15/02/10 07:12, yTakashi Iwai wrote: > >>> At Sun, 14 Feb 2010 20:29:01 +0000, > >>> Sid Boyce wrote: > >>>> > >>>> On 01/02/10 06:43, Takashi Iwai wrote: > >>>>> At Mon, 01 Feb 2010 02:01:21 +0000, > >>>>> Sid Boyce wrote: > >>>>>> > >>>>>> On 01/02/10 00:22, Rafael J. Wysocki wrote: > >>>>>>> This message has been generated automatically as a part of a report > >>>>>>> of recent regressions. > >>>>>>> > >>>>>>> The following bug entry is on the current list of known regressions > >>>>>>> from 2.6.32. Please verify if it still should be listed and let me know > >>>>>>> (either way). > >>>>>>> > >>>>>>> > >>>>>>> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15144 > >>>>>>> Subject : HDA Intel Audio hang on boot > >>>>>>> Submitter : Sid Boyce <sboyce@blueyonder.co.uk> > >>>>>>> Date : 2010-01-15 1:24 (17 days old) > >>>>>>> References : http://marc.info/?l=linux-kernel&m=126351866722507&w=4 > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>> > >>>>>> Still not fixed in 2.6.33-rc6. Takashi wrote that the fix was scheduled > >>>>>> for 2.6.33-rc6, but it did not appear. > >>>>> > >>>>> It just slipped from rc6 due to my busy load. > >>>>> The pull request was sent yesterday. > >>>>> > >>>>> > >>>>> Takashi > >>>>> > >>>> > >>>> Up to 2.6.33-rc8 still needs the work around in > >>>> /etc/modprobe.d/50-sound.conf, so the kernel blacklist fix does not work. > >>> > >>> Check the kernel message. Don't you have a message like "hda_intel: > >>> msi for device 1043:829c set to 0"? Otherwise give alsa-info.sh > >>> again. > >>> > >> No mention of it - 2.6.33-rc8. > >> tindog:~ # dmesg|grep 1043 > >> tindog:~ # grep 1043 /var/log/boot.msg > >> tindog:~ # grep 1043 /var/log/messages > >> tindog:~ # > >> The patch seems to be addressing the wrong device, alsa-info.sh shows > >> it as > >> Subsystem: 1043:81f6 > >> Subsystem Id: 0x104381f6 > >> Components : 'HDA:11d4198b,104381f6,00100300' > >> > >> tindog:/usr/src/linux-2.6.33-rc8 # grep 1043 ./sound/pci/hda/hda_intel.c > >> SND_PCI_QUIRK(0x1043, 0x813d, "ASUS P5AD2", POS_FIX_LPIB), > >> SND_PCI_QUIRK(0x1043, 0x1262, "ASUS W5Fm", 0x103), > >> SND_PCI_QUIRK(0x1043, 0x81f2, "ASUS", 0), /* Athlon64 X2 + nvidia */ > >> SND_PCI_QUIRK(0x1043, 0x829c, "ASUS", 0), /* nvidia */ > >> > >> I shall change the 0x81f2 to 0x81f6 and test. > > > > Yes, please. And update the bugzilla with the correct alsa-info.sh > > output, too. > > > >>> But, essentially this is a problem of your mobo and Linux MSI > >>> handling, not exactly a driver issue, IMO... > >>> > >> I think you are correct, could be the motherboard or BIOS. I have tried > >> a number of BIOS versions with the same result. I am about to change to > >> a Asus Crosshair III motherboard in a few days when the memory arrives. > >> It also wouldn't boot if I have kgdb enabled in .config, I get a stream > >> of Traces with "Tainted". > >> > >>> I guess the problem will go away if you remove your another sound card > >>> on the PCI slot. Or maybe it'd work even by moving to another > >>> slot... > >>> > >> It's the on-board sound. Before the work around I had to disable it in > >> the BIOS and use the USB sound card. > > > > Hm, then I must I have checking really a different alsa-info.sh. > > > I went back and checked the first alsa-info.txt I sent. > > My mistake this end, using ssh into that box, used scp to copy it to > this box and inadvertently provided the wrong alsa-info.txt which was > the one (1043:829c) for this box where email lives. > Sincere apologies for the mixup. > > > > thanks, > > > The change works, it should be "0x1043, 0x81f6" instead of 0x829c. OK, thanks for checking. I updated the git repo and will send another pull request later. Takashi ^ permalink raw reply [flat|nested] 76+ messages in thread
* [Bug #15192] netperf ~50% regression with 2.6.33-rc1, bisect to 1b9508f 2010-02-01 0:18 2.6.33-rc6: Reported regressions from 2.6.32 Rafael J. Wysocki ` (18 preceding siblings ...) 2010-02-01 0:22 ` [Bug #15144] HDA Intel Audio hang on boot Rafael J. Wysocki @ 2010-02-01 0:22 ` Rafael J. Wysocki 2010-02-01 8:04 ` Mike Galbraith 2010-02-01 0:22 ` [Bug #15195] kernel BUG at include/net/netns/generic.h:41, pfkey_create+0x36/0x18b [af_key] Rafael J. Wysocki ` (5 subsequent siblings) 25 siblings, 1 reply; 76+ messages in thread From: Rafael J. Wysocki @ 2010-02-01 0:22 UTC (permalink / raw) To: Linux Kernel Mailing List Cc: Kernel Testers List, Ingo Molnar, Lin Ming, Mike Galbraith, Peter Zijlstra This message has been generated automatically as a part of a report of recent regressions. The following bug entry is on the current list of known regressions from 2.6.32. Please verify if it still should be listed and let me know (either way). Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15192 Subject : netperf ~50% regression with 2.6.33-rc1, bisect to 1b9508f Submitter : Lin Ming <ming.m.lin@intel.com> Date : 2010-01-25 10:03 (7 days old) First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1b9508f6831e10d53256825de8904caa22d1ca2c References : http://marc.info/?l=linux-kernel&m=126441481427331&w=4 Handled-By : Mike Galbraith <efault@gmx.de> Peter Zijlstra <peterz@infradead.org> ^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: [Bug #15192] netperf ~50% regression with 2.6.33-rc1, bisect to 1b9508f 2010-02-01 0:22 ` [Bug #15192] netperf ~50% regression with 2.6.33-rc1, bisect to 1b9508f Rafael J. Wysocki @ 2010-02-01 8:04 ` Mike Galbraith 2010-02-02 20:38 ` Rafael J. Wysocki 2010-02-20 7:52 ` Lin Ming 0 siblings, 2 replies; 76+ messages in thread From: Mike Galbraith @ 2010-02-01 8:04 UTC (permalink / raw) To: Rafael J. Wysocki Cc: Linux Kernel Mailing List, Kernel Testers List, Ingo Molnar, Lin Ming, Peter Zijlstra On Mon, 2010-02-01 at 01:22 +0100, Rafael J. Wysocki wrote: > This message has been generated automatically as a part of a report > of recent regressions. > > The following bug entry is on the current list of known regressions > from 2.6.32. Please verify if it still should be listed and let me know > (either way). Yes, it should remain open. We're currently waiting for some data from Lin Ming. The regression itself isn't making much sense.. a kernel with NEWIDLE disabled should show the same performance, but does not. -Mike ^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: [Bug #15192] netperf ~50% regression with 2.6.33-rc1, bisect to 1b9508f 2010-02-01 8:04 ` Mike Galbraith @ 2010-02-02 20:38 ` Rafael J. Wysocki 2010-02-20 7:52 ` Lin Ming 1 sibling, 0 replies; 76+ messages in thread From: Rafael J. Wysocki @ 2010-02-02 20:38 UTC (permalink / raw) To: Mike Galbraith Cc: Linux Kernel Mailing List, Kernel Testers List, Ingo Molnar, Lin Ming, Peter Zijlstra On Monday 01 February 2010, Mike Galbraith wrote: > On Mon, 2010-02-01 at 01:22 +0100, Rafael J. Wysocki wrote: > > This message has been generated automatically as a part of a report > > of recent regressions. > > > > The following bug entry is on the current list of known regressions > > from 2.6.32. Please verify if it still should be listed and let me know > > (either way). > > Yes, it should remain open. We're currently waiting for some data from > Lin Ming. The regression itself isn't making much sense.. a kernel with > NEWIDLE disabled should show the same performance, but does not. Well, thanks for the update. Rafael ^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: [Bug #15192] netperf ~50% regression with 2.6.33-rc1, bisect to 1b9508f 2010-02-01 8:04 ` Mike Galbraith 2010-02-02 20:38 ` Rafael J. Wysocki @ 2010-02-20 7:52 ` Lin Ming 2010-02-22 4:59 ` Mike Galbraith 1 sibling, 1 reply; 76+ messages in thread From: Lin Ming @ 2010-02-20 7:52 UTC (permalink / raw) To: Mike Galbraith Cc: Rafael J. Wysocki, Linux Kernel Mailing List, Kernel Testers List, Ingo Molnar, Peter Zijlstra, venkatesh.pallipadi On Mon, 2010-02-01 at 16:04 +0800, Mike Galbraith wrote: > On Mon, 2010-02-01 at 01:22 +0100, Rafael J. Wysocki wrote: > > This message has been generated automatically as a part of a report > > of recent regressions. > > > > The following bug entry is on the current list of known regressions > > from 2.6.32. Please verify if it still should be listed and let me know > > (either way). > > Yes, it should remain open. We're currently waiting for some data from > Lin Ming. The regression itself isn't making much sense.. a kernel with > NEWIDLE disabled should show the same performance, but does not. (sorry for late response, I'm just back from vacation) We finally located this to a bug in mwait based C-state entry. Venki's patch has fixed it. http://patchwork.kernel.org/patch/78544/ Venki, this is the original report, http://marc.info/?l=linux-kernel&m=126441481427331&w=4 Thanks, Lin Ming ^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: [Bug #15192] netperf ~50% regression with 2.6.33-rc1, bisect to 1b9508f 2010-02-20 7:52 ` Lin Ming @ 2010-02-22 4:59 ` Mike Galbraith 0 siblings, 0 replies; 76+ messages in thread From: Mike Galbraith @ 2010-02-22 4:59 UTC (permalink / raw) To: Lin Ming Cc: Rafael J. Wysocki, Linux Kernel Mailing List, Kernel Testers List, Ingo Molnar, Peter Zijlstra, venkatesh.pallipadi, Len Brown, ACPI Devel Maling List On Sat, 2010-02-20 at 15:52 +0800, Lin Ming wrote: > On Mon, 2010-02-01 at 16:04 +0800, Mike Galbraith wrote: > > On Mon, 2010-02-01 at 01:22 +0100, Rafael J. Wysocki wrote: > > > This message has been generated automatically as a part of a report > > > of recent regressions. > > > > > > The following bug entry is on the current list of known regressions > > > from 2.6.32. Please verify if it still should be listed and let me know > > > (either way). > > > > Yes, it should remain open. We're currently waiting for some data from > > Lin Ming. The regression itself isn't making much sense.. a kernel with > > NEWIDLE disabled should show the same performance, but does not. > > (sorry for late response, I'm just back from vacation) > > We finally located this to a bug in mwait based C-state entry. > Venki's patch has fixed it. > http://patchwork.kernel.org/patch/78544/ > > Venki, this is the original report, > http://marc.info/?l=linux-kernel&m=126441481427331&w=4 Excellent, mystery solved. (adds acpi) -Mike ^ permalink raw reply [flat|nested] 76+ messages in thread
* [Bug #15195] kernel BUG at include/net/netns/generic.h:41, pfkey_create+0x36/0x18b [af_key] 2010-02-01 0:18 2.6.33-rc6: Reported regressions from 2.6.32 Rafael J. Wysocki ` (19 preceding siblings ...) 2010-02-01 0:22 ` [Bug #15192] netperf ~50% regression with 2.6.33-rc1, bisect to 1b9508f Rafael J. Wysocki @ 2010-02-01 0:22 ` Rafael J. Wysocki 2010-02-01 0:22 ` [Bug #15199] sata_nv and no /dev files Rafael J. Wysocki ` (4 subsequent siblings) 25 siblings, 0 replies; 76+ messages in thread From: Rafael J. Wysocki @ 2010-02-01 0:22 UTC (permalink / raw) To: Linux Kernel Mailing List Cc: Kernel Testers List, Alexey Dobriyan, Luca Tettamanti This message has been generated automatically as a part of a report of recent regressions. The following bug entry is on the current list of known regressions from 2.6.32. Please verify if it still should be listed and let me know (either way). Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15195 Subject : kernel BUG at include/net/netns/generic.h:41, pfkey_create+0x36/0x18b [af_key] Submitter : Luca Tettamanti <kronos.it@gmail.com> Date : 2010-01-30 13:23 (2 days old) References : http://marc.info/?l=linux-netdev&m=126485785004775&w=4 Handled-By : Alexey Dobriyan <adobriyan@gmail.com> Patch : http://patchwork.kernel.org/patch/75891/ ^ permalink raw reply [flat|nested] 76+ messages in thread
* [Bug #15199] sata_nv and no /dev files 2010-02-01 0:18 2.6.33-rc6: Reported regressions from 2.6.32 Rafael J. Wysocki ` (20 preceding siblings ...) 2010-02-01 0:22 ` [Bug #15195] kernel BUG at include/net/netns/generic.h:41, pfkey_create+0x36/0x18b [af_key] Rafael J. Wysocki @ 2010-02-01 0:22 ` Rafael J. Wysocki 2010-02-01 0:22 ` [Bug #15200] NFS problems in 2.6.33-rc6: Unknown error 526 Rafael J. Wysocki ` (3 subsequent siblings) 25 siblings, 0 replies; 76+ messages in thread From: Rafael J. Wysocki @ 2010-02-01 0:22 UTC (permalink / raw) To: Linux Kernel Mailing List; +Cc: Kernel Testers List, Bartłomiej Zimoń This message has been generated automatically as a part of a report of recent regressions. The following bug entry is on the current list of known regressions from 2.6.32. Please verify if it still should be listed and let me know (either way). Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15199 Subject : sata_nv and no /dev files Submitter : Bartłomiej Zimoń <uzi18@o2.pl> Date : 2010-01-31 23:45 (1 days old) References : http://marc.info/?l=linux-kernel&m=126498153112488&w=4 ^ permalink raw reply [flat|nested] 76+ messages in thread
* [Bug #15200] NFS problems in 2.6.33-rc6: Unknown error 526 2010-02-01 0:18 2.6.33-rc6: Reported regressions from 2.6.32 Rafael J. Wysocki ` (21 preceding siblings ...) 2010-02-01 0:22 ` [Bug #15199] sata_nv and no /dev files Rafael J. Wysocki @ 2010-02-01 0:22 ` Rafael J. Wysocki 2010-02-01 0:22 ` [Bug #15198] Radeon KMS regression Rafael J. Wysocki ` (2 subsequent siblings) 25 siblings, 0 replies; 76+ messages in thread From: Rafael J. Wysocki @ 2010-02-01 0:22 UTC (permalink / raw) To: Linux Kernel Mailing List; +Cc: Kernel Testers List, J.A. Magallón This message has been generated automatically as a part of a report of recent regressions. The following bug entry is on the current list of known regressions from 2.6.32. Please verify if it still should be listed and let me know (either way). Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15200 Subject : NFS problems in 2.6.33-rc6: Unknown error 526 Submitter : J.A. Magallón <jamagallon@ono.com> Date : 2010-01-31 22:46 (1 days old) References : http://marc.info/?l=linux-kernel&m=126497800408928&w=4 ^ permalink raw reply [flat|nested] 76+ messages in thread
* [Bug #15198] Radeon KMS regression 2010-02-01 0:18 2.6.33-rc6: Reported regressions from 2.6.32 Rafael J. Wysocki ` (22 preceding siblings ...) 2010-02-01 0:22 ` [Bug #15200] NFS problems in 2.6.33-rc6: Unknown error 526 Rafael J. Wysocki @ 2010-02-01 0:22 ` Rafael J. Wysocki 2010-02-02 0:04 ` Kevin Winchester 2010-02-01 0:22 ` [Bug #15196] kmem_cache_create: duplicate cache ccid2_h Rafael J. Wysocki 2010-02-01 0:22 ` [Bug #15202] lockdep warning during elevator_switch Rafael J. Wysocki 25 siblings, 1 reply; 76+ messages in thread From: Rafael J. Wysocki @ 2010-02-01 0:22 UTC (permalink / raw) To: Linux Kernel Mailing List Cc: Kernel Testers List, FUJITA Tomonori, Ingo Molnar, Kevin Winchester This message has been generated automatically as a part of a report of recent regressions. The following bug entry is on the current list of known regressions from 2.6.32. Please verify if it still should be listed and let me know (either way). Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15198 Subject : Radeon KMS regression Submitter : Kevin Winchester <kjwinchester@gmail.com> Date : 2010-01-30 17:18 (2 days old) First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=42590a75019a50012f25a962246498dead428433 References : http://marc.info/?l=linux-kernel&m=126487191019612&w=4 Handled-By : FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp> Patch : http://patchwork.kernel.org/patch/75023/ ^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: [Bug #15198] Radeon KMS regression 2010-02-01 0:22 ` [Bug #15198] Radeon KMS regression Rafael J. Wysocki @ 2010-02-02 0:04 ` Kevin Winchester 2010-02-02 20:25 ` Rafael J. Wysocki 0 siblings, 1 reply; 76+ messages in thread From: Kevin Winchester @ 2010-02-02 0:04 UTC (permalink / raw) To: Rafael J. Wysocki Cc: Linux Kernel Mailing List, Kernel Testers List, FUJITA Tomonori, Ingo Molnar On Mon, 2010-02-01 at 01:22 +0100, Rafael J. Wysocki wrote: > This message has been generated automatically as a part of a report > of recent regressions. > > The following bug entry is on the current list of known regressions > from 2.6.32. Please verify if it still should be listed and let me know > (either way). > > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15198 > Subject : Radeon KMS regression > Submitter : Kevin Winchester <kjwinchester@gmail.com> > Date : 2010-01-30 17:18 (2 days old) > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=42590a75019a50012f25a962246498dead428433 > References : http://marc.info/?l=linux-kernel&m=126487191019612&w=4 > Handled-By : FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp> > Patch : http://patchwork.kernel.org/patch/75023/ > > This is fixed by the patch from FUJITA Tomonori - I just confirmed with my latest build of Linus' tree (which has the patch). Thanks, -- Kevin Winchester ^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: [Bug #15198] Radeon KMS regression 2010-02-02 0:04 ` Kevin Winchester @ 2010-02-02 20:25 ` Rafael J. Wysocki 0 siblings, 0 replies; 76+ messages in thread From: Rafael J. Wysocki @ 2010-02-02 20:25 UTC (permalink / raw) To: Kevin Winchester Cc: Linux Kernel Mailing List, Kernel Testers List, FUJITA Tomonori, Ingo Molnar On Tuesday 02 February 2010, Kevin Winchester wrote: > On Mon, 2010-02-01 at 01:22 +0100, Rafael J. Wysocki wrote: > > This message has been generated automatically as a part of a report > > of recent regressions. > > > > The following bug entry is on the current list of known regressions > > from 2.6.32. Please verify if it still should be listed and let me know > > (either way). > > > > > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15198 > > Subject : Radeon KMS regression > > Submitter : Kevin Winchester <kjwinchester@gmail.com> > > Date : 2010-01-30 17:18 (2 days old) > > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=42590a75019a50012f25a962246498dead428433 > > References : http://marc.info/?l=linux-kernel&m=126487191019612&w=4 > > Handled-By : FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp> > > Patch : http://patchwork.kernel.org/patch/75023/ > > > > > > This is fixed by the patch from FUJITA Tomonori - I just confirmed with > my latest build of Linus' tree (which has the patch). Thanks, already closed. Rafael ^ permalink raw reply [flat|nested] 76+ messages in thread
* [Bug #15196] kmem_cache_create: duplicate cache ccid2_h 2010-02-01 0:18 2.6.33-rc6: Reported regressions from 2.6.32 Rafael J. Wysocki ` (23 preceding siblings ...) 2010-02-01 0:22 ` [Bug #15198] Radeon KMS regression Rafael J. Wysocki @ 2010-02-01 0:22 ` Rafael J. Wysocki 2010-02-01 3:30 ` Xiaotian Feng 2010-02-01 0:22 ` [Bug #15202] lockdep warning during elevator_switch Rafael J. Wysocki 25 siblings, 1 reply; 76+ messages in thread From: Rafael J. Wysocki @ 2010-02-01 0:22 UTC (permalink / raw) To: Linux Kernel Mailing List; +Cc: Kernel Testers List, Heinz Diehl This message has been generated automatically as a part of a report of recent regressions. The following bug entry is on the current list of known regressions from 2.6.32. Please verify if it still should be listed and let me know (either way). Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15196 Subject : kmem_cache_create: duplicate cache ccid2_h Submitter : Heinz Diehl <htd@fancy-poultry.org> Date : 2010-01-30 18:33 (2 days old) References : http://marc.info/?l=linux-kernel&m=126487640324942&w=4 ^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: [Bug #15196] kmem_cache_create: duplicate cache ccid2_h 2010-02-01 0:22 ` [Bug #15196] kmem_cache_create: duplicate cache ccid2_h Rafael J. Wysocki @ 2010-02-01 3:30 ` Xiaotian Feng 2010-02-01 7:20 ` David Miller 2010-02-01 15:06 ` Heinz Diehl 0 siblings, 2 replies; 76+ messages in thread From: Xiaotian Feng @ 2010-02-01 3:30 UTC (permalink / raw) To: Rafael J. Wysocki, htd Cc: Linux Kernel Mailing List, Kernel Testers List, nhorman On Mon, Feb 1, 2010 at 8:22 AM, Rafael J. Wysocki <rjw@sisk.pl> wrote: > This message has been generated automatically as a part of a report > of recent regressions. > > The following bug entry is on the current list of known regressions > from 2.6.32. Please verify if it still should be listed and let me know > (either way). > > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15196 > Subject : kmem_cache_create: duplicate cache ccid2_h > Submitter : Heinz Diehl <htd@fancy-poultry.org> > Date : 2010-01-30 18:33 (2 days old) > References : http://marc.info/?l=linux-kernel&m=126487640324942&w=4 Cced Neil, I think this one is introduced by commit de4ef86cfce60d2250111f34f8a084e769f23b16, passing char *slab_name_fmt as function parameter, but vsnprintf is using sizeof(slab_name_fmt), which is 8 (or 4 in 32bit kernel) instead of 32 as old version. Does following patch resolve this bug, Heinz? diff --git a/net/dccp/ccid.c b/net/dccp/ccid.c index 57dfb9c..6e52879 100644 --- a/net/dccp/ccid.c +++ b/net/dccp/ccid.c @@ -77,13 +77,14 @@ int ccid_getsockopt_builtin_ccids(struct sock *sk, int len, return err; } -static struct kmem_cache *ccid_kmem_cache_create(int obj_size, char *slab_name_fmt, const char *fmt,...) +static struct kmem_cache *ccid_kmem_cache_create(int obj_size, char *slab_name_fmt, + int length,const char *fmt,...) { struct kmem_cache *slab; va_list args; va_start(args, fmt); - vsnprintf(slab_name_fmt, sizeof(slab_name_fmt), fmt, args); + vsnprintf(slab_name_fmt, length, fmt, args); va_end(args); slab = kmem_cache_create(slab_name_fmt, sizeof(struct ccid) + obj_size, 0, @@ -104,6 +105,7 @@ static int ccid_activate(struct ccid_operations *ccid_ops) ccid_ops->ccid_hc_rx_slab = ccid_kmem_cache_create(ccid_ops->ccid_hc_rx_obj_size, ccid_ops->ccid_hc_rx_slab_name, + sizeof(ccid_ops->ccid_hc_rx_slab_name), "ccid%u_hc_rx_sock", ccid_ops->ccid_id); if (ccid_ops->ccid_hc_rx_slab == NULL) @@ -112,6 +114,7 @@ static int ccid_activate(struct ccid_operations *ccid_ops) ccid_ops->ccid_hc_tx_slab = ccid_kmem_cache_create(ccid_ops->ccid_hc_tx_obj_size, ccid_ops->ccid_hc_tx_slab_name, + sizeof(ccid_ops->ccid_hc_tx_slab_name), "ccid%u_hc_tx_sock", ccid_ops->ccid_id); if (ccid_ops->ccid_hc_tx_slab == NULL) > > > -- > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > ^ permalink raw reply related [flat|nested] 76+ messages in thread
* Re: [Bug #15196] kmem_cache_create: duplicate cache ccid2_h 2010-02-01 3:30 ` Xiaotian Feng @ 2010-02-01 7:20 ` David Miller 2010-02-01 11:55 ` Neil Horman 2010-02-01 15:06 ` Heinz Diehl 1 sibling, 1 reply; 76+ messages in thread From: David Miller @ 2010-02-01 7:20 UTC (permalink / raw) To: xtfeng; +Cc: rjw, htd, linux-kernel, kernel-testers, nhorman From: Xiaotian Feng <xtfeng@gmail.com> Date: Mon, 1 Feb 2010 11:30:02 +0800 > On Mon, Feb 1, 2010 at 8:22 AM, Rafael J. Wysocki <rjw@sisk.pl> wrote: >> This message has been generated automatically as a part of a report >> of recent regressions. >> >> The following bug entry is on the current list of known regressions >> from 2.6.32. Please verify if it still should be listed and let me know >> (either way). >> >> >> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15196 >> Subject : kmem_cache_create: duplicate cache ccid2_h >> Submitter : Heinz Diehl <htd@fancy-poultry.org> >> Date : 2010-01-30 18:33 (2 days old) >> References : http://marc.info/?l=linux-kernel&m=126487640324942&w=4 > > Cced Neil, > > I think this one is introduced by commit > de4ef86cfce60d2250111f34f8a084e769f23b16, > passing char *slab_name_fmt as function parameter, but vsnprintf is > using sizeof(slab_name_fmt), > which is 8 (or 4 in 32bit kernel) instead of 32 as old version. > > Does following patch resolve this bug, Heinz? There seems to be even more to this than that. Neils patch seems to need completely reverting. See the patch set posted by Gerrit Renker: http://marc.info/?l=linux-netdev&m=126500585823775&w=2 http://marc.info/?l=linux-netdev&m=126500591923880&w=2 ^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: [Bug #15196] kmem_cache_create: duplicate cache ccid2_h 2010-02-01 7:20 ` David Miller @ 2010-02-01 11:55 ` Neil Horman 2010-02-01 12:49 ` David Miller 0 siblings, 1 reply; 76+ messages in thread From: Neil Horman @ 2010-02-01 11:55 UTC (permalink / raw) To: David Miller; +Cc: xtfeng, rjw, htd, linux-kernel, kernel-testers On Sun, Jan 31, 2010 at 11:20:50PM -0800, David Miller wrote: > From: Xiaotian Feng <xtfeng@gmail.com> > Date: Mon, 1 Feb 2010 11:30:02 +0800 > > > On Mon, Feb 1, 2010 at 8:22 AM, Rafael J. Wysocki <rjw@sisk.pl> wrote: > >> This message has been generated automatically as a part of a report > >> of recent regressions. > >> > >> The following bug entry is on the current list of known regressions > >> from 2.6.32. Please verify if it still should be listed and let me know > >> (either way). > >> > >> > >> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15196 > >> Subject : kmem_cache_create: duplicate cache ccid2_h > >> Submitter : Heinz Diehl <htd@fancy-poultry.org> > >> Date : 2010-01-30 18:33 (2 days old) > >> References : http://marc.info/?l=linux-kernel&m=126487640324942&w=4 > > > > Cced Neil, > > > > I think this one is introduced by commit > > de4ef86cfce60d2250111f34f8a084e769f23b16, > > passing char *slab_name_fmt as function parameter, but vsnprintf is > > using sizeof(slab_name_fmt), > > which is 8 (or 4 in 32bit kernel) instead of 32 as old version. > > > > Does following patch resolve this bug, Heinz? > > There seems to be even more to this than that. Neils > patch seems to need completely reverting. > > See the patch set posted by Gerrit Renker: > > http://marc.info/?l=linux-netdev&m=126500585823775&w=2 > http://marc.info/?l=linux-netdev&m=126500591923880&w=2 > Dave, some of this doesn't make the least bit of sense to me. I get the sizeof error, thats clear (and I apologize, I should have seen that), but Gerrits revert of the dccp_probe changes is non-sensical. I'm not sure I even follow the comments: >Previously (during about 4 years of this module's history) there had never >been a problem with the 'silent dependency' that the commit tried to fix: >this dependency is deliberate and required, since dccp_probe performs probing >of dccp connections and hence needs to know about dccp internals. He claims this dependency is deliberate and requires, to which I agree, but he would seem to fix that by making the dccp_probe module error out in the event that dccp wasn't loaded. Why bother with that? Neil ^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: [Bug #15196] kmem_cache_create: duplicate cache ccid2_h 2010-02-01 11:55 ` Neil Horman @ 2010-02-01 12:49 ` David Miller 2010-02-01 13:01 ` Neil Horman 0 siblings, 1 reply; 76+ messages in thread From: David Miller @ 2010-02-01 12:49 UTC (permalink / raw) To: nhorman; +Cc: xtfeng, rjw, htd, linux-kernel, kernel-testers From: Neil Horman <nhorman@tuxdriver.com> Date: Mon, 1 Feb 2010 06:55:18 -0500 > He claims this dependency is deliberate and requires, to which I agree, but he > would seem to fix that by making the dccp_probe module error out in the event > that dccp wasn't loaded. Why bother with that? Neil, please get into the thread Gerrit started so he can see your questions and responses too. I already chided him for not CC:'ing you in the first place, guys stop hiding from eachother :-) ^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: [Bug #15196] kmem_cache_create: duplicate cache ccid2_h 2010-02-01 12:49 ` David Miller @ 2010-02-01 13:01 ` Neil Horman 0 siblings, 0 replies; 76+ messages in thread From: Neil Horman @ 2010-02-01 13:01 UTC (permalink / raw) To: David Miller; +Cc: xtfeng, rjw, htd, linux-kernel, kernel-testers On Mon, Feb 01, 2010 at 04:49:11AM -0800, David Miller wrote: > From: Neil Horman <nhorman@tuxdriver.com> > Date: Mon, 1 Feb 2010 06:55:18 -0500 > > > He claims this dependency is deliberate and requires, to which I agree, but he > > would seem to fix that by making the dccp_probe module error out in the event > > that dccp wasn't loaded. Why bother with that? > > Neil, please get into the thread Gerrit started so he can see your > questions and responses too. > > I already chided him for not CC:'ing you in the first place, guys > stop hiding from eachother :-) > I already posted to both of his posts (about 45 minutes ago). I think vger is being slow (whoever runs that system should really tune it up ;) ) Neil ^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: [Bug #15196] kmem_cache_create: duplicate cache ccid2_h 2010-02-01 3:30 ` Xiaotian Feng 2010-02-01 7:20 ` David Miller @ 2010-02-01 15:06 ` Heinz Diehl 2010-02-07 10:54 ` Heinz Diehl 1 sibling, 1 reply; 76+ messages in thread From: Heinz Diehl @ 2010-02-01 15:06 UTC (permalink / raw) To: Xiaotian Feng Cc: Rafael J. Wysocki, Linux Kernel Mailing List, Kernel Testers List, nhorman, davem On 01.02.2010, Xiaotian Feng wrote: > Does following patch resolve this bug, Heinz? [....] The patch was completely malformed, don't know what happened on the way, but I applied it by hand. Yes, it fixes the problem for me. Thanks, Heinz. ^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: [Bug #15196] kmem_cache_create: duplicate cache ccid2_h 2010-02-01 15:06 ` Heinz Diehl @ 2010-02-07 10:54 ` Heinz Diehl 2010-02-07 11:42 ` Rafael J. Wysocki 0 siblings, 1 reply; 76+ messages in thread From: Heinz Diehl @ 2010-02-07 10:54 UTC (permalink / raw) To: Xiaotian Feng Cc: Rafael J. Wysocki, Linux Kernel Mailing List, Kernel Testers List, nhorman, davem On 01.02.2010, Heinz Diehl wrote: [....] Quoting myself here... > The patch was completely malformed, don't know what happened on the way, > but I applied it by hand. Yes, it fixes the problem for me. Xiaotiangs patch quoted in the thread listed here (coming via kernel.org's bugtracker) http://patchwork.kernel.org/patch/76023/ is missing some lines, and the patch attached at the end of the thread is incomplete and malformed, as reported earlier. I guess this is how it should have looked like (please correct me if I'm wrong): --- /a/ccid.c 2010-02-06 23:17:12.000000000 +0100 +++ /b/ccid.c 2010-02-07 09:50:40.000000000 +0100 @@ -77,13 +77,13 @@ return err; } -static struct kmem_cache *ccid_kmem_cache_create(int obj_size, char *slab_name_fmt, const char *fmt,...) +static struct kmem_cache *ccid_kmem_cache_create(int obj_size, char *slab_name_fmt, int length, const char *fmt,...) { struct kmem_cache *slab; va_list args; va_start(args, fmt); - vsnprintf(slab_name_fmt, sizeof(slab_name_fmt), fmt, args); + vsnprintf(slab_name_fmt, length, fmt, args); va_end(args); slab = kmem_cache_create(slab_name_fmt, sizeof(struct ccid) + obj_size, 0, @@ -104,6 +104,7 @@ ccid_ops->ccid_hc_rx_slab = ccid_kmem_cache_create(ccid_ops->ccid_hc_rx_obj_size, ccid_ops->ccid_hc_rx_slab_name, + sizeof(ccid_ops->ccid_hc_rx_slab_name), "ccid%u_hc_rx_sock", ccid_ops->ccid_id); if (ccid_ops->ccid_hc_rx_slab == NULL) @@ -112,6 +113,7 @@ ccid_ops->ccid_hc_tx_slab = ccid_kmem_cache_create(ccid_ops->ccid_hc_tx_obj_size, ccid_ops->ccid_hc_tx_slab_name, + sizeof(ccid_ops->ccid_hc_tx_slab_name), "ccid%u_hc_tx_sock", ccid_ops->ccid_id); if (ccid_ops->ccid_hc_tx_slab == NULL) ^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: [Bug #15196] kmem_cache_create: duplicate cache ccid2_h 2010-02-07 10:54 ` Heinz Diehl @ 2010-02-07 11:42 ` Rafael J. Wysocki 0 siblings, 0 replies; 76+ messages in thread From: Rafael J. Wysocki @ 2010-02-07 11:42 UTC (permalink / raw) To: Heinz Diehl Cc: Xiaotian Feng, Linux Kernel Mailing List, Kernel Testers List, nhorman, davem On Sunday 07 February 2010, Heinz Diehl wrote: > On 01.02.2010, Heinz Diehl wrote: > > [....] > > Quoting myself here... > > > The patch was completely malformed, don't know what happened on the way, > > but I applied it by hand. Yes, it fixes the problem for me. > > Xiaotiangs patch quoted in the thread listed here (coming via kernel.org's > bugtracker) > > http://patchwork.kernel.org/patch/76023/ > > is missing some lines, and the patch attached at the end of the > thread is incomplete and malformed, as reported earlier. I guess this is > how it should have looked like (please correct me if I'm wrong): Thanks, I updated the bug entry with a link to your patch below. > --- /a/ccid.c 2010-02-06 23:17:12.000000000 +0100 > +++ /b/ccid.c 2010-02-07 09:50:40.000000000 +0100 > @@ -77,13 +77,13 @@ > return err; > } > > -static struct kmem_cache *ccid_kmem_cache_create(int obj_size, char *slab_name_fmt, const char *fmt,...) > +static struct kmem_cache *ccid_kmem_cache_create(int obj_size, char *slab_name_fmt, int length, const char *fmt,...) > { > struct kmem_cache *slab; > va_list args; > > va_start(args, fmt); > - vsnprintf(slab_name_fmt, sizeof(slab_name_fmt), fmt, args); > + vsnprintf(slab_name_fmt, length, fmt, args); > va_end(args); > > slab = kmem_cache_create(slab_name_fmt, sizeof(struct ccid) + obj_size, 0, > @@ -104,6 +104,7 @@ > ccid_ops->ccid_hc_rx_slab = > ccid_kmem_cache_create(ccid_ops->ccid_hc_rx_obj_size, > ccid_ops->ccid_hc_rx_slab_name, > + sizeof(ccid_ops->ccid_hc_rx_slab_name), > "ccid%u_hc_rx_sock", > ccid_ops->ccid_id); > if (ccid_ops->ccid_hc_rx_slab == NULL) > @@ -112,6 +113,7 @@ > ccid_ops->ccid_hc_tx_slab = > ccid_kmem_cache_create(ccid_ops->ccid_hc_tx_obj_size, > ccid_ops->ccid_hc_tx_slab_name, > + sizeof(ccid_ops->ccid_hc_tx_slab_name), > "ccid%u_hc_tx_sock", > ccid_ops->ccid_id); > if (ccid_ops->ccid_hc_tx_slab == NULL) > Rafael ^ permalink raw reply [flat|nested] 76+ messages in thread
* [Bug #15202] lockdep warning during elevator_switch 2010-02-01 0:18 2.6.33-rc6: Reported regressions from 2.6.32 Rafael J. Wysocki ` (24 preceding siblings ...) 2010-02-01 0:22 ` [Bug #15196] kmem_cache_create: duplicate cache ccid2_h Rafael J. Wysocki @ 2010-02-01 0:22 ` Rafael J. Wysocki 25 siblings, 0 replies; 76+ messages in thread From: Rafael J. Wysocki @ 2010-02-01 0:22 UTC (permalink / raw) To: Linux Kernel Mailing List; +Cc: Kernel Testers List, Hugh Dickins This message has been generated automatically as a part of a report of recent regressions. The following bug entry is on the current list of known regressions from 2.6.32. Please verify if it still should be listed and let me know (either way). Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15202 Subject : lockdep warning during elevator_switch Submitter : Hugh Dickins <hugh.dickins@tiscali.co.uk> Date : 2010-01-31 23:55 (1 days old) References : http://marc.info/?l=linux-kernel&m=126498212613051&w=4 ^ permalink raw reply [flat|nested] 76+ messages in thread
end of thread, other threads:[~2010-02-22 4:59 UTC | newest] Thread overview: 76+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2010-02-01 0:18 2.6.33-rc6: Reported regressions from 2.6.32 Rafael J. Wysocki 2010-02-01 0:19 ` [Bug #14791] Something has been broken in the network stack this week Rafael J. Wysocki 2010-02-01 0:46 ` Ben Hutchings 2010-02-01 0:22 ` [Bug #14937] WARNING: at kernel/lockdep.c:2830 Rafael J. Wysocki 2010-02-01 0:22 ` [Bug #14792] Misdetection of the TV output Rafael J. Wysocki 2010-02-01 0:22 ` [Bug #15036] soft lockup in dmesg after suspend/resume Rafael J. Wysocki 2010-02-01 0:22 ` [Bug #14950] tbench regression with 2.6.33-rc1 Rafael J. Wysocki 2010-02-01 7:57 ` Mike Galbraith 2010-02-02 20:45 ` Rafael J. Wysocki 2010-02-01 0:22 ` [Bug #14949] drm_vm.c:drm_mmap: possible circular locking dependency detected Rafael J. Wysocki 2010-02-01 18:01 ` Borislav Petkov 2010-02-02 20:46 ` Rafael J. Wysocki 2010-02-02 20:58 ` Borislav Petkov 2010-02-02 21:12 ` Rafael J. Wysocki 2010-02-03 2:18 ` Greg KH 2010-02-01 0:22 ` [Bug #15039] leds_alix2: can't allocate I/O for GPIO Rafael J. Wysocki 2010-02-01 0:22 ` [Bug #14999] possible circular locking dependency detected in rfkill at suspend Rafael J. Wysocki 2010-02-01 0:22 ` [Bug #15025] Oops in ext4 driver Rafael J. Wysocki 2010-02-01 0:22 ` [Bug #15076] System panic under load with clockevents_program_event Rafael J. Wysocki 2010-02-01 7:15 ` okias 2010-02-02 20:44 ` Rafael J. Wysocki 2010-02-01 0:22 ` [Bug #15043] Display goes off with i915.powersave=1 after suspend-resume Rafael J. Wysocki 2010-02-04 20:08 ` Soeren Sonnenburg 2010-02-04 20:42 ` Rafael J. Wysocki 2010-02-05 19:29 ` Jesse Barnes 2010-02-06 5:11 ` Soeren Sonnenburg 2010-02-06 5:53 ` Soeren Sonnenburg 2010-02-01 0:22 ` [Bug #15114] X.org hang with [drm:i915_gem_do_execbuffer] *ERROR* in dmesg Rafael J. Wysocki 2010-02-01 0:22 ` [Bug #15119] iwl_bg_scan_completed: WARN on scan complete Rafael J. Wysocki 2010-02-01 0:22 ` [Bug #15124] PCI host bridge windows ignored (works with pci=use_crs) Rafael J. Wysocki 2010-02-01 5:40 ` Yinghai Lu 2010-02-02 20:42 ` Rafael J. Wysocki 2010-02-02 20:50 ` Jeff Garrett 2010-02-02 21:13 ` Rafael J. Wysocki 2010-02-02 20:55 ` Bjorn Helgaas 2010-02-02 21:15 ` Rafael J. Wysocki 2010-02-01 0:22 ` [Bug #15139] e1000: transmit queue 0 timed out Rafael J. Wysocki 2010-02-01 0:22 ` [Bug #15125] hung task - jbd2/dm-1-8 (during raid rebuild) Rafael J. Wysocki 2010-02-01 0:42 ` Michael Breuer 2010-02-01 17:39 ` Michael Breuer 2010-02-02 20:42 ` Rafael J. Wysocki 2010-02-01 0:22 ` [Bug #15138] evdev regression on macbook Rafael J. Wysocki 2010-02-01 0:22 ` [Bug #15142] "INFO: possible circular locking dependency detected" Rafael J. Wysocki 2010-02-01 0:22 ` [Bug #15144] HDA Intel Audio hang on boot Rafael J. Wysocki 2010-02-01 2:01 ` Sid Boyce 2010-02-01 6:43 ` Takashi Iwai 2010-02-02 20:40 ` Rafael J. Wysocki 2010-02-03 2:37 ` Sid Boyce 2010-02-14 20:29 ` Sid Boyce 2010-02-14 21:50 ` Rafael J. Wysocki 2010-02-15 7:12 ` yTakashi Iwai 2010-02-15 12:46 ` Sid Boyce 2010-02-15 12:53 ` Takashi Iwai 2010-02-15 13:51 ` Sid Boyce 2010-02-15 16:08 ` Takashi Iwai 2010-02-01 0:22 ` [Bug #15192] netperf ~50% regression with 2.6.33-rc1, bisect to 1b9508f Rafael J. Wysocki 2010-02-01 8:04 ` Mike Galbraith 2010-02-02 20:38 ` Rafael J. Wysocki 2010-02-20 7:52 ` Lin Ming 2010-02-22 4:59 ` Mike Galbraith 2010-02-01 0:22 ` [Bug #15195] kernel BUG at include/net/netns/generic.h:41, pfkey_create+0x36/0x18b [af_key] Rafael J. Wysocki 2010-02-01 0:22 ` [Bug #15199] sata_nv and no /dev files Rafael J. Wysocki 2010-02-01 0:22 ` [Bug #15200] NFS problems in 2.6.33-rc6: Unknown error 526 Rafael J. Wysocki 2010-02-01 0:22 ` [Bug #15198] Radeon KMS regression Rafael J. Wysocki 2010-02-02 0:04 ` Kevin Winchester 2010-02-02 20:25 ` Rafael J. Wysocki 2010-02-01 0:22 ` [Bug #15196] kmem_cache_create: duplicate cache ccid2_h Rafael J. Wysocki 2010-02-01 3:30 ` Xiaotian Feng 2010-02-01 7:20 ` David Miller 2010-02-01 11:55 ` Neil Horman 2010-02-01 12:49 ` David Miller 2010-02-01 13:01 ` Neil Horman 2010-02-01 15:06 ` Heinz Diehl 2010-02-07 10:54 ` Heinz Diehl 2010-02-07 11:42 ` Rafael J. Wysocki 2010-02-01 0:22 ` [Bug #15202] lockdep warning during elevator_switch Rafael J. Wysocki
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).