• Problem with new SSD, system freezes on start Firefox.


    Hi.
    I installed a new SSD. When starting the firefox, the system freeze for about 15 seconds, firefox stops responding for about 15 seconds, the hard disk diode lights up all the time. After this time, everything returns to normal. I didn’t have such problems on my HDD on linux. I don’t have such problems on Windows10 either.0_1543692857410_1.png

  • Is that only in firefox ?

  • Today I found out that I also have these symptoms when working without a firefox. Below are the logs from today:

    10∶52∶16 kernel: audit: type=1131 audit(1543744336.628:58): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
    10∶51∶26 kernel: ata1: EH complete
    10∶51∶26 kernel: print_req_error: I/O error, dev sda, sector 217558656
    10∶51∶26 kernel: sd 0:0:0:0: [sda] tag#14 CDB: Read(10) 28 00 0c f7 ae 80 00 00 80 00
    10∶51∶26 kernel: ata1.00: configured for UDMA/133
    10∶51∶26 kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    10∶51∶26 kernel: ata1.00: status: { DRDY }
    10∶51∶26 kernel: ata1: SError: { PHYRdyChg CommWake }
    10∶51∶26 kernel: ata1.00: exception Emask 0x0 SAct 0x7010 SErr 0x50000 action 0x6 frozen
    10∶48∶09 kernel: ata1: EH complete
    10∶48∶09 kernel: ata1.00: device reported invalid CHS sector 0
    10∶48∶09 kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    10∶48∶09 kernel: ata1.00: status: { DRDY }
    10∶48∶09 kernel: ata1: SError: { PHYRdyChg CommWake }
    10∶48∶09 kernel: ata1.00: exception Emask 0x0 SAct 0x3c780000 SErr 0x50000 action 0x6 frozen
    10∶24∶14 kernel: ata1: EH complete
    10∶24∶14 kernel: ata1.00: device reported invalid CHS sector 0
    10∶24∶14 kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    10∶24∶14 kernel: ata1.00: status: { DRDY }
    10∶24∶14 kernel: ata1: SError: { PHYRdyChg CommWake }
    10∶24∶14 kernel: ata1.00: exception Emask 0x0 SAct 0x3ff8 SErr 0x50000 action 0x6 frozen
    10∶00∶02 kernel: audit: type=1131 audit(1543741202.690:56): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
    09∶59∶54 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready
    09∶59∶52 kernel: psmouse serio1: synaptics: queried min coordinates: x [1184..], y [1022..]
    09∶59∶51 kernel: audit: type=1130 audit(1543741191.946:55): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
    09∶59∶51 kernel: RTL8211E Gigabit Ethernet r8169-300:00: attached PHY driver [RTL8211E Gigabit Ethernet] (mii_bus:phy_addr=r8169-300:00, irq=IGNORE)
    09∶59∶51 kernel: IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
    09∶59∶51 kernel: audit: type=1131 audit(1543741191.876:54): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
    09∶59∶51 kernel: PM: suspend exit
    09∶59∶51 kernel: Restarting tasks ... done.
    09∶59∶51 kernel: OOM killer enabled.
    09∶59∶51 kernel: usb 3-1.3: reset high-speed USB device number 4 using ehci-pci
    09∶59∶51 kernel: ata1.00: configured for UDMA/133
    09∶59∶51 kernel: ata5.00: configured for UDMA/100
    09∶59∶51 kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
    09∶59∶51 kernel: ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
    09∶59∶51 kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    09∶59∶51 kernel: usb 3-1.1: reset high-speed USB device number 3 using ehci-pci
    09∶59∶51 kernel: ACPI: button: The lid device is not compliant to SW_LID.
    09∶59∶51 kernel: sd 0:0:0:0: [sda] Starting disk
    09∶59∶51 kernel: ACPI: EC: event unblocked
    09∶59∶51 kernel: CPU1 is up
    09∶59∶51 kernel:  cache: parent cpu1 should not be sleeping
    09∶59∶51 kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
    09∶59∶51 kernel: x86: Booting SMP configuration:
    09∶59∶51 kernel: Enabling non-boot CPUs ...
    09∶59∶51 kernel: PM: Restoring platform NVS memory
    09∶59∶51 kernel: ACPI: EC: EC started
    09∶59∶51 kernel: smpboot: CPU 1 is now offline
    09∶59∶51 kernel: Disabling non-boot CPUs ...
    09∶59∶51 kernel: PM: Saving platform NVS memory
    

    (edit: correct codetags)

  • and what is the Fstab for your ssd ?

  • # /etc/fstab: static file system information.
    #
    # Use 'blkid' to print the universally unique identifier for a
    # device; this may be used with UUID= as a more robust way to name devices
    # that works even if disks are added and removed. See fstab(5).
    #
    # <file system> <mount point>   <type>  <options>       <dump>  <pass>
    #
    UUID=b2f3b078-3647-4e72-92a4-66875ad696c5 / ext4 defaults,noatime,discard 0 1
    

    (edit: correct codetags)

  • @drk001 said in Problem with new SSD, system freezes on start Firefox.:

    print_req_error: I/O error, dev sda, sector // device reported invalid CHS sector 0

    But Windows is not on the new installed SSD?

    Looks like a failing disk, but can be also a defect cable or sata-connector…

  • @drk001 can you show the output of (from a terminal)

    LANG=C sudo lsblk -o NAME,FSTYPE,RO,RM,SIZE,STATE,OWNER,GROUP,MODE,TYPE,MOUNTPOINT,LABEL,MODEL
    
  • NAME FSTYPE RO RM   SIZE STATE OWNER GROUP MODE       TYPE MOUNTPOINT LABEL MODEL
    sda          0  0 111.8G runni             brw-rw---- disk                  CT120
    |-sda1
    |    ntfs    0  0  35.1G                   brw-rw---- part                  
    |-sda2
    |            0  0     1K                   brw-rw---- part                  
    |-sda5
    |    ntfs    0  0    62G                   brw-rw---- part                  
    |-sda6
    |    ext4    0  0  14.7G                   brw-rw---- part /                
    |sr0         0  1  1024M runni             brw-rw---- rom                   PLDS_
    

    edit: corrected code tags

  • @joekamprad yeah once i got a boot issue with antergos, i took the cable of my cdrom after it seemed fine…

    but is strange it do only firefox, you can try to remove your firefox profile

    https://askubuntu.com/questions/1058130/why-does-firefox-freeze-and-stop-my-computer

  • Unfortunately, the problem still exists even on a clean Firefox profile. A moment ago I was doing import bookmarks from .html backup to fresh firefox system again had a freeze.

  • @drk001 looks strange to me…

    sda1 = windows
    sda2 = extended partition
    sda5 = ntfs data
    sda6 = antergos

    so you choose to do not create swap on install?
    usually extended partition only takes one number of from device numbers but at yours 3+4 are missing…

    So can be also some issue with partiton …

  • The disk size for Antergos may be too small.
    Could you show the output of commands

    df -hT
    sudo fdisk -l
    
  • [[email protected] ~]$ df -hT
    System plików Typ rozm. użyte dost. %uż. zamont. na
    dev devtmpfs 1,8G 0 1,8G 0% /dev
    run tmpfs 1,8G 1,2M 1,8G 1% /run
    /dev/sda6 ext4 15G 5,0G 9,3G 36% /
    tmpfs tmpfs 1,8G 33M 1,7G 2% /dev/shm
    tmpfs tmpfs 1,8G 0 1,8G 0% /sys/fs/cgroup
    tmpfs tmpfs 1,8G 35M 1,7G 2% /tmp
    tmpfs tmpfs 353M 12K 353M 1% /run/user/1000
    /dev/sda1 fuseblk 36G 14G 22G 39% /run/media/drk001/5064730F393E6F8C
    /dev/sda5 fuseblk 62G 20G 43G 32% /run/media/drk001/3B16143C3B838676
    [[email protected] ~]$ sudo fdisk -l
    [sudo] hasło użytkownika drk001:
    Dysk /dev/sda: 111,8 GiB, bajtów: 120034123776, sektorów: 234441648
    Model dysku: CT120BX300SSD1
    Jednostki: sektorów, czyli 1 * 512 = 512 bajtów
    Rozmiar sektora (logiczny/fizyczny) w bajtach: 512 / 4096
    Rozmiar we/wy (minimalny/optymalny) w bajtach: 4096 / 4096
    Typ etykiety dysku: dos
    Identyfikator dysku: 0x9d18259e

    Urządzenie Rozruch Początek Koniec Sektory Rozmiar Id Typ
    /dev/sda1 * 2048 73521151 73519104 35,1G 7 HPFS/NTFS/exFAT
    /dev/sda2 73523198 234440703 160917506 76,7G 5 Rozszerzona
    /dev/sda5 73523200 203546623 130023424 62G 7 HPFS/NTFS/exFAT
    /dev/sda6 * 203548672 234440703 30892032 14,7G 83 Linux

    Partition 2 does not start at the border of the physical sector.

  • @drk001
    Small RAM and small disk space may cause slowness or freezing.

    I guess the problem may be caused by the small tmpfs partition /tmp. It is only 1,8GB. That means your machine’s RAM is about 4GB, right?

    You could try disabling automatic mount of /tmp:
    https://wiki.archlinux.org/index.php/Tmpfs#Disable_automatic_mount

    That would make more room for /tmp, and also release some RAM for other tasks.

  • Right. My laptop has 4GB RAM. I will try your solution. Thank you.

  • @drk001
    Any reports? :)

  • Hi.
    I reinstalled windows and antergos. The problem is still there. Below I paste reports:

    Filesystem     Type      Size  Used Avail Use% Mounted on
    dev            devtmpfs  1.8G     0  1.8G   0% /dev
    run            tmpfs     1.8G  1.2M  1.8G   1% /run
    /dev/sda5      ext4       50G  5.1G   45G  11% /
    tmpfs          tmpfs     1.8G   43M  1.7G   3% /dev/shm
    tmpfs          tmpfs     1.8G     0  1.8G   0% /sys/fs/cgroup
    tmpfs          tmpfs     1.8G   35M  1.7G   2% /tmp
    tmpfs          tmpfs     353M   32K  353M   1% /run/user/1000
    [[email protected] ~]$ sudo fdisk -l
    Disk /dev/sda: 111.8 GiB, 120034123776 bytes, 234441648 sectors
    Disk model: CT120BX300SSD1  
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes
    Disklabel type: dos
    Disk identifier: 0xb82d9ed6
    
    Device     Boot     Start       End   Sectors  Size Id Type
    /dev/sda1  *         2048 127701783 127699736 60.9G  7 HPFS/NTFS/exFAT
    /dev/sda2       127703038 234440703 106737666 50.9G  5 Extended
    /dev/sda5       127703102 234440703 106737602 50.9G 83 Linux
    
    Partition 2 does not start on physical sector boundary.
    Partition 5 does not start on physical sector boundary.
    
    
    14:14:17 kernel: print_req_error: I/O error, dev sda, sector 165765726
    14:14:17 kernel: print_req_error: I/O error, dev sda, sector 165765726
    14:14:17 kernel: print_req_error: I/O error, dev sda, sector 130160078
    14:14:17 kernel: print_req_error: I/O error, dev sda, sector 130198902
    14:14:17 kernel: print_req_error: I/O error, dev sda, sector 132312110
    14:14:17 kernel: ata1.00: status: { DRDY }
    14:14:17 kernel: ata1.00: status: { DRDY }
    14:14:17 kernel: ata1.00: cmd 61/08:f0:26:e8:a0/00:00:0a:00:00/40 tag 30 ncq dma 4096 out
             res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    14:14:17 kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    14:14:17 kernel: ata1.00: status: { DRDY }
    14:14:17 kernel: ata1.00: cmd 60/08:b0:5e:62:e1/00:00:09:00:00/40 tag 22 ncq dma 4096 in
             res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    14:14:17 kernel: ata1.00: failed command: READ FPDMA QUEUED
    14:14:17 kernel: ata1.00: status: { DRDY }
    14:14:17 kernel: ata1.00: cmd 60/a0:a8:ce:15:c2/00:00:07:00:00/40 tag 21 ncq dma 81920 in
             res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    14:14:17 kernel: ata1.00: failed command: READ FPDMA QUEUED
    14:14:17 kernel: ata1.00: status: { DRDY }
    14:14:17 kernel: ata1.00: cmd 60/a8:10:76:ad:c2/00:00:07:00:00/40 tag 2 ncq dma 86016 in
             res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    14:14:17 kernel: ata1.00: failed command: READ FPDMA QUEUED
    14:14:17 kernel: ata1.00: status: { DRDY }
    14:14:17 kernel: ata1.00: cmd 60/00:08:2e:ec:e2/01:00:07:00:00/40 tag 1 ncq dma 131072 in
             res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    14:14:17 kernel: ata1.00: failed command: READ FPDMA QUEUED
    14:14:17 kernel: ata1.00: status: { DRDY }
    14:14:17 kernel: ata1.00: cmd 61/08:00:8e:3c:a7/00:00:08:00:00/40 tag 0 ncq dma 4096 out
             res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    14:14:17 kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    14:14:17 kernel: ata1: SError: { PHYRdyChg CommWake }
    14:14:17 kernel: ata1.00: exception Emask 0x0 SAct 0x40600007 SErr 0x50000 action 0x6 frozen
    14:09:56 kernel: ata1: SError: { PHYRdyChg CommWake }
    14:09:56 kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x50000 action 0x6 frozen
    14:08:35 kernel: ACPI Error: Method parse/execution failed \_TZ.TZS0._SCP, AE_NOT_EXIST (20180810/psparse-516)
    

    (edit codeblocks)

  • looks even more like some defective hardware, Cable, Disk CPU or RAM Module…

  • On MS Windows everything works perfectly. The diagnostic programs show that the drive is ok and healthy. Problems only occur on linux.

  • @drk001
    Just an idea: do you still have the discard option in your /etc/fstab? You might want to try removing discard from there and see what happens.

    And you don’t have to put discard there, you may manually run

    sudo fstrim -Av
    

    about once a week, or put that to cron or systemd service to be run weekly.

system143 firefox43 ssd30 freezes26 Posts 23Views 571
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.