Which release of your OS (Operating System)?
24.04 LTS
Framework laptop (11th or 12th generation Framework laptop) are you asking for support with?
12th gen
If this is a Linux issue, please use the Linux tag or at least put Linux in the title.
Done
I use my old intel 12th gen as a Homeserver and it happens irregularly that the server freezes.
No SSH possible every docker container unreachable, etc.
Only thing that worked so far is to go into the server room and hold down the power button to do a hard reset.
I connected a screen and saw the message “cros_ec_lpcs cros_ec_lpcs.0 packet too long” that I also found in the journalct -b-1of the last boot.
So I stumbled over this three (only two because of max links per post, will add it in a comment), threads here:
cros_ec_lpcslooks like a kernel driver for chrome os because I can’t think of a thing on my server using chrome.
So I’m still a little bit confused in what could be the reason for the freeze and even more confused on how to fix that.
BIOS is Version 3.08
EDIT: Pinging works
EDIT2: Login on the device works. Looking into restarting the network manager and see if that might help
EDIT3: restarting network interfaces etc. did not help. Even worse eth0 interface now has no ip anymore. it had one before the restart (Oh and I use the framework ethernet adapter module to connect the server to the network)
Here the journalctl log for the timeframe the issues should happend… ok maybe the cifs vfs share that can’t be reconnected… (my NAS)
But why should it happen now, it worked for weeks already without any problem.
Jul 27 14:35:01 homework CRON[48289]: pam_unix(cron:session): session closed for user root
Jul 27 14:35:01 homework CRON[48290]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jul 27 14:35:01 homework CRON[48289]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
Jul 27 14:25:01 homework CRON[47544]: pam_unix(cron:session): session closed for user root
Jul 27 14:25:01 homework CRON[47545]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jul 27 14:25:01 homework CRON[47544]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
Jul 27 14:21:11 homework kernel: CIFS: VFS: \\192.168.1.101 has not responded in 180 seconds. Reconnecting...
Jul 27 14:17:01 homework CRON[46931]: pam_unix(cron:session): session closed for user root
Jul 27 14:17:01 homework CRON[46932]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Jul 27 14:17:01 homework CRON[46931]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
Jul 27 14:15:01 homework CRON[46790]: pam_unix(cron:session): session closed for user root
Jul 27 14:15:01 homework CRON[46791]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jul 27 14:15:01 homework CRON[46790]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
Jul 27 14:12:38 homework kernel: i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device
Jul 27 14:12:38 homework kernel: Console: switching to colour frame buffer device 80x30
Jul 27 14:12:38 homework kernel: fbcon: i915drmfb (fb0) is primary device
Jul 27 14:12:38 homework kernel: EDID block 0 (tag 0x00) checksum is invalid, remainder is 164
Jul 27 14:12:38 homework systemd-logind[944]: Watching system buttons on /dev/input/event14 (DP-4)
Jul 27 14:12:38 homework kernel: input: DP-4 as /devices/pci0000:00/0000:00:02.0/rc/rc0/input20
Jul 27 14:12:38 homework kernel: rc rc0: DP-4 as /devices/pci0000:00/0000:00:02.0/rc/rc0
Jul 27 14:12:38 homework kernel: Registered IR keymap rc-cec
Jul 27 14:12:38 homework kernel: [00] BAD 00 38 4c 1e 53 11 00 0a 20 20 20 20 20 20 01 92
Jul 27 14:12:38 homework kernel: [00] BAD 37 33 50 4c 50 48 0a 20 20 20 20 20 00 00 00 fd
Jul 27 14:12:38 homework kernel: [00] BAD 31 32 33 36 30 30 30 34 35 34 00 00 00 fc 00 32
Jul 27 14:12:38 homework kernel: [00] BAD 45 00 56 50 21 00 00 1e 00 00 00 ff 00 41 55 31
Jul 27 14:12:38 homework kernel: [00] BAD 01 01 01 01 01 01 02 3a 80 18 71 38 2d 40 58 2c
Jul 27 14:12:38 homework kernel: [00] BAD 00 50 54 bd 4b 00 d1 c0 81 80 95 0f 95 00 b3 00
Jul 27 14:12:38 homework kernel: [00] BAD 24 16 01 03 80 3c 22 78 2a ca 45 a4 56 4b 9c 25
Jul 27 14:12:38 homework kernel: [00] BAD 00 ff ff ff ff ff ff 00 41 0c a8 08 c6 01 00 00
Jul 27 14:12:38 homework kernel: EDID block 0 (tag 0x00) checksum is invalid, remainder is 164
the funny part is I don’t mount the cifs share manually.
It is defined in the docker-compose file(s)
example:
To help with any diagnosis, one would need the entire kernel logs.
dmesg or journalctl -b
Ideally, when it is actually happening, before a reboot.
You said you could login, ping, but no other network traffic worked.
Also, which slots cards and devices are attached to the FW13 and which slots are they in.
After collecting the logs, see if removing the ethernet card and re-inserting it helps it come back to life without rebooting.
@James3 removing and reinserting the ethernet card helps.
On the top right is a USB-C slot card for power
On the bottom right is the ethernet card
On the top left is an HDMI card
On the bottom left is a USB-A slot card
Can’t paste full dmesg and journalctl because it would be over the text limit and file upload is not allowed for files that are not images. ò.o
If removing and reinserting the ethernet card helps, I would point the problem more towards a Linux driver bug. Maybe the hardware buffers of the ethernet card overflow or some other error occurs and the Linux driver is not recovering.
I would probably suggest raising a Linux kernel bug in the “network” drivers area.
I have seem symptoms similar to yours with real servers (i.e. not laptops) where it responds to ping, but one cannot ssh to the server.
It is because I have seen it elsewhere that I suggest raising the Linux kernel bug.
While I have seen some usb related problems on my FW16, they are all associated with AMD mainboards, and I have not seen usb related problems raised on Intel based FW13s, so I don’t think it is a USB specific issue, its more a network driver issue.
It might be the configured speed of the network adapter, after changing the link mode from 2500baseT/Full to 1000baseT/Full the problem vanished until now. Not 100% shure it is the culprit but if i don’t write any updates here in the next days it looks like it was solved.
for people having the same problem.
Install ethtool
sudo ethtool -s <interfaceName> autoneg on speed 1000 duplex full