I just came across this message and didn't see a response.
Did you find a fix?

On Fri, Jun 06, 2008 at 07:40:13PM +0200, Angelo Rossi wrote:
> 
> I got this error in debian linux sparc 64 (ultra 5 platform):
> 
> X: warning; process set to priority -1 instead of requested priority 0
> 
> X.Org X Server 1.4.0.90
> Release Date: 5 September 2007
> X Protocol Version 11, Revision 0
> Build Operating System: Linux Debian (xorg-server 2:1.4.1~git20080517-1)
> Current Operating System: Linux ULTRA5 2.6.24-1-sparc64-smp #1 SMP Thu May 8 
> 18:15:33 UTC 2008 sparc64
> Build Date: 18 May 2008  02:46:04PM
> 
>         Before reporting problems, check http://wiki.x.org
>         to make sure that you have the latest version.
> Module Loader present
> Markers: (--) probed, (**) from config file, (==) default setting,
>         (++) from command line, (!!) notice, (II) informational,
>         (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
> (==) Log file: "/var/log/Xorg.0.log", Time: Sat May 31 13:12:34 2008
> (==) Using config file: "/etc/X11/xorg.conf"
> (II) Module "ddc" already built-in
> mmap failure: Invalid argument
> 
> Fatal server error:
> xf86MapDomainMem():  mmap() failure
> 
> XIO:  fatal IO error 54 (Connection reset by peer) on X server ":0.0"
>       after 0 requests (0 known processed) with 0 events remaining.
> 
> 
> The kernel suite is: uname -a
> 
> Linux ULTRA5 2.6.24-1-sparc64-smp #1 SMP Thu May 8 18:15:33 UTC 2008 sparc64 
> GNU/Linux

I have the same problem on my Ultra5 with onboard ATI graphics card
moving from kernel 2.6.21 and 2.6.22 to 2.6.24 or 2.6.25.

I believe that this is a PCI problem that that has been mentioned here
and decribed in detail at:

http://www.mail-archive.com/[EMAIL PROTECTED]/msg01094.html

http://www.archivum.info/[EMAIL PROTECTED]/2008-06/msg00929.html

My /var/log/Xorg.0.log under 2.6.25 looks like this:

 --------------------------------------------------------
X.Org X Server 1.4.0.90
Release Date: 5 September 2007
X Protocol Version 11, Revision 0
Build Operating System: Linux Debian (xorg-server 2:1.4.1~git20080517-1)
Current Operating System: Linux ultra5 2.6.25-2-sparc64 #2 Fri Jun 27 
 05:32:02 UTC 2008 sparc64
Build Date: 18 May 2008  02:46:04PM

(II) MACH64: Driver for ATI Mach64 chipsets
(II) Primary Device is: PCI 01:02:0
(--) Chipset ATI 3D Rage Pro found
(II) resource ranges after xf86ClaimFixedResources() call:
        [0] -1  1       0x0000a000 - 0x0000a0ff (0x100) MX[B]
        [1] -1  1       0x00008000 - 0x00008fff (0x1000) MX[B]
        [2] -1  1       0x00006000 - 0x00006fff (0x1000) MX[B]
        [3] -1  1       0x00004000 - 0x00004fff (0x1000) MX[B]
        [4] -1  1       0x00002000 - 0x000020ff (0x100) MX[B]
        [5] -1  1       0xe0000000 - 0xe000001f (0x20) MX[B]
        [6] -1  1       0xf1000000 - 0xf1000000 (0x1) MX[B]
        [7] -1  1       0xf0000000 - 0xf0000000 (0x1) MX[B]
        [8] -1  1       0xe1020000 - 0xe1020000 (0x1) MX[B](B)
        [9] -1  1       0xe2000000 - 0xe2000fff (0x1000) MX[B](B)
        [10] -1 1       0xe1000000 - 0xe1ffffff (0x1000000) MX[B](B)
        [11] -1 1       0x00000400 - 0x000004ff (0x100) IX[B]
        [12] -1 1       0x00c00020 - 0x00c0002f (0x10) IX[B]
        [13] -1 1       0x00c00018 - 0x00c0001b (0x4) IX[B]
        [14] -1 1       0x00c00010 - 0x00c00017 (0x8) IX[B]
        [15] -1 1       0x00c00008 - 0x00c0000b (0x4) IX[B]
        [16] -1 1       0x00c00000 - 0x00c00007 (0x8) IX[B]
(WW) ****INVALID MEM ALLOCATION**** b: 0xe1000000 e: 0xe1ffffff correcting
(II) window:
(II) resSize:
        [0] -1  1       0x00000000 - 0xffffffff (0x0) MX[B]
(II) window fixed:
(WW) ****INVALID MEM ALLOCATION**** b: 0xe2000000 e: 0xe2000fff correcting
(II) window:
(II) resSize:
        [0] -1  1       0x00000000 - 0xffffffff (0x0) MX[B]
(II) window fixed:
(II) resource ranges after probing:
        [0] -1  1       0x00000000 - 0xffffffff (0x0) MX[B](B)
        [1] -1  1       0x00000000 - 0xffffffff (0x0) MX[B](B)
        [2] -1  1       0x0000a000 - 0x0000a0ff (0x100) MX[B]
        [3] -1  1       0x00008000 - 0x00008fff (0x1000) MX[B]
        [4] -1  1       0x00006000 - 0x00006fff (0x1000) MX[B]
        [5] -1  1       0x00004000 - 0x00004fff (0x1000) MX[B]
        [6] -1  1       0x00002000 - 0x000020ff (0x100) MX[B]
        [7] -1  1       0xe0000000 - 0xe000001f (0x20) MX[B]
        [8] -1  1       0xf1000000 - 0xf1000000 (0x1) MX[B]
        [9] -1  1       0xf0000000 - 0xf0000000 (0x1) MX[B]
        [10] -1 1       0xe1020000 - 0xe1020000 (0x1) MX[B](B)
        [11] 0  1       0x000a0000 - 0x000affff (0x10000) MS[B]
        [12] 0  1       0x000b0000 - 0x000b7fff (0x8000) MS[B]
        [13] 0  1       0x000b8000 - 0x000bffff (0x8000) MS[B]
        [14] -1 1       0x00000400 - 0x000004ff (0x100) IX[B]
        [15] -1 1       0x00c00020 - 0x00c0002f (0x10) IX[B]
        [16] -1 1       0x00c00018 - 0x00c0001b (0x4) IX[B]
        [17] -1 1       0x00c00010 - 0x00c00017 (0x8) IX[B]
        [18] -1 1       0x00c00008 - 0x00c0000b (0x4) IX[B]
        [19] -1 1       0x00c00000 - 0x00c00007 (0x8) IX[B]
        [20] 0  1       0x000003b0 - 0x000003bb (0xc) IS[B]
        [21] 0  1       0x000003c0 - 0x000003df (0x20) IS[B]
(II) Setting vga for screen 0.
(II) MACH64(0): Creating default Display subsection in Screen section
        "Default Screen" for depth/fbbpp 24/32
(**) MACH64(0): Depth 24, (--) framebuffer bpp 32
(==) MACH64(0): Using XAA acceleration architecture
(WW) MACH64: Mach64 in slot 1:2:0 could not be detected!
(II) UnloadModule: "mach64"
(EE) Screen(s) found, but none have a usable configuration.

Fatal server error:
no screens found
 ----------------------------------------------------------------

I also had a problem booting directly to a SCSI drive attached to
this PCI card using the newer kernels.

02:01.0 SCSI storage controller: LSI Logic / Symbios Logic 53c875 (rev 03)
        Flags: bus master, medium devsel, latency 136, IRQ 15
        I/O ports at 1fe02000400 [size=256]
        Memory at 1ff00002000 (32-bit, non-prefetchable) [size=256]
        Memory at 1ff00004000 (32-bit, non-prefetchable) [size=4K]

For the time being I have simply gone back to using kernel 2.6.21
(unstable) or 2.6.22 (testing) and all is well.

Regards,

Howard E.
Ottawa


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to