* Change RO rootfs failed RF Kill Switch Status and Failed to start Run pending postinsts @ 2020-02-18 1:00 JH 2020-02-18 4:35 ` JH 2020-02-18 6:37 ` [yocto] " Belisko Marek 0 siblings, 2 replies; 4+ messages in thread From: JH @ 2020-02-18 1:00 UTC (permalink / raw) To: linux-wireless Cc: Yocto discussion list, linux-mtd, Patches and discussions about the oe-core layer Hi, Apologize for the cross posting. I am running kernel 4.19.75 on iMX6 customized device with WiFi and 4G LTE, it was running well in an RW rootfs. After I have just changed rootfs to RO UBIFS partition, it failed RF Kill and postinsts I suspect both try write to the RO and failed, any advice how to fix it? Despite it failed RF Kill and postinsts, it was still working. [ 6.097762] UBIFS (ubi0:2): UBIFS: mounted UBI device 0, volume 2, name "rootfs-volume", R/O mode .............. [ 6.151932] VFS: Mounted root (ubifs filesystem) readonly on device 0:13. ................. [ OK ] Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch. Starting Load/Save RF Kill Switch Status... [FAILED] Failed to start Load/Save RF Kill Switch Status. See 'systemctl status systemd-rfkill.service' for details. [FAILED] Failed to start Run pending postinsts. See 'systemctl status run-postinsts.service' for details. ............... root# Thank you. Kind regards, - jh ______________________________________________________ Linux MTD discussion mailing list http://lists.infradead.org/mailman/listinfo/linux-mtd/ ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Change RO rootfs failed RF Kill Switch Status and Failed to start Run pending postinsts 2020-02-18 1:00 Change RO rootfs failed RF Kill Switch Status and Failed to start Run pending postinsts JH @ 2020-02-18 4:35 ` JH 2020-02-18 6:37 ` [yocto] " Belisko Marek 1 sibling, 0 replies; 4+ messages in thread From: JH @ 2020-02-18 4:35 UTC (permalink / raw) To: linux-wireless Cc: Yocto discussion list, linux-mtd, Patches and discussions about the oe-core layer It also seems mwifiex_sdio tried to write to RO rootfs and failed and triggled RF Killm, does mwifiex_sdio needs some system directories for RW? [ 26.636845] mwifiex_sdio mmc0:0001:1: mwifiex_process_cmdresp: cmd 0x242 fain Starting Load/Save RF Kill Switch Status... [ 26.852990] mwifiex_sdio mmc0:0001:1: info: MWIFIEX VERSION: mwifiex 1.0 (14 [ 26.861518] mwifiex_sdio mmc0:0001:1: driver_version = mwifiex 1.0 (14.68.36 [FAILED] Failed to start Load/Save RF Kill Switch Status. See 'systemctl status systemd-rfkill.service' for details. Starting Load/Save RF Kill Switch Status... [FAILED] Failed to start Load/Save RF Kill Switch Status. See 'systemctl status systemd-rfkill.service' for details. Starting Load/Save RF Kill Switch Status... [FAILED] Failed to start Load/Save RF Kill Switch Status. See 'systemctl status systemd-rfkill.service' for details. Starting Load/Save RF Kill Switch Status... On 2/18/20, JH <jupiter.hce@gmail.com> wrote: > Hi, > > Apologize for the cross posting. > > I am running kernel 4.19.75 on iMX6 customized device with WiFi and 4G > LTE, it was running well in an RW rootfs. After I have just changed > rootfs to RO UBIFS partition, it failed RF Kill and postinsts I > suspect both try write to the RO and failed, any advice how to fix it? > Despite it failed RF Kill and postinsts, it was still working. > > [ 6.097762] UBIFS (ubi0:2): UBIFS: mounted UBI device 0, volume 2, > name "rootfs-volume", R/O mode > .............. > [ 6.151932] VFS: Mounted root (ubifs filesystem) readonly on device > 0:13. > ................. > [ OK ] Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch. > Starting Load/Save RF Kill Switch Status... > [FAILED] Failed to start Load/Save RF Kill Switch Status. > See 'systemctl status systemd-rfkill.service' for details. > > [FAILED] Failed to start Run pending postinsts. > See 'systemctl status run-postinsts.service' for details. > ............... > root# > > Thank you. > > Kind regards, > > - jh > ______________________________________________________ Linux MTD discussion mailing list http://lists.infradead.org/mailman/listinfo/linux-mtd/ ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [yocto] Change RO rootfs failed RF Kill Switch Status and Failed to start Run pending postinsts 2020-02-18 1:00 Change RO rootfs failed RF Kill Switch Status and Failed to start Run pending postinsts JH 2020-02-18 4:35 ` JH @ 2020-02-18 6:37 ` Belisko Marek 2020-02-18 7:20 ` JH 1 sibling, 1 reply; 4+ messages in thread From: Belisko Marek @ 2020-02-18 6:37 UTC (permalink / raw) To: JH Cc: Yocto discussion list, linux-wireless, linux-mtd, Patches and discussions about the oe-core layer Hi, On Tue, Feb 18, 2020 at 2:00 AM JH <jupiter.hce@gmail.com> wrote: > > Hi, > > Apologize for the cross posting. > > I am running kernel 4.19.75 on iMX6 customized device with WiFi and 4G > LTE, it was running well in an RW rootfs. After I have just changed > rootfs to RO UBIFS partition, it failed RF Kill and postinsts I > suspect both try write to the RO and failed, any advice how to fix it? > Despite it failed RF Kill and postinsts, it was still working. > > [ 6.097762] UBIFS (ubi0:2): UBIFS: mounted UBI device 0, volume 2, > name "rootfs-volume", R/O mode > .............. > [ 6.151932] VFS: Mounted root (ubifs filesystem) readonly on device 0:13. > ................. > [ OK ] Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch. > Starting Load/Save RF Kill Switch Status... > [FAILED] Failed to start Load/Save RF Kill Switch Status. > See 'systemctl status systemd-rfkill.service' for details. Can you pls provide output of systemctl status systemd-rfkill There should be some more info what issue is. > > [FAILED] Failed to start Run pending postinsts. > See 'systemctl status run-postinsts.service' for details. Pls this one also: systemctl status run-postinsts > ............... > root# > > Thank you. > > Kind regards, > > - jh > -=-=-=-=-=-=-=-=-=-=-=- > Links: You receive all messages sent to this group. > > View/Reply Online (#48463): https://lists.yoctoproject.org/g/yocto/message/48463 > Mute This Topic: https://lists.yoctoproject.org/mt/71363457/900721 > Group Owner: yocto+owner@lists.yoctoproject.org > Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [marek.belisko@gmail.com] > -=-=-=-=-=-=-=-=-=-=-=- BR, marek ______________________________________________________ Linux MTD discussion mailing list http://lists.infradead.org/mailman/listinfo/linux-mtd/ ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [yocto] Change RO rootfs failed RF Kill Switch Status and Failed to start Run pending postinsts 2020-02-18 6:37 ` [yocto] " Belisko Marek @ 2020-02-18 7:20 ` JH 0 siblings, 0 replies; 4+ messages in thread From: JH @ 2020-02-18 7:20 UTC (permalink / raw) To: Belisko Marek Cc: Yocto discussion list, linux-wireless, linux-mtd, Patches and discussions about the oe-core layer Hi Belisko, Thanks for your resonse. On 2/18/20, Belisko Marek <marek.belisko@gmail.com> wrote: > Can you pls provide output of systemctl status systemd-rfkill > There should be some more info what issue is. Failed at step STATE_DIRECTORY spawning /lib/systemd/systemd-rfkill: Read-only file system, did it try to write something in /lib/systemd? How should I fix it? # systemctl status systemd-rfkill -l * systemd-rfkill.service - Load/Save RF Kill Switch Status Loaded: loaded (8;;file://solar/lib/systemd/system/systemd-rfkill.service/lib/systemd/system/systemd-rfkill.service8;;; static; vendor preset: disabled) Active: failed (Result: exit-code) since Tue 2020-02-18 00:47:30 UTC; 1min 59s ago Docs: 8;;man:systemd-rfkill.service(8)man:systemd-rfkill.service(8)8;; Process: 149 ExecStart=/lib/systemd/systemd-rfkill (code=exited, status=238/STATE_DIRECTORY) Main PID: 149 (code=exited, status=238/STATE_DIRECTORY) Feb 18 00:47:30 solar systemd[1]: Starting Load/Save RF Kill Switch Status... Feb 18 00:47:30 solar systemd[149]: systemd-rfkill.service: Failed to set up special execution directory in /var/lib: Read-only file system Feb 18 00:47:30 solar systemd[149]: systemd-rfkill.service: Failed at step STATE_DIRECTORY spawning /lib/systemd/systemd-rfkill: Read-only file system Feb 18 00:47:30 solar systemd[1]: systemd-rfkill.service: Main process exited, code=exited, status=238/STATE_DIRECTORY Feb 18 00:47:30 solar systemd[1]: systemd-rfkill.service: Failed with result 'exit-code'. Feb 18 00:47:30 solar systemd[1]: Failed to start Load/Save RF Kill Switch Status. Feb 18 00:47:30 solar systemd[1]: systemd-rfkill.service: Start request repeated too quickly. Feb 18 00:47:30 solar systemd[1]: systemd-rfkill.service: Failed with result 'exit-code'. Feb 18 00:47:30 solar systemd[1]: Failed to start Load/Save RF Kill Switch Status. >> [FAILED] Failed to start Run pending postinsts. >> See 'systemctl status run-postinsts.service' for details. > Pls this one also: systemctl status run-postinsts # systemctl status run-postinsts -l * run-postinsts.service - Run pending postinsts Loaded: loaded (8;;file://solar/lib/systemd/system/run-postinsts.service/lib/systemd/system/run-postinsts.service8;;; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2020-02-18 00:47:37 UTC; 6min ago Process: 153 ExecStart=/usr/sbin/run-postinsts (code=exited, status=0/SUCCESS) Process: 159 ExecStartPost=/bin/systemctl --no-reload disable run-postinsts.service (code=exited, status=1/FAILURE) Main PID: 153 (code=exited, status=0/SUCCESS) Feb 18 00:47:36 solar systemd[1]: Starting Run pending postinsts... Feb 18 00:47:36 solar run-postinsts[153]: Configuring packages on first boot.... Feb 18 00:47:36 solar run-postinsts[153]: (This may take several minutes. Please do not power off the machine.) Feb 18 00:47:36 solar run-postinsts[153]: /usr/sbin/run-postinsts: eval: line 1: can't create /var/log/postinstall.log: nonexistent directory Feb 18 00:47:36 solar run-postinsts[153]: Removing any system startup links for run-postinsts ... Feb 18 00:47:37 solar systemctl[159]: Failed to disable unit: File /etc/systemd/system/sysinit.target.wants/run-postinsts.service: Read-only file system Feb 18 00:47:37 solar systemd[1]: run-postinsts.service: Control process exited, code=exited, status=1/FAILURE Feb 18 00:47:37 solar systemd[1]: run-postinsts.service: Failed with result 'exit-code'. Feb 18 00:47:37 solar systemd[1]: Failed to start Run pending postinsts. Was the problem to write to /var/log, the /var/volatile does not have a log? # ls -l /var drwxr-xr-x 2 1000 1000 160 Feb 18 2020 backups drwxr-xr-x 5 1000 1000 100 Feb 18 00:47 cache drwxr-xr-x 9 1000 1000 180 Feb 18 00:47 lib drwxr-xr-x 3 1000 1000 224 Feb 18 2020 local lrwxrwxrwx 1 1000 1000 11 Feb 18 2020 lock -> ../run/lock lrwxrwxrwx 1 1000 1000 12 Feb 18 00:52 log -> volatile/log lrwxrwxrwx 1 1000 1000 6 Feb 18 2020 run -> ../run drwxr-xr-x 3 1000 1000 60 Feb 18 2020 spool lrwxrwxrwx 1 1000 1000 12 Feb 18 2020 tmp -> volatile/tmp drwxrwxrwt 8 root root 160 Feb 18 00:47 volatile # ls -l /var/volatile/ drwxr-xr-x 5 1000 1000 100 Feb 18 00:47 cache drwxr-xr-x 9 1000 1000 180 Feb 18 00:47 lib drwxr-xr-x 3 1000 1000 60 Feb 18 2020 spool All system mount is the same as the original RW rootfs, did both write to none standard RW system mount? Here is defined system mount in fstab: proc /proc proc defaults 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 tmpfs /run tmpfs mode=0755,nodev,nosuid,strictatime 0 0 tmpfs /var/volatile tmpfs defaults 0 0 Here is the mount: # mount ubi0:rootfs-volume on / type ubifs (ro,relatime,assert=read-only,ubi=0,vol=2) devtmpfs on /dev type devtmpfs (rw,relatime,size=84564k,nr_inodes=21141,mode=755) sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) proc on /proc type proc (rw,relatime) securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755) tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755) cgroup2 on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate) cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd) tmpfs on /etc/machine-id type tmpfs (ro,mode=755) tmpfs on /tmp type tmpfs (rw,nosuid,nodev) debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime) fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime) tmpfs on /var/volatile type tmpfs (rw,relatime) ubi0:data-volume on /data type ubifs (rw,noatime,assert=read-only,ubi=0,vol=3) tmpfs on /var/spool type tmpfs (rw,relatime) tmpfs on /var/cache type tmpfs (rw,relatime) tmpfs on /var/lib type tmpfs (rw,relatime) tracefs on /sys/kernel/debug/tracing type tracefs (rw,nosuid,nodev,noexec,relatime) How should I fix it? Thank you. Kind regards, - jh ______________________________________________________ Linux MTD discussion mailing list http://lists.infradead.org/mailman/listinfo/linux-mtd/ ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2020-02-18 7:20 UTC | newest] Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2020-02-18 1:00 Change RO rootfs failed RF Kill Switch Status and Failed to start Run pending postinsts JH 2020-02-18 4:35 ` JH 2020-02-18 6:37 ` [yocto] " Belisko Marek 2020-02-18 7:20 ` JH
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).