[Splashy-devel] Bug#410579: splashy breaks resume from disk

[Tim Dijkstra]

On Mon, 12 Feb 2007 18:12:57 -0200
Otavio Salvador <otavio at debian.org> wrote:

> Tim Dijkstra <newsuser at famdijkstra.org> writes:
> 
> >> > Note that initramfs support is pretty much alpha quality... well we (I)
> >> > had some problems with it ourselves. The most important problem is the
> >> > time it takes to resume. For still unknow reasons splashy takes 100% of
> >> > the CPU which results (on my machine) in a delay of the boot process of
> >> > about 180 seconds and in other cases a complete hang...
> >> 
> >> That's one thing that I still want to debug. I do think that's the
> >> major blocker for 0.4 goes out.
> >
> > Last week I had a try at it using qemu. The results were a bit
> > demoralizing; stripping splashy down to the bare minimum of just a
> > splash screen also produced the same results. 
> 
> But then, looks like the process didn't go to "daemon mode" locking
> the rest of being run. If it's true, it explain why it takes more or
> less two minutes due the timeout of splashy.

No, I did had the forking still in there. If I don't fork indeed it
just waits there and times out.
Actually it is a bit worse in my qemu, the boot process just hangs...

grts Tim