Bug#692252: linux-image-3.6-trunk-amd64: cannot install kernel headers
Package: src:linux Version: 3.6.4-1~experimental.1 Severity: important Hello, the kernel headers for the trunk kernel are again not available. As it is suggested somewhere that the missing kbuild package can be easily generated I looked in the package docs. Sadly, no trace of a hint how to install the headers. Please fix the packages. Thanks -- 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/20121104070736.24873.37227.reportbug@iscsi
Bug#692252: [experimental] cannot install kernel headers
forcemerge 573483 692252 quit Hi Michal, Michal Suchanek wrote: the kernel headers for the trunk kernel are again not available. See http://bugs.debian.org/573483, http://bugs.debian.org/690280. 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/20121104064921.GA2@elie.Belkin
Processed: Re: [experimental] cannot install kernel headers
Processing commands for cont...@bugs.debian.org: forcemerge 573483 692252 Bug #573483 [src:linux] linux-headers in unstable regularly uninstallable due to missing linux-kbuild Bug #598504 [src:linux] [experimental] linux-headers-nnn depends on linux-kbuild-nnn which is unavailable Bug #603066 [src:linux] Please always upload linux-kbuild-NNN at the same time as linux-image-NNN Bug #642988 [src:linux] linux-headers packages in experimental are often uninstallable Bug #684623 [src:linux] Missing dependency makes package not usable Bug #684745 [src:linux] linux-headers-3.5-trunk-686-pae depends on linux-kbuild-3.5, which is not available Bug #684745 [src:linux] linux-headers-3.5-trunk-686-pae depends on linux-kbuild-3.5, which is not available Marked as found in versions linux/3.6.4-1~experimental.1. Marked as found in versions linux/3.6.4-1~experimental.1. Marked as found in versions linux/3.6.4-1~experimental.1. Marked as found in versions linux/3.6.4-1~experimental.1. Marked as found in versions linux/3.6.4-1~experimental.1. Marked as found in versions linux/3.6.4-1~experimental.1. Bug #692252 [src:linux] linux-image-3.6-trunk-amd64: cannot install kernel headers Severity set to 'grave' from 'important' Added indication that 692252 affects src:linux-tools Added tag(s) experimental. Bug #598504 [src:linux] [experimental] linux-headers-nnn depends on linux-kbuild-nnn which is unavailable Bug #603066 [src:linux] Please always upload linux-kbuild-NNN at the same time as linux-image-NNN Bug #642988 [src:linux] linux-headers packages in experimental are often uninstallable Bug #684623 [src:linux] Missing dependency makes package not usable Merged 573483 598504 603066 642988 684623 684745 692252 quit Stopping processing here. Please contact me if you need assistance. -- 573483: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=573483 598504: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=598504 603066: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603066 642988: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642988 684623: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684623 684745: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684745 692252: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692252 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.135201177514923.transcr...@bugs.debian.org
Processed: Re: [experimental] cannot install kernel headers
Processing commands for cont...@bugs.debian.org: # # | Delivery to the following recipient failed permanently: # | # | hramr...@centrum.cz # | # | Technical details of permanent failure: # | Google tried to deliver your message, but it was rejected by the recipient domain. We recommend contacting the other email provider for further information about the cause of this error. The error that the other server returned was: 550 550 #5.1.0 Address rejected. (state 13). # submitter 692252 Michal Suchanek hramr...@gmail.com Bug #692252 [src:linux] linux-image-3.6-trunk-amd64: cannot install kernel headers Bug #573483 [src:linux] linux-headers in unstable regularly uninstallable due to missing linux-kbuild Bug #598504 [src:linux] [experimental] linux-headers-nnn depends on linux-kbuild-nnn which is unavailable Bug #603066 [src:linux] Please always upload linux-kbuild-NNN at the same time as linux-image-NNN Bug #642988 [src:linux] linux-headers packages in experimental are often uninstallable Bug #684623 [src:linux] Missing dependency makes package not usable Bug #684745 [src:linux] linux-headers-3.5-trunk-686-pae depends on linux-kbuild-3.5, which is not available Changed Bug submitter to 'Michal Suchanek hramr...@gmail.com' from 'Michal Suchanek hramr...@centrum.cz' End of message, stopping processing here. Please contact me if you need assistance. -- 573483: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=573483 598504: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=598504 603066: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603066 642988: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642988 684623: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684623 684745: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684745 692252: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692252 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.135201195716403.transcr...@bugs.debian.org
Bug#692234: Intel HD 4000 (Ivy Bridge) graphics freeze
Ingo wrote: -- Package-specific info: [...] Thanks much. BOOT_IMAGE=/vmlinuz root=/dev/sda2 ro i915_enable_rc6=0 drm.debug=0x2 There's a spelling mistake here: the kernel parameter disabling rc6 should be spelled i915.i915_enable_rc6=0, since it's a module parameter for the i915 module. After trying that, what would be most useful is probably to test the precompiled 3.3~rc6-1~experimental.1 package from http://snapshot.debian.org/package/linux-2.6/. 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/20121104074624.GA25450@elie.Belkin
Bug#692225: [3.2-3.6.4 regression] screen starts to flicker after suspend-to-disk
Jonathan Nieder jrnie...@gmail.com writes: Hi Bjørn, Sebastian Ramacher wrote[1]: I've recently upgrade from 3.2 to 3.6. Since the upgrade after resuming from supsend-to-disk the screen starts to flicker and the kernel log contains the following traceback: [ 4730.108047] [ cut here ] [ 4730.108073] WARNING: at /build/buildd-linux_3.6.4-1~experimental.1-amd64-QnAy6j/linux-3.6.4/drivers/gpu/drm/i915/intel_display.c:1225 intel_crtc_disable+0x52/0x86 [i915]() [ 4730.108074] Hardware name: 7458WTH [ 4730.108076] pipe B assertion failure (expected off, current on) Looks like http://thread.gmane.org/gmane.comp.video.dri.devel/75108. Do you know if this got fixed? Looks like you already found the answer, but for the record: As a result of that thread I started using the fixes from the drm-intel-fixes branch of git://people.freedesktop.org/~danvet/drm-intel , including the referenced fa555837 commit, and I have not seen the warning since. I cannot remember having noticed the flicker issue though, so I cannot confirm whether that is fixed or not. Bjørn -- 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/877gq1iswk@nemi.mork.no
Bug#692225: [3.2-3.6.4 regression] screen starts to flicker after suspend-to-disk
Hi Jonathan, On 2012-11-03 12:08:51, Jonathan Nieder wrote: # [1] forwarded 692225 https://bugs.freedesktop.org/56118 quit Sebastian Ramacher wrote: I've recently upgrade from 3.2 to 3.6. Since the upgrade after resuming from supsend-to-disk the screen starts to flicker and the kernel log contains the following traceback: [ 4730.108047] [ cut here ] [ 4730.108073] WARNING: at /build/buildd-linux_3.6.4-1~experimental.1-amd64-QnAy6j/linux-3.6.4/drivers/gpu/drm/i915/intel_display.c:1225 intel_crtc_disable+0x52/0x86 [i915]() [ 4730.108074] Hardware name: 7458WTH [ 4730.108076] pipe B assertion failure (expected off, current on) Oh, here's a better link: [1]. This is said to be fixed by fa55583797d1 drm/i915: fixup the plane-pipe fixup code thanks for the quick reply. I'll try the 3.7 RC next week and report back if it's fixed. Cheers -- Sebastian Ramacher signature.asc Description: Digital signature
Bug#692234: Intel HD 4000 (Ivy Bridge) graphics freeze
Am 04.11.2012 08:46, schrieb Jonathan Nieder: Ingo wrote: -- Package-specific info: [...] Thanks much. BOOT_IMAGE=/vmlinuz root=/dev/sda2 ro i915_enable_rc6=0 drm.debug=0x2 There's a spelling mistake here: the kernel parameter disabling rc6 should be spelled i915.i915_enable_rc6=0, since it's a module parameter for the i915 module. Many thanks an shame on me. With correct spelling I can disable rc6 and power consumption goes 8 watts up. That's for sure not how it should be, so I removed the module parameter again. But with 'drm.debug=0x2' it only reports: [drm:intel_enable_rc6], RC6 enabled so rc6p is not enabled if I understand right. I am currently running kernel 3.2.32-1 from Sid and intend to run till I get freezes. Ingo -- 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/509653c3.5040...@gmx.net
Re: Bug#692252: linux-image-3.6-trunk-amd64: cannot install kernel headers
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Sunday 04 November 2012 12:37 PM, Michal Suchanek wrote: the kernel headers for the trunk kernel are again not available. As it is suggested somewhere that the missing kbuild package can be easily generated I looked in the package docs. Sadly, no trace of a hint how to install the headers. This has been reported multiple times. The wiki page for the Debian Kernel has all the details. http://wiki.debian.org/HowToRebuildAnOfficialDebianKernelPackage Why is it missed every time? Because currently, it is built from the linux-tools src package. The kernel images are build from the linux src package. - -- Given the large number of mailing lists I follow, I request you to CC me in replies for quicker response -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iQIcBAEBCgAGBQJQlnMmAAoJEKY6WKPy4XVpwIoP/3eTxM4fkSaJZ4nyaMbDKCzE 4YF2csxFGzErWtwvRoXN3UUjoHryaJn/oOPil7ywWVD/jfa/1tHxaPdMijwiIBdT 3xbqF9rjh64UcCtJUeHei1QiCVpnRfZHHgMYqXVUmRgnFpLJ2maVLDE5clVZHr08 AZAIWafMwuMylNsOa14VshyIE9CPmIkrc2tr9IeYsu8b0DUM+qjggsQUlwA/w+Lh b7hqIt+ZEwi5grOpH5zt7QW1foP7aD35O6jEfLIQVMaEXX8AQ6wVeT4GQcelqcSv DUIsejjQE/wne73S1On7wgP2DcbCDp742N6QjNCC9j2OUowk4UOYpjEReuha1rZ8 puWzttRRbwZ7EiTgVXUf0mm1jQUFESSXorDq60O7PYlb7EOIDnORdOoR90dupqwx GJpiPP08Sxr+X7zLt7+/OlhfpB88+t9V+XO3gnpmBaf2hD9DrfpprwTUSWaLkDFJ bBiEdJNu7mVC3iM0iXrFI8FUsWqKVZwdx8nBQObPRet+8KTpDkK0roZmQEndRTYs qdT7lsXTWBYm7Fa7b66NNpt2MCbdKStKQeTpzQjRbf8FGidp2WErGjtugQ4e3agT HgvPEJDy3aKeQmahCSF6YOIEmq4WFEE0E6/Ux6DrPaMzTK70s1xE3l/QeSTFOoEQ mbbMwk0rlxQqPKW2eusL =Bp0/ -END PGP SIGNATURE- -- 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/6i8im9xsgc@news.researchut.com
Bug#691902: [squeeze-wheezy regression] Unable to shutdown via normal means
Hi, did it the lazy way and installed linux-image-3.2.0-2-amd64 3.2.13-1 followed by 3.2.14-1 from the snapshots. You might want to take a look at the changes between 13 and 14, because 3.2.13-1 is shutting down properly :) Methods tried: - selecting shutdown from Gnome - issuing shutdown -h 0 happy hunting ;) On Sat, Nov 3, 2012 at 8:07 PM, Jonathan Nieder jrnie...@gmail.com wrote: found 691902 linux/3.6.4-1~experimental.1 quit Janne Boman wrote: acpidump dmesg attached 3.6 from experimental did not work... Thanks for checking so quickly. By did not work, you mean that after booting that kernel, shutting down caused the computer to reboot, right? Please test the pre-compiled 3.2.13-1 and 3.2.14-1 packages from http://snapshot.debian.org/package/linux-2.6/, or if you prefer, please test the attached patch against a 3.7-rc3 or newer kernel, for example by using the following directions: 0. prerequisites apt-get install git build-essential 1. get the kernel history, if you don't already have it git clone \ git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 2. configure, build, test cd linux git fetch origin git checkout origin/master cp /boot/config-3.6-trunk-amd64 .config; # stock configuration scripts/config --disable DEBUG_INFO make localmodconfig; # optional: minimize configuration make deb-pkg; # optionally with -jnum for parallel build dpkg -i ../name of package; # as root shut down, unplug, remove battery, wait a few seconds restore power, boot shutdown -h now Hopefully it reproduces the bug, so 3. try the patch cd linux git revert 41c7f7424259 :wq make deb-pkg; # maybe with -j4 dpkg -i ../name of package; # as root ... power down completely, test it ... Hope that helps, Jonathan
Processed: tagging 692025
Processing commands for cont...@bugs.debian.org: # Can't tell whether there's even a bug here tags 692025 - upstream Bug #692025 [src:linux-2.6] linux: internet connection refused after new route Removed tag(s) upstream. thanks Stopping processing here. Please contact me if you need assistance. -- 692025: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692025 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.135205141214030.transcr...@bugs.debian.org
Bug#692025: linux: internet connection refused after new route
Giving up on this as the submitter won't explain himself. Ben. -- Ben Hutchings No political challenge can be met by shopping. - George Monbiot signature.asc Description: This is a digitally signed message part
Bug#692025: linux: internet connection refused after new route
Hi Patrik, Ben Hutchings wrote: On Thu, 2012-11-01 at 13:58 +0100, Patrik Nilsson wrote: I suspect this bug is when a task (i.e. ntp, virus updater, ...) tries to connect to the Internet through a socket using the first interface, holds it open, the kernel won't reroute to the new one and you need try to again. [...] Example: When one wlan connection is up and you try to connect throught an other one, you need to retry. I have tested both examples with lftp trying to connect to an IP-address and you cant' connect as long as lftp's socket is in effect. Please explain in more detail what you're doing: - All the commands you run to reconfigure and use the network - The routing table (as shown by 'ip r') after each reconfiguration I suspect there was a miscommunication here: if I understand correctly, Ben was looking for a simple sequence of steps and, for each step, a routing table from after that step. This would help him to understand what was happening when you ran into this problem. Perhaps he could run similar steps in a similar setup and compare, to track down where the problem lies. See http://www.chiark.greenend.org.uk/~sgtatham/bugs.html for more context. Thanks for your patience, 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/20121104180006.GA28816@elie.Belkin
Bug#691902: [squeeze-wheezy regression] Unable to shutdown via normal means
found 691902 linux-2.6/3.2.14-1 quit Janne Boman wrote: did it the lazy way and installed linux-image-3.2.0-2-amd64 3.2.13-1 followed by 3.2.14-1 from the snapshots. You might want to take a look at the changes between 13 and 14, because 3.2.13-1 is shutting down properly :) \o/ Let's take this upstream. I'll send instructions after breakfast. Ciao, 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/20121104181942.GB28414@elie.Belkin
Processed: Re: [squeeze-wheezy regression] Unable to shutdown via normal means
Processing commands for cont...@bugs.debian.org: found 691902 linux-2.6/3.2.14-1 Bug #691902 [src:linux] Unable to shutdown Debian Wheezy via normal means Marked as found in versions linux-2.6/3.2.14-1. quit Stopping processing here. Please contact me if you need assistance. -- 691902: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691902 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.135205319426451.transcr...@bugs.debian.org
Bug#692025: linux: internet connection refused after new route
On 11/04/2012 07:00 PM, Jonathan Nieder wrote: Hi Patrik, I suspect there was a miscommunication here: if I understand correctly, Ben was looking for a simple sequence of steps and, for each step, a routing table from after that step. This would help him to understand what was happening when you ran into this problem. Perhaps he could run similar steps in a similar setup and compare, to track down where the problem lies. See http://www.chiark.greenend.org.uk/~sgtatham/bugs.html for more context. Thanks for your patience, and hope that helps. Jonathan Hi Jonathan, I would like to help, but the difference of what happens when it works and doesn't is seemingly none. No error messages or anything else is shown: The connection just doesn't work when I try it. It is why I suspect that if a (background) program holds a socket open, the kernel can't set the route. Although it reports the correct route. This error has also happened when I started Firefox to early and it checks for updates. When this error happens, I retry the connection (ctrl+c for openvpn and run it again). Sometimes I need to retry several (3-4) times, but usually one retry is enough. I have tested this bug with two different providers of openvpn-services and there is no difference. It has of course was easier to help the bug hunting, when the same error always happens in a sequence. Do you have any kind of dump program, to report all the status of all connections, which also reports the true state of the kernel? This error also exists in Ubuntu 11.04. (I haven't been using any later.) Best regards, Patrik -- 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/5096cb81.20...@gmail.com
Bug#550534: iwl4965 0000:03:00.0: Microcode SW error detected. Restarting 0x82000000.
Hello, I get the same errors that renders my network connection useless when this happens. I have a Thinkpad T61 and am tracking testing. What I can add is that this only seems to happen when connecting to my cisco AIR-AP1121G-E-K9 accesspoint. It does not seems to occur when using my FRITZ!Box Fon WLAN 7390. [598216.014608] iwl4965 :03:00.0: Microcode SW error detected. Restarting 0x8200. [598216.014612] iwl4965 :03:00.0: Loaded firmware version: 228.61.2.24 [598216.014628] iwl4965 :03:00.0: Start IWL Error Log Dump: [598216.014630] iwl4965 :03:00.0: Status: 0x000213E4, count: 5 [598216.014777] iwl4965 :03:00.0: Desc Time data1 data2 line [598216.014780] iwl4965 :03:00.0: FH_ERROR (0x000C) 3967722153 0x0008 0x0313 208 [598216.014783] iwl4965 :03:00.0: pc blink1 blink2 ilink1 ilink2 hcmd [598216.014786] iwl4965 :03:00.0: 0x0046C 0x05CB2 0x004C2 0x006DE 0x018B8 0x285001C [598216.014788] iwl4965 :03:00.0: FH register values: [598216.014802] iwl4965 :03:00.0: FH_RSCSR_CHNL0_STTS_WPTR_REG: 0X09373900 [598216.014816] iwl4965 :03:00.0: FH_RSCSR_CHNL0_RBDCB_BASE_REG: 0X00646f00 [598216.014830] iwl4965 :03:00.0: FH_RSCSR_CHNL0_WPTR: 0X0068 [598216.014843] iwl4965 :03:00.0: FH_MEM_RCSR_CHNL0_CONFIG_REG: 0X00819000 [598216.014857] iwl4965 :03:00.0: FH_MEM_RSSR_SHARED_CTRL_REG: 0X003c [598216.014870] iwl4965 :03:00.0: FH_MEM_RSSR_RX_STATUS_REG: 0X0313 [598216.014884] iwl4965 :03:00.0: FH_MEM_RSSR_RX_ENABLE_ERR_IRQ2DRV: 0X [598216.014897] iwl4965 :03:00.0: FH_TSSR_TX_STATUS_REG: 0X07ff0002 [598216.014911] iwl4965 :03:00.0: FH_TSSR_TX_ERROR_REG: 0X [598216.015157] ieee80211 phy1: Hardware restart was requested -- 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/5096d138.4030...@vrielink.net
Bug#689420: (no subject)
Hi Ben: I appreciate your debugging attempts a lot. Unfortunately I have no idea about the kernel internals like cache_alloc_refill(). I'm sending you two fotos from different boot attempts in hope that this will give you more information. One (BUG_acpi_off.jpg) shows the first serious error message, here, displaying of BUG from snd_hda_codec_hdmi (if I recollect correctly, booted with acpi=off). Another (second127.jpg) shows the state at second 127 just after Foto-0171 but before Foto-0172 (booted without acpi=off, without quiet, and with boot_delay=300) I am sorry for the quality, but you can recongnize, e.g., someone saying SECURITY FREEZE LOCK and other strange messages. kernel.sysrq = 1 This did not change anything: On pressing the key combination I still get the message that the operation is disabled. Can you tell me the model of laptop you are using? DELL Precision M 6700. There is a rumour that RHEL was running on such laptops. I have no idea about the kernel they were using. Can you also test Linux 3.6.6 when it is available (it should be in experimental in a few days). Ok, I'll wait for 3.6.6. -- 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/1352062205.956102.27680.14...@saddam1.rambler.ru
Bug#692234: Intel HD 4000 (Ivy Bridge) graphics freeze
I am currently running kernel 3.2.32-1 from Sid and intend to run till I get freezes. That happened already 1 hour ago. I was watching a HTML5 video on YouTube when machine froze totally, even SysRq doesn't work. Sound was looping the last fraction of a second endlessly. Power consumtion up at 80 watts! Hard reset took almost a minute till it responded (as already described in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689268). I now installed kernel 3.3.0-rc6-amd64 - we'll see. P.S.: probably watching videos is a good trigger? -- 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/5096dfed.6030...@gmx.net
Bug#692234: Intel HD 4000 (Ivy Bridge) graphics freeze
Seems this kernel has full support for Ivy Bridge and HD4000 grapkics and H77 chipset compared to 3.2.0: 'cat /var/log/kern.log | grep RC6' [drm:intel_enable_rc6], RC6 enabled [drm:intel_enable_rc6], RC6 and deep RC6 enabled [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp off [drm:intel_enable_rc6], RC6 enabled 'dmesg | grep HDA' input: HDA Digital PCBeep as /devices/pci:00/:00:1b.0/input/input7 input: HDA Intel PCH Line as /devices/pci:00/:00:1b.0/sound/card0/input8 input: HDA Intel PCH Front Mic as /devices/pci:00/:00:1b.0/sound/card0/input9 input: HDA Intel PCH Rear Mic as /devices/pci:00/:00:1b.0/sound/card0/input10 input: HDA Intel PCH Front Headphone as /devices/pci:00/:00:1b.0/sound/card0/input11 input: HDA Intel PCH Line Out CLFE as /devices/pci:00/:00:1b.0/sound/card0/input12 input: HDA Intel PCH Line Out Surround as /devices/pci:00/:00:1b.0/sound/card0/input13 input: HDA Intel PCH Line Out Front as /devices/pci:00/:00:1b.0/sound/card0/input14 I'll report as soon as I get any freeze, Ingo -- 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/5096e83f.7030...@gmx.net
Bug#684265: Bug#690515: Still with us -- still in Beta3
On Oct 14, 2012, at 11:55 PM, Rick Thomas wrote: On Sep 24, 2012, at 6:26 AM, Milan Kupcevic wrote: Please file a separate debian-installer bug report for problems related to finding other OS's on LVM partitions. Milan OK, here it is: Bug#690515 I hope it's an easy fix. It would be a shame to see it get into beta3... Rick Well... The bug made it into Beta3. [)-:] I just tested it with the Beta3 AMD64 DVD-1 (no repository servers -- to make sure I got just Beta3 and not the latest updates.) On my machine with three Debian root LVM partitions, it only found one (the one I was installing to). After finishing installing and rebooting into the installed system, update-grub does find the other partitions and it does the right thing. I'm happy to help by testing anything you suggest. That's what I keep this machine for. If you think it's a missing module, as it was with 684265, please point me to the module, and I'll test it. Thanks! Rick -- 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/b1566131-1c92-442d-8c04-91b7eef49...@pobox.com
Bug#681743:
At least in my case this is an upstream bug – I tested this with the vanilla kernel v3.6.4 and got the same results. -- 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/1352076045.3917.3.camel@rosa
Bug#681743: i915: display backlight brightness initially set to zero on boot
Hi Stefan, Stefan Nagy wrote: [Subject: (no subject)] Please keep in mind that these appear as emails in a crowded inbox, so the subject line can be a good place to put valuable context. At least in my case this is an upstream bug – I tested this with the vanilla kernel v3.6.4 and got the same results. Unless you have the same machine model as Gedalya (HP dm4t-1200 laptop), please file a separate bug. We can merge them if they seem to have the same cause. Thanks for testing, 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/20121105013614.GA1784@elie.Belkin
Bug#683695: Still exists in Wheezy Beta3
Hi, Fei Qi wrote: I installed wheezy-beta3-amd64 using CD1 on a machine with a NV GTS 450 card. The kernel failed to boot stopping at populating /dev. With the same installation, if I move the hard disk to another computer with a NV GTX 460 card, the system works well and starts GNOME 3. Please file a separate bug using the following command: reportbug linux-image-$(uname -r) 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/20121105013917.GA6187@elie.Belkin
Bug#692025: linux: internet connection refused after new route
Patrik Nilsson wrote: No error messages or anything else is shown: The connection just doesn't work when I try it. It is why I suspect that if a (background) program holds a socket open, the kernel can't set the route. Although it reports the correct route. I don't know anything about these things --- Ben is the networking expert here. :) Anyway, could you send ip r output from before and after connecting to your openvpn server, just to humor us? Also could you strace a program that tries to connect and fails in this scenario, so we can see what syscalls it makes and what response the kernel gives? 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/20121105015923.GA6277@elie.Belkin
Bug#692324: [3.2.32-3.6.4 regression] powerpc: Oops and hang at boot: Unable to handle kernel paging request for data at address 0x0000000c
Daniel Kahn Gillmor wrote: This machine works fine booting the wheezy kernel (3.2.0-4-powerpc 3.2.32-1) via grub 2.00-7. However, when I tried booting this machine to the 3.6 kernel in experimental, via grub 2.00-7, the machine hung on boot and displayed the Oops and backtrace shown in the attached image (apologies for the low resolution of my webcam). Quick inexact transcription: | [info] Loading kernel module loop. | [info] Loading kernel module snd-powermac. | [ 17.51 237] i2c i2c-7: i2c-powermac: modalias failure on /wmi- 0f00/i2c0f0001000/ 01c0 | [ 17.7 2150] i2c i2c-4: Failed to register i2c client request at 0x35 (-16) | [ 17.73] unable to handle kernel paging request for data at address 0x000c | [ 17.730292] Faulting instruction address: 0xf2cdeb10 | [ 17.734 61] Oops: kernel access of bad area, sig: 11 [01] | [ 17.73 3 ] PowerMac | [ 17.73 7 ] Modules linked in: snd_aoa_codec_tas snd_aoa i2c_powermac snd_powermac loop fireware_sbp2 snd_aoa_ | soundbus snd_pcm_oss snd_mixer_oss snd_pcm snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd | _timer snd soundcore evdev ext3 mbcache jbd hid_generic usbhid hid md_mod sg sd_mod crc_t10dif sr_mod cdrom ohci | rewire_ohcigen usbcore firewire_core crc_itu_t sungem_phy usb_common | [ 17.73 651] NIP: f2cde630 LR: f2cd47b0 CTR: f2cdf70 | [ 17.736815] REGS: ef52ba60 TRAP: Not tainted (3.6-trunk-powerpc Debian 3.6.4-1~experimental.1) | [ 17.7371 4] MSR: 3032 EE, E,IR,DR,RI CR: 22002028 XER: | [ 17.737 63] DAR: 003c, DSISR: 4000 | [ 17.737589] TASK = ef9294f0[17] 'kworker/ :1' THREAD: ef52a000 | : | : | : | : | [ 17.735 29] RIP [f2cdeb10] tumbler_detect_headphone+0x4/0x20 [snd_powermac] | [ 17.739452] LR [f2cdf7b0] device_change_handler+0x30/0x1d0 [snd_powermac] | [ 17.733667] Call Trace: | [ 17.7357 3] [ef92bf10] [006f] 0xbf (unreliable) | [ 17.739966] [ef92bf30] [c004f200] process_one_work+0x260/0x3ac | [ 17.74016 ] [ef92bf60] [c004f2d4] worker_thread+0x2a0/0x5b4 | [ 17.740367] [ef92bfb0] [c00542b0] kthread+0x00/0x04 | [ 17.740 45] [ef92bff0] [c000 234] kernel_thread+0x4c/0x68 | [ 17.740731] instruction dump: | [ 17.74 401] 7c0903ab 60630011 38c0 4c000421 881f0006 5463fffe 39610010 7c630270 | [ 17.749103] 7c630034 5463d97e 4bffc5d4 00630374 8003003c 2f80 419c000c 3863003c | [ 17.757395] --[ end trace 7636e8c31427d89a ]--- -- 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/20121105033659.GA6371@elie.Belkin
Bug#692324: [3.2.32-3.6.4 regression] Oops and hang at boot: Unable to handle kernel paging request for data at address 0x0000000c
Daniel Kahn Gillmor wrote: This machine works fine booting the wheezy kernel (3.2.0-4-powerpc 3.2.32-1) via grub 2.00-7. However, when I tried booting this machine to the 3.6 kernel in experimental, via grub 2.00-7, the machine hung on boot and displayed the Oops and backtrace shown Please attach full dmesg output from a normal, successful boot for comparison. 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/20121105034057.GB6371@elie.Belkin
Bug#692025: linux: internet connection refused after new route
On Sun, 2012-11-04 at 17:59 -0800, Jonathan Nieder wrote: Patrik Nilsson wrote: No error messages or anything else is shown: The connection just doesn't work when I try it. It is why I suspect that if a (background) program holds a socket open, the kernel can't set the route. Although it reports the correct route. I don't know anything about these things --- Ben is the networking expert here. :) While the existence of a socket can make the kernel hold onto routing information that has otherwise been deleed, this is not supposed to affect routing for any new sockets. Ben. Anyway, could you send ip r output from before and after connecting to your openvpn server, just to humor us? Also could you strace a program that tries to connect and fails in this scenario, so we can see what syscalls it makes and what response the kernel gives? -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Bug#692333: initramfs-tools: update-initramfs creates absolute symlink to /boot/initrd.img-..
Package: initramfs-tools Version: 0.109 Severity: normal Dear Maintainer, After updating the kernel (via aptitude), update-initramfs is called to generate a new initrd.img file: update-initramfs: Generating /boot/initrd.img-3.2.0-4-686-pae Symlink /initrd.img is also created, but it points to /boot/initrd.img-.. rather than to boot/initrd.img-.. This causes a problem when, e.g., lilo is run with the filesystem mounted at /foo, in which case /foo/initrd.img points to the wrong location. (The kernel is set up correctly: /vmlinuz - boot/vmlinuz-..) -- Package-specific info: -- initramfs sizes -- /proc/cmdline auto BOOT_IMAGE=testing ro root=UUID=e1490160-b40c-4e12-b676-a88e347a22ab reboot=w -- resume # RESUME=/dev/sda5 RESUME='UUID=e42e1e36-27a7-46ef-a336-46eeb6d91e47' -- /proc/filesystems ext3 -- lsmod Module Size Used by dm_mod 57278 0 cpufreq_userspace 12520 0 cpufreq_powersave 12422 0 cpufreq_stats 12762 0 cpufreq_conservative12987 0 pci_stub 12397 1 vboxpci18713 0 vboxnetadp 25431 0 vboxnetflt 23231 0 vboxdrv 165027 3 vboxnetflt,vboxnetadp,vboxpci uinput 12991 1 ipt_LOG12533 9 xt_limit 12484 9 ipt_REJECT 12454 5 xt_state 12455 6 xt_tcpudp 12506 19 iptable_mangle 12488 0 iptable_nat12800 1 nf_nat 17924 1 iptable_nat nf_conntrack_ipv4 13726 9 nf_nat,iptable_nat nf_defrag_ipv4 12443 1 nf_conntrack_ipv4 nf_conntrack 43121 4 nf_conntrack_ipv4,nf_nat,iptable_nat,xt_state iptable_filter 12488 1 ip_tables 17079 3 iptable_filter,iptable_nat,iptable_mangle x_tables 18121 9 ip_tables,iptable_filter,iptable_nat,iptable_mangle,xt_tcpudp,xt_state,ipt_REJECT,xt_limit,ipt_LOG nfsd 173714 13 nfs 265779 5 nfs_acl12463 2 nfs,nfsd auth_rpcgss32143 2 nfs,nfsd fscache31978 1 nfs lockd 57255 2 nfs,nfsd sunrpc143853 33 lockd,auth_rpcgss,nfs_acl,nfs,nfsd asus_laptop18060 0 sparse_keymap 12680 1 asus_laptop input_polldev 12802 1 asus_laptop firewire_sbp2 17664 0 loop 17810 0 snd_hda_codec_si305412662 1 snd_hda_codec_realtek 142221 1 snd_hda_intel 21856 0 snd_hda_codec 63477 3 snd_hda_intel,snd_hda_codec_realtek,snd_hda_codec_si3054 snd_hwdep 12943 1 snd_hda_codec snd_pcm_oss36181 0 snd_mixer_oss 17668 1 snd_pcm_oss snd_pcm53390 4 snd_pcm_oss,snd_hda_codec,snd_hda_intel,snd_hda_codec_si3054 joydev 17010 0 snd_page_alloc 12867 2 snd_pcm,snd_hda_intel snd_seq_midi 12744 0 snd_seq_midi_event 13124 1 snd_seq_midi snd_rawmidi18376 1 snd_seq_midi arc4 12418 2 snd_seq39487 2 snd_seq_midi_event,snd_seq_midi uvcvideo 56896 0 videodev 61658 1 uvcvideo media 13692 2 videodev,uvcvideo snd_seq_device 13016 3 snd_seq,snd_rawmidi,snd_seq_midi snd_timer 22356 2 snd_seq,snd_pcm i915 307698 2 snd42691 12 snd_timer,snd_seq_device,snd_seq,snd_rawmidi,snd_pcm,snd_mixer_oss,snd_pcm_oss,snd_hwdep,snd_hda_codec,snd_hda_intel,snd_hda_codec_realtek,snd_hda_codec_si3054 sdhci_pci 13576 0 r592 17543 0 memstick 13434 1 r592 sdhci 22377 1 sdhci_pci uhci_hcd 22337 0 drm_kms_helper 22699 1 i915 psmouse54927 0 iwl496573683 0 r8169 41810 0 iwl_legacy 47020 1 iwl4965 mac80211 171359 2 iwl_legacy,iwl4965 acpi_cpufreq 12807 0 mii12595 1 r8169 sg 21476 0 sr_mod 17468 0 cdrom 34813 1 sr_mod firewire_ohci 26784 0 r852 17530 0 ata_generic12439 0 firewire_core 38719 2 firewire_ohci,firewire_sbp2 soundcore 12921 1 snd cfg80211 117454 3 mac80211,iwl_legacy,iwl4965 sm_common 16434 1 r852 nand 43624 2 sm_common,r852 nand_ecc 12412 1 nand rfkill 18516 2 cfg80211,asus_laptop crc_itu_t 12331 1 firewire_core nand_ids8209 1 nand ehci_hcd 35509 0 ata_piix 21175 0 i2c_i801 12670 0 mtd27561 2 nand,sm_common usbcore 104352 4 ehci_hcd,uhci_hcd,uvcvideo drm 134178 3 drm_kms_helper,i915 mmc_core 61993
Bug#692098: firmware-iwlwifi: iwlwifi firmware does not connect to wpa2 wireless
2012/11/2 Ben Hutchings b...@decadent.org.uk: Can you try using these commands (as root) to disable hardware encryption for WPA: rmmod iwlwifi modprobe iwlwifi swcrypto=1 Also try connecting with 802.11g: rmmod iwlwifi modprobe iwlwifi 11n_disable=1 Do either or both of these configurations work? Ben. thanks for the solution Ben, both works. my /etc/rc.local looks like below to get the wireless working on wpa encrypted network at my office: rmmod iwlwifi modprobe iwlwifi swcrypto=1 exit 0 -- Regards, Umarzuki Mochlis http://debmal.my -- 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/cahw9mbwfm5oztwpg+u_ouxcuvgunods2v5btuw+1l6oev71...@mail.gmail.com
Bug#692098: firmware-iwlwifi: iwlwifi firmware does not connect to wpa2 wireless
On Mon, 2012-11-05 at 12:16 +0800, Umarzuki Mochlis wrote: 2012/11/2 Ben Hutchings b...@decadent.org.uk: Can you try using these commands (as root) to disable hardware encryption for WPA: rmmod iwlwifi modprobe iwlwifi swcrypto=1 Also try connecting with 802.11g: rmmod iwlwifi modprobe iwlwifi 11n_disable=1 Do either or both of these configurations work? Ben. thanks for the solution Ben, both works. Well they are workarounds, not really solutions. my /etc/rc.local looks like below to get the wireless working on wpa encrypted network at my office: rmmod iwlwifi modprobe iwlwifi swcrypto=1 exit 0 It is better to put module options in a file under /etc/modprobe.d, as described in the modprobe.conf manual page. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Bug#550534: long lines
long, non-wrapped, lines of posting from Bart-Jan Vrielink [598216.014608] iwl4965 :03:00.0: Microcode SW error detected. Restarting 0x8200. [598216.014612] iwl4965 :03:00.0: Loaded firmware version: 228.61.2.24 [598216.014628] iwl4965 :03:00.0: Start IWL Error Log Dump: [598216.014630] iwl4965 :03:00.0: Status: 0x000213E4, count: 5 [598216.014777] iwl4965 :03:00.0: Desc Time data1 data2 line [598216.014780] iwl4965 :03:00.0: FH_ERROR (0x000C) 3967722153 0x0008 0x0313 208 [598216.014783] iwl4965 :03:00.0: pc blink1 blink2 ilink1 ilink2 hcmd [598216.014786] iwl4965 :03:00.0: 0x0046C 0x05CB2 0x004C2 0x006DE 0x018B8 0x285001C [598216.014788] iwl4965 :03:00.0: FH register values: [598216.014802] iwl4965 :03:00.0: FH_RSCSR_CHNL0_STTS_WPTR_REG: 0X09373900 [598216.014816] iwl4965 :03:00.0: FH_RSCSR_CHNL0_RBDCB_BASE_REG: 0X00646f00 [598216.014830] iwl4965 :03:00.0: FH_RSCSR_CHNL0_WPTR: 0X0068 [598216.014843] iwl4965 :03:00.0: FH_MEM_RCSR_CHNL0_CONFIG_REG: 0X00819000 [598216.014857] iwl4965 :03:00.0: FH_MEM_RSSR_SHARED_CTRL_REG: 0X003c [598216.014870] iwl4965 :03:00.0: FH_MEM_RSSR_RX_STATUS_REG: 0X0313 [598216.014884] iwl4965 :03:00.0: FH_MEM_RSSR_RX_ENABLE_ERR_IRQ2DRV: 0X [598216.014897] iwl4965 :03:00.0: FH_TSSR_TX_STATUS_REG: 0X07ff0002 [598216.014911] iwl4965 :03:00.0: FH_TSSR_TX_ERROR_REG: 0X [598216.015157] ieee80211 phy1: Hardware restart was requested HTH -- 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/20121105065055.ga22...@gpm.stappers.nl
Bug#692333: marked as done (initramfs-tools: update-initramfs creates absolute symlink to /boot/initrd.img-..)
Your message dated Mon, 5 Nov 2012 07:34:37 + with message-id 20121105073437.gl10...@vostochny.stro.at and subject line Re: Bug#692333: initramfs-tools: update-initramfs creates absolute symlink to /boot/initrd.img-.. has caused the Debian Bug report #692333, regarding initramfs-tools: update-initramfs creates absolute symlink to /boot/initrd.img-.. 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.) -- 692333: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692333 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: initramfs-tools Version: 0.109 Severity: normal Dear Maintainer, After updating the kernel (via aptitude), update-initramfs is called to generate a new initrd.img file: update-initramfs: Generating /boot/initrd.img-3.2.0-4-686-pae Symlink /initrd.img is also created, but it points to /boot/initrd.img-.. rather than to boot/initrd.img-.. This causes a problem when, e.g., lilo is run with the filesystem mounted at /foo, in which case /foo/initrd.img points to the wrong location. (The kernel is set up correctly: /vmlinuz - boot/vmlinuz-..) -- Package-specific info: -- initramfs sizes -- /proc/cmdline auto BOOT_IMAGE=testing ro root=UUID=e1490160-b40c-4e12-b676-a88e347a22ab reboot=w -- resume # RESUME=/dev/sda5 RESUME='UUID=e42e1e36-27a7-46ef-a336-46eeb6d91e47' -- /proc/filesystems ext3 -- lsmod Module Size Used by dm_mod 57278 0 cpufreq_userspace 12520 0 cpufreq_powersave 12422 0 cpufreq_stats 12762 0 cpufreq_conservative12987 0 pci_stub 12397 1 vboxpci18713 0 vboxnetadp 25431 0 vboxnetflt 23231 0 vboxdrv 165027 3 vboxnetflt,vboxnetadp,vboxpci uinput 12991 1 ipt_LOG12533 9 xt_limit 12484 9 ipt_REJECT 12454 5 xt_state 12455 6 xt_tcpudp 12506 19 iptable_mangle 12488 0 iptable_nat12800 1 nf_nat 17924 1 iptable_nat nf_conntrack_ipv4 13726 9 nf_nat,iptable_nat nf_defrag_ipv4 12443 1 nf_conntrack_ipv4 nf_conntrack 43121 4 nf_conntrack_ipv4,nf_nat,iptable_nat,xt_state iptable_filter 12488 1 ip_tables 17079 3 iptable_filter,iptable_nat,iptable_mangle x_tables 18121 9 ip_tables,iptable_filter,iptable_nat,iptable_mangle,xt_tcpudp,xt_state,ipt_REJECT,xt_limit,ipt_LOG nfsd 173714 13 nfs 265779 5 nfs_acl12463 2 nfs,nfsd auth_rpcgss32143 2 nfs,nfsd fscache31978 1 nfs lockd 57255 2 nfs,nfsd sunrpc143853 33 lockd,auth_rpcgss,nfs_acl,nfs,nfsd asus_laptop18060 0 sparse_keymap 12680 1 asus_laptop input_polldev 12802 1 asus_laptop firewire_sbp2 17664 0 loop 17810 0 snd_hda_codec_si305412662 1 snd_hda_codec_realtek 142221 1 snd_hda_intel 21856 0 snd_hda_codec 63477 3 snd_hda_intel,snd_hda_codec_realtek,snd_hda_codec_si3054 snd_hwdep 12943 1 snd_hda_codec snd_pcm_oss36181 0 snd_mixer_oss 17668 1 snd_pcm_oss snd_pcm53390 4 snd_pcm_oss,snd_hda_codec,snd_hda_intel,snd_hda_codec_si3054 joydev 17010 0 snd_page_alloc 12867 2 snd_pcm,snd_hda_intel snd_seq_midi 12744 0 snd_seq_midi_event 13124 1 snd_seq_midi snd_rawmidi18376 1 snd_seq_midi arc4 12418 2 snd_seq39487 2 snd_seq_midi_event,snd_seq_midi uvcvideo 56896 0 videodev 61658 1 uvcvideo media 13692 2 videodev,uvcvideo snd_seq_device 13016 3 snd_seq,snd_rawmidi,snd_seq_midi snd_timer 22356 2 snd_seq,snd_pcm i915 307698 2 snd42691 12 snd_timer,snd_seq_device,snd_seq,snd_rawmidi,snd_pcm,snd_mixer_oss,snd_pcm_oss,snd_hwdep,snd_hda_codec,snd_hda_intel,snd_hda_codec_realtek,snd_hda_codec_si3054 sdhci_pci 13576 0 r592 17543 0 memstick 13434 1 r592 sdhci 22377 1 sdhci_pci uhci_hcd 22337 0 drm_kms_helper 22699 1 i915 psmouse54927 0 iwl496573683 0 r8169 41810 0 iwl_legacy 47020 1 iwl4965 mac80211 171359 2 iwl_legacy,iwl4965 acpi_cpufreq 12807
