| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <D936D925018D154694D8A362EEB0892003C36C42@orsmsx416.amr.corp.intel.com> Date: Tue, 26 Feb 2008 22:14:17 -0800 From: "Chatre, Reinette" <reinette.chatre@...el.com> To: "Tim Connors" <tconnors@...ro.swin.edu.au>, "Andrew Morton" <akpm@...ux-foundation.org> Cc: "kernel list" <linux-kernel@...r.kernel.org>, <linux-wireless@...r.kernel.org> Subject: RE: iwl4965 dropping packets and __dev_addr_discard: address leakage! da_users=1 On Monday, February 25, 2008 10:48 PM, Tim Connors wrote: > On Mon, 25 Feb 2008, Andrew Morton wrote: > >> On Tue, 26 Feb 2008 16:22:43 +1100 Tim Connors > <tconnors@...ro.swin.edu.au> wrote: >> >>> Possibly because of the frequent renegotiating my iwl4965 card has >>> been making, it has now decided it's not going to pass packets >>> reliably until presumably next time I reboot. >>> >>> I've noticed messages in syslog that I hadn't seen when things were >>> working fine. The problem possibly has only surfaced after >>> rmmodding the iwl4965 module, then remodding it. It stays with me >>> through being removed and modprobed again. It is being bonded in >>> conjunction with a physical ethernet, if that is relevant, although >>> I think I reproduced it when it was on its lonesome. >>> >>> >>> Fresh after reboot: >>> >>> Feb 22 09:49:31 dirac kernel: iwl4965: Intel(R) Wireless > WiFi Link 4965AGN driver for Linux, 1.1.17kds >>> Feb 22 09:49:31 dirac kernel: iwl4965: Copyright(c) 2003-2007 Intel >>> Corporation Feb 22 09:49:31 dirac kernel: ACPI: PCI Interrupt > 0000:0c:00.0[A] -> GSI 17 (level, low) -> IRQ 17 >>> Feb 22 09:49:31 dirac kernel: PCI: Setting latency timer of device >>> 0000:0c:00.0 to 64 Feb 22 09:49:31 dirac kernel: iwl4965: Detected >>> Intel Wireless WiFi Link 4965AGN Feb 22 09:49:31 dirac kernel: >>> ACPI: PCI Interrupt > 0000:00:1b.0[A] -> GSI 21 (level, low) -> IRQ 21 >>> Feb 22 09:49:31 dirac kernel: PCI: Setting latency timer of device >>> 0000:00:1b.0 to 64 Feb 22 09:49:31 dirac kernel: iwl4965: Tunable >>> channels: > 11 802.11bg, 13 802.11a channels >>> Feb 22 09:49:31 dirac kernel: phy0: Selected rate control algorithm >>> 'iwl-4965-rs' >>> >>> now finished with it, will be deconfigured and rmmodded: >>> >>> Feb 23 03:05:23 dirac kernel: __dev_addr_discard: address leakage! >>> da_users=1 Feb 23 03:05:23 dirac kernel: ACPI: PCI interrupt for >>> device 0000:0c:00.0 disabled >>> >>> The modprobed again: >>> >>> Feb 23 03:05:35 dirac kernel: iwl4965: Intel(R) Wireless > WiFi Link 4965AGN driver for Linux, 1.1.17kds >>> Feb 23 03:05:35 dirac kernel: iwl4965: Copyright(c) 2003-2007 Intel >>> Corporation Feb 23 03:05:35 dirac kernel: ACPI: PCI Interrupt > 0000:0c:00.0[A] -> GSI 17 (level, low) -> IRQ 17 >>> Feb 23 03:05:35 dirac kernel: PCI: Setting latency timer of device >>> 0000:0c:00.0 to 64 Feb 23 03:05:35 dirac kernel: iwl4965: Detected >>> Intel Wireless WiFi Link 4965AGN Feb 23 03:05:35 dirac kernel: >>> iwl4965: Tunable channels: > 11 802.11bg, 13 802.11a channels >>> Feb 23 03:05:35 dirac kernel: phy9: Selected rate control algorithm >>> 'iwl-4965-rs' >>> >>> according to lspci -vvv, 0c:00.0 is: >>> >>> 0c:00.0 Network controller: Intel Corporation PRO/Wireless > 4965 AG or AGN Network Connection (rev 61) >>> Subsystem: Intel Corporation Unknown device 1120 >>> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- > VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ >>> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- > DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- >>> Latency: 0, Cache Line Size: 64 bytes >>> Interrupt: pin A routed to IRQ 379 >>> Region 0: Memory at f9ffe000 (64-bit, non-prefetchable) >>> [size=8K] Capabilities: [c8] Power Management version 3 >>> Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA > PME(D0+,D1-,D2-,D3hot+,D3cold+) >>> Status: D0 PME-Enable- DSel=0 DScale=0 PME- >>> Capabilities: [d0] Message Signalled Interrupts: Mask- >>> 64bit+ Queue=0/0 Enable+ Address: 00000000fee0300c >>> Data: 4194 Capabilities: [e0] Express (v1) Endpoint, MSI 00 >>> DevCap: MaxPayload 128 bytes, PhantFunc 0, > Latency L0s <512ns, L1 unlimited >>> ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ >>> FLReset- DevCtl: Report errors: Correctable- >>> Non-Fatal- Fatal- Unsupported- RlxdOrd+ >>> ExtTag- PhantFunc- AuxPwr- NoSnoop+ >>> MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: >>> CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr+ >>> TransPend- LnkCap: Port #0, Speed 2.5GT/s, Width x1, > ASPM L0s L1, Latency L0 <128ns, L1 <64us >>> ClockPM+ Suprise- LLActRep- BwNot- >>> LnkCtl: ASPM L0s Enabled; RCB 64 bytes Disabled- >>> Retrain- CommClk+ ExtSynch- ClockPM- >>> AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, >>> Width x1, TrErr- > Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- >>> Capabilities: [100] Advanced Error Reporting <?> >>> Capabilities: [140] Device Serial Number >>> d7-36-9b-ff-ff-e8-13-00 Kernel driver in use: iwl4965 >>> Kernel modules: iwl4965 >> >> (cc linux-wireless) >> >> What kernel version is this? >> >> Is this a regression from an earlier kenrel version? If so, which? > > kernel 2.6.24 > version 4.44.1.20 of the firmware. > > The iwl4965 version is fairly ancient in mainline kernel: 1.1.17kds > Last time I looked, 1.2.24 was the latest version, but I never > succeeded in getting it to work (or compile?) in 2.6.24. > You can use the latest iwlwifi driver with kernel 2.6.24 when using the compat-wireless project (http://linuxwireless.org/en/users/Download). You can also load the driver with debugging (modprobe iwl4965 debug=0x43fff) to get more info about what happens during module unload. Reinette -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists