API tools faq
paste
Advertisement
Guest User

Untitled

a guest
May 9th, 2024
22
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 110.72 KB | None | 0 0
raw download clone embed print report
  1. May 09 10:31:32 duet3 kernel: Booting Linux on physical CPU 0x0000000000 [0x410fd083]
  2. May 09 10:31:32 duet3 kernel: Linux version 6.6.20+rpt-rpi-v8 (debian-kernel@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 >
  3. May 09 10:31:32 duet3 kernel: KASLR enabled
  4. May 09 10:31:32 duet3 kernel: random: crng init done
  5. May 09 10:31:32 duet3 kernel: Machine model: Raspberry Pi 4 Model B Rev 1.5
  6. May 09 10:31:32 duet3 kernel: efi: UEFI not found.
  7. May 09 10:31:32 duet3 kernel: Reserved memory: created CMA memory pool at 0x000000000e000000, size 512 MiB
  8. May 09 10:31:32 duet3 kernel: OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool
  9. May 09 10:31:32 duet3 kernel: OF: reserved mem: 0x000000000e000000..0x000000002dffffff (524288 KiB) map reusable linux,cma
  10. May 09 10:31:32 duet3 kernel: OF: reserved mem: 0x000000003ee642c0..0x000000003ee646bf (1 KiB) nomap non-reusable nvram@1
  11. May 09 10:31:32 duet3 kernel: OF: reserved mem: 0x000000003ee64700..0x000000003ee64747 (0 KiB) nomap non-reusable nvram@0
  12. May 09 10:31:32 duet3 kernel: Zone ranges:
  13. May 09 10:31:32 duet3 kernel: DMA [mem 0x0000000000000000-0x000000003fffffff]
  14. May 09 10:31:32 duet3 kernel: DMA32 [mem 0x0000000040000000-0x000000007fffffff]
  15. May 09 10:31:32 duet3 kernel: Normal empty
  16. May 09 10:31:32 duet3 kernel: Movable zone start for each node
  17. May 09 10:31:32 duet3 kernel: Early memory node ranges
  18. May 09 10:31:32 duet3 kernel: node 0: [mem 0x0000000000000000-0x000000003b2fffff]
  19. May 09 10:31:32 duet3 kernel: node 0: [mem 0x0000000040000000-0x000000007fffffff]
  20. May 09 10:31:32 duet3 kernel: Initmem setup node 0 [mem 0x0000000000000000-0x000000007fffffff]
  21. May 09 10:31:32 duet3 kernel: On node 0, zone DMA32: 19712 pages in unavailable ranges
  22. May 09 10:31:32 duet3 kernel: percpu: Embedded 30 pages/cpu s85672 r8192 d29016 u122880
  23. May 09 10:31:32 duet3 kernel: pcpu-alloc: s85672 r8192 d29016 u122880 alloc=30*4096
  24. May 09 10:31:32 duet3 kernel: pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
  25. May 09 10:31:32 duet3 kernel: Detected PIPT I-cache on CPU0
  26. May 09 10:31:32 duet3 kernel: CPU features: detected: Spectre-v2
  27. May 09 10:31:32 duet3 kernel: CPU features: detected: Spectre-v3a
  28. May 09 10:31:32 duet3 kernel: CPU features: detected: Spectre-v4
  29. May 09 10:31:32 duet3 kernel: CPU features: detected: Spectre-BHB
  30. May 09 10:31:32 duet3 kernel: CPU features: kernel page table isolation forced ON by KASLR
  31. May 09 10:31:32 duet3 kernel: CPU features: detected: Kernel page table isolation (KPTI)
  32. May 09 10:31:32 duet3 kernel: CPU features: detected: ARM erratum 1742098
  33. May 09 10:31:32 duet3 kernel: CPU features: detected: ARM errata 1165522, 1319367, or 1530923
  34. May 09 10:31:32 duet3 kernel: alternatives: applying boot alternatives
  35. May 09 10:31:32 duet3 kernel: Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=>
  36. May 09 10:31:32 duet3 kernel: Unknown kernel command line parameters "splash", will be passed to user space.
  37. May 09 10:31:32 duet3 kernel: Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes, linear)
  38. May 09 10:31:32 duet3 kernel: Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes, linear)
  39. May 09 10:31:32 duet3 kernel: Built 1 zonelists, mobility grouping on. Total pages: 496692
  40. May 09 10:31:32 duet3 kernel: mem auto-init: stack:all(zero), heap alloc:off, heap free:off
  41. May 09 10:31:32 duet3 kernel: software IO TLB: area num 4.
  42. May 09 10:31:32 duet3 kernel: software IO TLB: mapped [mem 0x0000000037300000-0x000000003b300000] (64MB)
  43. May 09 10:31:32 duet3 kernel: Memory: 1345392K/2018304K available (13376K kernel code, 2210K rwdata, 4260K rodata, 4864K init, 1083K bss, 148624K reserved, 524288K cma-rese>
  44. May 09 10:31:32 duet3 kernel: SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
  45. May 09 10:31:32 duet3 kernel: ftrace: allocating 43116 entries in 169 pages
  46. May 09 10:31:32 duet3 kernel: ftrace: allocated 169 pages with 4 groups
  47. May 09 10:31:32 duet3 kernel: trace event string verifier disabled
  48. May 09 10:31:32 duet3 kernel: rcu: Preemptible hierarchical RCU implementation.
  49. May 09 10:31:32 duet3 kernel: rcu: RCU event tracing is enabled.
  50. May 09 10:31:32 duet3 kernel: rcu: RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=4.
  51. May 09 10:31:32 duet3 kernel: Trampoline variant of Tasks RCU enabled.
  52. May 09 10:31:32 duet3 kernel: Rude variant of Tasks RCU enabled.
  53. May 09 10:31:32 duet3 kernel: Tracing variant of Tasks RCU enabled.
  54. May 09 10:31:32 duet3 kernel: rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.
  55. May 09 10:31:32 duet3 kernel: rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
  56. May 09 10:31:32 duet3 kernel: NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
  57. May 09 10:31:32 duet3 kernel: Root IRQ handler: gic_handle_irq
  58. May 09 10:31:32 duet3 kernel: GIC: Using split EOI/Deactivate mode
  59. May 09 10:31:32 duet3 kernel: rcu: srcu_init: Setting srcu_struct sizes based on contention.
  60. May 09 10:31:32 duet3 kernel: arch_timer: cp15 timer(s) running at 54.00MHz (phys).
  61. May 09 10:31:32 duet3 kernel: clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0xc743ce346, max_idle_ns: 440795203123 ns
  62. May 09 10:31:32 duet3 kernel: sched_clock: 56 bits at 54MHz, resolution 18ns, wraps every 4398046511102ns
  63. May 09 10:31:32 duet3 kernel: Console: colour dummy device 80x25
  64. May 09 10:31:32 duet3 kernel: printk: console [tty1] enabled
  65. May 09 10:31:32 duet3 kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 108.00 BogoMIPS (lpj=216000)
  66. May 09 10:31:32 duet3 kernel: pid_max: default: 32768 minimum: 301
  67. May 09 10:31:32 duet3 kernel: LSM: initializing lsm=capability,apparmor,integrity
  68. May 09 10:31:32 duet3 kernel: AppArmor: AppArmor initialized
  69. May 09 10:31:32 duet3 kernel: Mount-cache hash table entries: 4096 (order: 3, 32768 bytes, linear)
  70. May 09 10:31:32 duet3 kernel: Mountpoint-cache hash table entries: 4096 (order: 3, 32768 bytes, linear)
  71. May 09 10:31:32 duet3 kernel: cgroup: Disabling memory control group subsystem
  72. May 09 10:31:32 duet3 kernel: RCU Tasks: Setting shift to 2 and lim to 1 rcu_task_cb_adjust=1.
  73. May 09 10:31:32 duet3 kernel: RCU Tasks Rude: Setting shift to 2 and lim to 1 rcu_task_cb_adjust=1.
  74. May 09 10:31:32 duet3 kernel: RCU Tasks Trace: Setting shift to 2 and lim to 1 rcu_task_cb_adjust=1.
  75. May 09 10:31:32 duet3 kernel: rcu: Hierarchical SRCU implementation.
  76. May 09 10:31:32 duet3 kernel: rcu: Max phase no-delay instances is 1000.
  77. May 09 10:31:32 duet3 kernel: EFI services will not be available.
  78. May 09 10:31:32 duet3 kernel: smp: Bringing up secondary CPUs ...
  79. May 09 10:31:32 duet3 kernel: Detected PIPT I-cache on CPU1
  80. May 09 10:31:32 duet3 kernel: CPU1: Booted secondary processor 0x0000000001 [0x410fd083]
  81. May 09 10:31:32 duet3 kernel: Detected PIPT I-cache on CPU2
  82. May 09 10:31:32 duet3 kernel: CPU2: Booted secondary processor 0x0000000002 [0x410fd083]
  83. May 09 10:31:32 duet3 kernel: Detected PIPT I-cache on CPU3
  84. May 09 10:31:32 duet3 kernel: CPU3: Booted secondary processor 0x0000000003 [0x410fd083]
  85. May 09 10:31:32 duet3 kernel: smp: Brought up 1 node, 4 CPUs
  86. May 09 10:31:32 duet3 kernel: SMP: Total of 4 processors activated.
  87. May 09 10:31:32 duet3 kernel: CPU features: detected: 32-bit EL0 Support
  88. May 09 10:31:32 duet3 kernel: CPU features: detected: 32-bit EL1 Support
  89. May 09 10:31:32 duet3 kernel: CPU features: detected: CRC32 instructions
  90. May 09 10:31:32 duet3 kernel: CPU: All CPU(s) started at EL2
  91. May 09 10:31:32 duet3 kernel: alternatives: applying system-wide alternatives
  92. May 09 10:31:32 duet3 kernel: devtmpfs: initialized
  93. May 09 10:31:32 duet3 kernel: Enabled cp15_barrier support
  94. May 09 10:31:32 duet3 kernel: Enabled setend support
  95. May 09 10:31:32 duet3 kernel: clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
  96. May 09 10:31:32 duet3 kernel: futex hash table entries: 1024 (order: 4, 65536 bytes, linear)
  97. May 09 10:31:32 duet3 kernel: pinctrl core: initialized pinctrl subsystem
  98. May 09 10:31:32 duet3 kernel: DMI not present or invalid.
  99. May 09 10:31:32 duet3 kernel: NET: Registered PF_NETLINK/PF_ROUTE protocol family
  100. May 09 10:31:32 duet3 kernel: DMA: preallocated 1024 KiB GFP_KERNEL pool for atomic allocations
  101. May 09 10:31:32 duet3 kernel: DMA: preallocated 1024 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations
  102. May 09 10:31:32 duet3 kernel: DMA: preallocated 1024 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations
  103. May 09 10:31:32 duet3 kernel: audit: initializing netlink subsys (disabled)
  104. May 09 10:31:32 duet3 kernel: audit: type=2000 audit(0.036:1): state=initialized audit_enabled=0 res=1
  105. May 09 10:31:32 duet3 kernel: thermal_sys: Registered thermal governor 'step_wise'
  106. May 09 10:31:32 duet3 kernel: cpuidle: using governor menu
  107. May 09 10:31:32 duet3 kernel: hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
  108. May 09 10:31:32 duet3 kernel: ASID allocator initialised with 32768 entries
  109. May 09 10:31:32 duet3 kernel: Serial: AMBA PL011 UART driver
  110. May 09 10:31:32 duet3 kernel: bcm2835-mbox fe00b880.mailbox: mailbox enabled
  111. May 09 10:31:32 duet3 kernel: raspberrypi-firmware soc:firmware: Attached to firmware from 2024-02-29T12:24:53, variant start
  112. May 09 10:31:32 duet3 kernel: raspberrypi-firmware soc:firmware: Firmware hash is f4e2138c2adc8f3a92a3a65939e458f11d7298ba
  113. May 09 10:31:32 duet3 kernel: Modules: 2G module region forced by RANDOMIZE_MODULE_REGION_FULL
  114. May 09 10:31:32 duet3 kernel: Modules: 0 pages in range for non-PLT usage
  115. May 09 10:31:32 duet3 kernel: Modules: 517792 pages in range for PLT usage
  116. May 09 10:31:32 duet3 kernel: bcm2835-dma fe007000.dma-controller: DMA legacy API manager, dmachans=0x1
  117. May 09 10:31:32 duet3 kernel: iommu: Default domain type: Translated
  118. May 09 10:31:32 duet3 kernel: iommu: DMA domain TLB invalidation policy: strict mode
  119. May 09 10:31:32 duet3 kernel: SCSI subsystem initialized
  120. May 09 10:31:32 duet3 kernel: usbcore: registered new interface driver usbfs
  121. May 09 10:31:32 duet3 kernel: usbcore: registered new interface driver hub
  122. May 09 10:31:32 duet3 kernel: usbcore: registered new device driver usb
  123. May 09 10:31:32 duet3 kernel: pps_core: LinuxPPS API ver. 1 registered
  124. May 09 10:31:32 duet3 kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
  125. May 09 10:31:32 duet3 kernel: PTP clock support registered
  126. May 09 10:31:32 duet3 kernel: vgaarb: loaded
  127. May 09 10:31:32 duet3 kernel: clocksource: Switched to clocksource arch_sys_counter
  128. May 09 10:31:32 duet3 kernel: VFS: Disk quotas dquot_6.6.0
  129. May 09 10:31:32 duet3 kernel: VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
  130. May 09 10:31:32 duet3 kernel: FS-Cache: Loaded
  131. May 09 10:31:32 duet3 kernel: CacheFiles: Loaded
  132. May 09 10:31:32 duet3 kernel: AppArmor: AppArmor Filesystem Enabled
  133. May 09 10:31:32 duet3 kernel: NET: Registered PF_INET protocol family
  134. May 09 10:31:32 duet3 kernel: IP idents hash table entries: 32768 (order: 6, 262144 bytes, linear)
  135. May 09 10:31:32 duet3 kernel: tcp_listen_portaddr_hash hash table entries: 1024 (order: 2, 16384 bytes, linear)
  136. May 09 10:31:32 duet3 kernel: Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)
  137. May 09 10:31:32 duet3 kernel: TCP established hash table entries: 16384 (order: 5, 131072 bytes, linear)
  138. May 09 10:31:32 duet3 kernel: TCP bind hash table entries: 16384 (order: 7, 524288 bytes, linear)
  139. May 09 10:31:32 duet3 kernel: TCP: Hash tables configured (established 16384 bind 16384)
  140. May 09 10:31:32 duet3 kernel: MPTCP token hash table entries: 2048 (order: 3, 49152 bytes, linear)
  141. May 09 10:31:32 duet3 kernel: UDP hash table entries: 1024 (order: 3, 32768 bytes, linear)
  142. May 09 10:31:32 duet3 kernel: UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes, linear)
  143. May 09 10:31:32 duet3 kernel: NET: Registered PF_UNIX/PF_LOCAL protocol family
  144. May 09 10:31:32 duet3 kernel: RPC: Registered named UNIX socket transport module.
  145. May 09 10:31:32 duet3 kernel: RPC: Registered udp transport module.
  146. May 09 10:31:32 duet3 kernel: RPC: Registered tcp transport module.
  147. May 09 10:31:32 duet3 kernel: RPC: Registered tcp-with-tls transport module.
  148. May 09 10:31:32 duet3 kernel: RPC: Registered tcp NFSv4.1 backchannel transport module.
  149. May 09 10:31:32 duet3 kernel: PCI: CLS 0 bytes, default 64
  150. May 09 10:31:32 duet3 kernel: Trying to unpack rootfs image as initramfs...
  151. May 09 10:31:32 duet3 kernel: kvm [1]: IPA Size Limit: 44 bits
  152. May 09 10:31:32 duet3 kernel: kvm [1]: vgic interrupt IRQ9
  153. May 09 10:31:32 duet3 kernel: kvm [1]: Hyp mode initialized successfully
  154. May 09 10:31:32 duet3 kernel: Initialise system trusted keyrings
  155. May 09 10:31:32 duet3 kernel: workingset: timestamp_bits=46 max_order=19 bucket_order=0
  156. May 09 10:31:32 duet3 kernel: zbud: loaded
  157. May 09 10:31:32 duet3 kernel: NFS: Registering the id_resolver key type
  158. May 09 10:31:32 duet3 kernel: Key type id_resolver registered
  159. May 09 10:31:32 duet3 kernel: Key type id_legacy registered
  160. May 09 10:31:32 duet3 kernel: nfs4filelayout_init: NFSv4 File Layout Driver Registering...
  161. May 09 10:31:32 duet3 kernel: nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering...
  162. May 09 10:31:32 duet3 kernel: Key type asymmetric registered
  163. May 09 10:31:32 duet3 kernel: Asymmetric key parser 'x509' registered
  164. May 09 10:31:32 duet3 kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 247)
  165. May 09 10:31:32 duet3 kernel: io scheduler mq-deadline registered
  166. May 09 10:31:32 duet3 kernel: io scheduler kyber registered
  167. May 09 10:31:32 duet3 kernel: io scheduler bfq registered
  168. May 09 10:31:32 duet3 kernel: irq_brcmstb_l2: registered L2 intc (/soc/interrupt-controller@7ef00100, parent irq: 23)
  169. May 09 10:31:32 duet3 kernel: brcm-pcie fd500000.pcie: host bridge /scb/pcie@7d500000 ranges:
  170. May 09 10:31:32 duet3 kernel: brcm-pcie fd500000.pcie: No bus range found for /scb/pcie@7d500000, using [bus 00-ff]
  171. May 09 10:31:32 duet3 kernel: brcm-pcie fd500000.pcie: MEM 0x0600000000..0x063fffffff -> 0x00c0000000
  172. May 09 10:31:32 duet3 kernel: brcm-pcie fd500000.pcie: IB MEM 0x0000000000..0x007fffffff -> 0x0400000000
  173. May 09 10:31:32 duet3 kernel: brcm-pcie fd500000.pcie: PCI host bridge to bus 0000:00
  174. May 09 10:31:32 duet3 kernel: pci_bus 0000:00: root bus resource [bus 00-ff]
  175. May 09 10:31:32 duet3 kernel: pci_bus 0000:00: root bus resource [mem 0x600000000-0x63fffffff] (bus address [0xc0000000-0xffffffff])
  176. May 09 10:31:32 duet3 kernel: pci 0000:00:00.0: [14e4:2711] type 01 class 0x060400
  177. May 09 10:31:32 duet3 kernel: pci 0000:00:00.0: PME# supported from D0 D3hot
  178. May 09 10:31:32 duet3 kernel: pci 0000:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
  179. May 09 10:31:32 duet3 kernel: pci_bus 0000:01: supply vpcie3v3 not found, using dummy regulator
  180. May 09 10:31:32 duet3 kernel: pci_bus 0000:01: supply vpcie3v3aux not found, using dummy regulator
  181. May 09 10:31:32 duet3 kernel: pci_bus 0000:01: supply vpcie12v not found, using dummy regulator
  182. May 09 10:31:32 duet3 kernel: brcm-pcie fd500000.pcie: link up, 5.0 GT/s PCIe x1 (SSC)
  183. May 09 10:31:32 duet3 kernel: pci 0000:01:00.0: [1106:3483] type 00 class 0x0c0330
  184. May 09 10:31:32 duet3 kernel: pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x00000fff 64bit]
  185. May 09 10:31:32 duet3 kernel: pci 0000:01:00.0: PME# supported from D0 D3hot
  186. May 09 10:31:32 duet3 kernel: pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
  187. May 09 10:31:32 duet3 kernel: pci 0000:00:00.0: BAR 8: assigned [mem 0x600000000-0x6000fffff]
  188. May 09 10:31:32 duet3 kernel: pci 0000:01:00.0: BAR 0: assigned [mem 0x600000000-0x600000fff 64bit]
  189. May 09 10:31:32 duet3 kernel: pci 0000:00:00.0: PCI bridge to [bus 01]
  190. May 09 10:31:32 duet3 kernel: pci 0000:00:00.0: bridge window [mem 0x600000000-0x6000fffff]
  191. May 09 10:31:32 duet3 kernel: pcieport 0000:00:00.0: enabling device (0000 -> 0002)
  192. May 09 10:31:32 duet3 kernel: pcieport 0000:00:00.0: PME: Signaling with IRQ 27
  193. May 09 10:31:32 duet3 kernel: pcieport 0000:00:00.0: AER: enabled with IRQ 27
  194. May 09 10:31:32 duet3 kernel: brcm-pcie fd500000.pcie: clkreq control enabled
  195. May 09 10:31:32 duet3 kernel: simple-framebuffer 3e961000.framebuffer: framebuffer at 0x3e961000, 0x195000 bytes
  196. May 09 10:31:32 duet3 kernel: simple-framebuffer 3e961000.framebuffer: format=a8r8g8b8, mode=720x576x32, linelength=2880
  197. May 09 10:31:32 duet3 kernel: Console: switching to colour frame buffer device 90x36
  198. May 09 10:31:32 duet3 kernel: simple-framebuffer 3e961000.framebuffer: fb0: simplefb registered!
  199. May 09 10:31:32 duet3 kernel: iproc-rng200 fe104000.rng: hwrng registered
  200. May 09 10:31:32 duet3 kernel: vc-mem: phys_addr:0x00000000 mem_base=0x3eb00000 mem_size:0x3ff00000(1023 MiB)
  201. May 09 10:31:32 duet3 kernel: brd: module loaded
  202. May 09 10:31:32 duet3 kernel: loop: module loaded
  203. May 09 10:31:32 duet3 kernel: Loading iSCSI transport class v2.0-870.
  204. May 09 10:31:32 duet3 kernel: bcmgenet fd580000.ethernet: GENET 5.0 EPHY: 0x0000
  205. May 09 10:31:32 duet3 kernel: Freeing initrd memory: 15684K
  206. May 09 10:31:32 duet3 kernel: unimac-mdio unimac-mdio.-19: Broadcom UniMAC MDIO bus
  207. May 09 10:31:32 duet3 kernel: usbcore: registered new device driver r8152-cfgselector
  208. May 09 10:31:32 duet3 kernel: usbcore: registered new interface driver r8152
  209. May 09 10:31:32 duet3 kernel: usbcore: registered new interface driver lan78xx
  210. May 09 10:31:32 duet3 kernel: usbcore: registered new interface driver smsc95xx
  211. May 09 10:31:32 duet3 kernel: xhci_hcd 0000:01:00.0: xHCI Host Controller
  212. May 09 10:31:32 duet3 kernel: xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 1
  213. May 09 10:31:32 duet3 kernel: xhci_hcd 0000:01:00.0: hcc params 0x002841eb hci version 0x100 quirks 0x0300240000000890
  214. May 09 10:31:32 duet3 kernel: xhci_hcd 0000:01:00.0: xHCI Host Controller
  215. May 09 10:31:32 duet3 kernel: xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 2
  216. May 09 10:31:32 duet3 kernel: xhci_hcd 0000:01:00.0: Host supports USB 3.0 SuperSpeed
  217. May 09 10:31:32 duet3 kernel: usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.06
  218. May 09 10:31:32 duet3 kernel: usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
  219. May 09 10:31:32 duet3 kernel: usb usb1: Product: xHCI Host Controller
  220. May 09 10:31:32 duet3 kernel: usb usb1: Manufacturer: Linux 6.6.20+rpt-rpi-v8 xhci-hcd
  221. May 09 10:31:32 duet3 kernel: usb usb1: SerialNumber: 0000:01:00.0
  222. May 09 10:31:32 duet3 kernel: hub 1-0:1.0: USB hub found
  223. May 09 10:31:32 duet3 kernel: hub 1-0:1.0: 1 port detected
  224. May 09 10:31:32 duet3 kernel: usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.06
  225. May 09 10:31:32 duet3 kernel: usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
  226. May 09 10:31:32 duet3 kernel: usb usb2: Product: xHCI Host Controller
  227. May 09 10:31:32 duet3 kernel: usb usb2: Manufacturer: Linux 6.6.20+rpt-rpi-v8 xhci-hcd
  228. May 09 10:31:32 duet3 kernel: usb usb2: SerialNumber: 0000:01:00.0
  229. May 09 10:31:32 duet3 kernel: hub 2-0:1.0: USB hub found
  230. May 09 10:31:32 duet3 kernel: hub 2-0:1.0: 4 ports detected
  231. May 09 10:31:32 duet3 kernel: dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
  232. May 09 10:31:32 duet3 kernel: dwc_otg: FIQ enabled
  233. May 09 10:31:32 duet3 kernel: dwc_otg: NAK holdoff enabled
  234. May 09 10:31:32 duet3 kernel: dwc_otg: FIQ split-transaction FSM enabled
  235. May 09 10:31:32 duet3 kernel: Module dwc_common_port init
  236. May 09 10:31:32 duet3 kernel: usbcore: registered new interface driver uas
  237. May 09 10:31:32 duet3 kernel: usbcore: registered new interface driver usb-storage
  238. May 09 10:31:32 duet3 kernel: mousedev: PS/2 mouse device common for all mice
  239. May 09 10:31:32 duet3 kernel: sdhci: Secure Digital Host Controller Interface driver
  240. May 09 10:31:32 duet3 kernel: sdhci: Copyright(c) Pierre Ossman
  241. May 09 10:31:32 duet3 kernel: sdhci-pltfm: SDHCI platform and OF driver helper
  242. May 09 10:31:32 duet3 kernel: ledtrig-cpu: registered to indicate activity on CPUs
  243. May 09 10:31:32 duet3 kernel: hid: raw HID events driver (C) Jiri Kosina
  244. May 09 10:31:32 duet3 kernel: usbcore: registered new interface driver usbhid
  245. May 09 10:31:32 duet3 kernel: usbhid: USB HID core driver
  246. May 09 10:31:32 duet3 kernel: hw perfevents: enabled with armv8_cortex_a72 PMU driver, 7 counters available
  247. May 09 10:31:32 duet3 kernel: NET: Registered PF_PACKET protocol family
  248. May 09 10:31:32 duet3 kernel: Key type dns_resolver registered
  249. May 09 10:31:32 duet3 kernel: registered taskstats version 1
  250. May 09 10:31:32 duet3 kernel: Loading compiled-in X.509 certificates
  251. May 09 10:31:32 duet3 kernel: Key type .fscrypt registered
  252. May 09 10:31:32 duet3 kernel: Key type fscrypt-provisioning registered
  253. May 09 10:31:32 duet3 kernel: AppArmor: AppArmor sha1 policy hashing enabled
  254. May 09 10:31:32 duet3 kernel: uart-pl011 fe201000.serial: there is not valid maps for state default
  255. May 09 10:31:32 duet3 kernel: uart-pl011 fe201000.serial: cts_event_workaround enabled
  256. May 09 10:31:32 duet3 kernel: fe201000.serial: ttyAMA1 at MMIO 0xfe201000 (irq = 36, base_baud = 0) is a PL011 rev2
  257. May 09 10:31:32 duet3 kernel: serial serial0: tty port ttyAMA1 registered
  258. May 09 10:31:32 duet3 kernel: bcm2835-wdt bcm2835-wdt: Broadcom BCM2835 watchdog timer
  259. May 09 10:31:32 duet3 kernel: bcm2835-power bcm2835-power: Broadcom BCM2835 power domains driver
  260. May 09 10:31:32 duet3 kernel: mmc-bcm2835 fe300000.mmcnr: mmc_debug:0 mmc_debug2:0
  261. May 09 10:31:32 duet3 kernel: mmc-bcm2835 fe300000.mmcnr: DMA channel allocated
  262. May 09 10:31:32 duet3 kernel: mmc1: Controller never released inhibit bit(s).
  263. May 09 10:31:32 duet3 kernel: of_cfs_init
  264. May 09 10:31:32 duet3 kernel: of_cfs_init: OK
  265. May 09 10:31:32 duet3 kernel: clk: Disabling unused clocks
  266. May 09 10:31:32 duet3 kernel: mmc0: SDHCI controller on fe340000.mmc [fe340000.mmc] using ADMA
  267. May 09 10:31:32 duet3 kernel: Freeing unused kernel memory: 4864K
  268. May 09 10:31:32 duet3 kernel: Run /init as init process
  269. May 09 10:31:32 duet3 kernel: with arguments:
  270. May 09 10:31:32 duet3 kernel: /init
  271. May 09 10:31:32 duet3 kernel: splash
  272. May 09 10:31:32 duet3 kernel: with environment:
  273. May 09 10:31:32 duet3 kernel: HOME=/
  274. May 09 10:31:32 duet3 kernel: TERM=linux
  275. May 09 10:31:32 duet3 kernel: mmc1: new high speed SDIO card at address 0001
  276. May 09 10:31:32 duet3 kernel: usb 1-1: new high-speed USB device number 2 using xhci_hcd
  277. May 09 10:31:32 duet3 kernel: usb 1-1: New USB device found, idVendor=2109, idProduct=3431, bcdDevice= 4.21
  278. May 09 10:31:32 duet3 kernel: usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
  279. May 09 10:31:32 duet3 kernel: usb 1-1: Product: USB2.0 Hub
  280. May 09 10:31:32 duet3 kernel: hub 1-1:1.0: USB hub found
  281. May 09 10:31:32 duet3 kernel: hub 1-1:1.0: 4 ports detected
  282. May 09 10:31:32 duet3 kernel: usb 2-1: new SuperSpeed USB device number 2 using xhci_hcd
  283. May 09 10:31:32 duet3 kernel: usb 2-1: New USB device found, idVendor=152d, idProduct=0576, bcdDevice=12.01
  284. May 09 10:31:32 duet3 kernel: usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
  285. May 09 10:31:32 duet3 kernel: usb 2-1: Product: External Disk 3.0
  286. May 09 10:31:32 duet3 kernel: usb 2-1: Manufacturer: JMicron
  287. May 09 10:31:32 duet3 kernel: usb 2-1: SerialNumber: 000000778899
  288. May 09 10:31:32 duet3 kernel: scsi host0: uas
  289. May 09 10:31:32 duet3 kernel: scsi 0:0:0:0: Direct-Access JMicron Tech 1201 PQ: 0 ANSI: 6
  290. May 09 10:31:32 duet3 kernel: sd 0:0:0:0: [sda] 250069680 512-byte logical blocks: (128 GB/119 GiB)
  291. May 09 10:31:32 duet3 kernel: sd 0:0:0:0: [sda] 4096-byte physical blocks
  292. May 09 10:31:32 duet3 kernel: sd 0:0:0:0: [sda] Write Protect is off
  293. May 09 10:31:32 duet3 kernel: sd 0:0:0:0: [sda] Mode Sense: 53 00 00 08
  294. May 09 10:31:32 duet3 kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
  295. May 09 10:31:32 duet3 kernel: sd 0:0:0:0: [sda] Preferred minimum I/O size 4096 bytes
  296. May 09 10:31:32 duet3 kernel: sd 0:0:0:0: [sda] Optimal transfer size 33553920 bytes not a multiple of preferred minimum block size (4096 bytes)
  297. May 09 10:31:32 duet3 kernel: sda: sda1 sda2
  298. May 09 10:31:32 duet3 kernel: sd 0:0:0:0: [sda] Attached SCSI disk
  299. May 09 10:31:32 duet3 kernel: usb 1-1.2: new low-speed USB device number 3 using xhci_hcd
  300. May 09 10:31:32 duet3 kernel: usb 1-1.2: New USB device found, idVendor=c0f4, idProduct=08c0, bcdDevice= 1.10
  301. May 09 10:31:32 duet3 kernel: usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
  302. May 09 10:31:32 duet3 kernel: usb 1-1.2: Product: usb keyboard
  303. May 09 10:31:32 duet3 kernel: usb 1-1.2: Manufacturer: SZH
  304. May 09 10:31:32 duet3 kernel: brcmstb-i2c fef04500.i2c: @97500hz registered in polling mode
  305. May 09 10:31:32 duet3 kernel: brcmstb-i2c fef09500.i2c: @97500hz registered in polling mode
  306. May 09 10:31:32 duet3 kernel: i2c i2c-22: Added multiplexed i2c bus 0
  307. May 09 10:31:32 duet3 kernel: i2c i2c-22: Added multiplexed i2c bus 10
  308. May 09 10:31:32 duet3 kernel: input: SZH usb keyboard as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.2/1-1.2:1.0/0003:C0F4:08C0.00>
  309. May 09 10:31:32 duet3 kernel: [drm] Initialized v3d 1.0.0 20180419 for fec00000.v3d on minor 0
  310. May 09 10:31:32 duet3 kernel: Console: switching to colour dummy device 80x25
  311. May 09 10:31:32 duet3 kernel: vc4-drm gpu: bound fe400000.hvs (ops vc4_hvs_ops [vc4])
  312. May 09 10:31:32 duet3 kernel: hid-generic 0003:C0F4:08C0.0001: input,hidraw0: USB HID v1.10 Keyboard [SZH usb keyboard] on usb-0000:01:00.0-1.2/input0
  313. May 09 10:31:32 duet3 kernel: Registered IR keymap rc-cec
  314. May 09 10:31:32 duet3 kernel: rc rc0: vc4-hdmi-0 as /devices/platform/soc/fef00700.hdmi/rc/rc0
  315. May 09 10:31:32 duet3 kernel: input: vc4-hdmi-0 as /devices/platform/soc/fef00700.hdmi/rc/rc0/input1
  316. May 09 10:31:32 duet3 kernel: input: SZH usb keyboard Consumer Control as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.2/1-1.2:1.1/>
  317. May 09 10:31:32 duet3 kernel: input: vc4-hdmi-0 HDMI Jack as /devices/platform/soc/fef00700.hdmi/sound/card0/input2
  318. May 09 10:31:32 duet3 kernel: input: SZH usb keyboard System Control as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.2/1-1.2:1.1/00>
  319. May 09 10:31:32 duet3 kernel: vc4-drm gpu: bound fef00700.hdmi (ops vc4_hdmi_ops [vc4])
  320. May 09 10:31:32 duet3 kernel: hid-generic 0003:C0F4:08C0.0002: input,hidraw1: USB HID v1.10 Device [SZH usb keyboard] on usb-0000:01:00.0-1.2/input1
  321. May 09 10:31:32 duet3 kernel: Registered IR keymap rc-cec
  322. May 09 10:31:32 duet3 kernel: rc rc1: vc4-hdmi-1 as /devices/platform/soc/fef05700.hdmi/rc/rc1
  323. May 09 10:31:32 duet3 kernel: input: vc4-hdmi-1 as /devices/platform/soc/fef05700.hdmi/rc/rc1/input5
  324. May 09 10:31:32 duet3 kernel: input: vc4-hdmi-1 HDMI Jack as /devices/platform/soc/fef05700.hdmi/sound/card1/input6
  325. May 09 10:31:32 duet3 kernel: vc4-drm gpu: bound fef05700.hdmi (ops vc4_hdmi_ops [vc4])
  326. May 09 10:31:32 duet3 kernel: vc4-drm gpu: bound fe004000.txp (ops vc4_txp_ops [vc4])
  327. May 09 10:31:32 duet3 kernel: vc4-drm gpu: bound fe206000.pixelvalve (ops vc4_crtc_ops [vc4])
  328. May 09 10:31:32 duet3 kernel: vc4-drm gpu: bound fe207000.pixelvalve (ops vc4_crtc_ops [vc4])
  329. May 09 10:31:32 duet3 kernel: vc4-drm gpu: bound fe20a000.pixelvalve (ops vc4_crtc_ops [vc4])
  330. May 09 10:31:32 duet3 kernel: vc4-drm gpu: bound fe216000.pixelvalve (ops vc4_crtc_ops [vc4])
  331. May 09 10:31:32 duet3 kernel: vc4-drm gpu: bound fec12000.pixelvalve (ops vc4_crtc_ops [vc4])
  332. May 09 10:31:32 duet3 kernel: [drm] Initialized vc4 0.0.0 20140616 for gpu on minor 1
  333. May 09 10:31:32 duet3 kernel: Console: switching to colour frame buffer device 240x67
  334. May 09 10:31:32 duet3 kernel: vc4-drm gpu: [drm] fb0: vc4drmfb frame buffer device
  335. May 09 10:31:32 duet3 kernel: EXT4-fs (sda2): mounted filesystem 1eaf03dc-b993-4452-ae86-5606e9a40291 ro with ordered data mode. Quota mode: none.
  336. May 09 10:31:32 duet3 systemd[1]: System time before build time, advancing clock.
  337. May 09 10:31:32 duet3 kernel: NET: Registered PF_INET6 protocol family
  338. May 09 10:31:32 duet3 kernel: Segment Routing with IPv6
  339. May 09 10:31:32 duet3 kernel: In-situ OAM (IOAM) with IPv6
  340. May 09 10:31:32 duet3 systemd[1]: systemd 252.17-1~deb12u1+rpi1 running in system mode (+PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT -GNUTLS +OPENSSL +ACL +B>
  341. May 09 10:31:32 duet3 systemd[1]: Detected architecture arm64.
  342. May 09 10:31:32 duet3 systemd[1]: Hostname set to <duet3>.
  343. May 09 10:31:32 duet3 systemd[1]: Queued start job for default target graphical.target.
  344. May 09 10:31:32 duet3 systemd[1]: Created slice system-getty.slice - Slice /system/getty.
  345. May 09 10:31:32 duet3 systemd[1]: Created slice system-modprobe.slice - Slice /system/modprobe.
  346. May 09 10:31:32 duet3 systemd[1]: Created slice system-systemd\x2dfsck.slice - Slice /system/systemd-fsck.
  347. May 09 10:31:32 duet3 systemd[1]: Created slice user.slice - User and Session Slice.
  348. May 09 10:31:32 duet3 systemd[1]: Started systemd-ask-password-wall.path - Forward Password Requests to Wall Directory Watch.
  349. May 09 10:31:32 duet3 systemd[1]: Set up automount proc-sys-fs-binfmt_misc.automount - Arbitrary Executable File Formats File System Automount Point.
  350. May 09 10:31:32 duet3 systemd[1]: Reached target integritysetup.target - Local Integrity Protected Volumes.
  351. May 09 10:31:32 duet3 systemd[1]: Reached target nss-user-lookup.target - User and Group Name Lookups.
  352. May 09 10:31:32 duet3 systemd[1]: Reached target slices.target - Slice Units.
  353. May 09 10:31:32 duet3 systemd[1]: Reached target swap.target - Swaps.
  354. May 09 10:31:32 duet3 systemd[1]: Reached target veritysetup.target - Local Verity Protected Volumes.
  355. May 09 10:31:32 duet3 systemd[1]: Listening on systemd-fsckd.socket - fsck to fsckd communication Socket.
  356. May 09 10:31:32 duet3 systemd[1]: Listening on systemd-initctl.socket - initctl Compatibility Named Pipe.
  357. May 09 10:31:32 duet3 systemd[1]: Listening on systemd-journald-audit.socket - Journal Audit Socket.
  358. May 09 10:31:32 duet3 systemd[1]: Listening on systemd-journald-dev-log.socket - Journal Socket (/dev/log).
  359. May 09 10:31:32 duet3 systemd[1]: Listening on systemd-journald.socket - Journal Socket.
  360. May 09 10:31:32 duet3 systemd[1]: Listening on systemd-udevd-control.socket - udev Control Socket.
  361. May 09 10:31:32 duet3 systemd[1]: Listening on systemd-udevd-kernel.socket - udev Kernel Socket.
  362. May 09 10:31:32 duet3 systemd[1]: dev-hugepages.mount - Huge Pages File System was skipped because of an unmet condition check (ConditionPathExists=/sys/kernel/mm/hugepages>
  363. May 09 10:31:32 duet3 systemd[1]: Mounting dev-mqueue.mount - POSIX Message Queue File System...
  364. May 09 10:31:32 duet3 systemd[1]: Mounting sys-kernel-debug.mount - Kernel Debug File System...
  365. May 09 10:31:32 duet3 systemd[1]: Mounting sys-kernel-tracing.mount - Kernel Trace File System...
  366. May 09 10:31:32 duet3 systemd[1]: auth-rpcgss-module.service - Kernel Module supporting RPCSEC_GSS was skipped because of an unmet condition check (ConditionPathExists=/etc>
  367. May 09 10:31:32 duet3 systemd[1]: Starting fake-hwclock.service - Restore / save the current clock...
  368. May 09 10:31:32 duet3 systemd[1]: Starting keyboard-setup.service - Set the console keyboard layout...
  369. May 09 10:31:32 duet3 systemd[1]: Starting kmod-static-nodes.service - Create List of Static Device Nodes...
  370. May 09 10:31:32 duet3 systemd[1]: Starting modprobe@configfs.service - Load Kernel Module configfs...
  371. May 09 10:31:32 duet3 systemd[1]: Starting modprobe@dm_mod.service - Load Kernel Module dm_mod...
  372. May 09 10:31:32 duet3 systemd[1]: Starting modprobe@drm.service - Load Kernel Module drm...
  373. May 09 10:31:32 duet3 systemd[1]: Starting modprobe@efi_pstore.service - Load Kernel Module efi_pstore...
  374. May 09 10:31:32 duet3 systemd[1]: Starting modprobe@fuse.service - Load Kernel Module fuse...
  375. May 09 10:31:32 duet3 systemd[1]: Starting modprobe@loop.service - Load Kernel Module loop...
  376. May 09 10:31:32 duet3 systemd[1]: systemd-fsck-root.service - File System Check on Root Device was skipped because of an unmet condition check (ConditionPathExists=!/run/in>
  377. May 09 10:31:32 duet3 systemd[1]: Starting systemd-journald.service - Journal Service...
  378. May 09 10:31:32 duet3 kernel: device-mapper: ioctl: 4.48.0-ioctl (2023-03-01) initialised: dm-devel@redhat.com
  379. May 09 10:31:32 duet3 systemd[1]: Starting systemd-modules-load.service - Load Kernel Modules...
  380. May 09 10:31:32 duet3 systemd[1]: Starting systemd-remount-fs.service - Remount Root and Kernel File Systems...
  381. May 09 10:31:32 duet3 systemd[1]: Starting systemd-udev-trigger.service - Coldplug All udev Devices...
  382. May 09 10:31:32 duet3 systemd[1]: Mounted dev-mqueue.mount - POSIX Message Queue File System.
  383. May 09 10:31:32 duet3 systemd[1]: Mounted sys-kernel-debug.mount - Kernel Debug File System.
  384. May 09 10:31:32 duet3 systemd[1]: Mounted sys-kernel-tracing.mount - Kernel Trace File System.
  385. May 09 10:31:32 duet3 kernel: fuse: init (API version 7.39)
  386. May 09 10:31:32 duet3 systemd[1]: Finished fake-hwclock.service - Restore / save the current clock.
  387. May 09 10:31:32 duet3 kernel: i2c_dev: i2c /dev entries driver
  388. May 09 10:31:32 duet3 systemd[1]: Finished kmod-static-nodes.service - Create List of Static Device Nodes.
  389. May 09 10:31:32 duet3 systemd[1]: modprobe@configfs.service: Deactivated successfully.
  390. May 09 10:31:32 duet3 systemd[1]: Finished modprobe@configfs.service - Load Kernel Module configfs.
  391. May 09 10:31:32 duet3 systemd[1]: modprobe@dm_mod.service: Deactivated successfully.
  392. May 09 10:31:32 duet3 systemd[1]: Finished modprobe@dm_mod.service - Load Kernel Module dm_mod.
  393. May 09 10:31:32 duet3 systemd[1]: modprobe@drm.service: Deactivated successfully.
  394. May 09 10:31:32 duet3 systemd[1]: Finished modprobe@drm.service - Load Kernel Module drm.
  395. May 09 10:31:32 duet3 systemd[1]: modprobe@efi_pstore.service: Deactivated successfully.
  396. May 09 10:31:32 duet3 systemd[1]: Finished modprobe@efi_pstore.service - Load Kernel Module efi_pstore.
  397. May 09 10:31:32 duet3 systemd[1]: modprobe@fuse.service: Deactivated successfully.
  398. May 09 10:31:32 duet3 systemd[1]: Finished modprobe@fuse.service - Load Kernel Module fuse.
  399. May 09 10:31:32 duet3 systemd[1]: modprobe@loop.service: Deactivated successfully.
  400. May 09 10:31:32 duet3 systemd[1]: Finished modprobe@loop.service - Load Kernel Module loop.
  401. May 09 10:31:32 duet3 systemd[1]: Finished systemd-modules-load.service - Load Kernel Modules.
  402. May 09 10:31:32 duet3 kernel: EXT4-fs (sda2): re-mounted 1eaf03dc-b993-4452-ae86-5606e9a40291 r/w. Quota mode: none.
  403. May 09 10:31:32 duet3 systemd[1]: Mounting sys-fs-fuse-connections.mount - FUSE Control File System...
  404. May 09 10:31:32 duet3 systemd[1]: Mounting sys-kernel-config.mount - Kernel Configuration File System...
  405. May 09 10:31:32 duet3 systemd[1]: systemd-repart.service - Repartition Root Disk was skipped because no trigger condition checks were met.
  406. May 09 10:31:32 duet3 systemd[1]: Starting systemd-sysctl.service - Apply Kernel Variables...
  407. May 09 10:31:32 duet3 systemd[1]: Finished systemd-remount-fs.service - Remount Root and Kernel File Systems.
  408. May 09 10:31:32 duet3 systemd[1]: Mounted sys-fs-fuse-connections.mount - FUSE Control File System.
  409. May 09 10:31:32 duet3 systemd[1]: Mounted sys-kernel-config.mount - Kernel Configuration File System.
  410. May 09 10:31:32 duet3 systemd[1]: systemd-firstboot.service - First Boot Wizard was skipped because of an unmet condition check (ConditionFirstBoot=yes).
  411. May 09 10:31:32 duet3 systemd[1]: systemd-pstore.service - Platform Persistent Storage Archival was skipped because of an unmet condition check (ConditionDirectoryNotEmpty=>
  412. May 09 10:31:32 duet3 systemd[1]: Starting systemd-random-seed.service - Load/Save Random Seed...
  413. May 09 10:31:32 duet3 systemd[1]: Starting systemd-sysusers.service - Create System Users...
  414. May 09 10:31:32 duet3 systemd[1]: Finished systemd-sysctl.service - Apply Kernel Variables.
  415. May 09 10:31:32 duet3 systemd[1]: Finished systemd-random-seed.service - Load/Save Random Seed.
  416. May 09 10:31:32 duet3 systemd[1]: first-boot-complete.target - First Boot Complete was skipped because of an unmet condition check (ConditionFirstBoot=yes).
  417. May 09 10:31:32 duet3 systemd[1]: Finished systemd-sysusers.service - Create System Users.
  418. May 09 10:31:32 duet3 systemd-journald[277]: Journal started
  419. ░░ Subject: The journal has been started
  420. ░░ Defined-By: systemd
  421. ░░ Support: https://www.debian.org/support
  422. ░░
  423. ░░ The system journal process has started up, opened the journal
  424. ░░ files for writing and is now ready to process requests.
  425. May 09 10:31:32 duet3 systemd-journald[277]: Runtime Journal (/run/log/journal/080cb843f9e8448b9b2d5df741baf4ab) is 2.3M, max 18.4M, 16.1M free.
  426. ░░ Subject: Disk space used by the journal
  427. ░░ Defined-By: systemd
  428. ░░ Support: https://www.debian.org/support
  429. ░░
  430. ░░ Runtime Journal (/run/log/journal/080cb843f9e8448b9b2d5df741baf4ab) is currently using 2.3M.
  431. ░░ Maximum allowed usage is set to 18.4M.
  432. ░░ Leaving at least 9.2M free (of currently available 181.7M of disk space).
  433. ░░ Enforced usage limit is thus 18.4M, of which 16.1M are still available.
  434. ░░
  435. ░░ The limits controlling how much disk space is used by the journal may
  436. ░░ be configured with SystemMaxUse=, SystemKeepFree=, SystemMaxFileSize=,
  437. ░░ RuntimeMaxUse=, RuntimeKeepFree=, RuntimeMaxFileSize= settings in
  438. ░░ /etc/systemd/journald.conf. See journald.conf(5) for details.
  439. May 09 10:31:32 duet3 systemd-modules-load[279]: Inserted module 'i2c_dev'
  440. May 09 10:31:32 duet3 systemd-sysctl[293]: Couldn't write '1' to 'kernel/unprivileged_userns_clone', ignoring: No such file or directory
  441. May 09 10:31:32 duet3 fake-hwclock[270]: Thu 9 May 09:31:32 UTC 2024
  442. May 09 10:31:32 duet3 systemd[1]: Starting systemd-tmpfiles-setup-dev.service - Create Static Device Nodes in /dev...
  443. May 09 10:31:32 duet3 systemd[1]: Started systemd-journald.service - Journal Service.
  444. May 09 10:31:32 duet3 systemd[1]: Finished keyboard-setup.service - Set the console keyboard layout.
  445. ░░ Subject: A start job for unit keyboard-setup.service has finished successfully
  446. ░░ Defined-By: systemd
  447. ░░ Support: https://www.debian.org/support
  448. ░░
  449. ░░ A start job for unit keyboard-setup.service has finished successfully.
  450. ░░
  451. ░░ The job identifier is 35.
  452. May 09 10:31:32 duet3 systemd[1]: Starting systemd-journal-flush.service - Flush Journal to Persistent Storage...
  453. ░░ Subject: A start job for unit systemd-journal-flush.service has begun execution
  454. ░░ Defined-By: systemd
  455. ░░ Support: https://www.debian.org/support
  456. ░░
  457. ░░ A start job for unit systemd-journal-flush.service has begun execution.
  458. ░░
  459. ░░ The job identifier is 65.
  460. May 09 10:31:32 duet3 systemd-journald[277]: Time spent on flushing to /var/log/journal/080cb843f9e8448b9b2d5df741baf4ab is 136.734ms for 426 entries.
  461. May 09 10:31:32 duet3 systemd-journald[277]: System Journal (/var/log/journal/080cb843f9e8448b9b2d5df741baf4ab) is 8.0M, max 3.6G, 3.6G free.
  462. ░░ Subject: Disk space used by the journal
  463. ░░ Defined-By: systemd
  464. ░░ Support: https://www.debian.org/support
  465. ░░
  466. ░░ System Journal (/var/log/journal/080cb843f9e8448b9b2d5df741baf4ab) is currently using 8.0M.
  467. ░░ Maximum allowed usage is set to 3.6G.
  468. ░░ Leaving at least 1.8G free (of currently available 106.2G of disk space).
  469. ░░ Enforced usage limit is thus 3.6G, of which 3.6G are still available.
  470. ░░
  471. ░░ The limits controlling how much disk space is used by the journal may
  472. ░░ be configured with SystemMaxUse=, SystemKeepFree=, SystemMaxFileSize=,
  473. ░░ RuntimeMaxUse=, RuntimeKeepFree=, RuntimeMaxFileSize= settings in
  474. ░░ /etc/systemd/journald.conf. See journald.conf(5) for details.
  475. May 09 10:31:32 duet3 systemd-journald[277]: Received client request to flush runtime journal.
  476. May 09 10:31:32 duet3 systemd[1]: Finished systemd-tmpfiles-setup-dev.service - Create Static Device Nodes in /dev.
  477. ░░ Subject: A start job for unit systemd-tmpfiles-setup-dev.service has finished successfully
  478. ░░ Defined-By: systemd
  479. ░░ Support: https://www.debian.org/support
  480. ░░
  481. ░░ A start job for unit systemd-tmpfiles-setup-dev.service has finished successfully.
  482. ░░
  483. ░░ The job identifier is 71.
  484. May 09 10:31:32 duet3 systemd[1]: Reached target local-fs-pre.target - Preparation for Local File Systems.
  485. ░░ Subject: A start job for unit local-fs-pre.target has finished successfully
  486. ░░ Defined-By: systemd
  487. ░░ Support: https://www.debian.org/support
  488. ░░
  489. ░░ A start job for unit local-fs-pre.target has finished successfully.
  490. ░░
  491. ░░ The job identifier is 17.
  492. May 09 10:31:32 duet3 systemd[1]: Starting systemd-udevd.service - Rule-based Manager for Device Events and Files...
  493. ░░ Subject: A start job for unit systemd-udevd.service has begun execution
  494. ░░ Defined-By: systemd
  495. ░░ Support: https://www.debian.org/support
  496. ░░
  497. ░░ A start job for unit systemd-udevd.service has begun execution.
  498. ░░
  499. ░░ The job identifier is 43.
  500. May 09 10:31:32 duet3 systemd-udevd[305]: Using default interface naming scheme 'v252'.
  501. May 09 10:31:32 duet3 systemd[1]: Finished systemd-journal-flush.service - Flush Journal to Persistent Storage.
  502. ░░ Subject: A start job for unit systemd-journal-flush.service has finished successfully
  503. ░░ Defined-By: systemd
  504. ░░ Support: https://www.debian.org/support
  505. ░░
  506. ░░ A start job for unit systemd-journal-flush.service has finished successfully.
  507. ░░
  508. ░░ The job identifier is 65.
  509. May 09 10:31:32 duet3 systemd[1]: Finished systemd-udev-trigger.service - Coldplug All udev Devices.
  510. ░░ Subject: A start job for unit systemd-udev-trigger.service has finished successfully
  511. ░░ Defined-By: systemd
  512. ░░ Support: https://www.debian.org/support
  513. ░░
  514. ░░ A start job for unit systemd-udev-trigger.service has finished successfully.
  515. ░░
  516. ░░ The job identifier is 42.
  517. May 09 10:31:32 duet3 systemd[1]: Starting ifupdown-pre.service - Helper to synchronize boot up for ifupdown...
  518. ░░ Subject: A start job for unit ifupdown-pre.service has begun execution
  519. ░░ Defined-By: systemd
  520. ░░ Support: https://www.debian.org/support
  521. ░░
  522. ░░ A start job for unit ifupdown-pre.service has begun execution.
  523. ░░
  524. ░░ The job identifier is 108.
  525. May 09 10:31:32 duet3 systemd[1]: Finished ifupdown-pre.service - Helper to synchronize boot up for ifupdown.
  526. ░░ Subject: A start job for unit ifupdown-pre.service has finished successfully
  527. ░░ Defined-By: systemd
  528. ░░ Support: https://www.debian.org/support
  529. ░░
  530. ░░ A start job for unit ifupdown-pre.service has finished successfully.
  531. ░░
  532. ░░ The job identifier is 108.
  533. May 09 10:31:32 duet3 systemd[1]: Started systemd-udevd.service - Rule-based Manager for Device Events and Files.
  534. ░░ Subject: A start job for unit systemd-udevd.service has finished successfully
  535. ░░ Defined-By: systemd
  536. ░░ Support: https://www.debian.org/support
  537. ░░
  538. ░░ A start job for unit systemd-udevd.service has finished successfully.
  539. ░░
  540. ░░ The job identifier is 43.
  541. May 09 10:31:32 duet3 systemd[1]: Starting plymouth-start.service - Show Plymouth Boot Screen...
  542. ░░ Subject: A start job for unit plymouth-start.service has begun execution
  543. ░░ Defined-By: systemd
  544. ░░ Support: https://www.debian.org/support
  545. ░░
  546. ░░ A start job for unit plymouth-start.service has begun execution.
  547. ░░
  548. ░░ The job identifier is 32.
  549. May 09 10:31:33 duet3 systemd[1]: Started plymouth-start.service - Show Plymouth Boot Screen.
  550. ░░ Subject: A start job for unit plymouth-start.service has finished successfully
  551. ░░ Defined-By: systemd
  552. ░░ Support: https://www.debian.org/support
  553. ░░
  554. ░░ A start job for unit plymouth-start.service has finished successfully.
  555. ░░
  556. ░░ The job identifier is 32.
  557. May 09 10:31:33 duet3 systemd[1]: systemd-ask-password-console.path - Dispatch Password Requests to Console Directory Watch was skipped because of an unmet condition check >
  558. ░░ Subject: A start job for unit systemd-ask-password-console.path has finished successfully
  559. ░░ Defined-By: systemd
  560. ░░ Support: https://www.debian.org/support
  561. ░░
  562. ░░ A start job for unit systemd-ask-password-console.path has finished successfully.
  563. ░░
  564. ░░ The job identifier is 47.
  565. May 09 10:31:33 duet3 systemd[1]: Started systemd-ask-password-plymouth.path - Forward Password Requests to Plymouth Directory Watch.
  566. ░░ Subject: A start job for unit systemd-ask-password-plymouth.path has finished successfully
  567. ░░ Defined-By: systemd
  568. ░░ Support: https://www.debian.org/support
  569. ░░
  570. ░░ A start job for unit systemd-ask-password-plymouth.path has finished successfully.
  571. ░░
  572. ░░ The job identifier is 33.
  573. May 09 10:31:33 duet3 systemd[1]: Reached target cryptsetup.target - Local Encrypted Volumes.
  574. ░░ Subject: A start job for unit cryptsetup.target has finished successfully
  575. ░░ Defined-By: systemd
  576. ░░ Support: https://www.debian.org/support
  577. ░░
  578. ░░ A start job for unit cryptsetup.target has finished successfully.
  579. ░░
  580. ░░ The job identifier is 59.
  581. May 09 10:31:33 duet3 systemd[1]: Reached target paths.target - Path Units.
  582. ░░ Subject: A start job for unit paths.target has finished successfully
  583. ░░ Defined-By: systemd
  584. ░░ Support: https://www.debian.org/support
  585. ░░
  586. ░░ A start job for unit paths.target has finished successfully.
  587. ░░
  588. ░░ The job identifier is 90.
  589. May 09 10:31:33 duet3 mtp-probe[341]: checking bus 2, device 2: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-1"
  590. May 09 10:31:33 duet3 mtp-probe[342]: checking bus 1, device 3: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.2"
  591. May 09 10:31:33 duet3 mtp-probe[341]: bus: 2, device: 2 was not an MTP device
  592. May 09 10:31:33 duet3 mtp-probe[342]: bus: 1, device: 3 was not an MTP device
  593. May 09 10:31:33 duet3 (udev-worker)[313]: event3: Process '/usr/sbin/th-cmd --socket /var/run/thd.socket --passfd --udev' failed with exit code 1.
  594. May 09 10:31:33 duet3 (udev-worker)[320]: event5: Process '/usr/sbin/th-cmd --socket /var/run/thd.socket --passfd --udev' failed with exit code 1.
  595. May 09 10:31:33 duet3 (udev-worker)[318]: event1: Process '/usr/sbin/th-cmd --socket /var/run/thd.socket --passfd --udev' failed with exit code 1.
  596. May 09 10:31:33 duet3 kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0
  597. May 09 10:31:33 duet3 (udev-worker)[319]: event6: Process '/usr/sbin/th-cmd --socket /var/run/thd.socket --passfd --udev' failed with exit code 1.
  598. May 09 10:31:33 duet3 kernel: mc: Linux media interface: v0.10
  599. May 09 10:31:34 duet3 (udev-worker)[313]: event4: Process '/usr/sbin/th-cmd --socket /var/run/thd.socket --passfd --udev' failed with exit code 1.
  600. May 09 10:31:34 duet3 (udev-worker)[322]: event0: Process '/usr/sbin/th-cmd --socket /var/run/thd.socket --passfd --udev' failed with exit code 1.
  601. May 09 10:31:34 duet3 kernel: vc_sm_cma: module is from the staging directory, the quality is unknown, you have been warned.
  602. May 09 10:31:34 duet3 kernel: snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned.
  603. May 09 10:31:34 duet3 kernel: bcm2835_vc_sm_cma_probe: Videocore shared memory driver
  604. May 09 10:31:34 duet3 kernel: [vc_sm_connected_init]: start
  605. May 09 10:31:34 duet3 kernel: [vc_sm_connected_init]: installed successfully
  606. May 09 10:31:34 duet3 systemd[1]: Created slice system-usb\x2dmount.slice - Slice /system/usb-mount.
  607. ░░ Subject: A start job for unit system-usb\x2dmount.slice has finished successfully
  608. ░░ Defined-By: systemd
  609. ░░ Support: https://www.debian.org/support
  610. ░░
  611. ░░ A start job for unit system-usb\x2dmount.slice has finished successfully.
  612. ░░
  613. ░░ The job identifier is 146.
  614. May 09 10:31:34 duet3 systemd[1]: systemd-ask-password-console.path - Dispatch Password Requests to Console Directory Watch was skipped because of an unmet condition check >
  615. ░░ Subject: A start job for unit systemd-ask-password-console.path has finished successfully
  616. ░░ Defined-By: systemd
  617. ░░ Support: https://www.debian.org/support
  618. ░░
  619. ░░ A start job for unit systemd-ask-password-console.path has finished successfully.
  620. ░░
  621. ░░ The job identifier is 190.
  622. May 09 10:31:34 duet3 systemd[1]: dev-hugepages.mount - Huge Pages File System was skipped because of an unmet condition check (ConditionPathExists=/sys/kernel/mm/hugepages>
  623. ░░ Subject: A start job for unit dev-hugepages.mount has finished successfully
  624. ░░ Defined-By: systemd
  625. ░░ Support: https://www.debian.org/support
  626. ░░
  627. ░░ A start job for unit dev-hugepages.mount has finished successfully.
  628. ░░
  629. ░░ The job identifier is 173.
  630. May 09 10:31:34 duet3 kernel: rpi-gpiomem fe200000.gpiomem: window base 0xfe200000 size 0x00001000
  631. May 09 10:31:34 duet3 kernel: rpi-gpiomem fe200000.gpiomem: initialised 1 regions as /dev/gpiomem
  632. May 09 10:31:34 duet3 (udev-worker)[318]: event2: Process '/usr/sbin/th-cmd --socket /var/run/thd.socket --passfd --udev' failed with exit code 1.
  633. May 09 10:31:34 duet3 kernel: bcm2835_audio bcm2835_audio: card created with 8 channels
  634. May 09 10:31:34 duet3 systemd[1]: Starting modprobe@dm_mod.service - Load Kernel Module dm_mod...
  635. ░░ Subject: A start job for unit modprobe@dm_mod.service has begun execution
  636. ░░ Defined-By: systemd
  637. ░░ Support: https://www.debian.org/support
  638. ░░
  639. ░░ A start job for unit modprobe@dm_mod.service has begun execution.
  640. ░░
  641. ░░ The job identifier is 201.
  642. May 09 10:31:34 duet3 systemd[1]: Starting modprobe@efi_pstore.service - Load Kernel Module efi_pstore...
  643. ░░ Subject: A start job for unit modprobe@efi_pstore.service has begun execution
  644. ░░ Defined-By: systemd
  645. ░░ Support: https://www.debian.org/support
  646. ░░
  647. ░░ A start job for unit modprobe@efi_pstore.service has begun execution.
  648. ░░
  649. ░░ The job identifier is 168.
  650. May 09 10:31:34 duet3 systemd[1]: Starting modprobe@loop.service - Load Kernel Module loop...
  651. ░░ Subject: A start job for unit modprobe@loop.service has begun execution
  652. ░░ Defined-By: systemd
  653. ░░ Support: https://www.debian.org/support
  654. ░░
  655. ░░ A start job for unit modprobe@loop.service has begun execution.
  656. ░░
  657. ░░ The job identifier is 200.
  658. May 09 10:31:34 duet3 systemd[1]: systemd-firstboot.service - First Boot Wizard was skipped because of an unmet condition check (ConditionFirstBoot=yes).
  659. ░░ Subject: A start job for unit systemd-firstboot.service has finished successfully
  660. ░░ Defined-By: systemd
  661. ░░ Support: https://www.debian.org/support
  662. ░░
  663. ░░ A start job for unit systemd-firstboot.service has finished successfully.
  664. ░░
  665. ░░ The job identifier is 193.
  666. May 09 10:31:34 duet3 systemd[1]: first-boot-complete.target - First Boot Complete was skipped because of an unmet condition check (ConditionFirstBoot=yes).
  667. ░░ Subject: A start job for unit first-boot-complete.target has finished successfully
  668. ░░ Defined-By: systemd
  669. ░░ Support: https://www.debian.org/support
  670. ░░
  671. ░░ A start job for unit first-boot-complete.target has finished successfully.
  672. ░░
  673. ░░ The job identifier is 194.
  674. May 09 10:31:34 duet3 systemd[1]: systemd-fsck-root.service - File System Check on Root Device was skipped because of an unmet condition check (ConditionPathExists=!/run/in>
  675. ░░ Subject: A start job for unit systemd-fsck-root.service has finished successfully
  676. ░░ Defined-By: systemd
  677. ░░ Support: https://www.debian.org/support
  678. ░░
  679. ░░ A start job for unit systemd-fsck-root.service has finished successfully.
  680. ░░
  681. ░░ The job identifier is 161.
  682. May 09 10:31:34 duet3 systemd[1]: modprobe@dm_mod.service: Deactivated successfully.
  683. ░░ Subject: Unit succeeded
  684. ░░ Defined-By: systemd
  685. ░░ Support: https://www.debian.org/support
  686. ░░
  687. ░░ The unit modprobe@dm_mod.service has successfully entered the 'dead' state.
  688. May 09 10:31:34 duet3 systemd[1]: Finished modprobe@dm_mod.service - Load Kernel Module dm_mod.
  689. ░░ Subject: A start job for unit modprobe@dm_mod.service has finished successfully
  690. ░░ Defined-By: systemd
  691. ░░ Support: https://www.debian.org/support
  692. ░░
  693. ░░ A start job for unit modprobe@dm_mod.service has finished successfully.
  694. ░░
  695. ░░ The job identifier is 201.
  696. May 09 10:31:34 duet3 kernel: videodev: Linux video capture interface: v2.00
  697. May 09 10:31:34 duet3 systemd[1]: modprobe@efi_pstore.service: Deactivated successfully.
  698. ░░ Subject: Unit succeeded
  699. ░░ Defined-By: systemd
  700. ░░ Support: https://www.debian.org/support
  701. ░░
  702. ░░ The unit modprobe@efi_pstore.service has successfully entered the 'dead' state.
  703. May 09 10:31:34 duet3 systemd[1]: Finished modprobe@efi_pstore.service - Load Kernel Module efi_pstore.
  704. ░░ Subject: A start job for unit modprobe@efi_pstore.service has finished successfully
  705. ░░ Defined-By: systemd
  706. ░░ Support: https://www.debian.org/support
  707. ░░
  708. ░░ A start job for unit modprobe@efi_pstore.service has finished successfully.
  709. ░░
  710. ░░ The job identifier is 168.
  711. May 09 10:31:34 duet3 systemd[1]: modprobe@loop.service: Deactivated successfully.
  712. ░░ Subject: Unit succeeded
  713. ░░ Defined-By: systemd
  714. ░░ Support: https://www.debian.org/support
  715. ░░
  716. ░░ The unit modprobe@loop.service has successfully entered the 'dead' state.
  717. May 09 10:31:34 duet3 systemd[1]: Finished modprobe@loop.service - Load Kernel Module loop.
  718. ░░ Subject: A start job for unit modprobe@loop.service has finished successfully
  719. ░░ Defined-By: systemd
  720. ░░ Support: https://www.debian.org/support
  721. ░░
  722. ░░ A start job for unit modprobe@loop.service has finished successfully.
  723. ░░
  724. ░░ The job identifier is 200.
  725. May 09 10:31:34 duet3 systemd[1]: systemd-pstore.service - Platform Persistent Storage Archival was skipped because of an unmet condition check (ConditionDirectoryNotEmpty=>
  726. ░░ Subject: A start job for unit systemd-pstore.service has finished successfully
  727. ░░ Defined-By: systemd
  728. ░░ Support: https://www.debian.org/support
  729. ░░
  730. ░░ A start job for unit systemd-pstore.service has finished successfully.
  731. ░░
  732. ░░ The job identifier is 167.
  733. May 09 10:31:34 duet3 systemd[1]: systemd-repart.service - Repartition Root Disk was skipped because no trigger condition checks were met.
  734. ░░ Subject: A start job for unit systemd-repart.service has finished successfully
  735. ░░ Defined-By: systemd
  736. ░░ Support: https://www.debian.org/support
  737. ░░
  738. ░░ A start job for unit systemd-repart.service has finished successfully.
  739. ░░
  740. ░░ The job identifier is 199.
  741. May 09 10:31:34 duet3 systemd[1]: systemd-ask-password-console.path - Dispatch Password Requests to Console Directory Watch was skipped because of an unmet condition check >
  742. ░░ Subject: A start job for unit systemd-ask-password-console.path has finished successfully
  743. ░░ Defined-By: systemd
  744. ░░ Support: https://www.debian.org/support
  745. ░░
  746. ░░ A start job for unit systemd-ask-password-console.path has finished successfully.
  747. ░░
  748. ░░ The job identifier is 263.
  749. May 09 10:31:34 duet3 systemd[1]: dev-hugepages.mount - Huge Pages File System was skipped because of an unmet condition check (ConditionPathExists=/sys/kernel/mm/hugepages>
  750. ░░ Subject: A start job for unit dev-hugepages.mount has finished successfully
  751. ░░ Defined-By: systemd
  752. ░░ Support: https://www.debian.org/support
  753. ░░
  754. ░░ A start job for unit dev-hugepages.mount has finished successfully.
  755. ░░
  756. ░░ The job identifier is 246.
  757. May 09 10:31:34 duet3 kernel: rpivid_hevc: module is from the staging directory, the quality is unknown, you have been warned.
  758. May 09 10:31:34 duet3 systemd[1]: Starting modprobe@dm_mod.service - Load Kernel Module dm_mod...
  759. ░░ Subject: A start job for unit modprobe@dm_mod.service has begun execution
  760. ░░ Defined-By: systemd
  761. ░░ Support: https://www.debian.org/support
  762. ░░
  763. ░░ A start job for unit modprobe@dm_mod.service has begun execution.
  764. ░░
  765. ░░ The job identifier is 274.
  766. May 09 10:31:34 duet3 kernel: rpivid feb10000.codec: Device registered as /dev/video19
  767. May 09 10:31:34 duet3 systemd[1]: Starting modprobe@efi_pstore.service - Load Kernel Module efi_pstore...
  768. ░░ Subject: A start job for unit modprobe@efi_pstore.service has begun execution
  769. ░░ Defined-By: systemd
  770. ░░ Support: https://www.debian.org/support
  771. ░░
  772. ░░ A start job for unit modprobe@efi_pstore.service has begun execution.
  773. ░░
  774. ░░ The job identifier is 241.
  775. May 09 10:31:34 duet3 systemd[1]: Starting modprobe@loop.service - Load Kernel Module loop...
  776. ░░ Subject: A start job for unit modprobe@loop.service has begun execution
  777. ░░ Defined-By: systemd
  778. ░░ Support: https://www.debian.org/support
  779. ░░
  780. ░░ A start job for unit modprobe@loop.service has begun execution.
  781. ░░
  782. ░░ The job identifier is 273.
  783. May 09 10:31:34 duet3 systemd[1]: systemd-firstboot.service - First Boot Wizard was skipped because of an unmet condition check (ConditionFirstBoot=yes).
  784. May 09 10:31:34 duet3 systemd[1]: systemd-firstboot.service - First Boot Wizard was skipped because of an unmet condition check (ConditionFirstBoot=yes).
  785. ░░ Subject: A start job for unit systemd-firstboot.service has finished successfully
  786. ░░ Defined-By: systemd
  787. ░░ Support: https://www.debian.org/support
  788. ░░
  789. ░░ A start job for unit systemd-firstboot.service has finished successfully.
  790. ░░
  791. ░░ The job identifier is 266.
  792. May 09 10:31:34 duet3 systemd[1]: first-boot-complete.target - First Boot Complete was skipped because of an unmet condition check (ConditionFirstBoot=yes).
  793. ░░ Subject: A start job for unit first-boot-complete.target has finished successfully
  794. ░░ Defined-By: systemd
  795. ░░ Support: https://www.debian.org/support
  796. ░░
  797. ░░ A start job for unit first-boot-complete.target has finished successfully.
  798. ░░
  799. ░░ The job identifier is 267.
  800. May 09 10:31:34 duet3 systemd[1]: systemd-fsck-root.service - File System Check on Root Device was skipped because of an unmet condition check (ConditionPathExists=!/run/in>
  801. ░░ Subject: A start job for unit systemd-fsck-root.service has finished successfully
  802. ░░ Defined-By: systemd
  803. ░░ Support: https://www.debian.org/support
  804. ░░
  805. ░░ A start job for unit systemd-fsck-root.service has finished successfully.
  806. ░░
  807. ░░ The job identifier is 234.
  808. May 09 10:31:34 duet3 kernel: bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
  809. May 09 10:31:34 duet3 systemd[1]: modprobe@dm_mod.service: Deactivated successfully.
  810. ░░ Subject: Unit succeeded
  811. ░░ Defined-By: systemd
  812. ░░ Support: https://www.debian.org/support
  813. ░░
  814. ░░ The unit modprobe@dm_mod.service has successfully entered the 'dead' state.
  815. May 09 10:31:34 duet3 systemd[1]: Finished modprobe@dm_mod.service - Load Kernel Module dm_mod.
  816. ░░ Subject: A start job for unit modprobe@dm_mod.service has finished successfully
  817. ░░ Defined-By: systemd
  818. ░░ Support: https://www.debian.org/support
  819. ░░
  820. ░░ A start job for unit modprobe@dm_mod.service has finished successfully.
  821. ░░
  822. ░░ The job identifier is 274.
  823. May 09 10:31:34 duet3 systemd[1]: modprobe@efi_pstore.service: Deactivated successfully.
  824. ░░ Subject: Unit succeeded
  825. ░░ Defined-By: systemd
  826. ░░ Support: https://www.debian.org/support
  827. ░░
  828. ░░ The unit modprobe@efi_pstore.service has successfully entered the 'dead' state.
  829. May 09 10:31:34 duet3 systemd[1]: Finished modprobe@efi_pstore.service - Load Kernel Module efi_pstore.
  830. ░░ Subject: A start job for unit modprobe@efi_pstore.service has finished successfully
  831. ░░ Defined-By: systemd
  832. ░░ Support: https://www.debian.org/support
  833. ░░
  834. ░░ A start job for unit modprobe@efi_pstore.service has finished successfully.
  835. ░░
  836. ░░ The job identifier is 241.
  837. May 09 10:31:34 duet3 systemd[1]: modprobe@loop.service: Deactivated successfully.
  838. ░░ Subject: Unit succeeded
  839. ░░ Defined-By: systemd
  840. ░░ Support: https://www.debian.org/support
  841. ░░
  842. ░░ The unit modprobe@loop.service has successfully entered the 'dead' state.
  843. May 09 10:31:34 duet3 systemd[1]: Finished modprobe@loop.service - Load Kernel Module loop.
  844. ░░ Subject: A start job for unit modprobe@loop.service has finished successfully
  845. ░░ Defined-By: systemd
  846. ░░ Support: https://www.debian.org/support
  847. ░░
  848. ░░ A start job for unit modprobe@loop.service has finished successfully.
  849. ░░
  850. ░░ The job identifier is 273.
  851. May 09 10:31:34 duet3 systemd[1]: systemd-pstore.service - Platform Persistent Storage Archival was skipped because of an unmet condition check (ConditionDirectoryNotEmpty=>
  852. ░░ Subject: A start job for unit systemd-pstore.service has finished successfully
  853. ░░ Defined-By: systemd
  854. ░░ Support: https://www.debian.org/support
  855. ░░
  856. ░░ A start job for unit systemd-pstore.service has finished successfully.
  857. ░░
  858. ░░ The job identifier is 240.
  859. May 09 10:31:34 duet3 systemd[1]: systemd-repart.service - Repartition Root Disk was skipped because no trigger condition checks were met.
  860. ░░ Subject: A start job for unit systemd-repart.service has finished successfully
  861. ░░ Defined-By: systemd
  862. ░░ Support: https://www.debian.org/support
  863. ░░
  864. ░░ A start job for unit systemd-repart.service has finished successfully.
  865. ░░
  866. ░░ The job identifier is 272.
  867. May 09 10:31:34 duet3 kernel: bcm2835_codec: module is from the staging directory, the quality is unknown, you have been warned.
  868. May 09 10:31:34 duet3 kernel: bcm2835_v4l2: module is from the staging directory, the quality is unknown, you have been warned.
  869. May 09 10:31:34 duet3 kernel: bcm2835-codec bcm2835-codec: Device registered as /dev/video10
  870. May 09 10:31:34 duet3 kernel: bcm2835-codec bcm2835-codec: Loaded V4L2 decode
  871. May 09 10:31:34 duet3 kernel: bcm2835-codec bcm2835-codec: Device registered as /dev/video11
  872. May 09 10:31:34 duet3 kernel: bcm2835-codec bcm2835-codec: Loaded V4L2 encode
  873. May 09 10:31:34 duet3 kernel: bcm2835-codec bcm2835-codec: Device registered as /dev/video12
  874. May 09 10:31:34 duet3 kernel: bcm2835-codec bcm2835-codec: Loaded V4L2 isp
  875. May 09 10:31:34 duet3 kernel: bcm2835_isp: module is from the staging directory, the quality is unknown, you have been warned.
  876. May 09 10:31:34 duet3 kernel: bcm2835-codec bcm2835-codec: Device registered as /dev/video18
  877. May 09 10:31:34 duet3 kernel: bcm2835-codec bcm2835-codec: Loaded V4L2 image_fx
  878. May 09 10:31:34 duet3 kernel: bcm2835-codec bcm2835-codec: Device registered as /dev/video31
  879. May 09 10:31:34 duet3 kernel: bcm2835-codec bcm2835-codec: Loaded V4L2 encode_image
  880. May 09 10:31:34 duet3 kernel: bcm2835-isp bcm2835-isp: Device node output[0] registered as /dev/video13
  881. May 09 10:31:34 duet3 kernel: bcm2835-isp bcm2835-isp: Device node capture[0] registered as /dev/video14
  882. May 09 10:31:34 duet3 kernel: bcm2835-isp bcm2835-isp: Device node capture[1] registered as /dev/video15
  883. May 09 10:31:34 duet3 kernel: bcm2835-isp bcm2835-isp: Device node stats[2] registered as /dev/video16
  884. May 09 10:31:34 duet3 kernel: bcm2835-isp bcm2835-isp: Register output node 0 with media controller
  885. May 09 10:31:34 duet3 kernel: bcm2835-isp bcm2835-isp: Register capture node 1 with media controller
  886. May 09 10:31:34 duet3 kernel: bcm2835-isp bcm2835-isp: Register capture node 2 with media controller
  887. May 09 10:31:34 duet3 kernel: bcm2835-isp bcm2835-isp: Register capture node 3 with media controller
  888. May 09 10:31:34 duet3 kernel: bcm2835-isp bcm2835-isp: Device node output[0] registered as /dev/video20
  889. May 09 10:31:34 duet3 kernel: bcm2835-isp bcm2835-isp: Device node capture[0] registered as /dev/video21
  890. May 09 10:31:34 duet3 kernel: bcm2835-isp bcm2835-isp: Device node capture[1] registered as /dev/video22
  891. May 09 10:31:34 duet3 kernel: bcm2835-isp bcm2835-isp: Device node stats[2] registered as /dev/video23
  892. May 09 10:31:34 duet3 kernel: bcm2835-isp bcm2835-isp: Register output node 0 with media controller
  893. May 09 10:31:34 duet3 kernel: bcm2835-isp bcm2835-isp: Register capture node 1 with media controller
  894. May 09 10:31:34 duet3 kernel: bcm2835-isp bcm2835-isp: Register capture node 2 with media controller
  895. May 09 10:31:34 duet3 kernel: bcm2835-isp bcm2835-isp: Register capture node 3 with media controller
  896. May 09 10:31:34 duet3 kernel: bcm2835-isp bcm2835-isp: Loaded V4L2 bcm2835-isp
  897. May 09 10:31:34 duet3 kernel: imx708 10-001a: camera module ID 0x0301
  898. May 09 10:31:34 duet3 kernel: alsactl[441]: memfd_create() called without MFD_EXEC or MFD_NOEXEC_SEAL set
  899. May 09 10:31:34 duet3 (udev-worker)[320]: controlC1: Process '/usr/sbin/alsactl -E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 1' failed with exit code 99.
  900. May 09 10:31:34 duet3 kernel: Bluetooth: Core ver 2.22
  901. May 09 10:31:34 duet3 kernel: NET: Registered PF_BLUETOOTH protocol family
  902. May 09 10:31:34 duet3 kernel: Bluetooth: HCI device and connection manager initialized
  903. May 09 10:31:34 duet3 kernel: Bluetooth: HCI socket layer initialized
  904. May 09 10:31:34 duet3 kernel: Bluetooth: L2CAP socket layer initialized
  905. May 09 10:31:34 duet3 kernel: Bluetooth: SCO socket layer initialized
  906. May 09 10:31:34 duet3 kernel: cfg80211: Loading compiled-in X.509 certificates for regulatory database
  907. May 09 10:31:34 duet3 (udev-worker)[317]: controlC0: Process '/usr/sbin/alsactl -E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 0' failed with exit code 99.
  908. May 09 10:31:34 duet3 kernel: Loaded X.509 cert 'benh@debian.org: 577e021cb980e0e820821ba7b54b4961b8b4fadf'
  909. May 09 10:31:34 duet3 kernel: Loaded X.509 cert 'romain.perier@gmail.com: 3abbc6ec146e09d1b6016ab9d6cf71dd233f0328'
  910. May 09 10:31:34 duet3 kernel: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
  911. May 09 10:31:34 duet3 kernel: Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
  912. May 09 10:31:34 duet3 systemd[1]: systemd-ask-password-console.path - Dispatch Password Requests to Console Directory Watch was skipped because of an unmet condition check >
  913. ░░ Subject: A start job for unit systemd-ask-password-console.path has finished successfully
  914. ░░ Defined-By: systemd
  915. ░░ Support: https://www.debian.org/support
  916. ░░
  917. ░░ A start job for unit systemd-ask-password-console.path has finished successfully.
  918. ░░
  919. ░░ The job identifier is 336.
  920. May 09 10:31:34 duet3 systemd[1]: dev-hugepages.mount - Huge Pages File System was skipped because of an unmet condition check (ConditionPathExists=/sys/kernel/mm/hugepages>
  921. ░░ Subject: A start job for unit dev-hugepages.mount has finished successfully
  922. ░░ Defined-By: systemd
  923. ░░ Support: https://www.debian.org/support
  924. ░░
  925. ░░ A start job for unit dev-hugepages.mount has finished successfully.
  926. ░░
  927. ░░ The job identifier is 319.
  928. May 09 10:31:34 duet3 kernel: Bluetooth: HCI UART driver ver 2.3
  929. May 09 10:31:34 duet3 kernel: Bluetooth: HCI UART protocol H4 registered
  930. May 09 10:31:34 duet3 kernel: Bluetooth: HCI UART protocol Three-wire (H5) registered
  931. May 09 10:31:34 duet3 kernel: hci_uart_bcm serial0-0: supply vbat not found, using dummy regulator
  932. May 09 10:31:34 duet3 kernel: hci_uart_bcm serial0-0: supply vddio not found, using dummy regulator
  933. May 09 10:31:34 duet3 kernel: Bluetooth: HCI UART protocol Broadcom registered
  934. May 09 10:31:34 duet3 systemd[1]: Starting modprobe@dm_mod.service - Load Kernel Module dm_mod...
  935. ░░ Subject: A start job for unit modprobe@dm_mod.service has begun execution
  936. ░░ Defined-By: systemd
  937. ░░ Support: https://www.debian.org/support
  938. ░░
  939. ░░ A start job for unit modprobe@dm_mod.service has begun execution.
  940. ░░
  941. ░░ The job identifier is 347.
  942. May 09 10:31:34 duet3 systemd[1]: Starting modprobe@efi_pstore.service - Load Kernel Module efi_pstore...
  943. ░░ Subject: A start job for unit modprobe@efi_pstore.service has begun execution
  944. ░░ Defined-By: systemd
  945. ░░ Support: https://www.debian.org/support
  946. ░░
  947. ░░ A start job for unit modprobe@efi_pstore.service has begun execution.
  948. ░░
  949. ░░ The job identifier is 314.
  950. May 09 10:31:34 duet3 systemd[1]: Starting modprobe@loop.service - Load Kernel Module loop...
  951. ░░ Subject: A start job for unit modprobe@loop.service has begun execution
  952. ░░ Defined-By: systemd
  953. ░░ Support: https://www.debian.org/support
  954. ░░
  955. ░░ A start job for unit modprobe@loop.service has begun execution.
  956. ░░
  957. ░░ The job identifier is 346.
  958. May 09 10:31:34 duet3 systemd[1]: systemd-firstboot.service - First Boot Wizard was skipped because of an unmet condition check (ConditionFirstBoot=yes).
  959. ░░ Subject: A start job for unit systemd-firstboot.service has finished successfully
  960. ░░ Defined-By: systemd
  961. ░░ Support: https://www.debian.org/support
  962. ░░
  963. ░░ A start job for unit systemd-firstboot.service has finished successfully.
  964. ░░
  965. ░░ The job identifier is 339.
  966. May 09 10:31:34 duet3 systemd[1]: first-boot-complete.target - First Boot Complete was skipped because of an unmet condition check (ConditionFirstBoot=yes).
  967. ░░ Subject: A start job for unit first-boot-complete.target has finished successfully
  968. ░░ Defined-By: systemd
  969. ░░ Support: https://www.debian.org/support
  970. ░░
  971. ░░ A start job for unit first-boot-complete.target has finished successfully.
  972. ░░
  973. ░░ The job identifier is 340.
  974. May 09 10:31:34 duet3 systemd[1]: systemd-fsck-root.service - File System Check on Root Device was skipped because of an unmet condition check (ConditionPathExists=!/run/in>
  975. ░░ Subject: A start job for unit systemd-fsck-root.service has finished successfully
  976. ░░ Defined-By: systemd
  977. ░░ Support: https://www.debian.org/support
  978. ░░
  979. ░░ A start job for unit systemd-fsck-root.service has finished successfully.
  980. ░░
  981. ░░ The job identifier is 307.
  982. May 09 10:31:34 duet3 systemd[1]: modprobe@dm_mod.service: Deactivated successfully.
  983. ░░ Subject: Unit succeeded
  984. ░░ Defined-By: systemd
  985. ░░ Support: https://www.debian.org/support
  986. ░░
  987. ░░ The unit modprobe@dm_mod.service has successfully entered the 'dead' state.
  988. May 09 10:31:34 duet3 systemd[1]: Finished modprobe@dm_mod.service - Load Kernel Module dm_mod.
  989. ░░ Subject: A start job for unit modprobe@dm_mod.service has finished successfully
  990. ░░ Defined-By: systemd
  991. ░░ Support: https://www.debian.org/support
  992. ░░
  993. ░░ A start job for unit modprobe@dm_mod.service has finished successfully.
  994. ░░
  995. ░░ The job identifier is 347.
  996. May 09 10:31:34 duet3 systemd[1]: modprobe@efi_pstore.service: Deactivated successfully.
  997. ░░ Subject: Unit succeeded
  998. ░░ Defined-By: systemd
  999. ░░ Support: https://www.debian.org/support
  1000. ░░
  1001. ░░ The unit modprobe@efi_pstore.service has successfully entered the 'dead' state.
  1002. May 09 10:31:34 duet3 systemd[1]: Finished modprobe@efi_pstore.service - Load Kernel Module efi_pstore.
  1003. ░░ Subject: A start job for unit modprobe@efi_pstore.service has finished successfully
  1004. ░░ Defined-By: systemd
  1005. ░░ Support: https://www.debian.org/support
  1006. ░░
  1007. ░░ A start job for unit modprobe@efi_pstore.service has finished successfully.
  1008. ░░
  1009. ░░ The job identifier is 314.
  1010. May 09 10:31:34 duet3 systemd[1]: modprobe@loop.service: Deactivated successfully.
  1011. ░░ Subject: Unit succeeded
  1012. ░░ Defined-By: systemd
  1013. ░░ Support: https://www.debian.org/support
  1014. ░░
  1015. ░░ The unit modprobe@loop.service has successfully entered the 'dead' state.
  1016. May 09 10:31:34 duet3 systemd[1]: Finished modprobe@loop.service - Load Kernel Module loop.
  1017. ░░ Subject: A start job for unit modprobe@loop.service has finished successfully
  1018. ░░ Defined-By: systemd
  1019. ░░ Support: https://www.debian.org/support
  1020. ░░
  1021. ░░ A start job for unit modprobe@loop.service has finished successfully.
  1022. ░░
  1023. ░░ The job identifier is 346.
  1024. May 09 10:31:34 duet3 systemd[1]: systemd-pstore.service - Platform Persistent Storage Archival was skipped because of an unmet condition check (ConditionDirectoryNotEmpty=>
  1025. ░░ Subject: A start job for unit systemd-pstore.service has finished successfully
  1026. ░░ Defined-By: systemd
  1027. ░░ Support: https://www.debian.org/support
  1028. ░░
  1029. ░░ A start job for unit systemd-pstore.service has finished successfully.
  1030. ░░
  1031. ░░ The job identifier is 313.
  1032. May 09 10:31:34 duet3 systemd[1]: systemd-repart.service - Repartition Root Disk was skipped because no trigger condition checks were met.
  1033. ░░ Subject: A start job for unit systemd-repart.service has finished successfully
  1034. ░░ Defined-By: systemd
  1035. ░░ Support: https://www.debian.org/support
  1036. ░░
  1037. ░░ A start job for unit systemd-repart.service has finished successfully.
  1038. ░░
  1039. ░░ The job identifier is 345.
  1040. May 09 10:31:34 duet3 kernel: uart-pl011 fe201000.serial: no DMA platform data
  1041. May 09 10:31:35 duet3 kernel: Bluetooth: hci0: BCM: chip id 107
  1042. May 09 10:31:35 duet3 kernel: Bluetooth: hci0: BCM: features 0x2f
  1043. May 09 10:31:35 duet3 kernel: Bluetooth: hci0: BCM4345C0
  1044. May 09 10:31:35 duet3 kernel: Bluetooth: hci0: BCM4345C0 (003.001.025) build 0000
  1045. May 09 10:31:35 duet3 kernel: Bluetooth: hci0: BCM4345C0 'brcm/BCM4345C0.raspberrypi,4-model-b.hcd' Patch
  1046. May 09 10:31:35 duet3 kernel: brcmfmac: F1 signature read @0x18000000=0x15264345
  1047. May 09 10:31:35 duet3 kernel: brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
  1048. May 09 10:31:35 duet3 kernel: usbcore: registered new interface driver brcmfmac
  1049. May 09 10:31:35 duet3 kernel: brcmfmac_wcc: brcmf_wcc_attach: executing
  1050. May 09 10:31:35 duet3 kernel: brcmfmac: brcmf_c_process_txcap_blob: no txcap_blob available (err=-2)
  1051. May 09 10:31:35 duet3 kernel: brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Apr 15 2021 03:03:20 version 7.45.234 (4ca95bb CY) FWID 01-996384e2
  1052. May 09 10:31:35 duet3 kernel: Bluetooth: hci0: BCM: features 0x2f
  1053. May 09 10:31:35 duet3 kernel: Bluetooth: hci0: BCM43455 37.4MHz Raspberry Pi 3+-0190
  1054. May 09 10:31:35 duet3 kernel: Bluetooth: hci0: BCM4345C0 (003.001.025) build 0382
  1055. May 09 10:31:36 duet3 systemd[1]: Listening on systemd-rfkill.socket - Load/Save RF Kill Switch Status /dev/rfkill Watch.
  1056. ░░ Subject: A start job for unit systemd-rfkill.socket has finished successfully
  1057. ░░ Defined-By: systemd
  1058. ░░ Support: https://www.debian.org/support
  1059. ░░
  1060. ░░ A start job for unit systemd-rfkill.socket has finished successfully.
  1061. ░░
  1062. ░░ The job identifier is 440.
  1063. May 09 10:31:36 duet3 systemd[1]: Starting systemd-rfkill.service - Load/Save RF Kill Switch Status...
  1064. ░░ Subject: A start job for unit systemd-rfkill.service has begun execution
  1065. ░░ Defined-By: systemd
  1066. ░░ Support: https://www.debian.org/support
  1067. ░░
  1068. ░░ A start job for unit systemd-rfkill.service has begun execution.
  1069. ░░
  1070. ░░ The job identifier is 447.
  1071. May 09 10:31:36 duet3 (udev-worker)[512]: controlC2: Process '/usr/sbin/alsactl -E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 2' failed with exit code 2.
  1072. May 09 10:31:36 duet3 systemd[1]: systemd-ask-password-console.path - Dispatch Password Requests to Console Directory Watch was skipped because of an unmet condition check >
  1073. ░░ Subject: A start job for unit systemd-ask-password-console.path has finished successfully
  1074. ░░ Defined-By: systemd
  1075. ░░ Support: https://www.debian.org/support
  1076. ░░
  1077. ░░ A start job for unit systemd-ask-password-console.path has finished successfully.
  1078. ░░
  1079. ░░ The job identifier is 500.
  1080. May 09 10:31:36 duet3 systemd[1]: dev-hugepages.mount - Huge Pages File System was skipped because of an unmet condition check (ConditionPathExists=/sys/kernel/mm/hugepages>
  1081. ░░ Subject: A start job for unit dev-hugepages.mount has finished successfully
  1082. ░░ Defined-By: systemd
  1083. ░░ Support: https://www.debian.org/support
  1084. ░░
  1085. ░░ A start job for unit dev-hugepages.mount has finished successfully.
  1086. ░░
  1087. ░░ The job identifier is 483.
  1088. May 09 10:31:36 duet3 systemd[1]: Starting modprobe@dm_mod.service - Load Kernel Module dm_mod...
  1089. ░░ Subject: A start job for unit modprobe@dm_mod.service has begun execution
  1090. ░░ Defined-By: systemd
  1091. ░░ Support: https://www.debian.org/support
  1092. ░░
  1093. ░░ A start job for unit modprobe@dm_mod.service has begun execution.
  1094. ░░
  1095. ░░ The job identifier is 511.
  1096. May 09 10:31:36 duet3 systemd[1]: Starting modprobe@efi_pstore.service - Load Kernel Module efi_pstore...
  1097. ░░ Subject: A start job for unit modprobe@efi_pstore.service has begun execution
  1098. ░░ Defined-By: systemd
  1099. ░░ Support: https://www.debian.org/support
  1100. ░░
  1101. ░░ A start job for unit modprobe@efi_pstore.service has begun execution.
  1102. ░░
  1103. ░░ The job identifier is 478.
  1104. May 09 10:31:36 duet3 systemd[1]: Starting modprobe@loop.service - Load Kernel Module loop...
  1105. ░░ Subject: A start job for unit modprobe@loop.service has begun execution
  1106. ░░ Defined-By: systemd
  1107. ░░ Support: https://www.debian.org/support
  1108. ░░
  1109. ░░ A start job for unit modprobe@loop.service has begun execution.
  1110. ░░
  1111. ░░ The job identifier is 510.
  1112. May 09 10:31:36 duet3 systemd[1]: systemd-firstboot.service - First Boot Wizard was skipped because of an unmet condition check (ConditionFirstBoot=yes).
  1113. ░░ Subject: A start job for unit systemd-firstboot.service has finished successfully
  1114. ░░ Defined-By: systemd
  1115. ░░ Support: https://www.debian.org/support
  1116. ░░
  1117. ░░ A start job for unit systemd-firstboot.service has finished successfully.
  1118. ░░
  1119. ░░ The job identifier is 503.
  1120. May 09 10:31:36 duet3 systemd[1]: first-boot-complete.target - First Boot Complete was skipped because of an unmet condition check (ConditionFirstBoot=yes).
  1121. ░░ Subject: A start job for unit first-boot-complete.target has finished successfully
  1122. ░░ Defined-By: systemd
  1123. ░░ Support: https://www.debian.org/support
  1124. ░░
  1125. ░░ A start job for unit first-boot-complete.target has finished successfully.
  1126. ░░
  1127. ░░ The job identifier is 504.
  1128. May 09 10:31:36 duet3 systemd[1]: systemd-fsck-root.service - File System Check on Root Device was skipped because of an unmet condition check (ConditionPathExists=!/run/in>
  1129. ░░ Subject: A start job for unit systemd-fsck-root.service has finished successfully
  1130. ░░ Defined-By: systemd
  1131. ░░ Support: https://www.debian.org/support
  1132. ░░
  1133. ░░ A start job for unit systemd-fsck-root.service has finished successfully.
  1134. ░░
  1135. ░░ The job identifier is 471.
  1136. May 09 10:31:36 duet3 systemd[1]: Started systemd-rfkill.service - Load/Save RF Kill Switch Status.
  1137. ░░ Subject: A start job for unit systemd-rfkill.service has finished successfully
  1138. ░░ Defined-By: systemd
  1139. ░░ Support: https://www.debian.org/support
  1140. ░░
  1141. ░░ A start job for unit systemd-rfkill.service has finished successfully.
  1142. ░░
  1143. ░░ The job identifier is 447.
  1144. May 09 10:31:36 duet3 systemd[1]: modprobe@dm_mod.service: Deactivated successfully.
  1145. ░░ Subject: Unit succeeded
  1146. ░░ Defined-By: systemd
  1147. ░░ Support: https://www.debian.org/support
  1148. ░░
  1149. ░░ The unit modprobe@dm_mod.service has successfully entered the 'dead' state.
  1150. May 09 10:31:36 duet3 systemd[1]: Finished modprobe@dm_mod.service - Load Kernel Module dm_mod.
  1151. ░░ Subject: A start job for unit modprobe@dm_mod.service has finished successfully
  1152. ░░ Defined-By: systemd
  1153. ░░ Support: https://www.debian.org/support
  1154. ░░
  1155. ░░ A start job for unit modprobe@dm_mod.service has finished successfully.
  1156. ░░
  1157. ░░ The job identifier is 511.
  1158. May 09 10:31:36 duet3 systemd[1]: modprobe@efi_pstore.service: Deactivated successfully.
  1159. ░░ Subject: Unit succeeded
  1160. ░░ Defined-By: systemd
  1161. ░░ Support: https://www.debian.org/support
  1162. ░░
  1163. ░░ The unit modprobe@efi_pstore.service has successfully entered the 'dead' state.
  1164. May 09 10:31:36 duet3 systemd[1]: Finished modprobe@efi_pstore.service - Load Kernel Module efi_pstore.
  1165. ░░ Subject: A start job for unit modprobe@efi_pstore.service has finished successfully
  1166. ░░ Defined-By: systemd
  1167. ░░ Support: https://www.debian.org/support
  1168. ░░
  1169. ░░ A start job for unit modprobe@efi_pstore.service has finished successfully.
  1170. ░░
  1171. ░░ The job identifier is 478.
  1172. May 09 10:31:36 duet3 systemd[1]: modprobe@loop.service: Deactivated successfully.
  1173. ░░ Subject: Unit succeeded
  1174. ░░ Defined-By: systemd
  1175. ░░ Support: https://www.debian.org/support
  1176. ░░
  1177. ░░ The unit modprobe@loop.service has successfully entered the 'dead' state.
  1178. May 09 10:31:36 duet3 systemd[1]: Finished modprobe@loop.service - Load Kernel Module loop.
  1179. ░░ Subject: A start job for unit modprobe@loop.service has finished successfully
  1180. ░░ Defined-By: systemd
  1181. ░░ Support: https://www.debian.org/support
  1182. ░░
  1183. ░░ A start job for unit modprobe@loop.service has finished successfully.
  1184. ░░
  1185. ░░ The job identifier is 510.
  1186. May 09 10:31:36 duet3 systemd[1]: systemd-ask-password-console.path - Dispatch Password Requests to Console Directory Watch was skipped because of an unmet condition check >
  1187. ░░ Subject: A start job for unit systemd-ask-password-console.path has finished successfully
  1188. ░░ Defined-By: systemd
  1189. ░░ Support: https://www.debian.org/support
  1190. ░░
  1191. ░░ A start job for unit systemd-ask-password-console.path has finished successfully.
  1192. ░░
  1193. ░░ The job identifier is 575.
  1194. May 09 10:31:36 duet3 systemd[1]: dev-hugepages.mount - Huge Pages File System was skipped because of an unmet condition check (ConditionPathExists=/sys/kernel/mm/hugepages>
  1195. ░░ Subject: A start job for unit dev-hugepages.mount has finished successfully
  1196. ░░ Defined-By: systemd
  1197. ░░ Support: https://www.debian.org/support
  1198. ░░
  1199. ░░ A start job for unit dev-hugepages.mount has finished successfully.
  1200. ░░
  1201. ░░ The job identifier is 558.
  1202. May 09 10:31:36 duet3 systemd[1]: Starting modprobe@dm_mod.service - Load Kernel Module dm_mod...
  1203. ░░ Subject: A start job for unit modprobe@dm_mod.service has begun execution
  1204. ░░ Defined-By: systemd
  1205. ░░ Support: https://www.debian.org/support
  1206. ░░
  1207. ░░ A start job for unit modprobe@dm_mod.service has begun execution.
  1208. ░░
  1209. ░░ The job identifier is 586.
  1210. May 09 10:31:36 duet3 systemd[1]: Starting modprobe@efi_pstore.service - Load Kernel Module efi_pstore...
  1211. ░░ Subject: A start job for unit modprobe@efi_pstore.service has begun execution
  1212. ░░ Defined-By: systemd
  1213. ░░ Support: https://www.debian.org/support
  1214. ░░
  1215. ░░ A start job for unit modprobe@efi_pstore.service has begun execution.
  1216. ░░
  1217. ░░ The job identifier is 553.
  1218. May 09 10:31:36 duet3 systemd[1]: Starting modprobe@loop.service - Load Kernel Module loop...
  1219. ░░ Subject: A start job for unit modprobe@loop.service has begun execution
  1220. ░░ Defined-By: systemd
  1221. ░░ Support: https://www.debian.org/support
  1222. ░░
  1223. ░░ A start job for unit modprobe@loop.service has begun execution.
  1224. ░░
  1225. ░░ The job identifier is 585.
  1226. May 09 10:31:36 duet3 systemd[1]: systemd-firstboot.service - First Boot Wizard was skipped because of an unmet condition check (ConditionFirstBoot=yes).
  1227. ░░ Subject: A start job for unit systemd-firstboot.service has finished successfully
  1228. ░░ Defined-By: systemd
  1229. ░░ Support: https://www.debian.org/support
  1230. ░░
  1231. ░░ A start job for unit systemd-firstboot.service has finished successfully.
  1232. ░░
  1233. ░░ The job identifier is 578.
  1234. May 09 10:31:36 duet3 systemd[1]: first-boot-complete.target - First Boot Complete was skipped because of an unmet condition check (ConditionFirstBoot=yes).
  1235. ░░ Subject: A start job for unit first-boot-complete.target has finished successfully
  1236. ░░ Defined-By: systemd
  1237. ░░ Support: https://www.debian.org/support
  1238. ░░
  1239. ░░ A start job for unit first-boot-complete.target has finished successfully.
  1240. ░░
  1241. ░░ The job identifier is 579.
  1242. May 09 10:31:36 duet3 systemd[1]: systemd-fsck-root.service - File System Check on Root Device was skipped because of an unmet condition check (ConditionPathExists=!/run/in>
  1243. ░░ Subject: A start job for unit systemd-fsck-root.service has finished successfully
  1244. ░░ Defined-By: systemd
  1245. ░░ Support: https://www.debian.org/support
  1246. ░░
  1247. ░░ A start job for unit systemd-fsck-root.service has finished successfully.
  1248. ░░
  1249. ░░ The job identifier is 546.
  1250. May 09 10:31:36 duet3 systemd[1]: modprobe@dm_mod.service: Deactivated successfully.
  1251. ░░ Subject: Unit succeeded
  1252. ░░ Defined-By: systemd
  1253. ░░ Support: https://www.debian.org/support
  1254. ░░
  1255. ░░ The unit modprobe@dm_mod.service has successfully entered the 'dead' state.
  1256. May 09 10:31:36 duet3 systemd[1]: Finished modprobe@dm_mod.service - Load Kernel Module dm_mod.
  1257. ░░ Subject: A start job for unit modprobe@dm_mod.service has finished successfully
  1258. ░░ Defined-By: systemd
  1259. ░░ Support: https://www.debian.org/support
  1260. ░░
  1261. ░░ A start job for unit modprobe@dm_mod.service has finished successfully.
  1262. ░░
  1263. ░░ The job identifier is 586.
  1264. May 09 10:31:36 duet3 systemd[1]: modprobe@efi_pstore.service: Deactivated successfully.
  1265. ░░ Subject: Unit succeeded
  1266. ░░ Defined-By: systemd
  1267. ░░ Support: https://www.debian.org/support
  1268. ░░
  1269. ░░ The unit modprobe@efi_pstore.service has successfully entered the 'dead' state.
  1270. May 09 10:31:36 duet3 systemd[1]: Finished modprobe@efi_pstore.service - Load Kernel Module efi_pstore.
  1271. ░░ Subject: A start job for unit modprobe@efi_pstore.service has finished successfully
  1272. ░░ Defined-By: systemd
  1273. ░░ Support: https://www.debian.org/support
  1274. ░░
  1275. ░░ A start job for unit modprobe@efi_pstore.service has finished successfully.
  1276. ░░
  1277. ░░ The job identifier is 553.
  1278. May 09 10:31:36 duet3 systemd[1]: modprobe@loop.service: Deactivated successfully.
  1279. ░░ Subject: Unit succeeded
  1280. ░░ Defined-By: systemd
  1281. ░░ Support: https://www.debian.org/support
  1282. ░░
  1283. ░░ The unit modprobe@loop.service has successfully entered the 'dead' state.
  1284. May 09 10:31:36 duet3 systemd[1]: Finished modprobe@loop.service - Load Kernel Module loop.
  1285. ░░ Subject: A start job for unit modprobe@loop.service has finished successfully
  1286. ░░ Defined-By: systemd
  1287. ░░ Support: https://www.debian.org/support
  1288. ░░
  1289. ░░ A start job for unit modprobe@loop.service has finished successfully.
  1290. ░░
  1291. ░░ The job identifier is 585.
  1292. May 09 10:31:36 duet3 systemd[1]: systemd-pstore.service - Platform Persistent Storage Archival was skipped because of an unmet condition check (ConditionDirectoryNotEmpty=>
  1293. ░░ Subject: A start job for unit systemd-pstore.service has finished successfully
  1294. ░░ Defined-By: systemd
  1295. ░░ Support: https://www.debian.org/support
  1296. ░░
  1297. ░░ A start job for unit systemd-pstore.service has finished successfully.
  1298. ░░
  1299. ░░ The job identifier is 477.
  1300. May 09 10:31:36 duet3 systemd[1]: systemd-repart.service - Repartition Root Disk was skipped because no trigger condition checks were met.
  1301. ░░ Subject: A start job for unit systemd-repart.service has finished successfully
  1302. ░░ Defined-By: systemd
  1303. ░░ Support: https://www.debian.org/support
  1304. ░░
  1305. ░░ A start job for unit systemd-repart.service has finished successfully.
  1306. ░░
  1307. ░░ The job identifier is 509.
  1308. May 09 10:31:41 duet3 systemd[1]: systemd-rfkill.service: Deactivated successfully.
  1309. ░░ Subject: Unit succeeded
  1310. ░░ Defined-By: systemd
  1311. ░░ Support: https://www.debian.org/support
  1312. ░░
  1313. ░░ The unit systemd-rfkill.service has successfully entered the 'dead' state.
  1314. May 09 10:32:34 duet3 (udev-worker)[309]: sda1: Spawned process '/bin/systemctl start usb-mount@sda1.service' [364] is taking longer than 59s to complete
  1315. May 09 10:32:34 duet3 (udev-worker)[323]: sda2: Spawned process '/bin/systemctl start usb-mount@sda2.service' [359] is taking longer than 59s to complete
  1316. May 09 10:32:34 duet3 systemd-udevd[305]: sda1: Worker [309] processing SEQNUM=2038 is taking a long time
  1317. May 09 10:32:34 duet3 systemd-udevd[305]: sda2: Worker [323] processing SEQNUM=2039 is taking a long time
  1318. May 09 10:33:01 duet3 systemd[1]: dev-disk-by\x2dpartuuid-2b7037cc\x2d01.device: Job dev-disk-by\x2dpartuuid-2b7037cc\x2d01.device/start timed out.
  1319. May 09 10:33:01 duet3 systemd[1]: Timed out waiting for device dev-disk-by\x2dpartuuid-2b7037cc\x2d01.device - /dev/disk/by-partuuid/2b7037cc-01.
  1320. ░░ Subject: A start job for unit dev-disk-by\x2dpartuuid-2b7037cc\x2d01.device has failed
  1321. ░░ Defined-By: systemd
  1322. ░░ Support: https://www.debian.org/support
  1323. ░░
  1324. ░░ A start job for unit dev-disk-by\x2dpartuuid-2b7037cc\x2d01.device has finished with a failure.
  1325. ░░
  1326. ░░ The job identifier is 13 and the job result is timeout.
  1327. May 09 10:33:01 duet3 systemd[1]: Dependency failed for boot-firmware.mount - /boot/firmware.
  1328. ░░ Subject: A start job for unit boot-firmware.mount has failed
  1329. ░░ Defined-By: systemd
  1330. ░░ Support: https://www.debian.org/support
  1331. ░░
  1332. ░░ A start job for unit boot-firmware.mount has finished with a failure.
  1333. ░░
  1334. ░░ The job identifier is 8 and the job result is dependency.
  1335. May 09 10:33:01 duet3 systemd[1]: Dependency failed for local-fs.target - Local File Systems.
  1336. ░░ Subject: A start job for unit local-fs.target has failed
  1337. ░░ Defined-By: systemd
  1338. ░░ Support: https://www.debian.org/support
  1339. ░░
  1340. ░░ A start job for unit local-fs.target has finished with a failure.
  1341. ░░
  1342. ░░ The job identifier is 7 and the job result is dependency.
  1343. May 09 10:33:01 duet3 systemd[1]: local-fs.target: Job local-fs.target/start failed with result 'dependency'.
  1344. May 09 10:33:01 duet3 systemd[1]: local-fs.target: Triggering OnFailure= dependencies.
  1345. May 09 10:33:01 duet3 (udev-worker)[309]: sda1: Process '/bin/systemctl start usb-mount@sda1.service' failed with exit code 1.
  1346. May 09 10:33:01 duet3 systemd[1]: boot-firmware.mount: Job boot-firmware.mount/start failed with result 'dependency'.
  1347. May 09 10:33:01 duet3 systemd[1]: Dependency failed for systemd-fsck@dev-disk-by\x2dpartuuid-2b7037cc\x2d01.service - File System Check on /dev/disk/by-partuuid/2b7037cc-01.
  1348. ░░ Subject: A start job for unit systemd-fsck@dev-disk-by\x2dpartuuid-2b7037cc\x2d01.service has failed
  1349. ░░ Defined-By: systemd
  1350. ░░ Support: https://www.debian.org/support
  1351. ░░
  1352. ░░ A start job for unit systemd-fsck@dev-disk-by\x2dpartuuid-2b7037cc\x2d01.service has finished with a failure.
  1353. ░░
  1354. ░░ The job identifier is 10 and the job result is dependency.
  1355. May 09 10:33:01 duet3 systemd[1]: systemd-fsck@dev-disk-by\x2dpartuuid-2b7037cc\x2d01.service: Job systemd-fsck@dev-disk-by\x2dpartuuid-2b7037cc\x2d01.service/start failed >
  1356. May 09 10:33:01 duet3 systemd[1]: dev-disk-by\x2dpartuuid-2b7037cc\x2d01.device: Job dev-disk-by\x2dpartuuid-2b7037cc\x2d01.device/start failed with result 'timeout'.
  1357. May 09 10:33:01 duet3 (udev-worker)[323]: sda2: Process '/bin/systemctl start usb-mount@sda2.service' failed with exit code 1.
  1358. May 09 10:33:02 duet3 systemd[1]: systemd-ask-password-wall.path: Deactivated successfully.
  1359. ░░ Subject: Unit succeeded
  1360. ░░ Defined-By: systemd
  1361. ░░ Support: https://www.debian.org/support
  1362. ░░
  1363. ░░ The unit systemd-ask-password-wall.path has successfully entered the 'dead' state.
  1364. May 09 10:33:02 duet3 systemd[1]: Stopped systemd-ask-password-wall.path - Forward Password Requests to Wall Directory Watch.
  1365. ░░ Subject: A stop job for unit systemd-ask-password-wall.path has finished
  1366. ░░ Defined-By: systemd
  1367. ░░ Support: https://www.debian.org/support
  1368. ░░
  1369. ░░ A stop job for unit systemd-ask-password-wall.path has finished.
  1370. ░░
  1371. ░░ The job identifier is 678 and the job result is done.
  1372. May 09 10:33:02 duet3 systemd[1]: Reached target timers.target - Timer Units.
  1373. ░░ Subject: A start job for unit timers.target has finished successfully
  1374. ░░ Defined-By: systemd
  1375. ░░ Support: https://www.debian.org/support
  1376. ░░
  1377. ░░ A start job for unit timers.target has finished successfully.
  1378. ░░
  1379. ░░ The job identifier is 81.
  1380. May 09 10:33:02 duet3 systemd[1]: Reached target sound.target - Sound Card.
  1381. ░░ Subject: A start job for unit sound.target has finished successfully
  1382. ░░ Defined-By: systemd
  1383. ░░ Support: https://www.debian.org/support
  1384. ░░
  1385. ░░ A start job for unit sound.target has finished successfully.
  1386. ░░
  1387. ░░ The job identifier is 291.
  1388. May 09 10:33:02 duet3 systemd[1]: Reached target bluetooth.target - Bluetooth Support.
  1389. ░░ Subject: A start job for unit bluetooth.target has finished successfully
  1390. ░░ Defined-By: systemd
  1391. ░░ Support: https://www.debian.org/support
  1392. ░░
  1393. ░░ A start job for unit bluetooth.target has finished successfully.
  1394. ░░
  1395. ░░ The job identifier is 529.
  1396. May 09 10:33:02 duet3 systemd[1]: Reached target getty.target - Login Prompts.
  1397. ░░ Subject: A start job for unit getty.target has finished successfully
  1398. ░░ Defined-By: systemd
  1399. ░░ Support: https://www.debian.org/support
  1400. ░░
  1401. ░░ A start job for unit getty.target has finished successfully.
  1402. ░░
  1403. ░░ The job identifier is 92.
  1404. May 09 10:33:02 duet3 systemd[1]: Starting console-setup.service - Set console font and keymap...
  1405. ░░ Subject: A start job for unit console-setup.service has begun execution
  1406. ░░ Defined-By: systemd
  1407. ░░ Support: https://www.debian.org/support
  1408. ░░
  1409. ░░ A start job for unit console-setup.service has begun execution.
  1410. ░░
  1411. ░░ The job identifier is 137.
  1412. May 09 10:33:02 duet3 systemd[1]: systemd-machine-id-commit.service - Commit a transient machine-id on disk was skipped because of an unmet condition check (ConditionPathIs>
  1413. ░░ Subject: A start job for unit systemd-machine-id-commit.service has finished successfully
  1414. ░░ Defined-By: systemd
  1415. ░░ Support: https://www.debian.org/support
  1416. ░░
  1417. ░░ A start job for unit systemd-machine-id-commit.service has finished successfully.
  1418. ░░
  1419. ░░ The job identifier is 37.
  1420. May 09 10:33:02 duet3 systemd[1]: Reached target sockets.target - Socket Units.
  1421. ░░ Subject: A start job for unit sockets.target has finished successfully
  1422. ░░ Defined-By: systemd
  1423. ░░ Support: https://www.debian.org/support
  1424. ░░
  1425. ░░ A start job for unit sockets.target has finished successfully.
  1426. ░░
  1427. ░░ The job identifier is 76.
  1428. May 09 10:33:02 duet3 systemd[1]: Starting apparmor.service - Load AppArmor profiles...
  1429. ░░ Subject: A start job for unit apparmor.service has begun execution
  1430. ░░ Defined-By: systemd
  1431. ░░ Support: https://www.debian.org/support
  1432. ░░
  1433. ░░ A start job for unit apparmor.service has begun execution.
  1434. ░░
  1435. ░░ The job identifier is 19.
  1436. May 09 10:33:02 duet3 systemd[1]: Started emergency.service - Emergency Shell.
  1437. ░░ Subject: A start job for unit emergency.service has finished successfully
  1438. ░░ Defined-By: systemd
  1439. ░░ Support: https://www.debian.org/support
  1440. ░░
  1441. ░░ A start job for unit emergency.service has finished successfully.
  1442. ░░
  1443. ░░ The job identifier is 605.
  1444. May 09 10:33:02 duet3 systemd[1]: Reached target emergency.target - Emergency Mode.
  1445. ░░ Subject: A start job for unit emergency.target has finished successfully
  1446. ░░ Defined-By: systemd
  1447. ░░ Support: https://www.debian.org/support
  1448. ░░
  1449. ░░ A start job for unit emergency.target has finished successfully.
  1450. ░░
  1451. ░░ The job identifier is 604.
  1452. May 09 10:33:02 duet3 systemd[1]: Starting plymouth-read-write.service - Tell Plymouth To Write Out Runtime Data...
  1453. ░░ Subject: A start job for unit plymouth-read-write.service has begun execution
  1454. ░░ Defined-By: systemd
  1455. ░░ Support: https://www.debian.org/support
  1456. ░░
  1457. ░░ A start job for unit plymouth-read-write.service has begun execution.
  1458. ░░
  1459. ░░ The job identifier is 36.
  1460. May 09 10:33:02 duet3 systemd[1]: Starting systemd-binfmt.service - Set Up Additional Binary Formats...
  1461. ░░ Subject: A start job for unit systemd-binfmt.service has begun execution
  1462. ░░ Defined-By: systemd
  1463. ░░ Support: https://www.debian.org/support
  1464. ░░
  1465. ░░ A start job for unit systemd-binfmt.service has begun execution.
  1466. ░░
  1467. ░░ The job identifier is 31.
  1468. May 09 10:33:02 duet3 systemd[1]: systemd-pcrphase-sysinit.service - TPM2 PCR Barrier (Initialization) was skipped because of an unmet condition check (ConditionPathExists=>
  1469. ░░ Subject: A start job for unit systemd-pcrphase-sysinit.service has finished successfully
  1470. ░░ Defined-By: systemd
  1471. ░░ Support: https://www.debian.org/support
  1472. ░░
  1473. ░░ A start job for unit systemd-pcrphase-sysinit.service has finished successfully.
  1474. ░░
  1475. ░░ The job identifier is 38.
  1476. May 09 10:33:02 duet3 systemd[1]: Starting systemd-tmpfiles-setup.service - Create Volatile Files and Directories...
  1477. ░░ Subject: A start job for unit systemd-tmpfiles-setup.service has begun execution
  1478. ░░ Defined-By: systemd
  1479. ░░ Support: https://www.debian.org/support
  1480. ░░
  1481. ░░ A start job for unit systemd-tmpfiles-setup.service has begun execution.
  1482. ░░
  1483. ░░ The job identifier is 60.
  1484. May 09 10:33:02 duet3 systemd[1]: Finished console-setup.service - Set console font and keymap.
  1485. ░░ Subject: A start job for unit console-setup.service has finished successfully
  1486. ░░ Defined-By: systemd
  1487. ░░ Support: https://www.debian.org/support
  1488. ░░
  1489. ░░ A start job for unit console-setup.service has finished successfully.
  1490. ░░
  1491. ░░ The job identifier is 137.
  1492. May 09 10:33:02 duet3 systemd[1]: proc-sys-fs-binfmt_misc.automount: Got automount request for /proc/sys/fs/binfmt_misc, triggered by 586 (systemd-binfmt)
  1493. May 09 10:33:02 duet3 systemd[1]: Mounting proc-sys-fs-binfmt_misc.mount - Arbitrary Executable File Formats File System...
  1494. ░░ Subject: A start job for unit proc-sys-fs-binfmt_misc.mount has begun execution
  1495. ░░ Defined-By: systemd
  1496. ░░ Support: https://www.debian.org/support
  1497. ░░
  1498. ░░ A start job for unit proc-sys-fs-binfmt_misc.mount has begun execution.
  1499. ░░
  1500. ░░ The job identifier is 683.
  1501. May 09 10:33:02 duet3 apparmor.systemd[581]: Restarting AppArmor
  1502. May 09 10:33:02 duet3 apparmor.systemd[581]: Reloading AppArmor profiles
  1503. May 09 10:33:02 duet3 systemd[1]: Finished plymouth-read-write.service - Tell Plymouth To Write Out Runtime Data.
  1504. ░░ Subject: A start job for unit plymouth-read-write.service has finished successfully
  1505. ░░ Defined-By: systemd
  1506. ░░ Support: https://www.debian.org/support
  1507. ░░
  1508. ░░ A start job for unit plymouth-read-write.service has finished successfully.
  1509. ░░
  1510. ░░ The job identifier is 36.
  1511. May 09 10:33:02 duet3 systemd[1]: Mounted proc-sys-fs-binfmt_misc.mount - Arbitrary Executable File Formats File System.
  1512. ░░ Subject: A start job for unit proc-sys-fs-binfmt_misc.mount has finished successfully
  1513. ░░ Defined-By: systemd
  1514. ░░ Support: https://www.debian.org/support
  1515. ░░
  1516. ░░ A start job for unit proc-sys-fs-binfmt_misc.mount has finished successfully.
  1517. ░░
  1518. ░░ The job identifier is 683.
  1519. May 09 10:33:02 duet3 systemd[1]: Received SIGRTMIN+20 from PID 199 (plymouthd).
  1520. May 09 10:33:02 duet3 systemd[1]: Finished systemd-binfmt.service - Set Up Additional Binary Formats.
  1521. ░░ Subject: A start job for unit systemd-binfmt.service has finished successfully
  1522. ░░ Defined-By: systemd
  1523. ░░ Support: https://www.debian.org/support
  1524. ░░
  1525. ░░ A start job for unit systemd-binfmt.service has finished successfully.
  1526. ░░
  1527. ░░ The job identifier is 31.
  1528. May 09 10:33:02 duet3 kernel: audit: type=1400 audit(1715247182.271:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=599 comm=>
  1529. May 09 10:33:02 duet3 kernel: audit: type=1400 audit(1715247182.271:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=599>
  1530. May 09 10:33:02 duet3 kernel: audit: type=1400 audit(1715247182.275:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="lsb_release" pid=598 comm="app>
  1531. May 09 10:33:02 duet3 audit[599]: AVC apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=599 comm="apparmor_parser"
  1532. May 09 10:33:02 duet3 audit[599]: AVC apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=599 comm="apparmor_parser"
  1533. May 09 10:33:02 duet3 audit[598]: AVC apparmor="STATUS" operation="profile_load" profile="unconfined" name="lsb_release" pid=598 comm="apparmor_parser"
  1534. May 09 10:33:02 duet3 audit[602]: AVC apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=602 comm="apparmor_parser"
  1535. May 09 10:33:02 duet3 audit[602]: AVC apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_filter" pid=602 comm="apparmor_parser"
  1536. May 09 10:33:02 duet3 audit[602]: AVC apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_groff" pid=602 comm="apparmor_parser"
  1537. May 09 10:33:02 duet3 kernel: audit: type=1400 audit(1715247182.295:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=602 comm="ap>
  1538. May 09 10:33:02 duet3 kernel: audit: type=1400 audit(1715247182.295:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_filter" pid=602 comm="appa>
  1539. May 09 10:33:02 duet3 kernel: audit: type=1400 audit(1715247182.295:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_groff" pid=602 comm="appar>
  1540. May 09 10:33:02 duet3 kernel: audit: type=1400 audit(1715247182.299:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/arm-linux-gnueabihf/l>
  1541. May 09 10:33:02 duet3 kernel: audit: type=1400 audit(1715247182.299:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/arm-linux-gnueabihf/l>
  1542. May 09 10:33:02 duet3 audit[597]: AVC apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/arm-linux-gnueabihf/lightdm/lightdm-guest-session" pid=>
  1543. May 09 10:33:02 duet3 audit[597]: AVC apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/arm-linux-gnueabihf/lightdm/lightdm-guest-session//chro>
  1544. May 09 10:33:02 duet3 systemd[1]: Finished systemd-tmpfiles-setup.service - Create Volatile Files and Directories.
  1545. ░░ Subject: A start job for unit systemd-tmpfiles-setup.service has finished successfully
  1546. ░░ Defined-By: systemd
  1547. ░░ Support: https://www.debian.org/support
  1548. ░░
  1549. ░░ A start job for unit systemd-tmpfiles-setup.service has finished successfully.
  1550. ░░
  1551. ░░ The job identifier is 60.
  1552. May 09 10:33:02 duet3 audit[603]: AVC apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/cups-browsed" pid=603 comm="apparmor_parser"
  1553. May 09 10:33:02 duet3 kernel: audit: type=1400 audit(1715247182.323:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/cups-browsed" pid=6>
  1554. May 09 10:33:02 duet3 systemd[1]: Mounting run-rpc_pipefs.mount - RPC Pipe File System...
  1555. ░░ Subject: A start job for unit run-rpc_pipefs.mount has begun execution
  1556. ░░ Defined-By: systemd
  1557. ░░ Support: https://www.debian.org/support
  1558. ░░
  1559. ░░ A start job for unit run-rpc_pipefs.mount has begun execution.
  1560. ░░
  1561. ░░ The job identifier is 112.
  1562. May 09 10:33:02 duet3 audit[600]: AVC apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=600 comm="app>
  1563. May 09 10:33:02 duet3 audit[600]: AVC apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-helper" pid=600 comm="apparmor_p>
  1564. May 09 10:33:02 duet3 kernel: audit: type=1400 audit(1715247182.339:11): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dh>
  1565. May 09 10:33:02 duet3 audit[600]: AVC apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=600 comm="apparmor>
  1566. May 09 10:33:02 duet3 audit[600]: AVC apparmor="STATUS" operation="profile_load" profile="unconfined" name="/{,usr/}sbin/dhclient" pid=600 comm="apparmor_parser"
  1567. May 09 10:33:02 duet3 systemd[1]: Starting systemd-timesyncd.service - Network Time Synchronization...
  1568. ░░ Subject: A start job for unit systemd-timesyncd.service has begun execution
  1569. ░░ Defined-By: systemd
  1570. ░░ Support: https://www.debian.org/support
  1571. ░░
  1572. ░░ A start job for unit systemd-timesyncd.service has begun execution.
  1573. ░░
  1574. ░░ The job identifier is 27.
  1575. May 09 10:33:02 duet3 audit[604]: AVC apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=604 comm="apparmor_parser"
  1576. May 09 10:33:02 duet3 audit[604]: AVC apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/cupsd" pid=604 comm="apparmor_parser"
  1577. May 09 10:33:02 duet3 audit[604]: AVC apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/cupsd//third_party" pid=604 comm="apparmor_parser"
  1578. May 09 10:33:02 duet3 systemd[1]: Starting systemd-update-utmp.service - Record System Boot/Shutdown in UTMP...
  1579. ░░ Subject: A start job for unit systemd-update-utmp.service has begun execution
  1580. ░░ Defined-By: systemd
  1581. ░░ Support: https://www.debian.org/support
  1582. ░░
  1583. ░░ A start job for unit systemd-update-utmp.service has begun execution.
  1584. ░░
  1585. ░░ The job identifier is 122.
  1586. May 09 10:33:02 duet3 systemd[1]: Mounted run-rpc_pipefs.mount - RPC Pipe File System.
  1587. ░░ Subject: A start job for unit run-rpc_pipefs.mount has finished successfully
  1588. ░░ Defined-By: systemd
  1589. ░░ Support: https://www.debian.org/support
  1590. ░░
  1591. ░░ A start job for unit run-rpc_pipefs.mount has finished successfully.
  1592. ░░
  1593. ░░ The job identifier is 112.
  1594. May 09 10:33:02 duet3 systemd[1]: Reached target rpc_pipefs.target.
  1595. ░░ Subject: A start job for unit rpc_pipefs.target has finished successfully
  1596. ░░ Defined-By: systemd
  1597. ░░ Support: https://www.debian.org/support
  1598. ░░
  1599. ░░ A start job for unit rpc_pipefs.target has finished successfully.
  1600. ░░
  1601. ░░ The job identifier is 111.
  1602. May 09 10:33:02 duet3 systemd[1]: rpc-gssd.service - RPC security service for NFS client and server was skipped because of an unmet condition check (ConditionPathExists=/et>
  1603. ░░ Subject: A start job for unit rpc-gssd.service has finished successfully
  1604. ░░ Defined-By: systemd
  1605. ░░ Support: https://www.debian.org/support
  1606. ░░
  1607. ░░ A start job for unit rpc-gssd.service has finished successfully.
  1608. ░░
  1609. ░░ The job identifier is 110.
  1610. May 09 10:33:02 duet3 systemd[1]: Reached target nfs-client.target - NFS client services.
  1611. ░░ Subject: A start job for unit nfs-client.target has finished successfully
  1612. ░░ Defined-By: systemd
  1613. ░░ Support: https://www.debian.org/support
  1614. ░░
  1615. ░░ A start job for unit nfs-client.target has finished successfully.
  1616. ░░
  1617. ░░ The job identifier is 101.
  1618. May 09 10:33:02 duet3 systemd[1]: Reached target remote-fs-pre.target - Preparation for Remote File Systems.
  1619. ░░ Subject: A start job for unit remote-fs-pre.target has finished successfully
  1620. ░░ Defined-By: systemd
  1621. ░░ Support: https://www.debian.org/support
  1622. ░░
  1623. ░░ A start job for unit remote-fs-pre.target has finished successfully.
  1624. ░░
  1625. ░░ The job identifier is 113.
  1626. May 09 10:33:02 duet3 systemd[1]: Reached target remote-fs.target - Remote File Systems.
  1627. ░░ Subject: A start job for unit remote-fs.target has finished successfully
  1628. ░░ Defined-By: systemd
  1629. ░░ Support: https://www.debian.org/support
  1630. ░░
  1631. ░░ A start job for unit remote-fs.target has finished successfully.
  1632. ░░
  1633. ░░ The job identifier is 100.
  1634. May 09 10:33:02 duet3 audit[601]: AVC apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/evince" pid=601 comm="apparmor_parser"
  1635. May 09 10:33:02 duet3 audit[601]: AVC apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/evince//sanitized_helper" pid=601 comm="apparmor_parser"
  1636. May 09 10:33:02 duet3 audit[601]: AVC apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/evince-previewer" pid=601 comm="apparmor_parser"
  1637. May 09 10:33:02 duet3 audit[601]: AVC apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/evince-previewer//sanitized_helper" pid=601 comm="appar>
  1638. May 09 10:33:02 duet3 audit[601]: AVC apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/evince-thumbnailer" pid=601 comm="apparmor_parser"
  1639. May 09 10:33:02 duet3 systemd[1]: Finished systemd-update-utmp.service - Record System Boot/Shutdown in UTMP.
  1640. ░░ Subject: A start job for unit systemd-update-utmp.service has finished successfully
  1641. ░░ Defined-By: systemd
  1642. ░░ Support: https://www.debian.org/support
  1643. ░░
  1644. ░░ A start job for unit systemd-update-utmp.service has finished successfully.
  1645. ░░
  1646. ░░ The job identifier is 122.
  1647. May 09 10:33:02 duet3 systemd[1]: Finished apparmor.service - Load AppArmor profiles.
  1648. ░░ Subject: A start job for unit apparmor.service has finished successfully
  1649. ░░ Defined-By: systemd
  1650. ░░ Support: https://www.debian.org/support
  1651. ░░
  1652. ░░ A start job for unit apparmor.service has finished successfully.
  1653. ░░
  1654. ░░ The job identifier is 19.
  1655. May 09 10:33:02 duet3 systemd[1]: Starting networking.service - Raise network interfaces...
  1656. ░░ Subject: A start job for unit networking.service has begun execution
  1657. ░░ Defined-By: systemd
  1658. ░░ Support: https://www.debian.org/support
  1659. ░░
  1660. ░░ A start job for unit networking.service has begun execution.
  1661. ░░
  1662. ░░ The job identifier is 107.
  1663. May 09 10:33:02 duet3 systemd[1]: Starting systemd-update-utmp-runlevel.service - Record Runlevel Change in UTMP...
  1664. ░░ Subject: A start job for unit systemd-update-utmp-runlevel.service has begun execution
  1665. ░░ Defined-By: systemd
  1666. ░░ Support: https://www.debian.org/support
  1667. ░░
  1668. ░░ A start job for unit systemd-update-utmp-runlevel.service has begun execution.
  1669. ░░
  1670. ░░ The job identifier is 121.
  1671. May 09 10:33:02 duet3 systemd-update-utmp[610]: Failed to get new runlevel, utmp update skipped.
  1672. May 09 10:33:02 duet3 systemd[1]: systemd-update-utmp-runlevel.service: Deactivated successfully.
  1673. ░░ Subject: Unit succeeded
  1674. ░░ Defined-By: systemd
  1675. ░░ Support: https://www.debian.org/support
  1676. ░░
  1677. ░░ The unit systemd-update-utmp-runlevel.service has successfully entered the 'dead' state.
  1678. May 09 10:33:02 duet3 systemd[1]: Finished systemd-update-utmp-runlevel.service - Record Runlevel Change in UTMP.
  1679. ░░ Subject: A start job for unit systemd-update-utmp-runlevel.service has finished successfully
  1680. ░░ Defined-By: systemd
  1681. ░░ Support: https://www.debian.org/support
  1682. ░░
  1683. ░░ A start job for unit systemd-update-utmp-runlevel.service has finished successfully.
  1684. ░░
  1685. ░░ The job identifier is 121.
  1686. May 09 10:33:02 duet3 systemd[1]: Started systemd-timesyncd.service - Network Time Synchronization.
  1687. ░░ Subject: A start job for unit systemd-timesyncd.service has finished successfully
  1688. ░░ Defined-By: systemd
  1689. ░░ Support: https://www.debian.org/support
  1690. ░░
  1691. ░░ A start job for unit systemd-timesyncd.service has finished successfully.
  1692. ░░
  1693. ░░ The job identifier is 27.
  1694. May 09 10:33:02 duet3 systemd[1]: Reached target time-set.target - System Time Set.
  1695. ░░ Subject: A start job for unit time-set.target has finished successfully
  1696. ░░ Defined-By: systemd
  1697. ░░ Support: https://www.debian.org/support
  1698. ░░
  1699. ░░ A start job for unit time-set.target has finished successfully.
  1700. ░░
  1701. ░░ The job identifier is 28.
  1702. May 09 10:33:02 duet3 systemd[1]: Finished networking.service - Raise network interfaces.
  1703. ░░ Subject: A start job for unit networking.service has finished successfully
  1704. ░░ Defined-By: systemd
  1705. ░░ Support: https://www.debian.org/support
  1706. ░░
  1707. ░░ A start job for unit networking.service has finished successfully.
  1708. ░░
  1709. ░░ The job identifier is 107.
  1710.  
  1711.  
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!