> 00:00.0 Class 0406: 1039:0406 (rev 39) (prog-if 10)
> Subsystem: 002c:8000
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
> Status: 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR+ <PERR-
> Latency: 128 max, 0 set, cache line size 06
> Region 0: Memory at 80000010 (32-bit, non-prefetchable)
> 00: 39 10 06 04 06 00 00 60 39 10 06 04 06 00 00 60
> 10: 10 00 00 80 14 00 00 80 18 00 00 80 1c 00 00 80
> 20: 20 00 00 80 24 00 00 80 28 00 00 80 2c 00 00 80
> 30: 30 00 00 80 34 00 00 80 38 00 00 80 3c 00 00 80
Hmmm, yet another case of buggy hardware. It responds with utter rubbish when
accessing bytes 0x0c to 0x3f of the configuration space. The warning messages
kernel produces are totally harmless in this case -- you can ignore them
safely.
Have a nice fortnight
-- Martin `MJ' Mares <mj@ucw.cz> http://atrey.karlin.mff.cuni.cz/~mj/ Faculty of Math and Physics, Charles University, Prague, Czech Rep., Earth "And God said: E = 1/2mv^2 - Ze^2/r ...and there *WAS* light!"- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/