Date: Wed, 25 Apr 2012 09:20:13 GMT From: Kristof Provost <kristof@sigsegv.be> To: freebsd-arm@FreeBSD.org Subject: Re: arm/158950: arm/sheevaplug fails fsx when mmap operations are enabled Message-ID: <201204250920.q3P9KDDc093458@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR arm/158950; it has been noted by GNATS. From: Kristof Provost <kristof@sigsegv.be> To: bug-followup@FreeBSD.org Cc: Subject: Re: arm/158950: arm/sheevaplug fails fsx when mmap operations are enabled Date: Wed, 25 Apr 2012 11:15:17 +0200 The sample program above has the following output: root@openrd:/mnt# /bin/kp After mmap: offset 32 is 0, not 32 as expected After mmap: offset 33 is 0, not 33 as expected After mmap: offset 34 is 0, not 34 as expected ... After mmap: offset 61 is 0, not 61 as expected After mmap: offset 62 is 0, not 62 as expected After mmap: offset 63 is 0, not 63 as expected After mmap: offset 224 is 0, not 96 as expected After mmap: offset 225 is 0, not 97 as expected ... That's confirmed by hexdump-ing the test.img file afterwards. I'm also able to reproduce the problem described in arm/162159. You're probably right about the relation. The problem looks very similar too: 32-byte sections that are 0 rather than the expected values.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201204250920.q3P9KDDc093458>