| Summary: | meta-intel: BSPs built with linux-yocto-rt hang at 'waiting for removable media...' on USB hddimg boots | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Yocto Project Subprojects] Kernel | Reporter: | Tom Zanussi <tom.zanussi> | ||||
| Component: | kernel-configuration | Assignee: | Darren Hart <dvhart> | ||||
| Status: | VERIFIED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | Medium | CC: | dvhart, mihai.lindner, yp.kernel.watcher, yp.watcher | ||||
| Version: | 1.3 | ||||||
| Target Milestone: | 1.3 M3 | ||||||
| Hardware: | x86 | ||||||
| OS: | x86_64 | ||||||
| Whiteboard: | (Done) | ||||||
| OS type for building Yocto: | --- | Type of Regression: | --- | ||||
| Verified: | Documentation change: | --- | |||||
| Attachments: |
|
||||||
I just built fri2 with linux-yocto-rt_3.2 and it behaves the same. If I add and remove the USB stick, the kernel reports the removal and addition and correctly identifies it as /dev/sda. I'll instrument the init script and see what is missing. I think we need a INITDEBUG for our init scripts so we don't have to rebuild the the initrd to do this :/ Gah, scratch that. It actually works on the fri2. Checked the linux-yocto-rt .config for the jasperforest BSP. It is missing: CONFIG_BLK_DEV_SD CONFIG_USB_STORAGE CONFIG_VFAT_FS etc. See the fri2-preempt-rt.scc file, jasperforest is missing: # default policy for preempt-rt kernels include cfg/usb-mass-storage.scc include cfg/boot-live.scc include features/latencytop/latencytop.scc include features/profiling/profiling.scc I'll prepare a patch. Patches submitted to linux-yocto list for both 3.2 and 3.4 kernels. Commit in master: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=2b6114d5cc2f5ccac82d2530093c505686c0e4a8 . |
Created attachment 646 [details] boot log Both the chiefriver and jasperforest BSPs hang on bootup with 'waiting for removable media...' when booted from a USB stick (.hddimg) (see attached serial log). In both cases I tried both 3.2 and 3.4 rt kernels with the same result. I'm not sure if it's a kernel config issue or just that the rt kernel reliably triggers an underlying problem or race having to do with mounting USB filesystems, or something like that, so just marked it as a kernel config issue for lack of a better idea. To test this I basically replaced the preferred kernel in the machine config e.g PREFERRED_PROVIDER_virtual/kernel = "linux-yocto-rt" , built the core-image-rt image, etc.