| Summary: | [Test Case 237] system shutdown with UNFS | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] BSPs | Reporter: | Chandrak <chandrak> | ||||||
| Component: | bsps-runtime | Assignee: | Bruce Ashfield <bruce.ashfield> | ||||||
| Status: | RESOLVED WORKSFORME | QA Contact: | |||||||
| Severity: | minor | ||||||||
| Priority: | Medium | CC: | alexandru.c.georgescu, jessica.zhang, yp.kernel.watcher, yp.watcher | ||||||
| Version: | 1.5 | ||||||||
| Target Milestone: | 1.5.1 | ||||||||
| Hardware: | x86 | ||||||||
| OS: | Multiple | ||||||||
| Whiteboard: | |||||||||
| OS type for building Yocto: | --- | Type of Regression: | --- | ||||||
| Verified: | Documentation change: | Don't know | |||||||
| Attachments: |
|
||||||||
This can b e looked at post 1.5, but chances are, this is simply a shutdown ordering issue. If you shutown the ethernet interface too soon in the process, shutdown hangs since your rootfs goes away. It's a common issue with usermode NFS, but with the possibility of either systemd or sysvinit being enabled, the solution isn't as simple as it used to be. qemu: x86-64 and arm unable to boot the images. both are creating panic. 1.5_M5.rc6:102bf5e0f640fe85068452a42b85077f1c81e0c9 I will attach the panic bmp files soon... Created attachment 1561 [details]
panic snapshot
Created attachment 1562 [details]
qemu x86 panic snapshot
Hi Chandra, We have tested with the latest QEMU machines, and we didn't find any of the two issues you mentioned: boot and shutdown via NFS. Closing the bug since this hasn't been reproduced. |
STATUS: FAILED BUILD: master:566ca1e4769b4ec7e3f6c6a98bb817db2221cf82 ENVIRONMENT: qemu-x86 STEPS TO REPRODUCE: 1. Use UNFS to start QEMU targets runqemu-extract-sdk core-image-sato-arch.rootfs.tar.bz2 rootfs runqemu nfs kernel rootfs 2. Run shutdown in QEMU targets EXPECTED OUTCOME: QEMU shutdown with UNFS should work . P.S: see bug# 4599 also, it might help.. in 4599, testcase number was asked may be to reproduce the issue... This issue is seen on three platforms of Qemu (x86, x86-64 and arm ).