** Description changed:
=== Problem ===
- From the Maverick 2.6.35-16 kernel and onward, X does not load and the
computer boots to a tty login prompt.
+ 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: [<ffffffffa007e3c6>] ips_detect_cpu+0x76/0x1d0 [intel_ips]
- [ 20.162500] PGD aefed067 PUD a4804067 PMD 0
- [ 20.162616] Oops: 0000 [#1] SMP
+ [ 20.162500] PGD aefed067 PUD a4804067 PMD 0
+ [ 20.162616] Oops: 0000 [#1] SMP
[ 20.162702] last sysfs file: /sys/devices/pci0000:ff/0000:ff:02.1/uevent
- [ 20.162749] CPU 1
+ [ 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.163144]
[ 20.163176] Pid: 418, comm: modprobe Not tainted 2.6.35-22-generic
#33-Ubuntu FJNBB06/LIFEBOOK A530
[ 20.163229] RIP: 0010:[<ffffffffa007e3c6>] [<ffffffffa007e3c6>]
ips_detect_cpu+0x76/0x1d0 [intel_ips]
[ 20.163312] RSP: 0018:ffff8800a4883c48 EFLAGS: 00010202
[ 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: 00007f5616ada700(0000) GS:ffff880001f00000(0000)
knlGS:0000000000000000
[ 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] [<ffffffff81142fa4>] ? kmem_cache_alloc_notrace+0xb4/0xd0
[ 20.164896] [<ffffffffa007efb1>] ips_probe+0x71/0x710 [intel_ips]
[ 20.164967] [<ffffffff812d6ec7>] local_pci_probe+0x17/0x20
[ 20.165034] [<ffffffff812d71b9>] __pci_device_probe+0xe9/0xf0
[ 20.165104] [<ffffffff812b951a>] ? kobject_get+0x1a/0x30
[ 20.165172] [<ffffffff81383c29>] ? get_device+0x19/0x20
[ 20.165238] [<ffffffff812d825a>] pci_device_probe+0x3a/0x60
[ 20.165304] [<ffffffff81387fe8>] really_probe+0x68/0x190
[ 20.165371] [<ffffffff81388155>] driver_probe_device+0x45/0x70
[ 20.165436] [<ffffffff8138821b>] __driver_attach+0x9b/0xa0
[ 20.165503] [<ffffffff81388180>] ? __driver_attach+0x0/0xa0
[ 20.165566] [<ffffffff81387428>] bus_for_each_dev+0x68/0x90
[ 20.165633] [<ffffffff81387e5e>] driver_attach+0x1e/0x20
[ 20.165697] [<ffffffff8138771e>] bus_add_driver+0xde/0x280
[ 20.165761] [<ffffffff81388560>] driver_register+0x80/0x150
[ 20.165825] [<ffffffff8158d0f6>] ? notifier_call_chain+0x56/0x80
[ 20.165845] input: Fujitsu FUJ02B1 as
/devices/LNXSYSTM:00/LNXSYBUS:00/FUJ02B1:00/input/input4
[ 20.165898] ACPI: Fujitsu FUJ02B1 [FJEX] (on)
[ 20.166032] [<ffffffff812d84e6>] __pci_register_driver+0x56/0xd0
[ 20.166103] [<ffffffff81084f05>] ?
__blocking_notifier_call_chain+0x65/0x80
[ 20.166176] [<ffffffffa0084000>] ? ips_init+0x0/0x20 [intel_ips]
[ 20.166245] [<ffffffffa008401e>] ips_init+0x1e/0x20 [intel_ips]
[ 20.166314] [<ffffffff8100204c>] do_one_initcall+0x3c/0x1a0
[ 20.166382] [<ffffffff8109bc6b>] sys_init_module+0xbb/0x200
[ 20.166450] [<ffffffff8100a0f2>] system_call_fastpath+0x16/0x1b
- [ 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.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 [<ffffffffa007e3c6>] ips_detect_cpu+0x76/0x1d0 [intel_ips]
[ 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/xorg/modules/libfbdevhw.so
[ 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]
+ [ 197.074]
Fatal server error:
[ 197.074] no screens found
- [ 197.074]
- Please consult the The X.Org Foundation support
- at http://wiki.x.org
- for help.
+ [ 197.074]
+ Please consult the The X.Org Foundation support
+ at http://wiki.x.org
+ for help.
[ 197.074] Please also check the log file at "/var/log/Xorg.0.log" for
additional information.
- [ 197.074]
+ [ 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-xorg-video-intel
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://pastebin.com/9JNcNAN1
Xorg.log: http://pastebin.com/2XHxX45P
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: amd64 kernel-needs-review regression-potential
** Tags removed: edgers
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
Kernel Oops - unable to handle kernel NULL pointer dereference; IP:
[<ffffffffa007e3c6>] ips_detect_cpu+0x76/0x1d0 [intel_ips]
https://bugs.launchpad.net/bugs/648631
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
