On Mon, May 02, 2011, AJ ONeal wrote:
> Warning... fsck.ext3 for device /dev/mmcblk0p2 exited with signal 11.
fsck.ext3 segfaulting is pretty bad
>- Plymouth's availability reported/y affects `/` being mounted
That might be normal (see other message)
>- yet there are no errors on the
On Mon, May 02, 2011, AJ ONeal wrote:
> I don't think that plymouth is a particularly necessary service (especially
> since I don't have a display), so my temporary solution is to disable it
> like so:
> cd /etc/init
> ls plymouth*.conf | while read CONF
> do
> mv ${CONF} ${CONF}.off
> done
> Can
After rebooting several times in succession I can confirm that
- the hang at boot-time no longer occurs
- the hang at reboot still occurs
However, there is another error which has surfaced
Warning... fsck.ext3 for device /dev/mmcblk0p2 exited with signal 11.
mountall: fsck / [721] terminat
Every time I boot plymouth is always killed by SEGV
Every few reboots the system will hang without continuing to boot at this
message:
init: udev-fallback-graphics main process (993) terminated with status 1
init: plymouth main process (538) killed by SEGV signal
init: plymouth-splash main proces
