Hi Shannon and others,
First up, my sincere apologies for not responding earlier. I've been swamped
with other work, and have had a chance to look at this only now.
I just got caught up with the email thread, and it appears that you're seeing a
problem with the following configuration most
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
Juha Jäykkä ju...@iki.fi 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
tell Lenovo that I added the
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. Most annoying.
Nevertheless, the RAM
On Wed, 29 Feb 2012, Bjørn Mork wrote:
Juha Jäykkä ju...@iki.fi 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
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
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'm not current on the hardware/buses
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'm
On Sat, 2012-02-25 at 23:48 -0800, Shannon Dealy wrote:
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
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
For a complete power-cycle, you may need to remove both the power cord
and the battery. I don't think the Intel wireless cards have any
Sure, I did: detach the cord and battery, wait ten minutes, then plug them
back in. No use.
The log messages you sent are indicative of a total failure of
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
It wasn't required to trigger the problem on my system either, but it
seemed to happen a lot more often in the first few minutes after coming
out of hibernation.
Sorry, what I meant to say is that not hibernating does not help me at all.
an illusion due to the irratic nature of the problem).
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
On Sun, 2012-02-26 at 22:31 +, Juha Jäykkä wrote:
For a complete power-cycle, you may need to remove both the power cord
and the battery. I don't think the Intel wireless cards have any
Sure, I did: detach the cord and battery, wait ten minutes, then plug them
back in. No use.
On Thu, 2012-02-23 at 17:59 -0800, Shannon Dealy wrote:
[...]
While the firmware may play a role in the problem, at its core, there
are issues that must be occurring outside the firmware or even the iwlagn
driver, namely a kernel bug or bug in a supporting driver - there is
simply no way
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
tried at least 5 different versions. I have almost completely stopped
using hibernate (suspend only) on my system and have not seen the problem
in a long time and for my system at least, hibernate seems to be related
I never thought it was a firmware issue before, so I never paid any
0.35, and if I still see this, I will go back to ~0.30 to see if that
fixes the issue.
Down to 0.33, no help if running kernel 3.2. Now testing 0.33 2.6.39...
-Juha
--
---
| Juha Jäykkä, ju...@iki.fi
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
21 matches
Mail list logo
