Re: BTLB address misaligned
Michael Shalayeff <[email protected]>
| Newsgroups | gmane.os.openbsd.hppa |
|---|---|
| Message-ID | <[email protected]> |
Making, drinking tea and reading an opus magnum from Alexander Frolkin: > Hi, re > I'm trying to get OpenBSD working on a C110. Here's what happens: > > ----- > booting lf0a:/bsd: 2396160+77824+389120 [44+112016+92030]=0x423e88 > PDC_CACHE_SETCS: 0, 0, 0, 0 (-2) > SPID bits: 0x0, error = -2 > pmap_bootstrap(0x4ee000) > vtop: 0x20000 @ 0x4ef000 > physpool: 0x137000 @ 0x2c9000 > bootstrap: mapped 0x400000 - 0x4000000 > pdc_coproc: c0, c0 > [ using 204424 bytes of bsd ELF symbol table ] > pdc0: console init > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > Copyright (c) 1995-2003 OpenBSD. All rights reserved. http://www.OpenBSD.org/ > > pmap_init() > OpenBSD 3.2-current (GENERIC) #1213: Tue Jan 14 15:02:38 EST 2003 > [email protected]:/export/hppa/root/sys/arch/hppa/compile/GENERIC > HP9000/780/C110 (Raven 120 T') PA-RISC 1.1a > real mem = 67108864 (524288 reserved for PROM, 4194304 used by OpenBSD) > avail mem = 53366784 > using 1630 buffers containing 6676480 bytes of memory > mainbus0 (root) [flex fff80000] > pdc0 at mainbus0 > "FW SCSI" at mainbus0 (type 4, sv 89) offset 3f8c000 not configured > mem0 at mainbus0 offset ffb1000: size 64MB > cpu0 at mainbus0 offset ffa0000 irq 31: Tornado L1-A 120Mhz, FPU Tornado rev 1 > cpu0: 256K(32b/l) Icache, 258K(32b/l) wr-back coherent Dcache, 120 coherent TLB, > 16 BTLB > "WAX Bus Adapter" at mainbus0 (type b, sv 8e) offset fe00000 not configured > "WAX EISA Bus Adapter" at mainbus0 (type b, sv 90) offset c000000 not configured > > lasi0 at mainbus0 offset fd00000 irq 28: rev 3.0 > gsc0 at lasi0 > "PS/2 port" at gsc0 (type a, sv 84) offset 8100 not configured > "PS/2 port" at gsc0 (type a, sv 84) offset 8000 not configured > "floppy controller" at gsc0 (type a, sv 83) offset a000 not configured > "Advanced audio (ext.)" at gsc0 (type a, sv 7b) offset 4000 not configured > lpt0 at gsc0 offset 2000 irq 7 > com0 at gsc0 offset 5000 irq 5: ns16550a, 16 byte fifo > ie0 at gsc0 offset 7000 irq 8: LASI/i82596CA v3.0, address 08:00:09:ba:d4:15 > osiop0 at gsc0 offset 6000 irq 9: NCR53C710 rev 2, 40MHz, SCSI ID 7 > scsibus0 at osiop0: 8 targets > WARNING: BTLB address misaligned pa=0xf0040, len=0x80 > panic: trap: uvm_fault(0x416f88, f0069003, 0, 1): 14 > Stopped at Debugger+0x18: break 0,5 > RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS PANIC! > DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THAT INFORMATION! > ddb> trace > Debugger(fba68,0,4a4174,1a0) at Debugger+0x18 > panic(2a41b8,416f88,f0069003,0) at panic+0xf4 > panic(29e694,f0040,80,4af94c) at panic+0xd8 > trap(0,0,f0040000,42e800) at trap+0x7ec > $trapnowvirt+0x1b8 > ddb> ps > PID PPID PGRP UID S FLAGS WAIT COMMAND > * 0 -1 0 0 2 0x80204 swapper > ddb> > ----- > > Trying NetBSD gives a similar result (DTLB miss trap, I think). The > only thing I've found in (NetBSD) mailing list archives is that I > should pull out a few SIMMs. However, that's impossible in my case > since I only have two of them installed. > > I've also tried booting Linux, with a ramdisk, which seems to work > fine. > > Let me know if you need any more details. > > What does ``BTLB address misaligned'' mean, anyway? the real issue here is a different scsi chip. we are working on it. cu -- paranoic mickey (my employers have changed but, the name has remained)