On 07/22/2014 07:25 AM, Matthew Gabeler-Lee wrote: > > I'll accept that the severity I originally reported may not have been > correct, and I've reduced that here (FWIW, I think I misread the > descriptions and intended to make it "important", not "serious", but > I'll go with "normal" for now). > > And clearly my analysis of the cause was flawed, and may be due to it > first happening with 1.65-1 and the same symptoms happening with 1.65-2, > leading me to assume the same causes. > > But nonetheless with l-m-t installed, my system fails to boot, and > without it it boots fine. That doesn't seem worthy of "close the bug". > > What information would be most helpful in tracking down the source of > this failure? I presume enabling systemd debug and the debug-shell, and > using that to capture ps auxww and/or pstree -alp while systemd is stuck > would be a good start, along with journalctl output to get the systemd > debug messages?
Do you have any of the critical file systems (/, /usr) on an external USB disk ? If yes, what you need to do is to blacklist the corresponding USB device. -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
