How to report a **MINOR** firmware bug in m500 MU05?

Kilobyte Kid

How to report a **MINOR** firmware bug in m500 MU05?

Hello,
I can not find a place on the support page to report microcode bugs.  (I may have missed it)
So can one of the moderators from crucical report this?


Device: CT120M500SSD3 at MU05 microcode level


The length fields in the ComPacket and Packet do not account for the required padding bytes.  The length field and the data payload in the Subpacket are correct so this is more of a technical issue that can be worked arround by ignoring the incorrect length fields but the device would fail the tests defined in section 2.5.1.4.d and 2.5.1.5.e of the Opal Test Cases Specification v1r1 (04, Feb 2011), specifically the requirement that the length fields in the ComPacket header and the Packet header SHALL be a multiple of 4.
Here is a example:
The SyncSession response when starting a session is:

0000 00000000 10000000 00000000 00000000  ................
0010 00000049 00000000 00000000 00000000  ...I............
0020 00000000 00000000 00000031 00000000  ...........1....
0030 00000000 00000025 f8a80000 00000000  .......%........
0040 00ffa800 00000000 00ff03f0 84000000  ................
0050 69840000 1000f1f9 f0000000 f1000000  i............... 

 
The ComPacket length (@0x0010) is 0x49 which is not a multiple of 4, and the Packet length (@0x0028) is 0x31 which is also not a multiple of 4.

As I said above this can easily be coded around and or ignored so it is not a functionality issue but a standards compliance issue.

 

Here is the buffer trace from a LockingSP activate session where you can see that this is consistent for all responses returned where the payload data length is not a multiple of 4 (no attachments?).

- 09:15:44.000 DBG : Log level set to DBG3
- 09:15:44.000 DBG : Activating the LockingSP on\\.\PhysicalDrive3 with password password
- 09:15:44.000 DBG2: Entering activateLockingSP()
- 09:15:44.000 DBG2: Querying device for Opal features
- 09:15:44.000 DBG3: Dumping D0Response

0000 000000a0 00000001 00000000 00000000  ................ 
0010 00000000 00000000 00000000 00000000  ................ 
0020 00000000 00000000 00000000 00000000  ................ 
0030 0001100c 11000000 00000000 00000000  ................ 
0040 0002100c 09000000 00000000 00000000  ................ 
0050 0003101c 01000000 00000000 00000200  ................ 
0060 00000000 00000008 00000000 00000000  ................ 
0070 0201100c 00000009 04000000 00000000  ................ 
0080 0202100c 00000009 05a00000 00000001  ................ 
0090 02031010 10000001 00000400 09000000  ................ 
- 09:15:44.000 DBG2: Starting Session
- 09:15:44.000 DBG3: Dumping command buffer

0000 00000000 10000000 00000000 00000000  ................ 
0010 00000064 00000000 00000000 00000000  ...d............ 
0020 00000000 00000000 0000004c 00000000  ...........L.... 
0030 00000000 00000040 f8a80000 00000000  .......@........ 
0040 00ffa800 00000000 00ff02f0 820069a8  ..............i. 
0050 00000205 00000001 01f200a8 70617373  ............pass 
0060 776f7264 f3f203a8 00000009 00000006  word............ 
0070 f3f1f9f0 000000f1 00000000 00000000  ................ 
- 09:15:44.000 DBG3: Dumping reply buffer

0000 00000000 10000000 00000000 00000000  ................ 
0010 00000049 00000000 00000000 00000000  ...I............ 
0020 00000000 00000000 00000031 00000000  ...........1.... 
0030 00000000 00000025 f8a80000 00000000  .......%........ 
0040 00ffa800 00000000 00ff03f0 84000000  ................ 
0050 69840000 1000f1f9 f0000000 f1000000  i............... 
0060 00000000 00000000 00000000 00000000  ................ 
0070 00000000 00000000 00000000 00000000  ................ 
- 09:15:44.000 DBG2: Get Lifecycle
- 09:15:44.000 DBG3: Dumping command buffer

0000 00000000 10000000 00000000 00000000  ................ 
0010 0000004c 00001000 00000069 00000000  ...L.......i.... 
0020 00000000 00000000 00000034 00000000  ...........4.... 
0030 00000000 00000025 f8a80000 02050000  .......%........ 
0040 0002a800 00000600 000016f0 f0f20306  ................ 
0050 f3f20406 f3f1f1f9 f0000000 f1000000  ................ 
0060 00000000 00000000 00000000 00000000  ................ 
0070 00000000 00000000 00000000 00000000  ................ 
- 09:15:44.000 DBG3: Dumping reply buffer

0000 00000000 10000000 00000000 00000000  ................ 
0010 00000032 00001000 00000069 00000000  ...2.......i.... 
0020 00000000 00000000 0000001a 00000000  ................ 
0030 00000000 0000000e f0f0f206 08f3f1f1  ................ 
0040 f9f00000 00f10000 00000000 00000000  ................ 
0050 00000000 00000000 00000000 00000000  ................ 
0060 00000000 00000000 00000000 00000000  ................ 
0070 00000000 00000000 00000000 00000000  ................ 
- 09:15:44.000 DBG2: LockingSP_UID.Activate[]
- 09:15:44.000 DBG3: Dumping command buffer

0000 00000000 10000000 00000000 00000000  ................ 
0010 00000040 00001000 00000069 00000000  ...@.......i.... 
0020 00000000 00000000 00000028 00000000  ...........(.... 
0030 00000000 0000001b f8a80000 02050000  ................ 
0040 0002a800 00000600 000203f0 f1f9f000  ................ 
0050 0000f100 00000000 00000000 00000000  ................ 
0060 00000000 00000000 00000000 00000000  ................ 
0070 00000000 00000000 00000000 00000000  ................ 
- 09:15:44.047 DBG3: Dumping reply buffer

0000 00000000 10000000 00000000 00000000  ................ 
0010 0000002c 00001000 00000069 00000000  ...,.......i.... 
0020 00000000 00000000 00000014 00000000  ................ 
0030 00000000 00000008 f0f1f9f0 000000f1  ................ 
0040 00000000 00000000 00000000 00000000  ................ 
0050 00000000 00000000 00000000 00000000  ................ 
0060 00000000 00000000 00000000 00000000  ................ 
0070 00000000 00000000 00000000 00000000  ................ 
- 09:15:44.047 INFO: Locking SP Activate Complete
- 09:15:44.047 DBG2: End Session
- 09:15:44.047 DBG3: Dumping command buffer

0000 00000000 10000000 00000000 00000000  ................ 
0010 00000028 00001000 00000069 00000000  ...(.......i.... 
0020 00000000 00000000 00000010 00000000  ................ 
0030 00000000 00000001 fa000000 00000000  ................ 
0040 00000000 00000000 00000000 00000000  ................ 
0050 00000000 00000000 00000000 00000000  ................ 
0060 00000000 00000000 00000000 00000000  ................ 
0070 00000000 00000000 00000000 00000000  ................ 
- 09:15:44.047 DBG3: Dumping reply buffer

0000 00000000 10000000 00000000 00000000  ................ 
0010 00000025 00001000 00000069 00000000  ...%.......i.... 
0020 00000000 00000000 0000000d 00000000  ................ 
0030 00000000 00000001 fa000000 00000000  ................ 
0040 00000000 00000000 00000000 00000000  ................ 
0050 00000000 00000000 00000000 00000000  ................ 
0060 00000000 00000000 00000000 00000000  ................ 
0070 00000000 00000000 00000000 00000000  ................ 

 

1 Reply
Community Manager

Re: How to report a **MINOR** firmware bug in m500 MU05?

Hello,

 

Thanks for this data. We will pass it on the correct group so they may take a look at it. 

 

 





YogiH, Crucial Moderator, US


________________________________________
How do I know what memory to buy?
Shop for your region: US | UK | EU | France |
I think my memory is bad. What do I do now?
FAQs and Top Forum Solutions
Did a user help you? Say thanks by giving Kudos!
Still need help? Contact Customer Service
Want to be a Super User?