Disturbing things in my log! Operating arch x32 and x86-64

Questions about other topics - please check if your question fits better in another category before posting here
Forum rules
Before you post please read how to get help
Post Reply
RemonK
Level 4
Level 4
Posts: 372
Joined: Wed Feb 06, 2019 6:32 pm
Location: Land van Umme
Contact:

Disturbing things in my log! Operating arch x32 and x86-64

Post by RemonK »

I have as it seems, 2 operating architectures running on my system!? I'm not sure if that is normal, but i guess not! :oops:
Also a lot of fstab warnings about unmounting and mounting, and system mounts that can not be found or are already mounted?? As if fstab is invoked again and again...

Code: Select all

kern  :warn  : [<    0,007707>] printk: systemd-fstab-g: 6 output lines suppressed due to ratelimiting
kern  :warn  : [<    0,003698>] printk: systemd-sysv-ge: 238 output lines suppressed due to ratelimiting
kern  :info  : [<    0,094740>] lp: driver loaded but no devices found
kern  :info  : [<    0,004595>] ppdev: user-space parallel port driver
kern  :info  : [<    0,011223>] nct6775: Enabling hardware monitor logical device mappings.
kern  :info  : [<    0,001483>] nct6775: Found NCT6791D or compatible chip at 0x2e:0x290
kern  :info  : [<    0,014028>] RPC: Registered named UNIX socket transport module.
kern  :info  : [<    0,000001>] RPC: Registered udp transport module.
kern  :info  : [<    0,000000>] RPC: Registered tcp transport module.
kern  :info  : [<    0,000000>] RPC: Registered tcp NFSv4.1 backchannel transport module.
kern  :info  : [<    0,010988>] EXT4-fs (sdd3): re-mounted. Opts: errors=remount-ro
daemon:debug : [<    0,002889>] systemd[469]: Operating on architecture: x86
daemon:debug : [<    0,000005>] systemd[469]: Operating on architecture: x32
daemon:debug : [<    0,000212>] systemd[469]: Operating on architecture: x86-64
:
daemon:debug : [<    0,006331>] systemd[1]: No virtualization found in DMI
daemon:debug : [<    0,002199>] systemd[1]: No virtualization found in CPUID
daemon:debug : [<    0,002109>] systemd[1]: Virtualization XEN not found, /proc/xen does not exist
daemon:debug : [<    0,002012>] systemd[1]: This platform does not support /proc/device-tree
daemon:debug : [<    0,019300>] systemd[1]: No virtualization found in /proc/cpuinfo.
daemon:debug : [<    0,001751>] systemd[1]: This platform does not support /proc/sysinfo
daemon:debug : [<    0,001507>] systemd[1]: Found VM virtualization none
daemon:info  : [<    0,001507>] systemd[1]: Detected architecture x86-64.
daemon:debug : [<    0,001569>] systemd[1]: Mounting cgroup to /sys/fs/cgroup/memory of type cgroup with options memory.
daemon:debug : [<    0,035602>] systemd-fstab-generator[422]: Parsing /etc/fstab
daemon:debug : [<    0,000897>] systemd-gpt-auto-generator[424]: /dev/sdd3: root device /dev/sdd.
daemon:debug : [<    0,000774>] systemd-fstab-generator[422]: Found entry what=/dev/disk/by-uuid/c9c0a899-526d-4e9a-bfaf-b889b88045a1 where=/ 
daemon:debug : [<    0,010076>] systemd-sysv-generator[428]: Native unit for networking.service already exists, skipping.
daemon:debug : [<    0,001848>] systemd-sysv-generator[428]: Native unit for hwclock.service already exists, skipping.
daemon:debug : [<    0,000685>] systemd-fstab-generator[422]: Found entry what=/dev/disk/by-uuid/0BAB-160E where=/boot/efi type=vfat makefs=no
daemon:debug : [<    0,002677>] systemd-sysv-generator[428]: Cannot find unit pure-ftpd.service.
daemon:debug : [<    0,004386>] systemd-fstab-generator[422]: Found entry what=/dev/disk/by-uuid/ecfcac14-40dc-45e4-a27b-79be083d1bf5 where=/h
daemon:debug : [<    0,000378>] systemd-sysv-generator[428]: Native unit for sysstat.service already exists, skipping.
daemon:debug : [<    0,006164>] systemd-sysv-generator[428]: Native unit for autofs.service already exists, skipping.
daemon:debug : [<    0,001943>] systemd-sysv-generator[428]: Native unit for kmod.service already exists, skipping.
daemon:debug : [<    0,001637>] systemd-sysv-generator[428]: Native unit for cryptdisks.service already exists, skipping.
daemon:debug : [<    0,001351>] systemd-fstab-generator[422]: Found entry what=/dev/disk/by-uuid/2D04485B14803637 where=/media/admin/Backup ty
daemon:debug : [<    0,000415>] systemd-sysv-generator[428]: Cannot find unit speech-dispatcher.service.
daemon:debug : [<    0,000222>] systemd-gpt-auto-generator[424]: /boot already populated, ignoring.
daemon:debug : [<    0,003074>] systemd-fstab-generator[422]: Found entry what=/dev/disk/by-uuid/49CB3AAA7F6011FB where=/media/admin/Multimedi
daemon:debug : [<    0,002659>] systemd-sysv-generator[428]: Cannot find unit stunnel4.service.
daemon:debug : [<    0,001756>] systemd-fstab-generator[422]: Found entry what=/dev/disk/by-uuid/2EB1FFF4073EC0AC where=/media/admin/Games typ
daemon:debug : [<    0,004079>] systemd-sysv-generator[428]: Native unit for plymouth-log.service already exists, skipping.
daemon:debug : [<    0,000237>] systemd-fstab-generator[422]: Found entry what=/dev/disk/by-uuid/65B7BF921A42ED93 where=/media/admin/Download 
daemon:debug : [<    0,009834>] systemd-fstab-generator[422]: Found entry what=/dev/sr0 where=/media/admin/MYCDROM type=udf,iso9660 makefs=no 
daemon:debug : [<    0,010106>] systemd-fstab-generator[422]: Found entry what=/media/admin/Backup/Security_Camera/Thuis/IPCamOprit where=/mnt
:
daemon:debug : [<    0,006331>] systemd[1]: No virtualization found in DMI
daemon:debug : [<    0,002199>] systemd[1]: No virtualization found in CPUID
daemon:debug : [<    0,002109>] systemd[1]: Virtualization XEN not found, /proc/xen does not exist
daemon:debug : [<    0,002012>] systemd[1]: This platform does not support /proc/device-tree
daemon:debug : [<    0,019300>] systemd[1]: No virtualization found in /proc/cpuinfo.
daemon:debug : [<    0,001751>] systemd[1]: This platform does not support /proc/sysinfo
daemon:debug : [<    0,001507>] systemd[1]: Found VM virtualization none
daemon:info  : [<    0,001507>] systemd[1]: Detected architecture x86-64.
daemon:debug : [<    0,001569>] systemd[1]: Mounting cgroup to /sys/fs/cgroup/memory of type cgroup with options memory.
daemon:debug : [<    0,035602>] systemd-fstab-generator[422]: Parsing /etc/fstab
daemon:debug : [<    0,000897>] systemd-gpt-auto-generator[424]: /dev/sdd3: root device /dev/sdd.
daemon:debug : [<    0,000774>] systemd-fstab-generator[422]: Found entry what=/dev/disk/by-uuid/c9c0a899-526d-4e9a-bfaf-b889b88045a1 where=/ type=ext4 makefs=no nofail=no noauto=no
daemon:debug : [<    0,010076>] systemd-sysv-generator[428]: Native unit for networking.service already exists, skipping.
daemon:debug : [<    0,001848>] systemd-sysv-generator[428]: Native unit for hwclock.service already exists, skipping.
daemon:debug : [<    0,000685>] systemd-fstab-generator[422]: Found entry what=/dev/disk/by-uuid/0BAB-160E where=/boot/efi type=vfat makefs=no nofail=no noauto=no
daemon:debug : [<    0,002677>] systemd-sysv-generator[428]: Cannot find unit pure-ftpd.service.
daemon:debug : [<    0,004386>] systemd-fstab-generator[422]: Found entry what=/dev/disk/by-uuid/ecfcac14-40dc-45e4-a27b-79be083d1bf5 where=/home type=ext4 makefs=no nofail=no noauto=no
daemon:debug : [<    0,000378>] systemd-sysv-generator[428]: Native unit for sysstat.service already exists, skipping.
daemon:debug : [<    0,006164>] systemd-sysv-generator[428]: Native unit for autofs.service already exists, skipping.
daemon:debug : [<    0,001943>] systemd-sysv-generator[428]: Native unit for kmod.service already exists, skipping.
daemon:debug : [<    0,001637>] systemd-sysv-generator[428]: Native unit for cryptdisks.service already exists, skipping.
daemon:debug : [<    0,001351>] systemd-fstab-generator[422]: Found entry what=/dev/disk/by-uuid/2D04485B14803637 where=/media/admin/Backup type=ntfs makefs=no nofail=no noauto=no
daemon:debug : [<    0,000415>] systemd-sysv-generator[428]: Cannot find unit speech-dispatcher.service.
daemon:debug : [<    0,000222>] systemd-gpt-auto-generator[424]: /boot already populated, ignoring.
daemon:debug : [<    0,003074>] systemd-fstab-generator[422]: Found entry what=/dev/disk/by-uuid/49CB3AAA7F6011FB where=/media/admin/Multimedia type=ntfs makefs=no nofail=no noauto=no
daemon:debug : [<    0,002659>] systemd-sysv-generator[428]: Cannot find unit stunnel4.service.
daemon:debug : [<    0,001756>] systemd-fstab-generator[422]: Found entry what=/dev/disk/by-uuid/2EB1FFF4073EC0AC where=/media/admin/Games type=ntfs makefs=no nofail=no noauto=no
daemon:debug : [<    0,004079>] systemd-sysv-generator[428]: Native unit for plymouth-log.service already exists, skipping.
daemon:debug : [<    0,000237>] systemd-fstab-generator[422]: Found entry what=/dev/disk/by-uuid/65B7BF921A42ED93 where=/media/admin/Download type=ntfs makefs=no nofail=no noauto=no
daemon:debug : [<    0,009834>] systemd-fstab-generator[422]: Found entry what=/dev/sr0 where=/media/admin/MYCDROM type=udf,iso9660 makefs=no nofail=yes noauto=no
daemon:debug : [<    0,010106>] systemd-fstab-generator[422]: Found entry what=/media/admin/Backup/Security_Camera/Thuis/IPCamOprit where=/mnt/ftproot/IPCamOprit type=fuse.bindfs makefs=no nofail=no noauto=no
kern  :warn  : [<    0,007707>] printk: systemd-fstab-g: 6 output lines suppressed due to ratelimiting
kern  :warn  : [<    0,003698>] printk: systemd-sysv-ge: 238 output lines suppressed due to ratelimiting
kern  :info  : [<    0,094740>] lp: driver loaded but no devices found
kern  :info  : [<    0,004595>] ppdev: user-space parallel port driver
kern  :info  : [<    0,011223>] nct6775: Enabling hardware monitor logical device mappings.
kern  :info  : [<    0,001483>] nct6775: Found NCT6791D or compatible chip at 0x2e:0x290
kern  :info  : [<    0,014028>] RPC: Registered named UNIX socket transport module.
kern  :info  : [<    0,000001>] RPC: Registered udp transport module.
kern  :info  : [<    0,000000>] RPC: Registered tcp transport module.
kern  :info  : [<    0,000000>] RPC: Registered tcp NFSv4.1 backchannel transport module.
kern  :info  : [<    0,010988>] EXT4-fs (sdd3): re-mounted. Opts: errors=remount-ro
daemon:debug : [<    0,002889>] systemd[469]: Operating on architecture: x86
daemon:debug : [<    0,000005>] systemd[469]: Operating on architecture: x32
daemon:debug : [<    0,000212>] systemd[469]: Operating on architecture: x86-64
daemon:debug : [<    0,000143>] systemd[469]: Operating on architecture: x86
daemon:debug : [<    0,000051>] systemd[469]: Operating on architecture: x32
daemon:debug : [<    0,000029>] systemd[469]: Operating on architecture: x86-64
daemon:debug : [<    0,000034>] systemd[469]: Operating on architecture: x86
daemon:debug : [<    0,000029>] systemd[469]: Operating on architecture: x32
daemon:debug : [<    0,000024>] systemd[469]: Operating on architecture: x86-64
daemon:debug : [<    0,000199>] systemd[469]: Restricting namespace to: .
daemon:debug : [<    0,000005>] systemd[469]: Operating on architecture: x86
daemon:debug : [<    0,000008>] systemd[469]: Blocking cgroup.
daemon:debug : [<    0,000007>] systemd[469]: Blocking ipc.
daemon:debug : [<    0,000008>] systemd[469]: Blocking net.
daemon:debug : [<    0,000007>] systemd[469]: Blocking mnt.
daemon:debug : [<    0,000008>] systemd[469]: Blocking pid.
daemon:debug : [<    0,000007>] systemd[469]: Blocking user.
daemon:debug : [<    0,000007>] systemd[469]: Blocking uts.
daemon:debug : [<    0,000034>] systemd[469]: Operating on architecture: x32
daemon:debug : [<    0,000006>] systemd[469]: Blocking cgroup.
daemon:debug : [<    0,000006>] systemd[469]: Blocking ipc.
daemon:debug : [<    0,000006>] systemd[469]: Blocking net.
:
daemon:debug : [<    0,006331>] systemd[1]: No virtualization found in DMI
daemon:debug : [<    0,002199>] systemd[1]: No virtualization found in CPUID
daemon:debug : [<    0,002109>] systemd[1]: Virtualization XEN not found, /proc/xen does not exist
daemon:debug : [<    0,002012>] systemd[1]: This platform does not support /proc/device-tree
daemon:debug : [<    0,019300>] systemd[1]: No virtualization found in /proc/cpuinfo.
daemon:debug : [<    0,001751>] systemd[1]: This platform does not support /proc/sysinfo
daemon:debug : [<    0,001507>] systemd[1]: Found VM virtualization none
daemon:info  : [<    0,001507>] systemd[1]: Detected architecture x86-64.
daemon:debug : [<    0,001569>] systemd[1]: Mounting cgroup to /sys/fs/cgroup/memory of type cgroup with options memory.
daemon:debug : [<    0,035602>] systemd-fstab-generator[422]: Parsing /etc/fstab
And i guess this keeps happening because i got blocks and blocks of this in my logs!
Het leven is net een kartbaan; Sensatie, adrenaline en veel te snel voorbij!
Joeptjoep - Feestboek
User avatar
SMG
Level 16
Level 16
Posts: 6248
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Disturbing things in my log! Operating arch x32 and x86-64

Post by SMG »

RemonK wrote:
Wed May 26, 2021 6:24 pm
Also a lot of fstab warnings about unmounting and mounting, and system mounts that can not be found or are already mounted??
You posted a section of log, but have not told us from what log you gathered this information. How did you obtain the information you posted?

Please give us information about your install by entering this command in a terminal: inxi -Fxxxrz
Click </> from the mini toolbar above the textbox where you type your reply and then place your cursor between the code markers and paste the results of the command between the code markers [code]Results[/code]. This will let us know how Mint sees your hardware.
A woman typing on a laptop with LM20.2 Cinnamon.
RemonK
Level 4
Level 4
Posts: 372
Joined: Wed Feb 06, 2019 6:32 pm
Location: Land van Umme
Contact:

Re: Disturbing things in my log! Operating arch x32 and x86-64

Post by RemonK »

Sorry for the late reply, my dad past away this week..

But here is the inxi outcome:

Code: Select all

admin@P3300LX:~/.conky/MyPanels$ inxi -Fxxxrz
System:    Host: P3300LX Kernel: 5.4.0-74-generic x86_64 bits: 64 compiler: gcc v: 7.5.0 Desktop: Cinnamon 4.4.8 
           wm: muffin 4.4.4 dm: LightDM 1.26.0 Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic 
Machine:   Type: Desktop System: ASUS product: All Series v: N/A serial: <filter> 
           Mobo: ASUSTeK model: Z87-PRO v: Rev 1.xx serial: <filter> UEFI: American Megatrends v: 1504 date: 10/03/2013 
CPU:       Topology: Quad Core model: Intel Core i5-4670K bits: 64 type: MCP arch: Haswell rev: 3 L2 cache: 6144 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 27201 
           Speed: 3513 MHz min/max: 800/4300 MHz Core speeds (MHz): 1: 3513 2: 3723 3: 3814 4: 3790 
Graphics:  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics vendor: ASUSTeK driver: i915 v: kernel 
           bus ID: 00:02.0 chip ID: 8086:0412 
           Device-2: Advanced Micro Devices [AMD/ATI] Juniper XT [Radeon HD 5770] vendor: Micro-Star MSI driver: radeon 
           v: kernel bus ID: 01:00.0 chip ID: 1002:68b8 
           Display: x11 server: X.Org 1.19.6 driver: ati,modesetting,radeon unloaded: fbdev,vesa compositor: muffin v: 4.4.4 
           resolution: 1920x1080~60Hz, 1360x768~60Hz 
           OpenGL: renderer: AMD JUNIPER (DRM 2.50.0 / 5.4.0-74-generic LLVM 10.0.0) v: 3.3 Mesa 20.0.8 compat-v: 3.1 
           direct render: Yes 
Audio:     Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel 
           bus ID: 00:03.0 chip ID: 8086:0c0c 
           Device-2: Intel 8 Series/C220 Series High Definition Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel 
           bus ID: 00:1b.0 chip ID: 8086:8c20 
           Device-3: Advanced Micro Devices [AMD/ATI] Juniper HDMI Audio [Radeon HD 5700 Series] vendor: Micro-Star MSI 
           driver: snd_hda_intel v: kernel bus ID: 01:00.1 chip ID: 1002:aa58 
           Sound Server: ALSA v: k5.4.0-74-generic 
Network:   Device-1: Intel Ethernet I217-V vendor: ASUSTeK driver: e1000e v: 3.2.6-k port: f080 bus ID: 00:19.0 
           chip ID: 8086:153b 
           IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter> 
           Device-2: Qualcomm Atheros AR9462 Wireless Network Adapter vendor: ASUSTeK driver: ath9k v: kernel port: e000 
           bus ID: 03:00.0 chip ID: 168c:0034 
           IF: wlp3s0 state: down mac: <filter> 
Drives:    Local Storage: total: 3.23 TiB used: 2.22 TiB (69.0%) 
           ID-1: /dev/sda vendor: Samsung model: SSD 840 EVO 250GB size: 232.89 GiB speed: 6.0 Gb/s serial: <filter> rev: BB6Q 
           temp: 44 C scheme: MBR 
           ID-2: /dev/sdb vendor: Toshiba model: HDWD130 size: 2.73 TiB speed: 6.0 Gb/s rotation: 7200 rpm serial: <filter> 
           rev: ACF0 temp: 41 C scheme: MBR 
           ID-3: /dev/sdc vendor: Maxtor model: 6L160M0 size: 149.05 GiB speed: 1.5 Gb/s serial: <filter> rev: 1G10 temp: 46 C 
           scheme: MBR 
           ID-4: /dev/sdd vendor: Intenso model: SSD size: 111.79 GiB speed: 6.0 Gb/s serial: <filter> rev: 7A0 temp: 35 C 
           scheme: GPT 
           ID-5: /dev/sde type: USB vendor: Generic model: STORAGE DEVICE size: 14.84 GiB serial: <filter> rev: FT01 
           scheme: MBR 
Partition: ID-1: / size: 37.62 GiB used: 21.05 GiB (56.0%) fs: ext4 dev: /dev/sdd3 
           ID-2: /home size: 71.59 GiB used: 50.03 GiB (69.9%) fs: ext4 dev: /dev/sdd4 
Sensors:   System Temperatures: cpu: 43.5 C mobo: 40.0 C gpu: radeon temp: 49 C 
           Fan Speeds (RPM): fan-1: 686 fan-2: 524 fan-3: 541 fan-4: 0 fan-5: 582 fan-6: 0 
           Voltages: 12v: N/A 5v: N/A 3.3v: 3.31 vbat: 3.33 
Repos:     Active apt repos in: /etc/apt/sources.list 
           1: deb http://31.archive.ubuntu.com/ubuntu/ bionic main restricted universe
           2: deb http://31.archive.ubuntu.com/ubuntu/ bionic-security main restricted universe
           3: deb http://31.archive.ubuntu.com/ubuntu/ bionic-updates main restricted universe
           4: deb http://31.archive.ubuntu.com/ubuntu/ bionic-proposed main restricted universe
           5: deb http://download.webmin.com/download/repository sarge contrib
           Active apt repos in: /etc/apt/sources.list.d/additional-repositories.list 
           1: deb https://deb.opera.com/opera-stable/ stable non-free
           Active apt repos in: /etc/apt/sources.list.d/flexiondotorg-awf-bionic.list 
           1: deb-src http://ppa.launchpad.net/flexiondotorg/awf/ubuntu bionic main
           Active apt repos in: /etc/apt/sources.list.d/mark-pcnetspec-gksu-bionic.list 
           1: deb http://ppa.launchpad.net/mark-pcnetspec/gksu/ubuntu bionic main
           No active apt repos in: /etc/apt/sources.list.d/mikhailnov-pulseeffects-bionic.list 
           Active apt repos in: /etc/apt/sources.list.d/mkusb-ppa-bionic.list 
           1: deb http://ppa.launchpad.net/mkusb/ppa/ubuntu bionic main
           2: deb-src http://ppa.launchpad.net/mkusb/ppa/ubuntu bionic main
           Active apt repos in: /etc/apt/sources.list.d/nodesource.list 
           1: deb [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_16.x bionic main
           2: deb-src [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_16.x bionic main
           Active apt repos in: /etc/apt/sources.list.d/official-dbgsym-repositories.list 
           1: deb http://ddebs.ubuntu.com bionic main restricted universe multiverse
           2: deb http://ddebs.ubuntu.com bionic-updates main restricted universe multiverse
           Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 
           1: deb http://mintlinux.mirror.wearetriple.com/packages tricia main upstream import backport
           2: deb http://archive.ubuntu.com/ubuntu bionic main restricted universe multiverse
           3: deb http://archive.ubuntu.com/ubuntu bionic-updates main restricted universe multiverse
           4: deb http://archive.ubuntu.com/ubuntu bionic-backports main restricted universe multiverse
           5: deb http://security.ubuntu.com/ubuntu/ bionic-security main restricted universe multiverse
           6: deb http://archive.canonical.com/ubuntu/ bionic partner
           No active apt repos in: /etc/apt/sources.list.d/otto-kesselgulasch-gimp-bionic.list 
           No active apt repos in: /etc/apt/sources.list.d/playonlinux.list 
           Active apt repos in: /etc/apt/sources.list.d/remmina-ppa-team-remmina-next-bionic.list 
           1: deb http://ppa.launchpad.net/remmina-ppa-team/remmina-next/ubuntu bionic main
           Active apt repos in: /etc/apt/sources.list.d/signal-xenial.list 
           1: deb [arch=amd64 signed-by=/usr/share/keyrings/signal-desktop-keyring.gpg] https://updates.signal.org/desktop/apt xenial main
           No active apt repos in: /etc/apt/sources.list.d/team-xbmc-ppa-bionic.list 
           Active apt repos in: /etc/apt/sources.list.d/teejee2008-ppa-bionic.list 
           1: deb http://ppa.launchpad.net/teejee2008/ppa/ubuntu bionic main
           Active apt repos in: /etc/apt/sources.list.d/trebelnik-stefina-radeon-profile-bionic.list 
           1: deb http://ppa.launchpad.net/trebelnik-stefina/radeon-profile/ubuntu bionic main
           Active apt repos in: /etc/apt/sources.list.d/webupd8team-indicator-kdeconnect-bionic.list 
           1: deb http://ppa.launchpad.net/webupd8team/indicator-kdeconnect/ubuntu bionic main
Info:      Processes: 477 Uptime: 6d 10h 52m Memory: 15.51 GiB used: 8.69 GiB (56.0%) Init: systemd v: 237 runlevel: 5 
           Compilers: gcc: 7.5.0 alt: 7 Shell: bash v: 4.4.20 running in: guake inxi: 3.0.32 

The log was from journalctl in terminal.. if you want i can zip it and include.
There is so much wrong in it, that i don't know were to start.. :|
Het leven is net een kartbaan; Sensatie, adrenaline en veel te snel voorbij!
Joeptjoep - Feestboek
mikeflan
Level 7
Level 7
Posts: 1823
Joined: Sun Apr 26, 2020 9:28 am
Location: Houston, TX

Re: Disturbing things in my log! Operating arch x32 and x86-64

Post by mikeflan »

SMG wrote:
Fri May 28, 2021 3:59 pm
You posted a section of log
I'm quoting SMG to see if we can get her back here. Ignore this.
I have as it seems, 2 operating architectures running on my system
What makes you think there are 2 operating architectures (arch x32 and x86-64) running on your system? Where do you see the arch x32?

Show us the output of this in a terminal:

Code: Select all

cat /etc/fstab
Has your system run fine in the past? I guess technically it runs fine now. When did the long logs first appear - just days ago?
Last edited by Moem on Sun Jun 06, 2021 8:23 am, edited 1 time in total.
Reason: Added referral to the quote, so SMG may be notified.
User avatar
SMG
Level 16
Level 16
Posts: 6248
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Disturbing things in my log! Operating arch x32 and x86-64

Post by SMG »

RemonK wrote:
Sat Jun 05, 2021 9:15 pm
Sorry for the late reply, my dad past away this week..
Sending my condolences for your loss. :heart:
RemonK wrote:
Sat Jun 05, 2021 9:15 pm
The log was from journalctl in terminal.. if you want i can zip it and include.
I'm not used to seeing the line items in that format from journalctl which is why I asked.
RemonK wrote:
Sat Jun 05, 2021 9:15 pm
There is so much wrong in it, that i don't know were to start.. :|
Let's start with the fact not everything listed in journalctl is a problem. For example:

Code: Select all

kern  :info  : [<    0,010988>] EXT4-fs (sdd3): re-mounted. Opts: errors=remount-ro
is not an error. During the boot process, root is mounted so the system can be set up properly (read, write) and then it is remounted in read only (ro) format and set to give information to you when there are errors or problems. That is what that line means.

Sometimes errors happen so the operating makes a second attempt which is successful. That means the first set of errors are not an issue.

Regarding your comment about seeing the two different operating system architectures mentioned, it's possible that is relate to software you are using on your system. I noticed in your repos:

Code: Select all

           No active apt repos in: /etc/apt/sources.list.d/playonlinux.list 
Some older game software is only available in 32 bit versions. The graphics drivers will load both 32-bit and 64-bit libraries so one can use the older 32-bit software that may be running on one's 64-bit system. It's possible that is what those lines reference (but I do not know that for sure).

You seem to have run journalctl with a debugging option? Not sure. When I ask people for information I advise running the following:
journalctl -b | nc termbin.com 9999
That generates the standard information from the current boot cycle and sends it to termbin. It will return with a url address that you should post should you want us to help you analyze it.

Were you having a specific problem that you decided to check journalctl? Nothing jumps out at me as a possible issue in your inxi although it's a bit different because you have two sets of repos for updates. Usually only one set is in the list.

Code: Select all

Repos:     Active apt repos in: /etc/apt/sources.list 
           1: deb http://31.archive.ubuntu.com/ubuntu/ bionic main restricted universe
           2: deb http://31.archive.ubuntu.com/ubuntu/ bionic-security main restricted universe
           3: deb http://31.archive.ubuntu.com/ubuntu/ bionic-updates main restricted universe
           4: deb http://31.archive.ubuntu.com/ubuntu/ bionic-proposed main restricted universe
           5: deb http://download.webmin.com/download/repository sarge contrib
           Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 
           1: deb http://mintlinux.mirror.wearetriple.com/packages tricia main upstream import backport
           2: deb http://archive.ubuntu.com/ubuntu bionic main restricted universe multiverse
           3: deb http://archive.ubuntu.com/ubuntu bionic-updates main restricted universe multiverse
           4: deb http://archive.ubuntu.com/ubuntu bionic-backports main restricted universe multiverse
           5: deb http://security.ubuntu.com/ubuntu/ bionic-security main restricted universe multiverse
           6: deb http://archive.canonical.com/ubuntu/ bionic partner
A woman typing on a laptop with LM20.2 Cinnamon.
RemonK
Level 4
Level 4
Posts: 372
Joined: Wed Feb 06, 2019 6:32 pm
Location: Land van Umme
Contact:

Re: Disturbing things in my log! Operating arch x32 and x86-64

Post by RemonK »

mikeflan wrote:
Sun Jun 06, 2021 7:55 am
What makes you think there are 2 operating architectures (arch x32 and x86-64) running on your system? Where do you see the arch x32?
Ehh... maybe because of these millions of lines in my journal?

Code: Select all

jun 06 22:51:10 P3300LX systemd[23843]: Operating on architecture: x86
jun 06 22:51:10 P3300LX systemd[23843]: Operating on architecture: x32
jun 06 22:51:10 P3300LX systemd[23843]: Operating on architecture: x86-64
jun 06 22:51:10 P3300LX systemd[23843]: Operating on architecture: x86
jun 06 22:51:10 P3300LX systemd[23843]: Operating on architecture: x32
jun 06 22:51:10 P3300LX systemd[23843]: Operating on architecture: x86-64
jun 06 22:51:10 P3300LX systemd[23843]: Operating on architecture: x86
jun 06 22:51:10 P3300LX systemd[23843]: Operating on architecture: x32
jun 06 22:51:10 P3300LX systemd[23843]: Operating on architecture: x86-64
jun 06 22:51:10 P3300LX systemd[23843]: Operating on architecture: x86
jun 06 22:51:10 P3300LX systemd[23843]: Operating on architecture: x32
jun 06 22:51:10 P3300LX systemd[23843]: Operating on architecture: x86-64
jun 06 22:51:10 P3300LX systemd[23843]: Operating on architecture: x86
jun 06 22:51:10 P3300LX systemd[23843]: Operating on architecture: x32
jun 06 22:51:10 P3300LX systemd[23843]: Operating on architecture: x86-64
jun 06 22:51:10 P3300LX systemd[23843]: Operating on architecture: x86
jun 06 22:51:10 P3300LX systemd[23843]: Operating on architecture: x32
jun 06 22:51:10 P3300LX systemd[23843]: Operating on architecture: x86-64
jun 06 22:51:10 P3300LX systemd[23843]: Operating on architecture: x86
jun 06 22:51:10 P3300LX systemd[23843]: Operating on architecture: x32
jun 06 22:51:10 P3300LX systemd[23843]: Operating on architecture: x86-64
jun 06 22:51:10 P3300LX systemd[23843]: Operating on architecture: x86
jun 06 22:51:10 P3300LX systemd[23843]: Operating on architecture: x32
jun 06 22:51:10 P3300LX systemd[23843]: Operating on architecture: x86-64
jun 06 23:01:10 P3300LX systemd[13802]: Operating on architecture: x86
jun 06 23:01:10 P3300LX systemd[13802]: Operating on architecture: x32
jun 06 23:01:10 P3300LX systemd[13802]: Operating on architecture: x86-64
jun 06 23:01:10 P3300LX systemd[13802]: Operating on architecture: x86
jun 06 23:01:10 P3300LX systemd[13802]: Operating on architecture: x32
jun 06 23:01:10 P3300LX systemd[13802]: Operating on architecture: x86-64
jun 06 23:01:10 P3300LX systemd[13802]: Operating on architecture: x86
jun 06 23:01:10 P3300LX systemd[13802]: Operating on architecture: x32
jun 06 23:01:10 P3300LX systemd[13802]: Operating on architecture: x86-64
jun 06 23:01:10 P3300LX systemd[13802]: Operating on architecture: x86
jun 06 23:01:10 P3300LX systemd[13802]: Operating on architecture: x32
jun 06 23:01:10 P3300LX systemd[13802]: Operating on architecture: x86-64
jun 06 23:01:10 P3300LX systemd[13802]: Operating on architecture: x86
jun 06 23:01:10 P3300LX systemd[13802]: Operating on architecture: x32
jun 06 23:01:10 P3300LX systemd[13802]: Operating on architecture: x86-64
mikeflan wrote: Show us the output of this in a terminal:

Code: Select all

cat /etc/fstab

Code: Select all

# <file system>                              <mount point>          <type> <options>        <dump> <pass>
#
#
##  Mount SYSTEM
UUID=c9c0a899-526d-4e9a-bfaf-b889b88045a1    /                        ext4  errors=remount-ro    0  1
UUID=0BAB-160E                               /boot/efi                vfat  umask=0077           0  1
UUID=ecfcac14-40dc-45e4-a27b-79be083d1bf5    /home                    ext4  defaults             0  2
#UUID=f565c1d8-cff5-4744-8a0b-85025ef812fe    /media/root/BackupLinux  ext4
#
#
##  Mount other drives
#UUID=01CFF5309165B1B0     /media/admin/Win7_64       ntfs defaults,rw  0  0
UUID=2D04485B14803637      /media/admin/Backup        ntfs defaults,rw  0  0
UUID=49CB3AAA7F6011FB      /media/admin/Multimedia    ntfs defaults,rw  0  0
UUID=2EB1FFF4073EC0AC      /media/admin/Games         ntfs defaults,rw  0  0
UUID=65B7BF921A42ED93      /media/admin/Download      ntfs defaults,rw  0  0
#
#
##  Mount CDROM
/dev/sr0 /media/admin/MYCDROM udf,iso9660  user,noauto,exec,utf8  0  0
#
#
## SWAP is dphys-swapfile - swap[on|off]
#
#
##  Bind FTP shares for IPCams
/media/admin/Backup/Security_Camera/Thuis/IPCamOprit        /mnt/ftproot/IPCamOprit           fuse.bindfs  nonempty,force-user=ipcams,x-systemd.requires=/media/admin/Backup  0  0
/media/admin/Backup/Security_Camera/Thuis/IPCamAanbouw      /mnt/ftproot/IPCamAanbouw         fuse.bindfs  nonempty,force-user=ipcams,x-systemd.requires=/media/admin/Backup  0  0
/media/admin/Backup/Security_Camera/Thuis/IPCamWashok       /mnt/ftproot/IPCamWashok          fuse.bindfs  nonempty,force-user=ipcams,x-systemd.requires=/media/admin/Backup  0  0
/media/admin/Backup/Security_Camera/Thuis/IPCamShelby       /mnt/ftproot/IPCamShelby          fuse.bindfs  nonempty,force-user=ipcams,x-systemd.requires=/media/admin/Backup  0  0
/media/admin/Backup/Security_Camera/Thuis/IPCamAuto         /mnt/ftproot/IPCamAuto            fuse.bindfs  nonempty,force-user=ipcams,x-systemd.requires=/media/admin/Backup  0  0
#
#
##  Mount NAS shares via SSH
sshfs#admin@192.168.1.200:/                  /media/admin/NAS_Root      fuse  auto,defaults,allow_other,_netdev,ssh_command=sshpass\040-f\040/root/.ssh/host.password\040ssh  0  0
sshfs#admin@192.168.1.200:/i-data/b246bfb6   /media/admin/NAS_Volume1   fuse  users,auto,allow_other,ssh_command=sshpass\040-f\040/root/.ssh/host.password\040ssh             0  0
#
#
##  Mount SERVER shares via SSH
#sshfs#admin@192.168.1.102:/                                /media/admin/SERVER/root          fuse  users,auto,allow_other,ssh_command=sshpass\040-f\040/root/.ssh/host.password\040ssh  0  0
#sshfs#admin@192.168.1.102:/media/admin/server/VM_STORE     /media/admin/SERVER/VM_STORE      fuse  users,auto,allow_other,ssh_command=sshpass\040-f\040/root/.ssh/host.password\040ssh  0  0
#sshfs#admin@192.168.1.102:/media/admin/server/VM_MEDIA     /media/admin/SERVER/VM_MEDIA      fuse  users,auto,allow_other,ssh_command=sshpass\040-f\040/root/.ssh/host.password\040ssh  0  0
#sshfs#admin@192.168.1.102:/media/admin/server/VM_FORUM     /media/admin/SERVER/VM_FORUM      fuse  users,auto,allow_other,ssh_command=sshpass\040-f\040/root/.ssh/host.password\040ssh  0  0
#sshfs#admin@192.168.1.102:/media/admin/server/VM_FILES     /media/admin/SERVER/VM_FILES      fuse  users,auto,allow_other,ssh_command=sshpass\040-f\040/root/.ssh/host.password\040ssh  0  0
#sshfs#admin@192.168.1.102:/media/admin/server/VM_UTILS     /media/admin/SERVER/VM_UTILS      fuse  users,auto,allow_other,ssh_command=sshpass\040-f\040/root/.ssh/host.password\040ssh  0  0
#sshfs#admin@192.168.1.102:/media/admin/server/DATA_BACKUP  /media/admin/SERVER/DATA_BACKUP   fuse  users,auto,allow_other,ssh_command=sshpass\040-f\040/root/.ssh/host.password\040ssh  0  0
#
mikeflan wrote: Has your system run fine in the past? I guess technically it runs fine now. When did the long logs first appear - just days ago?
3 years ago i came from m$ and installed Mint 19.3. The setup went a little troublesome, but i managed to get it going! In week 2 the log from the firewall F-ed up my system and i got zero bytes left! It wouldn't start anymore.. :shock:
After a few days of trail and error, I managed to ditch the log, ditch my F-ed up account, made a new one and got it running again.
In these 3 years i also did some bad things myself, but every time i got my system up and running again. For me it was a linux learning curve.. ;) But sometimes i wonder if i just had started all over again with a clean setup, maybe it ran much smoother!
I had from the beginning (after the first crash) a lot of warnings and strange things in my log.. but since the last 2 months after i did some testing with Wine and Playonlinux it got mad! Even after i deleted complete Win and Playonlinux!
I am busy with a fresh setup of Mint 20 on a new drive and bit by bit installing all the daemons and customisations i made on this setup. But that's noway near finished yet, so for now i still have to work on this one..
Het leven is net een kartbaan; Sensatie, adrenaline en veel te snel voorbij!
Joeptjoep - Feestboek
RemonK
Level 4
Level 4
Posts: 372
Joined: Wed Feb 06, 2019 6:32 pm
Location: Land van Umme
Contact:

Re: Disturbing things in my log! Operating arch x32 and x86-64

Post by RemonK »

SMG wrote:
Sun Jun 06, 2021 8:56 am
RemonK wrote:
Sat Jun 05, 2021 9:15 pm
Sorry for the late reply, my dad past away this week..
Sending my condolences for your loss. :heart:
Thank you! One of the worst things of my life... 69 is way to young! :cry:


SMG wrote:
RemonK wrote:
Sat Jun 05, 2021 9:15 pm
There is so much wrong in it, that i don't know were to start.. :|
Let's start with the fact not everything listed in journalctl is a problem. For example:

Code: Select all

kern  :info  : [<    0,010988>] EXT4-fs (sdd3): re-mounted. Opts: errors=remount-ro
is not an error. During the boot process, root is mounted so the system can be set up properly (read, write) and then it is remounted in read only (ro) format and set to give information to you when there are errors or problems. That is what that line means.
Sometimes errors happen so the operating makes a second attempt which is successful. That means the first set of errors are not an issue.
Ok, that one i understand and have seen in more kernel logs. My little NAS server does the same.
But i have huge blocks of the same warnings/errors over and over!

SMG wrote: Regarding your comment about seeing the two different operating system architectures mentioned, it's possible that is relate to software you are using on your system. I noticed in your repos:

Code: Select all

           No active apt repos in: /etc/apt/sources.list.d/playonlinux.list 
Some older game software is only available in 32 bit versions. The graphics drivers will load both 32-bit and 64-bit libraries so one can use the older 32-bit software that may be running on one's 64-bit system. It's possible that is what those lines reference (but I do not know that for sure).
Well.. you may not guess again! ;) It started about 2 months ago after some testing with wine and playonlinux indeed. I noticed it too late, my monthly backup was already overwritten, or else i could timeshift back before the testing.

SMG wrote: You seem to have run journalctl with a debugging option? Not sure. When I ask people for information I advise running the following:
journalctl -b | nc termbin.com 9999
That generates the standard information from the current boot cycle and sends it to termbin. It will return with a url address that you should post should you want us to help you analyze it.
Thaaaat's very nice! Never knew about this option.. https://termbin.com/q621


SMG wrote: Were you having a specific problem that you decided to check journalctl? Nothing jumps out at me as a possible issue in your inxi although it's a bit different because you have two sets of repos for updates. Usually only one set is in the list.

Code: Select all

Repos:     Active apt repos in: /etc/apt/sources.list 
           1: deb http://31.archive.ubuntu.com/ubuntu/ bionic main restricted universe
           2: deb http://31.archive.ubuntu.com/ubuntu/ bionic-security main restricted universe
           3: deb http://31.archive.ubuntu.com/ubuntu/ bionic-updates main restricted universe
           4: deb http://31.archive.ubuntu.com/ubuntu/ bionic-proposed main restricted universe
           5: deb http://download.webmin.com/download/repository sarge contrib
           Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 
           1: deb http://mintlinux.mirror.wearetriple.com/packages tricia main upstream import backport
           2: deb http://archive.ubuntu.com/ubuntu bionic main restricted universe multiverse
           3: deb http://archive.ubuntu.com/ubuntu bionic-updates main restricted universe multiverse
           4: deb http://archive.ubuntu.com/ubuntu bionic-backports main restricted universe multiverse
           5: deb http://security.ubuntu.com/ubuntu/ bionic-security main restricted universe multiverse
           6: deb http://archive.canonical.com/ubuntu/ bionic partner
I guess.. could it be that wine or Playonlinux needed that? For some m$ software i had to install a 32bit version. But i can't remember what actions i made because i had to install wine over and over. It is a piece of shitty software, so i decided to stick with my VM. But i guess it left a big mess...
Het leven is net een kartbaan; Sensatie, adrenaline en veel te snel voorbij!
Joeptjoep - Feestboek
User avatar
SMG
Level 16
Level 16
Posts: 6248
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Disturbing things in my log! Operating arch x32 and x86-64

Post by SMG »

RemonK wrote:
Wed Jun 09, 2021 9:20 pm
But i have huge blocks of the same warnings/errors over and over!
You have also told the system to give you this information. I see you have added a kernel parameter debug --verbose which is probably why you are getting all these repeated messages. When you tell it "verbose" that means to give every little detail possible even the details that are repeats and may not add any value to the troubleshooting.

What exactly were you trying to "debug"?
RemonK wrote:
Wed Jun 09, 2021 9:20 pm
Thaaaat's very nice! Never knew about this option.. https://termbin.com/q621
To keep the information manageable, I recommend you remove debug --verbose. That way, the errors (if there are any) which are really problems can be more easily seen among all the lines in journalctl. I expect all those lines you are worried about will disappear if you remove that kernel parameter because I have not seen them in other journalctl outputs.

I also noticed you have the kernel parameter elevator=noop which I had not heard of before seeing it in your log. The only references I found were quite old except for the one answer in this thread How do I change to the noop scheduler? which indicates the parameter was removed in the 5.4 kernel block: elevator.c: Remove now unused elevator= argument . That is the kernel you are using, so you should remove the parameter.

When the output is sent to termbin, termbin has a line limit and will cut off anything past that limit. Normally, I can see much more of a start-up, but because you had not only the debug option, but also the verbose option, I did not see as much as I normally do. I think you are generating way more information than you need. That excess information is causing you unnecessary concern. That excess information also makes it harder to see if there are any actual problems. When something is a real problem, you do not need to add debug information and definitely not add debug --verbose information.

Remove the kernel parameters and then let us know if you are still seeing anything which concerns you.
A woman typing on a laptop with LM20.2 Cinnamon.
User avatar
Pjotr
Level 22
Level 22
Posts: 16678
Joined: Mon Mar 07, 2011 10:18 am
Location: The Netherlands (Holland) 🇳🇱
Contact:

Re: Disturbing things in my log! Operating arch x32 and x86-64

Post by Pjotr »

SMG wrote:
Thu Jun 10, 2021 3:28 pm
I see you have added a kernel parameter debug --verbose
That's just plain crazy. :shock:
Tip: 10 things to do after installing Linux Mint 20.2 Uma
Keep your Linux Mint healthy: Avoid these 10 fatal mistakes
Twitter: twitter.com/easylinuxtips
All in all, horse sense simply makes sense.
User avatar
Kadaitcha Man
Level 15
Level 15
Posts: 5636
Joined: Mon Aug 27, 2012 10:17 pm

Re: Disturbing things in my log! Operating arch x32 and x86-64

Post by Kadaitcha Man »

RemonK wrote:
Wed Jun 09, 2021 9:20 pm
... wine and playonlinux indeed.
And of course, therein lies the reason that you now have the 32-bit architecture installed.

Also, if you are horrified by what you see in the logs, don't read them.
[*] All kadaitcha men are liars
mikeflan
Level 7
Level 7
Posts: 1823
Joined: Sun Apr 26, 2020 9:28 am
Location: Houston, TX

Re: Disturbing things in my log! Operating arch x32 and x86-64

Post by mikeflan »

Ehh... maybe because of these millions of lines in my journal?
If I do journalctl | wc -l in a terminal I get "68050" lines in journalctl. If you happen to still have that problem system, please report what you get with journalctl | wc -l.
but since the last 2 months after i did some testing with Wine and Playonlinux it got mad! Even after i deleted complete Win and Playonlinux!
That is interesting. I start something on Playonlinux less than once a month, but it has caused me no troubles.
RemonK
Level 4
Level 4
Posts: 372
Joined: Wed Feb 06, 2019 6:32 pm
Location: Land van Umme
Contact:

Re: Disturbing things in my log! Operating arch x32 and x86-64

Post by RemonK »

SMG wrote:
Thu Jun 10, 2021 3:28 pm
You have also told the system to give you this information. I see you have added a kernel parameter debug --verbose which is probably why you are getting all these repeated messages. When you tell it "verbose" that means to give every little detail possible even the details that are repeats and may not add any value to the troubleshooting.

What exactly were you trying to "debug"?
Oh shit! I totally forgot that i had added that.. :oops: I had some problems with some network drives that refused to mount/bind at boot, so i added the debug to see what errors came from it. For normal boots it is indeed overkill, i totally forgot to remove the debug option. Well, at least that explains the excessive logging! :roll:
But in my opinion it still does not explain why the system is trying so many times to mount and unmount again and again??

SMG wrote:To keep the information manageable, I recommend you remove debug --verbose. That way, the errors (if there are any) which are really problems can be more easily seen among all the lines in journalctl. I expect all those lines you are worried about will disappear if you remove that kernel parameter because I have not seen them in other journalctl outputs.
I just removed the debug opion. Verbose i had always on, so i can see some info at booting. I have to go in a minute, but when i'm back i will boot and then post the new journal online.

SMG wrote:I also noticed you have the kernel parameter elevator=noop which I had not heard of before seeing it in your log. The only references I found were quite old except for the one answer in this thread How do I change to the noop scheduler? which indicates the parameter was removed in the 5.4 kernel block: elevator.c: Remove now unused elevator= argument . That is the kernel you are using, so you should remove the parameter.
About 3 years ago i read that noob was the best for SSD disks.. and i have 2 of them in my system and 2 rotators.. but since SSD are more sensible of wearing, i switched to noob. But i just removed that also!

SMG wrote:Remove the kernel parameters and then let us know if you are still seeing anything which concerns you.
I have some time left. Will make a boot without the parameters and post the new journal!

(anyways, thanx for looking at the journal, 2 sees more then one! ;) )
Het leven is net een kartbaan; Sensatie, adrenaline en veel te snel voorbij!
Joeptjoep - Feestboek
RemonK
Level 4
Level 4
Posts: 372
Joined: Wed Feb 06, 2019 6:32 pm
Location: Land van Umme
Contact:

Re: Disturbing things in my log! Operating arch x32 and x86-64

Post by RemonK »

Pjotr wrote:
Thu Jun 10, 2021 6:02 pm
SMG wrote:
Thu Jun 10, 2021 3:28 pm
I see you have added a kernel parameter debug --verbose
That's just plain crazy. :shock:
It is! But i only did that because of mount problems at boot with a few network drives.. i totally forgot to remove it! :oops: :mrgreen:
Het leven is net een kartbaan; Sensatie, adrenaline en veel te snel voorbij!
Joeptjoep - Feestboek
User avatar
SMG
Level 16
Level 16
Posts: 6248
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Disturbing things in my log! Operating arch x32 and x86-64

Post by SMG »

RemonK wrote:
Sat Jun 12, 2021 4:14 pm
But in my opinion it still does not explain why the system is trying so many times to mount and unmount again and again??
I'm not sure to what you are referring, but the system accesses quite a few files/locations before it remounts into read-only mode so you can use it. We'll see what is still showing in the journalctl after the kernel parameters are used.
A woman typing on a laptop with LM20.2 Cinnamon.
RemonK
Level 4
Level 4
Posts: 372
Joined: Wed Feb 06, 2019 6:32 pm
Location: Land van Umme
Contact:

Re: Disturbing things in my log! Operating arch x32 and x86-64

Post by RemonK »

The new journal online! A lot less garbage in it! :)

https://termbin.com/na6c
Het leven is net een kartbaan; Sensatie, adrenaline en veel te snel voorbij!
Joeptjoep - Feestboek
User avatar
SMG
Level 16
Level 16
Posts: 6248
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Disturbing things in my log! Operating arch x32 and x86-64

Post by SMG »

RemonK wrote:
Sun Jun 13, 2021 4:48 pm
The new journal online! A lot less garbage in it! :)

https://termbin.com/na6c
You did not remove -- verbose, so I still believe you are generating more info that you really need.

Code: Select all

jun 12 22:19:27 P3300LX kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-75-generic root=UUID=c9c0a899-526d-4e9a-bfaf-b889b88045a1 ro nosplash --verbose
Going back to your original post:
RemonK wrote:
Wed May 26, 2021 6:24 pm
I have as it seems, 2 operating architectures running on my system!? I'm not sure if that is normal, but i guess not! :oops:
Also a lot of fstab warnings about unmounting and mounting, and system mounts that can not be found or are already mounted?? As if fstab is invoked again and again...
It seems those issues are now gone.

There are some ACPI errors, but usually those can only be addressed with BIOS/UEFI updates.

These lines seems to indicate there might be a mis-match between the memory you have installed and the specs of your system. However, if you are not noticing problems in your system then this may not be a concern.

Code: Select all

jun 12 22:19:27 P3300LX kernel:  gran_size: 64K         chunk_size: 64K         num_reg: 10          lose cover RAM: 62M
jun 12 22:19:27 P3300LX kernel:  gran_size: 64K         chunk_size: 128K         num_reg: 10          lose cover RAM: 62M
jun 12 22:19:27 P3300LX kernel:  gran_size: 64K         chunk_size: 256K         num_reg: 10          lose cover RAM: 62M
jun 12 22:19:27 P3300LX kernel:  gran_size: 64K         chunk_size: 512K         num_reg: 10          lose cover RAM: 62M
jun 12 22:19:27 P3300LX kernel:  gran_size: 64K         chunk_size: 1M         num_reg: 10          lose cover RAM: 62M
jun 12 22:19:27 P3300LX kernel:  gran_size: 64K         chunk_size: 2M         num_reg: 10          lose cover RAM: 62M
jun 12 22:19:27 P3300LX kernel:  gran_size: 64K         chunk_size: 4M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 64K         chunk_size: 8M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 64K         chunk_size: 16M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 64K         chunk_size: 32M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 64K         chunk_size: 64M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 64K         chunk_size: 128M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 64K         chunk_size: 256M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel: *BAD*gran_size: 64K         chunk_size: 512M         num_reg: 10          lose cover RAM: -256M
jun 12 22:19:27 P3300LX kernel:  gran_size: 64K         chunk_size: 1G         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel: *BAD*gran_size: 64K         chunk_size: 2G         num_reg: 10          lose cover RAM: -1G
jun 12 22:19:27 P3300LX kernel:  gran_size: 128K         chunk_size: 128K         num_reg: 10          lose cover RAM: 62M
jun 12 22:19:27 P3300LX kernel:  gran_size: 128K         chunk_size: 256K         num_reg: 10          lose cover RAM: 62M
jun 12 22:19:27 P3300LX kernel:  gran_size: 128K         chunk_size: 512K         num_reg: 10          lose cover RAM: 62M
jun 12 22:19:27 P3300LX kernel:  gran_size: 128K         chunk_size: 1M         num_reg: 10          lose cover RAM: 62M
jun 12 22:19:27 P3300LX kernel:  gran_size: 128K         chunk_size: 2M         num_reg: 10          lose cover RAM: 62M
jun 12 22:19:27 P3300LX kernel:  gran_size: 128K         chunk_size: 4M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 128K         chunk_size: 8M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 128K         chunk_size: 16M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 128K         chunk_size: 32M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 128K         chunk_size: 64M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 128K         chunk_size: 128M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 128K         chunk_size: 256M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel: *BAD*gran_size: 128K         chunk_size: 512M         num_reg: 10          lose cover RAM: -256M
jun 12 22:19:27 P3300LX kernel:  gran_size: 128K         chunk_size: 1G         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel: *BAD*gran_size: 128K         chunk_size: 2G         num_reg: 10          lose cover RAM: -1G
jun 12 22:19:27 P3300LX kernel:  gran_size: 256K         chunk_size: 256K         num_reg: 10          lose cover RAM: 62M
jun 12 22:19:27 P3300LX kernel:  gran_size: 256K         chunk_size: 512K         num_reg: 10          lose cover RAM: 62M
jun 12 22:19:27 P3300LX kernel:  gran_size: 256K         chunk_size: 1M         num_reg: 10          lose cover RAM: 62M
jun 12 22:19:27 P3300LX kernel:  gran_size: 256K         chunk_size: 2M         num_reg: 10          lose cover RAM: 62M
jun 12 22:19:27 P3300LX kernel:  gran_size: 256K         chunk_size: 4M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 256K         chunk_size: 8M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 256K         chunk_size: 16M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 256K         chunk_size: 32M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 256K         chunk_size: 64M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 256K         chunk_size: 128M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 256K         chunk_size: 256M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel: *BAD*gran_size: 256K         chunk_size: 512M         num_reg: 10          lose cover RAM: -256M
jun 12 22:19:27 P3300LX kernel:  gran_size: 256K         chunk_size: 1G         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel: *BAD*gran_size: 256K         chunk_size: 2G         num_reg: 10          lose cover RAM: -1G
jun 12 22:19:27 P3300LX kernel:  gran_size: 512K         chunk_size: 512K         num_reg: 10          lose cover RAM: 62M
jun 12 22:19:27 P3300LX kernel:  gran_size: 512K         chunk_size: 1M         num_reg: 10          lose cover RAM: 62M
jun 12 22:19:27 P3300LX kernel:  gran_size: 512K         chunk_size: 2M         num_reg: 10          lose cover RAM: 62M
jun 12 22:19:27 P3300LX kernel:  gran_size: 512K         chunk_size: 4M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 512K         chunk_size: 8M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 512K         chunk_size: 16M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 512K         chunk_size: 32M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 512K         chunk_size: 64M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 512K         chunk_size: 128M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 512K         chunk_size: 256M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel: *BAD*gran_size: 512K         chunk_size: 512M         num_reg: 10          lose cover RAM: -256M
jun 12 22:19:27 P3300LX kernel:  gran_size: 512K         chunk_size: 1G         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel: *BAD*gran_size: 512K         chunk_size: 2G         num_reg: 10          lose cover RAM: -1G
jun 12 22:19:27 P3300LX kernel:  gran_size: 1M         chunk_size: 1M         num_reg: 10          lose cover RAM: 62M
jun 12 22:19:27 P3300LX kernel:  gran_size: 1M         chunk_size: 2M         num_reg: 10          lose cover RAM: 62M
jun 12 22:19:27 P3300LX kernel:  gran_size: 1M         chunk_size: 4M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 1M         chunk_size: 8M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 1M         chunk_size: 16M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 1M         chunk_size: 32M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 1M         chunk_size: 64M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 1M         chunk_size: 128M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 1M         chunk_size: 256M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel: *BAD*gran_size: 1M         chunk_size: 512M         num_reg: 10          lose cover RAM: -256M
jun 12 22:19:27 P3300LX kernel:  gran_size: 1M         chunk_size: 1G         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel: *BAD*gran_size: 1M         chunk_size: 2G         num_reg: 10          lose cover RAM: -1G
jun 12 22:19:27 P3300LX kernel:  gran_size: 2M         chunk_size: 2M         num_reg: 10          lose cover RAM: 62M
jun 12 22:19:27 P3300LX kernel:  gran_size: 2M         chunk_size: 4M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 2M         chunk_size: 8M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 2M         chunk_size: 16M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 2M         chunk_size: 32M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 2M         chunk_size: 64M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 2M         chunk_size: 128M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 2M         chunk_size: 256M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel: *BAD*gran_size: 2M         chunk_size: 512M         num_reg: 10          lose cover RAM: -256M
jun 12 22:19:27 P3300LX kernel:  gran_size: 2M         chunk_size: 1G         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel: *BAD*gran_size: 2M         chunk_size: 2G         num_reg: 10          lose cover RAM: -1G
jun 12 22:19:27 P3300LX kernel:  gran_size: 4M         chunk_size: 4M         num_reg: 10          lose cover RAM: 62M
jun 12 22:19:27 P3300LX kernel:  gran_size: 4M         chunk_size: 8M         num_reg: 10          lose cover RAM: 2M
jun 12 22:19:27 P3300LX kernel:  gran_size: 4M         chunk_size: 16M         num_reg: 10          lose cover RAM: 2M
jun 12 22:19:27 P3300LX kernel:  gran_size: 4M         chunk_size: 32M         num_reg: 10          lose cover RAM: 2M
jun 12 22:19:27 P3300LX kernel:  gran_size: 4M         chunk_size: 64M         num_reg: 10          lose cover RAM: 2M
jun 12 22:19:27 P3300LX kernel:  gran_size: 4M         chunk_size: 128M         num_reg: 10          lose cover RAM: 2M
jun 12 22:19:27 P3300LX kernel:  gran_size: 4M         chunk_size: 256M         num_reg: 10          lose cover RAM: 2M
jun 12 22:19:27 P3300LX kernel: *BAD*gran_size: 4M         chunk_size: 512M         num_reg: 10          lose cover RAM: -254M
jun 12 22:19:27 P3300LX kernel:  gran_size: 4M         chunk_size: 1G         num_reg: 10          lose cover RAM: 2M
jun 12 22:19:27 P3300LX kernel: *BAD*gran_size: 4M         chunk_size: 2G         num_reg: 10          lose cover RAM: -1022M
jun 12 22:19:27 P3300LX kernel:  gran_size: 8M         chunk_size: 8M         num_reg: 10          lose cover RAM: 62M
jun 12 22:19:27 P3300LX kernel:  gran_size: 8M         chunk_size: 16M         num_reg: 10          lose cover RAM: 6M
jun 12 22:19:27 P3300LX kernel:  gran_size: 8M         chunk_size: 32M         num_reg: 10          lose cover RAM: 6M
jun 12 22:19:27 P3300LX kernel:  gran_size: 8M         chunk_size: 64M         num_reg: 10          lose cover RAM: 6M
jun 12 22:19:27 P3300LX kernel:  gran_size: 8M         chunk_size: 128M         num_reg: 10          lose cover RAM: 6M
jun 12 22:19:27 P3300LX kernel:  gran_size: 8M         chunk_size: 256M         num_reg: 10          lose cover RAM: 6M
jun 12 22:19:27 P3300LX kernel: *BAD*gran_size: 8M         chunk_size: 512M         num_reg: 10          lose cover RAM: -250M
jun 12 22:19:27 P3300LX kernel:  gran_size: 8M         chunk_size: 1G         num_reg: 10          lose cover RAM: 6M
jun 12 22:19:27 P3300LX kernel: *BAD*gran_size: 8M         chunk_size: 2G         num_reg: 10          lose cover RAM: -1018M
jun 12 22:19:27 P3300LX kernel:  gran_size: 16M         chunk_size: 16M         num_reg: 10          lose cover RAM: 62M
jun 12 22:19:27 P3300LX kernel:  gran_size: 16M         chunk_size: 32M         num_reg: 10          lose cover RAM: 14M
jun 12 22:19:27 P3300LX kernel:  gran_size: 16M         chunk_size: 64M         num_reg: 10          lose cover RAM: 14M
jun 12 22:19:27 P3300LX kernel:  gran_size: 16M         chunk_size: 128M         num_reg: 10          lose cover RAM: 14M
jun 12 22:19:27 P3300LX kernel:  gran_size: 16M         chunk_size: 256M         num_reg: 10          lose cover RAM: 14M
jun 12 22:19:27 P3300LX kernel: *BAD*gran_size: 16M         chunk_size: 512M         num_reg: 10          lose cover RAM: -242M
jun 12 22:19:27 P3300LX kernel:  gran_size: 16M         chunk_size: 1G         num_reg: 10          lose cover RAM: 14M
jun 12 22:19:27 P3300LX kernel: *BAD*gran_size: 16M         chunk_size: 2G         num_reg: 10          lose cover RAM: -1010M
jun 12 22:19:27 P3300LX kernel:  gran_size: 32M         chunk_size: 32M         num_reg: 10          lose cover RAM: 46M
jun 12 22:19:27 P3300LX kernel:  gran_size: 32M         chunk_size: 64M         num_reg: 10          lose cover RAM: 46M
jun 12 22:19:27 P3300LX kernel:  gran_size: 32M         chunk_size: 128M         num_reg: 10          lose cover RAM: 46M
jun 12 22:19:27 P3300LX kernel:  gran_size: 32M         chunk_size: 256M         num_reg: 10          lose cover RAM: 46M
jun 12 22:19:27 P3300LX kernel: *BAD*gran_size: 32M         chunk_size: 512M         num_reg: 10          lose cover RAM: -210M
jun 12 22:19:27 P3300LX kernel:  gran_size: 32M         chunk_size: 1G         num_reg: 10          lose cover RAM: 46M
jun 12 22:19:27 P3300LX kernel: *BAD*gran_size: 32M         chunk_size: 2G         num_reg: 10          lose cover RAM: -978M
jun 12 22:19:27 P3300LX kernel:  gran_size: 64M         chunk_size: 64M         num_reg: 8          lose cover RAM: 110M
jun 12 22:19:27 P3300LX kernel:  gran_size: 64M         chunk_size: 128M         num_reg: 8          lose cover RAM: 110M
jun 12 22:19:27 P3300LX kernel:  gran_size: 64M         chunk_size: 256M         num_reg: 9          lose cover RAM: 110M
jun 12 22:19:27 P3300LX kernel:  gran_size: 64M         chunk_size: 512M         num_reg: 10          lose cover RAM: 110M
jun 12 22:19:27 P3300LX kernel:  gran_size: 64M         chunk_size: 1G         num_reg: 9          lose cover RAM: 110M
jun 12 22:19:27 P3300LX kernel:  gran_size: 64M         chunk_size: 2G         num_reg: 10          lose cover RAM: 110M
jun 12 22:19:27 P3300LX kernel:  gran_size: 128M         chunk_size: 128M         num_reg: 7          lose cover RAM: 174M
jun 12 22:19:27 P3300LX kernel:  gran_size: 128M         chunk_size: 256M         num_reg: 9          lose cover RAM: 174M
jun 12 22:19:27 P3300LX kernel:  gran_size: 128M         chunk_size: 512M         num_reg: 10          lose cover RAM: 174M
jun 12 22:19:27 P3300LX kernel:  gran_size: 128M         chunk_size: 1G         num_reg: 9          lose cover RAM: 174M
jun 12 22:19:27 P3300LX kernel:  gran_size: 128M         chunk_size: 2G         num_reg: 10          lose cover RAM: 174M
jun 12 22:19:27 P3300LX kernel:  gran_size: 256M         chunk_size: 256M         num_reg: 5          lose cover RAM: 430M
jun 12 22:19:27 P3300LX kernel:  gran_size: 256M         chunk_size: 512M         num_reg: 5          lose cover RAM: 430M
jun 12 22:19:27 P3300LX kernel:  gran_size: 256M         chunk_size: 1G         num_reg: 6          lose cover RAM: 430M
jun 12 22:19:27 P3300LX kernel:  gran_size: 256M         chunk_size: 2G         num_reg: 7          lose cover RAM: 430M
jun 12 22:19:27 P3300LX kernel:  gran_size: 512M         chunk_size: 512M         num_reg: 5          lose cover RAM: 430M
jun 12 22:19:27 P3300LX kernel:  gran_size: 512M         chunk_size: 1G         num_reg: 6          lose cover RAM: 430M
jun 12 22:19:27 P3300LX kernel:  gran_size: 512M         chunk_size: 2G         num_reg: 7          lose cover RAM: 430M
jun 12 22:19:27 P3300LX kernel:  gran_size: 1G         chunk_size: 1G         num_reg: 4          lose cover RAM: 942M
jun 12 22:19:27 P3300LX kernel:  gran_size: 1G         chunk_size: 2G         num_reg: 4          lose cover RAM: 942M
jun 12 22:19:27 P3300LX kernel:  gran_size: 2G         chunk_size: 2G         num_reg: 3          lose cover RAM: 1966M
jun 12 22:19:27 P3300LX kernel: mtrr_cleanup: can not find optimal value
jun 12 22:19:27 P3300LX kernel: please specify mtrr_gran_size/mtrr_chunk_size
I do not know if the below is because of something you may have configured?

Code: Select all

jun 12 22:19:27 P3300LX kernel: efifb: No BGRT, not showing boot graphics
Nothing else really jumped out at me. Was there something you saw in this which concerns you?
A woman typing on a laptop with LM20.2 Cinnamon.
RemonK
Level 4
Level 4
Posts: 372
Joined: Wed Feb 06, 2019 6:32 pm
Location: Land van Umme
Contact:

Re: Disturbing things in my log! Operating arch x32 and x86-64

Post by RemonK »

SMG wrote:
Sun Jun 13, 2021 8:57 pm
You did not remove -- verbose, so I still believe you are generating more info that you really need.

Code: Select all

jun 12 22:19:27 P3300LX kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-75-generic root=UUID=c9c0a899-526d-4e9a-bfaf-b889b88045a1 ro nosplash --verbose
Yes, but verbose i had already on from the beginning.. I like to see some info at boot what my system is doing!
So i was used to that amount of info, only the debug option i had totally forgotten haha :oops:
And i have still some mount errors at boot from my nas share. Had not yet time to look into it.. i will put a post-it on my monitor when i going to use the debug option again!! ;)

SMG wrote:Going back to your original post:
RemonK wrote:
Wed May 26, 2021 6:24 pm
I have as it seems, 2 operating architectures running on my system!? I'm not sure if that is normal, but i guess not! :oops:
Also a lot of fstab warnings about unmounting and mounting, and system mounts that can not be found or are already mounted?? As if fstab is invoked again and again...
It seems those issues are now gone.
Indeed! I saw one or two, but nothing worrying..

SMG wrote:There are some ACPI errors, but usually those can only be addressed with BIOS/UEFI updates.
I just recently read some info about that. It has something to do with a minor bug of storing the bits of those two ACPI values on another place than were it should be. And is indeed gone with an update. However updating a bios for such a minor bug only is not worth the risk for me as my system runs fine without them. I don't use them.
But maybe there is already a newer update with more bugfixing. I can at least look into that.

SMG wrote:These lines seems to indicate there might be a mis-match between the memory you have installed and the specs of your system. However, if you are not noticing problems in your system then this may not be a concern.

Code: Select all

jun 12 22:19:27 P3300LX kernel:  gran_size: 64K         chunk_size: 64K         num_reg: 10          lose cover RAM: 62M
jun 12 22:19:27 P3300LX kernel:  gran_size: 64K         chunk_size: 128K         num_reg: 10          lose cover RAM: 62M
jun 12 22:19:27 P3300LX kernel:  gran_size: 64K         chunk_size: 256K         num_reg: 10          lose cover RAM: 62M
jun 12 22:19:27 P3300LX kernel:  gran_size: 64K         chunk_size: 512K         num_reg: 10          lose cover RAM: 62M
jun 12 22:19:27 P3300LX kernel:  gran_size: 64K         chunk_size: 1M         num_reg: 10          lose cover RAM: 62M
jun 12 22:19:27 P3300LX kernel:  gran_size: 64K         chunk_size: 2M         num_reg: 10          lose cover RAM: 62M
jun 12 22:19:27 P3300LX kernel:  gran_size: 64K         chunk_size: 4M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 64K         chunk_size: 8M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 64K         chunk_size: 16M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 64K         chunk_size: 32M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 64K         chunk_size: 64M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 64K         chunk_size: 128M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 64K         chunk_size: 256M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel: *BAD*gran_size: 64K         chunk_size: 512M         num_reg: 10          lose cover RAM: -256M
jun 12 22:19:27 P3300LX kernel:  gran_size: 64K         chunk_size: 1G         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel: *BAD*gran_size: 64K         chunk_size: 2G         num_reg: 10          lose cover RAM: -1G
jun 12 22:19:27 P3300LX kernel:  gran_size: 128K         chunk_size: 128K         num_reg: 10          lose cover RAM: 62M
jun 12 22:19:27 P3300LX kernel:  gran_size: 128K         chunk_size: 256K         num_reg: 10          lose cover RAM: 62M
jun 12 22:19:27 P3300LX kernel:  gran_size: 128K         chunk_size: 512K         num_reg: 10          lose cover RAM: 62M
jun 12 22:19:27 P3300LX kernel:  gran_size: 128K         chunk_size: 1M         num_reg: 10          lose cover RAM: 62M
jun 12 22:19:27 P3300LX kernel:  gran_size: 128K         chunk_size: 2M         num_reg: 10          lose cover RAM: 62M
jun 12 22:19:27 P3300LX kernel:  gran_size: 128K         chunk_size: 4M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 128K         chunk_size: 8M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 128K         chunk_size: 16M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 128K         chunk_size: 32M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 128K         chunk_size: 64M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 128K         chunk_size: 128M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 128K         chunk_size: 256M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel: *BAD*gran_size: 128K         chunk_size: 512M         num_reg: 10          lose cover RAM: -256M
jun 12 22:19:27 P3300LX kernel:  gran_size: 128K         chunk_size: 1G         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel: *BAD*gran_size: 128K         chunk_size: 2G         num_reg: 10          lose cover RAM: -1G
jun 12 22:19:27 P3300LX kernel:  gran_size: 256K         chunk_size: 256K         num_reg: 10          lose cover RAM: 62M
jun 12 22:19:27 P3300LX kernel:  gran_size: 256K         chunk_size: 512K         num_reg: 10          lose cover RAM: 62M
jun 12 22:19:27 P3300LX kernel:  gran_size: 256K         chunk_size: 1M         num_reg: 10          lose cover RAM: 62M
jun 12 22:19:27 P3300LX kernel:  gran_size: 256K         chunk_size: 2M         num_reg: 10          lose cover RAM: 62M
jun 12 22:19:27 P3300LX kernel:  gran_size: 256K         chunk_size: 4M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 256K         chunk_size: 8M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 256K         chunk_size: 16M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 256K         chunk_size: 32M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 256K         chunk_size: 64M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 256K         chunk_size: 128M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 256K         chunk_size: 256M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel: *BAD*gran_size: 256K         chunk_size: 512M         num_reg: 10          lose cover RAM: -256M
jun 12 22:19:27 P3300LX kernel:  gran_size: 256K         chunk_size: 1G         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel: *BAD*gran_size: 256K         chunk_size: 2G         num_reg: 10          lose cover RAM: -1G
jun 12 22:19:27 P3300LX kernel:  gran_size: 512K         chunk_size: 512K         num_reg: 10          lose cover RAM: 62M
jun 12 22:19:27 P3300LX kernel:  gran_size: 512K         chunk_size: 1M         num_reg: 10          lose cover RAM: 62M
jun 12 22:19:27 P3300LX kernel:  gran_size: 512K         chunk_size: 2M         num_reg: 10          lose cover RAM: 62M
jun 12 22:19:27 P3300LX kernel:  gran_size: 512K         chunk_size: 4M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 512K         chunk_size: 8M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 512K         chunk_size: 16M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 512K         chunk_size: 32M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 512K         chunk_size: 64M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 512K         chunk_size: 128M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 512K         chunk_size: 256M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel: *BAD*gran_size: 512K         chunk_size: 512M         num_reg: 10          lose cover RAM: -256M
jun 12 22:19:27 P3300LX kernel:  gran_size: 512K         chunk_size: 1G         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel: *BAD*gran_size: 512K         chunk_size: 2G         num_reg: 10          lose cover RAM: -1G
jun 12 22:19:27 P3300LX kernel:  gran_size: 1M         chunk_size: 1M         num_reg: 10          lose cover RAM: 62M
jun 12 22:19:27 P3300LX kernel:  gran_size: 1M         chunk_size: 2M         num_reg: 10          lose cover RAM: 62M
jun 12 22:19:27 P3300LX kernel:  gran_size: 1M         chunk_size: 4M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 1M         chunk_size: 8M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 1M         chunk_size: 16M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 1M         chunk_size: 32M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 1M         chunk_size: 64M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 1M         chunk_size: 128M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 1M         chunk_size: 256M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel: *BAD*gran_size: 1M         chunk_size: 512M         num_reg: 10          lose cover RAM: -256M
jun 12 22:19:27 P3300LX kernel:  gran_size: 1M         chunk_size: 1G         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel: *BAD*gran_size: 1M         chunk_size: 2G         num_reg: 10          lose cover RAM: -1G
jun 12 22:19:27 P3300LX kernel:  gran_size: 2M         chunk_size: 2M         num_reg: 10          lose cover RAM: 62M
jun 12 22:19:27 P3300LX kernel:  gran_size: 2M         chunk_size: 4M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 2M         chunk_size: 8M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 2M         chunk_size: 16M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 2M         chunk_size: 32M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 2M         chunk_size: 64M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 2M         chunk_size: 128M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel:  gran_size: 2M         chunk_size: 256M         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel: *BAD*gran_size: 2M         chunk_size: 512M         num_reg: 10          lose cover RAM: -256M
jun 12 22:19:27 P3300LX kernel:  gran_size: 2M         chunk_size: 1G         num_reg: 10          lose cover RAM: 0G
jun 12 22:19:27 P3300LX kernel: *BAD*gran_size: 2M         chunk_size: 2G         num_reg: 10          lose cover RAM: -1G
jun 12 22:19:27 P3300LX kernel:  gran_size: 4M         chunk_size: 4M         num_reg: 10          lose cover RAM: 62M
jun 12 22:19:27 P3300LX kernel:  gran_size: 4M         chunk_size: 8M         num_reg: 10          lose cover RAM: 2M
jun 12 22:19:27 P3300LX kernel:  gran_size: 4M         chunk_size: 16M         num_reg: 10          lose cover RAM: 2M
jun 12 22:19:27 P3300LX kernel:  gran_size: 4M         chunk_size: 32M         num_reg: 10          lose cover RAM: 2M
jun 12 22:19:27 P3300LX kernel:  gran_size: 4M         chunk_size: 64M         num_reg: 10          lose cover RAM: 2M
jun 12 22:19:27 P3300LX kernel:  gran_size: 4M         chunk_size: 128M         num_reg: 10          lose cover RAM: 2M
jun 12 22:19:27 P3300LX kernel:  gran_size: 4M         chunk_size: 256M         num_reg: 10          lose cover RAM: 2M
jun 12 22:19:27 P3300LX kernel: *BAD*gran_size: 4M         chunk_size: 512M         num_reg: 10          lose cover RAM: -254M
jun 12 22:19:27 P3300LX kernel:  gran_size: 4M         chunk_size: 1G         num_reg: 10          lose cover RAM: 2M
jun 12 22:19:27 P3300LX kernel: *BAD*gran_size: 4M         chunk_size: 2G         num_reg: 10          lose cover RAM: -1022M
jun 12 22:19:27 P3300LX kernel:  gran_size: 8M         chunk_size: 8M         num_reg: 10          lose cover RAM: 62M
jun 12 22:19:27 P3300LX kernel:  gran_size: 8M         chunk_size: 16M         num_reg: 10          lose cover RAM: 6M
jun 12 22:19:27 P3300LX kernel:  gran_size: 8M         chunk_size: 32M         num_reg: 10          lose cover RAM: 6M
jun 12 22:19:27 P3300LX kernel:  gran_size: 8M         chunk_size: 64M         num_reg: 10          lose cover RAM: 6M
jun 12 22:19:27 P3300LX kernel:  gran_size: 8M         chunk_size: 128M         num_reg: 10          lose cover RAM: 6M
jun 12 22:19:27 P3300LX kernel:  gran_size: 8M         chunk_size: 256M         num_reg: 10          lose cover RAM: 6M
jun 12 22:19:27 P3300LX kernel: *BAD*gran_size: 8M         chunk_size: 512M         num_reg: 10          lose cover RAM: -250M
jun 12 22:19:27 P3300LX kernel:  gran_size: 8M         chunk_size: 1G         num_reg: 10          lose cover RAM: 6M
jun 12 22:19:27 P3300LX kernel: *BAD*gran_size: 8M         chunk_size: 2G         num_reg: 10          lose cover RAM: -1018M
jun 12 22:19:27 P3300LX kernel:  gran_size: 16M         chunk_size: 16M         num_reg: 10          lose cover RAM: 62M
jun 12 22:19:27 P3300LX kernel:  gran_size: 16M         chunk_size: 32M         num_reg: 10          lose cover RAM: 14M
jun 12 22:19:27 P3300LX kernel:  gran_size: 16M         chunk_size: 64M         num_reg: 10          lose cover RAM: 14M
jun 12 22:19:27 P3300LX kernel:  gran_size: 16M         chunk_size: 128M         num_reg: 10          lose cover RAM: 14M
jun 12 22:19:27 P3300LX kernel:  gran_size: 16M         chunk_size: 256M         num_reg: 10          lose cover RAM: 14M
jun 12 22:19:27 P3300LX kernel: *BAD*gran_size: 16M         chunk_size: 512M         num_reg: 10          lose cover RAM: -242M
jun 12 22:19:27 P3300LX kernel:  gran_size: 16M         chunk_size: 1G         num_reg: 10          lose cover RAM: 14M
jun 12 22:19:27 P3300LX kernel: *BAD*gran_size: 16M         chunk_size: 2G         num_reg: 10          lose cover RAM: -1010M
jun 12 22:19:27 P3300LX kernel:  gran_size: 32M         chunk_size: 32M         num_reg: 10          lose cover RAM: 46M
jun 12 22:19:27 P3300LX kernel:  gran_size: 32M         chunk_size: 64M         num_reg: 10          lose cover RAM: 46M
jun 12 22:19:27 P3300LX kernel:  gran_size: 32M         chunk_size: 128M         num_reg: 10          lose cover RAM: 46M
jun 12 22:19:27 P3300LX kernel:  gran_size: 32M         chunk_size: 256M         num_reg: 10          lose cover RAM: 46M
jun 12 22:19:27 P3300LX kernel: *BAD*gran_size: 32M         chunk_size: 512M         num_reg: 10          lose cover RAM: -210M
jun 12 22:19:27 P3300LX kernel:  gran_size: 32M         chunk_size: 1G         num_reg: 10          lose cover RAM: 46M
jun 12 22:19:27 P3300LX kernel: *BAD*gran_size: 32M         chunk_size: 2G         num_reg: 10          lose cover RAM: -978M
jun 12 22:19:27 P3300LX kernel:  gran_size: 64M         chunk_size: 64M         num_reg: 8          lose cover RAM: 110M
jun 12 22:19:27 P3300LX kernel:  gran_size: 64M         chunk_size: 128M         num_reg: 8          lose cover RAM: 110M
jun 12 22:19:27 P3300LX kernel:  gran_size: 64M         chunk_size: 256M         num_reg: 9          lose cover RAM: 110M
jun 12 22:19:27 P3300LX kernel:  gran_size: 64M         chunk_size: 512M         num_reg: 10          lose cover RAM: 110M
jun 12 22:19:27 P3300LX kernel:  gran_size: 64M         chunk_size: 1G         num_reg: 9          lose cover RAM: 110M
jun 12 22:19:27 P3300LX kernel:  gran_size: 64M         chunk_size: 2G         num_reg: 10          lose cover RAM: 110M
jun 12 22:19:27 P3300LX kernel:  gran_size: 128M         chunk_size: 128M         num_reg: 7          lose cover RAM: 174M
jun 12 22:19:27 P3300LX kernel:  gran_size: 128M         chunk_size: 256M         num_reg: 9          lose cover RAM: 174M
jun 12 22:19:27 P3300LX kernel:  gran_size: 128M         chunk_size: 512M         num_reg: 10          lose cover RAM: 174M
jun 12 22:19:27 P3300LX kernel:  gran_size: 128M         chunk_size: 1G         num_reg: 9          lose cover RAM: 174M
jun 12 22:19:27 P3300LX kernel:  gran_size: 128M         chunk_size: 2G         num_reg: 10          lose cover RAM: 174M
jun 12 22:19:27 P3300LX kernel:  gran_size: 256M         chunk_size: 256M         num_reg: 5          lose cover RAM: 430M
jun 12 22:19:27 P3300LX kernel:  gran_size: 256M         chunk_size: 512M         num_reg: 5          lose cover RAM: 430M
jun 12 22:19:27 P3300LX kernel:  gran_size: 256M         chunk_size: 1G         num_reg: 6          lose cover RAM: 430M
jun 12 22:19:27 P3300LX kernel:  gran_size: 256M         chunk_size: 2G         num_reg: 7          lose cover RAM: 430M
jun 12 22:19:27 P3300LX kernel:  gran_size: 512M         chunk_size: 512M         num_reg: 5          lose cover RAM: 430M
jun 12 22:19:27 P3300LX kernel:  gran_size: 512M         chunk_size: 1G         num_reg: 6          lose cover RAM: 430M
jun 12 22:19:27 P3300LX kernel:  gran_size: 512M         chunk_size: 2G         num_reg: 7          lose cover RAM: 430M
jun 12 22:19:27 P3300LX kernel:  gran_size: 1G         chunk_size: 1G         num_reg: 4          lose cover RAM: 942M
jun 12 22:19:27 P3300LX kernel:  gran_size: 1G         chunk_size: 2G         num_reg: 4          lose cover RAM: 942M
jun 12 22:19:27 P3300LX kernel:  gran_size: 2G         chunk_size: 2G         num_reg: 3          lose cover RAM: 1966M
jun 12 22:19:27 P3300LX kernel: mtrr_cleanup: can not find optimal value
jun 12 22:19:27 P3300LX kernel: please specify mtrr_gran_size/mtrr_chunk_size
No i don't think these mismatch my system ;) I matched them very carefully for (future) overclocking. But what i think is happening is that the kernel does not like the XMP profiles of these G.Skills. But that's my guess.. i did not yet do any testing with other profile settings yet or do any info search, because i have had not once a ram failure or system crash due to ram failure. And if it's not broken, don't fix it! :mrgreen:
I have in the past read a little bit of info over the linux kernel and such kind of mem warnings and what i understood about it was that it was not a big problem and the kernel could handle it. But don't pin me on the exact words said..
Ofcourse when i'm going to extreme overclock then i will research it more in dept!


SMG wrote:I do not know if the below is because of something you may have configured?

Code: Select all

jun 12 22:19:27 P3300LX kernel: efifb: No BGRT, not showing boot graphics
Not the slightest clue what it is??? I see this line for the first time... i have a grub bootmenu with a graphical theme, but that shows without any problems. If that has to do anything with this line??
After a quick search i think it has something to do with bootlogo's, resolution and bgrt tables... bootmenu shows ok, so i'm not worried about this one.

Code: Select all

On 17 June 2018 at 17:32, Hans de Goede <hdegoede@redhat.com> wrote:
> On systems where fbcon is configured for deferred console takeover, the
> intend is for the framebuffer to show the boot graphics (e.g a vendor
> logo) until some message (e.g. an error) is printed or a graphical
> session takes over.
>
> Some firmware however relies on the OS to show the boot graphics
> (indicated by bgrt_tab.status being 0) and the boot graphics may have
> been destroyed by e.g. the grub boot menu.
>
> This patch adds support to efifb to show the boot graphics and
> automatically enables this when fbcon is configured for deferred
> console takeover.
>
> Signed-off-by: Hans de Goede <hdegoede@redhat.com>

I have tested this code on ARM QEMU/mach-virt, and with a little tweak
(which I will post separately), the code works as expected, i.e., it
redraws the boot logo based on the contents of the BGRT table.

However, what it doesn't do is clear the screen, which means the logo
is drawn on top of whatever the boot environment left behind, and I
end up with something like this.

SMG wrote:Nothing else really jumped out at me. Was there something you saw in this which concerns you?
I just glanced over the new log, did not dive into it yet. But going to do that this week if i have some time left for the hobby. Still busy with managing a lot of things in regards of my dad.. it eats the energy out of you.
But when i find something i will post it here and tag you. If not i will mark this post as solved!
For now, thank you for your efford! :D


[edit] Something that does bother me is the 32bit architecture still active, even when i deleted Wine completely and also Playonlinux. I was hoping to ditch all the 32 bit stuff, but it is still there. Also in Synaptic after a search, it also shows 32bit stuff.. i vaguely remember turning on 32 bit architecture, but it was trail and lots of error when testing with Wine to run just 2 programs. Paintshop Pro (that was succesful) and Gene6FTP server (that was !@$^^!!!)
And after a week of annoyance, learning new combination of curse words, no nails left to bite on, i gave up!! Wine just sux! So i stick to my Windows 7 VM.
But in that week i installed, purged, installed again, purged, cleaned, installed other versions, purged again and did some other commands, i remember i had to activate the 32 bit architecture, but i can't remember what commands i used... is it possible to turn it off again?
Het leven is net een kartbaan; Sensatie, adrenaline en veel te snel voorbij!
Joeptjoep - Feestboek
User avatar
SMG
Level 16
Level 16
Posts: 6248
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Disturbing things in my log! Operating arch x32 and x86-64

Post by SMG »

RemonK wrote:
Mon Jun 14, 2021 2:32 am
I have in the past read a little bit of info over the linux kernel and such kind of mem warnings and what i understood about it was that it was not a big problem and the kernel could handle it.
This post and some subsequent ones have information I found on the *BAD*gran_size when helping someone else with a similar issue. As long as you are not noticing any issues then they probably can be ignored.
RemonK wrote:
Mon Jun 14, 2021 2:32 am
But in that week i installed, purged, installed again, purged, cleaned, installed other versions, purged again and did some other commands, i remember i had to activate the 32 bit architecture, but i can't remember what commands i used... is it possible to turn it off again?
I would assume that is possible, but I have not had any experience with doing that. Maybe someone else could help with that.
A woman typing on a laptop with LM20.2 Cinnamon.
Post Reply