Hi Moritz,
I have not seen this problem or any of the other iwl instabilities in a
long time, however, I have been running with these option lines disabling
11n functionality in order to achieve that stability:
options iwlagn 11n_disable50=1
options iwlwifi 11n_disable=1
since I am
Shannon Dealy writes:
> I have not seen this problem or any of the other iwl instabilities in
> a long time, however, I have been running with these option lines
> disabling 11n functionality in order to achieve that stability:
>
> options iwlagn 11n_disable50=1
> options iwlwifi 11n_disa
reassign 628444 src:linux
thanks
On Wed, Mar 14, 2012 at 08:37:17PM -0700, Shannon Dealy wrote:
>
>
>>> 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 p
On Tue, Mar 20, 2012 at 12:28:01AM +, Juha Jäykkä wrote:
> I am starting to believe I am in the clear here, but I am not yet convinced
> since the root cause is still unknown. In any case, thanks for all of you for
> helping hunt this down.
>
> Dafydd: I think you might want to try pcie_as
Hi Juha,
>Mar 22 20:13:47 rigel kernel: [1259943.614216] iwlwifi :03:00.0: RF_KILL
>bit toggled to disable radio.
>Mar 22 20:13:47 rigel kernel: [1259943.614350] iwlwifi :03:00.0: Not
>sending command - RF KILL
[MV] These are not technically error messages, and we had a patch fixing thes
This may or may not be related, but I thought it best to inform you about what
I just saw anyway:
I accidentally toggled the physical RF kill switch on my laptop and the result
was very much reminiscent of the bug we are discussing (note the QoS and
failure to remove key):
Mar 22 20:13:47 rige
My update (after a reboot caused by a crashed hibernation attempt at uptime ~8
days):
juhaj@rigel > uptime
00:18:27 up 14 days, 6:50, 9 users, load average: 0.00, 0.03, 0.05
juhaj@rigel > cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-3.2.0-1-amd64 root=/dev/mapper/system-root ro quiet
usbcore.aut
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 renamed to iwlwif
On Fri, Mar 16, 2012 at 01:30:46PM +0100, Dafydd Harries wrote:
> Today I got a failure, and on my machine it was using L0S, not L1S:
>
> Mar 16 11:38:45 localhost kernel: [ 9045.913617] iwlwifi :02:00.0: L1
> Disabled; Enabling L0S
>
> So I don't think this is the difference necessarily.
>
On Fri, Mar 16, 2012 at 10:03:54AM +0100, Bjørn Mork wrote:
> But I wonder about Juha's observation about this difference between my
> setup:
>
> [ 12.611061] iwlwifi :03:00.0: L1 Disabled; Enabling L0S
>
> and his:
>
> [245082.407512] iwlwifi :03:00.0: L1 Enabled; Disabling L0S
>
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 renamed to iwlwifi in 3.2.
Which makes this workaroun
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
Another failure today, but this time the device failed to come out of
a sleep state after a resume cycle.
...
Mar 15 16:10:52 localhost kernel: [79800.936071] ehci_hcd :00:1d.0: power
state changed by ACPI to D0
Mar 15 16:10:52 localhost kernel: [79800.936173] ahci :00:1f.2: restoring
c
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
On Mon, Mar 12, 2012 at 12:44:29PM -0500, Jonathan Nieder wrote:
> Dafydd Harries wrote:
> > Ar 12/03/2012 am 17:11, ysgrifennodd Venkataraman, Meenakshi:
> >>> Dafydd Harries wrote:
>
> Like others, the problems seemed to start around 2.6.39.
> [...]
> > Sadly, my dpkg.log only goes back to
Hi Dafydd,
>> >> I've been seeing similar problems with my "Intel Corporation Centrino
>> >> Ultimate-N 6300".
>> >>
>> >> Like others, the problems seemed to start around 2.6.39.
[MV] Hmm...this is interesting. Can you load the iwlwifi module with
bt_coex_active=0 and see if it changes anything
Hi,
>>> what platform are you using? And does your problem appear after a
>>> system hibernate?
>>
>> Linux nia 3.2.0-2-amd64 #1 SMP Sun Mar 4 22:48:17 UTC 2012 x86_64
>> GNU/Linux
>>
>> The system is Debian unstable.
>
>Maybe "lspci -vvnn" output (as an attachment) and "dmesg" output from
>bootin
Dafydd Harries wrote:
> Ar 12/03/2012 am 17:11, ysgrifennodd Venkataraman, Meenakshi:
>>> Dafydd Harries wrote:
Like others, the problems seemed to start around 2.6.39.
[...]
> Sadly, my dpkg.log only goes back to 3.0, which was installed last July
> (!).
Thanks for checking, and sorry for t
Ar 12/03/2012 am 17:11, ysgrifennodd Venkataraman, Meenakshi:
> Hi,
>
> >Dafydd Harries wrote:
> >
> >> I've been seeing similar problems with my "Intel Corporation Centrino
> >> Ultimate-N 6300".
> >>
> >> Like others, the problems seemed to start around 2.6.39.
> >
> >Odd. What kernel did you us
Hi,
>Dafydd Harries wrote:
>
>> I've been seeing similar problems with my "Intel Corporation Centrino
>> Ultimate-N 6300".
>>
>> Like others, the problems seemed to start around 2.6.39.
>
>Odd. What kernel did you use before then? (/var/log/dpkg.log might
>tell.)
>
>> Like othes, the card flakes
found 628444 linux-2.6/3.2.9-1
tags 628444 + upstream patch moreinfo
quit
Hi Dafydd,
Dafydd Harries wrote:
> I've been seeing similar problems with my "Intel Corporation Centrino
> Ultimate-N 6300".
>
> Like others, the problems seemed to start around 2.6.39.
Odd. What kernel did you use before
Hi,
Venkataraman, Meenakshi wrote:
> Hi Shannon and others,
Thanks for a helpful note. Forwarding to Shannon, Juha, and Bjørn:
> 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 caug
Hi Jonathan!
Sorry I took a while to respond and apologies in advance for them being quite
useless...
> - steps to reproduce, assuming I had the same hardware
Use the computer. My maximum time without hitting the bug has been less than
48 hours before I added the following module options: 11n
Hi Juha,
Juha Jäykkä wrote:
> 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 power-off (unplu
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
collect
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
> collect data on what is happening).
That's goo
26 matches
Mail list logo
