Bug#658401: Atheros AR9285 Wi-Fi adapter not working on HP 630 notebook with Wheezy
Not at all. Please do. 2012.02.21. 8:54, Jonathan Nieder jrnie...@gmail.com ezt írta: Gábor Illés wrote: Dear Jonathan, Thank you for your response. Here is the lsmod output: Thanks. Do you mind if I forward this message to the bug log?
Bug#652475: linux-image-3.1.0-1-amd64: USB autosuspend goes crazy filling the log files
found 652475 3.2.4-1 thanks Hi there! On Fri, 30 Dec 2011 13:48:59 +0100, Ben Hutchings wrote: On Sat, 2011-12-17 at 17:17 +0100, Luca Capello wrote: Package: linux-2.6 Version: 3.1.1-1 The bug is still present in newer kernels, version updated. There is a problem somewhere with USB autosuspending on my ThinkPad X60. When enabled through powertop, the kernel splits out messages different times every seconds, thus filling the log files: [...] I don't know that there is anything wrong with the auto-suspend behaviour. Are your USB devices working correctly? Yes, there is no problem with them except with an external 100 GB S-ATA HD, but this happens when copying 5 GB files and also with other machines/OSs, thus I guess the fault is the double S-ATA/IDE converter which does not give enough power to the HD (everything is fine with HDs smaller in size). However, I should note that sometime there is a general problem I have already reported in the past, IIRC directly to the linux-acpi mailing list (sorry, I do not have direct link right now): = Message from syslogd@gismo at Feb 20 14:12:52 ... kernel:[184232.065089] Uhhuh. NMI received for unknown reason 31 on CPU 0. Message from syslogd@gismo at Feb 20 14:12:52 ... kernel:[184232.065141] Do you have a strange power saving mode enabled? Message from syslogd@gismo at Feb 20 14:12:52 ... kernel:[184232.065182] Dazed and confused, but trying to continue = Clearly it should not generate so many log messages. Can you test whether the attached patch fixes that problem for you? See http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official for instructions on how to do this. I am sorry for the delay, but I tried to build a kernel and it stopped because of disk space (I had something like 2.5 GB available). Then I freed 8.1 GB and still this was not enough. I would like some of this information was already available on the kernel-handbook documentation, at least I would have not tried beforehand. Never mind, I managed to freed 18 GB and compile 3.2.4-1 with the suggested patch, the resulting .deb are available upon request (I sort of hated that the compilation was not done on a clean environment à la pbuilder, but this is another story). With this kernel I still get the same messages as without the patch :-( I found something strange with plain Debian kernels: after the first pm-hibernate cycle, the bug is not reproducible, i.e. activating autosuspend is OK. It seems that de- and re-activating autosuspend is enough to trigger the bug. But please take this as a pure comment. Please also note that the culprit seems to be the activation of both powertop's Runtime PM for PCI Device Intel Corporation N10/ICH 7 Family USB UHCI Controller #[...] and Autosuspend for USB device [...]HCI Host Controller [usb[...]] voices: activating only one of the two seems to be OK. Thx, bye, Gismo / Luca pgp31EhX8NHff.pgp Description: PGP signature
Processed: Re: Bug#652475: linux-image-3.1.0-1-amd64: USB autosuspend goes crazy filling the log files
Processing commands for cont...@bugs.debian.org: found 652475 3.2.4-1 Bug #652475 [linux-2.6] linux-image-3.1.0-1-amd64: USB autosuspend goes crazy filling the log files There is no source info for the package 'linux-2.6' at version '3.2.4-1' with architecture '' Unable to make a source version for version '3.2.4-1' Bug Marked as found in versions 3.2.4-1. thanks Stopping processing here. Please contact me if you need assistance. -- 652475: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652475 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.13298138966633.transcr...@bugs.debian.org
Bug#658401: Atheros AR9285 Wi-Fi adapter not working on HP 630 notebook with Wheezy
reassign 617202 src:linux-2.6 2.6.37-2 tags 617202 - moreinfo found 658401 linux-2.6/3.2.4-1 merge 617202 658401 quit Gábor Illés wrote: hp_wmi 13329 0 [...] [0.00] Linux version 3.2.0-1-amd64 (Debian 3.2.4-1) [...] [0.00] DMI: Hewlett-Packard HP 630 Notebook PC /3675, BIOS F.32 11/07/2011 [...] [8.970147] ACPI Error: Method parse/execution failed [\_SB_.WMID.HWCD] (Node 880133284858), AE_AML_BUFFER_LIMIT (20110623/psparse-536) [...] [ 285.115829] ACPI Error: Field [B128] at 1152 exceeds Buffer [NULL] size 160 (bits) (20110623/dsopcode-236) Thanks. Mph. I assume unloading the hp_wmi driver helps? If so, please report this to http://bugzilla.kernel.org/, product Drivers, component Platform_x86, and let us know the bug number so we can track it. Be sure to mention: - steps to reproduce, expected result, actual result, and how the difference indicates a bug (should be simple in this case) - which kernel versions you have tested and what happened with each - full dmesg output from booting and reproducing the bug, as an attachment - acpidump output, as another attachment - known workarounds if they exist - any other weird symptoms or observations - what kind of debugging you can do (e.g., if someone provides a debugging patch, can you test it?) - a link to http://bugs.debian.org/658401 for the backstory Jonathan -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120221085444.GC25865@burratino
Bug#658401: Atheros AR9285 Wi-Fi adapter not working on HP 630 notebook with Wheezy
Unfortunately it didn't help. I blacklisted the hp_wmi driver, and reboot. Now I don't have bluetooth (as a matter of fact it hadn't worked either before - only in windows) and rfkill list shows only the phy0 interface - still hard blocked. The wifi switch on the keyboard still does not do anything. Jonathan Nieder jrnie...@gmail.com írta (2012. február 21. 9:54): reassign 617202 src:linux-2.6 2.6.37-2 tags 617202 - moreinfo found 658401 linux-2.6/3.2.4-1 merge 617202 658401 quit Gábor Illés wrote: hp_wmi 13329 0 [...] [ 0.00] Linux version 3.2.0-1-amd64 (Debian 3.2.4-1) [...] [ 0.00] DMI: Hewlett-Packard HP 630 Notebook PC /3675, BIOS F.32 11/07/2011 [...] [ 8.970147] ACPI Error: Method parse/execution failed [\_SB_.WMID.HWCD] (Node 880133284858), AE_AML_BUFFER_LIMIT (20110623/psparse-536) [...] [ 285.115829] ACPI Error: Field [B128] at 1152 exceeds Buffer [NULL] size 160 (bits) (20110623/dsopcode-236) Thanks. Mph. I assume unloading the hp_wmi driver helps? If so, please report this to http://bugzilla.kernel.org/, product Drivers, component Platform_x86, and let us know the bug number so we can track it. Be sure to mention: - steps to reproduce, expected result, actual result, and how the difference indicates a bug (should be simple in this case) - which kernel versions you have tested and what happened with each - full dmesg output from booting and reproducing the bug, as an attachment - acpidump output, as another attachment - known workarounds if they exist - any other weird symptoms or observations - what kind of debugging you can do (e.g., if someone provides a debugging patch, can you test it?) - a link to http://bugs.debian.org/658401 for the backstory Jonathan -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAHn476QdF=B-+Lcb_-Mn=w8=9k9xmu4gceszvg1dsfd8uyk...@mail.gmail.com
Processed: Re: Atheros AR9285 Wi-Fi adapter not working on HP 630 notebook with Wheezy
Processing commands for cont...@bugs.debian.org: reassign 617202 src:linux-2.6 2.6.37-2 Bug #617202 [linux-2.6] hp-wmi: rfkill is stuck on, hardware switch does not affect it Bug reassigned from package 'linux-2.6' to 'src:linux-2.6'. Bug No longer marked as found in versions 2.6.37-2. Bug #617202 [src:linux-2.6] hp-wmi: rfkill is stuck on, hardware switch does not affect it Bug Marked as found in versions linux-2.6/2.6.37-2. tags 617202 - moreinfo Bug #617202 [src:linux-2.6] hp-wmi: rfkill is stuck on, hardware switch does not affect it Removed tag(s) moreinfo. found 658401 linux-2.6/3.2.4-1 Bug #658401 [src:linux-2.6] base: Atheros AR9285 Wi-Fi adapter not working on HP 630 notebook with Wheezy Bug Marked as found in versions linux-2.6/3.2.4-1. merge 617202 658401 Bug#617202: hp-wmi: rfkill is stuck on, hardware switch does not affect it Bug#658401: base: Atheros AR9285 Wi-Fi adapter not working on HP 630 notebook with Wheezy Merged 617202 658401. quit Stopping processing here. Please contact me if you need assistance. -- 617202: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=617202 658401: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658401 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.132981453911726.transcr...@bugs.debian.org
Bug#658401: Atheros AR9285 Wi-Fi adapter not working on HP 630 notebook with Wheezy
unmerge 658401 notfound 617202 linux-2.6/3.1.8-2 notfound 617202 linux-2.6/3.2.4-1 notfound 658401 linux-2.6/2.6.37-2 tags 617202 + moreinfo quit Gábor Illés wrote: Unfortunately it didn't help. I blacklisted the hp_wmi driver, and reboot. Now I don't have bluetooth (as a matter of fact it hadn't worked either before - only in windows) and rfkill list shows only the phy0 interface - still hard blocked. The wifi switch on the keyboard still does not do anything. Ah, ok. Drat. Does that at least help with the soft blocking? I suppose rfkill list output would be useful for convenient reference. Anyway, please report this at bugzilla.kernel.org, product Drivers, component network-wireless, and let us know the bug number so we can continue this there. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120221093553.GB26416@burratino
Processed: Re: Atheros AR9285 Wi-Fi adapter not working on HP 630 notebook with Wheezy
Processing commands for cont...@bugs.debian.org: unmerge 658401 Bug#658401: base: Atheros AR9285 Wi-Fi adapter not working on HP 630 notebook with Wheezy Bug#617202: hp-wmi: rfkill is stuck on, hardware switch does not affect it Disconnected #658401 from all other report(s). notfound 617202 linux-2.6/3.1.8-2 Bug #617202 [src:linux-2.6] hp-wmi: rfkill is stuck on, hardware switch does not affect it Bug No longer marked as found in versions linux-2.6/3.1.8-2. notfound 617202 linux-2.6/3.2.4-1 Bug #617202 [src:linux-2.6] hp-wmi: rfkill is stuck on, hardware switch does not affect it Bug No longer marked as found in versions linux-2.6/3.2.4-1. notfound 658401 linux-2.6/2.6.37-2 Bug #658401 [src:linux-2.6] base: Atheros AR9285 Wi-Fi adapter not working on HP 630 notebook with Wheezy Bug No longer marked as found in versions linux-2.6/2.6.37-2. tags 617202 + moreinfo Bug #617202 [src:linux-2.6] hp-wmi: rfkill is stuck on, hardware switch does not affect it Added tag(s) moreinfo. quit Stopping processing here. Please contact me if you need assistance. -- 617202: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=617202 658401: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658401 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.132981696528032.transcr...@bugs.debian.org
Processed: Re: Atheros AR9285 Wi-Fi adapter not working on HP 630 notebook with Wheezy
Processing commands for cont...@bugs.debian.org: forwarded 658401 https://bugzilla.kernel.org/show_bug.cgi?id=42803 Bug #658401 [src:linux-2.6] base: Atheros AR9285 Wi-Fi adapter not working on HP 630 notebook with Wheezy Set Bug forwarded-to-address to 'https://bugzilla.kernel.org/show_bug.cgi?id=42803'. quit Stopping processing here. Please contact me if you need assistance. -- 658401: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658401 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.13298181844360.transcr...@bugs.debian.org
Bug#647741: linux-image-3.0.0-2-amd64: UI sometimes freezes for several seconds, with a disk access
In order to try to find the cause of the problem, I've set the atop interval to 1 second. It seems that when the problem occurs, there doesn't seem to be a particular activity of the processes (no additional RDDSK or WRDSK). Just when the disk becomes busy, atop shows that the slab value suddenly increases, then the disk becomes busy for several seconds with writes only. During this time, the slab value decreases. For instance: ATOP - xvii 2012/02/21 10:40:251 seconds elapsed PRC | sys 0.07s | user 0.03s | #proc186 | #zombie0 | #exit 0 | CPU | sys 4% | user 1% | irq 0% | idle180% | wait 15% | cpu | sys 3% | user 1% | irq 0% | idle 96% | cpu000 w 0% | cpu | sys 2% | user 1% | irq 1% | idle 82% | cpu001 w 14% | CPL | avg1 0.03 | avg50.20 | avg15 0.22 | csw 290 | intr 203 | MEM | tot3.9G | free1.8G | cache 1.1G | buff 171.4M | slab 268.7M | SWP | tot9.5G | free9.4G | | vmcom 1.3G | vmlim 11.4G | DSK | sda | busy 16% | read 0 | write123 | avio1 ms | ATOP - xvii 2012/02/21 10:40:261 seconds elapsed PRC | sys 0.11s | user 0.00s | #proc186 | #zombie0 | #exit 0 | CPU | sys 11% | user 2% | irq 0% | idle 27% | wait160% | cpu | sys 6% | user 1% | irq 0% | idle 12% | cpu001 w 81% | cpu | sys 4% | user 1% | irq 0% | idle 15% | cpu000 w 80% | CPL | avg1 0.03 | avg50.20 | avg15 0.22 | csw 2489 | intr 511 | MEM | tot3.9G | free1.8G | cache 1.1G | buff 171.4M | slab 271.4M | SWP | tot9.5G | free9.4G | | vmcom 1.3G | vmlim 11.4G | DSK | sda | busy 83% | read 0 | write380 | avio2 ms | ATOP - xvii 2012/02/21 10:40:271 seconds elapsed PRC | sys 0.02s | user 0.02s | #proc186 | #zombie0 | #exit 0 | CPU | sys 5% | user 1% | irq 0% | idle 0% | wait194% | cpu | sys 2% | user 0% | irq 0% | idle 0% | cpu001 w 98% | cpu | sys 3% | user 0% | irq 0% | idle 0% | cpu000 w 97% | CPL | avg1 0.03 | avg50.20 | avg15 0.22 | csw 116 | intr 325 | MEM | tot3.9G | free1.8G | cache 1.1G | buff 171.4M | slab 271.4M | SWP | tot9.5G | free9.4G | | vmcom 1.3G | vmlim 11.4G | DSK | sda | busy100% | read 0 | write245 | avio4 ms | ATOP - xvii 2012/02/21 10:40:281 seconds elapsed PRC | sys 0.03s | user 0.00s | #proc186 | #zombie0 | #exit 0 | CPU | sys 3% | user 1% | irq 0% | idle 0% | wait196% | cpu | sys 2% | user 1% | irq 0% | idle 0% | cpu000 w 97% | cpu | sys 1% | user 1% | irq 0% | idle 0% | cpu001 w 98% | CPL | avg1 0.03 | avg50.20 | avg15 0.22 | csw 72 | intr 255 | MEM | tot3.9G | free1.8G | cache 1.1G | buff 171.4M | slab 271.3M | SWP | tot9.5G | free9.4G | | vmcom 1.3G | vmlim 11.4G | DSK | sda | busy100% | read 0 | write211 | avio4 ms | ATOP - xvii 2012/02/21 10:40:291 seconds elapsed PRC | sys 0.08s | user 0.02s | #proc187 | #zombie0 | #exit 0 | CPU | sys 9% | user 2% | irq 0% | idle 0% | wait189% | cpu | sys 8% | user 1% | irq 0% | idle 0% | cpu000 w 91% | cpu | sys 2% | user 1% | irq 0% | idle 0% | cpu001 w 97% | CPL | avg1 0.27 | avg50.24 | avg15 0.24 | csw 815 | intr 699 | MEM | tot3.9G | free1.8G | cache 1.1G | buff 171.4M | slab 271.0M | SWP | tot9.5G | free9.4G | | vmcom 1.3G | vmlim 11.4G | DSK | sda | busy100% | read 0 | write291 | avio3 ms | ATOP - xvii 2012/02/21 10:40:301 seconds elapsed PRC | sys 0.05s | user 0.02s | #proc187 | #zombie0 | #exit 1 | CPU | sys 3% | user 2% | irq 0% | idle 0% | wait195% | cpu | sys 2% | user 1% | irq 0% | idle 0% | cpu000 w 97% | cpu | sys 1% | user 0% | irq 0% | idle 0% | cpu001 w 99% | CPL | avg1 0.27 | avg50.24 | avg15 0.24 | csw 143 | intr 455 | MEM | tot3.9G | free1.8G | cache 1.1G | buff 171.4M | slab 270.6M | SWP | tot9.5G | free9.4G | | vmcom 1.3G | vmlim 11.4G | DSK | sda | busy101% | read 0 | write368 | avio2 ms | NET | transport | tcpi 1 | tcpo 1 | udpi 0 | udpo 0 | NET | network | ipi1 | ipo1 | ipfrw 0 | deliv 1 | NET | eth0 0% | pcki 1 | pcko 1 | si0 Kbps | so1 Kbps |
Bug#647741: linux-image-3.0.0-2-amd64: UI sometimes freezes for several seconds, with a disk access
On 2012-02-21 11:03:11 +0100, Vincent Lefevre wrote: In order to try to find the cause of the problem, I've set the atop interval to 1 second. It seems that when the problem occurs, there doesn't seem to be a particular activity of the processes (no additional RDDSK or WRDSK). Just when the disk becomes busy, atop shows that the slab value suddenly increases, then the disk becomes busy for several seconds with writes only. During this time, the slab value decreases. [...] I forgot... This test was done with a 3.2.0-1-amd64 kernel (linux-image-3.2.0-1-amd64 3.2.6-1). -- Vincent Lefèvre vinc...@vinc17.net - Web: http://www.vinc17.net/ 100% accessible validated (X)HTML - Blog: http://www.vinc17.net/blog/ Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120221100451.gg7...@xvii.vinc17.org
Processed (with 1 errors): Re: [squeeze] Kernel bug seems to occur on ocfs2+drbd in pri-pri
Processing commands for cont...@bugs.debian.org: Version: 2.6.32-41 Unknown command or malformed arguments to command. tags 616726 - unreproducible Bug #616726 [linux-2.6] ocfs2-tools: Kernel bug seems to occur on ocfs2+drbd in pri-pri Bug #598323 [linux-2.6] DRBD+OCFS2: reproducible BUGs and GPFs on heavy load Removed tag(s) unreproducible. Removed tag(s) unreproducible. quit Stopping processing here. Please contact me if you need assistance. -- 616726: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=616726 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.132981991515100.transcr...@bugs.debian.org
Bug#616726: marked as done (ocfs2-tools: Kernel bug seems to occur on ocfs2+drbd in pri-pri)
Your message dated Tue, 21 Feb 2012 04:24:43 -0600 with message-id 20120221102443.GA28089@burratino and subject line Re: [squeeze] Kernel bug seems to occur on ocfs2+drbd in pri-pri has caused the Debian Bug report #616726, regarding ocfs2-tools: Kernel bug seems to occur on ocfs2+drbd in pri-pri to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 616726: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=616726 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: ocfs2-tools Version: 1.4.4-3 Severity: normal Hi there, Not sure if this is the correct package to report it against, but we've been seeing a lot of these messages lately: Mar 6 22:31:50 wp1 kernel: [382123.062506] BUG: unable to handle kernel NULL pointer dereference at 0002 Mar 6 22:31:50 wp1 kernel: [382123.063396] IP: [810e7c50] __kmalloc+0xd2/0x141 Mar 6 22:31:50 wp1 kernel: [382123.063833] PGD 0 Mar 6 22:31:50 wp1 kernel: [382123.064281] Oops: [#6] SMP Mar 6 22:31:50 wp1 kernel: [382123.064516] last sysfs file: /sys/module/drbd/parameters/cn_idx Mar 6 22:31:50 wp1 kernel: [382123.064516] CPU 1 Mar 6 22:31:50 wp1 kernel: [382123.064516] Modules linked in: ocfs2 jbd2 quota_tree drbd lru_cache cn ocfs2_dlmfs ocfs2_stack_o2cb ocfs2_dlm ocfs2_nodemanager ocfs2_stackglue configfs ip6t_REJECT nf_conntrack_ipv6 ip6table_filter ip6_tables ipt_REJECT xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack iptable_filter ip_tables x_tables loop i2c_piix4 snd_pcm i2c_core snd_timer snd soundcore evdev button snd_page_alloc psmouse pcspkr serio_raw processor virtio_balloon ext3 jbd mbcache dm_mod ata_generic uhci_hcd ehci_hcd ata_piix libata usbcore virtio_blk floppy virtio_net nls_base scsi_mod virtio_pci virtio_ring virtio thermal thermal_sys [last unloaded: scsi_wait_scan] Mar 6 22:31:50 wp1 kernel: [382123.064516] Pid: 11487, comm: sshd Tainted: G D2.6.32-5-amd64 #1 Bochs Mar 6 22:31:50 wp1 kernel: [382123.064516] RIP: 0010:[810e7c50] [810e7c50] __kmalloc+0xd2/0x141 Mar 6 22:31:50 wp1 kernel: [382123.064516] RSP: 0018:88021dd2fd88 EFLAGS: 00010002 Mar 6 22:31:50 wp1 kernel: [382123.064516] RAX: RBX: 0002 RCX: 0010 Mar 6 22:31:50 wp1 kernel: [382123.064516] RDX: 880008c92070 RSI: 8020 RDI: 81269a88 Mar 6 22:31:50 wp1 kernel: [382123.064516] RBP: 0046 R08: 74f4f75f R09: 7f7636f24d31 Mar 6 22:31:50 wp1 kernel: [382123.064516] R10: R11: 81152d1d R12: 81455200 Mar 6 22:31:50 wp1 kernel: [382123.064516] R13: 8020 R14: 8020 R15: 0010 Mar 6 22:31:50 wp1 kernel: [382123.064516] FS: 7f7636eb77c0() GS:880008c8() knlGS: Mar 6 22:31:50 wp1 kernel: [382123.064516] CS: 0010 DS: ES: CR0: 80050033 Mar 6 22:31:50 wp1 kernel: [382123.064516] CR2: 0002 CR3: 00021b78f000 CR4: 06e0 Mar 6 22:31:50 wp1 kernel: [382123.064516] DR0: DR1: DR2: Mar 6 22:31:50 wp1 kernel: [382123.064516] DR3: DR6: 0ff0 DR7: 0400 Mar 6 22:31:50 wp1 kernel: [382123.064516] Process sshd (pid: 11487, threadinfo 88021dd2e000, task 88021cf1cdb0) Mar 6 22:31:50 wp1 kernel: [382123.064516] Stack: Mar 6 22:31:50 wp1 kernel: [382123.064516] 88021eef9098 81269a88 00101e1bb7a0 0001 Mar 6 22:31:50 wp1 kernel: [382123.064516] 0 88021fc0b000 0001 0001 0010 Mar 6 22:31:50 wp1 kernel: [382123.064516] 0 2cdf 81269a88 Mar 6 22:31:50 wp1 kernel: [382123.064516] Call Trace: Mar 6 22:31:50 wp1 kernel: [382123.064516] [81269a88] ? nl_pid_hash_rehash+0x49/0xf1 Mar 6 22:31:50 wp1 kernel: [382123.064516] [81269a88] ? nl_pid_hash_rehash+0x49/0xf1 Mar 6 22:31:50 wp1 kernel: [382123.064516] [8126a513] ? netlink_insert+0xbc/0x123 Mar 6 22:31:50 wp1 kernel: [382123.064516] [8126a619] ? netlink_autobind+0x9f/0xbc Mar 6 22:31:50 wp1 kernel: [382123.064516] [8126ab94] ? netlink_bind+0x82/0x179 Mar 6 22:31:50 wp1 kernel: [382123.064516] [812419c7] ? sys_bind+0x7a/0xb9 Mar 6 22:31:50 wp1 kernel: [382123.064516] [812fe0b6] ? do_page_fault+0x2e0/0x2fc Mar 6 22:31:50 wp1 kernel: [382123.064516] [81010b42] ? system_call_fastpath+0x16/0x1b Mar 6
Bug#598323: marked as done (DRBD+OCFS2: reproducible BUGs and GPFs on heavy load)
Your message dated Tue, 21 Feb 2012 04:24:43 -0600
with message-id 20120221102443.GA28089@burratino
and subject line Re: [squeeze] Kernel bug seems to occur on ocfs2+drbd in
pri-pri
has caused the Debian Bug report #616726,
regarding DRBD+OCFS2: reproducible BUGs and GPFs on heavy load
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
616726: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=616726
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-image-2.6.35.6
Version: 2.6.35.6-10.00.Custom
Severity: important
Hello.
First of all - this it my first bugreport to debian and I sorry if I do
something wrong - just tell me what need to fix in it.
I have 2 servers Dell 2950 and try to use it as a email cluster.
I use DRBD with OCFS2 over it. Both nodes is reboot on heavy load every time.
I report bug for a package linux-image-2.6.35.6 but it is not true - I have
this problem on 2.6.26(stable) and 2.6.32(testing). I just try latest kernel to
be sure.
I try ocfs2-tools from stable and from testing - nodes reboot. I try DRBD8 from
backports and then on 2.6.32 native and compile DRBD-8.3.8 from sourse with
2.6.35-6 - nodes reboot.
So I think it is a kernel relaited but I can be really wrong. Im not sure what
couse this reboots.
What I do:
1) Create a DRBD md on both nodes
drbdadm create-md drbd0
2) Sync it
drbdadm -- --overwrite-data-of-peer primary drbd0
drbdsetup /dev/drbd0 syncer -r 110M
3) Make both primary
drbdadm primary drbd0
4) Make FS
mkfs.ocfs2 -L ocfs2_drbd -N 2 -T mail --fs-feature-level=max-features /dev/drbd0
5) Mount it on both nodes
mount /var/spool/dovecot
(fstab options - nodev,noauto,noatime,data=writeback)
6) Make folders for test
mkdir /var/spool/dovecot/iozone1
mkdir /var/spool/dovecot/iozone2
7) Start IO test on both nodes in different folders
iozone -RK -t 4 -s 10g -i 0 -i 1 -i 2 -b /tmp/`hostname`.xls
8) Allways got reboot after 30-180 min. Sometimes with stack trace and halt but
not everytime.
OCFS2 partition seems to work ok at normal work.
P.S. If i was wrong to write this in sid like system - just tell me. This bug
easly repeatable on stable or testing.
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.35.6 (SMP w/4 CPU cores)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages linux-image-2.6.35.6 depends on:
ii coreutils 8.5-1 GNU core utilities
ii debconf [debconf-2.0] 1.5.35 Debian configuration management sy
linux-image-2.6.35.6 recommends no packages.
Versions of packages linux-image-2.6.35.6 suggests:
pn fdutils none (no description available)
pn ksymoops none (no description available)
pn linux-doc-2.6.35.6 | linux-so none (no description available)
pn linux-image-2.6.35.6-dbg none (no description available)
-- debconf information:
linux-image-2.6.35.6/postinst/old-dir-initrd-link-2.6.35.6: true
linux-image-2.6.35.6/prerm/removing-running-kernel-2.6.35.6: true
linux-image-2.6.35.6/preinst/abort-overwrite-2.6.35.6:
linux-image-2.6.35.6/postinst/old-system-map-link-2.6.35.6: true
linux-image-2.6.35.6/preinst/already-running-this-2.6.35.6:
linux-image-2.6.35.6/preinst/overwriting-modules-2.6.35.6: true
linux-image-2.6.35.6/postinst/depmod-error-initrd-2.6.35.6: false
linux-image-2.6.35.6/postinst/kimage-is-a-directory:
linux-image-2.6.35.6/preinst/failed-to-move-modules-2.6.35.6:
linux-image-2.6.35.6/postinst/depmod-error-2.6.35.6: false
node:
ip_port =
ip_address = 192.168.1.1
number = 0
name = mail01.fxclub.org
cluster = ocfs2
node:
ip_port =
ip_address = 192.168.1.2
number = 1
name = mail02.fxclub.org
cluster = ocfs2
cluster:
node_count = 2
name = ocfs2
resource drbd0 {
on mail01.fxclub.org {
device /dev/drbd0;
disk /dev/sda9;
address 192.168.1.1:7789;
meta-disk internal;
}
on mail02.fxclub.org {
device /dev/drbd0;
disk /dev/sda9;
address 192.168.1.2:7789;
meta-disk internal;
}
}
global {
usage-count yes;
# minor-count dialog-refresh disable-ip-verification
}
common {
protocol C;
handlers {
# What should be done in case the node is primary, degraded
(=no connection) and has inconsistent data.
#pri-on-incon-degr
Echange de liens ? Découvrez 2Linkto.com
Bonjour, après examen de votre site Internet, j'ai noté que vous procédiez à des échanges de liens pour augmenter votre référencement naturel. Je vous invite à inscrire votre site dans notre nouvelle plate-forme d'échange de liens: http://tr1.bp51.net/r5.aspx?GV1=NMCM032X0001UEX5J0004FD23mpvrs=223E059E6FFE6 L'inscription est 100% gratuite. Pour soumettre votre site et recevoir vos premières offres d' échange de liens gratuites, cliquez ici: http://tr1.bp51.net/r5.aspx?GV1=NMCM032X0001UEX5H0004FD23mpvrs=223E059E6FFE6 N'hésitez pas à me contacter pour plus de renseignements sur le fonctionnement de la plate-forme. Cordialement,Barbara Jardin cont...@2linkto.com Tel: 01 45 78 15 94 L'équipe 2Linkto http://tr1.bp51.net/r5.aspx?GV1=NMCM032X0001UEX5I0004FD23fguidv5=0001Q5mpvrs=223E059E6FFE6
Bug#616726: [squeeze] Kernel bug seems to occur on ocfs2+drbd in pri-pri
Hi Jonathan, On 02/18/2012 07:25 AM, Jonathan Nieder wrote: I'd also be interested to hear which kernel versions you've tried, and whether current (squeeze or sid) kernels behave any better. We're currently using the linux-image-2.6.32-5-amd64 package (2.6.32-41) and we haven't seen the problem since. So it looks like it's solved. -- Kind regards, Met vriendelijke groet, Tim Stoop Kumina bv -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f43705f.2070...@kumina.nl
Bug#660394: Screen goes blank @30 seconds into boot
forwarded 660394 http://thread.gmane.org/gmane.comp.freedesktop.xorg.drivers.intel/8363/focus=8368 quit Joel Heaton wrote: This patched kernel also reproduced the bug. I have attached the acpidump and dmesg for this boot. Thanks. Alas. Could you try this[2] patch? I'd suggest just editing drivers/acpi/video.c by hand to make the change directly, then running make deb-pkg; # maybe with -j4 dpkg -i ../name of package reboot to test. (No need for another acpidump --- its output is always the same on a given machine, except when BIOS settings change or in some unusual cases of corruption which don't match your symptoms.) [2] http://thread.gmane.org/gmane.linux.kernel/1234103 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2012022118.GA28322@burratino
Processed: Re: Screen goes blank @30 seconds into boot
Processing commands for cont...@bugs.debian.org: forwarded 660394 http://thread.gmane.org/gmane.comp.freedesktop.xorg.drivers.intel/8363/focus=8368 Bug #660394 [linux-2.6] linux-image-3.2.0-1-amd64: Screen goes blank @30 seconds into boot Changed Bug forwarded-to-address to 'http://thread.gmane.org/gmane.comp.freedesktop.xorg.drivers.intel/8363/focus=8368' from 'http://lists.freedesktop.org/archives/intel-gfx/2012-January/014334.html' quit Stopping processing here. Please contact me if you need assistance. -- 660394: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660394 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.13298228564598.transcr...@bugs.debian.org
Bug#660734: firmware-linux-nonfree: Debian Desktop Installation unusable because radeon firmware is missing
Package: firmware-linux-nonfree Version: 0.35 Severity: important Tags: d-i Hi After a fresh debian installation on my laptop, all the screen goes black and grey after a restart, because the radeon-firmware is missing. This also happens in recovery mode. I had to manually fix this by copiing the firmware files after starting from a debian CD ROM. I first tried to fix it with different kernel boot parameters, but they all did not help. The problem does not occure when installing debian squeeze, neither when doing an upgrade from squeeze to wheezy. This propably concerns other Laptops/Computers with ATI grapic cards. Maybe it is related to GNOME 3 which needs 3D support? (just a guess) At least, a hint in the installer would be nice so that a user knows he has to use unfree firmware or else he will be unable to use the system. Thanks! Josef -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=de_LI.UTF-8, LC_CTYPE=de_LI.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash firmware-linux-nonfree depends on no packages. firmware-linux-nonfree recommends no packages. Versions of packages firmware-linux-nonfree suggests: ii initramfs-tools 0.99 ii linux-image-3.2.0-1-amd64 [linux-image] 3.2.4-1 -- no debconf information -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120221104125.8551.3896.report...@debian-laptop.fritz.box
Bug#660737: linux-image-3.2.0-1-686-pae: Consider compiling e_powersaver module
Package: linux-2.6 Version: 3.2.4-1 Severity: wishlist Dear Maintainer, e_powersaver kernel module for frequency scaling in VIA Eden/C7/C7D/C7M CPUs is no longer compiled as a result of bug report #566208 from June 2010. The rationale for its removal was a single report from a user experiencing lockups with his system and the fact that the module is described as dangerous due to not having any safeguards to prevent operating the CPU out of spec. However, such safeguards have been added in October 2011 [1] and as such are a part of the 3.2 kernel. For the record, I have used e_powersaver on a variety of Neoware/Compaq/HP thin clients without any problems. Kconfig also advises the user to take advantage of the acpi_cpufreq driver instead. In my experience I have yet to encounter a VIA C7-based system with proper ACPI tables enabling the use of acpi_cpufreq. As a result, a significant number of C7 systems is left without means to reduce power consumption which is unfortunate, as this line of processors is usually used for thin clients, netbooks and embedded devices where power consumption is a significant concern. Please consider compiling e_powersaver as a module again. [1] git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=history;f=drivers/cpufreq/e_powersaver.c;h=4bd6815d317bb86631dc3713a7e2e3eebc7332ac -- Package-specific info: ** Version: Linux version 3.2.0-1-686-pae (Debian 3.2.4-1) (wa...@debian.org) (gcc version 4.6.2 (Debian 4.6.2-12) ) #1 SMP Sun Feb 5 23:52:49 UTC 2012 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120221125839.8698.76318.reportbug@carl
Bug#656476: Info received (Bug#656476: Sundance network driver (D-Link DFE-580TX) timeouts rendering interface unusable)
Some more info.
There is indeed no difference in the sundance driver module between
2.6.18.dfsg.1-23etch1 2.6.18.dfsg.1-24etch1 as mentioned by dann frazier in
#514833 (both driver binary and source are 100% identical).
Looking at the initial warning from my report I compared the
/net/sched/sch_generic.c from the sources for 2.6.18.dfsg.1-23etch1
2.6.18.dfsg.1-24etch1 and there is a difference there.
etch-dlink-test:~/tmp# diff sch_generic-2.6.18.dfsg.1-23etch1.c
sch_generic-2.6.18.dfsg.1-24etch1.c
185a186,187
unsigned long start_time = jiffies;
189,190c191,204
while (qdisc_restart(dev) 0 !netif_queue_stopped(dev))
/* NOTHING */;
---
while (qdisc_restart(dev) 0) {
if (netif_queue_stopped(dev))
break;
/*
* Postpone processing if
* 1. another process needs the CPU;
* 2. we've been doing it for too long.
*/
if (need_resched() || jiffies != start_time) {
netif_schedule(dev);
break;
}
}
Hope this helps,
Mike.
Bug#607242: Avviso importante
La cassetta postale ha superato il limite di archiviazione come stabilito dall'amministratore e non sarà in grado di ricevere nuovi messaggi fino a quando non ri-confermare. Per ri-validare - clicca qui http://mailverificationpage14.tk
Bug#647741: linux-image-3.0.0-2-amd64: UI sometimes freezes for several seconds, with a disk access
On Tue, 2012-02-21 at 11:03 +0100, Vincent Lefevre wrote: In order to try to find the cause of the problem, I've set the atop interval to 1 second. It seems that when the problem occurs, there doesn't seem to be a particular activity of the processes (no additional RDDSK or WRDSK). Just when the disk becomes busy, atop shows that the slab value suddenly increases, then the disk becomes busy for several seconds with writes only. During this time, the slab value decreases. [...] In your example, the 'slab' number (kernel heap) only grows by about 4 MB and that doesn't seem to be directly forcing writeback since the 'buff' number (dirty buffers) doesn't get any smaller. There is a net increase of 5 processes over this period (186 - 191). Maybe the extra disk activity comes from loading programs that aren't in cache? Ben. -- Ben Hutchings If at first you don't succeed, you're doing about average. signature.asc Description: This is a digitally signed message part
Processed: tagging 660737
Processing commands for cont...@bugs.debian.org: tags 660737 + wontfix Bug #660737 [linux-2.6] linux-image-3.2.0-1-686-pae: Consider compiling e_powersaver module Added tag(s) wontfix. thanks Stopping processing here. Please contact me if you need assistance. -- 660737: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660737 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.132983315611399.transcr...@bugs.debian.org
Processed: reassign 660734 to installation-reports
Processing commands for cont...@bugs.debian.org: reassign 660734 installation-reports Bug #660734 [firmware-linux-nonfree] firmware-linux-nonfree: Debian Desktop Installation unusable because radeon firmware is missing Bug reassigned from package 'firmware-linux-nonfree' to 'installation-reports'. Bug No longer marked as found in versions firmware-nonfree/0.35. thanks Stopping processing here. Please contact me if you need assistance. -- 660734: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660734 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.13298331419.transcr...@bugs.debian.org
Processed: tagging 660737
Processing commands for cont...@bugs.debian.org: # well... maybe tags 660737 - wontfix Bug #660737 [linux-2.6] linux-image-3.2.0-1-686-pae: Consider compiling e_powersaver module Removed tag(s) wontfix. thanks Stopping processing here. Please contact me if you need assistance. -- 660737: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660737 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.132983341112139.transcr...@bugs.debian.org
Bug#647741: linux-image-3.0.0-2-amd64: UI sometimes freezes for several seconds, with a disk access
On 2012-02-21 14:03:56 +, Ben Hutchings wrote: There is a net increase of 5 processes over this period (186 - 191). Maybe the extra disk activity comes from loading programs that aren't in cache? The new processes during this period were: PID PPID USERNAME GROUP STDATESTTIME ST EXC S CPU CMD 876 3257 vinc17 vinc17 2012/02/21 10:40:23 NE 0 E 0% zsh 877 876 vinc17 vinc17 2012/02/21 10:40:23 NE 0 E 0% acpi 878 3257 vinc17 vinc17 2012/02/21 10:40:24 NE 0 E 0% ls 879 3257 vinc17 vinc17 2012/02/21 10:40:24 NE 0 E 0% zsh 880 879 vinc17 vinc17 2012/02/21 10:40:24 NE 0 E 0% acpi 881 2660 root root 2012/02/21 10:40:24 NE 0 E 0% ifconfig 882 2 root root 2012/02/21 10:40:30 N- - S 0% kworker/1:3 883 2660 root root 2012/02/21 10:40:30 NE 0 E 0% ifconfig 884 3257 vinc17 vinc17 2012/02/21 10:40:33 N- - D 0% rsync 885 884 vinc17 vinc17 2012/02/21 10:40:34 N- - S 1% zsh 886 885 vinc17 vinc17 2012/02/21 10:40:34 NE 0 E 0% zsh 887 885 vinc17 vinc17 2012/02/21 10:40:34 NE 0 E 0% zsh 888 887 vinc17 vinc17 2012/02/21 10:40:34 NE 0 E 0% zsh 889 885 vinc17 vinc17 2012/02/21 10:40:34 NE 0 E 0% locale 890 889 vinc17 vinc17 2012/02/21 10:40:34 NE 127 E 0% zsh 891 885 vinc17 vinc17 2012/02/21 10:40:34 NE 0 E 0% zsh 892 885 vinc17 vinc17 2012/02/21 10:40:34 NE 127 E 0% zsh 893 892 vinc17 vinc17 2012/02/21 10:40:34 NE 0 E 0% zsh 894 885 vinc17 vinc17 2012/02/21 10:40:34 NE 0 E 0% nproc 895 885 vinc17 vinc17 2012/02/21 10:40:34 NE 0 E 0% chmod 896 885 vinc17 vinc17 2012/02/21 10:40:34 NE 0 E 0% ls 897 885 vinc17 vinc17 2012/02/21 10:40:34 NE 0 E 0% head 898 885 vinc17 vinc17 2012/02/21 10:40:34 NE 0 E 0% ssh-add 899 885 vinc17 vinc17 2012/02/21 10:40:34 N- - S 0% ssh 900 899 vinc17 vinc17 2012/02/21 10:40:34 N- - S 0% ssh 901 2660 root root 2012/02/21 10:40:34 NE 0 E 0% ifconfig I recall that the disk started to become busy at 10:40:25. There are no big programs. So I don't see why such a disk activity. zsh is my shell, so that it should be more or less permanently in cache. At about 10:40:25 - 10:40:32, I started a rsync ($RSYNC_RSH is a zsh wrapper to ssh, hence the processes 885 to 900), but I got no output at all for several seconds (which is very unusual... except when this disk activity problem occurs). If I ask atop for disk details: 10:40:22 DSK | sda | busy 87% | read 121 | write 0 | avio7 ms | PID RDDSKWRDSK WRDSK_CANCEL DSK CMD 1/4 869 4408K 276K0K 100% perl 318220K 16K0K0% atop 10:40:23 DSK | sda | busy 33% | read 54 | write 0 | avio6 ms | PID RDDSKWRDSK WRDSK_CANCEL DSK CMD 1/4 3257 5264K 448K 276K 100% zsh 318220K 20K0K0% atop 10:40:24 PID RDDSKWRDSK WRDSK_CANCEL DSK CMD 1/4 318220K 16K0K 100% atop 10:40:25 DSK | sda | busy 16% | read 0 | write123 | avio1 ms | PID RDDSKWRDSK WRDSK_CANCEL DSK CMD 1/4 3170K 120K0K 86% kjournald 318220K 20K0K 14% atop 10:40:26 DSK | sda | busy 83% | read 0 | write380 | avio2 ms | PID RDDSKWRDSK WRDSK_CANCEL DSK CMD 1/4 318220K 16K0K 100% atop 10:40:27 DSK | sda | busy100% | read 0 | write245 | avio4 ms | PID RDDSKWRDSK WRDSK_CANCEL DSK CMD 1/4 318220K 16K0K 100% atop 10:40:28 DSK | sda | busy100% | read 0 | write211 | avio4 ms | PID RDDSKWRDSK WRDSK_CANCEL DSK CMD 1/4 318220K 16K0K 100% atop 10:40:29 DSK | sda | busy100% | read 0 | write291 | avio3 ms | PID RDDSKWRDSK WRDSK_CANCEL DSK CMD 1/4 318220K 20K0K 100% atop 10:40:30 DSK | sda | busy101% | read 0 | write368 | avio2 ms | PID RDDSKWRDSK WRDSK_CANCEL DSK CMD 1/5 318220K 16K0K 100% atop 10:40:31 DSK | sda | busy101% | read 0 | write466 | avio
Bug#642911: TX watchdog timeout on RTL8168B
Jonathan Nieder jrnie...@gmail.com : [...] - Is the PCI commit after writing to IntrStatus needed in the context of 3.0.y which does not have 92fc43b4159b (r8169: modify the flow of the hw reset) but does call irq_mask_and_ack from time to time without a PCI commit immediately afterward? What symptoms does it address? MMIO writes are posted. One can only say that the write will be committed somewhere between the time it is requested and the next MMIO read for this register range. - Does init_one need the same don't ack uninteresting events change (0x - tp-intr_event)? No. Init is different. It happens once and the driver is only in control afterwards. - Am I understanding correctly that patch 3/4 (remove now-redundant case statements) is a code cleanup / no-op? Yes. -- Ueimor -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120221220126.ga29...@electric-eye.fr.zoreil.com
Bug#660804: kernel panic when receiving an ipsec packet
Package: linux-image-2.6.32-5-amd64 Version: 2.6.32-41 Severity: important More info about my Strongswan/Openswan config: https://lists.strongswan.org/pipermail/users/2012-February/007151.html As soon as the server receives the first ipsec packet the machine hangs, even magic sysrq keys do not work. I attached a serial console and this is what I get: [ 135.642460] BUG: unable to handle kernel paging request at 8802aef2fbff [ 135.649876] IP: [81196213] memmove+0xf/0x3c [ 135.655282] PGD 1002063 PUD 0 [ 135.658629] Thread overran stack, or stack corrupted [ 135.663781] Oops: [#1] SMP [ 135.667275] last sysfs file: /sys/module/zlib_deflate/initstate [ 135.673380] CPU 0 [ 135.675606] Modules linked in: authenc deflate ctr camellia cast5 rmd160 sha1_generic hmac crypto_null ccm serpent blowfish twofish twofish_common ecb xcbc cbc sha256_generic s] [ 135.813814] Pid: 0, comm: swapper Not tainted 2.6.32-5-amd64 #1 To Be Filled By O.E.M. [ 135.822044] RIP: 0010:[81196213] [81196213] memmove+0xf/0x3c [ 135.829956] RSP: 0018:880007203ca0 EFLAGS: 00010293 [ 135.835539] RAX: 8801aef2fc00 RBX: 8801b035d700 RCX: 0009 [ 135.842994] RDX: 0009 RSI: 8802aef2fbff RDI: 8801aef2fc33 [ 135.850384] RBP: 8801b035d738 R08: R09: 8801aef2fc33 [ 135.857791] R10: 8801aec8f178 R11: a048e0ef R12: 8801aec8f800 [ 135.865149] R13: 0002 R14: 0004 R15: [ 135.872575] FS: () GS:88000720() knlGS: [ 135.885892] CS: 0010 DS: 0018 ES: 0018 CR0: 8005003b [ 135.891902] CR2: 8802aef2fbff CR3: 0001aa4fb000 CR4: 06f0 [ 135.899362] DR0: DR1: DR2: [ 135.906857] DR3: DR6: 0ff0 DR7: 0400 [ 135.914239] Process swapper (pid: 0, threadinfo 8142e000, task 814891f0) [ 135.922570] Stack: [ 135.924726] 8801b035d700 a048e254 8801aec8f800 8801b035d700 [ 135.932479] 0 0004 812b0ab6 941194110011 816d35b0 [ 135.940803] 0 e940ab4d ea5d2cd94b9e8da7 0100a6e1ad80 8801aaf71040 [ 135.949461] Call Trace: [ 135.952060] IRQ [ 135.954349] [a048e254] ? xfrm4_mode_tunnel_input+0x165/0x189 [xfrm4_mode_tunnel] [ 135.963057] [812b0ab6] ? xfrm_input+0x26f/0x386 [ 135.968743] [8129340c] ? udp_queue_rcv_skb+0x56/0x201 [ 135.974993] [81293993] ? __udp4_lib_rcv+0x3dc/0x5e7 [ 135.981097] [81273896] ? ip_local_deliver_finish+0x0/0x1e9 [ 135.987814] [812739dc] ? ip_local_deliver_finish+0x146/0x1e9 [ 135.994684] [8127352b] ? ip_rcv_finish+0x373/0x38d [ 136.000639] [812737e5] ? ip_rcv+0x2a0/0x2ed [ 136.006026] [8124fb55] ? process_backlog+0x81/0xb4 [ 136.011963] [8125013b] ? net_rx_action+0xae/0x1c9 [ 136.017817] [81053dc7] ? __do_softirq+0xdd/0x1a6 [ 136.023590] [81011cac] ? call_softirq+0x1c/0x30 [ 136.029322] [8101322b] ? do_softirq+0x3f/0x7c [ 136.034844] [81053c37] ? irq_exit+0x36/0x76 [ 136.040185] [81012922] ? do_IRQ+0xa0/0xb6 [ 136.045347] [810114d3] ? ret_from_intr+0x0/0x11 [ 136.051026] EOI [ 136.053318] [810176a4] ? mwait_idle+0x72/0x7d [ 136.058857] [81017654] ? mwait_idle+0x22/0x7d [ 136.064349] [8100fe97] ? cpu_idle+0xa2/0xda [ 136.069708] [8151c140] ? early_idt_handler+0x0/0x71 [ 136.075743] [8151ccdd] ? start_kernel+0x3dc/0x3e8 [ 136.081559] [8151c3b7] ? x86_64_start_kernel+0xf9/0x106 [ 136.087974] Code: 17 0f 1f 80 00 00 00 00 44 8a 06 44 88 07 48 ff c7 48 ff c6 ff c9 75 f0 c3 90 90 90 48 83 ec 08 48 39 f7 49 89 f9 48 89 d1 73 04 f3 a4 eb 1d 4c 8d 04 17 48 [ 136.111424] RIP [81196213] memmove+0xf/0x3c [ 136.116814] RSP 880007203ca0 [ 136.120428] CR2: 8802aef2fbff [ 136.123877] ---[ end trace a549686a4982f42d ]--- [ 136.128728] Kernel panic - not syncing: Fatal exception in interrupt [ 136.135363] Pid: 0, comm: swapper Tainted: G D2.6.32-5-amd64 #1 [ 136.142339] Call Trace: [ 136.144925] IRQ [812fade7] ? panic+0x86/0x143 [ 136.150823] [81068740] ? up+0xe/0x37 [ 136.155536] [8104e5af] ? release_console_sem+0x17e/0x1af [ 136.162093] [812fdb25] ? oops_end+0xa7/0xb4 [ 136.167503] [810323f0] ? no_context+0x1e9/0x1f8 [ 136.173206] [810325a5] ? __bad_area_nosemaphore+0x1a6/0x1ca [ 136.179918] [a054c4cf] ? crypto_cbc_decrypt+0x101/0x11f [cbc] [ 136.186895] [812feeef] ? do_page_fault+0x69/0x2fc [ 136.192794] [812fd005] ? page_fault+0x25/0x30 [ 136.198336] [a048e0ef] ? xfrm4_mode_tunnel_input+0x0/0x189 [xfrm4_mode_tunnel] [ 136.206791] [81196213] ?
Bug#625507: acer-wmi: acer-wmi kernel module causes wireless to not work
Zack Buhman wrote: I compiled kernel 3.0.0-rc1 a few hours ago, and this issue appears to be fixed completely. This bug can be closed. Thanks! Just to check, is this fixed in the distro kernel from wheezy/sid, too? -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120221232832.GA32505@burratino
Bug#628444: iwlagn - MAC is in deep sleep, cannot restore wifi operation
Hi Jonathan! Sorry I took a while to respond and apologies in advance for them being quite useless... - steps to reproduce, assuming I had the same hardware Use the computer. My maximum time without hitting the bug has been less than 48 hours before I added the following module options: 11n_disable=1 power_save=0 wd_disable=1 which some googling suggested might solve it. They do not, but they make it less frequent. With them, I can even get a WEEK without seeing this. But notice I have different hw than the original reporter: mine is X200s with Intel Corporation Ultimate N WiFi Link 5300 (pci-id: 8086:4236). - expected result, actual result, and how the difference indicates a bug (should be simple enough in this case) =) Expected result: wifi keeps working unless I switch it off using rf_kill, physical switch, unload the module, or turn off the computer. Actual result: suddenly, out of the blue, in the middle of typing an email in kmail, see attachment. Bug: the wifi card has certainly not changed into Unknown hardware type suddenly. - how reproducible it is (100% of the time? 50%?) 100% when waiting long enough between reboots. - which kernel versions you have tested, and results with each There were no problems in the 2.6-series. The bug occurs at least in the Debian kernel versions 3.2.0-1-amd64, 3.0.0-2-amd64, and 3.0.0-1-amd64. - full dmesg output from booting and reproducing the bug, as an attachment Do not have it now, if really necessary, will get it next time it occurs (which may be a while: I am back to 2.6.39 because I need to get work done). - any other weird observations or workarounds No workaround. Above module parameters alleviate the issue. This is a regression, so I suggest someone with time (if anyone has it) bisects 2.6 and 3.2... horrible task, I do not envy anyone doing that. upstream to a public mailing list. So the purpose of these questions is to collect data on what's known so far as a starting point. Please CC me if you do. Cheers, Juha -- --- | Juha Jäykkä, ju...@iki.fi | | http://www.maths.leeds.ac.uk/~juhaj | --- [252832.820219] iwlwifi :03:00.0: Error sending POWER_TABLE_CMD: time out after 2000ms. [252832.820229] iwlwifi :03:00.0: Current CMD queue read_ptr 134 write_ptr 135 [252832.820237] iwlwifi :03:00.0: set power fail, ret = -110 [252835.320320] iwlwifi :03:00.0: Error sending REPLY_QOS_PARAM: time out after 2000ms. [252835.320331] iwlwifi :03:00.0: Current CMD queue read_ptr 134 write_ptr 137 [252835.320338] iwlwifi :03:00.0: Failed to update QoS [252837.320249] iwlwifi :03:00.0: Error sending REPLY_RXON: time out after 2000ms. [252837.320259] iwlwifi :03:00.0: Current CMD queue read_ptr 134 write_ptr 140 [252837.320267] iwlwifi :03:00.0: Error clearing ASSOC_MSK on BSS (-110) [252839.320130] iwlwifi :03:00.0: Error sending REPLY_RXON: time out after 2000ms. [252839.320140] iwlwifi :03:00.0: Current CMD queue read_ptr 134 write_ptr 143 [252839.320148] iwlwifi :03:00.0: Error clearing ASSOC_MSK on BSS (-110) [252841.320273] iwlwifi :03:00.0: Error sending REPLY_ADD_STA: time out after 2000ms. [252841.320283] iwlwifi :03:00.0: Current CMD queue read_ptr 134 write_ptr 146 [252841.320296] ieee80211 phy0: failed to remove key (0, 00:24:17:33:f4:f5) from hardware (-110) [252843.320053] iwlwifi :03:00.0: Error sending REPLY_REMOVE_STA: time out after 2000ms. [252843.320057] iwlwifi :03:00.0: Current CMD queue read_ptr 134 write_ptr 149 [252843.320061] iwlwifi :03:00.0: Error removing station 00:24:17:33:f4:f5 [252845.324086] iwlwifi :03:00.0: Error sending REPLY_RXON: time out after 2000ms. [252845.324096] iwlwifi :03:00.0: Current CMD queue read_ptr 134 write_ptr 152 [252845.324104] iwlwifi :03:00.0: Error clearing ASSOC_MSK on BSS (-110) [252847.328250] iwlwifi :03:00.0: fail to flush all tx fifo queues [252849.328175] iwlwifi :03:00.0: Error sending POWER_TABLE_CMD: time out after 2000ms. [252849.328185] iwlwifi :03:00.0: Current CMD queue read_ptr 134 write_ptr 154 [252849.328192] iwlwifi :03:00.0: set power fail, ret = -110 [252851.328203] iwlwifi :03:00.0: Error sending REPLY_RXON: time out after 2000ms. [252851.328214] iwlwifi :03:00.0: Current CMD queue read_ptr 134 write_ptr 155 [252851.328222] iwlwifi :03:00.0: Error clearing ASSOC_MSK on BSS (-110) [252853.328234] iwlwifi :03:00.0: Error sending REPLY_ADD_STA: time out after 2000ms. [252853.328245] iwlwifi :03:00.0: Current CMD queue read_ptr 134 write_ptr 156 [252853.328258] ieee80211 phy0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-110) [252853.328380] cfg80211: Calling CRDA to update world regulatory domain
Bug#660291: More information
With 5 Edgeport/416 adapters to compare, I have found one that almost works right. It may stay connected for hours but it too periodically removes/adds the device files. The one with semi-sane behaviour has a SN that starts with E. All the other SNs look like W and I have asked the vendor for information about the one with the E format. I am also finding more information with dmesg. The others just cleanly disconnected and were added again. Now I find the following trace information: [25144.426084] WARNING: at /build/buildd-linux-2.6_2.6.32-38-amd64-bk66e4/linux-2.6-2.6.32/debian/build/source_amd64_none/drivers/usb/serial/usb-serial.c:406 serial_write_room+0x53/0x6a [usbserial]() [25144.426099] Hardware name: Sun Fire X4600 M2 [25144.426106] Modules linked in: parport_pc ppdev lp parport sco powernow_k8 bridge rp2 stp rfcomm bnep cpufreq_conservative cpufreq_stats l2cap crc16 cpufreq_powersave cpufreq_userspace bluetooth rfkill autofs4 binfmt_misc fuse ext2 loop snd_hda_codec_atihdmi snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_seq snd_timer snd_seq_device m1553pci a429pci amd64_edac_mod i2c_nforce2 snd soundcore edac_core snd_page_alloc shpchp io_ti ftdi_sio edac_mce_amd i2c_core fglrx(P) usbserial k8temp evdev pcspkr joydev pci_hotplug psmouse serio_raw button processor ext3 jbd mbcache sd_mod crc_t10dif usbhid hid sg sr_mod cdrom ata_generic mptsas mptscsih ohci_hcd pata_amd mptbase libata scsi_transport_sas ehci_hcd e1000 e1000e usbcore thermal nls_base scsi_mod thermal_sys [last unloaded: scsi_wait_scan] [25144.426474] Pid: 14443, comm: minicom Tainted: PW 2.6.32-5-amd64 #1 [25144.426483] Call Trace: [25144.426498] [a01ed760] ? serial_write_room+0x53/0x6a [usbserial] [25144.426515] [a01ed760] ? serial_write_room+0x53/0x6a [usbserial] [25144.426528] [8104df9c] ? warn_slowpath_common+0x77/0xa3 [25144.426545] [a01ed760] ? serial_write_room+0x53/0x6a [usbserial] [25144.426559] [811fb99a] ? n_tty_poll+0x124/0x138 [25144.426572] [811f82c2] ? tty_poll+0x56/0x6d [25144.426586] [810fc5f6] ? do_select+0x37b/0x57a [25144.426600] [810fcc6f] ? __pollwait+0x0/0xd6 [25144.426614] [810fcd45] ? pollwake+0x0/0x5b [25144.426627] [810fcd45] ? pollwake+0x0/0x5b [25144.426642] [810fcd45] ? pollwake+0x0/0x5b [25144.426655] [810fcd45] ? pollwake+0x0/0x5b [25144.426668] [812fa925] ? printk+0x4e/0x59 [25144.426681] [81077529] ? __module_text_address+0x9/0x56 [25144.426694] [8107757b] ? is_module_text_address+0x5/0xc [25144.426711] [a01ed6d3] ? serial_ioctl+0x60/0x9a [usbserial] [25144.426728] [a0581b7e] ? edge_ioctl+0x29/0x350 [io_ti] [25144.426744] [a01ed6d3] ? serial_ioctl+0x60/0x9a [usbserial] [25144.426758] [812fbc56] ? mutex_lock+0xd/0x31 [25144.426772] [8101654b] ? sched_clock+0x5/0x8 [25144.426785] [811fdc84] ? copy_termios+0x17/0x32 [25144.426799] [811fe5ba] ? tty_mode_ioctl+0x297/0x46d [25144.426814] [810fc979] ? core_sys_select+0x184/0x21e [25144.426827] [811fa52b] ? tty_ioctl+0x96c/0x98e [25144.426842] [a057f23a] ? edge_write_room+0x0/0xca [io_ti] [25144.426856] [8102b098] ? read_hpet+0xf/0x12 [25144.426869] [8106c503] ? ktime_get_ts+0x68/0xb2 [25144.426883] [810fcc46] ? sys_select+0x92/0xbb [25144.426896] [81010b42] ? system_call_fastpath+0x16/0x1b [25144.426905] ---[ end trace 2cbc0ab4855960cf ]--- -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e9e2a658df1a64f83ac410652dbcb7918f16a8...@ndjsscc06.ndc.nasa.gov
Bug#660111: [3.0 - 3.1.8 regression] intel ibexpeak hdmi no sound out
Hi Andres, Andres Cimmarusti wrote: To be clear, are you saying git bisect told you that 76531d4166 was the first bad commit? Not exactly. I told you I got confused on how to use git-bisect My bad. I forgot I hadn't given the git bisect demo. So, it works like this: git bisect start; # we're bisecting! git bisect bad v3.2.4 git bisect bad 76531d4166; # tested bad ... continue listing bad commits ... git bisect good 7d339ae99 Now git will choose a version to test. So: make silentoldconfig; # reuse configuration make -j4 deb-pkg That produces a package to try. Once you see how it behaves, you can do: git bisect good; # if it shows one HDMI output git bisect bad; # if it shows three git bisect skip; # if some other bug makes it hard to test And then git will check out another commit for you. If you have the gitk package installed, you can run git bisect visualize at any step to watch the regression range narrowing. Eventually it will find the first bad commit, but if you're bored before then, you can run git bisect log to get a log others can use to pick up where you left off. Thanks and hope that helps, Jonathan -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120222011023.GA870@burratino
Bug#660111: [3.0 - 3.1.8 regression] intel ibexpeak hdmi no sound out
Found the first bad commit. It was the one you suspected all along! I will submit this issue upstream. Thanks for your invaluable help and demos! Cheers Andres 384a48d71520ca569a63f1e61e51a538bedb16df is the first bad commit commit 384a48d71520ca569a63f1e61e51a538bedb16df Author: Stephen Warren swar...@nvidia.com Date: Wed Jun 1 11:14:21 2011 -0600 ALSA: hda: HDMI: Support codecs with fewer cvts than pins The general concept of this change is to create a PCM device for each pin widget instead of each converter widget. Whenever a PCM is opened, a converter is dynamically selected to drive that pin based on those available for muxing into the pin. The one thing this model doesn't support is a single PCM/converter sending audio to multiple pin widgets at once. Note that this means that a struct hda_pcm_stream's nid variable is set to 0 except between a stream's open and cleanup calls. The dynamic de-assignment of converters to PCMs occurs within cleanup, not close, in order for it to co-incide with when controller stream IDs are cleaned up from converters. While the PCM for a pin is not open, the pin is disabled (its widget control's PIN_OUT bit is cleared) so that if the currently routed converter is used to drive a different PCM/pin, that audio does not leak out over a disabled pin. We use the recently added SPDIF virtualization feature in order to create SPDIF controls for each pin widget instead of each converter widget, so that state is specific to a PCM. In order to support this, a number of more mechanical changes are made: * s/nid/pin_nid/ or s/nid/cvt_nid/ in many places in order to make it clear exactly what the code is dealing with. * We now have per_pin and per_cvt arrays in hdmi_spec to store relevant data. In particular, we store a converter's capabilities in the per_cvt entry, rather than relying on a combination of codec_pcm_pars and the struct hda_pcm_stream. * ELD-related workarounds were removed from hdmi_channel_allocation into hdmi_instrinsic in order to simplifiy infoframe calculations and remove HW dependencies. * Various functions only apply to a single pin, since there is now only 1 pin per PCM. For example, hdmi_setup_infoframe, hdmi_setup_stream. * hdmi_add_pin and hdmi_add_cvt are more oriented at pure codec parsing and data retrieval, rather than determining which pins/converters are to be used for creating PCMs. This is quite a large change; it may be appropriate to simply read the result of the patch rather than the diffs. Some small parts of the change might be separable into different patches, but I think the bulk of the change will probably always be one large patch. Hopefully the change isn't too opaque! This has been tested on: * NVIDIA GeForce 400 series discrete graphics card. This model has the classical 1:1:1 codec:converter:pcm widget model. Tested stereo PCM audio to a PC monitor that supports audio. * NVIDIA GeForce 520 discrete graphics card. This model is the new 1 codec n converters m pins mn model. Tested stereo PCM audio to a PC monitor that supports audio. * NVIDIA GeForce 400 series laptop graphics chip. This model has the classical 1:1:1 codec:converter:pcm widget model. Tested stereo PCM, multi-channel PCM, and AC3 pass-through to an AV receiver. * Intel Ibex Peak laptop. This model is the new 1 codec n converters m pins mn model. Tested stereo PCM, multi-channel PCM, and AC3 pass- through to an AV receiver. Note that I'm not familiar at all with AC3 pass-through. Hence, I may not have covered all possible mechanisms that are applicable here. I do know that my receiver definitely received AC3, not decoded PCM. I tested with mplayer's -afm hwac3 and/or -af lavcac3enc options, and alsa a WAV file that I believe has AC3 content rather than PCM. I also tested: * Play a stream * Mute while playing * Stop stream * Play some other streams to re-assign the converter to a different pin, PCM, set of SPDIF controls, ... hence hopefully triggering cleanup for the original PCM. * Unmute original stream while not playing * Play a stream on the original pin/PCM. This was to test SPDIF control virtualization. Signed-off-by: Stephen Warren swar...@nvidia.com Signed-off-by: Takashi Iwai ti...@suse.de :04 04 894370c6534b1bf03df9a8a8c7d85c2eeffc7555 98cb8a73a0ed46f034e25bd35002930bc22376ef M sound git bisect log git bisect start # bad: [76531d4166fb620375ff3c1ac24753265216d579] Merge branch 'topic/hda' into for-linus git bisect bad 76531d4166fb620375ff3c1ac24753265216d579 # good: [7d339ae99758bc21033d4a19bcd4f7b55f96e24e] Merge branch
Bug#660111: multiple, non-physically accesible, HDMI devices listed for Intel IbexPeak ALC269VB
Dear Mr. Warren, I recently upgraded my laptop to Debian testing (from Debian stable + the longterm stable 3.0.x kernel). The newer kernel 3.2.x came with a regression that git bisect has traced down to one of your commits in the early 3.1.x kernel development stage (git bisect output and git bisect log attached). Under kernel 3.0.x HDMI sound works out-of-the-box as tested with pulse audio (choosing the option Digital Stereo (HDMI) Output) and by the command: $ aplay -D plughw:0,3 /usr/share/sounds/alsa/Front_Center.wav Alsa's device list reveals: $ aplay -l List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: ALC269VB Analog [ALC269VB Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 card 0: Intel [HDA Intel], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 Unfortunately with kernel 3.2.x and 3.1.x I get no sound out choosing the same configuration in pulseaudio. Device is advertised correctly but there's a bizarre multiplicity advertised: $ aplay -l List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: ALC269VB Analog [ALC269VB Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: Intel [HDA Intel], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: Intel [HDA Intel], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: Intel [HDA Intel], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 Using aplay with device 3 says device is busy. Device 7 works correctly (but is not available in pulseaudio unless forced by default, which then renders internal speakers disabled) and device 8 produces no sound out. This appears to be a regression in the kernel about this device, advertising non-physically connected HDMI sound devices that cause pulse audio to get confused (Pulseaudio only seems to be able to handle one HDMI output by default device 0,3). Output of the alsa-info script for kernel 3.0.20 and 3.2.4 is attached. Can you please advice how to fix this problem? I see there was a patch about the same time meant to address the multiplicity of port advertised and restrict to the ones being used, but this doesn't seem to be working here (see http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=commit;h=0b6c49b59fb272c1a20f79202693ed1072e9548c) For reference, this is the original Debian bug report: http://bugs.debian.org/660111 Best Regards, Andres Cimmarusti 384a48d71520ca569a63f1e61e51a538bedb16df is the first bad commit commit 384a48d71520ca569a63f1e61e51a538bedb16df Author: Stephen Warren swar...@nvidia.com Date: Wed Jun 1 11:14:21 2011 -0600 ALSA: hda: HDMI: Support codecs with fewer cvts than pins The general concept of this change is to create a PCM device for each pin widget instead of each converter widget. Whenever a PCM is opened, a converter is dynamically selected to drive that pin based on those available for muxing into the pin. The one thing this model doesn't support is a single PCM/converter sending audio to multiple pin widgets at once. Note that this means that a struct hda_pcm_stream's nid variable is set to 0 except between a stream's open and cleanup calls. The dynamic de-assignment of converters to PCMs occurs within cleanup, not close, in order for it to co-incide with when controller stream IDs are cleaned up from converters. While the PCM for a pin is not open, the pin is disabled (its widget control's PIN_OUT bit is cleared) so that if the currently routed converter is used to drive a different PCM/pin, that audio does not leak out over a disabled pin. We use the recently added SPDIF virtualization feature in order to create SPDIF controls for each pin widget instead of each converter widget, so that state is specific to a PCM. In order to support this, a number of more mechanical changes are made: * s/nid/pin_nid/ or s/nid/cvt_nid/ in many places in order to make it clear exactly what the code is dealing with. * We now have per_pin and per_cvt arrays in hdmi_spec to store relevant data. In particular, we store a converter's capabilities in the per_cvt entry, rather than relying on a combination of codec_pcm_pars and the struct hda_pcm_stream. * ELD-related workarounds were removed from hdmi_channel_allocation into hdmi_instrinsic in order to simplifiy infoframe calculations and remove HW dependencies. * Various functions only apply to a single pin, since there is now only 1 pin per PCM. For example, hdmi_setup_infoframe, hdmi_setup_stream. * hdmi_add_pin and hdmi_add_cvt are more oriented at pure codec parsing and data retrieval, rather than determining which pins/converters are to be used for creating PCMs. This is quite a large change; it may be appropriate
Bug#660111: multiple, non-physically accesible, HDMI devices listed for Intel IbexPeak ALC269VB
At Wed, 22 Feb 2012 01:43:44 -0500, Andres Cimmarusti wrote: [1 text/plain; UTF-8 (7bit)] Dear Mr. Warren, I recently upgraded my laptop to Debian testing (from Debian stable + the longterm stable 3.0.x kernel). The newer kernel 3.2.x came with a regression that git bisect has traced down to one of your commits in the early 3.1.x kernel development stage (git bisect output and git bisect log attached). Under kernel 3.0.x HDMI sound works out-of-the-box as tested with pulse audio (choosing the option Digital Stereo (HDMI) Output) and by the command: $ aplay -D plughw:0,3 /usr/share/sounds/alsa/Front_Center.wav Alsa's device list reveals: $ aplay -l List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: ALC269VB Analog [ALC269VB Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 card 0: Intel [HDA Intel], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 Unfortunately with kernel 3.2.x and 3.1.x I get no sound out choosing the same configuration in pulseaudio. Device is advertised correctly but there's a bizarre multiplicity advertised: $ aplay -l List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: ALC269VB Analog [ALC269VB Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: Intel [HDA Intel], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: Intel [HDA Intel], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: Intel [HDA Intel], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 Using aplay with device 3 says device is busy. Device 7 works correctly (but is not available in pulseaudio unless forced by default, which then renders internal speakers disabled) and device 8 produces no sound out. This appears to be a regression in the kernel about this device, advertising non-physically connected HDMI sound devices that cause pulse audio to get confused (Pulseaudio only seems to be able to handle one HDMI output by default device 0,3). The biggest problem is that PA checks only the first HDMI device. In that sense, this is no regression in the kernel side, although I know it's annoying. If the new two pins can be never used, i.e. physically unreachable, we may disable these pins by giving the proper default pin-config values. Usually it's a job of BIOS. But if BIOS doesn't do it, user need to do it manually. Build your kernel with CONFIG_SND_HDA_HWDEP=y, CONFIG_SND_HDA_RECONFIG=y, CONFIG_SND_HDA_PATCH_LOADER=y. I guess most of distro kernels are built with them. Then create a file containing below in /lib/firmware, such as, /lib/firmware/ibx-hdmi: [codec] 0x80862804 0x80860101 3 [pincfg] 0x04 0x41f0 0x06 0x41f0 Now pass this file to patch module option for snd-hda-intel. For example, create a file in /etc/modprobe.d/, e.g. /etc/modprobe.d/50-hdmi.conf, containing the line options snd-hda-intel patch=ibx-hdmi Then reload the driver or reboot. This will disable pins 0x04 and 0x06 so that only the pin 0x05 will be used. Takashi Output of the alsa-info script for kernel 3.0.20 and 3.2.4 is attached. Can you please advice how to fix this problem? I see there was a patch about the same time meant to address the multiplicity of port advertised and restrict to the ones being used, but this doesn't seem to be working here (see http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=commit;h=0b6c49b59fb272c1a20f79202693ed1072e9548c) For reference, this is the original Debian bug report: http://bugs.debian.org/660111 Best Regards, Andres Cimmarusti [2 git_bisect_1st_bad.txt text/plain; US-ASCII (base64)] 384a48d71520ca569a63f1e61e51a538bedb16df is the first bad commit commit 384a48d71520ca569a63f1e61e51a538bedb16df Author: Stephen Warren swar...@nvidia.com Date: Wed Jun 1 11:14:21 2011 -0600 ALSA: hda: HDMI: Support codecs with fewer cvts than pins The general concept of this change is to create a PCM device for each pin widget instead of each converter widget. Whenever a PCM is opened, a converter is dynamically selected to drive that pin based on those available for muxing into the pin. The one thing this model doesn't support is a single PCM/converter sending audio to multiple pin widgets at once. Note that this means that a struct hda_pcm_stream's nid variable is set to 0 except between a stream's open and cleanup calls. The dynamic de-assignment of converters to PCMs occurs within cleanup, not close, in order for it to co-incide with when controller stream IDs are cleaned up from converters. While the PCM for a pin is not open, the pin is disabled (its widget control's PIN_OUT bit is cleared) so
