Arch Linux

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#30982 - [systemd] Couldn't boot since v187, relevant commit isolated

Attached to Project: Arch Linux
Opened by Andreas (misc) - Thursday, 02 August 2012, 20:29 GMT
Last edited by Dave Reisner (falconindy) - Saturday, 20 October 2012, 16:56 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Dave Reisner (falconindy)
Tom Gundersen (tomegun)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

systemd v187 and v188-git would both come to complete halt after printing "Found device <HDD label>." for each partition to be mounted. All possible then was to try to restart via C-A-D.

v186 booted fine, with each of these "Found" messages accompanied by another containing some info on what is actually being mounted.

Until yesterday I resorted to the classic initscripts, then I did a bisection. The culprit turned out to be "mount: fix for complex automounts":

http://cgit.freedesktop.org/systemd/systemd/commit/?id=36fcd77e02cedf300e2f45f2449e7e091ef5a7ab

With that commit reverted, v188-git boots and runs just fine.


Additional info:
* systemd v187 - v188-git (3bea51c)
* no difference in behavior between kernel 3.4.x and 3.5
* fstab: http://pastie.org/4379750
This task depends upon

Closed by  Dave Reisner (falconindy)
Saturday, 20 October 2012, 16:56 GMT
Reason for closing:  No response
Comment by Andreas (misc) - Thursday, 02 August 2012, 20:30 GMT
Whoops: Linux x64, testing repos enabled
Comment by Dave Reisner (falconindy) - Thursday, 02 August 2012, 21:15 GMT
Please report this on systemd-devel or the systemd bug tracker. I'm not reverting anything upstream knowing about it.
Comment by Tom Gundersen (tomegun) - Saturday, 04 August 2012, 22:09 GMT
I think you a word: "We will not revert anything _without_ upstream knowing about it."

I'll leave this open though, so that we can track this once upstream gives some feedback on what is the best course of action.
Comment by Andreas (misc) - Monday, 20 August 2012, 19:26 GMT
Posted it on the systemd bugtracker a week ago: https://bugs.freedesktop.org/show_bug.cgi?id=53406

No reply yet.
Comment by Tom Gundersen (tomegun) - Saturday, 22 September 2012, 22:57 GMT
If this still a problem? If so, would you be able to 'bisect' your fstab (by commenting out parts of it) to figure out what is the minimal fstab to cause the problem?

Loading...