Once upon a time, Dave Jones <davej@xxxxxxxxxx> said: > Hardware specific problems like this are a nightmare for us to diagnose. > It might even come down to you needing to do a bisect to find the individual > kernel change that caused the problem. (assuming you know a 'good' version > to start from) I know suspend is another "fun" area, but are there any good tools to figure out what is wrong when suspend/resume doesn't work right? I've got a problem system (RH BZ 548593) that I don't know what else I can do to try to fix. -- Chris Adams <cmadams@xxxxxxxxxx> Systems and Network Administrator - HiWAAY Internet Services I don't speak for anybody but myself - that's enough trouble. -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
