driver crash radeon_gart.c:187 radeon_gart_bind+0x1b4/0x1c0

Bug #1007901 reported by marnus
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Linux Mint
New
Undecided
Unassigned
Fedora
Fix Released
Undecided
linux (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Linux 3.2.0-24-generic #39-Ubuntu SMP Mon May 21 16:52:17 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
Linux Mint 13 maya
MATE x64

I have upgraded my Linux Mint system from previous kernel version 3.2.0-23 and after reboot I get error on screen may be thousands of times:

Failed to allocate:
size: 4096000 bytes
aligment: 0 bytes
domains: 2

and in dmesg is this:

WARNING: at /build/buildd/linux-3.2.0/drivers/gpu/drm/radeon/radeon_gart.c:187 radeon_gart_bind+0x1b4/0x1c0 [radeon]()
[ 23.157299] Hardware name: AMILO Pa 2510
[ 23.157301] trying to bind memory to uninitialized GART !
[ 23.157303] Modules linked in: rfcomm bnep bluetooth parport_pc ppdev binfmt_misc nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc ext2 ip6t_LOG xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT ipt_LOG xt_limit xt_tcpudp xt_addrtype snd_hda_codec_realtek snd_hda_codec_si3054 xt_state arc4 snd_hda_intel snd_hda_codec ip6table_filter snd_hwdep ip6_tables snd_pcm snd_seq_midi nf_conntrack_netbios_ns nf_conntrack_broadcast snd_rawmidi nf_nat_ftp nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 ath5k snd_seq_midi_event nf_conntrack_ftp nf_conntrack iptable_filter ip_tables snd_seq x_tables ath radeon snd_timer mac80211 snd_seq_device joydev snd psmouse soundcore sp5100_tco serio_raw ttm snd_page_alloc cfg80211 video i2c_piix4 k8temp drm_kms_helper edac_core edac_mce_amd mac_hid drm i2c_algo_bit shpchp lp parport usbhid hid pata_atiixp r8169 usb_storage
[ 23.157372] Pid: 284, comm: plymouthd Tainted: G W 3.2.0-24-generic #39-Ubuntu
[ 23.157375] Call Trace:
[ 23.157388] [<ffffffff8106725f>] warn_slowpath_common+0x7f/0xc0
[ 23.157392] [<ffffffff81067356>] warn_slowpath_fmt+0x46/0x50
[ 23.157412] [<ffffffffa0133db2>] ? ttm_mem_global_alloc_page+0x42/0x50 [ttm]
[ 23.157433] [<ffffffffa029a5f4>] radeon_gart_bind+0x1b4/0x1c0 [radeon]
[ 23.157453] [<ffffffffa0297ef5>] radeon_ttm_backend_bind+0x35/0xb0 [radeon]
[ 23.157464] [<ffffffffa0134670>] ttm_tt_bind+0x50/0x80 [ttm]
[ 23.157473] [<ffffffffa0136597>] ttm_bo_handle_move_mem+0x347/0x3c0 [ttm]
[ 23.157482] [<ffffffffa01374ea>] ttm_bo_move_buffer+0x13a/0x150 [ttm]
[ 23.157524] [<ffffffffa008a36c>] ? drm_mm_kmalloc+0x3c/0xe0 [drm]
[ 23.157529] [<ffffffff811795ec>] ? alloc_file+0x9c/0xd0
[ 23.157539] [<ffffffffa01375e7>] ttm_bo_validate+0xe7/0xf0 [ttm]
[ 23.157547] [<ffffffffa01377a8>] ttm_bo_init+0x1b8/0x260 [ttm]
[ 23.157569] [<ffffffffa0299246>] radeon_bo_create+0x176/0x2a0 [radeon]
[ 23.157590] [<ffffffffa0298f70>] ? radeon_create_ttm_backend_entry+0x40/0x40 [radeon]
[ 23.157614] [<ffffffffa02a9d6a>] radeon_gem_object_create+0x5a/0x100 [radeon]
[ 23.157637] [<ffffffffa02aa0b8>] radeon_gem_create_ioctl+0x58/0xd0 [radeon]
[ 23.157643] [<ffffffff8129ceb1>] ? security_capable+0x21/0x30
[ 23.157657] [<ffffffffa007e5d4>] drm_ioctl+0x444/0x510 [drm]
[ 23.157682] [<ffffffffa02aa060>] ? radeon_gem_pwrite_ioctl+0x30/0x30 [radeon]
[ 23.157688] [<ffffffff8103dcf9>] ? default_spin_lock_flags+0x9/0x10
[ 23.157693] [<ffffffff811bbe2c>] ? ep_poll+0x1cc/0x380
[ 23.157698] [<ffffffff81189e0a>] do_vfs_ioctl+0x8a/0x340
[ 23.157702] [<ffffffff81177da0>] ? vfs_write+0x110/0x180
[ 23.157706] [<ffffffff8118a151>] sys_ioctl+0x91/0xa0
[ 23.157710] [<ffffffff811bc7ae>] ? sys_epoll_wait+0x8e/0xe0
[ 23.157716] [<ffffffff81664d82>] system_call_fastpath+0x16/0x1b
[ 23.157719] ---[ end trace 406cb566ecd48e27 ]---
[ 23.157724] [drm:radeon_ttm_backend_bind] *ERROR* failed to bind 1000 pages at 0x00000000
[ 23.163030] radeon 0000:01:05.0: object_init failed for (4096000, 0x00000002)
[ 23.168037] [drm:radeon_gem_object_create] *ERROR* Failed to allocate GEM object (4096000, 2, 4096, -22)

So it seems to be a problem with driver for ATI in new kernel.

Tags: mint-mate
Revision history for this message
marnus (marnus-mrs) wrote :
Revision history for this message
marnus (marnus-mrs) wrote :

I found that probably the same problem has Fedora 17, you can see the bug there in https://bugzilla.redhat.com/show_bug.cgi?id=785375.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Revision history for this message
shankao (shankao) wrote :

Is this still a problem in precise (of which Mint 13 is based from) with the latest updated kernel?

Changed in linux (Ubuntu):
status: New → Confirmed
shankao (shankao)
affects: ubuntu → linux (Ubuntu)
Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: precise
Changed in fedora:
importance: Unknown → Undecided
status: Unknown → Fix Released
Norbert (nrbrtx)
tags: removed: precise
Norbert (nrbrtx)
tags: added: mint-mate
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

This bug is too old to support. It's been almost 10 years.

Changed in linux (Ubuntu):
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.