Ubuntu
radeontool package

EAGAIN while mapping framebuffer

Bug #812778 reported by Timo Witte on 2011-07-19

This bug affects 1 person

	Status	Importance	Assigned to
xf86-video-ati	Invalid	Medium	freedesktop-bugs #40242
libpciaccess (Ubuntu)	Invalid	Undecided	Unassigned
radeontool (Ubuntu)	Incomplete	Medium	Unassigned

Bug Description

On line ~ 964 in the file radeontool.c the framebuffer is mapped via "pci_device_map_region(avivo_device, fb_region, 1)" this operation returns a EAGAIN (error code 11), which is generated by the libpciaccess. The Frambuffer Region is found correctly (in radeontool, avivotool just searched for 128M regions). I think this might somehow be a problem with changed kernel acccess behavior over time. I ran the tool from an X Session as root, and from remote ssh (without X running in the foreground [ctrl + alt + f1])

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: radeontool 1.6.1-1
ProcVersionSignature: Ubuntu 3.0.0-5.6-generic 3.0.0-rc7
Uname: Linux 3.0.0-5-generic x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
Date: Tue Jul 19 11:14:46 2011
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
ProcEnviron:
PATH=(custom, user)
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: radeontool
UpgradeStatus: Upgraded to oneiric on 2011-05-30 (49 days ago)

Tags:

Revision history for this message

Timo Witte (spacefish) wrote on 2011-07-19:

Dependencies.txt Edit (421 bytes, text/plain; charset="utf-8")

Revision history for this message

In freedesktop.org Bugzilla #40242, Bryce Harrington (bryce) wrote on 2011-08-19:

Forwarding this bug report from Ubuntu reporter Timo Witte:
https://bugs.launchpad.net/ubuntu/+source/radeontool/+bug/812778

[Problem]
On line ~ 964 in the file radeontool.c the framebuffer is mapped via "pci_device_map_region(avivo_device, fb_region, 1)" this operation returns a EAGAIN (error code 11), which is generated by the libpciaccess. The Frambuffer Region is found correctly (in radeontool, avivotool just searched for 128M regions). I think this might somehow be a problem with changed kernel acccess behavior over time. I ran the tool from an X Session as root, and from remote ssh (without X running in the foreground [ctrl + alt + f1])

Revision history for this message

Bryce Harrington (bryce) wrote on 2011-08-19:

Hi Timo, I've forwarded your bug upstream to https://bugs.freedesktop.org/show_bug.cgi?id=40242 - please subscribe there in case the upstream developers have further questions or wish you to test something. Thanks ahead of time!

Changed in radeontool (Ubuntu):
importance:	Undecided → Medium
status:	New → Triaged

Revision history for this message

Bryce Harrington (bryce) wrote on 2011-08-19:

[For now let's just track the bug in radeontool; if the issue is actually in libpciaccess upstream will let us know.]

Changed in libpciaccess (Ubuntu):
status:	New → Invalid

Bug Watch Updater (bug-watch-updater) on 2011-08-19

Changed in xf86-video-ati:
importance:	Unknown → Medium
status:	Unknown → Confirmed

Revision history for this message

Tormod Volden (tormodvolden) wrote on 2011-08-19:

Do you see this when running "sudo radeontool" ? Which graphics card are you using, can you please run "lspci -nn|grep VGA"? Please attach /var/log/Xorg.0.log so we see all details. I notice that you are using the fglrx driver, can this be a problem? Was the fglrx module loaded when you tried over ssh?

Revision history for this message

In freedesktop.org Bugzilla #40242, Michel Dänzer (michel-daenzer) wrote on 2011-08-22:

I don't see what this has to do with the radeon X driver...

(In reply to comment #1)
> NonfreeKernelModules: fglrx

I suspect it might have something to do with this though.

Bryce Harrington (bryce) on 2011-08-22

Changed in radeontool (Ubuntu):
status:	Triaged → Incomplete

Revision history for this message

In freedesktop.org Bugzilla #40242, Ajax-a (ajax-a) wrote on 2018-06-12:

Mass closure: This bug has been untouched for more than six years, and is not
obviously still valid. Please reopen this bug or file a new report if you continue to experience issues with current releases.

Bug Watch Updater (bug-watch-updater) on 2018-06-13