Giter Club home page Giter Club logo

meta-murata-wireless's People

Contributors

bchen-murata avatar jameel-kareem avatar jameelkareem avatar jameelkareem-mothra avatar jameelkareem-murata avatar romit-chatterjee avatar romit-murata avatar skerr-murata avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

meta-murata-wireless's Issues

Customization for a custom board

I'm trying to get to a custom build for a custom board that uses the Type 1CK module and is based on the imx6ullevk demo board. How can I use this script to setup everything but customize the build to work with my hardware? I've run through the script and run the bitbake command with the fsl-imx-x11 distro and imx6ulevk machine and the resulting image works on the demo eval board, but i need to end up with a device tree file that works for my board. If I create a device tree blob from a kernel source I downloaded, it just hangs prior to rootfs loading, however i know the device tree works on my board when i build the kernel from source outside yocto. additionally, i need to get to a rootfs that also has mono-complete (mono+gtk3+gtk-sharp). I can get there with buildroot, but that doesn't get me a setup that works with the murata wireless module.

Issue on driver loading step for imx8mm

Hi,

I try to connect and configure the 1DX SDIO module to a imx8mm EVK board.
The 1DX module is connected through an adapter (from Saiko system) to the microSD.

WL_REG_ON is connected on VIO_IN (3.3V)
WL_HOST_WAKE is not connected

I recover the meta-murata-wireless (branch imx-sumo-manda) layer from github and configure it with the script add-murata-wireless.sh for imx8mmevk board.
Compilation is fine.

I flash the eMMC with Uboot to start in TFTP + NFS.

Firmwares are correctly located in

# ls /lib/firmware/brcm/  
README_NVRAM                 brcmfmac43430-sdio.txt  
brcmfmac43012-sdio.bin       brcmfmac43455-sdio.bin  
brcmfmac43012-sdio.clm_blob  brcmfmac43455-sdio.clm_blob  
brcmfmac43012-sdio.txt       brcmfmac43455-sdio.txt  
brcmfmac43340-sdio.bin       brcmfmac4354-sdio.bin  
brcmfmac43340-sdio.txt       brcmfmac4354-sdio.clm_blob  
brcmfmac43362-sdio.bin       brcmfmac4354-sdio.txt  
brcmfmac43362-sdio.txt       brcmfmac4356-pcie.bin  
brcmfmac4339-sdio.bin        brcmfmac4356-pcie.clm_blob  
brcmfmac4339-sdio.txt        brcmfmac4356-pcie.txt  
brcmfmac43430-sdio.bin       brcmfmac4359-pcie.bin  
brcmfmac43430-sdio.clm_blob  murata-master  

My main issue is that I have several kinf of error messages. It seems issue on communication (RX/TX) bus.

I search into community forum without any success.

[ 81.424980] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[ 81.432118] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[ 81.440554] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
[ 81.447684] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[ 81.455792] mmc1: queuing unknown CIS tuple 0x80 (6 bytes)
[ 81.559031] mmc1: new high speed SDIO card at address 0001
[ 81.667279] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x0808c, err: -84
[ 81.694639] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x080ac, err: -84
[ 81.703149] brcmfmac: brcmf_fw_map_chip_to_name: using brcm/brcmfmac43430-sdio.bin for chip 0x00a9a6(43430) rev 0x000001
[ 81.875439] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x08508, err: -84
[ 81.895647] brcmfmac: brcmf_sdio_read_control: read 216 control bytes failed: -84
[ 81.903172] brcmfmac: brcmf_sdio_rxfail: abort command, terminate frame, send NAK
[ 84.443257] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 84.449111] brcmfmac: brcmf_c_process_clm_blob: clmload (7222 byte file) failed (-110);
[ 84.452354] brcmfmac: brcmf_sdio_readframes: RXHEADER FAILED: -84
[ 84.466590] brcmfmac: brcmf_sdio_rxfail: abort command, terminate frame, send NAK
[ 87.135290] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 87.141146] brcmfmac: brcmf_c_process_clm_blob: get clmload_status failed (-110)
[ 87.148582] brcmfmac: brcmf_c_preinit_dcmds: download CLM blob file failed, -5
[ 87.155832] brcmfmac: brcmf_bus_started: failed: -5
[ 87.160747] brcmfmac: brcmf_sdio_firmware_callback: dongle is not responding

[   30.304845] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x080e4, err: -84  
 [   30.316715] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x080fc, err: -84  
 [   30.329910] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x0c040, err: -84  
 [   30.343086] brcmfmac: brcmf_fw_map_chip_to_name: using brcm/brcmfmac43430-sdio.bin for chip 0x00a9a6(43430) rev 0x000001  
 [   31.405779] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50  
 [   32.439722] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50  
 [   33.458473] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50  


[   43.265595] mmc1: new high speed SDIO card at address 0001  
[   43.282966] brcmfmac: brcmf_fw_map_chip_to_name: using brcm/brcmfmac43430-sdio.bin for chip 0x00a9a6(43430) rev 0x000001  
[   43.453868] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x08508, err: -84  
[   43.477337] brcmfmac: brcmf_c_preinit_dcmds: Murata Customized Version: imx-sumo-manda_r1.0;  
[   43.485820] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Sep 11 2018 09:22:09 version 7.45.98.65 (r707797 CY) FWID 01-b54727f  
[   43.499047] brcmfmac: brcmf_sdio_read_control: read 232 control bytes failed: -84  
[   43.506573] brcmfmac: brcmf_sdio_rxfail: abort command, terminate frame, send NAK  
[   46.061988] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout  
[   46.077209] brcmfmac: brcmf_sdio_ulp_preinit: ulp_sdioctrl iovar returned err = -23  
[   46.096442] brcmfmac: brcmf_sdio_readframes: RXHEADER FAILED: -84  
[   46.102586] brcmfmac: brcmf_sdio_rxfail: abort command, terminate frame, send NAK  
[   48.738014] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout  
[   48.747608] brcmfmac: brcmf_sdio_readframes: RXHEADER FAILED: -84  
[   48.753734] brcmfmac: brcmf_sdio_rxfail: abort command, terminate frame, send NAK  
[   51.298013] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout  


[  580.074390] mmc1: new high speed SDIO card at address 0001  
[  580.167552] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x08000, err: -84  
[  580.175687] brcmfmac: brcmf_chip_recognition: chip backplane type 15 is not supported  
[  580.183543] brcmfmac: brcmf_sdio_probe_attach: brcmf_chip_attach failed!  
[  580.190299] brcmfmac: brcmf_sdio_probe: brcmf_sdio_probe_attach failed  
[  580.197025] brcmfmac: brcmf_ops_sdio_probe: F2 error, probe failed -19..  

Thanks for your help.

Fabrice .

support for imx6sllevk ?

Hello,

What is the status for the imx6sllevk ? I do not see anything in the documentation about it, but I was wondering if the support is there.

Any tips on how to get it up and running ?

Thank you,

Alex

Murata_Wireless_Yocto_Build_CYW fails on Ubuntu 20.04

I discovered this issue while building an image on a fresh install of Ubuntu 20.04 on WSL2 (including apt update, apt dist-upgrade, apt upgrade, etc.) After running the Host Setup script, I ran the Murata_Wireless_Yocto_Build_CYW.sh script and followed the prompts. The script seemed to run normally without any (obvious/RED) errors, but when it reached the end and I selected 'Y' to start the build, the script would exit without actually starting the build.

After looking more closely at the output, there were a few errors around Step 11 like "-bash ./imx-setup-release.sh: No such file or directory". So I started working through the steps in the script manually and found the issue when trying to run repo and I would get this error:

/usr/bin/env: ‘python’: No such file or directory

Implying that Python was not installed. In order to fix this on Ubuntu 20.04, I installed the "python-is-python3" package with

sudo apt install python-is-python3

This seems to have resolved the issue and now the Murata build script runs normally.

It may be worth updating your Host Setup script to ensure python is installed.

I hope this helps anyone else running into issues with the Murata build script.

Not able to integrate Bluez5-5.50 stack to the imx-morty-battra_r1.1 release

I used below options to build a Yocto image.

i.MX Yocto Release              : 4.9.11_1.0.0 GA
Yocto branch                    : morty
fmac version                    : "battra" (v4.14)
Target                          : imx6ull14x14evk
meta-murata-wireless Release Tag: imx-morty-battra_r1.1
VIO Signaling                   : 1.8V VIO signaling without UHS support - HW mods needed
DISTRO                          : fsl-imx-x11
Image                           : core-image-base 
Build Directory                 : build-imx6ull14x14evk

I am able to build it fine but Bluez5 stack version that I get with the image is 5.41 which is older and I want latest 5.50 stack in there so first I tried to include just PREFERRED_VERSION_bluez5 in there but that didn't help me to get that specific version automatically so then I tried adding custom dev layer along with correct Bluez5 bblayer recipes in there then getting below errors regarding parsing that recipe.

ERROR: ExpansionError during parsing xxx/murata-imx-bsp/sources/meta-dev/recipes-connectivity/bluez5/bluez5_5.50.bb

Traceback (most recent call last):
  File "xxx/murata-imx-bsp/sources/poky/meta/classes/base.bbclass", line 375, in __anon_656__xxx_murata_imx_bsp_sources_poky_meta_classes_base_bbclass(d=<bb.data_smart.DataSmart object at 0x7fc110f56908>):
             pkgconfig = (d.getVar('PACKAGECONFIG', True) or "").split()
    >        pn = d.getVar("PN", True)
     
  File "xxx/murata-imx-bsp/sources/poky/bitbake/lib/bb/data_smart.py", line 569, in DataSmart.getVar(var='PACKAGECONFIG', expand=True, noweakdefault=False, parsing=False):
         def getVar(self, var, expand, noweakdefault=False, parsing=False):
    >        return self.getVarFlag(var, "_content", expand, noweakdefault, parsing)
     
  File "xxx/murata-imx-bsp/sources/poky/bitbake/lib/bb/data_smart.py", line 737, in DataSmart.getVarFlag(var='PACKAGECONFIG', flag='_content', expand=True, noweakdefault=False, parsing=False):
                     cachename = var + "[" + flag + "]"
    >            value = self.expand(value, cachename)
     
  File "xxx/murata-imx-bsp/sources/poky/bitbake/lib/bb/data_smart.py", line 410, in DataSmart.expand(s="obex-profiles     readline     ${@bb.utils.filter('DISTRO_FEATURES', 'systemd', d)}     a2dp-profiles     avrcp-profiles     network-profiles     hid-profiles     hog-profiles     tools     deprecated ", varname='PACKAGECONFIG'):
         def expand(self, s, varname = None):
    >        return self.expandWithRefs(s, varname).value
     
  File "xxx/murata-imx-bsp/sources/poky/bitbake/lib/bb/data_smart.py", line 400, in DataSmart.expandWithRefs(s="obex-profiles     readline     ${@bb.utils.filter('DISTRO_FEATURES', 'systemd', d)}     a2dp-profiles     avrcp-profiles     network-profiles     hid-profiles     hog-profiles     tools     deprecated ", varname='PACKAGECONFIG'):
                 except Exception as exc:
    >                raise ExpansionError(varname, s, exc) from exc
     
bb.data_smart.ExpansionError: Failure expanding variable PACKAGECONFIG, expression was obex-profiles     readline     ${@bb.utils.filter('DISTRO_FEATURES', 'systemd', d)}     a2dp-profiles     avrcp-profiles     network-profiles     hid-profiles     hog-profiles     tools     deprecated  which triggered exception AttributeError: module 'bb.utils' has no attribute 'filter'


Summary: There was 1 WARNING message shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.

While if I use Sumo release branch for the Yocto then I am able to add the same custom dev layer fine without any issues in parsing that recipe.

So does anyone know how to fix this issue?

latest build does not work; imx-rocko-mini-manda_r1.0 not found

Hello,

The latest build does not seem to be working anymore; it looks like this tag does not exist (yet?).

error: pathspec 'imx-rocko-mini-manda_r1.0' did not match any file(s) known to git.
chmod: cannot access 'sources/meta-murata-wireless/add-murata-layer-script/add-murata-wireless.sh': No such file or directory
sh: 0: Can't open ./sources/meta-murata-wireless/add-murata-layer-script/add-murata-wireless.sh
./Murata_Wireless_Yocto_Build.sh: line 2672: cd: /home/miip/solox/wifi/sources/meta-murata-wireless/recipes-kernel/linux: No such file or directory

sumo build broken

Branch: imx-sumo-manda

Build was working a couple weeks ago, but now appears a file is missing in cyw-bt-patch.

/tmp/work/aarch64-poky-linux/murata-binaries/1.0-r0//cyw-bt-patch/CYW4345C0.1MW.hcd': No such file or directory

It appears the repo cyw-bt-patch was changed, but the recipe was not updated to match.

murata-binaries-1.0-r0 do_fetch: Fetcher failure

I'm trying to build the Yocto Zeus image, using the Murata_Wireless_Yocto_Build_CYW.sh script (version 08222022) from script-utils/latest directory.

The build is configured for following settings:

i.MX Yocto Release              : 5.4.47_2.2.0 GA
Yocto branch                    : zeus
fmac version                    : baragon
Target                          : imx8mqevk
NXP i.MX EVK Part Number        : MCIMX8M-EVKB
meta-murata-wireless Release Tag: imx-zeus-baragon_r1.0
DISTRO                          : fsl-imx-wayland
Image                           : fsl-image-validation-imx 
Build Directory                 : build-dir

Host distribution is Ubuntu 20.04.

The build fails with following:

ERROR: murata-binaries-1.0-r0 do_fetch: Fetcher failure: Unable to resolve 'master' in upstream git repository in git ls-remote output for git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
ERROR: Logfile of failure stored in: /home/ktuulos/yocto/meta-murata-wireless/zeus3/build-dir/tmp/work/aarch64-poky-linux/murata-binaries/1.0-r0/temp/log.do_fetch.3654789
ERROR: Task (/home/ktuulos/yocto/meta-murata-wireless/zeus3/sources/meta-murata-wireless/recipes-connectivity/murata-binaries/murata-binaries_1.0.bb:do_fetch) failed with exit code '1'

I have tried this in two different computers, both get the same result.

The logfile contains following:

DEBUG: Executing python function extend_recipe_sysroot
NOTE: Direct dependencies are []
NOTE: Installed into sysroot: []
NOTE: Skipping as already exists in sysroot: []
DEBUG: Python function extend_recipe_sysroot finished
DEBUG: Executing python function do_fetch
DEBUG: Executing python function base_do_fetch
DEBUG: Fetcher accessed the network with the command git -c core.fsyncobjectfiles=0 ls-remote http://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git 
DEBUG: Running export PSEUDO_DISABLED=1; unset _PYTHON_SYSCONFIGDATA_NAME; export DBUS_SESSION_BUS_ADDRESS="unix:abstract=/tmp/dbus-yuUGQmQkiM,guid=c815551fcc1b2721af7df63f632c1184"; export SSH_AUTH_SOCK="/home/ktuulos/.x2go/C-ktuulos-51-1663832443_stDLXQt_dp32/ssh-agent.PID"; export PATH="/home/ktuulos/yocto/meta-murata-wireless/zeus3/sources/poky/scripts:/home/ktuulos/yocto/meta-murata-wireless/zeus3/build-dir/tmp/work/aarch64-poky-linux/murata-binaries/1.0-r0/recipe-sysroot-native/usr/bin/aarch64-poky-linux:/home/ktuulos/yocto/meta-murata-wireless/zeus3/build-dir/tmp/work/aarch64-poky-linux/murata-binaries/1.0-r0/recipe-sysroot/usr/bin/crossscripts:/home/ktuulos/yocto/meta-murata-wireless/zeus3/build-dir/tmp/work/aarch64-poky-linux/murata-binaries/1.0-r0/recipe-sysroot-native/usr/sbin:/home/ktuulos/yocto/meta-murata-wireless/zeus3/build-dir/tmp/work/aarch64-poky-linux/murata-binaries/1.0-r0/recipe-sysroot-native/usr/bin:/home/ktuulos/yocto/meta-murata-wireless/zeus3/build-dir/tmp/work/aarch64-poky-linux/murata-binaries/1.0-r0/recipe-sysroot-native/sbin:/home/ktuulos/yocto/meta-murata-wireless/zeus3/build-dir/tmp/work/aarch64-poky-linux/murata-binaries/1.0-r0/recipe-sysroot-native/bin:/home/ktuulos/yocto/meta-murata-wireless/zeus3/sources/poky/bitbake/bin:/home/ktuulos/yocto/meta-murata-wireless/zeus3/build-dir/tmp/hosttools"; export HOME="/home/ktuulos"; git -c core.fsyncobjectfiles=0 ls-remote http://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git 
ERROR: Fetcher failure: Unable to resolve 'master' in upstream git repository in git ls-remote output for git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
DEBUG: Python function base_do_fetch finished
DEBUG: Python function do_fetch finished

Build Error

Error: /home/dipankar/linux-imx/oe-init-build-env doesn't exist!
Please run this script in oe-init-build-env's directory.
 
12) Starting Build Now.
-----------------------
 
NOTE: depending on machine type, the build may take 1-7 hours to complete.`

It throws an error and still goes for the build! Is it okay?

10) Verify your selection
-------------------------
 
i.MX Yocto Release              : 5.4.47_2.2.0 GA
Yocto branch                    : zeus
Wireless                        : CYW
fmac version                    : spiga
Target                          : imx6ull14x14evk
NXP i.MX EVK Part Number        : MCIMX6ULL-EVK
meta-murata-wireless Release Tag: imx-zeus-spiga_r1.0
DISTRO                          : fsl-imx-fb
Image                           : core-image-base 
Build Directory                 : build-imx6ullevk
 
Please verify your selection
Do you accept selected configurations ? Y/n: y

Any reply will be great

Publish a CONTRIBUTING.txt to assist contributors

We should have a documentation of some sort to state the criteria and standards of a contribution.

Some of the key points might be:

  1. Is GitHub pull requests allowed or is there a separate mailing list requirement?
  2. Title and description requirements should be clearly stated.
  3. Do contributors need to sign an agreement?

Thanks

1CX M.2 + NXP imx8mm: Can't get PCIe to initialize

Hi,

I'm using the NXP imx8mm and getting pcie error messags during init. My goal is to get the Embedded Artist 1CX M.2 module up and running.

  1. How do I begin to troubleshoot the issue?

  2. Do we need an epdev_on regulator for pcie to work?

  3. How does the ext_osc = <1> in the device tree relate to the message "pcie phy ppl can't be locked" dmesg

[    1.983047] imx6q-pcie 33800000.pcie: 33800000.pcie supply epdev_on not found, using dummy regulator
[    1.992612] OF: PCI: host bridge /pcie@0x33800000 ranges:
[    1.998031] OF: PCI:   No bus range found for /pcie@0x33800000, using [bus 00-ff]
[    2.005529] OF: PCI:    IO 0x1ff80000..0x1ff8ffff -> 0x00000000
[    2.011461] OF: PCI:   MEM 0x18000000..0x1fefffff -> 0x18000000
[    2.017844] imx6q-pcie 33800000.pcie: Initialize PHY with EXT REfCLK!.
[    2.024682] imx6q-pcie 33800000.pcie: PHY Initialization End!.
[    2.051619] imx6q-pcie 33800000.pcie: pcie phy pll can't be locked.
[    2.097900] imx6q-pcie 33800000.pcie: failed to initialize host
[    2.103825] imx6q-pcie 33800000.pcie: unable to add pcie port.

Memory leak in brcmf_wq/mmc0:0001:1 brcmf_sdio_dataworker

Good Morning.
We use imx6ull and 1dx (https://wireless.murata.com/type-1dx.html) from Murata(1DX M.2 Module).
Kernel 4.19.35 from NXP with fmac driver supported by murata.
After few hours we have problem with oom killer caused by Workqueue: brcmf_wq/mmc0:0001:1 brcmf_sdio_dataworker [brcmfmac]:
How can we make it better? Is there any support from murata or someone else?
Thank you very much

[11720.861001] kworker/u2:1 invoked oom-killer: gfp_mask=0x6082c2(GFP_KERNEL|__GFP_HIGHMEM|__GFP_NOWARN|__GFP_ZERO), nodemask=(null), order=0, oom_score_adj=0
[11720.873834] CPU: 0 PID: 718 Comm: kworker/u2:1 Not tainted 4.19.35-1.1.0+g0f9917c #1
[11720.880291] Hardware name: Freescale i.MX6 UltraLite (Device Tree)
[11720.885446] Workqueue: brcmf_wq/mmc0:0001:1 brcmf_sdio_dataworker [brcmfmac]
[11720.891264] [<8010f7a0>] (unwind_backtrace) from [<8010b798>] (show_stack+0x10/0x14)
[11720.897738] [<8010b798>] (show_stack) from [<80a490e8>] (dump_stack+0x78/0x8c)
[11720.903697] [<80a490e8>] (dump_stack) from [<801ce068>] (dump_header.constprop.5+0x64/0x1c8)
[11720.910865] [<801ce068>] (dump_header.constprop.5) from [<801cd200>] (oom_kill_process+0xac/0x510)
[11720.918552] [<801cd200>] (oom_kill_process) from [<801cdc50>] (out_of_memory+0xf0/0x43c)
[11720.925370] [<801cdc50>] (out_of_memory) from [<801d2d3c>] (__alloc_pages_nodemask+0x9c8/0xcac)
[11720.932801] [<801d2d3c>] (__alloc_pages_nodemask) from [<8020199c>] (__vmalloc_node_range+0x114/0x238)
[11720.940841] [<8020199c>] (__vmalloc_node_range) from [<80201d5c>] (__vmalloc_node.constprop.11+0x48/0x50)
[11720.949139] [<80201d5c>] (__vmalloc_node.constprop.11) from [<80201dc4>] (vzalloc+0x2c/0x34)
[11720.956482] [<80201dc4>] (vzalloc) from [<7f062f70>] (brcmf_sdio_dataworker+0x1da8/0x2258 [brcmfmac])
[11720.964616] [<7f062f70>] (brcmf_sdio_dataworker [brcmfmac]) from [<80145f14>] (process_one_work+0x1f0/0x3fc)
[11720.973176] [<80145f14>] (process_one_work) from [<80146c30>] (worker_thread+0x44/0x580)
[11720.979997] [<80146c30>] (worker_thread) from [<8014bb1c>] (kthread+0x148/0x150)
[11720.986124] [<8014bb1c>] (kthread) from [<801010e8>] (ret_from_fork+0x14/0x2c)
[11720.992058] Exception stack(0x83499fb0 to 0x83499ff8)
[11720.995827] 9fa0: 00000000 00000000 00000000 00000000
[11721.002725] 9fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[11721.009619] 9fe0: 00000000 00000000 00000000 00000000 00000013 00000000
[11721.016599] Mem-Info:
[11721.036691] active_anon:2038 inactive_anon:39 isolated_anon:0
active_file:281 inactive_file:260 isolated_file:32
unevictable:0 dirty:0 writeback:0 unstable:0
slab_reclaimable:655 slab_unreclaimable:2327
mapped:557 shmem:82 pagetables:106 bounce:0
free:70031 free_pcp:39 free_cma:63250
[11721.083379] Node 0 active_anon:8152kB inactive_anon:156kB active_file:44kB inactive_file:36kB unevictable:0kB isolated(anon):0kB isolated(file):0kB mapped:20kB dirty:0kB writeback:0kB shmem:328kB writeback_tmp:0kB unstable:0kB all_unreclaimable? yes
[11721.104417] Normal free:282348kB min:30000kB low:37500kB high:45000kB active_anon:8152kB inactive_anon:156kB active_file:44kB inactive_file:36kB unevictable:0kB writepending:0kB present:524288kB managed:503512kB mlocked:0kB kernel_stack:576kB pagetables:424kB bounce:0kB free_pcp:144kB local_pcp:144kB free_cma:253000kB
[11721.131443] lowmem_reserve[]: 0 0 0
[11721.133662] Normal: 4554kB (UME) 4098kB (UMC) 26116kB (UM) 6632kB (MC) 3064kB (M) 12128kB (UM) 7256kB (M) 1512kB (M) 31024kB (UMC) 22048kB (UC) 14096kB (C) 18192kB (U) 116384kB (C) 732768kB (C) = 282356kB
[11721.152125] 105 total pagecache pages
[11721.154496] 0 pages in swap cache
[11721.160161] Swap cache stats: add 0, delete 0, find 0/0
[11721.164790] Free swap = 0kB
[11721.166685] Total swap = 0kB
[11721.168279] 131072 pages RAM
[11721.169863] 0 pages HighMem/MovableOnly
[11721.173246] 5194 pages reserved
[11721.175100] 81920 pages cma reserved
[11721.177459] Tasks state (memory values in pages):
[11721.181496] [ pid ] uid tgid total_vm rss pgtables_bytes swapents oom_score_adj name
[11721.189720] [ 141] 0 141 2616 147 12288 0 -1000 udevd
[11721.198678] [ 506] 0 506 1908 94 14336 0 0 wpa_supplicant
[11721.207089] [ 509] 0 509 424 68 8192 0 0 dhcpcd
[11721.214743] [ 529] 0 529 424 68 8192 0 0 dhcpcd
[11721.232160] [ 544] 999 544 588 41 8192 0 0 dbus-daemon
[11721.240544] [ 548] 0 548 509 25 8192 0 0 dropbear
[11721.248670] [ 553] 998 553 455 34 10240 0 0 rpcbind
[11721.256031] [ 560] 997 560 609 139 10240 0 0 rpc.statd
[11721.269093] [ 567] 0 567 365 18 10240 0 0 atd
[11721.285245] [ 579] 994 579 1595 88 12288 0 0 ntpd
[11721.298341] [ 588] 0 588 375 28 10240 0 0 syslogd
[11721.306091] [ 590] 0 590 1099 778 12288 0 0 klogd
[11721.314633] [ 598] 996 598 747 65 10240 0 0 avahi-daemon
[11721.322497] [ 599] 996 599 716 44 10240 0 0 avahi-daemon
[11721.336580] [ 611] 0 611 1065 52 10240 0 0 ofonod
[11721.351178] [ 619] 0 619 540 120 10240 0 0 crond
[11721.359102] [ 634] 0 634 572 38 10240 0 0 start_getty
[11721.367544] [ 635] 0 635 885 19 10240 0 0 getty
[11721.375166] [ 653] 0 653 594 61 10240 0 0 sh
[11721.382228] [ 706] 0 706 497 26 10240 0 0 ping
[11721.390031] Out of memory: Kill process 590 (klogd) score 6 or sacrifice child
[11721.396164] Killed process 590 (klogd) total-vm:4396kB, anon-rss:3112kB, file-rss:0kB, shmem-rss:0kB

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.