* QM57/i7: i915 DRI kernel driver causes crash
@ 2011-01-19 21:32 John J. Stimson-III
2011-01-19 21:58 ` Chris Wilson
0 siblings, 1 reply; 4+ messages in thread
From: John J. Stimson-III @ 2011-01-19 21:32 UTC (permalink / raw)
To: intel-gfx; +Cc: John J. Stimson-III
My hardware:
motherboard: ITOX CP330-NRM (QM57 chipset)
CPU: Intel i7-620m
video display: VGA monitor connected to VGA port on motherboard
Kernel version 2.6.37.
A kernel compiled with AGP support with Intel AGP driver, and DRI
support enabled with no drivers, boots. X will not run with device
driver set to intel ("no mode switching driver found"), but it will
run with the driver set to vesa.
A kernel compiled with AGP support for Intel, and DRI support with the
Intel i915 driver with modeswitching enabled, crashes immediately
after LILO: I select the kernel to boot, there is a message about BIOS
checking, the screen blanks for an instant, and then the tail end of
kernel crash debugging information is displayed, with numerous
references to i915.
A kernel compiled with AGP support for Intel, and DRI support with the
Intel i915 and i830 drivers compiled as modules, boots just fine.
However, running modprobe i915 produces a series of kernel error
announcments. After a fresh reboot, running startx with the intel
Xwindows driver, without attempting to load the i915 module manually,
results in a blank screen and an unkillable X process.
Is the QM57 chipset with the i7 mobile processor supported by the
Intel DRI kernel drivers?
Is this a known problem?
What additional information do you need from me to help diagnose this
problem?
--
john@idsfa.net John Stimson
http://www.idsfa.net/~john/ HMC Physics '94
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: QM57/i7: i915 DRI kernel driver causes crash
2011-01-19 21:32 QM57/i7: i915 DRI kernel driver causes crash John J. Stimson-III
@ 2011-01-19 21:58 ` Chris Wilson
2011-01-19 22:51 ` John J. Stimson-III
0 siblings, 1 reply; 4+ messages in thread
From: Chris Wilson @ 2011-01-19 21:58 UTC (permalink / raw)
To: John J. Stimson-III, intel-gfx; +Cc: John J. Stimson-III
On Wed, 19 Jan 2011 13:32:50 -0800, "John J. Stimson-III" <john@idsfa.net> wrote:
> Is the QM57 chipset with the i7 mobile processor supported by the
> Intel DRI kernel drivers?
Yes.
> Is this a known problem?
No.
> What additional information do you need from me to help diagnose this
> problem?
The information on the screen at the time of the crash. It should be
available from dmesg and hopefully recorded in /var/log/message.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: QM57/i7: i915 DRI kernel driver causes crash
2011-01-19 21:58 ` Chris Wilson
@ 2011-01-19 22:51 ` John J. Stimson-III
2011-01-19 23:17 ` Chris Wilson
0 siblings, 1 reply; 4+ messages in thread
From: John J. Stimson-III @ 2011-01-19 22:51 UTC (permalink / raw)
To: Chris Wilson; +Cc: intel-gfx
On Wed, Jan 19, 2011 at 09:58:09PM +0000, Chris Wilson wrote:
> On Wed, 19 Jan 2011 13:32:50 -0800, "John J. Stimson-III" <john@idsfa.net> wrote:
> > What additional information do you need from me to help diagnose this
> > problem?
>
> The information on the screen at the time of the crash. It should be
> available from dmesg and hopefully recorded in /var/log/message.
The crash that occurred at bootup didn't get logged. I'm not sure if
I checked dmesg. Do you think if I replicated the crash, then
rebooted with the working kernel, that the information from the crash
would still be in dmesg? Where would it be stored? The crash happens
immediately when the kernel is loaded, before any of the filesystems
are brought up. The trace information is the first thing that's
displayed.
Here is a photo of what is displayed on the screen:
http://www.idsfa.net/~john/Images/2011/intel-crash/1200x900/IMG_0470.jpg
The kernel messages from running "modprobe i915" did get logged:
Jan 19 12:05:08 harlie kernel: mtrr: type mismatch for c0000000,10000000 old: write-back new: write-combining
Jan 19 12:05:08 harlie kernel: BUG: unable to handle kernel NULL pointer dereference at (null)
Jan 19 12:05:08 harlie kernel: IP: [< (null)>] (null)
Jan 19 12:05:08 harlie kernel: *pdpt = 000000002f183001 *pde = 0000000000000000
Jan 19 12:05:08 harlie kernel: Oops: 0010 [#1] SMP
Jan 19 12:05:08 harlie kernel: last sysfs file: /sys/devices/pci0000:00/0000:00:02.0/boot_vga
Jan 19 12:05:08 harlie kernel: Modules linked in: i915(+) drm_kms_helper cfbcopyarea video backlight cfbimgblt cfbfillrect
Jan 19 12:05:08 harlie kernel:
Jan 19 12:05:08 harlie kernel: Pid: 4166, comm: modprobe Not tainted 2.6.37Harlie #8 To be filled by O.E.M./To be filled by O.E.M.
Jan 19 12:05:08 harlie kernel: EIP: 0060:[<00000000>] EFLAGS: 00010246 CPU: 3
Jan 19 12:05:08 harlie kernel: EIP is at 0x0
Jan 19 12:05:08 harlie kernel: EAX: 00000000 EBX: f77ed000 ECX: f3383100 EDX: f77ed000
Jan 19 12:05:08 harlie kernel: ESI: f2c8a118 EDI: 00000000 EBP: f2c93c98 ESP: f2c93c7c
Jan 19 12:05:08 harlie kernel: DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
Jan 19 12:05:08 harlie kernel: Process modprobe (pid: 4166, ti=f2c92000 task=f2eb72a0 task.ti=f2c92000)
Jan 19 12:05:08 harlie kernel: Stack:
Jan 19 12:05:08 harlie kernel: c1071821 000000d0 ecf67110 00000000 000a13d2 f26cb600 00000001 f2c93cac
Jan 19 12:05:08 harlie kernel: c107192f 00000000 000a13d2 00000000 f2c93cd4 f86f40ed f2d3ddc0 00001000
Jan 19 12:05:08 harlie kernel: 00000000 000a13d2 f2c8a118 f26cb600 ed700000 00001000 f2c93d04 f86f57ab
Jan 19 12:05:08 harlie kernel: Call Trace:
Jan 19 12:05:08 harlie kernel: [<c1071821>] ? do_read_cache_page+0x71/0x160
Jan 19 12:05:08 harlie kernel: [<c107192f>] ? read_cache_page_gfp+0x1f/0x30
Jan 19 12:05:08 harlie kernel: [<f86f40ed>] ? i915_gem_object_get_pages+0xad/0x1d0 [i915]
Jan 19 12:05:08 harlie kernel: [<f86f57ab>] ? i915_gem_object_bind_to_gtt+0xeb/0x2d0 [i915]
Jan 19 12:05:08 harlie kernel: [<f86f7961>] ? i915_gem_object_pin+0x151/0x190 [i915]
Jan 19 12:05:08 harlie kernel: [<c11dedcd>] ? drm_gem_object_init+0x3d/0x60
Jan 19 12:05:08 harlie kernel: [<f86f7aa5>] ? i915_gem_init_ringbuffer+0x105/0x1e0 [i915]
Jan 19 12:05:08 harlie kernel: [<f86e91b7>] ? i915_driver_load+0x667/0x1160 [i915]
Jan 19 12:05:08 harlie kernel: [<c11f6ee2>] ? device_register+0x12/0x20
Jan 19 12:05:08 harlie kernel: [<c11e4455>] ? drm_sysfs_device_add+0x75/0xa0
Jan 19 12:05:08 harlie kernel: [<c11e3cd2>] ? drm_get_pci_dev+0x142/0x260
Jan 19 12:05:08 harlie kernel: [<f87205ec>] ? i915_pci_probe+0xd/0x189 [i915]
Jan 19 12:05:08 harlie kernel: [<c1176dae>] ? local_pci_probe+0xe/0x10
Jan 19 12:05:08 harlie kernel: [<c1176fe0>] ? pci_device_probe+0x60/0x80
Jan 19 12:05:08 harlie kernel: [<c11f8ef9>] ? driver_probe_device+0x69/0x180
Jan 19 12:05:08 harlie kernel: [<c1176ed3>] ? pci_match_device+0xb3/0xc0
Jan 19 12:05:08 harlie kernel: [<c11f90a1>] ? __driver_attach+0x91/0xa0
Jan 19 12:05:08 harlie kernel: [<c11f87c8>] ? bus_for_each_dev+0x48/0x70
Jan 19 12:05:08 harlie kernel: [<c11f8d89>] ? driver_attach+0x19/0x20
Jan 19 12:05:08 harlie kernel: [<c11f9010>] ? __driver_attach+0x0/0xa0
Jan 19 12:05:08 harlie kernel: [<c11f81b7>] ? bus_add_driver+0x187/0x250
Jan 19 12:05:08 harlie kernel: [<c1176f20>] ? pci_device_remove+0x0/0x40
Jan 19 12:05:08 harlie kernel: [<c11f9325>] ? driver_register+0x65/0x120
Jan 19 12:05:08 harlie kernel: [<c105ff73>] ? load_module+0x1113/0x1240
Jan 19 12:05:08 harlie kernel: [<c1177200>] ? __pci_register_driver+0x40/0xc0
Jan 19 12:05:08 harlie kernel: [<c11e3e9f>] ? drm_pci_init+0xaf/0xc0
Jan 19 12:05:08 harlie kernel: [<c11dd53f>] ? drm_init+0x4f/0x70
Jan 19 12:05:08 harlie kernel: [<f873508f>] ? i915_init+0x8f/0x91 [i915]
Jan 19 12:05:08 harlie kernel: [<c1001040>] ? do_one_initcall+0x30/0x160
Jan 19 12:05:08 harlie kernel: [<f8735000>] ? i915_init+0x0/0x91 [i915]
Jan 19 12:05:08 harlie kernel: [<c1060139>] ? sys_init_module+0x99/0x1e0
Jan 19 12:05:08 harlie kernel: [<c109c53d>] ? sys_read+0x3d/0x70
Jan 19 12:05:08 harlie kernel: [<c13907ed>] ? syscall_call+0x7/0xb
Jan 19 12:05:08 harlie kernel: Code: Bad EIP value.
Jan 19 12:05:08 harlie kernel: EIP: [<00000000>] 0x0 SS:ESP 0068:f2c93c7c
Jan 19 12:05:08 harlie kernel: CR2: 0000000000000000
Jan 19 12:05:08 harlie kernel: ---[ end trace f7459f2d373bd0da ]---
--
john@idsfa.net John Stimson
http://www.idsfa.net/~john/ HMC Physics '94
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: QM57/i7: i915 DRI kernel driver causes crash
2011-01-19 22:51 ` John J. Stimson-III
@ 2011-01-19 23:17 ` Chris Wilson
0 siblings, 0 replies; 4+ messages in thread
From: Chris Wilson @ 2011-01-19 23:17 UTC (permalink / raw)
To: John J. Stimson-III; +Cc: intel-gfx
On Wed, 19 Jan 2011 14:51:07 -0800, "John J. Stimson-III" <john@idsfa.net> wrote:
> The kernel messages from running "modprobe i915" did get logged:
>
> Jan 19 12:05:08 harlie kernel: mtrr: type mismatch for c0000000,10000000 old: write-back new: write-combining
> Jan 19 12:05:08 harlie kernel: BUG: unable to handle kernel NULL pointer dereference at (null)
> Jan 19 12:05:08 harlie kernel: IP: [< (null)>] (null)
> Jan 19 12:05:08 harlie kernel: *pdpt = 000000002f183001 *pde = 0000000000000000
> Jan 19 12:05:08 harlie kernel: Oops: 0010 [#1] SMP
> Jan 19 12:05:08 harlie kernel: last sysfs file: /sys/devices/pci0000:00/0000:00:02.0/boot_vga
> Jan 19 12:05:08 harlie kernel: Modules linked in: i915(+) drm_kms_helper cfbcopyarea video backlight cfbimgblt cfbfillrect
> Jan 19 12:05:08 harlie kernel:
> Jan 19 12:05:08 harlie kernel: Pid: 4166, comm: modprobe Not tainted 2.6.37Harlie #8 To be filled by O.E.M./To be filled by O.E.M.
> Jan 19 12:05:08 harlie kernel: EIP: 0060:[<00000000>] EFLAGS: 00010246 CPU: 3
> Jan 19 12:05:08 harlie kernel: EIP is at 0x0
> Jan 19 12:05:08 harlie kernel: EAX: 00000000 EBX: f77ed000 ECX: f3383100 EDX: f77ed000
> Jan 19 12:05:08 harlie kernel: ESI: f2c8a118 EDI: 00000000 EBP: f2c93c98 ESP: f2c93c7c
> Jan 19 12:05:08 harlie kernel: DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
> Jan 19 12:05:08 harlie kernel: Process modprobe (pid: 4166, ti=f2c92000 task=f2eb72a0 task.ti=f2c92000)
> Jan 19 12:05:08 harlie kernel: Stack:
> Jan 19 12:05:08 harlie kernel: c1071821 000000d0 ecf67110 00000000 000a13d2 f26cb600 00000001 f2c93cac
> Jan 19 12:05:08 harlie kernel: c107192f 00000000 000a13d2 00000000 f2c93cd4 f86f40ed f2d3ddc0 00001000
> Jan 19 12:05:08 harlie kernel: 00000000 000a13d2 f2c8a118 f26cb600 ed700000 00001000 f2c93d04 f86f57ab
> Jan 19 12:05:08 harlie kernel: Call Trace:
> Jan 19 12:05:08 harlie kernel: [<c1071821>] ? do_read_cache_page+0x71/0x160
> Jan 19 12:05:08 harlie kernel: [<c107192f>] ? read_cache_page_gfp+0x1f/0x30
> Jan 19 12:05:08 harlie kernel: [<f86f40ed>] ? i915_gem_object_get_pages+0xad/0x1d0 [i915]
> Jan 19 12:05:08 harlie kernel: [<f86f57ab>] ? i915_gem_object_bind_to_gtt+0xeb/0x2d0 [i915]
> Jan 19 12:05:08 harlie kernel: [<f86f7961>] ? i915_gem_object_pin+0x151/0x190 [i915]
> Jan 19 12:05:08 harlie kernel: [<c11dedcd>] ? drm_gem_object_init+0x3d/0x60
> Jan 19 12:05:08 harlie kernel: [<f86f7aa5>] ? i915_gem_init_ringbuffer+0x105/0x1e0 [i915]
I've never seen that one before. Looks suspiciously like that the backing
shmem file was not initialised. It would be useful to find out just which
line do_read_cache_page+0x71 corresponds to, i.e.:
gdb vmlinux
list *do_read_cache_page+0x71
and double check that CONFIG_SHMEM is indeed builtin.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2011-01-19 23:17 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-01-19 21:32 QM57/i7: i915 DRI kernel driver causes crash John J. Stimson-III
2011-01-19 21:58 ` Chris Wilson
2011-01-19 22:51 ` John J. Stimson-III
2011-01-19 23:17 ` Chris Wilson
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
