I've made a clean install yesterday, for the first time restarted, everything went good and then after I updated packages and copied my old home directory to replace the new one, when I restarted it hung when it was booting. I tried reinstalling again and doing the same thing, but again same thing happened.

Here's what I see, before when the Ubuntu logo with the five dots is shown:

Then after that, 3 or 4 of the dots will load and hangs there. If I press arrow up before that, this will be shown

I started my laptop again today(the pictures are for the day before) and after that, boot up with live CD and got the logs.

dmesg: http://pastebin.com/aVxV7BQF

syslog: http://pastebin.com/4E2BrRUK

And some info:

alfred@alFitop:~$ uname -a
Linux alFitop 3.2.0-24-generic #39-Ubuntu SMP Mon May 21 16:52:17 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

lshw: http://pastebin.com/AZbKJmsT

sources.list : http://pastebin.com/2HazmuyV

My problem is a bit similar to here: http://ubuntuforums.org/showthread.php?t=1918271 Though I didn't change my x.org config. Only changed home directory and updated packages.

I've tried memtest and fschk, both passed.

In the recovery mode boot option, I've also realized that same things happen in failsafe graphical mode. But when I go into the network mode, I can boot up my system, but of course same the graphics are just basic.

Adding blacklist intel_ips to /etc/modprobe.d/blacklist.conf solves the first message, but still I get the broken pipe and CPU stack traces.

The current kernel version is 3.2.0-25, I've tried booting up in the 3.2.0-23(the one the installer came with, but same results.)

Also uninstalled apparmor, didn't help. I've installed Ubuntu again, this time without copying the home directory, also same result.

--- UPDATE ---

This problem was solved before with removing backports, but its back again! I've updated my laptop last night and the problem came back. It's definitely one of these packages.

My /var/log/apt/term.log and /var/log/apt/history.log.

I'm almost having the same situation.

--- UPDATE ---

I realized this also have happened on times that I have updated(haven't restarted after it) and my computer power has been cut off and its shutdown due to lack of power. And I realized if I just do as I answered but not in somewhere without GUI(networking mode has the GUI) it wouldn't work.