All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ruediger Meier <sweet_f_a@gmx.de>
To: util-linux@vger.kernel.org
Cc: Aurelien Jarno <aurelien@aurel32.net>,
	Andreas Henriksson <andreas@fatal.se>
Subject: test fdisk/bsd on exotic archs
Date: Wed, 28 Jan 2015 11:45:20 +0100	[thread overview]
Message-ID: <201501281145.21775.sweet_f_a@gmx.de> (raw)

Hi,

the fdisk/bsd test fails on ppc64le:
 Create default BSD
-2e1cee529cb59c9341afef0443f196a1 bsd.img
+6d760d7a8ef33b27cc6e27f1e8807d48 bsd.img
[...]

Actually Aurelien's patch a80886e9 should already address this because
it's the case little endian, BSD_LABELSECTOR = 0, BSD_LABELOFFSET = 64.

Aurelien or Andreas, do you still have such a system for this case? I
guess it was little endian alpha. Maybe you could send us the hexdump
output when running the test with the following debug patch (current
HEAD master):

diff --git a/tests/ts/fdisk/bsd b/tests/ts/fdisk/bsd
--- a/tests/ts/fdisk/bsd
+++ b/tests/ts/fdisk/bsd
@@ -115,6 +115,8 @@ ts_log "Create default BSD"
 echo -e "${FDISK_CMD_BSD_CREATE}${FDISK_CMD_WRITE_CLOSE}" | \
 	$TS_CMD_FDISK ${TEST_IMAGE_NAME} &> /dev/null
 ts_image_md5sum >> $TS_OUTPUT 2>&1
+echo -e "\nhexdump default BSD"
+$TS_CMD_HEXDUMP -C ${TEST_IMAGE_NAME}
 
 print_bsd_layout
 
-- 


My ppc64le hexdump output looks like this one below. It seems to be ok
I think. It's the same like x86 except other offsets. But md5sum is
6d760d7a8ef33b27cc6e27f1e8807d48:

hexdump default BSD
00000000  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
000001b0  00 00 00 00 00 00 00 00  01 00 00 00 00 00 00 20  |............... |
000001c0  21 00 83 41 01 00 00 08  00 00 00 08 00 00 00 04  |!..A............|
000001d0  01 3e a5 13 41 36 00 10  00 00 00 40 00 00 00 00  |.>..A6.....@....|
000001e0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
000001f0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 55 aa  |..............U.|
00000200  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
00200040  57 45 56 82 06 00 00 00  00 00 00 00 00 00 00 00  |WEV.............|
00200050  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
00200060  00 00 00 00 00 00 00 00  00 02 00 00 3f 00 00 00  |............?...|
00200070  ff 00 00 00 01 00 00 00  c1 3e 00 00 c1 3e 00 00  |.........>...>..|
00200080  00 00 00 00 00 00 00 00  10 0e 01 00 00 00 00 00  |................|
00200090  00 00 00 00 00 00 00 00  20 00 00 00 00 00 00 00  |........ .......|
002000a0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
002000c0  00 00 00 00 57 45 56 82  33 62 04 00 00 20 00 00  |....WEV.3b... ..|
002000d0  00 20 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |. ..............|
002000e0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
002000f0  00 00 00 00 00 40 00 00  00 10 00 00 00 00 00 00  |.....@..........|
00200100  00 00 00 00 c1 3e 00 00  00 00 00 00 00 00 00 00  |.....>..........|
00200110  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
00a00000

cu,
Rudi

             reply	other threads:[~2015-01-28 20:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-28 10:45 Ruediger Meier [this message]
2015-01-28 13:31 ` test fdisk/bsd on exotic archs Andreas Henriksson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201501281145.21775.sweet_f_a@gmx.de \
    --to=sweet_f_a@gmx.de \
    --cc=andreas@fatal.se \
    --cc=aurelien@aurel32.net \
    --cc=util-linux@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.