Kernel Oops - unable to handle kernel NULL pointer dereference; IP: [<ffffffffa007e3c6>] ips_detect_cpu+0x76/0x1d0 [intel_ips]
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linux |
Invalid
|
Undecided
|
Unassigned | ||
linux (Ubuntu) |
Fix Released
|
Undecided
|
AceLan Kao | ||
Maverick |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
=== Problem ===
From the Maverick 2.6.35-17 kernel and onward, the INTEL_IPS config option was enabled to fix Bug 601057. Here, the intel_ips module causes an Oops which causes X not to load and the computer boots to a tty login prompt. Blacklisting INTEL_IPS fixes the bug completely.
=== dmesg (2.6.35-22.33) ===
(snip)
[ 20.162308] intel ips 0000:00:1f.6: No CPUID match found.
[ 20.162319] BUG: unable to handle kernel NULL pointer dereference at 0000000000000008
[ 20.162424] IP: [<ffffffffa007e
[ 20.162500] PGD aefed067 PUD a4804067 PMD 0
[ 20.162616] Oops: 0000 [#1] SMP
[ 20.162702] last sysfs file: /sys/devices/
[ 20.162749] CPU 1
[ 20.162780] Modules linked in: intel_ips(+) snd_page_alloc bluetooth led_class lp parport ahci r8169 mii libahci
[ 20.163144]
[ 20.163176] Pid: 418, comm: modprobe Not tainted 2.6.35-22-generic #33-Ubuntu FJNBB06/LIFEBOOK A530
[ 20.163229] RIP: 0010:[<
[ 20.163312] RSP: 0018:ffff8800a4
[ 20.163355] RAX: 0000000000a800c8 RBX: 0000000000000000 RCX: 0000000000a800c8
[ 20.163401] RDX: 0000000000000000 RSI: ffff8800a4883c64 RDI: 0000000000a800c8
[ 20.163451] RBP: ffff8800a4883c88 R08: 0000000000000000 R09: 0000000000000000
[ 20.163499] R10: 0000000000000000 R11: 0000000000000002 R12: 0000000000a800c8
[ 20.163565] R13: ffff8800a4331b40 R14: ffff8800b2af3090 R15: 00000000fffffff4
[ 20.163637] FS: 00007f5616ada70
[ 20.163729] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 20.163792] CR2: 0000000000000008 CR3: 00000000aeffb000 CR4: 00000000000006e0
[ 20.163860] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 20.163926] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[ 20.163994] Process modprobe (pid: 418, threadinfo ffff8800a4882000, task ffff8800a48596e0)
[ 20.164085] Stack:
[ 20.164138] ffff8800a4883c88 ffffffff81142fa4 ffff8800a4883d14 00000000b2af3000
[ 20.164283] <0> ffff8800b2af3000 ffff8800a4331b40 ffff8800b2af3000 00000000fffffff4
[ 20.164499] <0> ffff8800a4883cd8 ffffffffa007efb1 ffff8800a4883cb8 ffff8800aed53e10
[ 20.164763] Call Trace:
[ 20.164823] [<ffffffff81142
[ 20.164896] [<ffffffffa007e
[ 20.164967] [<ffffffff812d6
[ 20.165034] [<ffffffff812d7
[ 20.165104] [<ffffffff812b9
[ 20.165172] [<ffffffff81383
[ 20.165238] [<ffffffff812d8
[ 20.165304] [<ffffffff81387
[ 20.165371] [<ffffffff81388
[ 20.165436] [<ffffffff81388
[ 20.165503] [<ffffffff81388
[ 20.165566] [<ffffffff81387
[ 20.165633] [<ffffffff81387
[ 20.165697] [<ffffffff81387
[ 20.165761] [<ffffffff81388
[ 20.165825] [<ffffffff8158d
[ 20.165845] input: Fujitsu FUJ02B1 as /devices/
[ 20.165898] ACPI: Fujitsu FUJ02B1 [FJEX] (on)
[ 20.166032] [<ffffffff812d8
[ 20.166103] [<ffffffff81084
[ 20.166176] [<ffffffffa0084
[ 20.166245] [<ffffffffa0084
[ 20.166314] [<ffffffff81002
[ 20.166382] [<ffffffff8109b
[ 20.166450] [<ffffffff8100a
[ 20.166517] Code: a0 48 c7 c7 88 ec ac 81 48 c7 c3 80 0a 08 a0 e8 c1 fc 23 e1 48 85 c0 74 44 bf ac 01 00 00 4c 89 e6 e8 3f 7e fb e0 66 90 41 89 c4 <8b> 53 08 41 c1 e4 12 41 c1 ec 15 41 69 c4 e8 03 00 00 39 c2 0f
[ 20.168316] RIP [<ffffffffa007e
[ 20.168411] RSP <ffff8800a4883c48>
[ 20.168470] CR2: 0000000000000008
[ 20.168539] ---[ end trace 934ab8f8f0f56d90 ]---
=== Xorg.0.log (2.6.35-22.33) ===
(snip)
[ 95.229] (WW) Falling back to old probe method for vesa
[ 95.229] (WW) Falling back to old probe method for fbdev
[ 95.229] (II) Loading sub module "fbdevhw"
[ 95.229] (II) LoadModule: "fbdevhw"
[ 95.229] (II) Loading /usr/lib/
[ 95.230] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 95.230] compiled for 1.9.0, module version = 0.0.2
[ 95.230] ABI class: X.Org Video Driver, version 8.0
[ 95.230] (EE) open /dev/fb0: No such file or directory
[ 197.074] (EE) intel(0): No kernel modesetting driver detected.
[ 197.074] (II) UnloadModule: "intel"
[ 197.074] (EE) Screen(s) found, but none have a usable configuration.
[ 197.074]
Fatal server error:
[ 197.074] no screens found
[ 197.074]
Please consult the The X.Org Foundation support
at http://
for help.
[ 197.074] Please also check the log file at "/var/log/
[ 197.074]
[ 197.080] ddxSigGiveUp: Closing log
=== Upstream Testing ===
2.6.35.1 works. (This maps to 2.6.35-15.)
2.6.35.2 works. (This maps to 2.6.35-16.)
2.6.36-rc6 works.
=== Original Report ===
Binary package hint: xserver-
Basically, on Maverick, X fails to start properly for me on newer kernels. Kernels up to 2.6.35-15 work just fine, but the later ones don't. While booting, I get into a terminal login. If I run startx from there, it complains that it couldn't load the screen properly and offers low graphics mode.
Driver version: 2:2.12.0-1ubuntu4
dmesg log from kernel 2.6.35-17 (one of the not working ones): http://
Xorg.log: http://
Note that these logs have drivers & Xorg from the xorg-edgers ppa. Removing it with ppa-purge doesn't change the situation in any way though.
Also, my GPU is Intel HD Graphics, lspci | grep VGA output being:
00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02)
It's my first time reporting a bug, I hope I didn't miss anything important! I already made a thread on the maverick forums about this, where I was advised to report a bug.
tags: | added: edgers |
tags: | added: maverick |
affects: | xserver-xorg-video-intel (Ubuntu) → linux (Ubuntu) |
tags: | removed: needs-upstream-testing |
description: | updated |
summary: |
- Intel graphics drivers not working on new kernels on Maverick? + Kernel Oops - unable to handle kernel NULL pointer dereference; IP: + [<ffffffffa007e3c6>] ips_detect_cpu+0x76/0x1d0 [intel_ips] |
description: | updated |
tags: |
added: amd64 kernel-needs-review regression-potential removed: edgers |
Changed in linux (Ubuntu): | |
status: | Incomplete → Confirmed |
Changed in linux: | |
importance: | Unknown → Undecided |
status: | Unknown → New |
status: | New → Invalid |
Changed in linux (Ubuntu): | |
assignee: | nobody → AceLan Kao (acelankao) |
Changed in linux (Ubuntu): | |
status: | Confirmed → In Progress |
tags: | added: hwe-blocker |
To my untrained eye, the dmesg log in my report shows that *something* is crashing at bootup (starting at line 765) which isn't happening on the kernels that are working just fine. I'd bet that's related.