kernel panic foutmelding

Pagina: 1
Acties:

Vraag


  • l.vaneijck
  • Registratie: Februari 2015
  • Laatst online: 17:12
Mijn vraag
nadat ik updates geinstalleerd had kreeg ik de fout in de blijlage, normaal krijg ik na updaten de melding: opnieuw opstarten om update af te ronden, nu niet volgens mij, moet ik hier iets mee? als het een fout in de update is die nu klaar is dan wil ik dat graag weten, als er iets fout zit ook,

Relevante software en hardware die ik gebruik
linux zorin 18.1 core

dell vostro 3559

Wat ik al gevonden of geprobeerd heb
ik heb gegoogled naar kernel fouten, maar kreeg alleen maar meldingen over oude fouten, misschien zoek ik niet goed?Afbeeldingslocatie: https://tweakers.net/i/bXHEtNL5iKqaonVUocZIdUNIrBQ=/800x/filters:strip_icc():strip_exif()/f/image/cwbVOBdnKsJg5DCOIOLQkHkW.jpg?f=fotoalbum_large

[ Voor 25% gewijzigd door l.vaneijck op 22-10-2026 16:24 ]

Beste antwoord (via l.vaneijck op 22-10-2026 17:07)


  • leander-s
  • Registratie: November 2011
  • Laatst online: 17:11
Aangezien dit de logs zijn die je terugkrijgt met -1 geeft het aan dat je logs tijdens de kernel panic niet weggeschreven zijn of corrupt zijn geraakt.

Werkt het handmatig updaten nog correct via:
code:
1
sudo apt update && sudo apt full-upgrade

Alle reacties


  • leander-s
  • Registratie: November 2011
  • Laatst online: 17:11
@l.vaneijck, En welke fout/ kernelpanic krijg je dan te zien.

Heb je een screenshot/foto van het scherm op dat moment?

  • l.vaneijck
  • Registratie: Februari 2015
  • Laatst online: 17:12
yes, net bijgevoegd, alles lijkt het nu weer normaal te doen

[ Voor 51% gewijzigd door l.vaneijck op 22-10-2026 16:27 ]


  • l.vaneijck
  • Registratie: Februari 2015
  • Laatst online: 17:12
weet niet of jullie er iets aan hebben maar ik post hier een log van de update:

laurens@laurens-Vostro-3559:~$ journalctl -u apt-daily.service

apr 01 22:54:37 laurens-Vostro-3559 systemd[1]: Starting apt-daily.service - Da>

apr 01 22:54:48 laurens-Vostro-3559 systemd[1]: apt-daily.service: Deactivated >

apr 01 22:54:48 laurens-Vostro-3559 systemd[1]: Finished apt-daily.service - Da>

apr 01 22:54:48 laurens-Vostro-3559 systemd[1]: apt-daily.service: Consumed 10.>

-- Boot d0e008c285ce411c9f64b7fce8145533 --

apr 02 16:27:59 laurens-Vostro-3559 systemd[1]: Starting apt-daily.service - Da>

apr 02 16:28:13 laurens-Vostro-3559 systemd[1]: apt-daily.service: Deactivated >

apr 02 16:28:13 laurens-Vostro-3559 systemd[1]: Finished apt-daily.service - Da>

apr 02 16:28:13 laurens-Vostro-3559 systemd[1]: apt-daily.service: Consumed 13.>

-- Boot b0a5f95cff334fecbd6a4119f6f669b9 --

apr 03 10:36:44 laurens-Vostro-3559 systemd[1]: Starting apt-daily.service - Da>

apr 03 10:36:52 laurens-Vostro-3559 systemd[1]: apt-daily.service: Deactivated >

apr 03 10:36:52 laurens-Vostro-3559 systemd[1]: Finished apt-daily.service - Da>

apr 03 10:36:52 laurens-Vostro-3559 systemd[1]: apt-daily.service: Consumed 7.6>

-- Boot 54086bac91d5401f9ca2d60dcdf62e41 --

apr 04 15:43:20 laurens-Vostro-3559 systemd[1]: Starting apt-daily.service - Da>

apr 04 15:43:32 laurens-Vostro-3559 systemd[1]: apt-daily.service: Deactivated >

apr 04 15:43:32 laurens-Vostro-3559 systemd[1]: Finished apt-daily.service - Da>

apr 04 15:43:32 laurens-Vostro-3559 systemd[1]: apt-daily.service: Consumed 12.>

apr 04 22:31:09 laurens-Vostro-3559 systemd[1]: Starting apt-daily.service - Da>

apr 04 22:31:15 laurens-Vostro-3559 systemd[1]: apt-daily.service: Deactivated >

apr 04 22:31:15 laurens-Vostro-3559 systemd[1]: Finished apt-daily.service - Da>

-- Boot 365020c0824d413c9b77615d36a205af --

lines 1-23...skipping...

apr 01 22:54:37 laurens-Vostro-3559 systemd[1]: Starting apt-daily.service - Daily apt download activities...

apr 01 22:54:48 laurens-Vostro-3559 systemd[1]: apt-daily.service: Deactivated successfully.

apr 01 22:54:48 laurens-Vostro-3559 systemd[1]: Finished apt-daily.service - Daily apt download activities.

apr 01 22:54:48 laurens-Vostro-3559 systemd[1]: apt-daily.service: Consumed 10.179s CPU time.

-- Boot d0e008c285ce411c9f64b7fce8145533 --

apr 02 16:27:59 laurens-Vostro-3559 systemd[1]: Starting apt-daily.service - Daily apt download activities...

apr 02 16:28:13 laurens-Vostro-3559 systemd[1]: apt-daily.service: Deactivated successfully.

apr 02 16:28:13 laurens-Vostro-3559 systemd[1]: Finished apt-daily.service - Daily apt download activities.

apr 02 16:28:13 laurens-Vostro-3559 systemd[1]: apt-daily.service: Consumed 13.793s CPU time.

-- Boot b0a5f95cff334fecbd6a4119f6f669b9 --

apr 03 10:36:44 laurens-Vostro-3559 systemd[1]: Starting apt-daily.service - Daily apt download activities...

apr 03 10:36:52 laurens-Vostro-3559 systemd[1]: apt-daily.service: Deactivated successfully.

apr 03 10:36:52 laurens-Vostro-3559 systemd[1]: Finished apt-daily.service - Daily apt download activities.

apr 03 10:36:52 laurens-Vostro-3559 systemd[1]: apt-daily.service: Consumed 7.697s CPU time.

-- Boot 54086bac91d5401f9ca2d60dcdf62e41 --

apr 04 15:43:20 laurens-Vostro-3559 systemd[1]: Starting apt-daily.service - Daily apt download activities...

apr 04 15:43:32 laurens-Vostro-3559 systemd[1]: apt-daily.service: Deactivated successfully.

apr 04 15:43:32 laurens-Vostro-3559 systemd[1]: Finished apt-daily.service - Daily apt download activities.

apr 04 15:43:32 laurens-Vostro-3559 systemd[1]: apt-daily.service: Consumed 12.494s CPU time.

apr 04 22:31:09 laurens-Vostro-3559 systemd[1]: Starting apt-daily.service - Daily apt download activities...

apr 04 22:31:15 laurens-Vostro-3559 systemd[1]: apt-daily.service: Deactivated successfully.

apr 04 22:31:15 laurens-Vostro-3559 systemd[1]: Finished apt-daily.service - Daily apt download activities.

-- Boot 365020c0824d413c9b77615d36a205af --

apr 05 13:09:43 laurens-Vostro-3559 systemd[1]: Starting apt-daily.service - Daily apt download activities...

apr 05 13:09:55 laurens-Vostro-3559 systemd[1]: apt-daily.service: Deactivated successfully.

apr 05 13:09:55 laurens-Vostro-3559 systemd[1]: Finished apt-daily.service - Daily apt download activities.

apr 05 13:09:55 laurens-Vostro-3559 systemd[1]: apt-daily.service: Consumed 12.186s CPU time.

apr 05 18:46:39 laurens-Vostro-3559 systemd[1]: Starting apt-daily.service - Daily apt download activities...

apr 05 18:46:40 laurens-Vostro-3559 systemd[1]: apt-daily.service: Deactivated successfully.

apr 05 18:46:40 laurens-Vostro-3559 systemd[1]: Finished apt-daily.service - Daily apt download activities.

apr 06 11:28:43 laurens-Vostro-3559 systemd[1]: Starting apt-daily.service - Daily apt download activities...

apr 06 11:28:48 laurens-Vostro-3559 systemd[1]: apt-daily.service: Deactivated successfully.

apr 06 11:28:48 laurens-Vostro-3559 systemd[1]: Finished apt-daily.service - Daily apt download activities.

apr 06 11:28:48 laurens-Vostro-3559 systemd[1]: apt-daily.service: Consumed 5.723s CPU time.

-- Boot f3d2e7f6471d47c8a6fc87f71893e2fa --

apr 07 08:23:41 laurens-Vostro-3559 systemd[1]: Starting apt-daily.service - Daily apt download activities...

apr 07 08:23:48 laurens-Vostro-3559 systemd[1]: apt-daily.service: Deactivated successfully.

apr 07 08:23:48 laurens-Vostro-3559 systemd[1]: Finished apt-daily.service - Daily apt download activities.

apr 07 08:23:48 laurens-Vostro-3559 systemd[1]: apt-daily.service: Consumed 7.622s CPU time.

apr 08 07:17:16 laurens-Vostro-3559 systemd[1]: Starting apt-daily.service - Daily apt download activities...

apr 08 07:17:33 laurens-Vostro-3559 systemd[1]: apt-daily.service: Deactivated successfully.

lines 1-41

apr 01 22:54:37 laurens-Vostro-3559 systemd[1]: Starting apt-daily.service - Daily apt download activities...

apr 01 22:54:48 laurens-Vostro-3559 systemd[1]: apt-daily.service: Deactivated successfully.

apr 01 22:54:48 laurens-Vostro-3559 systemd[1]: Finished apt-daily.service - Daily apt download activities.

apr 01 22:54:48 laurens-Vostro-3559 systemd[1]: apt-daily.service: Consumed 10.179s CPU time.

-- Boot d0e008c285ce411c9f64b7fce8145533 --

apr 02 16:27:59 laurens-Vostro-3559 systemd[1]: Starting apt-daily.service - Daily apt download activities...

apr 02 16:28:13 laurens-Vostro-3559 systemd[1]: apt-daily.service: Deactivated successfully.

apr 02 16:28:13 laurens-Vostro-3559 systemd[1]: Finished apt-daily.service - Daily apt download activities.

apr 02 16:28:13 laurens-Vostro-3559 systemd[1]: apt-daily.service: Consumed 13.793s CPU time.

-- Boot b0a5f95cff334fecbd6a4119f6f669b9 --

apr 03 10:36:44 laurens-Vostro-3559 systemd[1]: Starting apt-daily.service - Daily apt download activities...

apr 03 10:36:52 laurens-Vostro-3559 systemd[1]: apt-daily.service: Deactivated successfully.

apr 03 10:36:52 laurens-Vostro-3559 systemd[1]: Finished apt-daily.service - Daily apt download activities.

apr 03 10:36:52 laurens-Vostro-3559 systemd[1]: apt-daily.service: Consumed 7.697s CPU time.

-- Boot 54086bac91d5401f9ca2d60dcdf62e41 --

apr 04 15:43:20 laurens-Vostro-3559 systemd[1]: Starting apt-daily.service - Daily apt download activities...

apr 04 15:43:32 laurens-Vostro-3559 systemd[1]: apt-daily.service: Deactivated successfully.

apr 04 15:43:32 laurens-Vostro-3559 systemd[1]: Finished apt-daily.service - Daily apt download activities.

apr 04 15:43:32 laurens-Vostro-3559 systemd[1]: apt-daily.service: Consumed 12.494s CPU time.

apr 04 22:31:09 laurens-Vostro-3559 systemd[1]: Starting apt-daily.service - Daily apt download activities...

apr 04 22:31:15 laurens-Vostro-3559 systemd[1]: apt-daily.service: Deactivated successfully.

apr 04 22:31:15 laurens-Vostro-3559 systemd[1]: Finished apt-daily.service - Daily apt download activities.

-- Boot 365020c0824d413c9b77615d36a205af --

apr 05 13:09:43 laurens-Vostro-3559 systemd[1]: Starting apt-daily.service - Daily apt download activities...

apr 05 13:09:55 laurens-Vostro-3559 systemd[1]: apt-daily.service: Deactivated successfully.

apr 05 13:09:55 laurens-Vostro-3559 systemd[1]: Finished apt-daily.service - Daily apt download activities.

apr 05 13:09:55 laurens-Vostro-3559 systemd[1]: apt-daily.service: Consumed 12.186s CPU time.

apr 05 18:46:39 laurens-Vostro-3559 systemd[1]: Starting apt-daily.service - Daily apt download activities...

apr 05 18:46:40 laurens-Vostro-3559 systemd[1]: apt-daily.service: Deactivated successfully.

apr 05 18:46:40 laurens-Vostro-3559 systemd[1]: Finished apt-daily.service - Daily apt download activities.

apr 06 11:28:43 laurens-Vostro-3559 systemd[1]: Starting apt-daily.service - Daily apt download activities...

apr 06 11:28:48 laurens-Vostro-3559 systemd[1]: apt-daily.service: Deactivated successfully.

apr 06 11:28:48 laurens-Vostro-3559 systemd[1]: Finished apt-daily.service - Daily apt download activities.

apr 06 11:28:48 laurens-Vostro-3559 systemd[1]: apt-daily.service: Consumed 5.723s CPU time.

-- Boot f3d2e7f6471d47c8a6fc87f71893e2fa --

apr 07 08:23:41 laurens-Vostro-3559 systemd[1]: Starting apt-daily.service - Daily apt download activities...

  • leander-s
  • Registratie: November 2011
  • Laatst online: 17:11
Je kan proberen om de logs te bekijken van de de boot waarin de kernel panic optreed. De volledige trace geeft namelijk meer informatie dan op je scherm van jouw computer.

Als het de vorige boot was kun je gebruik maken van
code:
1
sudo journalctl -b -1
Of de -1 vervangen door -2 als het de boot daarvoor was

[ Voor 5% gewijzigd door leander-s op 22-10-2026 16:44 ]


  • l.vaneijck
  • Registratie: Februari 2015
  • Laatst online: 17:12
wat ik nou niet snap is dat hier 18 oktober staat terwijl ik toch vanochtend een update had:

laurens@laurens-Vostro-3559:~$ sudo journalctl -b -1

[sudo] password for laurens:

okt 18 23:05:20 laurens-Vostro-3559 kernel: Linux version 7.0.0-38-generic (bui>

okt 18 23:05:20 laurens-Vostro-3559 kernel: Command line: BOOT_IMAGE=/vmlinuz-7>

okt 18 23:05:20 laurens-Vostro-3559 kernel: KERNEL supported cpus:

okt 18 23:05:20 laurens-Vostro-3559 kernel: Intel GenuineIntel

okt 18 23:05:20 laurens-Vostro-3559 kernel: AMD AuthenticAMD

okt 18 23:05:20 laurens-Vostro-3559 kernel: Hygon HygonGenuine

okt 18 23:05:20 laurens-Vostro-3559 kernel: Centaur CentaurHauls

okt 18 23:05:20 laurens-Vostro-3559 kernel: zhaoxin Shanghai

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-provided physical RAM map:

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [mem 0x0000000000000000->

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [mem 0x0000000000058000->

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [mem 0x0000000000059000->

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [mem 0x000000000009d000->

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [gap 0x00000000000a0000->

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [mem 0x0000000000100000->

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [mem 0x000000007a3b3000->

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [mem 0x000000007a3b4000->

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [mem 0x000000007a3de000->

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [mem 0x000000007a440000->

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [mem 0x000000007abf0000->

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [mem 0x0000000086c07000->

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [mem 0x0000000087640000->

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [mem 0x0000000087f99000->

lines 1-23...skipping...

okt 18 23:05:20 laurens-Vostro-3559 kernel: Linux version 7.0.0-38-generic (buildd@lcy02-amd64-063) (x86_64-linux-gnu-gcc-13 (Ubuntu 13.3.0-6ubuntu2~24.04.1) 13.3.0, GNU ld (GNU B>

okt 18 23:05:20 laurens-Vostro-3559 kernel: Command line: BOOT_IMAGE=/vmlinuz-7.0.0-38-generic root=/dev/mapper/vgzorin-root ro quiet splash vt.handoff=7

okt 18 23:05:20 laurens-Vostro-3559 kernel: KERNEL supported cpus:

okt 18 23:05:20 laurens-Vostro-3559 kernel: Intel GenuineIntel

okt 18 23:05:20 laurens-Vostro-3559 kernel: AMD AuthenticAMD

okt 18 23:05:20 laurens-Vostro-3559 kernel: Hygon HygonGenuine

okt 18 23:05:20 laurens-Vostro-3559 kernel: Centaur CentaurHauls

okt 18 23:05:20 laurens-Vostro-3559 kernel: zhaoxin Shanghai

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-provided physical RAM map:

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [mem 0x0000000000000000-0x0000000000057fff] System RAM

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [mem 0x0000000000058000-0x0000000000058fff] device reserved

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [mem 0x0000000000059000-0x000000000009cfff] System RAM

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [mem 0x000000000009d000-0x000000000009ffff] device reserved

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [gap 0x00000000000a0000-0x00000000000fffff]

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [mem 0x0000000000100000-0x000000007a3b2fff] System RAM

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [mem 0x000000007a3b3000-0x000000007a3b3fff] ACPI NVS

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [mem 0x000000007a3b4000-0x000000007a3ddfff] device reserved

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [mem 0x000000007a3de000-0x000000007a43ffff] System RAM

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [mem 0x000000007a440000-0x000000007abeffff] device reserved

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [mem 0x000000007abf0000-0x0000000086c06fff] System RAM

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [mem 0x0000000086c07000-0x000000008763ffff] device reserved

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [mem 0x0000000087640000-0x0000000087f98fff] ACPI NVS

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [mem 0x0000000087f99000-0x0000000087ffdfff] ACPI data

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [mem 0x0000000087ffe000-0x0000000087ffefff] System RAM

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [gap 0x0000000087fff000-0x0000000087ffffff]

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [mem 0x0000000088000000-0x00000000880fffff] device reserved

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [gap 0x0000000088100000-0x00000000dfffffff]

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] device reserved

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [gap 0x00000000f0000000-0x00000000fdffffff]

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010fff] device reserved

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [gap 0x00000000fe011000-0x00000000febfffff]

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] device reserved

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [gap 0x00000000fec01000-0x00000000fedfffff]

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] device reserved

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [gap 0x00000000fee01000-0x00000000feffffff]

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] device reserved

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [mem 0x0000000100000000-0x0000000472ffffff] System RAM

okt 18 23:05:20 laurens-Vostro-3559 kernel: NX (Execute Disable) protection: active

okt 18 23:05:20 laurens-Vostro-3559 kernel: APIC: Static calls initialized

okt 18 23:05:20 laurens-Vostro-3559 kernel: efi: EFI v2.4 by American Megatrends

okt 18 23:05:20 laurens-Vostro-3559 kernel: efi: ACPI=0x87fd6000 ACPI 2.0=0x87fd6000 SMBIOS=0xf0000 ESRT=0x86fe8598 MOKvar=0x87082000 INITRD=0x782ef818 TPMEventLog=0x87fd3018

lines 1-41

okt 18 23:05:20 laurens-Vostro-3559 kernel: Linux version 7.0.0-38-generic (buildd@lcy02-amd64-063) (x86_64-linux-gnu-gcc-13 (Ubuntu 13.3.0-6ubuntu2~24.04.1) 13.3.0, G>

okt 18 23:05:20 laurens-Vostro-3559 kernel: Command line: BOOT_IMAGE=/vmlinuz-7.0.0-38-generic root=/dev/mapper/vgzorin-root ro quiet splash vt.handoff=7

okt 18 23:05:20 laurens-Vostro-3559 kernel: KERNEL supported cpus:

okt 18 23:05:20 laurens-Vostro-3559 kernel: Intel GenuineIntel

okt 18 23:05:20 laurens-Vostro-3559 kernel: AMD AuthenticAMD

okt 18 23:05:20 laurens-Vostro-3559 kernel: Hygon HygonGenuine

okt 18 23:05:20 laurens-Vostro-3559 kernel: Centaur CentaurHauls

okt 18 23:05:20 laurens-Vostro-3559 kernel: zhaoxin Shanghai

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-provided physical RAM map:

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [mem 0x0000000000000000-0x0000000000057fff] System RAM

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [mem 0x0000000000058000-0x0000000000058fff] device reserved

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [mem 0x0000000000059000-0x000000000009cfff] System RAM

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [mem 0x000000000009d000-0x000000000009ffff] device reserved

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [gap 0x00000000000a0000-0x00000000000fffff]

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [mem 0x0000000000100000-0x000000007a3b2fff] System RAM

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [mem 0x000000007a3b3000-0x000000007a3b3fff] ACPI NVS

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [mem 0x000000007a3b4000-0x000000007a3ddfff] device reserved

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [mem 0x000000007a3de000-0x000000007a43ffff] System RAM

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [mem 0x000000007a440000-0x000000007abeffff] device reserved

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [mem 0x000000007abf0000-0x0000000086c06fff] System RAM

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [mem 0x0000000086c07000-0x000000008763ffff] device reserved

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [mem 0x0000000087640000-0x0000000087f98fff] ACPI NVS

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [mem 0x0000000087f99000-0x0000000087ffdfff] ACPI data

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [mem 0x0000000087ffe000-0x0000000087ffefff] System RAM

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [gap 0x0000000087fff000-0x0000000087ffffff]

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [mem 0x0000000088000000-0x00000000880fffff] device reserved

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [gap 0x0000000088100000-0x00000000dfffffff]

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] device reserved

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [gap 0x00000000f0000000-0x00000000fdffffff]

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010fff] device reserved

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [gap 0x00000000fe011000-0x00000000febfffff]

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] device reserved

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [gap 0x00000000fec01000-0x00000000fedfffff]

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] device reserved

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [gap 0x00000000fee01000-0x00000000feffffff]

okt 18 23:05:20 laurens-Vostro-3559 kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] device reserved

Acties:
  • Beste antwoord ✓

  • leander-s
  • Registratie: November 2011
  • Laatst online: 17:11
Aangezien dit de logs zijn die je terugkrijgt met -1 geeft het aan dat je logs tijdens de kernel panic niet weggeschreven zijn of corrupt zijn geraakt.

Werkt het handmatig updaten nog correct via:
code:
1
sudo apt update && sudo apt full-upgrade

  • l.vaneijck
  • Registratie: Februari 2015
  • Laatst online: 17:12
laurens@laurens-Vostro-3559:~$ sudo apt update

[sudo] password for laurens:

Hit:1 http://nl.archive.ubuntu.com/ubuntu noble InRelease

Get:2 http://nl.archive.ubuntu.com/ubuntu noble-updates InRelease [126 kB]

Hit:3 http://nl.archive.ubuntu.com/ubuntu noble-backports InRelease

Hit:4 https://brave-browser-apt-release.s3.brave.com stable InRelease

Hit:5 http://security.ubuntu.com/ubuntu noble-security InRelease

Hit:6 https://ppa.launchpadcontent.net/zorinos/apps/ubuntu noble InRelease

Hit:7 https://ppa.launchpadcontent.net/zorinos/drivers/ubuntu noble InRelease

Hit:8 https://ppa.launchpadcontent.net/zorinos/patches/ubuntu noble InRelease

Hit:9 https://ppa.launchpadcontent.net/zorinos/stable/ubuntu noble InRelease

Get:10 http://nl.archive.ubuntu.com/ubuntu noble-updates/main i386 Packages [570 kB]

Get:11 http://nl.archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages [1.400 kB]

Hit:12 https://packages.zorinos.com/stable noble InRelease

Hit:13 https://packages.zorinos.com/patches noble InRelease

Hit:14 https://packages.zorinos.com/apps noble InRelease

Hit:15 https://packages.zorinos.com/drivers noble InRelease

Fetched 2.096 kB in 1s (1.399 kB/s)

Reading package lists... Done

Building dependency tree... Done

Reading state information... Done

9 packages can be upgraded. Run 'apt list --upgradable' to see them.

laurens@laurens-Vostro-3559:~$ sudo apt full-ugrade

E: Invalid operation full-ugrade

laurens@laurens-Vostro-3559:~$ sudo apt full-upgrade

Reading package lists... Done

Building dependency tree... Done

Reading state information... Done

Calculating upgrade... Done

The following packages were automatically installed and are no longer required:

folder-color libetonyek-0.1-1 libfwupd2 zorin-os-feedback

Use 'sudo apt autoremove' to remove them.

The following upgrades have been deferred due to phasing:

gir1.2-glib-2.0 libglib2.0-0t64 libglib2.0-bin libglib2.0-data

The following packages will be upgraded:

brave-browser xserver-common xserver-xephyr xserver-xorg-core

xserver-xorg-legacy

5 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.

Need to get 156 MB of archives.

After this operation, 5.131 kB of additional disk space will be used.

Do you want to continue? [Y/n] y

Get:1 http://nl.archive.ubuntu.com/ubuntu noble-updates/main amd64 xserver-common all 2:21.1.12-1ubuntu1.9 [35,0 kB]

Get:2 http://nl.archive.ubuntu.com/ubuntu noble-updates/main amd64 xserver-xephyr amd64 2:21.1.12-1ubuntu1.9 [1.019 kB]

Get:3 http://nl.archive.ubuntu.com/ubuntu noble-updates/main amd64 xserver-xorg-legacy amd64 2:21.1.12-1ubuntu1.9 [42,0 kB]

Get:4 https://brave-browser-apt-release.s3.brave.com stable/main amd64 brave-browser amd64 1.98.60 [153 MB]

Get:5 http://nl.archive.ubuntu.com/ubuntu noble-updates/main amd64 xserver-xorg-core amd64 2:21.1.12-1ubuntu1.9 [1.476 kB]

Fetched 156 MB in 2s (74,0 MB/s)

Preconfiguring packages ...

setting xserver-xorg-legacy/xwrapper/allowed_users from configuration file

(Reading database… 293287 files and directories currently installed.)

Preparing to unpack …/brave-browser_1.98.60_amd64.deb…

Unpacking brave-browser (1.98.60) over (1.97.59)…

Preparing to unpack …/xserver-common_2%3a21.1.12-1ubuntu1.9_all.deb…

Unpacking xserver-common (2:21.1.12-1ubuntu1.9) over (2:21.1.12-1ubuntu1.8)…

Preparing to unpack …/xserver-xephyr_2%3a21.1.12-1ubuntu1.9_amd64.deb…

Unpacking xserver-xephyr (2:21.1.12-1ubuntu1.9) over (2:21.1.12-1ubuntu1.8)…

Preparing to unpack …/xserver-xorg-legacy_2%3a21.1.12-1ubuntu1.9_amd64.deb…

Unpacking xserver-xorg-legacy (2:21.1.12-1ubuntu1.9) over (2:21.1.12-1ubuntu1.8)

…

Preparing to unpack …/xserver-xorg-core_2%3a21.1.12-1ubuntu1.9_amd64.deb…

Unpacking xserver-xorg-core (2:21.1.12-1ubuntu1.9) over (2:21.1.12-1ubuntu1.8)…

Setting up brave-browser (1.98.60)…

Setting up xserver-common (2:21.1.12-1ubuntu1.9)…

Setting up xserver-xorg-legacy (2:21.1.12-1ubuntu1.9)…

setting xserver-xorg-legacy/xwrapper/allowed_users from configuration file

Setting up xserver-xorg-core (2:21.1.12-1ubuntu1.9)…

Setting up xserver-xephyr (2:21.1.12-1ubuntu1.9)…

Processing triggers for gnome-menus (3.36.0-1.1ubuntu3)…

Processing triggers for man-db (2.12.0-4build2)…

Processing triggers for desktop-file-utils (0.27-2build1)…

laurens@laurens-Vostro-3559:~$

  • l.vaneijck
  • Registratie: Februari 2015
  • Laatst online: 17:12
lijkt nu opgelost? klopt dat?

  • leander-s
  • Registratie: November 2011
  • Laatst online: 17:11
Ja, voor nu wel. je apt updates werken nog en zijn niet corrupt. En aangezien je computer weer goed opstart lijkt het een eenmalig ding te zijn en nog niet direct te wijzen op een hardwareprobleem of curruptie in het bestandssysteem

  • l.vaneijck
  • Registratie: Februari 2015
  • Laatst online: 17:12
super bedankt voor je hulp!
Pagina: 1