Comment 4 for bug 129196

Sorry for taking so long, but I'm quite busy :-)

So I attach a file with the relevant portion of the logs
there are two files for each logfile one labelled 2.6.17-11.log and the other 2.6.17-12.log

In fact after much trying (which is why it took me so long) I finally succeded in getting to the boot prompt with 2.6.17-12 where the kernel panicked with something along the lines of "Aiie no syncing disabling interrupt"

In reviewing the logs I see that modules loading seems to be impossible with 2.6.17-12 can this be the cause of all that ?

If there is still something I can do to help, don't hesitate to ask, I wont upgrade this particular server to gutsy for at least a week (the other ones have been upgraded without a glitch and are perfectly fonctionnal (even with the Open Manager from Dell at least after you realised that you have to replace the sh link to point to bash rather than dash) )