I'm having what appears to be the same problem with a few differences of note:
- Lenovo T480 (original report was for a T580)
- Linux kernel 4.19.0-6-amd64
- lxdm
- xfce4
- External monitor connected via HDMI
Shannon C. Dealy | DeaTech Research Inc.
de...@deatech.com
(800) 467-5820 | - Natural Building Instruction -
or: (541) 929-4089 | www.deatech.com
On Thu, 15 Aug 2013, Moritz Muehlenhoff wrote:
reassign 628444 src:linux
thanks
On Wed, Mar 14, 2012 at 08:37:17PM -0700, Shannon Dealy wrote:
Like others, the problems seemed to star
On Fri, 16 Mar 2012, Bjørn Mork wrote:
Shannon Dealy writes:
I created a file "/etc/modprobe.d/iwlagn.conf" and placed the
following line in it:
options iwlagn 11n_disable=1 11n_disable50=1
Note that the 11n_disable50 options was removed in 3.0 and the iwlagn
module was
Found these two pages discussing what appears to be the same problem:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/575492
http://ubuntuforums.org/showthread.php?t=1470820
in at least one case, it is definitely the same problem ("deep sleep"
message shows up in the posted log). N
Like others, the problems seemed to start around 2.6.39.
Thought I should note here, my system showed this problem with 2.6.36
through 2.6.39. It seems to have stopped showing the problem (possibly
due to a memory upgrade many months ago), but it still has chronic
instability of the conne
Thought I should note that the addition of "pcie_aspm=off" to my command
line has not cured my link problems, but it has changed the behavior of
the problems. It is now more likely to recover on its own without me
reloading the driver and when I do reload the driver, it is far more
likely to
Thought I should note that the addition of "pcie_aspm=off" to my command
line has not cured my link problems, but it has changed the behavior of
the problems. It is now more likely to recover on its own without me
reloading the driver and when I do reload the driver, it is far more
likely to
On Thu, 1 Mar 2012, Ben Hutchings wrote:
On Wed, 2012-02-29 at 21:09 -0800, Shannon Dealy wrote:
[...]
Actually, a RAM upgrade can most definitely have an impact. Replacing any
hardware on the bus changes bus loads, propagation delays and overall
timing of the bus.
[...]
Unfortunately, I&#
On Wed, 29 Feb 2012, Juha Jäykkä wrote:
that the memory slots and mini-pcie slots are behind the same cover in
the X201 as well? Replugging it seems like a good idea...
I wish they were! They are in X4? and X30? but not X200s, where I had to
remove the keyboard and handrest to get to the card.
On Wed, 29 Feb 2012, Bjørn Mork wrote:
Juha Jäykkä writes:
One thing just occurred to me: I added 2 GB of memory (total 4 GB) at about
the time these problems started. I cannot say for sure the problems did not
start earlier, but it is quite possible they started after! (Please do not
[snip]
On Sun, 26 Feb 2012, Juha Jäykkä wrote:
[snip]
Shannon: FWIF, I have now rebooted with pci_aspm=off and we'll see what
happens.
Ben: I also replugged the wifi card.
I have also rebooted with pci_aspm=off, and while it has only been a few
hours, I have not seen any of the usual irratic behavi
On Fri, 24 Feb 2012, Juha Jäykkä wrote:
[snip]
I never had any issues with hibernate or suspend and certainly neither was
ever needed to trigger the bug. For example yesterday, I hit the bug after
about 3 hours without ever putting the laptop off my lap meanwhile.
It wasn't required to trigger
On Sun, 26 Feb 2012, Ben Hutchings wrote:
[snip]
No, wasn't even aware of its existance. System shows it is currently at
"default" unfortunately, the debug kernel I am currently running has the
pcie_aspm regression which prevents it from being changed without
rebooting which is rather time cons
On Sun, 26 Feb 2012, Ben Hutchings wrote:
On Thu, 2012-02-23 at 17:59 -0800, Shannon Dealy wrote:
[...]
some point, outside software MUST be providing bogus information to the
driver. I say this because after the deep sleep bug occcurs and the
hardware has been power cycled (through hibernate
On Wed, 22 Feb 2012, Juha Jäykkä wrote:
Replying to myself, really, but two new observations:
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.
As much as I thought and hoped this was true, it is n
On Sat, 11 Feb 2012, Juha Jäykkä wrote:
Hi Shannon!
What is the status of the fix from Intel? I have the same problem since
upgrading to 3.x series and it is VERY annoying - only way I can fix it is
rebooting the kernel, so it really seems a kernel bug. Hibernating the system
and doing a full p
On Wed, 23 Nov 2011, Jonathan Nieder wrote:
Shannon Dealy wrote:
A developer at Intel contacted me regarding this bug the other day (he was
following up on a similar bug report from another source) and I am working
with him on the problem (currently doing a debug build of the module to
A developer at Intel contacted me regarding this bug the other day (he
was following up on a similar bug report from another source) and I
am working with him on the problem (currently doing a debug build of the
module to collect data on what is happening).
Shannon C. Dealy |
On Sat, 17 Sep 2011, maximilian attems wrote:
I wasn't aware that the 3.0 kernels were out until you sent this
message. Unfortunately, since this bug takes time to manifest, it
will require that I run with 3.0 as my default kernel, this means I
have to get vmware to run with it (since I use it h
On Tue, 13 Sep 2011, maximilian attems wrote:
tags 628444 moreinfo
stop
This bug actually applies to all Debian kernels I have tried including
2.6.36, 2.6.37, 2.6.38, and 2.6,39
Did you try since newer 3.0 images, how are they performing?
thank you
I wasn't aware that the 3.0 kernels were
Oops, the previously closed bug I mentioned should have been:
#589353
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589353
NOT #589383
Sorry for the confusion.
Shannon C. Dealy | DeaTech Research Inc.
de...@deatech.com | - Custom Software Development -
Package: linux-2.6
Version: 2.6.39-1
Severity: important
After some arbitrary period of use, wifi fails and errors show up in syslog
indicating "MAC is in deep sleep" after which nothing can be done to restore
wifi functionality other than rebooting the system. In most (possibly all)
cases, the
22 matches
Mail list logo
