kernel-gki-expert

Analyze GKI kernel module workflows to resolve loading, ABI, and panic issues.

40|7|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/jonaschen/Android-Software --skill kernel-gki-expert
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kernel-gki-expert
Source: https://github.com/jonaschen/Android-Software/tree/main/skills/L2-kernel-gki-expert
Command: npx skills add https://github.com/jonaschen/Android-Software --skill kernel-gki-expert

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires modinfo, nm, llvm-nm, bash, xmllint, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill guides Android kernel teams through GKI module compliance, KMI symbol guardrails, module signing, and panic triage so they avoid invalid driver loads and ABI failures.

Core Features & Use Cases

  • Path and trigger clarity: Understand when to load the kernel-gki-expert based on module loading issues, Kconfig tweaks, Device Tree edits, ABI mismatches, or page-size migration requests.
  • Architecture intelligence: Learn how the GKI kernel, KMI symbol lists, module signing, and 16KB page size configurations work together to keep vendor modules compatible.
  • Tool calls & references: Follow the provided checks and documentation to inspect symbol lists, decode panics, verify signatures, and hand off to related L2 experts like SELinux or HAL specialists.
  • Use Case: When an OEM module fails insmod on an Android 15 device, use the compliance checklist to confirm symbol exports, review ABI lists, and validate that signatures and configs match the required GKI branches before handing off to downstream experts.

Quick Start

Ask about a vendor module failing to load so the skill pinpoints the missing KMI symbols, signature status, and relevant handoff.

Frequently Asked Questions about kernel-gki-expert

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why does my Android GKI kernel module fail to load on insmod?

GKI kernel module loading fails when KMI symbols are missing, module signatures are invalid, or ABI configurations mismatch the required branch. Verify symbol exports, validate signatures, and review ABI lists to ensure vendor module compliance.

How do I verify KMI symbol usage for an Android vendor module?

Verify KMI symbol usage by inspecting symbol lists with tools like nm and modinfo to confirm required exports. This ensures the vendor module only uses guarded symbols, preventing invalid driver loads and ABI failures on GKI kernels.

What is the process for troubleshooting GKI kernel panics related to drivers?

Troubleshooting GKI kernel panics involves decoding the panic traces, verifying Kconfig options, and checking Device Tree edits. This process isolates driver interface failures and ABI mismatches under the kernel and common path scope.

Do I need to update module signing configurations when migrating to a 16KB page size?

Yes, migrating to a 16KB page size requires updating module signing and Kconfig configurations. Ensuring these configurations match the GKI branch keeps vendor modules compatible and prevents ABI stability issues.

Can I use standard tools like nm and modinfo to diagnose GKI module compliance issues?

Yes, tools like nm, llvm-nm, and modinfo inspect symbol lists and verify module signatures. Using these dependencies alongside provided checks confirms KMI symbol use and validates GKI kernel module stability.

When should I hand off a GKI kernel module issue to a downstream SELinux or HAL expert?

Hand off GKI kernel module issues to SELinux or HAL experts after confirming KMI symbols, signatures, and configs are valid. This ensures the interaction handoff occurs only when downstream policy or hardware abstraction layers are the root cause.