** Changed in: plymouth (Ubuntu)
Status: Incomplete = Invalid
--
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
Also added my kern.log and syslog for further insight
** Attachment added: kern.log
http://launchpadlibrarian.net/52416582/kern.log
--
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
** Attachment added: syslog
http://launchpadlibrarian.net/52416627/syslog
--
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
Shane,
Are all the boots in kern.log from the default Maverick boot? They seem to be
using the Maverick kernel, but I also noticed you suspended in a couple of
them, which would be hard to do if you can't boot :)
It seems ureadahead is taking all of your memory, and then both it and plymouth
Sorry, the kern.log snippet should have been:
[3.994657] ureadahead invoked oom-killer: gfp_mask=0xd0, order=0, oom_adj=0
[3.994664] ureadahead cpuset=/ mems_allowed=0
[3.994669] Pid: 371, comm: ureadahead Not tainted 2.6.35-10-generic
#15-Ubuntu
[3.994672] Call Trace:
...
[
@ Stenten
I may have caused some misunderstanding. This is all from Maverick and it DOES
boot into desktop.
The errors and such I have posted about stop plymouth splash from showing,
delay boot (sometimes considerably) and throw up allsorts of errors/warnings
but yes, it does boot which is
Just to add, version of ureadahead on my system IS 0.100.0-6
sh...@shane-laptop:~$ apt-cache show ureadahead
Package: ureadahead
Priority: important
Section: admin
Installed-Size: 144
Maintainer: Scott James Remnant sc...@ubuntu.com
Architecture: i386
Version: 0.100.0-6
Replaces: readahead
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
Ok, bug filed.
https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/609561
Let me know if it needs more info.
--
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
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/52354491/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/52354492/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/52354493/Dependencies.txt
**
The message that you've seen — conflicting fb hw usage inteldrmfb vs
VESA VGA - removing generic driver — is entirely expected. This is the
vesafb framebuffer gracefully handing off to the intel framebuffer.
Moving to plymouth, as this seems to be what the actual problem is.
** Package changed:
Indeed, further exploration of the various logs suggests that is exactly what
is going on.
The fact that maverick displays this message and plymouth fails, whereas lucid
doesn't display it (or more likely it is hidden by the splash) led me to
believe it was an error.
--
conflicting fb hw
Chris,
Are you sure this isn't an X bug? There's a segfault in the Xorg.0.log.old
(which is the default boot where the error occured). Wouldn't this be the
problem? Or is the segfault rather a symptom of the Plymouth bug?
--
conflicting fb hw usage inteldrmfb vs VESA VGA
13 matches
Mail list logo
