Bug#649412:
fixed 649412 linux-2.6/3.2.9-1 thanks Hi, The iwlwifi fix for #651199 that went into 3.2.9-1 seems to have fixed this for me. As described in the upstream bug report, using swcrypto=1 was a workaround. Since 3.2.9-1, I've removed that from the GRUB command line (and ran update-grub, reboot, obviously), and the problem seems to be fixed indeed. I haven't closed the upstream bug yet as I'm unsure what fixed it (seems to be Johannes' patch, but I haven't checked in detail). Not sure if closing the upstream bug report would automagically close the BTS report. Feel free to mark as done if that's the correct procedure. :-) Thanks a bunch, -- 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/canvyna9gay19qewqg7vdiikwv0orziqydzzcygsbnb8d7im...@mail.gmail.com
Bug#649412: linux-image-3.1.0-1-amd64: No route to host after some time with iwlagn and kernel 3.1
Hi, 2011/11/26 Ben Hutchings b...@decadent.org.uk: On Sun, 2011-11-20 at 16:58 -0200, Fernando Tarlá Cardoso Lemos wrote: Package: linux-2.6 Version: 3.1.1-1 Severity: normal After upgrading to 3.1, I get somewhat periodic network problems with iwlagn. This is a Dell laptop (Vostro 3450) with a Centrino 1030 BGN interface. I'm using a 802.11g (not 802.11n) router with WPA2 authentication. The router advertises the SSID. I haven't had the opportunity to test this with other routers yet. I boot up, and after a few minutes (usually between 400 and 1000 seconds after I've connected), I get Destination Host Unreachable network errors: It looks to me as if you accidentally pressed some key combination that turns wifi off and on: [...] [ 930.958778] keyboard: can't emulate rawmode for keycode 240 [ 930.958808] keyboard: can't emulate rawmode for keycode 240 [ 930.964597] iwlagn :01:00.0: RF_KILL bit toggled to disable radio. [ 930.964762] iwlagn :01:00.0: Not sending command - RF KILL [ 930.964770] iwlagn :01:00.0: Error sending REPLY_QOS_PARAM: enqueue_hcmd failed: -5 [...] [ 932.827396] keyboard: can't emulate rawmode for keycode 240 [ 932.827427] keyboard: can't emulate rawmode for keycode 240 [ 932.834164] iwlagn :01:00.0: RF_KILL bit toggled to enable radio. [...] Is that possible? Otherwise, it's also conceivable that these events are being triggered wrongly. Nope, I pressed it on purpose so I could fill the bug report. Fn + F2 triggers rfkill, if I press that twice I get a reconnection and then I get connectivity back. I did this one or twice so I could gather enough information to submit the report. The first time I lose connectivity, there are no rfkill-related messages. I couldn't find anything in the logs that could point out to the problem, unfortunately. :-( Regards, -- 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/canvyna9jmsex7cp+m9aunruc9spdfi-2kt5hpvconabsusd...@mail.gmail.com
Bug#580601:
I can no longer reproduce this in 2.6.37. After the update to 2.6.37, I commented out options i915 powersave=0 from modprobe.d and used update-initramfs -k all -u. That was more than a week ago (probably two weeks ago), and so far I haven't seen any corruption at all. I've been switching between 2.6.36 and 2.6.37 recently so that I can use VirtualBox (linux-kbuild-2.6.37 isn't released yet, so I can't compile virtualbox-ose-dkms for 2.6.37), and every time I'm booted into 2.6.36 I can see the corruption every now and then, as I described in this report. It looks like it's fixed in 2.6.37 for me, then. :-) 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/AANLkTinSbWu2VM6V9u-Pgz+c=hrmecjuvjmarl-xa...@mail.gmail.com
Bug#602009: linux-image-2.6.36-trunk-amd64: i915.powersave option is not respected in 2.6.36
Hello, On Tue, Nov 2, 2010 at 1:10 AM, Fernando Lemos fernando...@gmail.com wrote: Thanks for your prompt response. Done, it's bug #31311: https://bugs.freedesktop.org/show_bug.cgi?id=31311 Chris Wilson's reply shed some light on this and I now understand what's going on. I commented up i915.powersave=0 to test if #580601 was gone in 2.6.36, and that made into the initrd, as I found out after examining it. Running update-initramfs -k all -u solved the issue. In 2.6.36, as Chris Wilson stated, /sys/modules/i915/parameters/powersave is 0400. I'm led to believe that at some point in initialization, after the root filesystem is mounted, modprobe goes over /etc/modprobe.d again to reset the options. This might be why leaving i915.powersave=0 commented out in the initrd worked before 2.6.36. If this is the case, then it might be nice to have the commit mentioned in the f.d.o bug report backported, perhaps. It could also be that my other initrds simply didn't have that option commented out. Anyways, the issue is now solved for me: ferna...@vostro:~$ sudo cat /sys/module/i915/parameters/powersave 0 ferna...@vostro:~$ uname -a Linux vostro 2.6.36-trunk-amd64 #1 SMP Wed Oct 27 14:28:29 UTC 2010 x86_64 GNU/Linux ferna...@vostro:~$ Please feel free to close/archive/invalidate this bug report. Sorry for any inconvenience and thanks for your time. Regards, -- 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/aanlktimade9h92bp=_4ansmdhz2ljg6figa2kf5xe...@mail.gmail.com
Bug#602009: linux-image-2.6.36-trunk-amd64: i915.powersave option is not respected in 2.6.36
Hi, Ben 2010/11/1 Ben Hutchings b...@decadent.org.uk: Please report this upstream on https://bugs.freedesktop.org under product 'DRI', component 'DRM/Intel'. Let us know the bug number or URL so we can track it. Thanks for your prompt response. Done, it's bug #31311: https://bugs.freedesktop.org/show_bug.cgi?id=31311 Also, please comment on http://bugs.freedesktop.org/show_bug.cgi?id=27589 (same as #580601) that that bug is still present in 2.6.36, and add yourself to the cc list so you can answer questions from the upstream maintainers. Done and done. Regards, -- 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/aanlktindnvckp5j1wz8e9+gvuahlpxh_1ge6t7vo-...@mail.gmail.com
Bug#580601: [drm/i915] flickering and artifacts on (some?) gm45 with powersave' from 'xserver-xorg-core: Flickering and artifacts after update, using intel driver
Some days ago linux-image-2.6.32-14 was released, and one of the entries in the changelog says: * Add drm changes from stable 2.6.33.5: - i915: Disable FBC on 915GM and 945GM (Closes: #582427) I think that's the patch: https://patchwork.kernel.org/patch/86999/ #582427 could be related to this issue. However, I just booted into 2.6.32-15 with powersave=1 commented out (this time I'm using modprobe.d instead of defaults/grub, and I re-ran update-grub afterwards to make sure I really was not setting powersave=0 or powersave=1) and the problem is still there (the screen flickered several times in just a few minutes). -- 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/aanlktim0zlgy3oufi7i-fr4-qpppqmbxw_-fz92x1...@mail.gmail.com
