Re: OpenBSD/sparc64 6.7-beta not working on silver Blade 2500
On Thu, Apr 09, 2020 at 12:24:17PM +0200, Otto Moerbeek wrote: > On Wed, Apr 08, 2020 at 07:03:29PM +0200, Sigi Rudzio wrote: > > > Am Mi., 8. Apr. 2020 um 08:37 Uhr schrieb Otto Moerbeek : > > > > > > On Wed, Apr 08, 2020 at 01:11:29AM +0200, Sigi Rudzio wrote: > > > > > > > Hello misc@, > > > > > > > > while testing the FFS2 patches by otto@ I noticed that I was unable > > > > to install -current on my silver Blade 2500. > > > > > > > > tar fails while unpacking the sets, although the files are ok, if I > > > > rename > > > > base67.tgz to base66.tgz to fool the 6.6 installer I can install > > > > 6.7-beta, > > > > although it fails/panics with a lot of "Illegal instruction" errors on > > > > the > > > > first boot. > > > > > > > > otto@ already told me that this might be fallout from the recent clang > > > > changes. > > > > > > Well, I sais it *could be*, but you did not show my the actual errors > > > in that email. The errorsbelow indicate a harware issue, i.e. bad > > > disk. > > > > > > -Otto > > > > Sorry, I should have been clearer. > > > > I tried another disk from my working V240 and got the same errors. > > > > Installing on an IDE hard disk works and the system is working fine, > > even writing large files to the SCSI disk is fine, but I can make it panic > > with tar. > > So I guess this is some kind of SCSI bus hardware issue that 6.6 doesn't > > trigger and some change between 6.6 and 6.7-beta does trigger it. > > > > Sorry for the noise and thanks for the help! > > Hmm, you might be onto something. I have seen similar issues on a > Blade 150 but blamed it on hardware. Sadly I do not thave easy access > to the machine atm. In the meantime krw@ committed (with your help) a fix for a DMA issue on mpi(4) that seems to make my Blade150 much more reliable. Thanks to both of you! -Otto
Re: OpenBSD/sparc64 6.7-beta not working on silver Blade 2500
Am Do., 9. Apr. 2020 um 12:24 Uhr schrieb Otto Moerbeek : > > On Wed, Apr 08, 2020 at 07:03:29PM +0200, Sigi Rudzio wrote: > > > Am Mi., 8. Apr. 2020 um 08:37 Uhr schrieb Otto Moerbeek : > > > > > > On Wed, Apr 08, 2020 at 01:11:29AM +0200, Sigi Rudzio wrote: > > > > > > > Hello misc@, > > > > > > > > while testing the FFS2 patches by otto@ I noticed that I was unable > > > > to install -current on my silver Blade 2500. > > > > > > > > tar fails while unpacking the sets, although the files are ok, if I > > > > rename > > > > base67.tgz to base66.tgz to fool the 6.6 installer I can install > > > > 6.7-beta, > > > > although it fails/panics with a lot of "Illegal instruction" errors on > > > > the > > > > first boot. > > > > > > > > otto@ already told me that this might be fallout from the recent clang > > > > changes. > > > > > > Well, I sais it *could be*, but you did not show my the actual errors > > > in that email. The errorsbelow indicate a harware issue, i.e. bad > > > disk. > > > > > > -Otto > > > > Sorry, I should have been clearer. > > > > I tried another disk from my working V240 and got the same errors. > > > > Installing on an IDE hard disk works and the system is working fine, > > even writing large files to the SCSI disk is fine, but I can make it panic > > with tar. > > So I guess this is some kind of SCSI bus hardware issue that 6.6 doesn't > > trigger and some change between 6.6 and 6.7-beta does trigger it. > > > > Sorry for the noise and thanks for the help! > > Hmm, you might be onto something. I have seen similar issues on a > Blade 150 but blamed it on hardware. Sadly I do not thave easy access > to the machine atm. > > -Otto > I think I did indeed find a bug! If I manually revert this change (only this change): http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/dev/ic/mpi.c.diff?r1=1.206=1.207=h and compile a -current kernel with the change, I can write to the disk no problem at all (my test was while true; do tar -xzpvf base67.tgz; done) a current kernel (or any kernel after Nov. 15) crashes almost immediately, my kernel with the mpi.c change reverted never crashes. Maybe it is a hardware defect and the change only exposes it, I still hope this helps. Should I compile a complete release with bsd.rd and try an installation? Regards, S. Rudzio > > > > Regards > > > > S. Rudzio > > > > > > > > > > > > > 6.6 works fine. > > > > > > > > The failures are a bit random, it doesn't panic every time, sometimes > > > > while installing 6.7-beta tar fails and I get to try again a few times > > > > before > > > > I give up/it panics. > > > > > > > > I hope this information helps. > > > > > > > > Regards, > > > > > > > > S. Rudzio > > > > > > > > output from > > > > -6.7-beta bsd.rd failing > > > > -6.6 bsd.rd > > > > -6.6 bsd.mp > > > > -6.7-beta bsd.mp failing/panicing (installed with 6.6 bsd.rd) > > > > following: > > > > > > > > latest bsd.rd (the previous two snapshots also failed, but I didn't > > > > save any > > > > logs): > > > > Booting /pci@1c,60/network@3/bsd.rd > > > > 4671584@0x100+6048@0x1474860+3248464@0x1c0+945840@0x1f19150 > > > > symbols @ 0xfec68440 175+356136+219433 start=0x100 > > > > console is /pci@1e,60/isa@7/serial@0,3f8 > > > > Copyright (c) 1982, 1986, 1989, 1991, 1993 > > > > The Regents of the University of California. All rights > > > > reserved. > > > > Copyright (c) 1995-2020 OpenBSD. All rights reserved. > > > > https://www.OpenBSD.org > > > > > > > > OpenBSD 6.7-beta (RAMDISK) #259: Mon Apr 6 19:13:12 MDT 2020 > > > > > > > > dera...@sparc64.openbsd.org:/usr/src/sys/arch/sparc64/compile/RAMDISK > > > > real mem = 2147483648 (2048MB) > > > > avail mem = 2098044928 (2000MB) > > > > mainbus0 at root: Sun Blade 2500 (Silver) > > > > "SUNW,UltraSPARC-IIIi" at mainbus0 not configured > > > > cpu0 at mainbus0: SUNW,UltraSPARC-IIIi (rev 3.4) @ 1600 MHz > > > > cpu0: physical 32K instruction (32 b/l), 64K data (32 b/l), 1024K > > > > external (64 b/l) > > > > "memory-controller" at mainbus0 not configured > > > > "memory-controller" at mainbus0 not configured > > > > schizo0 at mainbus0: "Tomatillo", version 4, ign 700, bus A 0 to 0 > > > > schizo0: dvma map c000-dfff > > > > pci0 at schizo0 > > > > bge0 at pci0 dev 3 function 0 "Broadcom BCM5703" rev 0x00, > > > > BCM5702/5703 A2 (0x1002)bge0: nvram lock timed out > > > > : ivec 0x71c, address 00:03:ba:f2:ee:53 > > > > brgphy0 at bge0 phy 1: BCM5703 10/100/1000baseT PHY, rev. 2 > > > > "ppm" at mainbus0 not configured > > > > schizo1 at mainbus0: "Tomatillo", version 4, ign 740, bus B 0 to 0 > > > > schizo1: dvma map c000-dfff > > > > pci1 at schizo1 > > > > mpi0 at pci1 dev 4 function 0 "Symbios Logic 53c1030" rev 0x07: ivec > > > > 0x769 > > > > mpi0: 0, firmware 1.3.11.1 > > > > scsibus0 at mpi0: 16 targets, initiator 7 > > > > sd0 at scsibus0 targ 0 lun 0: > > > > serial.SEAGATE_ST314670LSUN146G4442RJNV_3KS2RJNV > > > > sd0: 140009MB,
Re: OpenBSD/sparc64 6.7-beta not working on silver Blade 2500
On Wed, Apr 08, 2020 at 07:03:29PM +0200, Sigi Rudzio wrote: > Am Mi., 8. Apr. 2020 um 08:37 Uhr schrieb Otto Moerbeek : > > > > On Wed, Apr 08, 2020 at 01:11:29AM +0200, Sigi Rudzio wrote: > > > > > Hello misc@, > > > > > > while testing the FFS2 patches by otto@ I noticed that I was unable > > > to install -current on my silver Blade 2500. > > > > > > tar fails while unpacking the sets, although the files are ok, if I rename > > > base67.tgz to base66.tgz to fool the 6.6 installer I can install 6.7-beta, > > > although it fails/panics with a lot of "Illegal instruction" errors on the > > > first boot. > > > > > > otto@ already told me that this might be fallout from the recent clang > > > changes. > > > > Well, I sais it *could be*, but you did not show my the actual errors > > in that email. The errorsbelow indicate a harware issue, i.e. bad > > disk. > > > > -Otto > > Sorry, I should have been clearer. > > I tried another disk from my working V240 and got the same errors. > > Installing on an IDE hard disk works and the system is working fine, > even writing large files to the SCSI disk is fine, but I can make it panic > with tar. > So I guess this is some kind of SCSI bus hardware issue that 6.6 doesn't > trigger and some change between 6.6 and 6.7-beta does trigger it. > > Sorry for the noise and thanks for the help! Hmm, you might be onto something. I have seen similar issues on a Blade 150 but blamed it on hardware. Sadly I do not thave easy access to the machine atm. -Otto > > Regards > > S. Rudzio > > > > > > > > > 6.6 works fine. > > > > > > The failures are a bit random, it doesn't panic every time, sometimes > > > while installing 6.7-beta tar fails and I get to try again a few times > > > before > > > I give up/it panics. > > > > > > I hope this information helps. > > > > > > Regards, > > > > > > S. Rudzio > > > > > > output from > > > -6.7-beta bsd.rd failing > > > -6.6 bsd.rd > > > -6.6 bsd.mp > > > -6.7-beta bsd.mp failing/panicing (installed with 6.6 bsd.rd) > > > following: > > > > > > latest bsd.rd (the previous two snapshots also failed, but I didn't save > > > any > > > logs): > > > Booting /pci@1c,60/network@3/bsd.rd > > > 4671584@0x100+6048@0x1474860+3248464@0x1c0+945840@0x1f19150 > > > symbols @ 0xfec68440 175+356136+219433 start=0x100 > > > console is /pci@1e,60/isa@7/serial@0,3f8 > > > Copyright (c) 1982, 1986, 1989, 1991, 1993 > > > The Regents of the University of California. All rights > > > reserved. > > > Copyright (c) 1995-2020 OpenBSD. All rights reserved. > > > https://www.OpenBSD.org > > > > > > OpenBSD 6.7-beta (RAMDISK) #259: Mon Apr 6 19:13:12 MDT 2020 > > > dera...@sparc64.openbsd.org:/usr/src/sys/arch/sparc64/compile/RAMDISK > > > real mem = 2147483648 (2048MB) > > > avail mem = 2098044928 (2000MB) > > > mainbus0 at root: Sun Blade 2500 (Silver) > > > "SUNW,UltraSPARC-IIIi" at mainbus0 not configured > > > cpu0 at mainbus0: SUNW,UltraSPARC-IIIi (rev 3.4) @ 1600 MHz > > > cpu0: physical 32K instruction (32 b/l), 64K data (32 b/l), 1024K > > > external (64 b/l) > > > "memory-controller" at mainbus0 not configured > > > "memory-controller" at mainbus0 not configured > > > schizo0 at mainbus0: "Tomatillo", version 4, ign 700, bus A 0 to 0 > > > schizo0: dvma map c000-dfff > > > pci0 at schizo0 > > > bge0 at pci0 dev 3 function 0 "Broadcom BCM5703" rev 0x00, > > > BCM5702/5703 A2 (0x1002)bge0: nvram lock timed out > > > : ivec 0x71c, address 00:03:ba:f2:ee:53 > > > brgphy0 at bge0 phy 1: BCM5703 10/100/1000baseT PHY, rev. 2 > > > "ppm" at mainbus0 not configured > > > schizo1 at mainbus0: "Tomatillo", version 4, ign 740, bus B 0 to 0 > > > schizo1: dvma map c000-dfff > > > pci1 at schizo1 > > > mpi0 at pci1 dev 4 function 0 "Symbios Logic 53c1030" rev 0x07: ivec > > > 0x769 > > > mpi0: 0, firmware 1.3.11.1 > > > scsibus0 at mpi0: 16 targets, initiator 7 > > > sd0 at scsibus0 targ 0 lun 0: > > > serial.SEAGATE_ST314670LSUN146G4442RJNV_3KS2RJNV > > > sd0: 140009MB, 512 bytes/sector, 286739329 sectors > > > mpi0: target 0 Sync at 160MHz width 16bit offset 63 QAS 1 DT 1 IU 1 > > > mpi1 at pci1 dev 4 function 1 "Symbios Logic 53c1030" rev 0x07: ivec > > > 0x768 > > > mpi1: 0, firmware 1.3.11.1 > > > scsibus1 at mpi1: 16 targets, initiator 7 > > > schizo2 at mainbus0: "Tomatillo", version 4, ign 780, bus A 0 to 1 > > > schizo2: dvma map c000-dfff > > > pci2 at schizo2 > > > ebus0 at pci2 dev 7 function 0 "Acer Labs M1533 ISA" rev 0x00 > > > "flashprom" at ebus0 addr 0-f not configured > > > rtc0 at ebus0 addr 70-71: m5823 > > > "i2c" at ebus0 addr 320-321 ivec 0x2e not configured > > > "power" at ebus0 addr 800-82f ivec 0x20 not configured > > > com0 at ebus0 addr 3f8-3ff ivec 0x2c: ns16550a, 16 byte fifo > > > com0: console > > > com1 at ebus0 addr 2e8-2ef ivec 0x2c: ns16550a, 16 byte fifo > > > "dma" at ebus0 addr 0- not configured > > > "Acer Labs M7101 Power" rev 0x00 at pci2
Re: OpenBSD/sparc64 6.7-beta not working on silver Blade 2500
Am Mi., 8. Apr. 2020 um 08:37 Uhr schrieb Otto Moerbeek : > > On Wed, Apr 08, 2020 at 01:11:29AM +0200, Sigi Rudzio wrote: > > > Hello misc@, > > > > while testing the FFS2 patches by otto@ I noticed that I was unable > > to install -current on my silver Blade 2500. > > > > tar fails while unpacking the sets, although the files are ok, if I rename > > base67.tgz to base66.tgz to fool the 6.6 installer I can install 6.7-beta, > > although it fails/panics with a lot of "Illegal instruction" errors on the > > first boot. > > > > otto@ already told me that this might be fallout from the recent clang > > changes. > > Well, I sais it *could be*, but you did not show my the actual errors > in that email. The errorsbelow indicate a harware issue, i.e. bad > disk. > > -Otto Sorry, I should have been clearer. I tried another disk from my working V240 and got the same errors. Installing on an IDE hard disk works and the system is working fine, even writing large files to the SCSI disk is fine, but I can make it panic with tar. So I guess this is some kind of SCSI bus hardware issue that 6.6 doesn't trigger and some change between 6.6 and 6.7-beta does trigger it. Sorry for the noise and thanks for the help! Regards S. Rudzio > > > > > 6.6 works fine. > > > > The failures are a bit random, it doesn't panic every time, sometimes > > while installing 6.7-beta tar fails and I get to try again a few times > > before > > I give up/it panics. > > > > I hope this information helps. > > > > Regards, > > > > S. Rudzio > > > > output from > > -6.7-beta bsd.rd failing > > -6.6 bsd.rd > > -6.6 bsd.mp > > -6.7-beta bsd.mp failing/panicing (installed with 6.6 bsd.rd) > > following: > > > > latest bsd.rd (the previous two snapshots also failed, but I didn't save any > > logs): > > Booting /pci@1c,60/network@3/bsd.rd > > 4671584@0x100+6048@0x1474860+3248464@0x1c0+945840@0x1f19150 > > symbols @ 0xfec68440 175+356136+219433 start=0x100 > > console is /pci@1e,60/isa@7/serial@0,3f8 > > Copyright (c) 1982, 1986, 1989, 1991, 1993 > > The Regents of the University of California. All rights > > reserved. > > Copyright (c) 1995-2020 OpenBSD. All rights reserved. > > https://www.OpenBSD.org > > > > OpenBSD 6.7-beta (RAMDISK) #259: Mon Apr 6 19:13:12 MDT 2020 > > dera...@sparc64.openbsd.org:/usr/src/sys/arch/sparc64/compile/RAMDISK > > real mem = 2147483648 (2048MB) > > avail mem = 2098044928 (2000MB) > > mainbus0 at root: Sun Blade 2500 (Silver) > > "SUNW,UltraSPARC-IIIi" at mainbus0 not configured > > cpu0 at mainbus0: SUNW,UltraSPARC-IIIi (rev 3.4) @ 1600 MHz > > cpu0: physical 32K instruction (32 b/l), 64K data (32 b/l), 1024K > > external (64 b/l) > > "memory-controller" at mainbus0 not configured > > "memory-controller" at mainbus0 not configured > > schizo0 at mainbus0: "Tomatillo", version 4, ign 700, bus A 0 to 0 > > schizo0: dvma map c000-dfff > > pci0 at schizo0 > > bge0 at pci0 dev 3 function 0 "Broadcom BCM5703" rev 0x00, > > BCM5702/5703 A2 (0x1002)bge0: nvram lock timed out > > : ivec 0x71c, address 00:03:ba:f2:ee:53 > > brgphy0 at bge0 phy 1: BCM5703 10/100/1000baseT PHY, rev. 2 > > "ppm" at mainbus0 not configured > > schizo1 at mainbus0: "Tomatillo", version 4, ign 740, bus B 0 to 0 > > schizo1: dvma map c000-dfff > > pci1 at schizo1 > > mpi0 at pci1 dev 4 function 0 "Symbios Logic 53c1030" rev 0x07: ivec > > 0x769 > > mpi0: 0, firmware 1.3.11.1 > > scsibus0 at mpi0: 16 targets, initiator 7 > > sd0 at scsibus0 targ 0 lun 0: > > serial.SEAGATE_ST314670LSUN146G4442RJNV_3KS2RJNV > > sd0: 140009MB, 512 bytes/sector, 286739329 sectors > > mpi0: target 0 Sync at 160MHz width 16bit offset 63 QAS 1 DT 1 IU 1 > > mpi1 at pci1 dev 4 function 1 "Symbios Logic 53c1030" rev 0x07: ivec > > 0x768 > > mpi1: 0, firmware 1.3.11.1 > > scsibus1 at mpi1: 16 targets, initiator 7 > > schizo2 at mainbus0: "Tomatillo", version 4, ign 780, bus A 0 to 1 > > schizo2: dvma map c000-dfff > > pci2 at schizo2 > > ebus0 at pci2 dev 7 function 0 "Acer Labs M1533 ISA" rev 0x00 > > "flashprom" at ebus0 addr 0-f not configured > > rtc0 at ebus0 addr 70-71: m5823 > > "i2c" at ebus0 addr 320-321 ivec 0x2e not configured > > "power" at ebus0 addr 800-82f ivec 0x20 not configured > > com0 at ebus0 addr 3f8-3ff ivec 0x2c: ns16550a, 16 byte fifo > > com0: console > > com1 at ebus0 addr 2e8-2ef ivec 0x2c: ns16550a, 16 byte fifo > > "dma" at ebus0 addr 0- not configured > > "Acer Labs M7101 Power" rev 0x00 at pci2 dev 6 function 0 not > > configured > > "Acer Labs M5451 Audio" rev 0x02 at pci2 dev 8 function 0 not > > configured > > ohci0 at pci2 dev 10 function 0 "Acer Labs M5237 USB" rev 0x03: ivec > > 0x7a7, version 1.0, legacy support > > ohci1 at pci2 dev 11 function 0 "Acer Labs M5237 USB" rev 0x03: ivec > > 0x7a6, version 1.0, legacy support > > pciide0 at pci2 dev 13 function 0 "Acer Labs M5229 UDMA IDE" rev 0xc4: > > DMA, channel 0 configured to native-PCI, channel 1 configured
Re: OpenBSD/sparc64 6.7-beta not working on silver Blade 2500
On Wed, Apr 08, 2020 at 01:11:29AM +0200, Sigi Rudzio wrote: > Hello misc@, > > while testing the FFS2 patches by otto@ I noticed that I was unable > to install -current on my silver Blade 2500. > > tar fails while unpacking the sets, although the files are ok, if I rename > base67.tgz to base66.tgz to fool the 6.6 installer I can install 6.7-beta, > although it fails/panics with a lot of "Illegal instruction" errors on the > first boot. > > otto@ already told me that this might be fallout from the recent clang > changes. Well, I sais it *could be*, but you did not show my the actual errors in that email. The errorsbelow indicate a harware issue, i.e. bad disk. -Otto > > 6.6 works fine. > > The failures are a bit random, it doesn't panic every time, sometimes > while installing 6.7-beta tar fails and I get to try again a few times before > I give up/it panics. > > I hope this information helps. > > Regards, > > S. Rudzio > > output from > -6.7-beta bsd.rd failing > -6.6 bsd.rd > -6.6 bsd.mp > -6.7-beta bsd.mp failing/panicing (installed with 6.6 bsd.rd) > following: > > latest bsd.rd (the previous two snapshots also failed, but I didn't save any > logs): > Booting /pci@1c,60/network@3/bsd.rd > 4671584@0x100+6048@0x1474860+3248464@0x1c0+945840@0x1f19150 > symbols @ 0xfec68440 175+356136+219433 start=0x100 > console is /pci@1e,60/isa@7/serial@0,3f8 > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights > reserved. > Copyright (c) 1995-2020 OpenBSD. All rights reserved. > https://www.OpenBSD.org > > OpenBSD 6.7-beta (RAMDISK) #259: Mon Apr 6 19:13:12 MDT 2020 > dera...@sparc64.openbsd.org:/usr/src/sys/arch/sparc64/compile/RAMDISK > real mem = 2147483648 (2048MB) > avail mem = 2098044928 (2000MB) > mainbus0 at root: Sun Blade 2500 (Silver) > "SUNW,UltraSPARC-IIIi" at mainbus0 not configured > cpu0 at mainbus0: SUNW,UltraSPARC-IIIi (rev 3.4) @ 1600 MHz > cpu0: physical 32K instruction (32 b/l), 64K data (32 b/l), 1024K > external (64 b/l) > "memory-controller" at mainbus0 not configured > "memory-controller" at mainbus0 not configured > schizo0 at mainbus0: "Tomatillo", version 4, ign 700, bus A 0 to 0 > schizo0: dvma map c000-dfff > pci0 at schizo0 > bge0 at pci0 dev 3 function 0 "Broadcom BCM5703" rev 0x00, > BCM5702/5703 A2 (0x1002)bge0: nvram lock timed out > : ivec 0x71c, address 00:03:ba:f2:ee:53 > brgphy0 at bge0 phy 1: BCM5703 10/100/1000baseT PHY, rev. 2 > "ppm" at mainbus0 not configured > schizo1 at mainbus0: "Tomatillo", version 4, ign 740, bus B 0 to 0 > schizo1: dvma map c000-dfff > pci1 at schizo1 > mpi0 at pci1 dev 4 function 0 "Symbios Logic 53c1030" rev 0x07: ivec > 0x769 > mpi0: 0, firmware 1.3.11.1 > scsibus0 at mpi0: 16 targets, initiator 7 > sd0 at scsibus0 targ 0 lun 0: > serial.SEAGATE_ST314670LSUN146G4442RJNV_3KS2RJNV > sd0: 140009MB, 512 bytes/sector, 286739329 sectors > mpi0: target 0 Sync at 160MHz width 16bit offset 63 QAS 1 DT 1 IU 1 > mpi1 at pci1 dev 4 function 1 "Symbios Logic 53c1030" rev 0x07: ivec > 0x768 > mpi1: 0, firmware 1.3.11.1 > scsibus1 at mpi1: 16 targets, initiator 7 > schizo2 at mainbus0: "Tomatillo", version 4, ign 780, bus A 0 to 1 > schizo2: dvma map c000-dfff > pci2 at schizo2 > ebus0 at pci2 dev 7 function 0 "Acer Labs M1533 ISA" rev 0x00 > "flashprom" at ebus0 addr 0-f not configured > rtc0 at ebus0 addr 70-71: m5823 > "i2c" at ebus0 addr 320-321 ivec 0x2e not configured > "power" at ebus0 addr 800-82f ivec 0x20 not configured > com0 at ebus0 addr 3f8-3ff ivec 0x2c: ns16550a, 16 byte fifo > com0: console > com1 at ebus0 addr 2e8-2ef ivec 0x2c: ns16550a, 16 byte fifo > "dma" at ebus0 addr 0- not configured > "Acer Labs M7101 Power" rev 0x00 at pci2 dev 6 function 0 not > configured > "Acer Labs M5451 Audio" rev 0x02 at pci2 dev 8 function 0 not > configured > ohci0 at pci2 dev 10 function 0 "Acer Labs M5237 USB" rev 0x03: ivec > 0x7a7, version 1.0, legacy support > ohci1 at pci2 dev 11 function 0 "Acer Labs M5237 USB" rev 0x03: ivec > 0x7a6, version 1.0, legacy support > pciide0 at pci2 dev 13 function 0 "Acer Labs M5229 UDMA IDE" rev 0xc4: > DMA, channel 0 configured to native-PCI, channel 1 configured to > native-PCI > pciide0: using ivec 0x798 for native-PCI interrupt > pciide0: channel 0 disabled (no drives) > atapiscsi0 at pciide0 channel 1 drive 0 > scsibus2 at atapiscsi0: 2 targets > cd0 at scsibus2 targ 0 lun 0: > removable > cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2 > radeonfb0 at pci2 dev 2 function 0 "ATI Radeon VE" rev 0x00 > radeonfb0: SUNW,375-3181, 1152x900 > wsdisplay0 at radeonfb0 > wsdisplay0: screen 0 added (std, sun emulation) > ppb0 at pci2 dev 4 function 0 "TI PCI2250" rev 0x02 > pci3 at ppb0 bus 1 > ohci2 at pci3 dev 8 function 0 "NEC USB" rev 0x43: ivec 0x794, version > 1.0 > ohci3 at pci3 dev 8 function 1 "NEC USB" rev 0x43: ivec 0x795, version > 1.0 > ehci0 at pci3 dev 8 function 2
Re: OpenBSD/sparc64 6.7-beta not working on silver Blade 2500
On Tue, Apr 07, 2020 at 06:25:30PM -0600, Theo de Raadt wrote: > Well, that definately looks like the filesystem blowing up. my bet would be a hardware issue. -Otto > > Installing bsd.rd 100% |**| 8560 KB00:00 > Installing base67.tgz66% |* | 113 MB > 00:17 ETAftp: Reading from file: Input/output error > gzip: stdin: Input/output error > tar: End of archive volume 1 reached > /mnt/usr: bad dir ino 622362 at offset 0: mangled entry > panic: bad dir > syncing disks...95 95 54 done >
Re: OpenBSD/sparc64 6.7-beta not working on silver Blade 2500
Well, that definately looks like the filesystem blowing up. Installing bsd.rd 100% |**| 8560 KB00:00 Installing base67.tgz66% |* | 113 MB 00:17 ETAftp: Reading from file: Input/output error gzip: stdin: Input/output error tar: End of archive volume 1 reached /mnt/usr: bad dir ino 622362 at offset 0: mangled entry panic: bad dir syncing disks...95 95 54 done
