Date: Fri, 29 Jun 2018 15:54:33 -0700 From: bob prohaska <fbsd@www.zefox.net> To: freebsd-arm@freebsd.org Subject: Re: RPI3 swap experiments Message-ID: <20180629225433.GB35717@www.zefox.net> In-Reply-To: <C6303FC5-B412-472C-98E4-9A1E45C38535@yahoo.com> References: <201806261040.w5QAeBKq035183@donotpassgo.dyslexicfish.net> <A6986B21-FF6E-48F5-9F3A-06B3D2A92C55@yahoo.com> <20180626151843.GD17293@www.zefox.net> <3525D7C7-F848-45A1-BD85-2DAC895DF48C@yahoo.com> <20180626222834.GA20270@www.zefox.net> <28012DFB-37A0-461A-BB62-CD3EE61E82F0@yahoo.com> <20180627054027.GA22144@www.zefox.net> <CC72E766-03CB-476C-8F2B-DAAC266CE63D@yahoo.com> <20180627194217.GA27793@www.zefox.net> <C6303FC5-B412-472C-98E4-9A1E45C38535@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jun 27, 2018 at 06:12:53PM -0700, Mark Millard wrote: > > It would be handy for something simpler than buildworld to be > able to induce some of the types of problems, for sure. > It appears that running root@www:/home/bob/stress2/misc # sh ./snap.sh > 5thstress2.log & triggers a stream of console errors that resemble those produced by -j4 buildworld: GEOM: md10: invalid disklabel. GEOM: ufsid/5a5a128b05c5944d: invalid disklabel. (da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 00 18 a9 80 00 00 30 00 (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error (da0:umass-sim0:0:0:0): Retrying command, 3 more tries remain (da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 00 18 a9 80 00 00 30 00 The error stream continues until powercycling, escape to debugger does not work. To some extent, the machine remains responsive in ssh sessions, at least for simple commands (ls -l, tail). The stress2 logfile is empty. The details captured are visible at http://www.zefox.net/~fbsd/rpi3/swaptests/r335655/1gbsdflash/stress2/5thtest/ One oddity is a stream of indisplayable characters, briefly, in http://www.zefox.net/~fbsd/rpi3/swaptests/r335655/1gbsdflash/stress2/5thtest/5thswapuse.log following the initial error message. Another oddity is that during a single user reboot similar errors are briefly displayed before starting the shell. After two rounds of fsck -f they seem to vanish, not to return without appropriate provocation. This does not happen on every reboot, but enough to be no-longer surprising. It looks as if this particular error message has nothing at all to do with swap. Does it seem in any way related to similar errors seen during swap-stressed buildworld sessions? Thanks for reading, bob prohaska
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180629225433.GB35717>