Eric Lowe wrote:
> vincent wang wrote:
>>> There's another clue though. I tried to run scanpci (always worked
>>> before) and that caused my laptop to freeze up solid. So apparently
>>> it isn't just X that is causing problems.
>>>
>> Then I'd suggest using /usr/sbin/pcitool to dump the Configuration
>> Space of both the CardBus bridge and its parent.
>
> When things are working the PCI config and BARs look normal, after
> things hose up (running scanpci a couple of times usually does it) the
> PCI config and BARs read as zero for all of the devices under the
> PCI-PCI bridge, not just the cardbus bridge (I discovered this by
> using a USB keyboard which also stopped working).
Probing the PCI bus involves changing BARs to -1 (unsigned) to determine
BAR size. Its usually a really bad idea to do this on device,
_especially_ on a PCI bus.
Running scanpci on a live system is probably a bad idea. If X is also
probing the bus in the same way, then the same problem could happen.
It would be far, far better to use the technique of gathering this data
nondestructively. The showpci tool I posted earlier does using the
libdevinfo routines, and can be used as an example.
-- Garrett
>
> Let me know what information you want me to collect/send (specifically
> any pcitool syntax to get what you need) and I'll send the info off-list.
>
> - Eric
> _______________________________________________
> laptop-discuss mailing list
> laptop-discuss at opensolaris.org
--
Garrett D'Amore, Principal Software Engineer
Tadpole Computer / Computing Technologies Division,
General Dynamics C4 Systems
http://www.tadpolecomputer.com/
Phone: 951 325-2134 Fax: 951 325-2191
