[WP7605][SW] How to capture syslog(kernel log)

Question:
Could you tell me the way how to collect syslog(kernel log)?

Back Ground:
According to SFDC#01219418, dev team request to collect syslog for debugging.
In my understanding, “dmesg” was captured syslog, but dev team request to collect “logread”, “logread -f”, and “logread -f | … &”, but my device was faild to “logread”.
I would like to know the way to collect syslog by any “logread” command.

Best Regards,

dmesg is for kernel log
logread is for syslog including the log of legato.

What do yo mean by “my device was faild to “logread””?

Please see the below logs.

root@swi-mdm9x28-wp:~# logread
logread: can’t find syslogd buffer: No such file or directory

I don’t see problem in my module, how to reproduce this issue?

This is customer module as SKU#1104763.
There is only way to send “logread” during stand-by mode.
Yes, my device was not reproduced this behavior.

then how to reproduce with your customer module?
Is it 100% reproducible?
Or there are certain reproducible steps?

Here is step by step to reproduce this issue.
Reproduce rate is 100%.

#1 boot-up, wait to sense standby
#2 192.168.2.2 login (root)
#3 type “logread”
#4 show as “logread: can’t find syslogd buffer: No such file or directory”

Please note that cusomer device used legato application and it was installed inside this failure device.

how many modules are seeing this issue?
Only one?
Or all modules in customer devices?

All modules in customer device as same setting and SKU#.

do you mean once you received these fresh modules, they are having this issue?
(then this might be some quality issue instead of legato issue)

Will the module be recovered if you clear the userapp partition?

I have some test here, even the legato framework is not running, the logread should be still Ok to get syslog.

root@swi-mdm9x28-wp:~# find / -name "syslog"
/etc/init.d/syslog
find: /proc/1856: No such file or directory
/sys/fs/smackfs/syslog
root@swi-mdm9x28-wp:~# legato status
Systems installed:
  19 [good] <-- current
Legato framework is NOT running.