<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Meteor-Lake on Angel Sulev | Cybersecurity + Agentic AI</title><link>https://ansulev.com/tags/meteor-lake/</link><description>Recent content in Meteor-Lake on Angel Sulev | Cybersecurity + Agentic AI</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 18 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ansulev.com/tags/meteor-lake/index.xml" rel="self" type="application/rss+xml"/><item><title>Fixing Suspend/Resume on Meteor Lake: One Kernel Parameter, One Year Too Late</title><link>https://ansulev.com/blog/meteor-lake-suspend-fix-psr2-sel-fetch/</link><pubDate>Thu, 18 Jun 2026 00:00:00 +0000</pubDate><guid>https://ansulev.com/blog/meteor-lake-suspend-fix-psr2-sel-fetch/</guid><description>&lt;p&gt;I held the power button down more than 300 times on this machine.&lt;/p&gt;
&lt;p&gt;ThinkPad P1 Gen7, Intel Core Ultra 9 185H (Meteor Lake), kernel 6.x through 7.x. Every suspend attempt ended the same way: freeze on entry or black screen on resume, then a hard shutdown. Over a year of real work on a machine that couldn&amp;rsquo;t sleep. That is not a minor inconvenience — it means no lid-close during meetings, no quick suspend between tasks, battery draining because you forgot to plug in before walking away.&lt;/p&gt;</description></item></channel></rss>