Bug 40216

Summary: X crashes when I open some specific pictures in Firefox. I can reproduce this at reliably.
Product: DRI Reporter: Steven Koutstaal <skoutstaal>
Component: DRM/RadeonAssignee: Default DRI bug account <dri-devel>
Status: RESOLVED MOVED QA Contact:
Severity: major    
Priority: medium    
Version: XOrg git   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
Xorg.0.log with crash.
none
Bus error debugging none

Description Steven Koutstaal 2011-08-19 02:16:00 UTC
Created attachment 50368 [details]
Xorg.0.log with crash.

**Relavant lines in the log file;

[146065.387]
Backtrace:
[146065.387] 0: /usr/bin/X (xorg_backtrace+0x3b) [0x80eab8b]
[146065.387] 1: /usr/bin/X (0x8048000+0x5fb38) [0x80a7b38]
[146065.387] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0xd1440c]
[146065.387] 3: /usr/lib/xorg/modules/drivers/radeon_drv.so (0x746000+0xa29f1) [0x7e89f1]
[146065.387] 4: /usr/lib/xorg/modules/libexa.so (0x15e000+0x8f4f) [0x166f4f]
[146065.387] 5: /usr/bin/X (0x8048000+0xe2905) [0x812a905]
[146065.387] 6: /usr/bin/X (0x8048000+0x24988) [0x806c988]
[146065.387] 7: /usr/bin/X (0x8048000+0x28167) [0x8070167]
[146065.387] 8: /usr/bin/X (0x8048000+0x1a81c) [0x806281c]
[146065.387] 9: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xe7) [0x53ee37]
[146065.388] 10: /usr/bin/X (0x8048000+0x1a411) [0x8062411]
[146065.388] Bus error at address 0xb36d7008
[146065.388]
Caught signal 7 (Bus error). Server aborting
[146065.388]


**My display adapter, according to lspci
01:00.0 VGA compatible controller: ATI Technologies Inc M64-S [Mobility Radeon X2300]

**radeon-related dmesg messages
# dmesg | grep -i radeon
[   15.353469] [drm] radeon defaulting to kernel modesetting.
[   15.353471] [drm] radeon kernel modesetting enabled.
[   15.353525] radeon 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[   15.353531] radeon 0000:01:00.0: setting latency timer to 64
[   15.354812] radeon 0000:01:00.0: VRAM: 128M 0x0000000000000000 - 0x0000000007FFFFFF (128M used)
[   15.354815] radeon 0000:01:00.0: GTT: 512M 0x0000000008000000 - 0x0000000027FFFFFF
[   15.354868] radeon 0000:01:00.0: irq 46 for MSI/MSI-X
[   15.354873] radeon 0000:01:00.0: radeon: using MSI.
[   15.354895] [drm] radeon: irq initialized.
[   15.359633] [drm] radeon: 128M of VRAM memory ready
[   15.359635] [drm] radeon: 512M of GTT memory ready.
[   15.361088] [drm] radeon: 1 quad pipes, 1 z pipes initialized.
[   15.362373] radeon 0000:01:00.0: WB enabled
[   15.409831] [drm] radeon: ring at 0x0000000008001000
[   15.410001] [drm] radeon: ib pool ready.
[   15.414531] [drm] Radeon Display Connectors
[   15.541601] [drm] radeon: power management initialized
[   15.775058] fbcon: radeondrmfb (fb0) is primary device
[   15.775648] fb0: radeondrmfb frame buffer device
[   15.775656] [drm] Initialized radeon 2.8.0 20080528 for 0000:01:00.0 on minor 0
Comment 1 Michel Dänzer 2011-08-19 05:19:31 UTC
Can you try a newer kernel, e.g. 3.0.x?

Please attach the full dmesg output, captured after the problem occurred.

Can you point to any specific pictures triggering the problem?
Comment 2 Steven Koutstaal 2011-08-19 05:44:21 UTC
> Can you try a newer kernel, e.g. 3.0.x?

Not right now. I use the machine for work.. Maybe in the weekend I can make some time..

 
> Please attach the full dmesg output, captured after the problem occurred.

dmesg does not show anything for the crash.

 
> Can you point to any specific pictures triggering the problem?

For example this one;
  http://www.koutstaal.com/foobar/IMG_0580.JPG


Please let me know if I need to run some debugs while the crash happens, this is not a big problem.

thx,
/steven
Comment 3 Michel Dänzer 2011-08-19 06:15:24 UTC
Created attachment 50374 [details] [review]
Bus error debugging

This patch should generate more output in dmesg when the bus error occurs.
Comment 4 Martin Peres 2019-11-19 08:20:32 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/210.

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.