[Splashy-devel] Bug#455872: splashy: Fails to initialize, messes up loading other modules

[Georg Wittenburg]

On Tuesday 18 December 2007 04:47:11 Luis Mondesi wrote:
> On Dec 12, 2007 3:13 AM, Georg Wittenburg <georg.wittenburg at gmx.net> wrote:
> > Package: splashy
> > Version: 0.3.7-1
> > Severity: critical
> > Justification: breaks the whole system
> >
> >
> > Hi!
> >
> > After upgrading to splashy 0.3.7, splashy fails to start with error code
> > -3 from splashy_start_splashy().
> >
> > What is worse, several unrelated other modules fail to load afterwards,
> > e.g. all sound drivers (snd_*) and the WLAN driver iwl4965. This
> > effectively breaks sound and networking on my system.
> >
> > I haven't seen any suspicios messages in dmesg or syslog that would
> > point to what exactly the problem is, but I could provide the output if
> > necessary. As a workaround I removed "splash" from the kernel command
> > line and the system works fine.
> >
> > Regards,
> >
> >   Georg
>
> This looks like udev is not starting properly. Can you move
> /usr/share/initramfs-tools/scripts/init-top/splashy to
> /usr/share/initramfs-tools/scripts/init-bottom/z_splashy
>
> and redo your initrd?
>
> update-initramfs -u
>
> That should allow udev to start first and it should fix your problem.
>
> We will do a minor (bug fix) release shortly. If you can send us the result
> of this test it will be greatly appreciated.
>
> Regards,

Unfortunately, even with the new initrd, the problem remains unchanged.

In fact, on shutdown splashy segfaults (I assume it did that, too, prior to 
the changes). If the problem had to do with hardware initialization, I find 
it strange that splashy should crash when the system is going down.

The exact message (as captured with `splashy test`) is

	segfault at 0000000c eip b7efb27d esp bfcab720 error 4

Two more bits of information: On boot, just before I get error code -3 from 
splashy_start_splashy(), it complains that it can't open /dev/fb0. Further, 
NetworkManager also gives me errors on shutdown, if splashy is 
enabled. It's quite a bit of text and I'm unsure how to capture that.

Regards,

    Georg

-- 
Georg Wittenburg
http://page.mi.fu-berlin.de/~wittenbu/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://lists.alioth.debian.org/pipermail/splashy-devel/attachments/20071218/ab5ba4f0/attachment.pgp