Bug#455909: linux-image-2,6-iop32x: many misaligned memory accesses

["Martin Guy" <martinwguy@yahoo.it>]

> I can reproduce this problem with 2.6.18-5 and 2.6.22-3, but not with
> 2.6.23-1 from unstable.  Can you try 2.6.23?

Seems I can't, no, having spent a day trying. But then I never built a
kernel package before, so that doesn't mean much. After most of a day
trying I'm giving up. Can you give me a prod in the right direction?

The binary's not in the repo, and all my various attempts at building
it from the linux-2.6_2.6.23-1 Debian sources with dpkg-makepackage or
from linux-sources-2.6.23 using:
make-kpkg all fail, gabbling about

/bin/sh: line 0: [: -lt: unary operator expected
/bin/sh: line 0: [: -eq: unary operator expected
/bin/sh: line 0: [: -eq: unary operator expected
/bin/sh: line 0: [: -eq: unary operator expected
/bin/sh: line 0: [: -lt: unary operator expected
/bin/sh: line 0: [: -eq: unary operator expected
/bin/sh: line 0: [: -eq: unary operator expected
/bin/sh: line 0: [: -gt: unary operator expected
/bin/sh: line 0: [: -ge: unary operator expected
/bin/sh: line 0: [: -ge: unary operator expected
Not in correct source directory

For example, the make-kpkg runes I'm using are:
# apt-get install linux-source-2.6.23
$ cd /usr/src
$ tar xfj lin*bz2
$ ln -s linux-2.6.23 linux
martin@n2100:/usr/src$ cd linux
martin@n2100:/usr/src/linux$ make iop32x_defconfig
martin@n2100:/usr/src/linux$ fakeroot make-kpkg kernel_image
exec debian/rules  DEBIAN_REVISION=..-10.00.Custom  kernel_image
/bin/sh: line 0: [: -lt: unary operator expected
/bin/sh: line 0: [: -eq: unary operator expected
/bin/sh: line 0: [: -eq: unary operator expected
/bin/sh: line 0: [: -gt: unary operator expected
/bin/sh: line 0: [: -ge: unary operator expected
/bin/sh: line 0: [: -ge: unary operator expected
Not in correct source directory

I also don't understand how the autobuilt kernel package gets its
config, so I've used iop32x_defconfig in the debian-patched source
tree. Is that right?

Riku reports that 2.6.23-1 on his N2100s does not exhibit the same
symptoms either.

Any clues, or shall I wait until a binary makes it into the repo?

Cheers

    M