Lines Matching refs:that
11 2) If that does not help, try reading tricks.txt and
21 always it's a driver that is buggy. Thank God for the suspend/resume
22 debugging - the thing that Chuck tried to disable. That's often the _only_
25 driver that doesn't resume and recompile and reboot).
28 machine that doesn't boot) is:
49 which means that the last trace event was just before trying to resume
50 device 0000:01:00.0. Then figure out what driver is controlling that
55 the culprit may be a device from a loadable kernel module that is not loaded
63 that "radeonfb" simply cannot resume that device - it tries to set the
70 Reason for this is that the RTC is the only reliably available piece of
71 hardware during resume operations where a value can be set that will
78 Consequence is that after a resume (even if it is successful) your system
84 As the clock keeps ticking it is also essential that the reboot is done