Bug 7760 - "invalid io allocation" error with radeon driver
Summary: "invalid io allocation" error with radeon driver
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/Radeon (show other bugs)
Version: 7.2 (2007.02)
Hardware: x86 (IA32) Linux (All)
: high normal
Assignee: Xorg Project Team
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-08-03 14:46 UTC by Ryan Lovett
Modified: 2010-10-20 05:39 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
/etc/X11/xorg.conf (1.78 KB, text/plain)
2006-08-03 14:46 UTC, Ryan Lovett
no flags Details
The X log (1.29 KB, text/plain)
2006-08-04 09:52 UTC, Ryan Lovett
no flags Details
The real X log (26.55 KB, text/plain)
2006-08-04 09:58 UTC, Ryan Lovett
no flags Details
Xorg log from latest Ubuntu Dapper (43.95 KB, text/plain)
2006-10-21 14:19 UTC, Alex Muntada
no flags Details
Xorg.0.log from latest Ubuntu Gustsy (23.14 KB, text/plain)
2007-09-22 04:33 UTC, Alex Muntada
no flags Details
Default config by dpkg-reconfigure xserver-xorg in Gutsy (2.36 KB, text/plain)
2007-09-22 04:38 UTC, Alex Muntada
no flags Details

Description Ryan Lovett 2006-08-03 14:46:02 UTC
On Ubuntu 6.06 amd64, Xorg fails to launch with the error "invalid io
allocation". The vesa driver seems to work fine. Ubuntu's bug tracker told me to
report this upstream.

# lspci | grep ATI
0000:09:00.0 VGA compatible controller: ATI Technologies Inc Radeon R200 QL
[Radeon 8500 LE]


xserver-xorg 7.0.0-0ubuntu45
xserver-xorg-driver-ati 6.5.7.3-0ubuntu7
Comment 1 Ryan Lovett 2006-08-03 14:46:28 UTC
Created attachment 6447 [details]
/etc/X11/xorg.conf
Comment 2 Michel Dänzer 2006-08-04 04:48:17 UTC
Please attach a log file from an attempt to start the X server with the radeon
driver.

Does this also happen without specifying the BusID?
Comment 3 Ryan Lovett 2006-08-04 09:52:58 UTC
Created attachment 6454 [details]
The X log
Comment 4 Ryan Lovett 2006-08-04 09:58:14 UTC
Created attachment 6455 [details]
The real X log

The previous was a redirect from stderr/stdout; please ignore.
Comment 5 Ryan Lovett 2006-08-04 10:01:13 UTC
Thanks for your inquiry. I commented out the BusID line and the same thing happened.
Comment 6 Michel Dänzer 2006-08-06 10:56:01 UTC
Thanks. Does this still happen with xf86-video-ati git ati-1-0-branch or master?
Comment 7 Alex Muntada 2006-10-21 14:15:43 UTC
I get the same error, though no memory errors are shown:

...
(WW) ****INVALID IO ALLOCATION**** b: 0xf0000400 e: 0xf00004ff correcting^G
(EE) end of block range 0xefffffff < begin 0xf0000000
...

I'll be attaching the whole log file next.

BTW, if I manage to test the latest driver from git I'll report back,
but first I'll try to upgrade my Ubuntu Dapper to Edgy.
Comment 8 Alex Muntada 2006-10-21 14:19:57 UTC
Created attachment 7482 [details]
Xorg log from latest Ubuntu Dapper

This error happened always, whatever the xorg.conf changes I've ever made.
Comment 9 Alex Muntada 2007-09-22 04:33:53 UTC
Created attachment 11680 [details]
Xorg.0.log from latest Ubuntu Gustsy

The INVALID IO ALLOCATION error is still present in xserver-xorg-video-ati 6.7.193-1ubuntu1.
Comment 10 Alex Muntada 2007-09-22 04:36:26 UTC
Just added a new Xorg.0.log to show that this error still persists in latest driver version available.

The error was produced using a default generated xorg.conf, which I'm attaching next.
Comment 11 Alex Muntada 2007-09-22 04:38:44 UTC
Created attachment 11681 [details]
Default config by dpkg-reconfigure xserver-xorg in Gutsy
Comment 12 Alex Deucher 2008-12-02 23:36:35 UTC
are you still seeing this in a more recent release or in ati git master?
Comment 13 Ryan Lovett 2008-12-03 00:38:39 UTC
No, I could not reproduce this with Ubuntu Intrepid. I can't speak for Alex Muntada though.
Comment 14 Alex Muntada 2008-12-08 15:52:05 UTC
I'm still running ubuntu hardy on my MacMini and this error is still present (xserver-xorg-video-ati is version 1:6.8.0-1), so I downloaded current ati git master (Xorg.0.log says version 6.9.0) but the result is the same: the error still shows in the log.

I'm not attaching the log since there are only a few differences (/dev/dri/card0 is now OK):

@@ -223,7 +223,7 @@
 (II) LoadModule: "ati"
 (II) Loading /usr/lib/xorg/modules/drivers//ati_drv.so
 (II) Module ati: vendor="X.Org Foundation"
-       compiled for 1.4.0.90, module version = 6.8.0
+       compiled for 1.4.0.90, module version = 6.9.0
        Module class: X.Org Video Driver
        ABI class: X.Org Video Driver, version 2.0
 (II) LoadModule: "radeon"
@ -457,9 +457,7 @@
 (WW) RADEON(0): Attempting to read Video BIOS from legacy ISA space!
 (WW) RADEON(0): Unrecognized BIOS signature, BIOS data will not be used
 drmOpenDevice: node name is /dev/dri/card0
-drmOpenDevice: open result is -1, (No such device or address)
-drmOpenDevice: open result is -1, (No such device or address)
-drmOpenDevice: Open failed
+drmOpenDevice: open result is 6, (OK)
 drmOpenByBusid: Searching for BusID pci:0000:00:10.0
 drmOpenDevice: node name is /dev/dri/card0
 drmOpenDevice: open result is 6, (OK)

Let me know if I can help in any way.
Comment 15 Alex Deucher 2010-10-19 15:44:50 UTC
Is this still an issue with kms or a more recent driver?
Comment 16 Alex Muntada 2010-10-20 01:26:54 UTC
After upgrading to ubuntu karmic the message disappeared.

Let me know if you want me to upgrade to newer versions or provide some logs, etc.
Comment 17 Julien Cristau 2010-10-20 05:39:03 UTC
(In reply to comment #16)
> After upgrading to ubuntu karmic the message disappeared.
> 
Let's call this fixed then.  Thanks.


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.