Bug 580218 - 5ghz N connectivity falls over with iwlagn 0000:0c:00.0: iwl_tx_agg _start on ra = 00:22:6b:68:89:f5 tid = 0
Summary: 5ghz N connectivity falls over with iwlagn 0000:0c:00.0: iwl_tx_agg _start on...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 13
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Stanislaw Gruszka
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 577003 578663
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-07 18:11 UTC by Jesse Keating
Modified: 2013-01-10 03:32 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 577003
Environment:
Last Closed: 2010-06-04 16:10:40 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jesse Keating 2010-04-07 18:11:13 UTC
+++ This bug was initially created as a clone of Bug #577003 +++

2.6.32.10-83.fc12.x86_64 broke, 2.6.32.9 was working.

F13 kernels are also broken, potentially in a different way.

--- Additional comment from jkeating on 2010-03-25 19:16:21 EDT ---

 <cebbert>       this got added in .10: http://git.kernel.org/?p=
 linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff_plain;h=5e2f75b8993a0d83d46
 9388b50716dd5551f2eb4
 Mar 18 20:07:19 <Oxf13> yeah, I think .9 worked, and .10 broke

--- Additional comment from pekkas on 2010-03-26 09:01:00 EDT ---

I think I'm probably seeing the same thing: kernel-2.6.32.10-90.fc12.i686 broke, going back to 2.6.32.9-70.fc12.i686 was OK.  Network works for something like 2-3 minutes, after which ARP requests for default gw no longer get response. I see some inbound packets.  After reassociating (clicking 'eduroam' SSID again in NM) it works again for a couple of minutes.

FWIW, I get the $SUBJECT dmesg message in both kernels, but 2.6.32.9 works fine regardless of that.

The driver:

03:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection (rev 61)
	Subsystem: Intel Corporation Lenovo ThinkPad T61
	Physical Slot: 3
	Flags: bus master, fast devsel, latency 0, IRQ 29
	Memory at f7f00000 (64-bit, non-prefetchable) [size=8K]
	Capabilities: [c8] Power Management version 3
	Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
	Capabilities: [e0] Express Endpoint, MSI 00
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [140] Device Serial Number 00-21-5c-ff-ff-62-a7-75
	Kernel driver in use: iwlagn
	Kernel modules: iwlagn

HTH.

--- Additional comment from sgruszka on 2010-04-07 03:44:10 EDT ---

This bug is a duplicate, problems should be solved in -94 kernel:
http://koji.fedoraproject.org/koji/buildinfo?buildID=164636

(In reply to comment #0)
> F13 kernels are also broken, potentially in a different way.    

Please open new F13 bugzilla and assign it to me. Thanks. 

(In reply to comment #2)
> I think I'm probably seeing the same thing: kernel-2.6.32.10-90.fc12.i686
> broke, going back to 2.6.32.9-70.fc12.i686 was OK.  Network works for something
> like 2-3 minutes, after which ARP requests for default gw no longer get
> response. I see some inbound packets.  After reassociating (clicking 'eduroam'
> SSID again in NM) it works again for a couple of minutes.

Please open new bug (+ assign to me) if this still happens on uptodate kernels. Thanks.

*** This bug has been marked as a duplicate of bug 578663 ***

--- Additional comment from pekkas on 2010-04-07 07:00:55 EDT ---

I can confirm that testing -94 appears to have fixed my problem.

Comment 1 Stanislaw Gruszka 2010-04-08 12:46:52 UTC
Jesse,

Please give me some more details since on F13 breakage is different (or not?). At least your card type. If I have the same, most likely I will be able to reproduce.

Comment 2 Jesse Keating 2010-04-08 16:10:38 UTC
0c:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection (rev 61)

Right now I don't even see the 5ghz N AP in my list of available APs to connect to.  It just doesn't appear.

Comment 3 Stanislaw Gruszka 2010-06-04 09:08:33 UTC
Is this still broken on up to date F-13 (2.6.33.x) kernel. If so,  what about F-14 (2.6.34.x) kernels ?

Comment 4 Pekka Savola 2010-06-04 09:26:26 UTC
I've updated from F12 to F13 and works fine on 2.6.33.5-112.fc13.i686, so I suppose this can be closed.

Comment 5 Stanislaw Gruszka 2010-06-04 10:08:11 UTC
Jesse, how about you?

Comment 6 Jesse Keating 2010-06-04 16:10:40 UTC
Yes, this is working for me on up to date F13.


Note You need to log in before you can comment on or make changes to this bug.