[Bug 72351] [GM45] oops in iowrite32 after long hibernation

bugzilla-daemon at bugzilla.kernel.org bugzilla-daemon at bugzilla.kernel.org
Tue Mar 18 13:02:35 PDT 2014


https://bugzilla.kernel.org/show_bug.cgi?id=72351

--- Comment #6 from Jae-hyeon Park <jhyeon at gmail.com> ---
I realized that my ebuild script was stripping the kernel modules before
installing them, so I recompiled the kernel without stripping the modules.  I
also switched on the CONFIG_DEBUG_INFO option.  But then the system locked up
hardly after resume, so I could not get dmesg or syslog.  Therefore, I just
tried the gdb command, hoping that the address is not changed whether to
(un)strip or to turn on/off CONFIG_DEBUG_INFO.  The result is:

# gdb /lib/modules/3.10.0-1+/kernel/drivers/gpu/drm/i915/i915.ko
GNU gdb (Gentoo 7.6.2 p1) 7.6.2
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
For bug reporting instructions, please see:
<http://bugs.gentoo.org/>...
Reading symbols from
/lib64/modules/3.10.0-1+/kernel/drivers/gpu/drm/i915/i915.ko...done.
(gdb) list *intel_gen4_queue_flip+0xc4
0x2d1b4 is in intel_gen4_queue_flip
(/var/tmp/portage/sys-kernel/bisect-3.99.99/work/linux-3.99.99/drivers/gpu/drm/i915/intel_ringbuffer.h:233).
228   
/var/tmp/portage/sys-kernel/bisect-3.99.99/work/linux-3.99.99/drivers/gpu/drm/i915/intel_ringbuffer.h:
No such file or directory.

Line intel_ringbuffer.h:233 is in the function:

    229 static inline void intel_ring_emit(struct intel_ring_buffer *ring,
    230                                    u32 data)
    231 {
    232         iowrite32(data, ring->virtual_start + ring->tail);
    233         ring->tail += 4;
    234 }

BTW, the kernel crashed without the tp_smapi modules.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the intel-gfx-bugs mailing list