[REPAIRED]brocken touchpad/fsck

jl2 · 2023-05-13 07:45:46

Hi

I have a slow boot process since yesterday.

Startup finished in 7.098s (firmware) + 3.457s (loader) + 382ms (kernel) + 730ms (initrd) + 25.349s (userspace) = 37.018s 
graphical.target reached after 25.349s in userspace.

I usually had ~5s in userspace until graphical.target is reached.

systemd-analyse critical-chain:

The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target @25.349s
└─sddm.service @25.348s
  └─systemd-user-sessions.service @25.339s +6ms
    └─network.target @25.317s
      └─NetworkManager.service @25.265s +51ms
        └─dbus.service @24.990s +242ms
          └─basic.target @24.986s
            └─systemd-pcrphase-sysinit.service @24.948s +37ms
              └─sysinit.target @24.946s
                └─systemd-update-utmp.service @24.937s +8ms
                  └─systemd-tmpfiles-setup.service @24.887s +48ms
                    └─local-fs.target @24.826s
                      └─run-credentials-systemd\x2dtmpfiles\x2dsetup.service.mount @24.891s
                        └─local-fs-pre.target @228ms
                          └─lvm2-monitor.service @164ms +63ms
                            └─dm-event.socket @137ms
                              └─system.slice
                                └─-.slice

systemctl status local-fs-pre.target :

● local-fs-pre.target - Preparation for Local File Systems
     Loaded: loaded (/usr/lib/systemd/system/local-fs-pre.target; static)
     Active: active since Sat 2023-05-13 09:16:16 CEST; 20min ago
       Docs: man:systemd.special(7)

May 13 09:16:16 ArchLinux systemd[1]: Reached target Preparation for Local File Systems.

sudo journalctl -b 0: http://0x0.st/HNB8.txt

I don't know if this is relevant, but my EFI parttition has this warning:
part of sudo dmesg --level 4:

[   25.989857] FAT-fs (nvme0n1p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.

sudo fsck.fat -r /dev/nvme0n1p1:

fsck.fat 4.2 (2021-01-31)
Seek to 335951360:Invalid argument

Last edited by jl2 (2023-06-02 16:53:10)

seth · 2023-05-13 15:13:29

May 13 09:16:17 ArchLinux kernel: usbhid: USB HID core driver
May 13 09:16:17 ArchLinux systemd[1]: Mounting /efi...
May 13 09:16:21 ArchLinux kernel: i2c_hid_acpi i2c-SYNA2BA6:00: failed to reset device: -61
May 13 09:16:27 ArchLinux kernel: i2c_hid_acpi i2c-SYNA2BA6:00: failed to reset device: -61
May 13 09:16:33 ArchLinux kernel: i2c_hid_acpi i2c-SYNA2BA6:00: failed to reset device: -61
May 13 09:16:40 ArchLinux kernel: i2c_hid_acpi i2c-SYNA2BA6:00: failed to reset device: -61
May 13 09:16:41 ArchLinux kernel: i2c_hid_acpi i2c-SYNA2BA6:00: can't add hid device: -61
May 13 09:16:41 ArchLinux kernel: i2c_hid_acpi: probe of i2c-SYNA2BA6:00 failed with error -61
May 13 09:16:41 ArchLinux kernel: FAT-fs (nvme0n1p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
May 13 09:16:41 ArchLinux systemd[1]: Mounted /efi.

fsck the drive but the delay seems to be from the i2c device (touchpad) which doesn't respond.
=> Does the touchpad work? Does the device have some touchpad toggle key/switch?
Is there a parallel windows installation?

May 13 09:16:17 ArchLinux kernel: ccp 0000:33:00.2: ccp: unable to access the device: you might be running a broken BIOS.

May 13 09:16:15 archlinux kernel: DMI: LENOVO 82QF/LNVNB161216, BIOS K5CN39WW 03/08/2023

Did you recently update the BIOS?

Edit:

Seek to 335951360:Invalid argument

lsblk -f

Edit #2:
also

fdisk -l nvme0n1

Last edited by seth (2023-05-13 15:19:50)

jl2 · 2023-05-13 18:57:37

you're good: I did update my bios 2-3 days ago and the touchpad doesn't work since (at least) yesterday.
It doesn't seam to have happened to other people with the same laptop: https://github.com/tomsom/yoga-linux/issues/26
I forgot about it, didn't use it all morning + waiting a day or two sometimes fixes stuff.
do you think it's a broken touchpad or a loose connector?

lsblk -f:

NAME    FSTYPE FSVER LABEL    UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
zram0                                                                             [SWAP]
nvme0n1                                                                           
├─nvme0n1p1
│       vfat   FAT32 SYSTEM_DRV
│                             EEAA-7941                             106.2M    67% /efi
├─nvme0n1p2
│                                                                                 
├─nvme0n1p3
│       ntfs         Windows-SSD
│                             2C2EAD422EAD0644                        153G    46% /windows
└─nvme0n1p4
        ext4   1.0   root     5263a2c3-7f15-42d3-8081-45b17b060b0f  117.7G    33% /

fdisk -l nvme0n1:

Disk /dev/nvme0n1: 476.94 GiB, 512110190592 bytes, 1000215216 sectors
Disk model: UMIS RPJTJ512MGE1QDY                    
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 4453F4E3-7A50-490F-AC8E-DDE850991FD3

Device             Start        End   Sectors   Size Type
/dev/nvme0n1p1      2048     657407    655360   320M EFI System
/dev/nvme0n1p2    657408     690175     32768    16M Microsoft reserved
/dev/nvme0n1p3    690176  597561343 596871168 284.6G Microsoft basic data
/dev/nvme0n1p4 597561344 1000214527 402653184   192G Linux filesystem

I also don't know if it's related to this but I have UKI images disappearing from my EFI partition (lucky I have fallback )
EDIT: fsck fails (output in OP)

Last edited by jl2 (2023-05-13 18:59:43)

seth · 2023-05-13 19:07:45

I think it's maybe the BIOS update.
Or maybe not:

Since there's a windows installation, does the touchpad work there?
Also see the 3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

The size of the efi partition and FS look sane, the FS itself might have taken a hit - or is in use by windows.
Try to check it there while ensuring that fast-start is (still) disabled.

I also don't know if it's related

Yes, the FS is certainly corrupted.
This might also be related to the nvme, do you mount anything there "discard"?

jl2 · 2023-05-14 04:57:32

no, the touchpad doesn't work there (it also doesn't work in the bios settings)
boot time is normal again. the error has changed from:

May 13 09:16:21 ArchLinux kernel: i2c_hid_acpi i2c-SYNA2BA6:00: failed to reset device: -61
May 13 09:16:27 ArchLinux kernel: i2c_hid_acpi i2c-SYNA2BA6:00: failed to reset device: -61
May 13 09:16:33 ArchLinux kernel: i2c_hid_acpi i2c-SYNA2BA6:00: failed to reset device: -61
May 13 09:16:40 ArchLinux kernel: i2c_hid_acpi i2c-SYNA2BA6:00: failed to reset device: -61
May 13 09:16:41 ArchLinux kernel: i2c_hid_acpi i2c-SYNA2BA6:00: can't add hid device: -61
May 13 09:16:41 ArchLinux kernel: i2c_hid_acpi: probe of i2c-SYNA2BA6:00 failed with error -61

to:

[    1.414294] i2c_designware AMDI0010:00: i2c_dw_handle_tx_abort: lost arbitration

already have visited that link thrice: fastboot and hibernation are both disabled since ages.
with discard: I deleted some partitionons (my swap partition) some time ago (2 months or such) with gparted
should I copy down the partition, make a new fs and copy it all onto it again?

EDIT: i remember the touchpad being before the bios update; I'm pretty sure I used my touchpad on friday morning.

Last edited by jl2 (2023-05-14 05:10:52)

seth · 2023-05-14 06:26:07

boot time is normal again. the error has changed from:

What changed interim? But apparently the touchpad caused the timeout?

it also doesn't work in the bios settings … the touchpad being before the bios update

Can you downgrade the BIOS?

with discard: I deleted some partitionons

https://wiki.archlinux.org/title/Solid_ … nuous_TRIM
https://wiki.archlinux.org/title/Solid_ … e#Discards - despite the discussion, note the red warning.

jl2 · 2023-05-14 16:10:19

discard: cat /etc/fstab:

# <device>                                                                      <dir>       <type>           <options>       <dump>  <fsck>

# /dev/nvme0n1p1 boot
UUID=EEAA-7941          /efi            vfat            rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro        0 2

# /dev/nvme0n1p3 Windows
UUID=2C2EAD422EAD0644   /windows        ntfs            uid=1000,gid=1000,rw,nosuid,nodev   0 0

# zram
/dev/zram0      none    swap    defaults        0 0

so no.

boot time is normal again. the error has changed from:

I didn't change anything. just realized it changed itself. boot time shortened itself by 24s. whatever you are asking here.

Does downgrading the bios only work from within the bios settings?

Last edited by jl2 (2023-05-14 16:10:52)

seth · 2023-05-14 16:21:27

I didn't change anything. just realized it changed itself.

Is the "Volume was not properly unmounted. Some data may be corrupt. Please run fsck." warning still present?

Does downgrading the bios only work from within the bios settings?

That's system sepcific, you'll apparently have to disable the secure rollback prevention in the BIOS - but I don't know that for certain.

jl2 · 2023-05-14 16:39:19

Is the "Volume was not properly unmounted. Some data may be corrupt. Please run fsck." warning still present

yes.

the touchpad error now changed to:

[    2.436633] i2c_designware AMDI0010:00: controller timed out

In the bios i found the 'enable bios downgrade/rollback' feature. it's enabled, but i'll probably have to dig in to downgrading.

EDIT: i can't see my old bios version: https://pcsupport.lenovo.com/us/en/prod … IOS%2FUEFI
EDIT2: I am not motivated to downgrade my bios with unofficial stuff.
now the error changed again:

 [    1.469177] i2c_hid_acpi i2c-SYNA2BA6:00: failed to change power setting.
[    7.574675] i2c_hid_acpi i2c-SYNA2BA6:00: failed to reset device: -61
[    7.574934] i2c_hid_acpi i2c-SYNA2BA6:00: failed to change power setting.
[   13.718374] i2c_hid_acpi i2c-SYNA2BA6:00: failed to reset device: -61
[   19.862662] i2c_hid_acpi i2c-SYNA2BA6:00: failed to reset device: -61
[   20.870377] i2c_hid_acpi i2c-SYNA2BA6:00: can't add hid device: -61

but i think this is getting irrelevant, so I'll stop posting the changes

Last edited by jl2 (2023-05-14 17:19:15)

seth · 2023-05-14 19:59:51

It is relevant in that both are inidcative of the failing touchpad, but since it's not available in the BIOS or, more importantly, windows unfortunately not more.
You might have to wait for another FW update to fix it again (just to be sure: the internal keyboard still works? The thing isn't just in tablet mode?)

jl2 · 2023-05-15 05:43:29

Yes, it does. And since my pen broke i don't use tablet mode.
EDIT: could we at least try to fix the EFI partition?

Last edited by jl2 (2023-05-15 13:37:42)

jl2 · 2023-06-02 15:47:09

So, my laptop is back from the repair. some broken copper wire.
i still have this:

[    2.343368] FAT-fs (nvme0n1p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.

should I copy off/delete/remake partiton/copy back? will this break windows?

seth · 2023-06-02 15:50:13

Simply fsck the partition - unless you're rebooting w/ the power button the partition should™ afterwards get cleanly unmounted and the error no longer show up.
Edit: sorry, been a while.
Since you've a parallel windows you could try to have it chkdsk the partition first.

Last edited by seth (2023-06-02 16:01:36)

jl2 · 2023-06-02 16:52:40

yeah, fixed it. thanks for helping, seth.

Arch Linux

#1 2023-05-13 07:45:46

[REPAIRED]brocken touchpad/fsck

#2 2023-05-13 15:13:29

Re: [REPAIRED]brocken touchpad/fsck

#3 2023-05-13 18:57:37

Re: [REPAIRED]brocken touchpad/fsck

#4 2023-05-13 19:07:45

Re: [REPAIRED]brocken touchpad/fsck

#5 2023-05-14 04:57:32

Re: [REPAIRED]brocken touchpad/fsck

#6 2023-05-14 06:26:07

Re: [REPAIRED]brocken touchpad/fsck

#7 2023-05-14 16:10:19

Re: [REPAIRED]brocken touchpad/fsck

#8 2023-05-14 16:21:27

Re: [REPAIRED]brocken touchpad/fsck

#9 2023-05-14 16:39:19

Re: [REPAIRED]brocken touchpad/fsck

#10 2023-05-14 19:59:51

Re: [REPAIRED]brocken touchpad/fsck

#11 2023-05-15 05:43:29

Re: [REPAIRED]brocken touchpad/fsck

#12 2023-06-02 15:47:09

Re: [REPAIRED]brocken touchpad/fsck

#13 2023-06-02 15:50:13

Re: [REPAIRED]brocken touchpad/fsck

#14 2023-06-02 16:52:40

Re: [REPAIRED]brocken touchpad/fsck

Board footer