On 22/02/2015 15:25, Simon McVittie wrote:
Control: tags -1 moreinfo
"Lockup" in what sense? Does the computer still respond to Ctrl+Alt+Del, Ctrl+Alt+F1/F2, or the "magic sysrq key" (for instance AltGr/right Alt + PrintScreen/SysRq + h to show help), or to toggling num lock/caps lock?
No it does not respond to Ctrl+Alt+Del and Ctrl+Alt+F1/F2 is too early for sure... Haven't tried "magic sysrq key" but dunno what it may bring to the discussion as I can't access log file from there...
Please provide the relevant section of a Journal log from a boot where this happens, ideally without "quiet" on the kernel command-line.
That suppose I can access to the failing system which is false (no loggin, no network).
Which dbus version were you previously using without problems - 1.8.x from unstable (which one? - apt/dpkg logs would tell you), or an earlier 1.9.x from experimental? Similarly, did you upgrade systemd from unstable's v215, or from experimental's v218?
I was using already experimental systemd 218 and also the libdbus from experimental. Only when I upgraded both to systemd 219 and dbus 1.9.10-3 did I saw problem (once about third boot). Seems to be a race condition or something...
--eric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
