• System crashing, fail to load kernal msgs on boot, but still boots.


    While playing a game in wine, system crashes on occassion.I don’t know if it is because of wine-staging, or cpu or what, but the audio and video go dead and all I can do is reboot, but I noticed it says some things fail to load.

    Let me know what other logs I should add if any.
    but here is journal logs
    https://www.dropbox.com/s/mcs63p90q26m6v5/Logs 5-7-19.zip?dl=0

  • May 07 21:44:24 beholder kernel: EXT4-fs (sda4): error count since last fsck: 521
    May 07 21:44:24 beholder kernel: EXT4-fs (sda4): initial error at time 1555794503: ext4_validate_block_bitmap:376
    May 07 21:44:24 beholder kernel: EXT4-fs (sda4): last error at time 1557279721: ext4_validate_block_bitmap:376: inode 17040094
    
    Process 590 (ksplashqml) of user 1000 dumped core.
    
    May 07 21:38:41 beholder kernel: usb 3-1-port4: cannot disable (err = -110)
    May 07 21:38:45 beholder kernel: random: crng init done
    May 07 21:38:46 beholder kernel: hub 3-1:1.0: hub_ext_port_status failed (err = -110)
    May 07 21:38:47 beholder kernel: usb 3-1-port4: cannot reset (err = -110)
    May 07 21:38:48 beholder kernel: usb 3-1-port4: cannot reset (err = -110)
    May 07 21:38:49 beholder kernel: usb 3-1-port4: cannot reset (err = -110)
    May 07 21:38:51 beholder kernel: usb 3-1-port4: cannot reset (err = -110)
    May 07 21:38:52 beholder kernel: usb 3-1-port4: cannot reset (err = -110)
    May 07 21:38:52 beholder kernel: usb 3-1-port4: Cannot enable. Maybe the USB cable is bad?
    May 07 21:38:53 beholder kernel: usb 3-1-port4: cannot disable (err = -110)
    May 07 21:38:58 beholder kernel: hub 3-1:1.0: hub_ext_port_status failed (err = -110)
    May 07 21:38:59 beholder kernel: usb 3-1-port4: cannot reset (err = -110)
    May 07 21:39:00 beholder kernel: usb 3-1-port4: cannot reset (err = -110)
    May 07 21:39:01 beholder kernel: usb 3-1-port4: cannot reset (err = -110)
    May 07 21:39:02 beholder kernel: usb 3-1-port4: cannot reset (err = -110)
    May 07 21:39:03 beholder kernel: usb 3-1-port4: cannot reset (err = -110)
    May 07 21:39:03 beholder kernel: usb 3-1-port4: Cannot enable. Maybe the USB cable is bad?
    May 07 21:39:04 beholder kernel: usb 3-1-port4: cannot disable (err = -110)
    May 07 21:39:09 beholder kernel: hub 3-1:1.0: hub_ext_port_status failed (err = -110)
    May 07 21:39:10 beholder kernel: usb 3-1-port4: cannot reset (err = -110)
    May 07 21:39:11 beholder kernel: usb 3-1-port4: cannot reset (err = -110)
    May 07 21:39:12 beholder kernel: usb 3-1-port4: cannot reset (err = -110)
    May 07 21:39:13 beholder kernel: usb 3-1-port4: cannot reset (err = -110)
    May 07 21:39:14 beholder kernel: usb 3-1-port4: cannot reset (err = -110)
    May 07 21:39:14 beholder kernel: usb 3-1-port4: Cannot enable. Maybe the USB cable is bad?
    May 07 21:39:15 beholder kernel: usb 3-1-port4: cannot disable (err = -110)
    May 07 21:39:17 beholder kernel: usb 3-1-port4: cannot disable (err = -110)
    
    May 07 21:40:12 beholder kernel: EXT4-fs error (device sda4): ext4_validate_block_bitmap:376: comm Enpass: bg 2277: bad block bitmap checksum
    May 07 21:40:13 beholder kernel: EXT4-fs error (device sda4): ext4_validate_block_bitmap:376: comm Enpass: bg 2278: bad block bitmap checksum
    

    may not rebooted after a kernel update,…,

    or a real hardware issue with RAM, CPU or HD

  • Thanks Joe,
    I got to looking at the boot screen and saw more of what the line that said

    "[FAILED] Failed to start Load Kernel Modules.
    See ‘systemctl status systemd-modules-load.service’ for details. "
    

    I looked that part up and found
    https://forum.antergos.com/topic/7022/failed-to-load-start-kernel-modules

    Turns out the same stuff happened there.
    I uninstalled virtualbox for now, rebooted, the error disappeared along with
    all the stuff it said it was loading, I kinda like that screen lol, but I’m wondering if when it does show up, it means something might be wrong? idk

    I might have put something in wrong when I redid virtualbox

    All seems good now I guess.

    [[email protected] ~]$ systemctl status systemd-modules-load.service
    [sudo] password for major: 
    ● systemd-modules-load.service - Load Kernel Modules
       Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static; vendor preset: disabled)
       Active: active (exited) since Thu 2019-05-09 20:11:13 EDT; 1min 49s ago
         Docs: man:systemd-modules-load.service(8)
               man:modules-load.d(5)
      Process: 221 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, status=0/SUCCESS)
     Main PID: 221 (code=exited, status=0/SUCCESS)
    
    May 09 20:11:13 beholder systemd-modules-load[221]: Inserted module 'crypto_user'
    May 09 20:11:13 beholder systemd-modules-load[221]: Inserted module 'sg'
    May 09 20:11:13 beholder systemd[1]: Started Load Kernel Modules.
    Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
    

    Anyway, looked at the last journal, and did find this

    May 09 20:11:17 beholder kernel: EXT4-fs (sda4): warning: mounting fs with errors, running e2fsck is recommended
    
    idk what this means though
    beholder systemd-udevd[315]: Process '/usr/bin/alsactl restore 0' failed with exit code 99.
    

    I need to know how/where to properly do the e2fsck.
    It would seem it won’t run while mounted I guess bc it’s fixing disk errors like chkdsk did for win, but want to do it right without breaking stuff and not sure where to do it lol

    I’ll mark this solved and try to pay more attention when I revisit the virtualbox setup, it always seems to give me issues someplace haha

  • @Firespray said in System crashing, fail to load kernal msgs on boot, but still boots.:

    e2fsck

    https://linux.die.net/man/8/e2fsck
    https://wiki.archlinux.org/index.php/Fsck
    http://polarhome.com/service/man/?qf=FSCK&tf=2&of=Archlinux&sf=8

    if partition is not used by your system (e.g. / rootpartition or /home /boot e.t.c…) then you can simple run:
    sudo fsck.ext4 /dev/sda4

    If partition /dev/sda4 is one of the system partitions you may better boot with LiveISO and run the command from there.

  • @joekamprad said in System crashing, fail to load kernal msgs on boot, but still boots.:

    May 07 21:39:14 beholder kernel: usb 3-1-port4: Cannot enable. Maybe the USB cable is bad?

  • Yes thankyou for reminding me of that, …I have bay device for laptop hard drives, switched ports, the error port number changed so either bay device failing or plug coming out of back…I unplugged for now, error gone.

    I had another shutdown of wine game last night, I did reinstall 39xx-dkms drivers after that, last thing I did before today.

    On this reboot after unplugging usb bay device, I just started searching for failed and found this to start with…
    should I start a different thread for help to track these down?

    kernel: nvidia: module verification failed: signature and/or required key missing - tainting kernel
    

    current journal
    https://www.dropbox.com/s/crhuy64uewghwzg/journal?dl=0

    shutting down now to run e2fsck, also thanks for that, I could only find info on fsck and better to ask dumb question than to risk f’ing something up :P

system144 fail20 crashing13 kernal1 Posts 6Views 136
Log in to reply
Bloom Email Optin Plugin

Looks like your connection to Antergos Community Forum was lost, please wait while we try to reconnect.