NEWS
Seltsame Abstürze RPI4
-
@uwe-waizmann sagte in Seltsame Abstürze RPI4:
Kannst du mal nach dem kernel.log und dem sys.log schauen? Sollten in /var/log/ liegen. So um 16:17 herum sollte da was drinstehen.
-
@thomas-braun
sehr gerne, hoffe wir kommen dem Problem näher, denn so nervt das schon gewaltig
kern.logApr 15 16:17:06 whome kernel: [ 4.893869] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null) Apr 15 16:17:06 whome kernel: [ 4.897861] VFS: Mounted root (ext4 filesystem) readonly on device 8:2. Apr 15 16:17:06 whome kernel: [ 4.902417] devtmpfs: mounted Apr 15 16:17:06 whome kernel: [ 4.915383] Freeing unused kernel memory: 2048K Apr 15 16:17:06 whome kernel: [ 4.933736] Run /sbin/init as init process Apr 15 16:17:06 whome kernel: [ 4.937579] with arguments: Apr 15 16:17:06 whome kernel: [ 4.937593] /sbin/init Apr 15 16:17:06 whome kernel: [ 4.937607] with environment: Apr 15 16:17:06 whome kernel: [ 4.937622] HOME=/ Apr 15 16:17:06 whome kernel: [ 4.937636] TERM=linux Apr 15 16:17:06 whome kernel: [ 5.556776] NET: Registered protocol family 10 Apr 15 16:17:06 whome kernel: [ 5.562163] Segment Routing with IPv6 Apr 15 16:17:06 whome kernel: [ 6.594095] random: systemd: uninitialized urandom read (16 bytes read) Apr 15 16:17:06 whome kernel: [ 6.615339] random: systemd: uninitialized urandom read (16 bytes read) Apr 15 16:17:06 whome kernel: [ 6.630295] random: systemd: uninitialized urandom read (16 bytes read) Apr 15 16:17:06 whome kernel: [ 6.793710] i2c /dev entries driver Apr 15 16:17:06 whome kernel: [ 7.539932] EXT4-fs (sda2): re-mounted. Opts: (null) Apr 15 16:17:06 whome kernel: [ 8.394406] rpivid-mem feb00000.hevc-decoder: rpivid-hevcmem initialised: Registers at 0xfeb00000 length 0x00010000 Apr 15 16:17:06 whome kernel: [ 8.402145] rpivid-mem feb10000.rpivid-local-intc: rpivid-intcmem initialised: Registers at 0xfeb10000 length 0x00001000 Apr 15 16:17:06 whome kernel: [ 8.407404] rpivid-mem feb20000.h264-decoder: rpivid-h264mem initialised: Registers at 0xfeb20000 length 0x00010000 Apr 15 16:17:06 whome kernel: [ 8.408391] rpivid-mem feb30000.vp9-decoder: rpivid-vp9mem initialised: Registers at 0xfeb30000 length 0x00010000 Apr 15 16:17:06 whome kernel: [ 8.483250] snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned. Apr 15 16:17:06 whome kernel: [ 8.501575] mc: Linux media interface: v0.10 Apr 15 16:17:06 whome kernel: [ 8.501830] bcm2835_audio bcm2835_audio: card created with 4 channels Apr 15 16:17:06 whome kernel: [ 8.525521] bcm2835_audio bcm2835_audio: card created with 4 channels Apr 15 16:17:06 whome kernel: [ 8.527497] vc_sm_cma: module is from the staging directory, the quality is unknown, you have been warned. Apr 15 16:17:06 whome kernel: [ 8.529773] bcm2835_vc_sm_cma_probe: Videocore shared memory driver Apr 15 16:17:06 whome kernel: [ 8.529800] [vc_sm_connected_init]: start Apr 15 16:17:06 whome kernel: [ 8.563801] [vc_sm_connected_init]: installed successfully Apr 15 16:17:06 whome kernel: [ 8.590989] videodev: Linux video capture interface: v2.00 Apr 15 16:17:06 whome kernel: [ 8.642519] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned. Apr 15 16:17:06 whome kernel: [ 8.659713] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned. Apr 15 16:17:06 whome kernel: [ 8.662353] bcm2835_isp: module is from the staging directory, the quality is unknown, you have been warned. Apr 15 16:17:06 whome kernel: [ 8.673004] bcm2835_codec: module is from the staging directory, the quality is unknown, you have been warned. Apr 15 16:17:06 whome kernel: [ 8.700340] bcm2835-isp bcm2835-isp: Device node output[0] registered as /dev/video13 Apr 15 16:17:06 whome kernel: [ 8.711331] bcm2835-isp bcm2835-isp: Device node capture[0] registered as /dev/video14 Apr 15 16:17:06 whome kernel: [ 8.717865] bcm2835_v4l2: module is from the staging directory, the quality is unknown, you have been warned. Apr 15 16:17:06 whome kernel: [ 8.732122] bcm2835-isp bcm2835-isp: Device node capture[1] registered as /dev/video15 Apr 15 16:17:06 whome kernel: [ 8.741645] bcm2835-isp bcm2835-isp: Device node stats[2] registered as /dev/video16 Apr 15 16:17:06 whome kernel: [ 8.741994] bcm2835-isp bcm2835-isp: Register output node 0 with media controller Apr 15 16:17:06 whome kernel: [ 8.742030] bcm2835-isp bcm2835-isp: Register capture node 1 with media controller Apr 15 16:17:06 whome kernel: [ 8.742056] bcm2835-isp bcm2835-isp: Register capture node 2 with media controller Apr 15 16:17:06 whome kernel: [ 8.742114] bcm2835-isp bcm2835-isp: Register capture node 3 with media controller Apr 15 16:17:06 whome kernel: [ 8.746199] bcm2835-isp bcm2835-isp: Loaded V4L2 bcm2835-isp Apr 15 16:17:06 whome kernel: [ 8.787872] [drm] Initialized v3d 1.0.0 20180419 for fec00000.v3d on minor 0 Apr 15 16:17:06 whome kernel: [ 8.815075] bcm2835-codec bcm2835-codec: Device registered as /dev/video10 Apr 15 16:17:06 whome kernel: [ 8.815137] bcm2835-codec bcm2835-codec: Loaded V4L2 decode Apr 15 16:17:06 whome kernel: [ 8.825070] bcm2835-codec bcm2835-codec: Device registered as /dev/video11 Apr 15 16:17:06 whome kernel: [ 8.825119] bcm2835-codec bcm2835-codec: Loaded V4L2 encode Apr 15 16:17:06 whome kernel: [ 8.845696] vc4-drm gpu: bound fe600000.firmwarekms (ops vc4_fkms_ops [vc4]) Apr 15 16:17:06 whome kernel: [ 8.845726] checking generic (3e2fe000 7f8000) vs hw (0 ffffffffffffffff) Apr 15 16:17:06 whome kernel: [ 8.845743] fb0: switching to vc4drmfb from simple Apr 15 16:17:06 whome kernel: [ 8.845909] bcm2835-codec bcm2835-codec: Device registered as /dev/video12 Apr 15 16:17:06 whome kernel: [ 8.845954] bcm2835-codec bcm2835-codec: Loaded V4L2 isp Apr 15 16:17:06 whome kernel: [ 8.846545] Console: switching to colour dummy device 80x30 Apr 15 16:17:06 whome kernel: [ 8.873819] [drm] Initialized vc4 0.0.0 20140616 for gpu on minor 1 Apr 15 16:17:06 whome kernel: [ 8.899427] cfg80211: Loading compiled-in X.509 certificates for regulatory database Apr 15 16:17:06 whome kernel: [ 9.029595] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' Apr 15 16:17:06 whome kernel: [ 9.032332] sd 0:0:0:0: Attached scsi generic sg0 type 0 Apr 15 16:17:06 whome kernel: [ 9.087145] Console: switching to colour frame buffer device 240x67 Apr 15 16:17:06 whome kernel: [ 9.099033] brcmfmac: F1 signature read @0x18000000=0x15264345 Apr 15 16:17:06 whome kernel: [ 9.111849] vc4-drm gpu: [drm] fb0: vc4drmfb frame buffer device Apr 15 16:17:06 whome kernel: [ 9.123088] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6 Apr 15 16:17:06 whome kernel: [ 9.124185] usbcore: registered new interface driver brcmfmac Apr 15 16:17:06 whome kernel: [ 9.159380] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt failed with error -2 Apr 15 16:17:06 whome kernel: [ 9.400951] random: crng init done Apr 15 16:17:06 whome kernel: [ 9.400968] random: 7 urandom warning(s) missed due to ratelimiting Apr 15 16:17:06 whome kernel: [ 9.403086] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6 Apr 15 16:17:06 whome kernel: [ 9.414017] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Jan 4 2021 19:56:29 version 7.45.229 (617f1f5 CY) FWID 01-2dbd9d2e Apr 15 16:17:06 whome kernel: [ 9.550053] logitech-djreceiver 0003:046D:C52B.0005: hiddev96,hidraw2: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:01:00.0-1.1.3.4/input2 Apr 15 16:17:06 whome kernel: [ 9.691025] input: Logitech Wireless Device PID:400a Mouse as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.1/1-1.1.3/1-1.1.3.4/1-1.1.3.4:1.2/0003:046D:C52B.0005/0003:046D:400A.0006/input/input8 Apr 15 16:17:06 whome kernel: [ 9.691694] hid-generic 0003:046D:400A.0006: input,hidraw3: USB HID v1.11 Mouse [Logitech Wireless Device PID:400a] on usb-0000:01:00.0-1.1.3.4/input2:1 Apr 15 16:17:06 whome kernel: [ 9.695990] input: Logitech Wireless Device PID:4003 Keyboard as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.1/1-1.1.3/1-1.1.3.4/1-1.1.3.4:1.2/0003:046D:C52B.0005/0003:046D:4003.0007/input/input12 Apr 15 16:17:06 whome kernel: [ 9.701763] input: Logitech Wireless Device PID:4003 Consumer Control as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.1/1-1.1.3/1-1.1.3.4/1-1.1.3.4:1.2/0003:046D:C52B.0005/0003:046D:4003.0007/input/input13 Apr 15 16:17:06 whome kernel: [ 9.702186] input: Logitech Wireless Device PID:4003 System Control as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.1/1-1.1.3/1-1.1.3.4/1-1.1.3.4:1.2/0003:046D:C52B.0005/0003:046D:4003.0007/input/input14 Apr 15 16:17:06 whome kernel: [ 9.702655] hid-generic 0003:046D:4003.0007: input,hidraw4: USB HID v1.11 Keyboard [Logitech Wireless Device PID:4003] on usb-0000:01:00.0-1.1.3.4/input2:2 Apr 15 16:17:06 whome kernel: [ 10.517714] input: Logitech Wireless Device PID:400a as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.1/1-1.1.3/1-1.1.3.4/1-1.1.3.4:1.2/0003:046D:C52B.0005/0003:046D:400A.0006/input/input18 Apr 15 16:17:06 whome kernel: [ 10.519729] logitech-hidpp-device 0003:046D:400A.0006: input,hidraw3: USB HID v1.11 Mouse [Logitech Wireless Device PID:400a] on usb-0000:01:00.0-1.1.3.4/input2:1 Apr 15 16:17:06 whome kernel: [ 10.935588] input: Logitech K270 as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.1/1-1.1.3/1-1.1.3.4/1-1.1.3.4:1.2/0003:046D:C52B.0005/0003:046D:4003.0007/input/input19 Apr 15 16:17:06 whome kernel: [ 10.936905] logitech-hidpp-device 0003:046D:4003.0007: input,hidraw4: USB HID v1.11 Keyboard [Logitech K270] on usb-0000:01:00.0-1.1.3.4/input2:2 Apr 15 16:17:06 whome kernel: [ 11.906258] uart-pl011 fe201000.serial: no DMA platform data Apr 15 16:17:06 whome kernel: [ 12.142710] 8021q: 802.1Q VLAN Support v1.8 Apr 15 16:17:06 whome kernel: [ 12.713688] Adding 102396k swap on /var/swap. Priority:-2 extents:1 across:102396k FS Apr 15 16:17:07 whome kernel: [ 13.254551] bcmgenet fd580000.ethernet: configuring instance for external RGMII (RX delay) Apr 15 16:17:07 whome kernel: [ 13.254961] bcmgenet fd580000.ethernet eth0: Link is Down Apr 15 16:17:10 whome kernel: [ 16.393559] bcmgenet fd580000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off Apr 15 16:17:10 whome kernel: [ 16.393588] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Apr 15 16:17:12 whome kernel: [ 18.782512] Bluetooth: Core ver 2.22 Apr 15 16:17:12 whome kernel: [ 18.782572] NET: Registered protocol family 31 Apr 15 16:17:12 whome kernel: [ 18.782579] Bluetooth: HCI device and connection manager initialized Apr 15 16:17:12 whome kernel: [ 18.782596] Bluetooth: HCI socket layer initialized Apr 15 16:17:12 whome kernel: [ 18.782606] Bluetooth: L2CAP socket layer initialized Apr 15 16:17:12 whome kernel: [ 18.782621] Bluetooth: SCO socket layer initialized Apr 15 16:17:12 whome kernel: [ 18.795842] Bluetooth: HCI UART driver ver 2.3 Apr 15 16:17:12 whome kernel: [ 18.795856] Bluetooth: HCI UART protocol H4 registered Apr 15 16:17:12 whome kernel: [ 18.795927] Bluetooth: HCI UART protocol Three-wire (H5) registered Apr 15 16:17:12 whome kernel: [ 18.796133] Bluetooth: HCI UART protocol Broadcom registered Apr 15 16:17:13 whome kernel: [ 19.002855] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 Apr 15 16:17:13 whome kernel: [ 19.002863] Bluetooth: BNEP filters: protocol multicast Apr 15 16:17:13 whome kernel: [ 19.002876] Bluetooth: BNEP socket layer initialized Apr 15 17:26:28 whome kernel: [ 0.000000] Booting Linux on physical CPU 0x0
die sys.log hört am 15.04 00:00 auf
code_text
-
@uwe-waizmann sagte in Seltsame Abstürze RPI4:
Link is Up - 100Mbps/Full - flow control off
Wie ist der PI im Netzwerk angebunden?
Sicher das der einen kompletten restart macht und nicht nur die Netzwerkverbindung verliert?
Hängt der an einem 100Mbit Port ?
Was ist da noch alles direkt oder indirekt per Bluetooth angeschlossen?
-
@wendy2702
er hängt direkt mit Kabel an einer Fritzbox
Bluetooth ist gar nichts dran.
Sonst ist seit gestern über den Hub nur die Tastatur und die Maus angeschlossen.
Nein, er hängt dann komplett, kann mit Tastatur nichts mehr machen, nur noch Stecker ziehen.
Bei früheren Abstürzen konnte ich ihn noch an pingen, hab ich heute aber nicht probiert.
Per putty komme ich dann aber auch nicht mehr dran. -
@uwe-waizmann Und die FB hat nur 100Mbit Ports oder wird im Energiesparmode betrieben?
-
@wendy2702
Und es ist gerade wieder passiert
Kann jetzt aber sagen wann genau.
Beim Kaffee trinken schau ich mit der APP auf die VIS, alles ok, auch Refresh funktioniert.
Ich wecke meinen PC auf, wo iobroker und VIS im Browser offen sind, dann bleibt er stehen.
Ping geht noch, ssh keine Chance mehr, er steht da wie eingefroren.Der Port war im Green Mode mit 100Mbit/s, hab ihn jetzt umgeschaltet auf 1Gbit/s.
hier der Log vor dem Absturz.
Etwas seltsam finde ich den Sprung der Uhrzeit von 8:44 zurück auf 8:172021-04-16 09:11:08.079 error (3092) info.0 already running host.whome 2021-04-16 09:11:05.914 info instance system.adapter.info.0 started with pid 3092 host.whome 2021-04-16 09:11:03.695 info Restart adapter system.adapter.followthesun.0 because enabled host.whome 2021-04-16 09:11:03.694 error instance system.adapter.followthesun.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) followthesun.0 2021-04-16 09:11:03.070 warn (2739) Terminated (ADAPTER_ALREADY_RUNNING): Without reason followthesun.0 2021-04-16 09:11:03.066 error (2739) followthesun.0 already running host.whome 2021-04-16 09:11:01.906 info instance system.adapter.followthesun.0 started with pid 2739 host.whome 2021-04-16 09:10:59.818 info Restart adapter system.adapter.fb-checkpresence.0 because enabled host.whome 2021-04-16 09:10:59.817 error instance system.adapter.fb-checkpresence.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) fb-checkpresence.0 2021-04-16 09:10:59.245 warn (2354) Terminated (ADAPTER_ALREADY_RUNNING): Without reason fb-checkpresence.0 2021-04-16 09:10:59.243 error (2354) fb-checkpresence.0 already running host.whome 2021-04-16 08:17:34.535 info instance system.adapter.fb-checkpresence.0 started with pid 2354 host.whome 2021-04-16 08:17:32.241 info Restart adapter system.adapter.discovery.0 because enabled host.whome 2021-04-16 08:17:32.240 error instance system.adapter.discovery.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) discovery.0 2021-04-16 08:17:31.663 warn (2032) Terminated (ADAPTER_ALREADY_RUNNING): Without reason discovery.0 2021-04-16 08:17:31.660 error (2032) discovery.0 already running host.whome 2021-04-16 08:17:30.513 info instance system.adapter.discovery.0 started with pid 2032 host.whome 2021-04-16 08:17:28.574 info Restart adapter system.adapter.cloud.0 because enabled host.whome 2021-04-16 08:17:28.573 error instance system.adapter.cloud.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) cloud.0 2021-04-16 08:17:27.996 warn (1697) Terminated (ADAPTER_ALREADY_RUNNING): Without reason cloud.0 2021-04-16 08:17:27.993 error (1697) cloud.0 already running host.whome 2021-04-16 08:17:26.529 info instance system.adapter.cloud.0 started with pid 1697 host.whome 2021-04-16 08:17:24.403 info Restart adapter system.adapter.chromecast.0 because enabled host.whome 2021-04-16 08:17:24.402 error instance system.adapter.chromecast.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) host.whome 2021-04-16 08:17:24.402 error Caught by controller[0]: at processTicksAndRejections (internal/process/task_queues.js:97:5) host.whome 2021-04-16 08:17:24.402 error Caught by controller[0]: at Timeout._onTimeout (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:352:25) host.whome 2021-04-16 08:17:24.401 error Caught by controller[0]: at process.exit (internal/process/per_thread.js:168:15) host.whome 2021-04-16 08:17:24.401 error Caught by controller[0]: at process.emit (events.js:314:20) host.whome 2021-04-16 08:17:24.400 error Caught by controller[0]: at Object.onceWrapper (events.js:421:26) host.whome 2021-04-16 08:17:24.400 error Caught by controller[0]: at process.stop (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:8620:22) host.whome 2021-04-16 08:17:24.400 error Caught by controller[0]: at Adapter.emit (events.js:314:20) host.whome 2021-04-16 08:17:24.399 error Caught by controller[0]: at Adapter.unload (/opt/iobroker/node_modules/iobroker.chromecast/main.js:79:19) host.whome 2021-04-16 08:17:24.399 error Caught by controller[0]: TypeError: Cannot read property 'info' of undefined chromecast.0 2021-04-16 08:17:23.756 warn (1338) Terminated (ADAPTER_ALREADY_RUNNING): Without reason chromecast.0 2021-04-16 08:17:23.754 error (1338) chromecast.0 already running host.whome 2021-04-16 08:17:23.464 info Restart adapter system.adapter.backitup.0 because enabled host.whome 2021-04-16 08:17:23.463 error instance system.adapter.backitup.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) backitup.0 2021-04-16 08:17:22.811 warn (986) Terminated (ADAPTER_ALREADY_RUNNING): Without reason backitup.0 2021-04-16 08:17:22.807 error (986) backitup.0 already running host.whome 2021-04-16 08:17:22.444 info instance system.adapter.chromecast.0 started with pid 1338 host.whome 2021-04-16 08:17:18.432 info instance system.adapter.backitup.0 started with pid 986 host.whome 2021-04-16 08:17:16.950 info Restart adapter system.adapter.admin.0 because enabled host.whome 2021-04-16 08:17:16.949 error instance system.adapter.admin.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) admin.0 2021-04-16 08:17:16.350 warn (799) Terminated (ADAPTER_ALREADY_RUNNING): Without reason admin.0 2021-04-16 08:17:16.347 error (799) admin.0 already running host.whome 2021-04-16 08:17:14.531 info instance system.adapter.admin.0 started with pid 799 host.whome 2021-04-16 08:17:14.412 info starting 19 instances host.whome 2021-04-16 08:17:14.353 info 25 instances found host.whome 2021-04-16 08:17:13.756 info added notifications configuration of host host.whome 2021-04-16 08:17:13.702 info connected to Objects and States host.whome-Server 2021-04-16 08:17:13.563 error Cannot load /opt/iobroker/iobroker-data/states.json: /opt/iobroker/iobroker-data/states.json: Unexpected end of JSON input. Try last Backup! host.whome 2021-04-16 08:17:13.068 info ip addresses: fe80::d8:6431:90b3:eeab host.whome 2021-04-16 08:17:13.067 info hostname: whome, node: v12.22.1 host.whome 2021-04-16 08:17:13.066 info Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker web.0 2021-04-16 08:44:55.078 info web.0 2021-04-16 08:44:55.078 info (7199) <==Disconnect system.user.admin from ::ffff:192.168.1.30 web.0 2021-04-16 08:44:41.152 info (7199) ==>Connected system.user.admin from ::ffff:192.168.1.30 web.0 2021-04-16 08:44:41.019 info (7199) ==>Connected system.user.admin from ::ffff:192.168.1.30 web.0 2021-04-16 08:42:25.371 info (7199) <==Disconnect system.user.admin from ::ffff:192.168.1.30 vis.0 web.0 2021-04-16 08:42:25.200 info (7199) ==>Connected system.user.admin from ::ffff:192.168.1.30 web.0 2021-04-16 08:42:25.078 info (7199) ==>Connected system.user.admin from ::ffff:192.168.1.30 web.0 2021-04-16 08:37:19.727 info (7199) <==Disconnect system.user.admin from ::ffff:192.168.1.30 vis.0 web.0 2021-04-16 08:32:53.878 info (7199) ==>Connected system.user.admin from ::ffff:192.168.1.30
-
@uwe-waizmann Blöde Frage: dein Rechner und PI haben nicht zufällig dieselbe IP Adresse ?
-
@wendy2702 sagte in Seltsame Abstürze RPI4:
@uwe-waizmann Blöde Frage: dein Rechner und PI haben nicht zufällig dieselbe IP Adresse ?
Haben alle die 127.0.0.1!
-
@thomas-braun said in Seltsame Abstürze RPI4:
@wendy2702 sagte in Seltsame Abstürze RPI4:
@uwe-waizmann Blöde Frage: dein Rechner und PI haben nicht zufällig dieselbe IP Adresse ?
Haben alle die 127.0.0.1!
hey, die hab ich auch
-
@oliverio Gib die zurück! Die ist mir!
-
@thomas-braun said in Seltsame Abstürze RPI4:
@oliverio Gib die zurück! Die ist mir!
musst einen Antrag bei https://www.iana.org/ stellen.
-
@thomas-braun Menno....
Dachte immer das wäre meine
-
@wendy2702
Nein, haben alle zugewiesene IP, sonst würd ich bei den vielen Geräten nicht mehr durchblicken