On Wed, 2007-10-24 at 16:27 +0200, Ingo Molnar wrote: > > CONFIG_PROVE_LOCKING=y > CONFIG_DEBUG_LIST=y > CONFIG_FRAME_POINTER=y > CONFIG_DEBUG_SLAB=y > > and please post the resulting dmesg output - does lockdep notice any > lockup reason? (your backtrace suggests some mutex stuff so it might as > well detect it) >
Done. The results are at: http://www.dea.icai.upcomillas.es/romano/linux/info/2624rc1_2/ in the syslog-after-failed-suspend.txt file. After the failed suspend (at line 15766) there where the bunch of things in D-state. I have left the file intact. At line 17646 there is: WARNING: at kernel/lockdep.c:2033 trace_hardirqs_on() I waited a bit and then, on an already-opened root shell, did s2ram -f -p -m (line 17811) and then a lot more things happened, and I am somewhat lost. Hope this could be useful to you. Romano -- Sorry for the disclaimer --- ¡I cannot stop it! -- La presente comunicación tiene carácter confidencial y es para el exclusivo uso del destinatario indicado en la misma. Si Ud. no es el destinatario indicado, le informamos que cualquier forma de distribución, reproducción o uso de esta comunicación y/o de la información contenida en la misma están estrictamente prohibidos por la ley. Si Ud. ha recibido esta comunicación por error, por favor, notifíquelo inmediatamente al remitente contestando a este mensaje y proceda a continuación a destruirlo. Gracias por su colaboración. This communication contains confidential information. It is for the exclusive use of the intended addressee. If you are not the intended addressee, please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited by law. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy this message. Thank you for your cooperation. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
