Bug 25747 - radeon drm oops with benchmark=1
Summary: radeon drm oops with benchmark=1
Status: RESOLVED INVALID
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Radeon (show other bugs)
Version: XOrg git
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-21 13:38 UTC by Andrew Randrianasulu
Modified: 2017-01-29 07:17 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
kernel .config (95.19 KB, text/plain)
2009-12-21 13:43 UTC, Andrew Randrianasulu
no flags Details

Description Andrew Randrianasulu 2009-12-21 13:38:31 UTC
Using Linus' master tree up to commit dd59f6c76b265ed2ff18b497d6105a9511b1feb1
Merge: 70e66a5... acadbfb...
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Dec 19 12:38:55 2009 -0800

    Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/mattst88/alpha-2.6

i still have stack trace after attempt to load radeon module with benchmark=1 parameter.  tried with default (none) extra options, and also with agpmode=1 (1x mode). Same result.

Dec 21 23:12:07 (none) kernel: BUG: unable to handle kernel NULL pointer dereference at (null)
Dec 21 23:12:07 (none) kernel: IP: [<(null)>] (null)
Dec 21 23:12:07 (none) kernel: *pde = 00000000 
Dec 21 23:12:07 (none) kernel: Oops: 0000 [#1] SMP 
Dec 21 23:12:07 (none) kernel: last sysfs file: /sys/class/firmware/radeon_cp.0/loading
Dec 21 23:12:07 (none) kernel: Modules linked in: radeon(+) ttm drm_kms_helper drm i2c_algo_bit cfbcopyarea cfbimgblt cfbfillrect snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_pcm_oss snd_mixer_oss nfsd lockd nfs_acl auth_rpcgss sunrpc ipv6 uhci_hcd tuner_simple tuner_types snd_cs4236 tda9887 snd_mpu401 snd_wavefront snd_via82xx tda8290 snd_wss_lib snd_ac97_codec ac97_bus snd_pcm snd_opl3_lib ppdev snd_timer snd_hwdep snd_page_alloc ehci_hcd snd_mpu401_uart saa7134 snd_rawmidi rtc_cmos snd_seq_device parport_pc rtc_core rtc_lib ns558 ir_common shpchp floppy gameport snd parport videobuf_dma_sg pci_hotplug processor thermal soundcore button usbcore 8139too videobuf_core ir_core tveeprom mii via_agp mousedev evdev ufs xfs exportfs agpgart psmouse tuner v4l2_common videodev v4l1_compat w83627hf hwmon_vid hwmon i2c_viapro i2c_dev i2c_core fbcon tileblit font bitblit softcursor fb via82cxxx ide_gd_mod ide_core
Dec 21 23:12:07 (none) kernel: 
Dec 21 23:12:07 (none) kernel: EIP: 0060:[<00000000>] EFLAGS: 00010246 CPU: 0
Dec 21 23:12:07 (none) kernel: EIP is at 0x0
Dec 21 23:12:07 (none) kernel: EAX: cd6d1000 EBX: d11fee38 ECX: 00000000 EDX: e0201000
Dec 21 23:12:07 (none) kernel: ESI: 00000000 EDI: cd6d1000 EBP: cd6a2e20 ESP: cd6a2dd0
Dec 21 23:12:07 (none) kernel:  DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
Dec 21 23:12:07 (none) kernel: Process modprobe (pid: 3708, ti=cd6a2000 task=cd4bda20 task.ti=cd6a2000)
Dec 21 23:12:07 (none) kernel: Stack:
Dec 21 23:12:07 (none) kernel:  d11cb325 00040000 00000000 00000100 cbb90100 00000002 00100000 00000100
Dec 21 23:12:07 (none) kernel: <0> ffff132c 00000000 00040000 00000000 e0201000 00000000 cbb90100 cd5b6e00
Dec 21 23:12:07 (none) kernel: <0> cd5b6b00 cd6d1000 00000001 cd6d1000 cd6a2e30 d11cb4f5 00000004 00000000
Dec 21 23:12:07 (none) kernel: Call Trace:
Dec 21 23:12:07 (none) kernel:  [<d11cb325>] ? radeon_benchmark_move+0x11e/0x2d2 [radeon]
Dec 21 23:12:07 (none) kernel:  [<d11cb4f5>] ? radeon_benchmark+0x1c/0x37 [radeon]
Dec 21 23:12:07 (none) kernel:  [<d11b2778>] ? radeon_device_init+0x27d/0x292 [radeon]
Dec 21 23:12:07 (none) kernel:  [<d11b30d7>] ? radeon_driver_load_kms+0xe0/0x141 [radeon]
Dec 21 23:12:07 (none) kernel:  [<d10b08fc>] ? drm_get_dev+0x2f6/0x3c2 [drm]
Dec 21 23:12:07 (none) kernel:  [<d11e8686>] ? radeon_pci_probe+0x12/0xd4 [radeon]
Dec 21 23:12:07 (none) kernel:  [<c114ecde>] ? local_pci_probe+0x13/0x15
Dec 21 23:12:07 (none) kernel:  [<c114f74a>] ? pci_device_probe+0x48/0x6b
Dec 21 23:12:07 (none) kernel:  [<c11a0662>] ? driver_probe_device+0x7e/0x10a
Dec 21 23:12:07 (none) kernel:  [<c11a0736>] ? __driver_attach+0x48/0x64
Dec 21 23:12:07 (none) kernel:  [<c11a0037>] ? bus_for_each_dev+0x42/0x6c
Dec 21 23:12:07 (none) kernel:  [<c11a052c>] ? driver_attach+0x19/0x1b
Dec 21 23:12:07 (none) kernel:  [<c11a06ee>] ? __driver_attach+0x0/0x64
Dec 21 23:12:07 (none) kernel:  [<c119fa3f>] ? bus_add_driver+0xa7/0x1d4
Dec 21 23:12:07 (none) kernel:  [<c11a09a3>] ? driver_register+0x90/0xf0
Dec 21 23:12:07 (none) kernel:  [<c114f923>] ? __pci_register_driver+0x3d/0x96
Dec 21 23:12:07 (none) kernel:  [<d10ac789>] ? drm_init+0x60/0xb8 [drm]
Dec 21 23:12:07 (none) kernel:  [<d1213000>] ? radeon_init+0x0/0xae [radeon]
Dec 21 23:12:07 (none) kernel:  [<d12130ac>] ? radeon_init+0xac/0xae [radeon]
Dec 21 23:12:07 (none) kernel:  [<c1001143>] ? do_one_initcall+0x51/0x13b
Dec 21 23:12:07 (none) kernel:  [<c105be66>] ? sys_init_module+0xac/0x1e0
Dec 21 23:12:07 (none) kernel:  [<c1240175>] ? syscall_call+0x7/0xb
Dec 21 23:12:07 (none) kernel: Code:  Bad EIP value.
Dec 21 23:12:07 (none) kernel: EIP: [<00000000>] 0x0 SS:ESP 0068:cd6a2dd0
Dec 21 23:12:07 (none) kernel: CR2: 0000000000000000
Dec 21 23:12:07 (none) kernel: ---[ end trace c60f58aed34248be ]---
Comment 1 Andrew Randrianasulu 2009-12-21 13:41:32 UTC
additional info from /var/log/messages

----start------

Dec 21 23:11:36 (none) kernel: warning: `squid' uses 32-bit capabilities (legacy support in use)
Dec 21 23:12:06 (none) kernel: [drm] Initialized drm 1.1.0 20060810
Dec 21 23:12:06 (none) kernel: [drm] radeon defaulting to kernel modesetting.
Dec 21 23:12:06 (none) kernel: [drm] radeon kernel modesetting enabled.
Dec 21 23:12:06 (none) kernel: radeon 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Dec 21 23:12:06 (none) kernel: [drm] radeon: Initializing kernel modesetting.
Dec 21 23:12:06 (none) kernel: [drm] register mmio base: 0xDFEF0000
Dec 21 23:12:06 (none) kernel: [drm] register mmio size: 65536
Dec 21 23:12:06 (none) kernel: [drm] GPU reset succeed (RBBM_STATUS=0x00000140)
Dec 21 23:12:06 (none) kernel: [drm] Generation 2 PCI interface, using max accessible memory
Dec 21 23:12:06 (none) kernel: [drm] AGP mode requested: 1
Dec 21 23:12:06 (none) kernel: agpgart-via 0000:00:00.0: AGP 2.0 bridge
Dec 21 23:12:06 (none) kernel: agpgart-via 0000:00:00.0: putting AGP V2 device into 1x mode
Dec 21 23:12:06 (none) kernel: radeon 0000:01:00.0: putting AGP V2 device into 1x mode
Dec 21 23:12:06 (none) kernel: [drm] radeon: VRAM 128M
Dec 21 23:12:06 (none) kernel: [drm] radeon: VRAM from 0x00000000 to 0x07FFFFFF
Dec 21 23:12:06 (none) kernel: [drm] radeon: GTT 32M
Dec 21 23:12:06 (none) kernel: [drm] radeon: GTT from 0xE0000000 to 0xE1FFFFFF
Dec 21 23:12:06 (none) kernel: [drm] radeon: irq initialized.
Dec 21 23:12:06 (none) kernel: [drm] Detected VRAM RAM=128M, BAR=128M
Dec 21 23:12:06 (none) kernel: [drm] RAM width 64bits DDR
Dec 21 23:12:06 (none) kernel: [TTM] Zone  kernel: Available graphics memory: 126774 kiB.
Dec 21 23:12:06 (none) kernel: [drm] radeon: 64M of VRAM memory ready
Dec 21 23:12:06 (none) kernel: [drm] radeon: 32M of GTT memory ready.
Dec 21 23:12:06 (none) kernel: [drm] radeon: cp idle (0x02000603)
Dec 21 23:12:06 (none) kernel: [drm] Loading R200 Microcode
Dec 21 23:12:06 (none) kernel: platform radeon_cp.0: firmware: requesting radeon/R200_cp.bin
Dec 21 23:12:07 (none) kernel: [drm] radeon: ring at 0x00000000E0000000
Dec 21 23:12:07 (none) kernel: [drm] ring test succeeded in 0 usecs
Dec 21 23:12:07 (none) kernel: [drm] radeon: ib pool ready.
Dec 21 23:12:07 (none) kernel: [drm] ib test succeeded in 0 usecs
Dec 21 23:12:07 (none) kernel: Pid: 3708, comm: modprobe Not tainted 2.6.33-rc1-i486 #54 MS-6380E/MS-6380E
Dec 21 23:13:20 (none) exiting on signal 15

-----stop------

Comment 2 Andrew Randrianasulu 2009-12-21 13:43:03 UTC
Created attachment 32229 [details]
kernel .config
Comment 3 Andrew Randrianasulu 2017-01-29 07:17:31 UTC
Let me close this very old bug  - I don't have hw described here anymore, and in those 7+ years  too many things changed in drm/kernel.


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.