Re: Sparc64 Panic -current : Caused by PGX64 graphics card

Previous thread: Re: Looking for something similar to "screen"-command by Jon on Wednesday, September 12, 2007 - 5:12 am. (3 messages)

Next thread: VMware releases the sources of VMware tools by Martin Schröder on Wednesday, September 12, 2007 - 8:07 am. (1 message)
From: Edd Barrett
Date: Wednesday, September 12, 2007 - 6:30 am

Hi,

I bought a PGX64 graphics card hoping to have accelerated X on my sun
blade 1000. Unfortunately it cause a panic. Here's the details:

---8<---
SUNW,Sun-Blade-1000 (UltraSPARC-III) , No Keyboard
Copyright 1998-2004 Sun Microsystems, Inc.  All rights reserved.
OpenBoot 4.16.4, 1024 MB memory installed, Serial #51383914.
Ethernet address 0:3:ba:10:e:6a, Host ID: 83100e6a.

ok boot
Boot device: /pci@8,600000/SUNW,qlc@4/fp@0,0/disk@w21000004cf4c6d77,0:a
 File and args:
OpenBSD IEEE 1275 Bootblock 1.1
..>> OpenBSD BOOT 1.2
Trying bsd...
Booting /pci@8,600000/SUNW,qlc@4/fp@0,0/disk@w21000004cf4c6d77,0:a/bsd
5056160@0x1000000+184488@0x1800000+4009816@0x182d0a8
symbols @ 0xfef52240 52+305568+184378 start=0x1000000
[ using 490584 bytes of bsd ELF symbol table ]
console is /pci@8,700000/ebus@5/serial@1,400000:a
Copyright (c) 1982, 1986, 1989, 1991, 1993
        The Regents of the University of California.  All rights reserved.
Copyright (c) 1995-2007 OpenBSD. All rights reserved.  http://www.OpenBSD.org

OpenBSD 4.2-current (GENERIC) #0: Tue Sep 11 14:16:19 BST 2007
    root@warbastard.bournemouth.ac.uk:/usr/src/sys/arch/sparc64/compile/GENERIC
real mem = 1073741824 (1024MB)
avail mem = 1027866624 (980MB)
mainbus0 at root: SUNW,Sun-Blade-1000 (UltraSPARC-III)
cpu0 at mainbus0: SUNW,UltraSPARC-III (rev 5.14) @ 900 MHz
cpu0: physical 32K instruction (32 b/l), 64K data (32 b/l), 8192K
external (512 b/l)
"memory-controller" at mainbus0 not configured
schizo0 at mainbus0: "Schizo", version 4, ign 200, bus B 0 to 0
schizo0: dvma map c0000000-ffffffff, iotdb 1bec000-1cec000
pci0 at schizo0
ebus0 at pci0 dev 5 function 0 "Sun RIO EBus" rev 0x01
"flashprom" at ebus0 addr 0-1fffff not configured
pcfiic0 at ebus0 addr 2e-2f, 2d-2d ipl 35
iic0 at pcfiic0
bbc0 at ebus0 addr 0-fffff
ppm0 at ebus0 addr e-28, 728000-728003, 30002e-30002f, 300600-300607
pcfiic1 at ebus0 addr 30-31 ipl 35
iic1 at pcfiic1
admtemp0 at iic1 addr 0x18: max1617
"tda8444" at iic1 addr 0x24 not ...
From: Miod Vallat
Date: Wednesday, September 12, 2007 - 6:41 am

Does it panic if you use the glass console instead of the serial console?

Miod

From: Edd Barrett
Date: Wednesday, September 12, 2007 - 6:45 am

Afraid so.

I only put the serial line in so I could copy and paste it into the email.


-- 
Best Regards

Edd

---------------------------------------------------
http://students.dec.bournemouth.ac.uk/ebarrett

From: Miod Vallat
Date: Wednesday, September 12, 2007 - 6:54 am

Ok.

Can you, at the "ok" prompt, go to your frame buffer device node
(cd schizo@whatever, cd pci@whatever, etc) and give me the output
of ".properties" (or ".attributes" if the former does not work)?

Miod

From: Edd Barrett
Date: Wednesday, September 12, 2007 - 7:29 am

Hi,



I think this is the device:
/pci@8,600000/SUNW,m64B@1

assigned-addresses       82000810 00000000 01000000 00000000 01000000
                         81000814 00000000 00000400 00000000 00000100
                         82000818 00000000 00102000 00000000 00002000
                         82000830 00000000 00140000 00000000 00020000
aty,fcode                1.69
aty,card#                109-XXXXX-XX
aty,rom#                 113-XXXXX-100
aty,model                ATY,RageXL
model                    SUNW,370-4362
name                     SUNW,m64B
pgx_version              @(#) pgx64.fth 1.12 01/05/04
reg                      00000800 00000000 00000000 00000000 00000000
                         02000810 00000000 00000000 00000000 01000000
                         02000818 00000000 00000000 00000000 00001000
                         02000830 00000000 00000000 00000000 00020000
character-set            ISO8859-1
device_type              display
linebytes                00000480
v-freq                   00000042
depth                    00000008
height                   00000384
width                    00000480
fb-memory                00000008
aty,flags                00000000
aty,status               00000004
fcode-rom-offset         00000000
fast-back-to-back
devsel-speed             00000001
class-code               00030000
interrupts               00000001
latency-timer            00000040
cache-line-size          00000010
max-latency              00000000
min-grant                00000008
revision-id              00000027
device-id                00004752
vendor-id                00001002

Does this help?

-- 
Best Regards

Edd

---------------------------------------------------
http://students.dec.bournemouth.ac.uk/ebarrett

From: Miod Vallat
Date: Wednesday, September 12, 2007 - 7:43 am

Yes and no; I was wondering if the memory regions were, for some reason,
not consistent with the reported geometry, but everything looks correct.

This (conveniently) looks like a schizo issue to me at the moment.

Miod

From: Edd Barrett
Date: Wednesday, September 12, 2007 - 7:47 am

Ok well, I have access to this box during working hours, so if you
would like any other information, don't hesitate to drop me mail.

Keep me posted!

Cheers

-- 
Best Regards

Edd

---------------------------------------------------
http://students.dec.bournemouth.ac.uk/ebarrett

Previous thread: Re: Looking for something similar to "screen"-command by Jon on Wednesday, September 12, 2007 - 5:12 am. (3 messages)

Next thread: VMware releases the sources of VMware tools by Martin Schröder on Wednesday, September 12, 2007 - 8:07 am. (1 message)