Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- [root@mycubox ~]# journalctl -f
- -- Logs begin at Tue 2014-08-12 15:24:07 EDT. --
- Aug 15 17:53:49 mycubox systemd[528]: Starting Timers.
- Aug 15 17:53:49 mycubox systemd[528]: Reached target Timers.
- Aug 15 17:53:49 mycubox systemd[528]: Starting Sockets.
- Aug 15 17:53:49 mycubox systemd[528]: Reached target Sockets.
- Aug 15 17:53:49 mycubox systemd[528]: Starting Basic System.
- Aug 15 17:53:49 mycubox systemd[528]: Reached target Basic System.
- Aug 15 17:53:49 mycubox systemd[528]: Starting Default.
- Aug 15 17:53:49 mycubox systemd[528]: Reached target Default.
- Aug 15 17:53:49 mycubox systemd[528]: Startup finished in 79ms.
- Aug 15 17:53:49 mycubox systemd[1]: Started User Manager for UID 0.
- Aug 15 17:54:06 mycubox systemd-timesyncd[203]: interval/delta/delay/jitter/drift 32s/+0.097s/0.118s/0.037s/+500ppm
- Aug 15 17:54:11 mycubox sshd[552]: Accepted password for root from 192.168.10.241 port 63655 ssh2
- Aug 15 17:54:11 mycubox sshd[552]: pam_unix(sshd:session): session opened for user root by (uid=0)
- Aug 15 17:54:11 mycubox systemd[1]: Starting Session c2 of user root.
- Aug 15 17:54:11 mycubox systemd-logind[223]: New session c2 of user root.
- Aug 15 17:54:11 mycubox systemd[1]: Started Session c2 of user root.
- Aug 15 17:54:19 mycubox systemd[1]: Stopped Broadcom 43xx bluetooth HCI.
- Aug 15 17:54:26 mycubox systemd[1]: Stopped Bluetooth service.
- Aug 15 17:54:33 mycubox systemd[1]: Starting Broadcom 43xx firmware update...
- Aug 15 17:54:33 mycubox brcm43xx-firmware-update[568]: Updating bluetooth firmware via /dev/ttymxc3 from /lib/firmware/brcm/bcm4330.hcd.
- Aug 15 17:54:34 mycubox systemd[1]: Started Broadcom 43xx firmware update.
- Aug 15 17:54:34 mycubox systemd[1]: Starting Broadcom 43xx bluetooth HCI...
- Aug 15 17:54:34 mycubox systemd[1]: Started Broadcom 43xx bluetooth HCI.
- Aug 15 17:54:34 mycubox systemd[1]: Starting Load/Save RF Kill Switch Status of rfkill1...
- Aug 15 17:54:34 mycubox systemd[1]: Starting Bluetooth service...
- Aug 15 17:54:34 mycubox systemd[1]: Started Load/Save RF Kill Switch Status of rfkill1.
- Aug 15 17:54:34 mycubox bluetoothd[584]: Bluetooth daemon 5.21
- Aug 15 17:54:34 mycubox systemd[1]: Started Bluetooth service.
- Aug 15 17:54:34 mycubox systemd[1]: Starting Bluetooth.
- Aug 15 17:54:34 mycubox systemd[1]: Reached target Bluetooth.
- Aug 15 17:54:34 mycubox bluetoothd[584]: Starting SDP server
- Aug 15 17:54:34 mycubox dbus[226]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
- Aug 15 17:54:34 mycubox bluetoothd[584]: Bluetooth management interface 1.3 initialized
- Aug 15 17:54:34 mycubox systemd[1]: Starting Hostname Service...
- Aug 15 17:54:34 mycubox systemd[1]: Couldn't stat device /dev/pts/ptmx
- Aug 15 17:54:34 mycubox bluetoothd[584]: Sap driver initialization failed.
- Aug 15 17:54:34 mycubox bluetoothd[584]: sap-server: Operation not permitted (1)
- Aug 15 17:54:34 mycubox bluetoothd[584]: hci0 Load Connection Parameters failed: Unknown Command (0x01)
- Aug 15 17:54:34 mycubox dbus[226]: [system] Successfully activated service 'org.freedesktop.hostname1'
- Aug 15 17:54:34 mycubox systemd[1]: Started Hostname Service.
- Aug 15 17:54:38 mycubox systemd-timesyncd[203]: interval/delta/delay/jitter/drift 64s/+0.020s/0.037s/0.034s/+500ppm
- Aug 15 17:54:44 mycubox systemd[1]: Started Bluetooth service.
- Aug 15 17:55:04 mycubox kernel: usb 1-1: USB disconnect, device number 2
- Aug 15 17:55:43 mycubox systemd-timesyncd[203]: interval/delta/delay/jitter/drift 128s/-0.036s/0.047s/0.039s/+361ppm
- Aug 15 17:57:51 mycubox systemd-timesyncd[203]: interval/delta/delay/jitter/drift 256s/-0.006s/0.048s/0.040s/+349ppm
- Aug 15 17:58:44 mycubox bluetoothd[584]: Refusing input device connect: No such file or directory (2)
- Aug 15 17:58:44 mycubox bluetoothd[584]: Refusing connection from 38:C0:96:A8:B4:2A: unknown device
- Aug 15 17:59:20 mycubox bluetoothd[584]: Refusing input device connect: No such file or directory (2)
- Aug 15 17:59:20 mycubox bluetoothd[584]: Refusing connection from 38:C0:96:A8:B4:2A: unknown device
- Aug 15 18:00:46 mycubox bluetoothd[584]: Refusing input device connect: No such file or directory (2)
- Aug 15 18:00:46 mycubox bluetoothd[584]: Refusing connection from 38:C0:96:A8:B4:2A: unknown device
- Aug 15 18:00:51 mycubox bluetoothd[584]: Refusing input device connect: No such file or directory (2)
- Aug 15 18:00:51 mycubox bluetoothd[584]: Refusing connection from 38:C0:96:A8:B4:2A: unknown device
- Aug 15 18:00:52 mycubox bluetoothd[584]: Can't get HIDP connection info
- Aug 15 18:00:52 mycubox bluetoothd[584]: connect error: Connection refused (111)
- Aug 15 18:00:55 mycubox bluetoothd[584]: Can't get HIDP connection info
- Aug 15 18:00:55 mycubox bluetoothd[584]: connect error: Connection refused (111)
- Aug 15 18:01:05 mycubox kernel: sony 0005:054C:0268.0002: Fixing up Sony Sixaxis report descriptor
- Aug 15 18:01:05 mycubox kernel: sony 0005:054C:0268.0002: unknown main item tag 0x0
- Aug 15 18:01:05 mycubox kernel: input: Sony Computer Entertainment Wireless Controller as /devices/soc0/soc.1/2100000.aips-bus/21f0000.serial/tty/ttymxc3/hci0/hci0:11/input3
- Aug 15 18:01:05 mycubox kernel: sony 0005:054C:0268.0002: input,hidraw0: BLUETOOTH HID v1.00 Joystick [Sony Computer Entertainment Wireless Controller] on 43:30:a0:00:00:00
- Aug 15 18:01:15 mycubox bluetoothd[584]: sixaxis: compatible device connected: PLAYSTATION(R)3 Controller (054C:0268)
- Aug 15 18:01:15 mycubox kernel: sony: probe of 0005:054C:0268.0002 failed with error -5
- Aug 15 18:02:07 mycubox systemd-timesyncd[203]: interval/delta/delay/jitter/drift 256s/-0.056s/0.054s/0.048s/+241ppm
- Aug 15 18:06:24 mycubox systemd-timesyncd[203]: interval/delta/delay/jitter/drift 512s/-0.036s/0.070s/0.052s/+230ppm
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement