Lines Matching refs:that

9 2) If that does not help, try reading tricks.txt and
19 always it's a driver that is buggy. Thank God for the suspend/resume
20 debugging - the thing that Chuck tried to disable. That's often the _only_
23 driver that doesn't resume and recompile and reboot).
26 machine that doesn't boot) is:
47    which means that the last trace event was just before trying to resume
48    device 0000:01:00.0. Then figure out what driver is controlling that
53    the culprit may be a device from a loadable kernel module that is not loaded
61 that "radeonfb" simply cannot resume that device - it tries to set the
68 Reason for this is that the RTC is the only reliably available piece of
69 hardware during resume operations where a value can be set that will
76 Consequence is that after a resume (even if it is successful) your system
82 As the clock keeps ticking it is also essential that the reboot is done