Bug 22193 - [945GME]kernel oops when killing 100 gears
Summary: [945GME]kernel oops when killing 100 gears
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: Other Linux (All)
: medium major
Assignee: Eric Anholt
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-10 00:10 UTC by liuhaien
Modified: 2017-10-06 14:54 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
dmesg_post_oops (122.56 KB, text/plain)
2009-06-10 00:10 UTC, liuhaien
no flags Details
100gears.sh (177 bytes, text/plain)
2009-06-10 00:11 UTC, liuhaien
no flags Details
xorg.0.log (19.71 KB, text/plain)
2009-06-10 00:12 UTC, liuhaien
no flags Details

Description liuhaien 2009-06-10 00:10:35 UTC
Created attachment 26620 [details]
dmesg_post_oops

ystem Environment:
--------------------------
Host:           x-aspire1
Arch:           i386
Platform:               945GME
xf86-video-intel   (master)66ceedc0cc123e5c9f85f708b2e56d943f00e4b9
mesa   (mesa_7_5_branch)cfff2a6189b38f1ee8c8ca204e223574a5abf760
kernel  (for-linus)0e7ddf7eeeef5aea85412120539ab5369577faeb
libdrm  (master)3d4bfe8c893d016ef43d1ebf28e4607aa1f540a4
Xserver:        (server-1.6-branch)5cd5a01259ba349f1868ca4af04207cf120d69e4

Bug detailed description:
-------------------------
start X, then run 100 gears. it will cause kernel oops when killing all gears:

Message from syslogd@localhost at Jun 10 14:56:47 ...
kernel:Oops: 0000 [#1] SMP

Message from syslogd@localhost at Jun 10 14:56:47 ...
kernel:last sysfs file: /sys/devices/LNXSYSTM:00/device:00/PNP0C0A:00/power_supply/BAT1/charge_full

Message from syslogd@localhost at Jun 10 14:56:47 ...
kernel:Process X (pid: 2550, ti=f67c2000 task=f67b98e0 task.ti=f67c2000)

Message from syslogd@localhost at Jun 10 14:56:47 ...
kernel:Stack:

Message from syslogd@localhost at Jun 10 14:56:47 ...
kernel: 00100000 f67c3e54 f81865ae f7157c00 f67c3e8c f67c3e8c f67c3e74 f81d79d2

Message from syslogd@localhost at Jun 10 14:56:47 ...
kernel: f68085a0 f67c3e74 c02fe934 0000005b f67c3e8c c010645b f67c3f18 f8185578

Message from syslogd@localhost at Jun 10 14:56:47 ...
kernel:Call Trace:

Message from syslogd@localhost at Jun 10 14:56:47 ...
kernel: [<f81865ae>] ? drm_gem_object_alloc+0x25/0xa0 [drm]

Message from syslogd@localhost at Jun 10 14:56:47 ...
kernel: [<f81d79d2>] ? i915_gem_create_ioctl+0x39/0x97 [i915]

Message from syslogd@localhost at Jun 10 14:56:47 ...
kernel: [<c02fe934>] ? copy_from_user+0x40/0x63

Message from syslogd@localhost at Jun 10 14:56:47 ...
kernel: [<f8185578>] ? drm_ioctl+0x20d/0x2a9 [drm]

Message from syslogd@localhost at Jun 10 14:56:47 ...
kernel: [<f81d7999>] ? i915_gem_create_ioctl+0x0/0x97 [i915]

Message from syslogd@localhost at Jun 10 14:56:47 ...
kernel: [<c021b1c0>] ? update_curr+0xc4/0xff

Message from syslogd@localhost at Jun 10 14:56:47 ...
kernel: [<c023aac8>] ? hrtimer_forward+0xf2/0x108

Message from syslogd@localhost at Jun 10 14:56:47 ...
kernel: [<c023deed>] ? getnstimeofday+0x52/0xd6

Message from syslogd@localhost at Jun 10 14:56:47 ...
kernel: [<c020f52c>] ? lapic_next_event+0x16/0x1a

Message from syslogd@localhost at Jun 10 14:56:47 ...
kernel: [<c029be3d>] ? vfs_ioctl+0x4e/0x67

Message from syslogd@localhost at Jun 10 14:56:47 ...
kernel: [<c029c2d5>] ? do_vfs_ioctl+0x47f/0x4ce

Message from syslogd@localhost at Jun 10 14:56:47 ...
kernel: [<c025f39d>] ? __rcu_process_callbacks+0x104/0x170

Message from syslogd@localhost at Jun 10 14:56:47 ...
kernel: [<c029c364>] ? sys_ioctl+0x40/0x5a

Message from syslogd@localhost at Jun 10 14:56:47 ...
kernel: [<c0202904>] ? sysenter_do_call+0x12/0x22

Message from syslogd@localhost at Jun 10 14:56:47 ...
kernel:Code: 84 00 00 00 8b 42 10 89 45 ec 8b 3a 85 ff 75 16 52 8b 45 e8 83 c9 ff 8b 55 e0 53 e8 af e9 ff ff 59 5f 89 c3 eb 0a 8b 42 0c 89 fb <8b> 04 87 89 02 56 9d 66 83 7d e0 00 79 20 85 db 74 1c 8b 4d ec

Message from syslogd@localhost at Jun 10 14:56:47 ...
kernel:EIP: [<c028d827>] __kmalloc+0xdf/0x155 SS:ESP 0068:f67c3e1c

Message from syslogd@localhost at Jun 10 14:56:47 ...
kernel:CR2: 0000000000000001


Reproduce steps:
----------------
1.xinit&
2.run 100gears.sh (in the attachment)
Comment 1 liuhaien 2009-06-10 00:11:37 UTC
Created attachment 26621 [details]
100gears.sh
Comment 2 liuhaien 2009-06-10 00:12:37 UTC
Created attachment 26622 [details]
xorg.0.log
Comment 3 fangxun 2009-09-09 02:21:25 UTC
This issue still exists with following commits:

Libdrm:    (master)121b9648f846d900e67818869974ee82046e9b25
Mesa:      (mesa_7_6_branch)9216b4e7be942fed432ceb42a4337d7298d0bc6c
Xserver:    (server-1.6-branch)3044711412d0a08ba65a491bd2441c0c8980f5e2
Xf86_video_intel:  (master)94fc93d4e2b88565dca17f72903d8991213c9ee8
Kernel:      (master)e07cccf4046978df10f2e13fe2b99b2f9b3a65db
Comment 4 Chris Wilson 2010-02-23 03:42:08 UTC
commit 845792d940f5755b7a7837c450a71d9e831a13e2
Author: Jiri Slaby <jirislaby@gmail.com>
Date:   Mon Jul 13 23:20:21 2009 +0200

    drm: drm_gem, check kzalloc retval
    
    Check kzalloc retval against NULL in drm_gem_object_alloc and bail out
    appropriately.
    
    While at it merge the fail paths and jump to them by gotos at the end
    of the function.
    
    Signed-off-by: Jiri Slaby <jirislaby@gmail.com>
    Signed-off-by: Dave Airlie <airlied@linux.ie>

Comment 5 fangxun 2010-02-24 20:35:29 UTC
Verified with current code.
Comment 6 Elizabeth 2017-10-06 14:54:44 UTC
Closing old verified.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.