|
Bugzilla – Full Text Bug Listing |
| Summary: | on acer one atom computer with kernel 2.3.39 systemd don't boot | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 12.1 | Reporter: | Jean-Daniel Dodin <jdd> |
| Component: | Basesystem | Assignee: | E-mail List <bnc-team-screening> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | bruno, fcrozat, zaitor |
| Version: | Factory | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Bug Depends on: | |||
| Bug Blocks: | 696902 | ||
| Attachments: |
/var/log/message after successfull boot
dmesg just after boot boot.svg |
||
|
Description
Jean-Daniel Dodin
2011-05-30 09:57:31 UTC
two precision : On factory no need to use kotd, 2.6.39 is in oss the metabug is for having it working under next 12.1 boot line : init=/bin/systemd it that was used in /etc/systemd/system.conf it's good to have [Manager] LogLevel=debug LogTarget=syslog-or-kmsg tty10 should have messages normally In case of previous install of systemd ( < version 26 ) it's better to remove all systemd related packages zypper rm systemd systemd-gtk systemd-sysvinit and clear any conf or file found in /etc/systemd and /lib/systemd today, I tried again systemd and it booted after an extremely long stop (several minutes). But it booted :-). copy of /var/log/messages just in case :-) Created attachment 434080 [details]
/var/log/message after successfull boot
tgz
ust tried again: at least 5 (five) minutes stop... before booting I had the same issue as reporter - I did the clean all recomended in comment 2 : In case of previous install of systemd ( < version 26 ) it's better to remove all systemd related packages zypper rm systemd systemd-gtk systemd-sysvinit and clear any conf or file found in /etc/systemd and /lib/systemd + I removed the systemd folder in /run Now I'm back to normal speedy bootup with systemd * I never installed systemd before, so I neglected the cleaning. No I have done. I had no systemd-sysvinit nor systemd-gtk, but only the plain old systemd, I removed it rm -R all the folders listed here zypper in systemd and now the boot is much faster. There is still a small wait at the same place, but rather acceptable (20 seconds?) thanks, I will make this default just a note: after the cleaning, I could no more stop the computer from kde (always going to gdm) in /etc/sysconfig/network/config, change NM_ONLINE_TIMEOUT to 0 and test again systemd. Created attachment 434287 [details]
dmesg just after boot
well... changing the timeout didn't change much the boot time. Investigating I noticed some nmbd problem, as this was probably the result of upgrading old config (many things stay no moren used), I cleaned the services. The long time may be simply psochologic, because nothing is displayed from the second 20 (I beg the numbers on logs are time) to the final display of gdm. I join the dmesg, with all the timing. please run systemd-analyse plot > boot.svg and attach the file to this bug report. Created attachment 434326 [details]
boot.svg
boot.svg as asked
I close this bug (fixed), because the subject is misleading (systemd boots now without problem on this computer) I will try to discuss start speed elsewhere, beginning with #700002 thanks all Now this system boots - solved by config change or system update |