usb 16go key copy problem on SAM and AOS4.1 U1 (now)

@ZeroG

Quote:

i want to thank you for the short cut too

@Amigo1

He, He, OCZ 16go FAT32 key dead again on AOS4.1U1.

This time, I have renamed the key, for testing and also deleting 500mo from the job and try to copy a 16mo and a 41 mo files from the HD to the USB key.

This 2 files without E flag and.... and during the copy, I have made a addbuffers USB0C: 1500 (200 per default and do that for testing).




Time for crashing the key (10 minuts)...

- Crazy size.
- 8+3 files.
- Crazy dates and filename caracters.

@Mrodfr

This is normal here..you need to know that you using USB on OS4 ..and OS4 for me have very bad USB stack :( ..All my USB stuff like memory stick,usb cam using on A1200 OS3/OS4 in combination with Posedion!! and no problems here! Poseidon is what wee need !!

@VooDoo

Yes, I know voodoo, and do exactly the same. I have just would dlike to see if allways the problems on AOS4.1U1 (again, yes I know) and I'm surprised to see It was too easy.

Rebooted the amiga and the Key have another name, good free size and total size but like the screenshot.

It's for remembering the problem on amigans.net for other amiga users and to be carefull with USB on AOS4.1.


A second AROS distro is actually made that mean we could use AROS and Poseidon on SAM soon. Crossing fingers



EDIT Saturday morning:

Wwitch on the classic and poseidon. Inserted the key on the spider2 and show with dopus4 that the key make a slowly directory read untill 15.9 go (the capacity of the key).

The key is empty with 15.9 go free (yesterday, lots of garbaged files on the SAM).


- copy a small file with the classic on the key give:

DEFEND~1 240 bytes

- Copy a second time the same file:

.defendguirc 240 bytes

and this time no problems. Strange.....


I copy actually the complete workbench HD on the key, with the classic and poseidon, and no problems, without usb FAT32 format.

Look like crossDOSfilesystem AOS3 repair the copy of the file on the USB key the second time.

Should i try to use crossdosfilesystem V42.5 - AOS3 (old one) on AOS4 ???? (for suriosity first).

@Mrodfr

Since my previou post, I have reformatted my key on a PC and put all files and drawer on the SAM HD to RWED.

My test was to copy all on SYS: to the Key.

At half on the copy, this USB memguard hit and the key stop with a requester described block error.

the USB pass his time to reset and show the key on the workbench screen. I have used retry and all the HD icons diseapeared.

The amiga boot fine and fortunately the key is allways here without loss.


I have allready reported this hit during AOS4.1 and AOS4 team know this problem but allways here with AOS4.1U1.......


NOTE: this is just an OHCI problem during a copy and could arrive, IMHO, on all time of medias.

NOTE2: for me, this problem is related to one of my USB hardware maybe not completely supported actually on AOS4.1U1.


The warning:

SFS: Warning: Task 0x5fe50070 ("OHCI Controller Task Unit 0") called DoPkt()
SFS: Warning: Task 0x5fe50070 ("OHCI Controller Task Unit 0") called DoPkt()
SFS: Warning: Task 0x5fe50070 ("OHCI Controller Task Unit 0") called DoPkt()
SFS: Warning: Task 0x5fe50070 ("OHCI Controller Task Unit 0") called DoPkt()
SFS: Warning: Task 0x5fe50070 ("OHCI Controller Task Unit 0") called DoPkt()
SFS: Warning: Task 0x5fe50070 ("OHCI Controller Task Unit 0") called DoPkt()

MEMGUARD HIT - "OHCI Controller Task Unit 0" (5fe50070)
allocation of 8192 bytes by AllocVecTagList() failed
0: 6edc8be4 5fe36d90 00000000 01ca97c4 00002000 5fe36e18 5ff60be8 59541088
8: 00002000 00000008 01ca97c4 0000207f 24000082 00000000 00000000 00000000
16: 00000000 00000001 59541088 5fe1e790 5fe1f680 00002000 01e70000 5ff9ab40
24: 00000000 00000040 5fe1c8a8 5fe8d5b8 00000000 00000040 00000002 00000003
----> 6edc8be4 : "MemGuard" segment 0005 offset 8bdc
----> 01ca97c4 : "Kickstart/kernel" segment 0001 offset 497c0
----> 01ca97c4 : "Kickstart/kernel" segment 0001 offset 497c0
----> 01e70000 : "Kickstart/newlib.library.kmod" segment 0001 offset 061c
LR 014136f0 : "Kickstart/kernel" segment 0000 offset 136ec
CTR 6edc8be4 : "MemGuard" segment 0005 offset 8bdc

Stack backtrace:
----> 014136f0 : "Kickstart/kernel" segment 0000 offset 136ec
----> 018c6dfc : "Kickstart/ohci.usbhcd" segment 0000 offset 5558
----> 018c45b4 : "Kickstart/ohci.usbhcd" segment 0000 offset 2d10
----> 018cb608 : "Kickstart/ohci.usbhcd" segment 0000 offset 9d64
----> 018cb788 : "Kickstart/ohci.usbhcd" segment 0000 offset 9ee4
----> 018c90b4 : "Kickstart/ohci.usbhcd" segment 0000 offset 7810
----> 0141587c : "Kickstart/kernel" segment 0000 offset 15878

Disassembly:
014136ec: 4e800421 bctrl
014136f0: 80010084 lwz r0,132(r1)
014136f4: 38210080 addi r1,r1,128
014136f8: 7c0803a6 mtlr r0
014136fc: 4e800020 blr