Fedora Moblin remix

Adam Williamson awilliam at redhat.com
Mon Nov 9 19:18:52 UTC 2009


On Mon, 2009-11-09 at 19:11 +0000, Bastien Nocera wrote:

> > That's a very common error message and, AFAICT anyway, doesn't really
> > indicate that anything is particularly broken. At least I see it all the
> > time on systems that otherwise appear to work fine. So if you're having
> > problems I _doubt_ they trace to that message. Check with a qualified X
> > hacker though =)
> 
> I guess, for myself, and a number of other bug reporters, that's the
> sort of error you would _see_ when an error message from the console
> gets printed using KMS.

Yeah, it's one you tend to notice when you get dumped to a console for
some other reason, but was actually there all the time and you just
weren't seeing it when whatever actually turns out to be broken was
working...

> Only problem is that it's not the error message we actually wanted to
> see. In my case, it was the initrd being unable to find its new root
> device. Which I later fixed in:
> https://bugzilla.redhat.com/show_bug.cgi?id=533824

Yeah, I have a similar case where occasionally my system just fails to
boot; I see the drm error, but it's actually grub or my BIOS falling
over. I've verified the same error exists on a successful boot, I just
don't see it because the bootsplash hides it.

-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net




More information about the fedora-devel-list mailing list