<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: kmemleak during linux boot up in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/kmemleak-during-linux-boot-up/m-p/363487#M51389</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Xiaoqiang &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;it is recommended to use latest 3.10.17 yocto release, since&lt;/P&gt;&lt;P&gt;3.0.x kernels have memory leak issues, as stated on link below:&lt;/P&gt;&lt;P&gt;"defect in 3.0.35 where free memory is depleted by faulty cache&lt;/P&gt;&lt;P&gt;allocations and frees"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.nxp.com/thread/323018"&gt;Long running vpu task with memory leak bug on imx6&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regarding kmemleak usage you can refer below&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://gomathikumar1006.blogspot.ru/2013/10/kmemleak.html" title="http://gomathikumar1006.blogspot.ru/2013/10/kmemleak.html"&gt;Dive into Technical - A beginner's sharing: KMEMLEAK&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.kernel.org/doc/Documentation/kmemleak.txt" title="https://www.kernel.org/doc/Documentation/kmemleak.txt"&gt;https://www.kernel.org/doc/Documentation/kmemleak.txt&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;&lt;P&gt;chip&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;P&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 18 Aug 2014 15:16:55 GMT</pubDate>
    <dc:creator>igorpadykov</dc:creator>
    <dc:date>2014-08-18T15:16:55Z</dc:date>
    <item>
      <title>kmemleak during linux boot up</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/kmemleak-during-linux-boot-up/m-p/363486#M51388</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;Now I am playing on my own designed i.MX6Q custom board and have been running u-boot2009.08 successfully.But I have trouble on starting linux.&lt;/P&gt;&lt;P&gt;Booting the linux kernel take a long time and after login,it's response is too slow.In addition,kmemleak appeared.This is the log:&lt;/P&gt;&lt;P&gt;bootargs:&lt;/P&gt;&lt;P&gt;ipaddr=192.168.2.66 &lt;/P&gt;&lt;P&gt;serverip=192.168.2.130 &lt;/P&gt;&lt;P&gt;netmask=255.255.255.0 &lt;/P&gt;&lt;P&gt;loadaddr=0x10800000 &lt;/P&gt;&lt;P&gt;rd_loadaddr=(0x1300000) &lt;/P&gt;&lt;P&gt;netdev=eth0 &lt;/P&gt;&lt;P&gt;ethprime=FEC0 &lt;/P&gt;&lt;P&gt;uboot=u-boot.bin &lt;/P&gt;&lt;P&gt;kernel=uImage &lt;/P&gt;&lt;P&gt;nfsroot=/srv/rootfs &lt;/P&gt;&lt;P&gt;bootargs_base=setenv bootargs console=ttymxc0,115200 &lt;/P&gt;&lt;P&gt;bootargs_nfs=setenv bootargs $&lt;SPAN __jive_macro_name="bootargs"&gt; root=/dev/nfs ip=dhcp nfsroot=${serveri 
p}:$&lt;SPAN __jive_macro_name="nfsroot"&gt;&lt;/SPAN&gt;,v3,tcp 
bootcmd_net=run bootargs_base bootargs_nfs; tftp uImage; bootm 
bootargs_mmc=setenv bootargs $&lt;/SPAN&gt; ip=dhcp root=/dev/mmcblk0p1 rootwait &lt;/P&gt;&lt;P&gt;bootcmd=run bootcmd_net &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;OL&gt;&lt;OL&gt;&lt;LI level="2" type="ol"&gt;&lt;P&gt;Booting kernel from Legacy Image at 10800000 ...&lt;/P&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;/OL&gt;&lt;P&gt;Image Name: Linux-3.0.35-2666-gbdde708&lt;/P&gt;&lt;P&gt;Image Type: ARM Linux Kernel Image (uncompressed)&lt;/P&gt;&lt;P&gt;Data Size: 3904476 Bytes = 3.7 MB&lt;/P&gt;&lt;P&gt;Load Address: 10008000&lt;/P&gt;&lt;P&gt;Entry Point: 10008000&lt;/P&gt;&lt;P&gt;Verifying Checksum ... OK&lt;/P&gt;&lt;P&gt;Loading Kernel Image ... OK&lt;/P&gt;&lt;P&gt;OK&lt;/P&gt;&lt;P&gt;Starting kernel ...&lt;/P&gt;&lt;P&gt;Uncompressing Linux... done, booting the kernel. &lt;/P&gt;&lt;P&gt;Linux version 3.0.35-2666-gbdde708 (root@lab-linux) (gcc version 4.6.2 20110630 (prerelease) (Freescale MAD -- Linaro 2011.07 -- Built at 2011/08/10 09:20) ) #44 SMP PREEMPT Mon Aug 18 12:31:36 CST 2014 &lt;/P&gt;&lt;P&gt;CPU: ARMv7 Processor  revision 10 (ARMv7), cr=10c53c7d &lt;/P&gt;&lt;P&gt;CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache &lt;/P&gt;&lt;P&gt;Machine: Freescale i.MX 6Quad/DualLite/Solo Sabre-SD Board &lt;/P&gt;&lt;P&gt;Ignoring unrecognised tag 0x54410008 &lt;/P&gt;&lt;P&gt;Memory policy: ECC disabled, Data cache writealloc &lt;/P&gt;&lt;P&gt;CPU identified as i.MX6Q, silicon rev 1.2 &lt;/P&gt;&lt;P&gt;PERCPU: Embedded 7 pages/cpu @8c80e000 s5440 r8192 d15040 u32768 &lt;/P&gt;&lt;P&gt;Built 1 zonelists in Zone order, mobility grouping on. Total pages: 454656 &lt;/P&gt;&lt;P&gt;Kernel command line: console=ttymxc0,115200 root=/dev/nfs ip=dhcp nfsroot=192.168.2.130:/srv/rootfs,v3,tcp &lt;/P&gt;&lt;P&gt;PID hash table entries: 4096 (order: 2, 16384 bytes) &lt;/P&gt;&lt;P&gt;Dentry cache hash table entries: 262144 (order: 8, 1048576 bytes) &lt;/P&gt;&lt;P&gt;Inode-cache hash table entries: 131072 (order: 7, 524288 bytes) &lt;/P&gt;&lt;P&gt;Memory: 512MB 1280MB = 1792MB total &lt;/P&gt;&lt;P&gt;Memory: 1805240k/1805240k available, 291912k reserved, 360448K highmem &lt;/P&gt;&lt;P&gt;Virtual kernel memory layout: &lt;/P&gt;&lt;P&gt;vector : 0xffff0000 - 0xffff1000 ( 4 kB) &lt;/P&gt;&lt;P&gt;fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB) &lt;/P&gt;&lt;P&gt;DMA : 0xf4600000 - 0xffe00000 ( 184 MB) &lt;/P&gt;&lt;P&gt;vmalloc : 0xea800000 - 0xf2000000 ( 120 MB) &lt;/P&gt;&lt;P&gt;lowmem : 0x80000000 - 0xea000000 (1696 MB) &lt;/P&gt;&lt;P&gt;pkmap : 0x7fe00000 - 0x80000000 ( 2 MB) &lt;/P&gt;&lt;P&gt;modules : 0x7f000000 - 0x7fe00000 ( 14 MB) &lt;/P&gt;&lt;P&gt;.init : 0x80008000 - 0x80045000 ( 244 kB) &lt;/P&gt;&lt;P&gt;.text : 0x80045000 - 0x80aaa0cc (10645 kB) &lt;/P&gt;&lt;P&gt;.data : 0x80aac000 - 0x80b10300 ( 401 kB) &lt;/P&gt;&lt;P&gt;.bss : 0x80b10324 - 0x80b5e70c ( 313 kB) &lt;/P&gt;&lt;P&gt;SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 &lt;/P&gt;&lt;P&gt;Preemptible hierarchical RCU implementation. &lt;/P&gt;&lt;P&gt;NR_IRQS:624 &lt;/P&gt;&lt;P&gt;MXC GPIO hardware &lt;/P&gt;&lt;P&gt;sched_clock: 32 bits at 3000kHz, resolution 333ns, wraps every 1431655ms &lt;/P&gt;&lt;P&gt;arm_max_freq=800MHz &lt;/P&gt;&lt;P&gt;MXC_Early serial console at MMIO 0x2020000 (options '115200') &lt;/P&gt;&lt;P&gt;bootconsole  enabled &lt;/P&gt;&lt;P&gt;Console: colour dummy device 80x30 &lt;/P&gt;&lt;P&gt;Calibrating delay loop... 1581.05 BogoMIPS (lpj=7905280) &lt;/P&gt;&lt;P&gt;pid_max: default: 32768 minimum: 301 &lt;/P&gt;&lt;P&gt;Mount-cache hash table entries: 512 &lt;/P&gt;&lt;P&gt;CPU: Testing write buffer coherency: ok &lt;/P&gt;&lt;P&gt;hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available &lt;/P&gt;&lt;P&gt;CPU1: Booted secondary processor &lt;/P&gt;&lt;P&gt;CPU2: Booted secondary processor &lt;/P&gt;&lt;P&gt;CPU3: Booted secondary processor &lt;/P&gt;&lt;P&gt;Brought up 4 CPUs &lt;/P&gt;&lt;P&gt;SMP: Total of 4 processors activated (6324.22 BogoMIPS). &lt;/P&gt;&lt;P&gt;print_constraints: dummy: &lt;/P&gt;&lt;P&gt;NET: Registered protocol family 16 &lt;/P&gt;&lt;P&gt;print_constraints: vddpu: 725  at 0 &lt;/P&gt;&lt;P&gt;mxs-dma mxs-dma-apbh: initialized &lt;/P&gt;&lt;P&gt;print_constraints: SPKVDD: 4200 mV &lt;/P&gt;&lt;P&gt;print_constraints: vmmc: 3300 mV &lt;/P&gt;&lt;P&gt;vgaarb: loaded &lt;/P&gt;&lt;P&gt;SCSI subsystem initialized &lt;/P&gt;&lt;P&gt;spi_imx imx6q-ecspi.0: probed &lt;/P&gt;&lt;P&gt;usbcore: registered new interface driver usbfs &lt;/P&gt;&lt;P&gt;usbcore: registered new interface driver hub &lt;/P&gt;&lt;P&gt;usbcore: registered new device driver usb &lt;/P&gt;&lt;P&gt;Freescale USB OTG Driver loaded, $Revision: 1.55 $ &lt;/P&gt;&lt;P&gt;mc_pfuze 1-0008: recv failed!:-5,80 &lt;/P&gt;&lt;P&gt;mc_pfuze: probe of 1-0008 failed with error -1 &lt;/P&gt;&lt;P&gt;imx-ipuv3 imx-ipuv3.0: IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7) &lt;/P&gt;&lt;P&gt;imx-ipuv3 imx-ipuv3.1: IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7) &lt;/P&gt;&lt;P&gt;mxc_mipi_csi2 mxc_mipi_csi2: i.MX MIPI CSI2 driver probed &lt;/P&gt;&lt;P&gt;mxc_mipi_csi2 mxc_mipi_csi2: i.MX MIPI CSI2 dphy version is 0x3130302a &lt;/P&gt;&lt;P&gt;MIPI CSI2 driver module loaded &lt;/P&gt;&lt;P&gt;Advanced Linux Sound Architecture Driver Version 1.0.24. &lt;/P&gt;&lt;P&gt;Bluetooth: Core ver 2.16 &lt;/P&gt;&lt;P&gt;NET: Registered protocol family 31 &lt;/P&gt;&lt;P&gt;Bluetooth: HCI device and connection manager initialized &lt;/P&gt;&lt;P&gt;Bluetooth: HCI socket layer initialized &lt;/P&gt;&lt;P&gt;Bluetooth: L2CAP socket layer initialized &lt;/P&gt;&lt;P&gt;Bluetooth: SCO socket layer initialized &lt;/P&gt;&lt;P&gt;cfg80211: Calling CRDA to update world regulatory domain &lt;/P&gt;&lt;P&gt;max17135 2-0048: PMIC MAX17135 for eInk display &lt;/P&gt;&lt;P&gt;i2c-core: driver  using legacy suspend method &lt;/P&gt;&lt;P&gt;i2c-core: driver  using legacy resume method &lt;/P&gt;&lt;P&gt;Switching to clocksource mxc_timer1 &lt;/P&gt;&lt;P&gt;NET: Registered protocol family 2 &lt;/P&gt;&lt;P&gt;IP route cache hash table entries: 65536 (order: 6, 262144 bytes) &lt;/P&gt;&lt;P&gt;TCP established hash table entries: 262144 (order: 9, 2097152 bytes) &lt;/P&gt;&lt;P&gt;TCP bind hash table entries: 65536 (order: 7, 786432 bytes) &lt;/P&gt;&lt;P&gt;TCP: Hash tables configured (established 262144 bind 65536) &lt;/P&gt;&lt;P&gt;TCP reno registered &lt;/P&gt;&lt;P&gt;UDP hash table entries: 1024 (order: 3, 32768 bytes) &lt;/P&gt;&lt;P&gt;UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes) &lt;/P&gt;&lt;P&gt;NET: Registered protocol family 1 &lt;/P&gt;&lt;P&gt;RPC: Registered named UNIX socket transport module. &lt;/P&gt;&lt;P&gt;RPC: Registered udp transport module. &lt;/P&gt;&lt;P&gt;RPC: Registered tcp transport module. &lt;/P&gt;&lt;P&gt;RPC: Registered tcp NFSv4.1 backchannel transport module. &lt;/P&gt;&lt;P&gt;PMU: registered new PMU device of type 0 &lt;/P&gt;&lt;P&gt;Static Power Management for Freescale i.MX6 &lt;/P&gt;&lt;P&gt;wait mode is enabled for i.MX6 &lt;/P&gt;&lt;P&gt;cpaddr = ea880000 suspend_iram_base=ea8f0000 &lt;/P&gt;&lt;P&gt;PM driver module loaded &lt;/P&gt;&lt;P&gt;iMX6 PCIe PCIe RC mode imx_pcie_pltfm_probe entering. &lt;/P&gt;&lt;P&gt;PCIE: imx_pcie_pltfm_probe start link up. &lt;/P&gt;&lt;P&gt;IMX PCIe port: link up. &lt;/P&gt;&lt;P&gt;PCI: bus0: Fast back to back transfers disabled &lt;/P&gt;&lt;P&gt;PCI: bus1: Fast back to back transfers disabled &lt;/P&gt;&lt;P&gt;PCI: bus2: Fast back to back transfers disabled &lt;/P&gt;&lt;P&gt;PCI: bus3: Fast back to back transfers disabled &lt;/P&gt;&lt;P&gt;PCI: bus4: Fast back to back transfers enabled &lt;/P&gt;&lt;P&gt;PCI: bus5: Fast back to back transfers enabled &lt;/P&gt;&lt;P&gt;PCI: bus6: Fast back to back transfers enabled &lt;/P&gt;&lt;P&gt;PCI: bus7: Fast back to back transfers enabled &lt;/P&gt;&lt;P&gt;PCI: bus8: Fast back to back transfers enabled &lt;/P&gt;&lt;P&gt;pci 0000:00:00.0: BAR 0: assigned  &lt;/P&gt;&lt;P&gt;pci 0000:00:00.0: BAR 0: set to  (PCI address ) &lt;/P&gt;&lt;P&gt;pci 0000:00:00.0: BAR 8: assigned  &lt;/P&gt;&lt;P&gt;pci 0000:00:00.0: BAR 6: assigned  &lt;/P&gt;&lt;P&gt;pci 0000:01:00.0: BAR 0: assigned  &lt;/P&gt;&lt;P&gt;pci 0000:01:00.0: BAR 0: set to  (PCI address ) &lt;/P&gt;&lt;P&gt;pci 0000:03:00.0: PCI bridge to  &lt;/P&gt;&lt;P&gt;pci 0000:03:00.0: bridge window  &lt;/P&gt;&lt;P&gt;pci 0000:03:00.0: bridge window  &lt;/P&gt;&lt;P&gt;pci 0000:03:00.0: bridge window  &lt;/P&gt;&lt;P&gt;pci 0000:02:01.0: PCI bridge to  &lt;/P&gt;&lt;P&gt;pci 0000:02:01.0: bridge window  &lt;/P&gt;&lt;P&gt;pci 0000:02:01.0: bridge window  &lt;/P&gt;&lt;P&gt;pci 0000:02:01.0: bridge window  &lt;/P&gt;&lt;P&gt;pci 0000:02:04.0: PCI bridge to  &lt;/P&gt;&lt;P&gt;pci 0000:02:04.0: bridge window  &lt;/P&gt;&lt;P&gt;pci 0000:02:04.0: bridge window  &lt;/P&gt;&lt;P&gt;pci 0000:02:04.0: bridge window  &lt;/P&gt;&lt;P&gt;pci 0000:02:05.0: PCI bridge to  &lt;/P&gt;&lt;P&gt;pci 0000:02:05.0: bridge window  &lt;/P&gt;&lt;P&gt;pci 0000:02:05.0: bridge window  &lt;/P&gt;&lt;P&gt;pci 0000:02:05.0: bridge window  &lt;/P&gt;&lt;P&gt;pci 0000:02:07.0: PCI bridge to  &lt;/P&gt;&lt;P&gt;pci 0000:02:07.0: bridge window  &lt;/P&gt;&lt;P&gt;pci 0000:02:07.0: bridge window  &lt;/P&gt;&lt;P&gt;pci 0000:02:07.0: bridge window  &lt;/P&gt;&lt;P&gt;pci 0000:02:09.0: PCI bridge to  &lt;/P&gt;&lt;P&gt;pci 0000:02:09.0: bridge window  &lt;/P&gt;&lt;P&gt;pci 0000:02:09.0: bridge window  &lt;/P&gt;&lt;P&gt;pci 0000:02:09.0: bridge window  &lt;/P&gt;&lt;P&gt;pci 0000:01:00.0: PCI bridge to  &lt;/P&gt;&lt;P&gt;pci 0000:01:00.0: bridge window  &lt;/P&gt;&lt;P&gt;pci 0000:01:00.0: bridge window  &lt;/P&gt;&lt;P&gt;pci 0000:01:00.0: bridge window  &lt;/P&gt;&lt;P&gt;pci 0000:00:00.0: PCI bridge to  &lt;/P&gt;&lt;P&gt;pci 0000:00:00.0: bridge window  &lt;/P&gt;&lt;P&gt;pci 0000:00:00.0: bridge window  &lt;/P&gt;&lt;P&gt;pci 0000:00:00.0: bridge window  &lt;/P&gt;&lt;P&gt;PCI: enabling device 0000:01:00.0 (0140 -&amp;gt; 0143) &lt;/P&gt;&lt;P&gt;PCI: enabling device 0000:02:01.0 (0140 -&amp;gt; 0143) &lt;/P&gt;&lt;P&gt;PCI: enabling device 0000:03:00.0 (0140 -&amp;gt; 0143) &lt;/P&gt;&lt;P&gt;PCI: enabling device 0000:02:04.0 (0140 -&amp;gt; 0143) &lt;/P&gt;&lt;P&gt;PCI: enabling device 0000:02:05.0 (0140 -&amp;gt; 0143) &lt;/P&gt;&lt;P&gt;PCI: enabling device 0000:02:07.0 (0140 -&amp;gt; 0143) &lt;/P&gt;&lt;P&gt;PCI: enabling device 0000:02:09.0 (0140 -&amp;gt; 0143) &lt;/P&gt;&lt;P&gt;IMX usb wakeup probe &lt;/P&gt;&lt;P&gt;add wake up source irq 75 &lt;/P&gt;&lt;P&gt;IMX usb wakeup probe &lt;/P&gt;&lt;P&gt;cpu regulator mode:ldo_enable &lt;/P&gt;&lt;P&gt;i.MXC CPU frequency driver &lt;/P&gt;&lt;P&gt;highmem bounce pool size: 64 pages &lt;/P&gt;&lt;P&gt;JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc. &lt;/P&gt;&lt;P&gt;msgmni has been set to 2821 &lt;/P&gt;&lt;P&gt;alg: No test for stdrng (krng) &lt;/P&gt;&lt;P&gt;io scheduler noop registered &lt;/P&gt;&lt;P&gt;io scheduler deadline registered &lt;/P&gt;&lt;P&gt;io scheduler cfq registered (default) &lt;/P&gt;&lt;P&gt;mxc_mipi_dsi mxc_mipi_dsi: i.MX MIPI DSI driver probed &lt;/P&gt;&lt;P&gt;MIPI DSI driver module loaded &lt;/P&gt;&lt;P&gt;mxc_sdc_fb mxc_sdc_fb.0: register mxc display driver ldb &lt;/P&gt;&lt;P&gt;&lt;U&gt;regulator&lt;/U&gt;get: get() with no identifier &lt;/P&gt;&lt;P&gt;imx-ipuv3 imx-ipuv3.1: IPU DMFC DP HIGH RESOLUTION: 1(0,1), 5B(2~5), 5F(6,7) &lt;/P&gt;&lt;P&gt;Console: switching to colour frame buffer device 128x48 &lt;/P&gt;&lt;P&gt;mxc_sdc_fb mxc_sdc_fb.1: register mxc display driver ldb &lt;/P&gt;&lt;P&gt;mxc_sdc_fb mxc_sdc_fb.2: register mxc display driver lcd &lt;/P&gt;&lt;P&gt;mxc_sdc_fb mxc_sdc_fb.3: register mxc display driver ldb &lt;/P&gt;&lt;P&gt;mxc_sdc_fb mxc_sdc_fb.3: ipu1-di0 already in use &lt;/P&gt;&lt;P&gt;mxc_sdc_fb: probe of mxc_sdc_fb.3 failed with error -16 &lt;/P&gt;&lt;P&gt;imx-sdma imx-sdma: loaded firmware 1.1 &lt;/P&gt;&lt;P&gt;imx-sdma imx-sdma: initialized &lt;/P&gt;&lt;P&gt;Serial: IMX driver &lt;/P&gt;&lt;P&gt;imx-uart.2: ttymxc2 at MMIO 0x21ec000 (irq = 60) is a IMX &lt;/P&gt;&lt;P&gt;imx-uart.0: ttymxc0 at MMIO 0x2020000 (irq = 58) is a IMX &lt;/P&gt;&lt;P&gt;console  enabled, bootconsole disabled &lt;/P&gt;&lt;P&gt;console  enabled, bootconsole disabled &lt;/P&gt;&lt;P&gt;loop: module loaded &lt;/P&gt;&lt;P&gt;No sata disk. &lt;/P&gt;&lt;P&gt;m25p80 spi0.0: found m25p32, expected sst25vf016b &lt;/P&gt;&lt;P&gt;m25p80 spi0.0: m25p32 (4096 Kbytes) &lt;/P&gt;&lt;P&gt;Creating 2 MTD partitions on "m25p80": &lt;/P&gt;&lt;P&gt;0x000000000000-0x000000100000 : "bootloader" &lt;/P&gt;&lt;P&gt;0x000000100000-0x000000400000 : "kernel" &lt;/P&gt;&lt;P&gt;GPMI NAND driver registered. (IMX) &lt;/P&gt;&lt;P&gt;vcan: Virtual CAN interface driver &lt;/P&gt;&lt;P&gt;CAN device driver interface &lt;/P&gt;&lt;P&gt;flexcan netdevice driver &lt;/P&gt;&lt;P&gt;FEC Ethernet Driver &lt;/P&gt;&lt;P&gt;fec_enet_mii_bus: probed &lt;/P&gt;&lt;P&gt;ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver &lt;/P&gt;&lt;P&gt;fsl-ehci fsl-ehci.0: Freescale On-Chip EHCI Host Controller &lt;/P&gt;&lt;P&gt;fsl-ehci fsl-ehci.0: new USB bus registered, assigned bus number 1 &lt;/P&gt;&lt;P&gt;fsl-ehci fsl-ehci.0: irq 75, io base 0x02184000 &lt;/P&gt;&lt;P&gt;fsl-ehci fsl-ehci.0: USB 2.0 started, EHCI 1.00 &lt;/P&gt;&lt;P&gt;hub 1-0:1.0: USB hub found &lt;/P&gt;&lt;P&gt;hub 1-0:1.0: 1 port detected &lt;/P&gt;&lt;P&gt;add wake up source irq 72 &lt;/P&gt;&lt;P&gt;fsl-ehci fsl-ehci.1: Freescale On-Chip EHCI Host Controller &lt;/P&gt;&lt;P&gt;fsl-ehci fsl-ehci.1: new USB bus registered, assigned bus number 2 &lt;/P&gt;&lt;P&gt;fsl-ehci fsl-ehci.1: irq 72, io base 0x02184200 &lt;/P&gt;&lt;P&gt;fsl-ehci fsl-ehci.1: USB 2.0 started, EHCI 1.00 &lt;/P&gt;&lt;P&gt;hub 2-0:1.0: USB hub found &lt;/P&gt;&lt;P&gt;hub 2-0:1.0: 1 port detected &lt;/P&gt;&lt;P&gt;Initializing USB Mass Storage driver... &lt;/P&gt;&lt;P&gt;usbcore: registered new interface driver usb-storage &lt;/P&gt;&lt;P&gt;USB Mass Storage support registered. &lt;/P&gt;&lt;P&gt;ARC USBOTG Device Controller driver (1 August 2005) &lt;/P&gt;&lt;P&gt;mousedev: PS/2 mouse device common for all mice &lt;/P&gt;&lt;P&gt;input: gpio-keys as /devices/platform/gpio-keys/input/input0 &lt;/P&gt;&lt;P&gt;input: max11801_ts as /devices/platform/imx-i2c.1/i2c-1/1-0048/input/input1 &lt;/P&gt;&lt;P&gt;egalax_ts 1-0004: egalax_ts: failed to read firmware version &lt;/P&gt;&lt;P&gt;egalax_ts: probe of 1-0004 failed with error -5 &lt;/P&gt;&lt;P&gt;egalax_ts 2-0004: egalax_ts: failed to read firmware version &lt;/P&gt;&lt;P&gt;egalax_ts: probe of 2-0004 failed with error -5 &lt;/P&gt;&lt;P&gt;usb 2-1: new full speed USB device number 2 using fsl-ehci &lt;/P&gt;&lt;P&gt;elan - Read Hello Packet Failed &lt;/P&gt;&lt;P&gt;elan-touch: probe of 2-0010 failed with error -22 &lt;/P&gt;&lt;P&gt;i2c-core: driver  using legacy suspend method &lt;/P&gt;&lt;P&gt;i2c-core: driver  using legacy resume method &lt;/P&gt;&lt;P&gt;snvs_rtc snvs_rtc.0: rtc core: registered snvs_rtc as rtc0 &lt;/P&gt;&lt;P&gt;i2c /dev entries driver &lt;/P&gt;&lt;P&gt;Linux video capture interface: v2.00 &lt;/P&gt;&lt;P&gt;mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video16 &lt;/P&gt;&lt;P&gt;mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video17 &lt;/P&gt;&lt;P&gt;mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video18 &lt;/P&gt;&lt;P&gt;mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video19 &lt;/P&gt;&lt;P&gt;mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video20 &lt;/P&gt;&lt;P&gt;usb 2-1: device descriptor read/64, error -71 &lt;/P&gt;&lt;P&gt;mag3110 2-000e: check mag3110 chip ID &lt;/P&gt;&lt;P&gt;mag3110 2-000e: read chip ID 0xfffffffb is not equal to 0xc4! &lt;/P&gt;&lt;P&gt;mag3110: probe of 2-000e failed with error -22 &lt;/P&gt;&lt;P&gt;i2c-core: driver  using legacy suspend method &lt;/P&gt;&lt;P&gt;i2c-core: driver  using legacy resume method &lt;/P&gt;&lt;P&gt;mma8451 0-001c: read chip ID 0x1 is not equal to 0x1a or 0x2a! &lt;/P&gt;&lt;P&gt;mma8451: probe of 0-001c failed with error -22 &lt;/P&gt;&lt;P&gt;imx2-wdt imx2-wdt.0: IMX2+ Watchdog Timer enabled. timeout=60s (nowayout=1) &lt;/P&gt;&lt;P&gt;Bluetooth: Virtual HCI driver ver 1.3 &lt;/P&gt;&lt;P&gt;Bluetooth: HCI UART driver ver 2.2 &lt;/P&gt;&lt;P&gt;Bluetooth: HCIATH3K protocol initialized &lt;/P&gt;&lt;P&gt;Bluetooth: Generic Bluetooth USB driver ver 0.6 &lt;/P&gt;&lt;P&gt;usbcore: registered new interface driver btusb &lt;/P&gt;&lt;P&gt;mxc_vdoa mxc_vdoa: i.MX Video Data Order Adapter(VDOA) driver probed &lt;/P&gt;&lt;P&gt;VPU initialized &lt;/P&gt;&lt;P&gt;mxc_asrc registered &lt;/P&gt;&lt;P&gt;Galcore version 4.6.9.6622 &lt;/P&gt;&lt;P&gt;Thermal calibration data is 0x5544d069 &lt;/P&gt;&lt;P&gt;Thermal sensor with ratio = 175 &lt;/P&gt;&lt;P&gt;Anatop Thermal registered as thermal_zone0 &lt;/P&gt;&lt;P&gt;anatop_thermal_probe: default cooling device is cpufreq! &lt;/P&gt;&lt;P&gt;usbcore: registered new interface driver usbhid &lt;/P&gt;&lt;P&gt;usbhid: USB HID core driver &lt;/P&gt;&lt;P&gt;usbcore: registered new interface driver snd-usb-audio &lt;/P&gt;&lt;P&gt;mxc_hdmi_soc mxc_hdmi_soc.0: MXC HDMI Audio &lt;/P&gt;&lt;P&gt;Cirrus Logic CS42888 ALSA SoC Codec Driver &lt;/P&gt;&lt;P&gt;i2c-core: driver  using legacy suspend method &lt;/P&gt;&lt;P&gt;i2c-core: driver  using legacy resume method &lt;/P&gt;&lt;P&gt;imx-hdmi-soc-dai imx-hdmi-soc-dai.0: Failed: Load HDMI-video first. &lt;/P&gt;&lt;P&gt;wm8962 0-001a: Failed to get supply 'DCVDD': -19 &lt;/P&gt;&lt;P&gt;wm8962 0-001a: Failed to request supplies: -19 &lt;/P&gt;&lt;P&gt;wm8962 0-001a: asoc: failed to probe CODEC wm8962.0-001a: -19 &lt;/P&gt;&lt;P&gt;asoc: failed to instantiate card wm8962-audio: -19 &lt;/P&gt;&lt;P&gt;imx_3stack asoc driver &lt;/P&gt;&lt;P&gt;Initialize HDMI-audio failed. Load HDMI-video first! &lt;/P&gt;&lt;P&gt;ALSA device list: &lt;/P&gt;&lt;P&gt;No soundcards found. &lt;/P&gt;&lt;P&gt;NET: Registered protocol family 26 &lt;/P&gt;&lt;P&gt;TCP cubic registered &lt;/P&gt;&lt;P&gt;NET: Registered protocol family 17 &lt;/P&gt;&lt;P&gt;can: controller area network core (rev 20090105 abi 8) &lt;/P&gt;&lt;P&gt;NET: Registered protocol family 29 &lt;/P&gt;&lt;P&gt;can: raw protocol (rev 20090105) &lt;/P&gt;&lt;P&gt;can: broadcast manager protocol (rev 20090105 t) &lt;/P&gt;&lt;P&gt;Bluetooth: RFCOMM TTY layer initialized &lt;/P&gt;&lt;P&gt;Bluetooth: RFCOMM socket layer initialized &lt;/P&gt;&lt;P&gt;Bluetooth: RFCOMM ver 1.11 &lt;/P&gt;&lt;P&gt;Bluetooth: BNEP (Ethernet Emulation) ver 1.3 &lt;/P&gt;&lt;P&gt;Bluetooth: BNEP filters: protocol multicast &lt;/P&gt;&lt;P&gt;Bluetooth: HIDP (Human Interface Emulation) ver 1.2 &lt;/P&gt;&lt;P&gt;lib80211: common routines for IEEE802.11 drivers &lt;/P&gt;&lt;P&gt;VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4 &lt;/P&gt;&lt;P&gt;Bus freq driver module loaded &lt;/P&gt;&lt;P&gt;Bus freq driver Enabled &lt;/P&gt;&lt;P&gt;mxc_dvfs_core_probe &lt;/P&gt;&lt;P&gt;DVFS driver module loaded &lt;/P&gt;&lt;P&gt;usb 2-1: device descriptor read/64, error -71 &lt;/P&gt;&lt;P&gt;kmemleak: Kernel memory leak detector initialized &lt;/P&gt;&lt;P&gt;kmemleak: Automatic memory scanning thread started &lt;/P&gt;&lt;P&gt;regulator_init_complete: vmmc: incomplete constraints, leaving on &lt;/P&gt;&lt;P&gt;regulator_init_complete: SPKVDD: incomplete constraints, leaving on &lt;/P&gt;&lt;P&gt;snvs_rtc snvs_rtc.0: setting system clock to 1970-01-01 00:00:00 UTC (0) &lt;/P&gt;&lt;P&gt;eth0: Freescale FEC PHY driver  (mii_bus:phy_addr=1:00, irq=-1) &lt;/P&gt;&lt;P&gt;usb 2-1: new full speed USB device number 3 using fsl-ehci &lt;/P&gt;&lt;P&gt;usb 2-1: device descriptor read/64, error -71 &lt;/P&gt;&lt;P&gt;usb 2-1: device descriptor read/64, error -71 &lt;/P&gt;&lt;P&gt;usb 2-1: new full speed USB device number 4 using fsl-ehci &lt;/P&gt;&lt;P&gt;usb 2-1: device not accepting address 4, error -71 &lt;/P&gt;&lt;P&gt;usb 2-1: new full speed USB device number 5 using fsl-ehci &lt;/P&gt;&lt;P&gt;usb 2-1: device not accepting address 5, error -71 &lt;/P&gt;&lt;P&gt;hub 2-0:1.0: unable to enumerate USB device on port 1 &lt;/P&gt;&lt;P&gt;PHY: 1:00 - Link is Up - 100/Full &lt;/P&gt;&lt;P&gt;Sending DHCP requests ., &lt;/P&gt;&lt;P&gt;. OK &lt;/P&gt;&lt;P&gt;IP-Config: Got DHCP answer from 0.0.0.0, my address is 192.168.2.117 &lt;/P&gt;&lt;P&gt;IP-Config: Complete: &lt;/P&gt;&lt;P&gt;device=eth0, addr=192.168.2.117, mask=255.255.255.0, gw=192.168.2.10, &lt;/P&gt;&lt;P&gt;host=192.168.2.117, domain=, nis-domain=(none), &lt;/P&gt;&lt;P&gt;bootserver=0.0.0.0, rootserver=192.168.2.130, rootpath=, mtu=576 &lt;/P&gt;&lt;P&gt;VFS: Mounted root (nfs filesystem) on device 0:12. &lt;/P&gt;&lt;P&gt;Freeing init memory: 244K &lt;/P&gt;&lt;P&gt;kmemleak: 1 new suspected memory leaks (see /sys/kernel/debug/kmemleak) &lt;/P&gt;&lt;P&gt;note: it stopped here for a long time&lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 not responding, still trying &lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 not responding, still trying &lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 not responding, still trying &lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 not responding, still trying &lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 not responding, still trying &lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 not responding, still trying &lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 not responding, still trying &lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 not responding, still trying &lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 not responding, still trying &lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 not responding, still trying &lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 not responding, still trying &lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 not responding, still trying &lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 not responding, still trying &lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 not responding, still trying &lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 not responding, still trying &lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 OK &lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 OK &lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 OK &lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 OK &lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 OK &lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 OK &lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 OK &lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 OK &lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 OK &lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 OK &lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 OK &lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 OK &lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 OK &lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 OK &lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 OK &lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 not responding, still trying &lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 not responding, still trying &lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 not responding, still trying &lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 not responding, still trying &lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 not responding, still trying &lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 not responding, still trying &lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 not responding, still trying &lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 not responding, still trying &lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 not responding, still trying &lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 not responding, still trying &lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 not responding, still trying &lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 not responding, still trying &lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 not responding, still trying &lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 not responding, still trying &lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 not responding, still trying &lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 not responding, still trying &lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 OK &lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 OK &lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 OK &lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 OK &lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 OK &lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 OK &lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 OK &lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 OK &lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 OK &lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 OK &lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 OK &lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 OK &lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 OK &lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 OK &lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 OK &lt;/P&gt;&lt;P&gt;nfs: server 192.168.2.130 OK &lt;/P&gt;&lt;P&gt;starting pid 1413, tty '': '/etc/rc.d/rcS' &lt;/P&gt;&lt;P&gt;Mounting /proc and /sys &lt;/P&gt;&lt;P&gt;Starting the hotplug events dispatcher udevd &lt;/P&gt;&lt;P&gt;udevd (1460): /proc/1460/oom_adj is deprecated, please use /proc/1460/oom_score_adj instead. &lt;/P&gt;&lt;P&gt;Synthesizing initial hotplug events &lt;/P&gt;&lt;P&gt;Setting the hostname to freescale &lt;/P&gt;&lt;P&gt;Mounting filesystems &lt;/P&gt;&lt;P&gt;Booted NFS, not relocating: /tmp /var &lt;/P&gt;&lt;P&gt;mount: mounting usbfs on /proc/bus/usb failed: No such file or directory &lt;/P&gt;&lt;P&gt;starting pid 2729, tty '': '/etc/rc.d/rc_gpu.S' &lt;/P&gt;&lt;P&gt;starting pid 2736, tty '': '/etc/rc.d/rc_mxc.S' &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;arm-none-linux-gnueabi-gcc (Freescale MAD -- Linaro 2011.07 -- Built at 2011/08/10 09:20) 4.6.2 20110630 (prerelease) &lt;/P&gt;&lt;P&gt;root filesystem built on Mon, 11 Aug 2014 14:22:50 +0800 &lt;/P&gt;&lt;P&gt;Freescale Semiconductor, Inc. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;freescale login: kmemleak: 3 new suspected memory leaks (see /sys/kernel/debug/kmemleak) &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;arm-none-linux-gnueabi-gcc (Freescale MAD -- Linaro 2011.07 -- Built at 2011/08/10 09:20) 4.6.2 20110630 (prerelease) &lt;/P&gt;&lt;P&gt;root filesystem built on Mon, 11 Aug 2014 14:22:50 +0800 &lt;/P&gt;&lt;P&gt;Freescale Semiconductor, Inc. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;freescale login: root &lt;/P&gt;&lt;P&gt;login[2738]: root login on 'ttymxc0' &lt;/P&gt;&lt;P&gt;root@freescale ~$ mount -t debugfs nodev /sys/kernel/debug/ &lt;/P&gt;&lt;P&gt;root@freescale ~$ echo scan /sys/kernel/debug/kmemleak &lt;/P&gt;&lt;P&gt;scan /sys/kernel/debug/kmemleak &lt;/P&gt;&lt;P&gt;root@freescale ~$ cat /sys/kernel/debug/kmemleak &lt;/P&gt;&lt;P&gt;unreferenced object 0xe412e3c0 (size 64): &lt;/P&gt;&lt;P&gt;comm "swapper", pid 1, jiffies 4294937508 (age 859.550s) &lt;/P&gt;&lt;P&gt;hex dump (first 32 bytes): &lt;/P&gt;&lt;P&gt;2c a2 9d e9 2c a2 9d e9 fc 49 a1 80 3c 00 00 00 ,...,....I..] 0xffffffff &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I don't know why there is memory leaks and how to find the key by the file '/sys/kernel/debug/kmemleak'.&lt;/P&gt;&lt;P&gt;Any reply will be appreciated!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best Regargs&lt;/P&gt;&lt;P&gt;Xiaoqiang&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 18 Aug 2014 06:00:06 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/kmemleak-during-linux-boot-up/m-p/363486#M51388</guid>
      <dc:creator>xiaoqiangyang</dc:creator>
      <dc:date>2014-08-18T06:00:06Z</dc:date>
    </item>
    <item>
      <title>Re: kmemleak during linux boot up</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/kmemleak-during-linux-boot-up/m-p/363487#M51389</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Xiaoqiang &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;it is recommended to use latest 3.10.17 yocto release, since&lt;/P&gt;&lt;P&gt;3.0.x kernels have memory leak issues, as stated on link below:&lt;/P&gt;&lt;P&gt;"defect in 3.0.35 where free memory is depleted by faulty cache&lt;/P&gt;&lt;P&gt;allocations and frees"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.nxp.com/thread/323018"&gt;Long running vpu task with memory leak bug on imx6&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regarding kmemleak usage you can refer below&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://gomathikumar1006.blogspot.ru/2013/10/kmemleak.html" title="http://gomathikumar1006.blogspot.ru/2013/10/kmemleak.html"&gt;Dive into Technical - A beginner's sharing: KMEMLEAK&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.kernel.org/doc/Documentation/kmemleak.txt" title="https://www.kernel.org/doc/Documentation/kmemleak.txt"&gt;https://www.kernel.org/doc/Documentation/kmemleak.txt&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;&lt;P&gt;chip&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;P&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 18 Aug 2014 15:16:55 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/kmemleak-during-linux-boot-up/m-p/363487#M51389</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2014-08-18T15:16:55Z</dc:date>
    </item>
  </channel>
</rss>

