Die Hardware scheint so selten genutzt zu sein das bisher nur von dir eine Problemmeldung kam.
Vielleicht ein Ticket dazu in Github aufmachen?
Oder läufts inzwischen?
Moderatoren: jmaus, Co-Administratoren
Die Hardware scheint so selten genutzt zu sein das bisher nur von dir eine Problemmeldung kam.
Also wirkliche Auswirkungen kann ich aktuell keine feststellen, die Meldung tritt allerdings alle paar Stunden (kein erkennbarer Intervall) auf
Code: Alles auswählen
Dec 4 08:11:29 homematic kern.err kernel: [74892.080783] ==================================================================
Dec 4 08:11:29 homematic kern.err kernel: [74892.080808] BUG: KFENCE: memory corruption in free_async+0x1d8/0x1e0
Dec 4 08:11:29 homematic kern.err kernel: [74892.080808]
Dec 4 08:11:29 homematic kern.err kernel: [74892.080829] Corrupted memory at 0x0000000041480cc8 [ ! . . . . . . . . . . . . . . . ] (in kfence-#72):
Dec 4 08:11:29 homematic kern.warn kernel: [74892.080921] free_async+0x1d8/0x1e0
Dec 4 08:11:29 homematic kern.warn kernel: [74892.080936] usbdev_ioctl+0x138/0x1c40
Dec 4 08:11:29 homematic kern.warn kernel: [74892.080950] __arm64_sys_ioctl+0xd0/0x130
Dec 4 08:11:29 homematic kern.warn kernel: [74892.080971] invoke_syscall+0x7c/0x130
Dec 4 08:11:29 homematic kern.warn kernel: [74892.080991] el0_svc_common.constprop.0+0x6c/0x160
Dec 4 08:11:29 homematic kern.warn kernel: [74892.081010] do_el0_svc+0x38/0x120
Dec 4 08:11:29 homematic kern.warn kernel: [74892.081028] el0_svc+0x34/0xc0
Dec 4 08:11:29 homematic kern.warn kernel: [74892.081046] el0t_64_sync_handler+0x11c/0x150
Dec 4 08:11:29 homematic kern.warn kernel: [74892.081064] el0t_64_sync+0x198/0x19c
Dec 4 08:11:29 homematic kern.err kernel: [74892.081078]
Dec 4 08:11:29 homematic kern.warn kernel: [74892.081083] kfence-#72: 0x00000000c9de991e-0x00000000a43cc636, size=7, cache=kmalloc-128
Dec 4 08:11:29 homematic kern.warn kernel: [74892.081083]
Dec 4 08:11:29 homematic kern.warn kernel: [74892.081098] allocated by task 1634 on cpu 0 at 74892.078656s:
Dec 4 08:11:29 homematic kern.warn kernel: [74892.081124] proc_do_submiturb+0xdb0/0x1000
Dec 4 08:11:29 homematic kern.warn kernel: [74892.081138] usbdev_ioctl+0x12c0/0x1c40
Dec 4 08:11:29 homematic kern.warn kernel: [74892.081151] __arm64_sys_ioctl+0xd0/0x130
Dec 4 08:11:29 homematic kern.warn kernel: [74892.081170] invoke_syscall+0x7c/0x130
Dec 4 08:11:29 homematic kern.warn kernel: [74892.081187] el0_svc_common.constprop.0+0x6c/0x160
Dec 4 08:11:29 homematic kern.warn kernel: [74892.081205] do_el0_svc+0x38/0x120
Dec 4 08:11:29 homematic kern.warn kernel: [74892.081222] el0_svc+0x34/0xc0
Dec 4 08:11:29 homematic kern.warn kernel: [74892.081238] el0t_64_sync_handler+0x11c/0x150
Dec 4 08:11:29 homematic kern.warn kernel: [74892.081255] el0t_64_sync+0x198/0x19c
Dec 4 08:11:29 homematic kern.warn kernel: [74892.081267]
Dec 4 08:11:29 homematic kern.warn kernel: [74892.081272] freed by task 1634 on cpu 0 at 74892.080736s:
Dec 4 08:11:29 homematic kern.warn kernel: [74892.081304] free_async+0x1d8/0x1e0
Dec 4 08:11:29 homematic kern.warn kernel: [74892.081317] usbdev_ioctl+0x138/0x1c40
Dec 4 08:11:29 homematic kern.warn kernel: [74892.081329] __arm64_sys_ioctl+0xd0/0x130
Dec 4 08:11:29 homematic kern.warn kernel: [74892.081348] invoke_syscall+0x7c/0x130
Dec 4 08:11:29 homematic kern.warn kernel: [74892.081366] el0_svc_common.constprop.0+0x6c/0x160
Dec 4 08:11:29 homematic kern.warn kernel: [74892.081384] do_el0_svc+0x38/0x120
Dec 4 08:11:29 homematic kern.warn kernel: [74892.081400] el0_svc+0x34/0xc0
Dec 4 08:11:29 homematic kern.warn kernel: [74892.081416] el0t_64_sync_handler+0x11c/0x150
Dec 4 08:11:29 homematic kern.warn kernel: [74892.081433] el0t_64_sync+0x198/0x19c
Dec 4 08:11:29 homematic kern.err kernel: [74892.081445]
Dec 4 08:11:29 homematic kern.err kernel: [74892.081452] CPU: 0 PID: 1634 Comm: usbhid-ups Tainted: G C O 6.1.63 #1
Dec 4 08:11:29 homematic kern.err kernel: [74892.081468] Hardware name: Raspberry Pi 3 Model B Rev 1.2 (DT)
Dec 4 08:11:29 homematic kern.err kernel: [74892.081476] ==================================================================
Dec 4 08:58:32 homematic kern.err kernel: [77714.342839] ==================================================================
Dec 4 08:58:32 homematic kern.err kernel: [77714.342859] BUG: KFENCE: memory corruption in free_async+0x1d8/0x1e0
Dec 4 08:58:32 homematic kern.err kernel: [77714.342859]
Dec 4 08:58:32 homematic kern.err kernel: [77714.342875] Corrupted memory at 0x00000000a544051b [ ! ! ! . . . . . . . . . . . . . ] (in kfence-#20):
Dec 4 08:58:32 homematic kern.warn kernel: [77714.342941] free_async+0x1d8/0x1e0
Dec 4 08:58:32 homematic kern.warn kernel: [77714.342951] usbdev_ioctl+0x138/0x1c40
Dec 4 08:58:32 homematic kern.warn kernel: [77714.342961] __arm64_sys_ioctl+0xd0/0x130
Dec 4 08:58:32 homematic kern.warn kernel: [77714.342977] invoke_syscall+0x7c/0x130
Dec 4 08:58:32 homematic kern.warn kernel: [77714.342991] el0_svc_common.constprop.0+0x6c/0x160
Dec 4 08:58:32 homematic kern.warn kernel: [77714.343005] do_el0_svc+0x38/0x120
Dec 4 08:58:32 homematic kern.warn kernel: [77714.343017] el0_svc+0x34/0xc0
Dec 4 08:58:32 homematic kern.warn kernel: [77714.343030] el0t_64_sync_handler+0x11c/0x150
Dec 4 08:58:32 homematic kern.warn kernel: [77714.343042] el0t_64_sync+0x198/0x19c
Dec 4 08:58:32 homematic kern.err kernel: [77714.343052]
Dec 4 08:58:32 homematic kern.warn kernel: [77714.343057] kfence-#20: 0x00000000bba2bf8b-0x0000000031d05650, size=5, cache=kmalloc-128
Dec 4 08:58:32 homematic kern.warn kernel: [77714.343057]
Dec 4 08:58:32 homematic kern.warn kernel: [77714.343067] allocated by task 1634 on cpu 2 at 77714.147012s:
Dec 4 08:58:32 homematic kern.warn kernel: [77714.343086] proc_do_submiturb+0xdb0/0x1000
Dec 4 08:58:32 homematic kern.warn kernel: [77714.343096] usbdev_ioctl+0x12c0/0x1c40
Dec 4 08:58:32 homematic kern.warn kernel: [77714.343105] __arm64_sys_ioctl+0xd0/0x130
Dec 4 08:58:32 homematic kern.warn kernel: [77714.343118] invoke_syscall+0x7c/0x130
Dec 4 08:58:32 homematic kern.warn kernel: [77714.343130] el0_svc_common.constprop.0+0x6c/0x160
Dec 4 08:58:32 homematic kern.warn kernel: [77714.343143] do_el0_svc+0x38/0x120
Dec 4 08:58:32 homematic kern.warn kernel: [77714.343155] el0_svc+0x34/0xc0
Dec 4 08:58:32 homematic kern.warn kernel: [77714.343166] el0t_64_sync_handler+0x11c/0x150
Dec 4 08:58:32 homematic kern.warn kernel: [77714.343178] el0t_64_sync+0x198/0x19c
Dec 4 08:58:32 homematic kern.warn kernel: [77714.343187]
Dec 4 08:58:32 homematic kern.warn kernel: [77714.343191] freed by task 1634 on cpu 2 at 77714.342802s:
Dec 4 08:58:32 homematic kern.warn kernel: [77714.343213] free_async+0x1d8/0x1e0
Dec 4 08:58:32 homematic kern.warn kernel: [77714.343222] usbdev_ioctl+0x138/0x1c40
Dec 4 08:58:32 homematic kern.warn kernel: [77714.343231] __arm64_sys_ioctl+0xd0/0x130
Dec 4 08:58:32 homematic kern.warn kernel: [77714.343244] invoke_syscall+0x7c/0x130
Dec 4 08:58:32 homematic kern.warn kernel: [77714.343256] el0_svc_common.constprop.0+0x6c/0x160
Dec 4 08:58:32 homematic kern.warn kernel: [77714.343269] do_el0_svc+0x38/0x120
Dec 4 08:58:32 homematic kern.warn kernel: [77714.343280] el0_svc+0x34/0xc0
Dec 4 08:58:32 homematic kern.warn kernel: [77714.343291] el0t_64_sync_handler+0x11c/0x150
Dec 4 08:58:32 homematic kern.warn kernel: [77714.343303] el0t_64_sync+0x198/0x19c
Dec 4 08:58:32 homematic kern.err kernel: [77714.343311]
Dec 4 08:58:32 homematic kern.err kernel: [77714.343317] CPU: 2 PID: 1634 Comm: usbhid-ups Tainted: G B C O 6.1.63 #1
Dec 4 08:58:32 homematic kern.err kernel: [77714.343328] Hardware name: Raspberry Pi 3 Model B Rev 1.2 (DT)
Dec 4 08:58:32 homematic kern.err kernel: [77714.343335] ==================================================================
D
Und wenn du den gesamten NUT Dienst mal abschaltest? Verschwindet dann der Fehler?
Dann ist dein Grundkonzept falsch. Essentielle Dinge wie eine Heizung im Winter dürfen nicht vom Vorhandensein einer Zentralensteuerung abhängig sein. Du solltest immer noch eine manuelle Möglichkeit für solche Notfälle vorsehen (Thermostate kannst du doch auch von Hand passend einstellen)...
der konnte noch nie etwas. Bei HMIP hat er leider auch nichts dazugelernt.
Du wirst ein CS Problem haben.
Ich lese das so das die Fehlermeldungen in den 12h ohne angesteckte USV nicht kamen sondern nur der upsmon (verständlicherweise) gemeckert hat.
Code: Alles auswählen
[brics]
desc = "CP BRICKs LCD 1000"
# driver.name
driver = "usbhid-ups"
# driver.parameter.port
port = "auto"
# driver.parameter.mode
synchronous = yes
# driver.parameter.pollintervall
pollinterval = 5
Oder ohne Meldung aufgegeben ...
ErledigtVielleicht ein Ticket dazu in Github aufmachen?
Nee, habe Samstag Nachmittag mit div. Versuchen (inkl. neuer Hardware) verbracht und seither läuft der alte Stand wieder.Oder läufts inzwischen?