NetBSD-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: xsrc/50429: Xserver fails to start on Ultra-5 andNetBSD/sparc64 7.0



The following reply was made to PR xsrc/50429; it has been noted by GNATS.

From: Izumi Tsutsui <tsutsui%ceres.dti.ne.jp@localhost>
To: macallan%netbsd.org@localhost
Cc: gnats-bugs%NetBSD.org@localhost, tsutsui%ceres.dti.ne.jp@localhost
Subject: Re: xsrc/50429: Xserver fails to start on Ultra-5 andNetBSD/sparc64
	 7.0
Date: Sun, 15 Nov 2015 15:52:36 +0900

 (cc'ed to gnats-bugs@)
 
 macallan@ wrote:
 
 > > [   297.885] (EE) Unable to map mmio aperture. Invalid argument (22)
 > > [   297.887] (EE) Unable to map mmio aperture. Invalid argument (22)
 > 
 > That's the failure, and this...
 > 
 > > [   296.972] (--) PCI:*(1:1:2:0) 1002:4754:0000:0000 rev 154, Mem @
 > > 0xe1000000/16777216, 0x00000000/4096, I/O @ 0x00000000/256, BIOS @
 > > 0x????????/131072
 > 
 > ... seems to be the cause, the MMIO aperture is either not configured
 > or not implemented by hardware - I've seen both on Sun hardware. This
 > appears to be a Rage II, so it's not implemented. The driver *should*
 > fall back to using the I/O aperture, which may or may not work
 > correctly either, at 0x0. Failing that, it should use the register
 > mapping in the main aperture. Something in that logic is apparently
 > broken.
 > Please post the card's pcictl dump output and ( assuming you're using
 > machfb ) the machfb output from dmesg.
 
 dmesg:
 ---
 machfb0 at pci1 dev 2 function 0: ATI Technologies 3D Rage I/II (rev. 0x9a)
 machfb0: 16 MB aperture at 0xe1000000, 4 KB registers at 0x00000000
 machfb0: 128 KB ROM at 0xe1020000
 machfb0: 2048 KB SGRAM 62.999 MHz, maximum RAMDAC clock 170 MHz
 machfb0: initializing the DSP
 machfb0: initial resolution 1152x864 at 8 bpp
 machfb0: initializing the DSP
 wsdisplay1 at machfb0 kbdmux 1
 wsmux1: connecting to wsdisplay1
 wsdisplay1: screen 0-3 added (default)
 direct rendering for machfb0 unsupported
 ---
 
 Full dmesg is here:
  http://dmesgd.nycbug.org/index.cgi?action=dmesgd&do=view&id=2850
 
 pcictl dump:
 ---
 # pcictl /dev/pci1 dump -d 2
 PCI configuration registers:
   Common header:
     0x00: 0x47541002 0x02800087 0x0300009a 0x00004240
 
     Vendor Name: ATI Technologies (0x1002)
     Device Name: 3D Rage I/II (0x4754)
     Command register: 0x0087
       I/O space accesses: on
       Memory space accesses: on
       Bus mastering: on
       Special cycles: off
       MWI transactions: off
       Palette snooping: off
       Parity error checking: off
       Address/data stepping: on
       System error (SERR): off
       Fast back-to-back transactions: off
       Interrupt disable: off
     Status register: 0x0280
       Interrupt status: inactive
       Capability List support: off
       66 MHz capable: off
       User Definable Features (UDF) support: off
       Fast back-to-back capable: on
       Data parity error detected: off
       DEVSEL timing: medium (0x1)
       Slave signaled Target Abort: off
       Master received Target Abort: off
       Master received Master Abort: off
       Asserted System Error (SERR): off
       Parity error detected: off
     Class Name: display (0x03)
     Subclass Name: VGA (0x00)
     Interface: 0x00
     Revision ID: 0x9a
     BIST: 0x00
     Header Type: 0x00 (0x00)
     Latency Timer: 0x42
     Cache Line Size: 256bytes (0x40)
 
   Type 0 ("normal" device) header:
     0x10: 0xe1000000 0x00000001 0x00000000 0x00000000
     0x20: 0x00000000 0x00000000 0x00000000 0x00000000
     0x30: 0xe1020000 0x00000000 0x00000000 0x00080131
 
     Base address register at 0x10
       type: 32-bit nonprefetchable memory
       base: 0xe1000000, not sized
     Base address register at 0x14
       type: i/o
       base: 0x00000000, not sized
     Base address register at 0x18
       not implemented(?)
     Base address register at 0x1c
       not implemented(?)
     Base address register at 0x20
       not implemented(?)
     Base address register at 0x24
       not implemented(?)
     Cardbus CIS Pointer: 0x00000000
     Subsystem vendor ID: 0x0000
     Subsystem ID: 0x0000
     Expansion ROM Base Address: 0xe1020000
     Reserved @ 0x34: 0x00000000
     Reserved @ 0x38: 0x00000000
     Maximum Latency: 0x00
     Minimum Grant: 0x08
     Interrupt pin: 0x01 (pin A)
     Interrupt line: 0x31
 
   Device-dependent header:
     0x40: 0x0000000c 0x00000000 0x00000000 0x00000000
     0x50: 0x00000000 0x00000000 0x00000000 0x00000000
     0x60: 0x00000000 0x00000000 0x00000000 0x00000000
     0x70: 0x00000000 0x00000000 0x00000000 0x00000000
     0x80: 0x00000000 0x00000000 0x00000000 0x00000000
     0x90: 0x00000000 0x00000000 0x00000000 0x00000000
     0xa0: 0x00000000 0x00000000 0x00000000 0x00000000
     0xb0: 0x00000000 0x00000000 0x00000000 0x00000000
     0xc0: 0x00000000 0x00000000 0x00000000 0x00000000
     0xd0: 0x00000000 0x00000000 0x00000000 0x00000000
     0xe0: 0x00000000 0x00000000 0x00000000 0x00000000
     0xf0: 0x00000000 0x00000000 0x00000000 0x00000000
 
 ---
 
 Note it's Ultra-5/10 on-board one.
 
 > 
 > > XAA is obsolete in current Xorg version?
 > 
 > No, not in 7.0 and not yet in -current.
 > The failure seems to happen before either XAA or EXA could take over.
 > 
 > The Rage II in my beige G3 ( which has no MMIO aperture ) works fine,
 > although that's -current. I have a 2MB Rage II with Sun firmware
 > somewhere, let me dig it up and see if I can reproduce the failure.
 > 
 > have fun
 > Michael
 


Home | Main Index | Thread Index | Old Index