On Sun, 23 Apr 2017, Stefan Sperling wrote: > On Sat, Apr 22, 2017 at 04:31:02PM -0600, Jeff wrote: > > Booting from sr0a seemed to do the trick to get my system upgraded to > > 6.1. Unfortunately, it's now panicing frequently with, "panic: > > psycho0: uncorrectable DMA error" but on different commands each time. > > Please follow the steps in https://www.openbsd.org/report.html > In the past we have found bugs in drivers where the hardware ends up > doing an out of bounds access during DMA transactions. On most platforms > those bugs don't get noticed but psycho on sparc64 is catching them > which results in this panic.
Due to the criticality of my system, I installed 6.1 from scratch on a spare V120. That system seems to be working great. I was going to wait a few days and rebuild the first system to try and determine if it has a hardware issue but I'll wait and submit a bug report first. > > Question: After upgrading to 6.1, it's still booting with "OpenBSD > > BOOT 1.7" but I noticed when booting from the burned install61.iso > > CD, it reports BOOT 1.9. I tried running "installboot sd2" but > > there's no change. Is there another method I'm overlooking to > > update the boot image? > > Is sd2 your softraid disk? What does installboot -n -v sd2 say? > # installboot -n -v sd2 Using / as root would install bootstrap on /dev/rsd2c using first-stage /usr/mdec/bootblk, second-stage /usr/mdec/ofwboot boot block is 5840 bytes (12 blocks @ 512 bytes = 6144 bytes) sd2: softraid volume with 2 disk(s) sd0d: installing boot blocks on /dev/rsd0c would write boot block to disk /dev/rsd0c sd1d: installing boot blocks on /dev/rsd1c would write boot block to disk /dev/rsd1c # ls -l /usr/mdec total 428 -rw-r--r-- 1 root bin 5840 Apr 1 16:21 bootblk -r--r--r-- 1 root bin 101048 Apr 1 16:21 ofwboot -r--r--r-- 1 root bin 53608 Apr 1 16:21 ofwboot.net -r--r--r-- 1 root bin 53320 Apr 1 16:21 ofwbootfd Based on the timestamps, things seem to be in order. Thanks! -Jeff
