| Summary: | Intel SSD in USB 3.0 enclosure with USB 3.0 hub not detected at boot time when plugged into USB 2.0 port | ||
|---|---|---|---|
| Product: | [Hardware Platforms] MinnowBoard MAX Firmware | Reporter: | Max Eliaser <max.eliaser> |
| Component: | minnowmax-edk2 | Assignee: | He, Tim <tim.he> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | normal | ||
| Priority: | Low | CC: | sjolley.yp.pm, warthog9 |
| Version: | unspecified | ||
| Target Milestone: | Production Release | ||
| Hardware: | MinnowBoard Max | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Don't know | |
I have just observed the bug happening a couple of times with the USB 3.0 hub plugged into the USB 3.0 port, which contracticts what I wrote in the initial report. Closing as I've been unable to reproduce. |
This is a pretty weird and oddly specific one. I have a 40 GB Intel SSD. The model number is SSDSA2M040G2GC, so I think it's this one: http://www.newegg.com/Product/Product.aspx?Item=N82E16820167025 The SSD is in a Sabrent-branded USB 3.0 enclosure for laptop-sized hard drives. It has no additional power source besides USB. When I plug the enclosure into a USB 3.0 hub, and then plug the hub into the MinnowMax's USB 2.0 port, the disk is not detected by the firmware when the MinnowMax is powered on. If I unplug and replug either the enclosure or the hub, then run "map -r", the disk *is* detected. If I just run "connect -r" or "map -r" without unplugging/replugging first, nothing happens. If I move the USB 3.0 hub to the MinnowMax's USB 3.0 port instead of the MinnowMax's USB 2.0 port, the drive *does* get detected. When I switch to a USB 2.0 hub, the bug goes away as well, and the drive gets detected no matter which USB port the hub is connected to. When I plug the drive directly into either USB port on the MinnowMax it works correctly. When I switch from the enclosed SSD to a regular USB 3.0 flash drive, it also works correctly. Confused yet? Have a table: Configuration Result ---------------------------------------------------------------------------- Enclosed SSD -> USB 3.0 Hub -> MinnowMax USB 2.0 port Not detected Enclosed SSD -> USB 3.0 Hub -> MinnowMax USB 3.0 port Detected Enclosed SSD -> USB 2.0 Hub -> MinnowMax USB 2.0 port Detected Enclosed SSD -> USB 2.0 Hub -> MinnowMax USB 3.0 port Detected Enclosed SSD -> MinnowMax USB 2.0 port Detected Enclosed SSD -> MinnowMax USB 3.0 port Detected USB Stick -> USB 3.0 Hub -> MinnowMax USB 2.0 port Detected USB Stick -> USB 3.0 Hub -> MinnowMax USB 3.0 port Detected USB Stick -> USB 2.0 Hub -> MinnowMax USB 2.0 port Detected USB Stick -> USB 2.0 Hub -> MinnowMax USB 3.0 port Detected USB Stick -> MinnowMax USB 2.0 port Detected USB Stick -> MinnowMax USB 3.0 port Detected Like I said though, even in the "not detected" case, unplugging/replugging the hub or enclosure and then running "map -r" at the EFI shell will cause the drive to be detected correctly. It just isn't picked up when the MinnowMax is powered on. I tried this with two USB 3.0 hubs and two USB 2.0 hubs. *Both* USB 3.0 hubs behaved identically to each other, and both USB 2.0 hubs behaved identically to each other. All four hubs used in this test were capable of being powered hubs, but none of them were tested with their power adapters plugged in. I only had the one enclosure/SSD for this test, and I only used one USB stick as well. This bug is not guaranteed to happen every time, but it happens the vast bulk of attempts so it should not be hard to reproduce. This firmware bug is a regression. I was running a weeks-old firmware version without this issue. However, versions 7.10 and 7.18 of the firmware both exhibit this behavior. Unfortunately I don't know what firmware version I was using before so I can't tell you a known-working version yet. This has also been observed on two separate MinnowMaxs, so it's definitely firmware and not hardware.