"cg 0: bad magic number" with umass

[Hans Petter Selasky]

On Tuesday 30 June 2009 19:57:28 Ari Sovijärvi wrote:
> Hans Petter Selasky wrote:
> > Could you show the dmesg of the USB controller? At which bus is it
> > connected? Nexus? There might be bugs in the actual USB device/host
> > hardware.
>
> Here's all I could find of the USB controller from the dmesg's output.
>
> ohci0: <AcerLabs M5237 (Aladdin-V) USB controller> mem 0x1000000-0x1000fff
> at device 10.0 on pci0
> ohci0: [GIANT-LOCKED]
> ohci0: [ITHREAD]
> usb0: OHCI version 1.0, legacy support
> usb0: <AcerLabs M5237 (Aladdin-V) USB controller> on ohci0
> usb0: USB revision 1.0
> uhub0: <AcerLabs OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb0
> uhub0: 2 ports with 2 removable, self powered
>
> If you need to see anything else from the dmesg, here's the full output:
> http://pastebin.ca/1479774
>
> The USB-enclosure I used was LaCie's "design by porsche" with 1 terabyte
> Seagate disk.
>
> > Are you using 8-current ?
>
> No, 7.2.

Hi,

If you do a simple test on the disk:

dd if=/dev/urandom of=test.img bs=65536 count=16

cat test.img > /dev/daX

dd if=/dev/daX of=test_rb.img bs=65536 count=16

diff test.img test_rb.img

The only problem I can see is that there is something wrong with the cache 
invalidate/flush instruction wrappers on the sparc.

If you need, umass debugging:

sysctl hw.usb.umass.debug=-1

--HPS