|
Bugzilla – Full Text Bug Listing |
| Summary: | Switch from verbose to silent boot splash stops the boot process | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Andreas Schneider <asn> |
| Component: | Kernel | Assignee: | Michael Schröder <mls> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Critical | ||
| Priority: | P5 - None | CC: | mls, novell.suse, werner |
| Version: | Beta 2 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Beta-Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | /etc/init.d/boot.test | ||
|
Description
Andreas Schneider
2005-08-20 11:05:49 UTC
This was added due bug #104592 ... Michael? Why I can not restore the splash screen without stopping the boot process? Currently the restore() shell function looks like restore () { stty $otty < $REDIRECT; [[ "$splash" =~ silent ]] && echo silent > /proc/splash } were $splash contains the line get with read splash < /proc/splash in the shell function redirect() Andreas? Can you please re-enable the restore() function at line 240?
After you've done this I'd like to ask you if your can comment out
the line
stty $otty < $REDIRECT;
in restore() and reboot your system. I'd like to know if the boot
splash restore or the tty restore freeze the boot process.
Stops with #stty $otty < $REDIRECT; too, so it is the bootsplash. Yep, I can reproduce this. I've written a boot.test script which, after marked as INTERACTIVE in /etc/insserv.conf, reproduce the behaviour after insserv-ing it. Created attachment 47259 [details]
/etc/init.d/boot.test
Don't forget to mark it as INTERACTIVE in
/etc/insserv.conf before running `insserv boot.test'
Now it seems to be a kernel bug within the splash interface. *** Bug 114706 has been marked as a duplicate of this bug. *** Actually not a kernel bug, but a fd leak. Fixed in startpar and in the splash utility (better safe than sorry). *** Bug 116451 has been marked as a duplicate of this bug. *** |