--- title: Linus Torvalds uses AI to debug an Intel GPU driver bug description: A kernel patch fixes a bug in the Intel xe GPU driver where the flat CCS (compression control surface) storage offset was rounded up instead of down, causing a... canonical: https://daily.dev/posts/linus-torvalds-uses-ai-to-debug-an-intel-gpu-driver-bug-weykt2svk twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Linus Torvalds uses AI to debug an Intel GPU driver bug | daily.dev og:description: A kernel patch fixes a bug in the Intel xe GPU driver where the flat CCS (compression control surface) storage offset was rounded up instead of down, causing a... og:url: https://daily.dev/posts/linus-torvalds-uses-ai-to-debug-an-intel-gpu-driver-bug-weykt2svk og:image: https://api.daily.dev/og/posts/WEYKT2svK.png og:image:alt: Linus Torvalds uses AI to debug an Intel GPU driver bug og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Linus Torvalds uses AI to debug an Intel GPU driver bug **[Lobsters](https://daily.dev/sources/lobsters)** · 3 min read · 0 upvotes · 0 comments ## Summary A kernel patch fixes a bug in the Intel xe GPU driver where the flat CCS (compression control surface) storage offset was rounded up instead of down, causing a small region of compression-hardware-owned memory to be handed out as usable VRAM. On a Battlemage G21 GPU this caused silent memory corruption that intermittently crashed a Mesa VM's page tables, producing a black screen loop with gdm endlessly restarting the compositor. The fix changes round_up() to round_down() and tightens a debug assertion that previously could never trigger. Linus Torvalds describes the marathon debugging session, including using an AI assistant that repeatedly wanted to give up but kept generating useful debug output when pushed, and credits the AI with writing the commit message. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Why did my Intel Battlemage GPU system randomly get a black screen with gdm restarting in a loop? The xe kernel driver's flat CCS (compression control surface) offset calculation used round_up() instead of round_down(), so a small region of memory owned by the GPU's compression hardware was incorrectly handed to the VRAM allocator as free memory. On a Battlemage G21 with 16 GiB, this exposed the last 2 KiB of a page, which occasionally held a Mesa VM's page table and got silently overwritten by compression metadata, crashing the compositor's first submission. _Track kernel driver fixes like this xe GPU memory corruption bug as you debug flaky graphics crashes on daily.dev._ ### What was wrong with the CCS storage assertion in the xe driver before this fix? The debug assertion compared the flat CCS offset against GSMBASE minus ccs_size for equality, but that reference value is itself 128K aligned, so it only agreed with the buggy rounded-up offset precisely when the real base was misaligned. This meant the check could never catch the bug it was meant to catch, and it was also compiled out unless CONFIG_DRM_XE_DEBUG was enabled. _Follow how kernel maintainers harden broken assertions when researching GPU driver reliability on daily.dev._ ## Community take How the wider developer community reacted, aggregated from 3 discussions and 18 comments across lobsters, hackernews (as of 2026-08-23). **TL;DR:** Commenters admire the debugging story and how effectively AI-generated debug output helped crack a nasty hardware bug, but many are uneasy about Linus letting AI write the commit message and its verbose, history-explaining code comments creeping into the kernel. **Sentiment:** 25% positive · 45% mixed · 30% skeptical **The case for** - The AI generated genuinely useful debug output when pushed, even after repeatedly claiming the bug was unsolvable. - Getting an AI to write in convincing 'kernel/Linus style' for a commit message is seen as an impressive capability. - Some argue it's a high-quality patch from a domain expert, so calling it 'slop' is unfair. **The pushback** - AI-written comments tend to describe what changed rather than why, which is seen as low-value and even misleading to future readers/agents. - Discomfort that 'slop' style prose is now in the kernel with Linus's implicit endorsement. - Concern that Linus may be in an early honeymoon phase with AI output before noticing its repetitive, low-signal patterns. - Some engineers have started actively blocking or filtering LLM-written comments in their own workflows due to this same issue. **By community** - lobsters (mixed): A long thread balancing genuine appreciation for the debugging feat against real discomfort with AI-authored commit messages and comment style creeping into kernel code. - hackernews (mixed): Brief comments note the irony that despite the AI's dramatic back-and-forth, the eventual fix was just a one-line change. **Hottest debate:** Whether AI-generated commit messages and code comments (which explain history/changes rather than current-state rationale) count as harmless convenience or unwanted 'slop' in serious codebases. **Open questions** - Will heavier use of AI-authored commit messages and comments become an accepted kernel convention or be pushed back on? - Can prompting/tooling reliably stop LLMs from producing verbose, low-value comments across long sessions? **Highlights** > The debugging using AI is great, as this sounds indeed like a horrible issue to debug and it's great that the fix exists now and is in the kernel. However. 1. "and I let the AI write the commit message above." While this is a pretty well-written commit message, and so I guess I cannot fault Linus for the result here, it still sits uncomfortable with me. 2. The comments introduced in the commit do the classical LLM thing (recently discussed on this forum too!) where the comment describes the change from the previous state rather than the why of the current state. Now, I don't read kernel code daily so I don't know what the conventions are, but if it's anything like normal coding style, this is unhelpful. Furthermore, the unhelpfulness (and verbosity!) of the comment is one thing, but what I dislike most is that clearly Linus thought this was good enough! And it seems the commit is on master, so it's not a to-be-reviewed commit either. "My kernel has LLM output in it" is a ship-has-sailed situation, but it seems my kernel now has slop in it, and slop from Linus' hand. That makes me unhappy. > — [tomsmeding on lobsters · 23 points, 3 comments](https://lobste.rs/s/eyaz5f/linus_torvalds_uses_ai_debug_intel_gpu#c_gy3daf) > It's possible that Linus is still in the honeymoon phase with AI output. It really does feel quite magical, at least until you start noticing the same repeating patterns everywhere and it begins to feel gross. > — [cesarandreu on lobsters · 5 points, 1 comments](https://lobste.rs/s/eyaz5f/linus_torvalds_uses_ai_debug_intel_gpu#c_mmyyve) > It is a high quality patch written by a domain expert so why would you call it slop other than to be negative. > — [st3fan on lobsters · 1 points](https://lobste.rs/s/eyaz5f/linus_torvalds_uses_ai_debug_intel_gpu#c_gelfqh) > I was thinking along those lines too. At first i didn't notice these things on LLM output. Now i'm way more vigilant of this "explain the history of how the next line got to be what it is, when its behavior is now the corrected and obvious thing and doesn't need an explanation" comments. I have of course added system prompts, code style guides, and any nudges that seemed reasonable, to try to steer the LLMs into a saner direction. I *think* some of it has worked, as the bots sometimes mention writing comments following the project style, but these things are so stochastic that it's difficult to say anything with certainty. It's pretty ironic that these AIs are so good at understanding ("understanding") code that is poorly documented, convoluted, and sometimes even minified, but they still tend towards over-commenting the code they generate. Even if they'd have no trouble understanding said code without those comments. > — [epidemian on lobsters · 3 points](https://lobste.rs/s/eyaz5f/linus_torvalds_uses_ai_debug_intel_gpu#c_jl4vu2) > Linus also wrote: "the AI several times stated flat out that this was impossible and unsolvable and that we should just write a report about it" and: "So credit where credit is due and I let the AI write the commit message above." FWIW in the end it was a one-line fix. > — [TacticalCoder on hackernews](https://news.ycombinator.com/item?id=49395571) **Source threads** - [lobsters](https://lobste.rs/s/eyaz5f/linus_torvalds_uses_ai_debug_intel_gpu) · 19 points · 16 comments - [hackernews](https://news.ycombinator.com/item?id=49395262) · 9 points · 2 comments - [hackernews](https://news.ycombinator.com/item?id=49401592) · 4 points · 0 comments ## Similar posts on daily.dev - [Intel Xe Driver For Linux 7.4 Adds vRAM Health Check, Degraded Memory Handling](https://daily.dev/posts/intel-xe-driver-for-linux-7-4-adds-vram-health-check-degraded-memory-handling-a6dldrusi) · Phoronix · 0 upvotes · 0 comments - [Linux 7.3 is giving my decade-old AMD GPU features it never had on Windows](https://daily.dev/posts/linux-7-3-is-giving-my-decade-old-amd-gpu-features-it-never-had-on-windows-da0i4agni) · XDA Developers · 0 upvotes · 0 comments - [Intel Xe Driver Improves Memory Pressure / Out-Of-Memory Behavior For vRAM With Linux 7.1](https://daily.dev/posts/intel-xe-driver-improves-memory-pressure-out-of-memory-behavior-for-vram-with-linux-7-1-1ap5cocjh) · Phoronix · 0 upvotes · 0 comments --- Tags: [#linux](https://daily.dev/tags/linux), [#gpu](https://daily.dev/tags/gpu) [View this post on daily.dev](https://daily.dev/posts/linus-torvalds-uses-ai-to-debug-an-intel-gpu-driver-bug-weykt2svk) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Linus Torvalds uses AI to debug an Intel GPU driver bug","url":"https://daily.dev/posts/linus-torvalds-uses-ai-to-debug-an-intel-gpu-driver-bug-weykt2svk","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/linus-torvalds-uses-ai-to-debug-an-intel-gpu-driver-bug-weykt2svk"},"datePublished":"2026-08-22T23:36:10.566Z","dateModified":"2026-08-23T17:23:49.863Z","description":"A kernel patch fixes a bug in the Intel xe GPU driver where the flat CCS (compression control surface) storage offset was rounded up instead of down, causing a...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/34a41129305853f1f8174c1e735717eb?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/34a41129305853f1f8174c1e735717eb?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Lobsters","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Lobsters","logo":"https://media.daily.dev/image/upload/s--tl8v_Fku--/f_auto,t_logo/v1698841318/logos/lobste.jpg","url":"https://daily.dev/sources/lobsters"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/linus-torvalds-uses-ai-to-debug-an-intel-gpu-driver-bug-weykt2svk","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"linux,gpu","timeRequired":"PT3M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Lobsters","item":"https://daily.dev/sources/lobsters"},{"@type":"ListItem","position":3,"name":"Linus Torvalds uses AI to debug an Intel GPU driver bug"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/linus-torvalds-uses-ai-to-debug-an-intel-gpu-driver-bug-weykt2svk#faq","mainEntity":[{"@type":"Question","name":"Why did my Intel Battlemage GPU system randomly get a black screen with gdm restarting in a loop?","acceptedAnswer":{"@type":"Answer","text":"The xe kernel driver's flat CCS (compression control surface) offset calculation used round_up() instead of round_down(), so a small region of memory owned by the GPU's compression hardware was incorrectly handed to the VRAM allocator as free memory. On a Battlemage G21 with 16 GiB, this exposed the last 2 KiB of a page, which occasionally held a Mesa VM's page table and got silently overwritten by compression metadata, crashing the compositor's first submission. Track kernel driver fixes like this xe GPU memory corruption bug as you debug flaky graphics crashes on daily.dev."}},{"@type":"Question","name":"What was wrong with the CCS storage assertion in the xe driver before this fix?","acceptedAnswer":{"@type":"Answer","text":"The debug assertion compared the flat CCS offset against GSMBASE minus ccs_size for equality, but that reference value is itself 128K aligned, so it only agreed with the buggy rounded-up offset precisely when the real base was misaligned. This meant the check could never catch the bug it was meant to catch, and it was also compiled out unless CONFIG_DRM_XE_DEBUG was enabled. Follow how kernel maintainers harden broken assertions when researching GPU driver reliability on daily.dev."}}]} ```