Ah, I see the problem now. ureadahead is causing the system to run out of memory before the kernel sets up the swap space. So without the spillover into swap, it's forced to kill processes, one of which is plymouth, and this explains why you're not seeing it. Just search the kern.log you uploaded for "swap" and you'll see what I mean.
[ 4.011349] 0 pages in swap cache [ 4.011350] Swap cache stats: add 0, delete 0, find 0/0 [ 4.011352] Free swap = 0kB [ 4.011353] Total swap = 0kB [ 4.016847] 751615 pages RAM [ 4.016850] 524290 pages HighMem [ 4.016851] 12490 pages reserved [ 4.016852] 443 pages shared [ 4.016853] 215331 pages non-shared [ 4.584624] Adding 2096444k swap on /dev/sda5. Priority:-1 extents:1 across:2096444k All that is *after* the ureadahead/memory errors I posted above. I agree that you might as well open a new bug against ureadahead with 'ubuntu-bug ureadahead' at this point. It'll contain all the Apport information they'll expect (instead of this xserver-xorg-video-intel info) and they won't have to wade through 10+ comments trying to figure out the problem. So if you wouldn't mind running 'ubuntu-bug ureadahead' immediately after booting into Maverick, and once you've finished reporting, post the ureadahead bug's url here and mark this report invalid. Thanks! -- conflicting fb hw usage inteldrmfb vs VESA VGA https://bugs.launchpad.net/bugs/609044 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
