Solved!
Go to SolutionDell Latitude 7220 Hanging and Force Shutdown
titude 7220 Rugged Extreme freezes in both Windows and Linux; touch firmware A2_N and ACPI resume errors
I am experiencing intermittent freezes on a Dell Latitude 7220 Rugged Extreme Tablet. The same type of freezing also occurred when the tablet was running Windows, so this does not appear to be limited to my current Linux installation.
System details:
- Dell Latitude 7220 Rugged Extreme Tablet
- Intel Core i5-8365U
- Intel UHD Graphics 620 (PCI ID 8086:3ea0)
- BIOS 1.52.0, dated June 8, 2026
- Current OS: CachyOS Linux
- Kernel: 6.18.52-1-cachyos-lts
- Mesa: 26.2.3
- Desktop/compositor: Niri 26.04 (Wayland)
On September 28, 2026, the tablet froze twice:
1. Once while a browser and FreeTube were open.
2. Once with only one browser open.
3. On record there are a total of 8 hangs where even the audio would freeze
All incidents ended in an unclean shutdown. A WebGL sample from webglsamples.org was subsequently tested and did not reproduce the freeze.
Checks performed after the incidents:
- No kernel panic, OOM event, i915 GPU hang/reset, machine-check error, PCIe AER error, NVMe error, or Btrfs device error was recorded before the logs stopped.
- NVMe SMART health passed with zero media/data-integrity errors and zero error-log entries.
- Btrfs device statistics are all zero.
- Temperatures were normal during subsequent testing.
- There was ample available RAM during the WebGL test.
There are repeatable ACPI firmware errors after resume:
```
ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [DRQL] at bit offset/length 136/8 exceeds size of target Buffer (128 bits)
ACPI Error: Aborting method \\_SB.PCI0.LPCB.SIO1.DSRS due to previous error
ACPI Error: Aborting method \\_SB.PCI0.LPCB.UAR1._SRS due to previous error
serial 00:01: activation failed
serial 00:01: PM: failed to resume: error -5
```
One of the Linux freezes happened on a boot that had resumed from suspend earlier; the other boot had not been suspended.
I also found that the touchscreen currently identifies as:
```text
eGalaxTouch P81X84 A020 vA2_N k4.18.201
USB ID 0eef:c002
```
Dell article 000207232 says Latitude 7220 touch-panel firmware older than A4N can lose touch input after reboot or resume because of a communication problem between the MCU and touch-controller IC. Dell provides the Windows-only `Dell Touch Firmware Update Tool-A4_N_ZPE.exe` (driver ID J2JC4).
There are also existing Dell Community reports involving multiple Latitude 7220 units hanging despite passing ePSA, and another fleet report involving random power-offs and BIOS over-current-protection events.
Could Dell please advise:
1. Is there a known Latitude 7220 firmware, embedded-controller, touch-controller, power, or Intel graphics issue that can cause complete intermittent freezes in both Windows and Linux?
2. Is touchscreen firmware A2_N definitely affected by article 000207232, and is A4N the correct update for this particular P81X84/0eef:c002 panel?
3. Is there an operating-system-independent method of applying the A4N touch firmware, or must Windows be installed?
4. Are the `DRQL`, `SIO1.DSRS`, and `UAR1._SRS` ACPI resume errors known for BIOS 1.52.0 on this model?
5. Which BIOS Event Log entries, extended ePSA tests, or Dell diagnostics should be collected to determine whether the tablet needs motherboard, power-system, or touchscreen service/replacement?
Relevant Dell pages:
- Touchscreen advisory: https://www.dell.com/support/kbdoc/en-us/000207232/touch-screen-function-lost-after-system-s4-reboot-on-rugged-latitude-7220-computers
- A4N touch firmware: https://www.dell.com/support/home/en-ca/drivers/driversdetails?driverid=j2jc4
- Existing Latitude 7220 hang report: https://www.dell.com/community/en/conversations/latitude/latitude-7220-rugged-extreme-tablet/647f9bcdf4ccf8a8defc484b
- Existing Latitude 7220 power-off report: https://www.dell.com/community/en/conversations/latitude/latitu
de-rugged-extreme-7220-over-current-protection/65f7dbae5c8e1a0ebcb05910
12
0
Posted September 30th, 2026 11:57
I apologize for reposting this issue, but the previous description felt inaccurate so I wanted to edit it.
10
1
Posted October 1st, 2026 06:36
I had this exact kind of hard freeze on my Latitude running Linux a while back, even the audio would lock up and the only way out was holding the power button. What fixed it for me was flashing the touch firmware, mine was also sitting on an old version. The updater is Windows only unfortunately, so I ran it from a Windows To Go USB stick and never actually installed Windows on the machine. After that the random hangs stopped.
Your A2_N is pretty old so I would do that one first. And while you are in there double check you are on the latest BIOS too. If it still hangs after both of those, run the full ePSA pre-boot diagnostics, support is going to ask for that anyway if you open a case.
The ACPI resume errors you are seeing look like BIOS quirks more than the actual cause to me. My money is on the touch firmware.
7
1
Posted October 5th, 2026 20:03
@nl1222 The bios on dell's website for this equipmetn is probably out of date. They kill support for older stuff and quit posting compatible updates for their bios' too. You should be able to run at least "2.43.3". I have it now on dell Latitude 7212. Don't downgrade. Don't force it if it won't go. It's not the fix, i promise.
8
1
Posted October 5th, 2026 20:06
@StarLitHunter Also, don't forget to update your initcpio after adding fixes to stuff. Arch is: sudo mkinitcpio -P. I dunno for deb or fedora etc.
7
0
Posted October 5th, 2026 20:51
@StarLitHunter this probably is the answer because you are right I was actually using Anker power station to charge my PC via type c, and I guess that was causing multiple unstable charges/ discharges until it crashes?
Somehow you nailed it actually (I can only guess you are right), for the other recommended solutions you suggested that I could try I think it's definitely worth it. I am on cachyos, which is interesting to see that it even crashes on cachyos despite having the most recent and supported kernels and packages for the Intel I had, but worth a shot!
9
0
Posted October 5th, 2026 20:52
@benalvi I might have mentioned this before in another comment but basically I'm stuck on not being able to update my bios and other firmware via dell launcher assistance for some reason when I reboot it shows as if I am downgrading. Another comment pointed out that it's not the solution, in either case.
StarLitHunter
1 Rookie
•
4 Posts
•
14 Points
7
2
Posted October 5th, 2026 19:50
Hey. The critical thing here is power management. My theory is that you're experiencing mini-brownouts on your CPU because intel integrated graphics uses your cpu as a gpu, and most operating systems seem to anticipate that you have two separate chip sets for both. Your device is being under-powered for the sake of energy efficiency. My advice is: #1, from TTY, if it's more stable for you, find the right .conf file that allows boot customization. In Arch linux, I have /etc/kernel/cmdline. in that file i placed the parameters (in the same line as the other stuff, one space to separate) i915.enable_psr=0 (this disables panel self refresh [notoriously glitchy]) i915.enable_dc=0(this disables display C-states which messes with timing). Also, I'm using the Latitude 7212. It's a bit older, so i found it's way more stable running graphics through mesa-amber instead of just mesa.
Second thing, i'd install tlp, tlp-pd, tlp-rdw, and tlpui. Then sudo systemctl enable tlp.services --now
This is an advanced power management package designed to help with intel hardware. If you read the documentation on the tlp webpage: https://linrunner.de/tlp/index.html you can use the relatively large amounts of configuration options to custom tune your hardware power profile. I suggest juicing up your intel chipset where possible. But, if you're stable, don't mess with success.
If it works, don't tell Microsoft. They'll get grumpy and buy more legislation.
Dell makes a solid piece of hardware. All the reason I'm glad you're going for Linux.
(edited)