Re: OpenBSD boot fails on V890

Aaron Scheiner <[email protected]>
Newsgroups gmane.os.openbsd.sparc
Message-ID <[email protected]>
Hey Randal

Yes, Solaris 10 runs quite happily on this machine. The problem is, not
much runs on Solaris :P .

Bwahahahaa @ company toy... no I bought it for myself. I bought two 
off an auction sale. The item was described in the newspaper as an
"electronic filing cabinet" and as a result no one was interested 
in it, except me. I paid R 1000 per machine... about 133 USD . The
machines were originally the property of the Fidentia Group... the 
owner or manager of that company stole millions from trust 
funds belonging to orphans and widows :( .

A friend of mine is an electrical engineer and when I told him about
it he begged me to sell him the second machine, so now we both have 
our own.

It's been quite a learning curve for me. I have no prior experience 
with Sun machines... even building a serial cable to interact with 
it was a nightmare. Sun's manual says it's a null modem cable
(crossover) but in actual fact it's a straight serial cable.

Someone associated with Debian's sparc list asked if I had added
anything non-standard to the machine, I have, it's an S3 Trio 64 
PCI graphics card, which the machine doesn't recognise. I have 
ordered a framebuffer card from Sun's agents here, which costs 
more than three times what I paid for the machine.

Lastly, this machine is very good at rendering fractals... but 
I'm hoping to use it for HD video transcoding.

:)

Aaron

On Mon, 2009-11-23 at 02:00 -0500, Randal T. Rioux wrote:
> On Sun, November 22, 2009 2:56 pm, Aaron Sheiner wrote:
> <snip>
> > schizo1 at mainbus0: "Schizo", version 7, ign 200, bus A 0 to 0
> > schizo1: dvma map c0000000-ffffffff
> > schizo1: pci bus A error
> > PCIAFSR=320000000<MEM>
> > PCIAFAR=4000c0
> > PCICTRL=60002010a003f<SPD,MMU_INT,EEN>
> > PCICSR=2a00146<MEM,MASTER,PARITY,SERR,CLK66,BACK2BACK_STAT,DEVSEL_MEDIUM>
> > panic: schizo1: fatal
> > kdb breakpoint at 1419c40
> > Stopped at      Debugger+0x4:   nop
> > schizo_pci_error(4001dacb800, d, e0017ec8, 2, 13e1460, 1c097e8) at
> > schizo_pci_e
> > rror+0x1b8
> > sparc_interrupt(4001d8de7a0, 0, fffffffffffffff8, 0, 4001d8de700,
> > 1c098e8) at s
> > parc_interrupt+0x2a8
> > malloc(4001d8de700, 182db20, 5, d, 14ca0f0, 8) at malloc+0x51c
> > bus_intr_allocate(15842a8, 13e1420, 4001dd1cd00, 230, f, 4ccfb729180) at
> > bus_in
> > tr_allocate+0x10
> > schizo_set_intr(4001dac8e00, 2, f, 13e1420, 4001dd1cd00, 230) at
> > schizo_set_int
> > r+0xbc
> > schizo_init(4001dd1cd00, 1, 1c09be0, 14, 14ca0f0, 5) at schizo_init
> > +0x46c
> > config_attach(1808210, 4001dd1cd00, 1c09be0, 1407580, 1c09c00, 5) at
> > config_att
> > ach+0x12c
> > mainbus_match(0, 4001dac7f80, 0, 80, 18b5900, 40) at mainbus_match+0x718
> > config_attach(1808210, 4001dac7f80, 0, 0, 14ca0f0, 5) at config_attach
> > +0x12c
> > cpu_configure(11684c0, 1801000, 0, ffffffffffffe000, 1, 1) at
> > cpu_configure+0x7
> > 8
> > RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS
> > PANIC!
> > IF RUNNING SMP, USE 'mach ddbcpu <#>' AND 'trace' ON OTHER PROCESSORS,
> > TOO.
> > DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THAT INFORMATION!
> > ddb{0}> trace
> > schizo_pci_error(4001dacb800, d, e0017ec8, 2, 13e1460, 1c097e8) at
> > schizo_pci_e
> > rror+0x1b8
> > sparc_interrupt(4001d8de7a0, 0, fffffffffffffff8, 0, 4001d8de700,
> > 1c098e8) at s
> > parc_interrupt+0x2a8
> > malloc(4001d8de700, 182db20, 5, d, 14ca0f0, 8) at malloc+0x51c
> > bus_intr_allocate(15842a8, 13e1420, 4001dd1cd00, 230, f, 4ccfb729180) at
> > bus_in
> > tr_allocate+0x10
> > schizo_set_intr(4001dac8e00, 2, f, 13e1420, 4001dd1cd00, 230) at
> > schizo_set_int
> > r+0xbc
> > schizo_init(4001dd1cd00, 1, 1c09be0, 14, 14ca0f0, 5) at schizo_init
> > +0x46c
> > config_attach(1808210, 4001dd1cd00, 1c09be0, 1407580, 1c09c00, 5) at
> > config_att
> > ach+0x12c
> > mainbus_match(0, 4001dac7f80, 0, 80, 18b5900, 40) at mainbus_match+0x718
> > config_attach(1808210, 4001dac7f80, 0, 0, 14ca0f0, 5) at config_attach
> > +0x12c
> > cpu_configure(11684c0, 1801000, 0, ffffffffffffe000, 1, 1) at
> > cpu_configure+0x7
> > 8
> > main(0, 114b2a0, 18, f006bcfc, f006bcfc, 1801010) at main+0x490
> > print_dtlb(100000, 1208, 1000000, fff59a30, 18, 47) at print_dtlb+0x158
> > ddb{0}> ps
> >    PID   PPID   PGRP    UID  S       FLAGS  WAIT          COMMAND
> > *    0     -1      0      0  7     0x80200                swapper
> > ddb{0}>
> 
> I had this happen on a smaller machine before, and it turned out to be a
> bad ASIC chip on the mainboard. I hope that isn't the case with your
> elephant.
> 
> Does Solaris run error-less on it?
> 
> On a side note, did you buy this behemoth yourself or is it a company toy?
> That is one fun Sun :-)
> 
> Randy
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.