Bug#884638: Bug #884638
This bug makes my Lenovo laptop with Intel graphics essentially unusable with the 4.9.0-4 kernel. The flickering is every few seconds and some operations like maximizing a window can drive the screen to flicker constantly. Downgrading to 4.9.0-3 solves the problem.
Bug#628444: Also in stable, now
To add to my previous report: of the workrounds described above, the 11n_disable suggestion does absolutely nothing for me. However, pcie_aspm=off as a boot option does greatly reduce the extent of the problem. (Sadly it doesn't eliminate it completely -- I just had a repeat of the problem apparently triggered by moving from mains to battery power. But that's the first time in a week of use since I made the change to the command line.) I'd suggest therefore that the recent change to the kernel in stable (which I believe to be the only plausible explanation for my experience) is one that affects the PCIe power saving controlled by this command line option. -- 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/CANGLxoZPLw1YZxQa=UEOBHPOPX27=e8rtqfv_vd1l8gnnd2...@mail.gmail.com
Bug#628444: Also in stable, now
Hi all I'm running stable (squeeze), with the standard 2.6.32-5 kernel, on a Lenovo Thinkpad X200 tablet; lspci says 03:00.0 Network controller: Intel Corporation Ultimate N WiFi Link 5300 and the module is iwlagn, obviously. The machine has been running squeeze since it was released without any problems. But in the last few days, I have started having very frequent problems along the lines described. May 31 06:12:32 rigel kernel: [ 1029.842353] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready May 31 06:12:41 rigel kernel: [ 1038.685375] iwlagn :03:00.0: iwl_tx_agg_start on ra = a0:21:b7:4d:3d:9c tid = 0 May 31 06:14:43 rigel kernel: [ 1161.316130] No probe response from AP a0:21:b7:4d:3d:9c after 500ms, disconnecting. May 31 06:14:43 rigel kernel: [ 1161.320094] iwlagn :03:00.0: MAC is in deep sleep!. CSR_GP_CNTRL = 0x May 31 06:14:43 rigel kernel: [ 1161.320094] iwlagn :03:00.0: MAC is in deep sleep!. CSR_GP_CNTRL = 0x [...] At this point rmmod/modprobe do nothing at all, and the only solution is a reboot. This particular one was on wakeup, but frequently it's in the middle of normal use. Nothing's changed with the hardware: I did have the keyboard off a few weeks ago to remove a stuck stylus, but I don't think the timing is quite right to suggest I unseated the card at that point; also, the machine dual-boots into Windows, and I see no problems there, though I use it much less. However, I do keep the system updated, and I seem to recall that there was a new kernel *and firmware* version a little while ago as part of the 6.0.5 release. That was on May 12, and my problems started, according to the logs, after a reboot on May 14! I post this in the hope that someone might have some insight as a result of knowing what's changed in the latest stable release. In the meantime, I am going to try some of the workrounds described in this thread. Cheers Martin -- 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/CANGLxoas6uG26JCz9UaAKkUauNbQBVmfA6q0SE=xqe9l+ga...@mail.gmail.com
Bug#628444: Also in stable, now
On 31 May 2012 14:12, Ben Hutchings b...@decadent.org.uk wrote: There was no change to any firmware or to this driver in the 6.0.5 release. So what's your explanation for the problem appearing immediately after the 6.0.5 release was installed? Just coincidence? I'm not trying to make any point in particular, just curious. Anyway, as the problem is now present in stable as well, I hope someone can find a fix. It makes the machine pretty much unusable for its intended purpose. Cheers Martin -- 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/CANGLxob5bN7GS4ERPJDEg5yKwP_G893GTCQjWg=22blntkg...@mail.gmail.com
Bug#628444: Also in stable, now
On 31 May 2012 18:42, Ben Hutchings b...@decadent.org.uk wrote: You rebooted. Problems often show up after a reboot. Yeah: just to provide some additional information, I had actually rebooted the machine on previous occasions since first installing stable without this problem showing up. I don't think it's been established that the problem you're seeing is the same as the one reported here. OK: what information would you suggest I try to obtain in order to establish that? Martin -- 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/canglxoz91c20b-urklpbkyeln8d+9vyrnbjrrdc1o2a5bps...@mail.gmail.com
