iwlagn interrupt problem

iwlagn interrupt problem

[Alexander E. Patrakov]

[linux-wireless: sorry for the duplicate, I didn't use the correct
address for LKML, as this is my first LKML post from work]

Hello. My kernel is 2.6.27.6, and at work, I sit in a place with
unreliable wireless connection. The problematic piece of dmesg looks
like this:

[17454.155855] wlan0: deauthenticated
[17456.509322] iwlagn 0000:0c:00.0: PCI INT A disabled
[17456.557701] iwlagn 0000:0c:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[17456.557814] iwlagn 0000:0c:00.0: restoring config space at offset
0x1 (was 0x100102, writing 0x100106)
[17456.756926] Registered led device: iwl-phy0:radio
[17456.756976] Registered led device: iwl-phy0:assoc
[17456.757028] Registered led device: iwl-phy0:RX
[17456.757065] Registered led device: iwl-phy0:TX
[17456.766141] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[17460.329937] wlan0: authenticate with AP 00:19:5b:ba:53:b7
[17460.335391] wlan0: authenticated
[17460.335401] wlan0: associate with AP 00:19:5b:ba:53:b7
[17460.532088] wlan0: associate with AP 00:19:5b:ba:53:b7
[17460.534523] wlan0: RX AssocResp from 00:19:5b:ba:53:b7 (capab=0x431
status=0 aid=2)
[17460.534533] wlan0: associated
[17460.541523] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[17471.476059] wlan0: no IPv6 routers present
[17821.193753] wlan0: deauthenticated
[17823.550303] iwlagn 0000:0c:00.0: PCI INT A disabled
[17823.612978] iwlagn 0000:0c:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[17823.613110] iwlagn 0000:0c:00.0: restoring config space at offset
0x1 (was 0x100102, writing 0x100106)
[17823.812945] Registered led device: iwl-phy0:radio
[17823.812995] Registered led device: iwl-phy0:assoc
[17823.813048] Registered led device: iwl-phy0:RX
[17823.813085] Registered led device: iwl-phy0:TX
[17823.823450] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[17827.380770] wlan0: authenticate with AP 00:19:5b:ba:53:b7
[17827.382603] wlan0: authenticated
[17827.382613] wlan0: associate with AP 00:19:5b:ba:53:b7
[17827.581037] wlan0: associate with AP 00:19:5b:ba:53:b7
[17827.583418] wlan0: RX AssocResp from 00:19:5b:ba:53:b7 (capab=0x431
status=0 aid=2)
[17827.583429] wlan0: associated
[17827.591080] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[17838.392089] wlan0: no IPv6 routers present

Prevois kernels panicked in this place, see description and photo at
http://patrakov.blogspot.com/2008/09/kernel-panic.html

The messages about "PCI INT A" are still a problem, because at this
time, the audio loops and the mouse is unresponsive (i.e., the system
locks up for a brief period of time, but eventually recovers). Here is
/proc/interrupts:

          CPU0       CPU1
 0:    2600610    2598665   IO-APIC-edge      timer
 1:        173        181   IO-APIC-edge      i8042
 3:          1          1   IO-APIC-edge
 4:          1          1   IO-APIC-edge
 7:          0          0   IO-APIC-edge      parport0
 8:         42         32   IO-APIC-edge      rtc0
 9:       2229       2204   IO-APIC-fasteoi   acpi
 12:         72         66   IO-APIC-edge      i8042
 14:      92707      91972   IO-APIC-edge      ata_piix
 15:          0          0   IO-APIC-edge      ata_piix
 16:        255        247   IO-APIC-fasteoi   firewire_ohci, yenta,
i915@pci:0000:00:02.0
 21:     357656     360896   IO-APIC-fasteoi   HDA Intel
 22:        110         97   IO-APIC-fasteoi   uhci_hcd:usb1,
uhci_hcd:usb2, uhci_hcd:usb4, uhci_hcd:usb5, uhci_hcd:usb6
 23:      70327      69245   IO-APIC-fasteoi   ehci_hcd:usb3, ehci_hcd:usb7
219:     126299     126470   PCI-MSI-edge      iwlagn
220:      29297      29382   PCI-MSI-edge      eth0
221:      41694      41968   PCI-MSI-edge      ahci
NMI:          0          0   Non-maskable interrupts
LOC:    1584309    2655947   Local timer interrupts
RES:     461218     469590   Rescheduling interrupts
CAL:        987      67106   function call interrupts
TLB:        987       1027   TLB shootdowns
TRM:          0          0   Thermal event interrupts
SPU:          0          0   Spurious interrupts
ERR:          0
MIS:          0

Here is lspci && lspci -n:

00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory
Controller Hub (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile
GM965/GL960 Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile GM965/GL960
Integrated Graphics Controller (rev 03)
00:1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB
UHCI Controller #4 (rev 03)
00:1a.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB
UHCI Controller #5 (rev 03)
00:1a.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2
EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio
Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express
Port 1 (rev 03)
00:1c.2 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express
Port 3 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB
UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB
UHCI Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801H (ICH8 Family) USB
UHCI Controller #3 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2
EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f3)
00:1f.0 ISA bridge: Intel Corporation 82801HEM (ICH8M) LPC Interface
Controller (rev 03)
00:1f.1 IDE interface: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E)
IDE Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation 82801HBM/HEM
(ICH8M/ICH8M-E) SATA AHCI Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 03)
04:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8055
PCI-E Gigabit Ethernet Controller (rev 14)
0c:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or
AGN [Kedron] Network Connection (rev 61)
1c:03.0 CardBus bridge: O2 Micro, Inc. OZ711SP1 Memory CardBus
Controller (rev 01)
1c:03.2 SD Host controller: O2 Micro, Inc. Integrated MMC/SD Controller (rev 02)
1c:03.3 Mass storage controller: O2 Micro, Inc. Integrated MS/xD
Controller (rev 01)
1c:03.4 FireWire (IEEE 1394): O2 Micro, Inc. Firewire (IEEE 1394) (rev 02)
00:00.0 0600: 8086:2a00 (rev 03)
00:02.0 0300: 8086:2a02 (rev 03)
00:02.1 0380: 8086:2a03 (rev 03)
00:1a.0 0c03: 8086:2834 (rev 03)
00:1a.1 0c03: 8086:2835 (rev 03)
00:1a.7 0c03: 8086:283a (rev 03)
00:1b.0 0403: 8086:284b (rev 03)
00:1c.0 0604: 8086:283f (rev 03)
00:1c.2 0604: 8086:2843 (rev 03)
00:1d.0 0c03: 8086:2830 (rev 03)
00:1d.1 0c03: 8086:2831 (rev 03)
00:1d.2 0c03: 8086:2832 (rev 03)
00:1d.7 0c03: 8086:2836 (rev 03)
00:1e.0 0604: 8086:2448 (rev f3)
00:1f.0 0601: 8086:2815 (rev 03)
00:1f.1 0101: 8086:2850 (rev 03)
00:1f.2 0106: 8086:2829 (rev 03)
00:1f.3 0c05: 8086:283e (rev 03)
04:00.0 0200: 11ab:4363 (rev 14)
0c:00.0 0280: 8086:4229 (rev 61)
1c:03.0 0607: 1217:7136 (rev 01)
1c:03.2 0805: 1217:7120 (rev 02)
1c:03.3 0180: 1217:7130 (rev 01)
1c:03.4 0c00: 1217:00f7 (rev 02)

Here is /proc/cmdline (nomsi is needed in order to work around the
erratum in the GM965 graphics chipset without upgrading the driver).

root=/dev/mapper/aep-root ro nomsi quiet resume=/dev/mapper/aep-swap_1

If more information is needed, just ask.

--
Alexander E. Patrakov

Re: iwlagn interrupt problem

[reinette chatre]

On Wed, 2008-12-10 at 07:10 -0800, Alexander E. Patrakov wrote:
> [linux-wireless: sorry for the duplicate, I didn't use the correct
> address for LKML, as this is my first LKML post from work]
> 
> Hello. My kernel is 2.6.27.6, and at work, I sit in a place with
> unreliable wireless connection. The problematic piece of dmesg looks
> like this:
> 
> [17454.155855] wlan0: deauthenticated
> [17456.509322] iwlagn 0000:0c:00.0: PCI INT A disabled
> [17456.557701] iwlagn 0000:0c:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
> [17456.557814] iwlagn 0000:0c:00.0: restoring config space at offset
> 0x1 (was 0x100102, writing 0x100106)
> [17456.756926] Registered led device: iwl-phy0:radio
> [17456.756976] Registered led device: iwl-phy0:assoc
> [17456.757028] Registered led device: iwl-phy0:RX
> [17456.757065] Registered led device: iwl-phy0:TX
> [17456.766141] ADDRCONF(NETDEV_UP): wlan0: link is not ready
> [17460.329937] wlan0: authenticate with AP 00:19:5b:ba:53:b7
> [17460.335391] wlan0: authenticated
> [17460.335401] wlan0: associate with AP 00:19:5b:ba:53:b7
> [17460.532088] wlan0: associate with AP 00:19:5b:ba:53:b7
> [17460.534523] wlan0: RX AssocResp from 00:19:5b:ba:53:b7 (capab=0x431
> status=0 aid=2)
> [17460.534533] wlan0: associated
> [17460.541523] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
> [17471.476059] wlan0: no IPv6 routers present
> [17821.193753] wlan0: deauthenticated
> [17823.550303] iwlagn 0000:0c:00.0: PCI INT A disabled
> [17823.612978] iwlagn 0000:0c:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
> [17823.613110] iwlagn 0000:0c:00.0: restoring config space at offset
> 0x1 (was 0x100102, writing 0x100106)
> [17823.812945] Registered led device: iwl-phy0:radio
> [17823.812995] Registered led device: iwl-phy0:assoc
> [17823.813048] Registered led device: iwl-phy0:RX
> [17823.813085] Registered led device: iwl-phy0:TX
> [17823.823450] ADDRCONF(NETDEV_UP): wlan0: link is not ready
> [17827.380770] wlan0: authenticate with AP 00:19:5b:ba:53:b7
> [17827.382603] wlan0: authenticated
> [17827.382613] wlan0: associate with AP 00:19:5b:ba:53:b7
> [17827.581037] wlan0: associate with AP 00:19:5b:ba:53:b7
> [17827.583418] wlan0: RX AssocResp from 00:19:5b:ba:53:b7 (capab=0x431
> status=0 aid=2)
> [17827.583429] wlan0: associated
> [17827.591080] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
> [17838.392089] wlan0: no IPv6 routers present
> 
> Prevois kernels panicked in this place, see description and photo at
> http://patrakov.blogspot.com/2008/09/kernel-panic.html
> 
> The messages about "PCI INT A" are still a problem, because at this
> time, the audio loops and the mouse is unresponsive (i.e., the system
> locks up for a brief period of time, but eventually recovers). Here is
> /proc/interrupts:

The messages you refer to are printed because a user space app
(wpa_supplicant or network manager) brings the wireless interface down
and up. Interrupts are disabled when interface is brought down and
reenabled when interface is brought up.

The unresponsiveness is due to a bug that was fixed recently. The
patches have been merged into wireless-testing repo and will be included
in 2.6.29. If you want to try 
the individual patches, please try:
http://marc.info/?l=linux-wireless&m=122824886623698&w=2
http://marc.info/?l=linux-wireless&m=122849275528102&w=2


Reinette

Re: iwlagn interrupt problem

[Alexander E. Patrakov]

2008/12/10 reinette chatre <reinette.chatre@intel.com>:
> The messages you refer to are printed because a user space app
> (wpa_supplicant or network manager) brings the wireless interface down
> and up. Interrupts are disabled when interface is brought down and
> reenabled when interface is brought up.

OK.

> The unresponsiveness is due to a bug that was fixed recently. The
> patches have been merged into wireless-testing repo and will be included
> in 2.6.29. If you want to try
> the individual patches, please try:
> http://marc.info/?l=linux-wireless&m=122824886623698&w=2
> http://marc.info/?l=linux-wireless&m=122849275528102&w=2

These individual patches don't apply to 2.6.27.6, so I installed
today's compat-wireless-2.6, and it seems to work. Thanks!

OTOH, are these patches a material for backporting into -stable?

-- 
Alexander E. Patrakov

Re: iwlagn interrupt problem

[reinette chatre]

On Thu, 2008-12-11 at 05:48 -0800, Alexander E. Patrakov wrote:
> 2008/12/10 reinette chatre <reinette.chatre@intel.com>:
> > The unresponsiveness is due to a bug that was fixed recently. The
> > patches have been merged into wireless-testing repo and will be included
> > in 2.6.29. If you want to try
> > the individual patches, please try:
> > http://marc.info/?l=linux-wireless&m=122824886623698&w=2
> > http://marc.info/?l=linux-wireless&m=122849275528102&w=2
> 
> These individual patches don't apply to 2.6.27.6, so I installed
> today's compat-wireless-2.6, and it seems to work. Thanks!
> 
> OTOH, are these patches a material for backporting into -stable?

We are not planning to do so, but you are welcome to.

Reinette

Re: iwlagn interrupt problem

[Zdenek Kabelac]

Alexander E. Patrakov napsal(a):
> 2008/12/10 reinette chatre <reinette.chatre-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>:
>> The messages you refer to are printed because a user space app
>> (wpa_supplicant or network manager) brings the wireless interface down
>> and up. Interrupts are disabled when interface is brought down and
>> reenabled when interface is brought up.
> 
> OK.
> 
>> The unresponsiveness is due to a bug that was fixed recently. The
>> patches have been merged into wireless-testing repo and will be included
>> in 2.6.29. If you want to try
>> the individual patches, please try:
>> http://marc.info/?l=linux-wireless&m=122824886623698&w=2
>> http://marc.info/?l=linux-wireless&m=122849275528102&w=2
> 
> These individual patches don't apply to 2.6.27.6, so I installed
> today's compat-wireless-2.6, and it seems to work. Thanks!
> 
> OTOH, are these patches a material for backporting into -stable?
> 

Hi

I assume that this backtrace I've got with 2.6.28-rc7 is the same issue ?
(If I get it right - this issue will not be fixed in 2.6.28 and is delay for 
2.6.29 ?))

usb 3-2: reset full speed USB device using uhci_hcd and address 9
Restarting tasks ... done.
e1000e 0000:00:19.0: irq 377 for MSI/MSI-X
e1000e 0000:00:19.0: irq 377 for MSI/MSI-X
ADDRCONF(NETDEV_UP): eth0: link is not ready
iwl3945 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
iwl3945 0000:03:00.0: irq 376 for MSI/MSI-X
ADDRCONF(NETDEV_UP): wlan0: link is not ready
wlan0: direct probe to AP 00:11:d8:da:65:40 try 1
wlan0: direct probe to AP 00:11:d8:da:65:40 try 1
wlan0 direct probe responded
wlan0: authenticate with AP 00:11:d8:da:65:40
wlan0: authenticated
wlan0: associate with AP 00:11:d8:da:65:40
wlan0: RX AssocResp from 00:11:d8:da:65:40 (capab=0x401 status=0 aid=8)
wlan0: associated
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
wlan0: disassociating by local choice (reason=3)
wlan0: no IPv6 routers present
wlan0: direct probe to AP 00:11:d8:da:65:40 try 1
wlan0: direct probe to AP 00:11:d8:da:65:40 try 1
wlan0 direct probe responded
wlan0: authenticate with AP 00:11:d8:da:65:40
wlan0: authenticated
wlan0: associate with AP 00:11:d8:da:65:40
wlan0: RX ReassocResp from 00:11:d8:da:65:40 (capab=0x401 status=0 aid=8)
wlan0: associated
wlan0: No ProbeResp from current AP 00:11:d8:da:65:40 - assume out of range
iwl3945: Error sending REPLY_SCAN_CMD: time out after 500ms.
iwl3945: Error sending REPLY_RXON_ASSOC: time out after 500ms.
iwl3945: Error setting RXON_ASSOC configuration (-110).
iwl3945: Error sending REPLY_TX_PWR_TABLE_CMD: time out after 500ms.
iwl3945: Error sending REPLY_RXON_ASSOC: time out after 500ms.
iwl3945: Error setting RXON_ASSOC configuration (-110).
iwl3945: Error sending REPLY_RXON_ASSOC: time out after 500ms.
iwl3945: Error setting RXON_ASSOC configuration (-110).
iwl3945: Error sending REPLY_QOS_PARAM: time out after 500ms.
iwl3945: Error sending REPLY_QOS_PARAM: time out after 500ms.
iwl3945: Error sending REPLY_QOS_PARAM: time out after 500ms.
iwl3945: Error sending REPLY_QOS_PARAM: time out after 500ms.
iwl3945: Error sending REPLY_RXON: time out after 500ms.
iwl3945: Error setting new configuration (-110).
wlan0: direct probe to AP 00:11:d8:da:65:40 try 1
iwl3945: Error sending REPLY_RXON: time out after 500ms.
iwl3945: Error setting new configuration (-110).
iwl3945: Error sending REPLY_RXON: time out after 500ms.
iwl3945: Error setting new configuration (-110).
wlan0: direct probe to AP 00:11:d8:da:65:40 try 1
wlan0: direct probe to AP 00:11:d8:da:65:40 try 2
wlan0: direct probe to AP 00:11:d8:da:65:40 try 3
wlan0: direct probe to AP 00:11:d8:da:65:40 timed out
iwl3945: Error sending REPLY_RXON: time out after 500ms.
iwl3945: Error setting new configuration (-110).
iwl3945: Error sending REPLY_RXON: time out after 500ms.
iwl3945: Error setting new configuration (-110).
iwl3945: Error sending REPLY_RXON: time out after 500ms.
iwl3945: Error setting new configuration (-110).
iwl3945: Error sending REPLY_RXON: time out after 500ms.
iwl3945: Error setting new configuration (-110).
wlan0: direct probe to AP 00:11:d8:da:65:40 try 1
wlan0: direct probe to AP 00:11:d8:da:65:40 try 2
wlan0: direct probe to AP 00:11:d8:da:65:40 try 3
wlan0: direct probe to AP 00:11:d8:da:65:40 timed out
iwl3945: Error sending REPLY_SCAN_CMD: time out after 500ms.
iwl3945: Error sending REPLY_RXON: time out after 500ms.
iwl3945: Error setting new configuration (-110).
iwl3945: Error sending REPLY_TX_PWR_TABLE_CMD: time out after 500ms.
iwl3945: Error sending REPLY_SCAN_CMD: time out after 500ms.
iwl3945: Error sending REPLY_RXON: time out after 500ms.
iwl3945: Error setting new configuration (-110).
iwl3945: Error sending REPLY_TX_PWR_TABLE_CMD: time out after 500ms.
iwl3945: Error sending REPLY_SCAN_CMD: time out after 500ms.
iwl3945: Error sending REPLY_RXON: time out after 500ms.
iwl3945: Error setting new configuration (-110).
iwl3945: Error sending REPLY_TX_PWR_TABLE_CMD: time out after 500ms.
iwl3945: Error sending REPLY_SCAN_CMD: time out after 500ms.
iwl3945: Error sending REPLY_RXON: time out after 500ms.
iwl3945: Error setting new configuration (-110).
iwl3945: Error sending REPLY_TX_PWR_TABLE_CMD: time out after 500ms.
iwl3945: Error sending REPLY_RXON: time out after 500ms.
iwl3945: Error setting new configuration (-110).
iwl3945: Error sending REPLY_RXON: time out after 500ms.
iwl3945: Error setting new configuration (-110).
iwl3945: No space for Tx
iwl3945: Error sending REPLY_RXON: iwl3945_enqueue_hcmd failed: -28
iwl3945: Error setting new configuration (-28).
iwl3945: No space for Tx
iwl3945: Error sending REPLY_RXON: iwl3945_enqueue_hcmd failed: -28
iwl3945: Error setting new configuration (-28).
wlan0: direct probe to AP 00:11:d8:da:65:40 try 1
wlan0: direct probe to AP 00:11:d8:da:65:40 try 2
wlan0: direct probe to AP 00:11:d8:da:65:40 try 3
wlan0: direct probe to AP 00:11:d8:da:65:40 timed out
iwl3945: No space for Tx
iwl3945: Error sending REPLY_SCAN_CMD: iwl3945_enqueue_hcmd failed: -28
iwl3945: No space for Tx
iwl3945: Error sending REPLY_RXON: iwl3945_enqueue_hcmd failed: -28
iwl3945: Error setting new configuration (-28).
iwl3945: No space for Tx
iwl3945: Error sending REPLY_TX_PWR_TABLE_CMD: iwl3945_enqueue_hcmd failed: -28
iwl3945: No space for Tx
iwl3945: Error sending REPLY_SCAN_CMD: iwl3945_enqueue_hcmd failed: -28
iwl3945: No space for Tx
iwl3945: Error sending REPLY_RXON: iwl3945_enqueue_hcmd failed: -28
iwl3945: Error setting new configuration (-28).
iwl3945: No space for Tx
iwl3945: Error sending REPLY_TX_PWR_TABLE_CMD: iwl3945_enqueue_hcmd failed: -28
iwl3945: No space for Tx
iwl3945: Error sending REPLY_SCAN_CMD: iwl3945_enqueue_hcmd failed: -28
iwl3945: No space for Tx
iwl3945: Error sending REPLY_RXON: iwl3945_enqueue_hcmd failed: -28
iwl3945: Error setting new configuration (-28).
iwl3945: No space for Tx
iwl3945: Error sending REPLY_TX_PWR_TABLE_CMD: iwl3945_enqueue_hcmd failed: -28
iwl3945: No space for Tx
iwl3945: Error sending REPLY_SCAN_CMD: iwl3945_enqueue_hcmd failed: -28
iwl3945: No space for Tx
iwl3945: Error sending REPLY_RXON: iwl3945_enqueue_hcmd failed: -28
iwl3945: Error setting new configuration (-28).
iwl3945: No space for Tx
iwl3945: Error sending REPLY_TX_PWR_TABLE_CMD: iwl3945_enqueue_hcmd failed: -28
iwl3945: No space for Tx
iwl3945: Error sending REPLY_SCAN_CMD: iwl3945_enqueue_hcmd failed: -28
iwl3945: No space for Tx
iwl3945: Error sending REPLY_RXON: iwl3945_enqueue_hcmd failed: -28
iwl3945: Error setting new configuration (-28).
iwl3945: No space for Tx
iwl3945: Error sending REPLY_TX_PWR_TABLE_CMD: iwl3945_enqueue_hcmd failed: -28
iwl3945: No space for Tx
iwl3945: Error sending REPLY_RXON: iwl3945_enqueue_hcmd failed: -28
iwl3945: Error setting new configuration (-28).
iwl3945: No space for Tx
iwl3945: Error sending REPLY_RXON: iwl3945_enqueue_hcmd failed: -28
iwl3945: Error setting new configuration (-28).
iwl3945: No space for Tx
iwl3945: Error sending REPLY_RXON: iwl3945_enqueue_hcmd failed: -28
iwl3945: Error setting new configuration (-28).
iwl3945: No space for Tx
iwl3945: Error sending REPLY_RXON: iwl3945_enqueue_hcmd failed: -28
iwl3945: Error setting new configuration (-28).
wlan0: direct probe to AP 00:11:d8:da:65:40 try 1
wlan0: direct probe to AP 00:11:d8:da:65:40 try 2
wlan0: direct probe to AP 00:11:d8:da:65:40 try 3
wlan0: direct probe to AP 00:11:d8:da:65:40 timed out
iwl3945: No space for Tx
iwl3945: Error sending REPLY_SCAN_CMD: iwl3945_enqueue_hcmd failed: -28
iwl3945: No space for Tx
iwl3945: Error sending REPLY_RXON: iwl3945_enqueue_hcmd failed: -28
iwl3945: Error setting new configuration (-28).
iwl3945: No space for Tx
iwl3945: Error sending REPLY_TX_PWR_TABLE_CMD: iwl3945_enqueue_hcmd failed: -28
iwl3945: No space for Tx
iwl3945: Error sending REPLY_SCAN_CMD: iwl3945_enqueue_hcmd failed: -28
iwl3945: No space for Tx
iwl3945: Error sending REPLY_RXON: iwl3945_enqueue_hcmd failed: -28
iwl3945: Error setting new configuration (-28).
iwl3945: No space for Tx
iwl3945: Error sending REPLY_TX_PWR_TABLE_CMD: iwl3945_enqueue_hcmd failed: -28
iwl3945: No space for Tx
iwl3945: Error sending REPLY_SCAN_CMD: iwl3945_enqueue_hcmd failed: -28
iwl3945: No space for Tx
iwl3945: Error sending REPLY_RXON: iwl3945_enqueue_hcmd failed: -28
iwl3945: Error setting new configuration (-28).
iwl3945: No space for Tx
iwl3945: Error sending REPLY_TX_PWR_TABLE_CMD: iwl3945_enqueue_hcmd failed: -28
iwl3945: No space for Tx
iwl3945: Error sending REPLY_SCAN_CMD: iwl3945_enqueue_hcmd failed: -28
iwl3945: No space for Tx
iwl3945: Error sending REPLY_RXON: iwl3945_enqueue_hcmd failed: -28
iwl3945: Error setting new configuration (-28).
iwl3945: No space for Tx
iwl3945: Error sending REPLY_TX_PWR_TABLE_CMD: iwl3945_enqueue_hcmd failed: -28


Zdenek

Re: iwlagn interrupt problem

[Zdenek Kabelac]

Alexander E. Patrakov napsal(a):
> 2008/12/12 Zdenek Kabelac <zkabelac@redhat.com>:
>> I assume that this backtrace I've got with 2.6.28-rc7 is the same issue ?
> 
> No, this is different. My issue is with unacceptable latency when
> bringing the interface down. In your dmesg, the interface was never
> brought up or down.
> 

Hmm - it was something like an hour after resume when the problem started,

Here is timed part of the same backtrace:

[65627.782972] wlan0: associate with AP 00:11:d8:da:65:40
[65627.785569] wlan0: RX ReassocResp from 00:11:d8:da:65:40 (capab=0x401 
status=0 aid=8)
[65627.785576] wlan0: associated
[69541.209873] wlan0: No ProbeResp from current AP 00:11:d8:da:65:40 - assume 
out of range
[69541.810104] iwl3945: Error sending REPLY_SCAN_CMD: time out after 500ms.
[69542.309861] iwl3945: Error sending REPLY_RXON_ASSOC: time out after 500ms.


The begging of my trace looked similar.

Should I open new bugzilla separately ?

Zdenek

Re: iwlagn interrupt problem

[Alexander E. Patrakov]

2008/12/12 Zdenek Kabelac <zkabelac@redhat.com>:
> Should I open new bugzilla separately ?

Try it. In the worst case, your report will be closed as a duplicate
of something else :)

-- 
Alexander E. Patrakov

Re: iwlagn interrupt problem

[Dan Williams]

On Fri, 2008-12-12 at 12:31 +0100, Zdenek Kabelac wrote:
> 
> Alexander E. Patrakov napsal(a):
> > 2008/12/12 Zdenek Kabelac <zkabelac@redhat.com>:
> >> I assume that this backtrace I've got with 2.6.28-rc7 is the same issue ?
> > 
> > No, this is different. My issue is with unacceptable latency when
> > bringing the interface down. In your dmesg, the interface was never
> > brought up or down.
> > 
> 
> Hmm - it was something like an hour after resume when the problem started,
> 
> Here is timed part of the same backtrace:
> 
> [65627.782972] wlan0: associate with AP 00:11:d8:da:65:40
> [65627.785569] wlan0: RX ReassocResp from 00:11:d8:da:65:40 (capab=0x401 
> status=0 aid=8)
> [65627.785576] wlan0: associated
> [69541.209873] wlan0: No ProbeResp from current AP 00:11:d8:da:65:40 - assume 
> out of range
> [69541.810104] iwl3945: Error sending REPLY_SCAN_CMD: time out after 500ms.
> [69542.309861] iwl3945: Error sending REPLY_RXON_ASSOC: time out after 500ms.
> 
> 
> The begging of my trace looked similar.
> 
> Should I open new bugzilla separately ?

If you can reproduce this, it sounds more like a firmware problem, so
Reinette is probably going to want you to enable firmware debugging in
the driver.  Try removing the iwl3945 module with rmmod, then "modprobe
iwl3945 debug=0x43fff", reproduce this command timeout, and attach the
logs to whatever bug report you file.

Dan

Re: iwlagn interrupt problem

[Zdenek Kabelac]

Dan Williams napsal(a):
> On Fri, 2008-12-12 at 12:31 +0100, Zdenek Kabelac wrote:
>> Alexander E. Patrakov napsal(a):
>>> 2008/12/12 Zdenek Kabelac <zkabelac@redhat.com>:
>>>> I assume that this backtrace I've got with 2.6.28-rc7 is the same issue ?
>>> No, this is different. My issue is with unacceptable latency when
>>> bringing the interface down. In your dmesg, the interface was never
>>> brought up or down.
>>>
>> Hmm - it was something like an hour after resume when the problem started,
>>
>> Here is timed part of the same backtrace:
>>
>> [65627.782972] wlan0: associate with AP 00:11:d8:da:65:40
>> [65627.785569] wlan0: RX ReassocResp from 00:11:d8:da:65:40 (capab=0x401 
>> status=0 aid=8)
>> [65627.785576] wlan0: associated
>> [69541.209873] wlan0: No ProbeResp from current AP 00:11:d8:da:65:40 - assume 
>> out of range
>> [69541.810104] iwl3945: Error sending REPLY_SCAN_CMD: time out after 500ms.
>> [69542.309861] iwl3945: Error sending REPLY_RXON_ASSOC: time out after 500ms.
>>
>>
>> The begging of my trace looked similar.
>>
>> Should I open new bugzilla separately ?
> 
> If you can reproduce this, it sounds more like a firmware problem, so
> Reinette is probably going to want you to enable firmware debugging in
> the driver.  Try removing the iwl3945 module with rmmod, then "modprobe
> iwl3945 debug=0x43fff", reproduce this command timeout, and attach the
> logs to whatever bug report you file.
> 

Unfortunately I do not have a reproducing case and it happened just once on 
Wednesday after resume.

But when (if) it will repeat I'll try to reinsert module with debug - I think 
without this my bug is not resolvable right ?

Zdenek