All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 31708] New: kernel oops when loading large images with firefox
Date: Thu, 18 Nov 2010 03:07:17 -0800 (PST)	[thread overview]
Message-ID: <bug-31708-502@http.bugs.freedesktop.org/> (raw)

https://bugs.freedesktop.org/show_bug.cgi?id=31708

           Summary: kernel oops when loading large images with firefox
           Product: DRI
           Version: XOrg CVS
          Platform: x86 (IA32)
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Radeon
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: manuel.lauss@gmail.com


The following kernel oops happens whenever a very large image is loaded in
firefox:
(RV350, 855PM AGP):

------------[ cut here ]------------
kernel BUG at /usr/src/linux-2.6.git/drivers/gpu/drm/ttm/ttm_bo.c:1123!
invalid opcode: 0000 [#1] PREEMPT
last sysfs file:
/sys/devices/LNXSYSTM:00/device:00/PNP0A03:00/device:10/PNP0C09:00/PNP0C0A:00/power_supply/BAT1/energy_full
Modules linked in: ipw2200 libipw

Pid: 5117, comm: X Not tainted 2.6.37-rc2 #1 /VGN-A197XP(DE)
EIP: 0060:[<b143104a>] EFLAGS: 00013202 CPU: 0
EIP is at ttm_bo_check_placement+0x1a/0x20
EAX: d8ae262c EBX: ee97a40c ECX: 00000000 EDX: 00004000
ESI: 00000000 EDI: 04258000 EBP: b1466370 ESP: df8f3d74
DS: 007b ES: 007b FS: 0000 GS: 0033 SS: 0068
Process X (pid: 5117, ti=df8f2000 task=ed535000 task.ti=df8f2000)
Stack:
b143379d 00000000 cd4b19c8 018f3da8 d8ae262c d8ae2600 ee97a000 00000000
cd4ab6c0 b14662a0 00000000 d8ae2614 00000000 00000000 00000001 00000000
04258000 b1466370 00000000 04258000 ee97b648 ee97a40c 00000001 cd4ab6c0
Call Trace:
[<b143379d>] ? ttm_bo_init+0x16d/0x350
[<b14662a0>] ? radeon_bo_create+0xe0/0x1b0
[<b1466370>] ? radeon_ttm_bo_destroy+0x0/0x90
[<b147a618>] ? radeon_gem_object_create+0x78/0x100
[<b147a702>] ? radeon_gem_create_ioctl+0x62/0xd0
[<b141eefe>] ? drm_ioctl+0x19e/0x440
[<b147a6a0>] ? radeon_gem_create_ioctl+0x0/0xd0
[<b1090165>] ? do_sync_read+0xa5/0xe0
[<b1047f69>] ? ktime_get+0x59/0x100
[<b141ed60>] ? drm_ioctl+0x0/0x440
[<b109e47c>] ? do_vfs_ioctl+0x9c/0x700
[<b102d55c>] ? irq_exit+0x2c/0x70
[<b109eb1d>] ? sys_ioctl+0x3d/0x70
[<b1002d50>] ? sysenter_do_call+0x12/0x26
Code: 0f 0b eb fe 8d b6 00 00 00 00 8d bc 27 00 00 00 00 8b 0a 85 c9 75 0a 8b
52 04 85 d2 75 06 31 c0 c3 8b 52 04 29 ca 39 50 40 76 f3 <0f> 0b eb ff
EIP: [<b143104a>] ttm_bo_check_placement+0x1a/0x20 SS:ESP 0068:df8f3d74
---[ end trace a8625bcdd779303f ]---


Linux agpgart interface v0.103
agpgart-intel 0000:00:00.0: Intel 855PM Chipset
agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xe0000000
[drm] Initialized drm 1.1.0 20060810
[drm] radeon defaulting to kernel modesetting.
[drm] radeon kernel modesetting enabled.
ACPI: PCI Interrupt Link [LNKE] enabled at IRQ 9
radeon 0000:01:00.0: PCI INT A -> Link[LNKE] -> GSI 9 (level, low) -> IRQ 9
[drm] initializing kernel modesetting (RV350 0x1002:0x4E50).
[drm] register mmio base: 0xFF5F0000
[drm] register mmio size: 65536
agpgart-intel 0000:00:00.0: AGP 2.0 bridge
agpgart-intel 0000:00:00.0: putting AGP V2 device into 4x mode
radeon 0000:01:00.0: putting AGP V2 device into 4x mode
radeon 0000:01:00.0: GTT: 256M 0xE0000000 - 0xEFFFFFFF
[drm] Generation 2 PCI interface, using max accessible memory
radeon 0000:01:00.0: VRAM: 128M 0xD0000000 - 0xD7FFFFFF (64M used)
[drm] radeon: irq initialized.
[drm] Detected VRAM RAM=128M, BAR=128M
[drm] RAM width 128bits DDR
[TTM] Zone  kernel: Available graphics memory: 513282 kiB.
[TTM] Initializing pool allocator.
[drm] radeon: 64M of VRAM memory ready
[drm] radeon: 256M of GTT memory ready.
[drm] radeon: 1 quad pipes, 1 Z pipes initialized.
radeon 0000:01:00.0: WB disabled
[drm] Loading R300 Microcode
[drm] radeon: ring at 0x00000000E0001000
[drm] ring test succeeded in 1 usecs
[drm] radeon: ib pool ready.
[drm] ib test succeeded in 0 usecs
[drm] Panel ID String: 1920X1200 WUXGA         
[drm] Panel Size 1920x1200
[drm] Radeon Display Connectors
[drm] Connector 0:
[drm]   VGA
[drm]   DDC: 0x60 0x60 0x60 0x60 0x60 0x60 0x60 0x60
[drm]   Encoders:
[drm]     CRT1: INTERNAL_DAC1
[drm] Connector 1:
[drm]   DVI-D
[drm]   HPD1
[drm]   DDC: 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64
[drm]   Encoders:
[drm]     DFP1: INTERNAL_TMDS1
[drm] Connector 2:
[drm]   LVDS
[drm]   Encoders:
[drm]     LCD1: INTERNAL_LVDS
[drm] Connector 3:
[drm]   S-video
[drm]   Encoders:
[drm]     TV1: INTERNAL_DAC2
[drm] fb mappable at 0xD0040000
[drm] vram apper at 0xD0000000
[drm] size 9216000
[drm] fb depth is 24
[drm]    pitch is 7680
Console: switching to colour frame buffer device 240x75
fb0: radeondrmfb frame buffer device
drm: registered panic notifier
[drm] Initialized radeon 2.7.0 20080528 for 0000:01:00.0 on minor 0

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

             reply	other threads:[~2010-11-18 11:07 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-18 11:07 bugzilla-daemon [this message]
2010-11-18 12:47 ` [Bug 31708] kernel oops when loading large images with firefox bugzilla-daemon
2010-11-18 13:07 ` bugzilla-daemon
2010-11-18 18:38 ` bugzilla-daemon
2010-11-18 18:52 ` bugzilla-daemon
2010-11-18 19:42 ` bugzilla-daemon
2010-11-19 20:56 ` bugzilla-daemon
2010-11-21 19:32 ` bugzilla-daemon
2010-11-22 15:29 ` bugzilla-daemon
2010-11-22 15:30 ` bugzilla-daemon
2010-11-22 17:23 ` bugzilla-daemon
2010-11-22 17:24 ` bugzilla-daemon
2010-11-22 17:34 ` bugzilla-daemon
2010-11-22 17:48 ` bugzilla-daemon
2010-12-15 20:11 ` bugzilla-daemon
2010-12-20 18:25 ` bugzilla-daemon
2011-03-07 19:11 ` [Bug 31708] [RADEON:KMS:TTM] " bugzilla-daemon
2012-09-14  7:08 ` bugzilla-daemon
2012-09-14 10:49 ` bugzilla-daemon
2012-09-14 15:42 ` bugzilla-daemon
2012-09-14 15:48 ` bugzilla-daemon
2012-09-15  8:19 ` bugzilla-daemon
2012-09-15 14:25 ` bugzilla-daemon
2012-09-15 15:18 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-31708-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.