| 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
| ||
|
Date: Fri, 4 Apr 2008 01:41:29 +0000
From: "Justin Mattock" <justinmattock@...il.com>
To: "Maciej Żenczykowski" <maze@....uj.edu.pl>
Cc: linux-kernel@...r.kernel.org
Subject: Re: Suspending and resuming a single PCI device (and bridge)
Hello; I noticed this with the macbook pro ati chipset as well(FIFO
thing), you probably read somewhere but if you didn't try
iwpriv ath0 bgscan 0, and put that in /etc/rc.local for starting up.
hope this solves the problem with ath0, also I notice with 2.6.25-rc1
this happend quite a bit with the new madwifi, but using
madwifi-dfs-r3221-20080119 seems to not produce that kind of problem.
Hopefully this helps you out. (if this problem is more than above then
hopefully somebody else has the answer for you.)
regards;
Justin P. Mattock
On Fri, Apr 4, 2008 at 12:13 AM, Maciej Żenczykowski <maze@....uj.edu.pl> wrote:
> I've got a wireless card (atheros 5418 on a MacBookPro3,1) which is
> (kind-of) supported by the madwifi driver (from head), however
> occasionally it gets stuck (long outstanding bug with lots of
> comments, but no fixes) - I've noticed that a suspend to ram and
> resume (almost?) always fixes the problem.
>
> Thus, I'm wondering if there is a way to cause a pci device (and
> possibly the pci bridge/port it's connected to) to suspend/resume
> manually (or naturally, any other solution to the problem)...
>
> The hardware in question:
>
> # lspci -t | egrep 0b; lspci -vvnn -s 00:1c.4; lspci -vvnn -s 0b:00.0
>
> +-1c.4-[0000:0b]----00.0
>
> 00:1c.4 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI
> Express Port 5 [8086:2847] (rev 03) (prog-if 00 [Normal decode])
> 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: 256 bytes
> Bus: primary=00, secondary=0b, subordinate=0b, sec-latency=0
> Memory behind bridge: d7300000-d73fffff
> Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort-
> <TAbort- <MAbort- <SERR- <PERR-
> BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
> PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
> Capabilities: [40] Express (v1) Root Port (Slot+), MSI 00
> DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s
> unlimited, L1 unlimited
> ExtTag- 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 #5, Speed 2.5GT/s, Width x1, ASPM L0s L1,
> Latency L0 <256ns, L1 <4us
> ClockPM- Suprise- LLActRep+ BwNot-
> LnkCtl: ASPM L1 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-
> SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd-
> HotPlug+ Surpise+
> Slot # 4, PowerLimit 6.500000; Interlock- NoCompl-
> SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet-
> CmdCplt- HPIrq- LinkChg-
> Control: AttnInd Unknown, PwrInd Unknown,
> Power- Interlock-
> SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt-
> PresDet+ Interlock-
> Changed: MRL- PresDet+ LinkState+
> RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal-
> PMEIntEna- CRSVisible-
> RootCap: CRSVisible-
> RootSta: PME ReqID 0000, PMEStatus- PMEPending-
> Capabilities: [80] Message Signalled Interrupts: Mask- 64bit-
> Queue=0/0 Enable-
> Address: fee0300c Data: 4179
> Capabilities: [90] Subsystem: Gammagraphx, Inc. Unknown device
> [0000:0000]
> Capabilities: [a0] Power Management version 2
> Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
> PME(D0+,D1-,D2-,D3hot+,D3cold+)
> Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> Kernel driver in use: pcieport-driver
> Kernel modules: shpchp
>
> 0b:00.0 Network controller [0280]: Atheros Communications, Inc. AR5418
> 802.11abgn Wireless PCI Express Adapter [168c:0024] (rev 01)
> Subsystem: Apple Computer Inc. Unknown device [106b:0087]
> 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: 256 bytes
> Interrupt: pin A routed to IRQ 16
> Region 0: Memory at d7300000 (64-bit, non-prefetchable) [size=64K]
> Capabilities: [40] Power Management version 2
> Flags: PMEClk- DSI- D1+ D2- AuxCurrent=375mA
> PME(D0+,D1+,D2-,D3hot+,D3cold-)
> Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> Capabilities: [50] Message Signalled Interrupts: Mask- 64bit-
> Queue=0/0 Enable-
> Address: 00000000 Data: 0000
> Capabilities: [60] Express (v1) Legacy Endpoint, MSI 00
> DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s
> <512ns, L1 <64us
> ExtTag- AttnBtn- AttnInd- PwrInd- RBE- FLReset-
> DevCtl: Report errors: Correctable- Non-Fatal- Fatal-
> Unsupported-
> RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
> MaxPayload 128 bytes, MaxReadReq 512 bytes
> DevSta: CorrErr- UncorrErr+ FatalErr- UnsuppReq+
> AuxPwr- TransPend-
> LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1,
> Latency L0 <512ns, L1 <64us
> ClockPM- Suprise- LLActRep- BwNot-
> LnkCtl: ASPM L1 Enabled; RCB 128 bytes Disabled-
> Retrain- CommClk+
> ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
> LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train-
> SlotClk+ DLActive- BWMgmt- ABWMgmt-
> Capabilities: [90] MSI-X: Enable- Mask- TabSize=1
> Vector table: BAR=0 offset=00000000
> PBA: BAR=0 offset=00000000
> Kernel driver in use: ath_pci
> Kernel modules: ath5k, ath_pci
>
> When the problem happens, the kernel driver reports:
> kernel: wifi0: ath_rxorn_tasklet: Receive FIFO overrun; resetting.
> kernel:last message repeated 92 times
>
> I've noticed this seems to be correlated to <MAbort+ being asserted on
> the pci port (00:1c.4) and on the device itself (0b:00.0) - thus I
> think the above message is more of a symptom, than an actual
> problem...
>
> Does anyone have any ideas (for example how [else] to clear MAbort)?
>
> This is on kernel 2.6.24.4-74.fc8 from koji for fedora core 8 (also
> present on 2.6.24.3-*.fc8), but people have reported issues on pretty
> much everything (ubuntu, etc), any desired futher information
> available by request...
>
> Not currently subscribed so please keep me CC'ed.
>
> Thanks,
> Maciej
> --
> 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/
>
--
Justin P. Mattock
Powered by blists - more mailing lists