Thanks for the help. Well, let's talk with the machine. All the steps (I'm writing this, on a second machine, at the same time I perform the refered steps):
=>Boot into recovery mode. =>manually running dbus and hal ... [OK] Hmm, the system still running. Great! =>apt-get dist-upgrade (hmm, getting 2.6.24-8) =>reboot =>boot (now, in 2.6.24-8) =>Gnome can't initialize 'HAL' =>mv /root/dbus /root/hal /etc/init.d/ =>remove from /boot/grub/menu.lst, at the kernel line, options 'quiet' and 'splash' =>reboot =>boot Well, the system boot, but Gnome can't initialize 'HAL' again. Strange. =>reconfiguring hal, gdm and reboot =>boot Everything ok! Strange. What had change? Some fix? Well, I will now try running LiveCD, the one that had work one time, and now doesn't work any more. If it still fails, I don't know why it had work one time in past, and doesn't work any more.(1) Anyway, at this moment my system works, with the last upgrade. If it boot up correctly, this will be a mystery. Just one conclusion arrives: "Some of my hardware components are in a unstable state" (2) Well, let's boot LiveCD: =>Boot LiveCD (WOW, it boot correctly) Well. situation (2) had been verified. I don't change anything. I just let the laptop rest some days. lol For the machine history, it remains the log file: http://launchpadlibrarian.net/11961233/dmesg.13.02.08_21.45h.log Do you have any idea, what had cause that crash? Has I had say, on 13/02 i run memtest86+ for at least 12h and none error was reported. At the current moment, the only thing that I find strange is, at boot time, the fowling stopping times. (see comments) (...) [ 10.763506] ata1: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0x18c0 irq 14 [ 10.763546] ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0x18c8 irq 15 ## comment added. (stop for at least 30 seconds) [ 11.090929] ata1.00: ATA-6: ST9100822A, 3.01, max UDMA/100 [ 11.090969] ata1.00: 195371568 sectors, multi 16: LBA48 [ 11.091027] ata1.01: ATAPI: Slimtype DVDRW SLW-831S, WRS1, max UDMA/33 [ 11.106848] ata1.00: configured for UDMA/100 ## comment added. (stop for at least 20 seconds) [ 11.262390] Clocksource tsc unstable (delta = -56907254232 ns) (...) The current dmesg file, follow in attachment. I see now your last answer. Yes, I believe it is "BUG: soft lockup - CPU#0 stuck for 11s". At that time, I don't save the dmesg file. Now, I don't get none of that errors. ** Attachment added: "current_dmesg.21Feb15h15m.log" http://launchpadlibrarian.net/12134204/current_dmesg.21Feb15h15m.log -- BUG in kernel 2.6.24-7? BUG: unable to handle kernel NULL pointer dereference at virtual address 00000001 Based on question #24954 https://bugs.launchpad.net/bugs/191721 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
