On Sun, Sep 02, 2007 at 11:40:17AM -0700, Arjan van de Ven wrote:

Hello,

quoted text
> can you give us an lspci -vvxx of the system when it's in this "bad"
> state? We have a very vague suspicion on something like this, the lspci
> would help us a lot (this is a really rare thing that we can't really
> reproduce, but it has been reported a few times before)

sure, took some time, I waited yesterday 4h next to the laptop and it
didn't happen ;-)
(i usually run some virtualization and then wakeups are screwed anyway)

This time i also did not forget the powertop output.

The lspcivvxx_good was done with the same linux running, after a resume
from ram, then the wakeup behavior was also ok again.
The difference is:

Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
that is in the good case, and in the bad it is MAbort+


Christian Leber
 
-- 
http://rettetdieti.vde-uni-mannheim.de/