Having found no help anywhere in solving this bug, I contacted Jayen Ashar and asked him if he had somehow found a workaround. He said he hadn't, and added that the problem had simply "gone away" ... So I tried "# dpkg --configure -a" today ... ... and it worked. !?! It didn't stop in the middle of the update-initramfs process... I checked kern.log (attached a extract - March 6th and 7th) ... and found that it didn't always oops! kernel oopsed on 1st March around 19.85 2nd March around 20.45 5th March around 19.65 6th March around 19.68 ... but not on 3rd March, or 4th or 7th. etc. What causes the Kernel to Oops? The order modules are loaded ? I am afraid I am not capable of understanding this and finding out on my own. Hope it helps... Jerome Sequier Une messagerie gratuite, garantie à vie et des services en plus, ça vous tente ? Je crée ma boîte mail www.laposte.net
Attachment:
kern.log.extract
Description: Binary data