Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#40679 - [libsystemd] [systemd] [systemd-sysvcompat] System don´t boot after update.

Attached to Project: Community Packages
Opened by Alexandre Bolelli Soares (Semeion) - Wednesday, 04 June 2014, 09:17 GMT
Last edited by Dave Reisner (falconindy) - Wednesday, 04 June 2014, 13:02 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture i686
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: After my last pacman -Syu my system don´t reboot.

http://i.imgur.com/Z5MXaai.png
http://i.imgur.com/GVvCeOp.png

3 packages had updated after my pacman -Syu: libsystemd, systemd, systemd-sysvcompat.

To solve the problem i have booted in a livecd, chroot and make downgrade of that 3 packages using pacman -U <package>.

That solution was said by "sheep" in freenode #archlinux IRC channel (thanks sheep).

Additional info:
I am using 3 kernels in grub, and the system don´t boot in all.
- latest oficial
- LTS
- and my old custom kernel (Linux 3.0.27) without ipv6 and smp

Yes, i have tested all, including fallback options and none work.

* package version(s)
see log:

* config and/or log files etc.
[2014-06-04 04:06] [PACMAN] upgraded libsystemd (212-3 -> 213-5)
[2014-06-04 04:06] [PACMAN] upgraded systemd (212-3 -> 213-5)
[2014-06-04 04:06] [PACMAN] upgraded systemd-sysvcompat (212-3 -> 213-5)

Steps to reproduce:
sudo pacman -Syu

PS. I don´t speak english very well, sorry.
This task depends upon

Closed by  Dave Reisner (falconindy)
Wednesday, 04 June 2014, 13:02 GMT
Reason for closing:  None
Additional comments about closing:  No evidence of an actual bug here -- looks like problems related to a cgroup-less kernel or other misconfiguration
Comment by Alexandre Bolelli Soares (Semeion) - Wednesday, 04 June 2014, 09:29 GMT
Maybe the reason of problem is because in the moment of the first upgrade i was using my custom kernel.

I don´t know.
Comment by Alexandre Bolelli Soares (Semeion) - Wednesday, 04 June 2014, 10:02 GMT
I have systemd requeriments in my custom config, can be missing anything?

AUTOFS4_FS [=m] && BLK_DEV_BSG [=y] && CGROUPS [=y] && EPOLL [=y] && FANOTIFY [=y] && FHANDLE [=y] &&
INOTIFY_USER [=y] && NET [=y] && NET_NS [=y] && PROC_FS [=y] && SIGNALFD [=y] && SYSFS [=y] && TIMERFD [=y] &&
ANON_INODES [=y] && BLOCK [=y] && EVENTFD [=y] && FSNOTIFY [=y] && INET [=y] && NLATTR [=y]

I repeat, the problem was with all my 3 kernels, but in moment of update i was using my custom, i don´t know if it is important in this case.
Comment by Alexandre Bolelli Soares (Semeion) - Wednesday, 04 June 2014, 10:03 GMT
The others 2 kernels are oficial config/packages.
Comment by Dave Reisner (falconindy) - Wednesday, 04 June 2014, 13:01 GMT
Please use the forums for support. I don't see any behavior here that wouldn't be caused by some horrible misconfiguration or other user error, especially not if upgrading from 213-3 to 213-5 is what you claim caused this problem. The pkgrel bump only added a small change to the post_upgrade scriptlet in order to keep systemd-resolved around for users who need it.

Loading...