[Mageia-dev] More systemd strangeness

Thu Sep 27 20:21:05 CEST 2012

'Twas brillig, and Frank Griffin at 27/09/12 19:11 did gyre and gimble:
+> I set the systemd log-level to "debug" to debug another problem, and
+> found that a new problem with an HP printer that has been working
+> forever is apparently laid at its door:
+> 
+> Sep 27 14:07:41 ftgme2 systemd[1]:
+> sys-devices-pci0000:00-0000:00:12.0-us...ad
+> Sep 27 14:07:41 ftgme2 systemd[1]: Running GC...
+> Sep 27 14:07:41 ftgme2 systemd[1]: Collecting
+> sys-devices-pci0000:00-0000...ce
+> Sep 27 14:07:41 ftgme2 systemd[1]: Collecting dev-usb-lp0.device
+> Sep 27 14:07:41 ftgme2 kernel: usblp 1-1:1.0: usblp0: USB Bidirectional
+> p...17
+> Sep 27 14:07:41 ftgme2 systemd[1]: dev-usb-lp0.device changed dead ->
+> plugged
+> Sep 27 14:07:41 ftgme2 systemd[1]:
+> sys-devices-pci0000:00-0000:00:12.0-us...ed
+> Sep 27 14:07:47 ftgme2 kernel: usblp0: removed
+> Sep 27 14:07:47 ftgme2 systemd[1]: dev-usb-lp0.device changed plugged ->
+> dead
+> Sep 27 14:07:47 ftgme2 systemd[1]:
+> sys-devices-pci0000:00-0000:00:12.0-us...ad
+> 
+> This goes on constantly, dead -> plugged, plugged -> dead at 5 second
+> intervals.  Or is this a kernel problem and is systemd just an innocent
+> bystander ?
+
+Hmm, looks like systemd is the innocent bystander here as the message
+from the kernel is the interesting bit and systemd is just reflecting
+it's device mapping state.
+
+Does your dmesg report anything interesting going on with the device?
+
+Note that you can avoid the shortening of the lines from journalctl via
+the -a (or --all) argument.
+
+
+Col
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+