Re: OpenBSD boot fails on V890
"Randal T. Rioux" <[email protected]>
| Newsgroups | gmane.os.openbsd.sparc |
|---|---|
| Message-ID | <[email protected]> |
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