Hi Yanmin, 0000:00:0c [0xc = 12 dec] is a PCI bridge. 0000:00:12 [0x12 = 18 dec] is the USB controller. Below is the lspci -vvv dump for 0000:00:0c. I retried 2.6.27 with your original patch (aer_bypass_unknown_cap_2.6.27-rc7_vw.patch) and there are no _OSC error messages and everything works fine (I get "aer 0000:00:0c.0:pcie01: service driver aer loaded" in the boot log). So it seems like something's changed b/w 2.6.27 and 2.6.28rc2 -> any ideas? Hi Taku, Any ideas based on the extended ACPI debug data provided in previous email? 00:0c.0 PCI bridge: CUSTOM (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: 32 bytes Bus: primary=00, secondary=02, subordinate=02, sec-latency=0 I/O behind bridge: 0000f000-00000fff Memory behind bridge: fc000000-fc0fffff Prefetchable memory behind bridge: 00000000fff00000-00000000000fffff 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: [50] 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: [58] Express (v2) Root Port (Slot+), MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <64ns, L1 <1us 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 #1, Speed 5GT/s, Width x8, ASPM L0s L1, Latency L0 <64ns, L1 <1us ClockPM- Suprise- LLActRep+ BwNot+ LnkCtl: ASPM Disabled; 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 # c, PowerLimit 75.000000; 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: [a0] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable+ Address: feeff00c Data: 4161 Capabilities: [b0] Subsystem: <CUSTOM> Device 1234 Capabilities: [100] Vendor Specific Information <?> Capabilities: [150] Advanced Error Reporting <?> Capabilities: [190] Access Controls <?> Kernel driver in use: pcieport-driver Kernel modules: shpchp Tomasz On Thu, Oct 30, 2008 at 1:55 AM, Zhang, Yanmin <yanmin_zhang@xxxxxxxxxxxxxxx> wrote: > > On Wed, 2008-10-29 at 13:21 -0400, Tomasz Czernecki wrote: >> Sorry - that was a typo. The 'x' should be a 'c' in my error message. > The lspci output in your previous email just shows 0000:00:0c.[012] are > USB controllers, not root ports. > >> This is the same system as I was using previously. I'll try the >> older kernel with Yanmin's original patch to see if that works to >> ensure there isn't anything else wrong with the system. The BIOS is >> also newer now but nothing should have changed in the OSC >> implementation. >> >> Attached is the output of dmesg | grep OSC. Any thoughts? Let me >> know if you need any of the dmesg dump around any of the lines (the >> boot log is 60M in size since I turned on all the debug levels so I >> just filtered out the lines with "OSC" for now) >> >> Tomasz >> >> On Wed, Oct 29, 2008 at 4:12 AM, Taku Izumi <izumi.taku@xxxxxxxxxxxxxx> wrote: >> > Hi Tomasz, >> > >> >> I got the latest 2.6 (2.6.28-rc2) working, but the problem I see now >> >> is that I get this message: >> >> >> >> "aer 0000:00:0x.0:pcie01: AER service couldn't init device: _OSC failed" >> >> >> >> I didn't get this with the older patched kernel, which worked fine. >> >> Any ideas what could be causing this? >> > >> > I tested 2.6.28-rc2 (the latest linux-next branch of Jesses' git tree) >> > on my machine, and aer driver seems to work well. >> > How about enabling CONFIG_ACPI_DEBUG in kernel config and booting >> > with acpi.deubg_level option specified ? >> > >> > Maybe your problem has anything to do with the following patch. >> > >> > http://marc.info/?l=git-commits-head&m=122506555727097&w=2 >> > >> > >> > Best regards, >> > Taku Izumi <izumi.taku@xxxxxxxxxxxxxx> >> > >> > > > -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
