On 25.09.2011 15:32, Rafael J. Wysocki wrote: > On Sunday, September 25, 2011, Christoph wrote: >> test results of the patch below: >> >> 1. real machine >> >> suspends fine but on wakeup, after loading image: hard reset. nvidia >> gpu => disabled compitz => wakeup worked two times. > > Hmm, so there's a separate bug related to NVidia I guess. Maybe. Just made another test: the machine (macbook) woke up, loaded image, thaw. It got stuck at vt#1, displaying console with login. Cursor blinking, but no (usb) keyboard or network enabled. Bricked?!! On the other hand I've got another box with nvidia gpu: debian5 32bit 2.6.38.2+ #3 SMP Fri Apr 1 nvidia 260.19.36 It's up since I compiled the kernel: I use it twice a week and I kept it freezed all the time. It was solid rock until today: hard reset on resume. WTF? (I remember this version combo was stable on the macbook but the kernel lacks a solid wireless driver). There are a stupid situation where you can't debug. What else can go wrong? This is off topic but it's a cute kernel crash while I gave the nouveau driver a chance: http://events.ccc.de/camp/2011/wiki/File:Dome22.jpg chris http://events.ccc.de/camp/2011/wiki/DomeTent > >> 2. virtualbox / stress test / xfs and ext4 >> >> on 3rd resume, it booted up "normal" like this: >> >> [ 3.351813] Freeing unused kernel memory: 568k freed [ >> 3.460973] Freeing unused kernel memory: 284k freed >> >> [ 17.328356] PM: Preparing processes for restore. >> ... -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
