hardkernel / linux Goto Github PK

This project forked from torvalds/linux

Linux kernel source tree

License: Other

Perl 0.21% C 97.72% Shell 0.08% Awk 0.01% Python 0.08% Assembly 1.54% C++ 0.03% Objective-C 0.01% UnrealScript 0.01% Makefile 0.30% GDB 0.01% Yacc 0.02% Lex 0.01% Roff 0.01% Mathematica 0.01% Gherkin 0.01% XS 0.01% Clojure 0.01% M4 0.01% sed 0.01%

linux's Introduction

        Linux kernel release 4.x <http://kernel.org/>

These are the release notes for Linux version 4.  Read them carefully,
as they tell you what this is all about, explain how to install the
kernel, and what to do if something goes wrong.

WHAT IS LINUX?

  Linux is a clone of the operating system Unix, written from scratch by
  Linus Torvalds with assistance from a loosely-knit team of hackers across
  the Net. It aims towards POSIX and Single UNIX Specification compliance.

  It has all the features you would expect in a modern fully-fledged Unix,
  including true multitasking, virtual memory, shared libraries, demand
  loading, shared copy-on-write executables, proper memory management,
  and multistack networking including IPv4 and IPv6.

  It is distributed under the GNU General Public License - see the
  accompanying COPYING file for more details.

ON WHAT HARDWARE DOES IT RUN?

  Although originally developed first for 32-bit x86-based PCs (386 or higher),
  today Linux also runs on (at least) the Compaq Alpha AXP, Sun SPARC and
  UltraSPARC, Motorola 68000, PowerPC, PowerPC64, ARM, Hitachi SuperH, Cell,
  IBM S/390, MIPS, HP PA-RISC, Intel IA-64, DEC VAX, AMD x86-64, AXIS CRIS,
  Xtensa, Tilera TILE, AVR32, ARC and Renesas M32R architectures.

  Linux is easily portable to most general-purpose 32- or 64-bit architectures
  as long as they have a paged memory management unit (PMMU) and a port of the
  GNU C compiler (gcc) (part of The GNU Compiler Collection, GCC). Linux has
  also been ported to a number of architectures without a PMMU, although
  functionality is then obviously somewhat limited.
  Linux has also been ported to itself. You can now run the kernel as a
  userspace application - this is called UserMode Linux (UML).

DOCUMENTATION:

 - There is a lot of documentation available both in electronic form on
   the Internet and in books, both Linux-specific and pertaining to
   general UNIX questions.  I'd recommend looking into the documentation
   subdirectories on any Linux FTP site for the LDP (Linux Documentation
   Project) books.  This README is not meant to be documentation on the
   system: there are much better sources available.

 - There are various README files in the Documentation/ subdirectory:
   these typically contain kernel-specific installation notes for some
   drivers for example. See Documentation/00-INDEX for a list of what
   is contained in each file.  Please read the Changes file, as it
   contains information about the problems, which may result by upgrading
   your kernel.

 - The Documentation/DocBook/ subdirectory contains several guides for
   kernel developers and users.  These guides can be rendered in a
   number of formats:  PostScript (.ps), PDF, HTML, & man-pages, among others.
   After installation, "make psdocs", "make pdfdocs", "make htmldocs",
   or "make mandocs" will render the documentation in the requested format.

INSTALLING the kernel source:

 - If you install the full sources, put the kernel tarball in a
   directory where you have permissions (e.g. your home directory) and
   unpack it:

     xz -cd linux-4.X.tar.xz | tar xvf -

   Replace "X" with the version number of the latest kernel.

   Do NOT use the /usr/src/linux area! This area has a (usually
   incomplete) set of kernel headers that are used by the library header
   files.  They should match the library, and not get messed up by
   whatever the kernel-du-jour happens to be.

 - You can also upgrade between 4.x releases by patching.  Patches are
   distributed in the xz format.  To install by patching, get all the
   newer patch files, enter the top level directory of the kernel source
   (linux-4.X) and execute:

     xz -cd ../patch-4.x.xz | patch -p1

   Replace "x" for all versions bigger than the version "X" of your current
   source tree, _in_order_, and you should be ok.  You may want to remove
   the backup files (some-file-name~ or some-file-name.orig), and make sure
   that there are no failed patches (some-file-name# or some-file-name.rej).
   If there are, either you or I have made a mistake.

   Unlike patches for the 4.x kernels, patches for the 4.x.y kernels
   (also known as the -stable kernels) are not incremental but instead apply
   directly to the base 4.x kernel.  For example, if your base kernel is 4.0
   and you want to apply the 4.0.3 patch, you must not first apply the 4.0.1
   and 4.0.2 patches. Similarly, if you are running kernel version 4.0.2 and
   want to jump to 4.0.3, you must first reverse the 4.0.2 patch (that is,
   patch -R) _before_ applying the 4.0.3 patch. You can read more on this in
   Documentation/applying-patches.txt

   Alternatively, the script patch-kernel can be used to automate this
   process.  It determines the current kernel version and applies any
   patches found.

     linux/scripts/patch-kernel linux

   The first argument in the command above is the location of the
   kernel source.  Patches are applied from the current directory, but
   an alternative directory can be specified as the second argument.

 - Make sure you have no stale .o files and dependencies lying around:

     cd linux
     make mrproper

   You should now have the sources correctly installed.

SOFTWARE REQUIREMENTS

   Compiling and running the 4.x kernels requires up-to-date
   versions of various software packages.  Consult
   Documentation/Changes for the minimum version numbers required
   and how to get updates for these packages.  Beware that using
   excessively old versions of these packages can cause indirect
   errors that are very difficult to track down, so don't assume that
   you can just update packages when obvious problems arise during
   build or operation.

BUILD directory for the kernel:

   When compiling the kernel, all output files will per default be
   stored together with the kernel source code.
   Using the option "make O=output/dir" allows you to specify an alternate
   place for the output files (including .config).
   Example:

     kernel source code: /usr/src/linux-4.X
     build directory:    /home/name/build/kernel

   To configure and build the kernel, use:

     cd /usr/src/linux-4.X
     make O=/home/name/build/kernel menuconfig
     make O=/home/name/build/kernel
     sudo make O=/home/name/build/kernel modules_install install

   Please note: If the 'O=output/dir' option is used, then it must be
   used for all invocations of make.

CONFIGURING the kernel:

   Do not skip this step even if you are only upgrading one minor
   version.  New configuration options are added in each release, and
   odd problems will turn up if the configuration files are not set up
   as expected.  If you want to carry your existing configuration to a
   new version with minimal work, use "make oldconfig", which will
   only ask you for the answers to new questions.

 - Alternative configuration commands are:

     "make config"      Plain text interface.

     "make menuconfig"  Text based color menus, radiolists & dialogs.

     "make nconfig"     Enhanced text based color menus.

     "make xconfig"     Qt based configuration tool.

     "make gconfig"     GTK+ based configuration tool.

     "make oldconfig"   Default all questions based on the contents of
                        your existing ./.config file and asking about
                        new config symbols.

     "make silentoldconfig"
                        Like above, but avoids cluttering the screen
                        with questions already answered.
                        Additionally updates the dependencies.

     "make olddefconfig"
                        Like above, but sets new symbols to their default
                        values without prompting.

     "make defconfig"   Create a ./.config file by using the default
                        symbol values from either arch/$ARCH/defconfig
                        or arch/$ARCH/configs/${PLATFORM}_defconfig,
                        depending on the architecture.

     "make ${PLATFORM}_defconfig"
                        Create a ./.config file by using the default
                        symbol values from
                        arch/$ARCH/configs/${PLATFORM}_defconfig.
                        Use "make help" to get a list of all available
                        platforms of your architecture.

     "make allyesconfig"
                        Create a ./.config file by setting symbol
                        values to 'y' as much as possible.

     "make allmodconfig"
                        Create a ./.config file by setting symbol
                        values to 'm' as much as possible.

     "make allnoconfig" Create a ./.config file by setting symbol
                        values to 'n' as much as possible.

     "make randconfig"  Create a ./.config file by setting symbol
                        values to random values.

     "make localmodconfig" Create a config based on current config and
                           loaded modules (lsmod). Disables any module
                           option that is not needed for the loaded modules.

                           To create a localmodconfig for another machine,
                           store the lsmod of that machine into a file
                           and pass it in as a LSMOD parameter.

                   target$ lsmod > /tmp/mylsmod
                   target$ scp /tmp/mylsmod host:/tmp

                   host$ make LSMOD=/tmp/mylsmod localmodconfig

                           The above also works when cross compiling.

     "make localyesconfig" Similar to localmodconfig, except it will convert
                           all module options to built in (=y) options.

   You can find more information on using the Linux kernel config tools
   in Documentation/kbuild/kconfig.txt.

 - NOTES on "make config":

    - Having unnecessary drivers will make the kernel bigger, and can
      under some circumstances lead to problems: probing for a
      nonexistent controller card may confuse your other controllers

    - A kernel with math-emulation compiled in will still use the
      coprocessor if one is present: the math emulation will just
      never get used in that case.  The kernel will be slightly larger,
      but will work on different machines regardless of whether they
      have a math coprocessor or not.

    - The "kernel hacking" configuration details usually result in a
      bigger or slower kernel (or both), and can even make the kernel
      less stable by configuring some routines to actively try to
      break bad code to find kernel problems (kmalloc()).  Thus you
      should probably answer 'n' to the questions for "development",
      "experimental", or "debugging" features.

COMPILING the kernel:

 - Make sure you have at least gcc 3.2 available.
   For more information, refer to Documentation/Changes.

   Please note that you can still run a.out user programs with this kernel.

 - Do a "make" to create a compressed kernel image. It is also
   possible to do "make install" if you have lilo installed to suit the
   kernel makefiles, but you may want to check your particular lilo setup first.

   To do the actual install, you have to be root, but none of the normal
   build should require that. Don't take the name of root in vain.

 - If you configured any of the parts of the kernel as `modules', you
   will also have to do "make modules_install".

 - Verbose kernel compile/build output:

   Normally, the kernel build system runs in a fairly quiet mode (but not
   totally silent).  However, sometimes you or other kernel developers need
   to see compile, link, or other commands exactly as they are executed.
   For this, use "verbose" build mode.  This is done by passing
   "V=1" to the "make" command, e.g.

     make V=1 all

   To have the build system also tell the reason for the rebuild of each
   target, use "V=2".  The default is "V=0".

 - Keep a backup kernel handy in case something goes wrong.  This is
   especially true for the development releases, since each new release
   contains new code which has not been debugged.  Make sure you keep a
   backup of the modules corresponding to that kernel, as well.  If you
   are installing a new kernel with the same version number as your
   working kernel, make a backup of your modules directory before you
   do a "make modules_install".

   Alternatively, before compiling, use the kernel config option
   "LOCALVERSION" to append a unique suffix to the regular kernel version.
   LOCALVERSION can be set in the "General Setup" menu.

 - In order to boot your new kernel, you'll need to copy the kernel
   image (e.g. .../linux/arch/x86/boot/bzImage after compilation)
   to the place where your regular bootable kernel is found.

 - Booting a kernel directly from a floppy without the assistance of a
   bootloader such as LILO, is no longer supported.

   If you boot Linux from the hard drive, chances are you use LILO, which
   uses the kernel image as specified in the file /etc/lilo.conf.  The
   kernel image file is usually /vmlinuz, /boot/vmlinuz, /bzImage or
   /boot/bzImage.  To use the new kernel, save a copy of the old image
   and copy the new image over the old one.  Then, you MUST RERUN LILO
   to update the loading map! If you don't, you won't be able to boot
   the new kernel image.

   Reinstalling LILO is usually a matter of running /sbin/lilo.
   You may wish to edit /etc/lilo.conf to specify an entry for your
   old kernel image (say, /vmlinux.old) in case the new one does not
   work.  See the LILO docs for more information.

   After reinstalling LILO, you should be all set.  Shutdown the system,
   reboot, and enjoy!

   If you ever need to change the default root device, video mode,
   ramdisk size, etc.  in the kernel image, use the 'rdev' program (or
   alternatively the LILO boot options when appropriate).  No need to
   recompile the kernel to change these parameters.

 - Reboot with the new kernel and enjoy.

IF SOMETHING GOES WRONG:

 - If you have problems that seem to be due to kernel bugs, please check
   the file MAINTAINERS to see if there is a particular person associated
   with the part of the kernel that you are having trouble with. If there
   isn't anyone listed there, then the second best thing is to mail
   them to me ([email protected]), and possibly to any other
   relevant mailing-list or to the newsgroup.

 - In all bug-reports, *please* tell what kernel you are talking about,
   how to duplicate the problem, and what your setup is (use your common
   sense).  If the problem is new, tell me so, and if the problem is
   old, please try to tell me when you first noticed it.

 - If the bug results in a message like

     unable to handle kernel paging request at address C0000010
     Oops: 0002
     EIP:   0010:XXXXXXXX
     eax: xxxxxxxx   ebx: xxxxxxxx   ecx: xxxxxxxx   edx: xxxxxxxx
     esi: xxxxxxxx   edi: xxxxxxxx   ebp: xxxxxxxx
     ds: xxxx  es: xxxx  fs: xxxx  gs: xxxx
     Pid: xx, process nr: xx
     xx xx xx xx xx xx xx xx xx xx

   or similar kernel debugging information on your screen or in your
   system log, please duplicate it *exactly*.  The dump may look
   incomprehensible to you, but it does contain information that may
   help debugging the problem.  The text above the dump is also
   important: it tells something about why the kernel dumped code (in
   the above example, it's due to a bad kernel pointer). More information
   on making sense of the dump is in Documentation/oops-tracing.txt

 - If you compiled the kernel with CONFIG_KALLSYMS you can send the dump
   as is, otherwise you will have to use the "ksymoops" program to make
   sense of the dump (but compiling with CONFIG_KALLSYMS is usually preferred).
   This utility can be downloaded from
   ftp://ftp.<country>.kernel.org/pub/linux/utils/kernel/ksymoops/ .
   Alternatively, you can do the dump lookup by hand:

 - In debugging dumps like the above, it helps enormously if you can
   look up what the EIP value means.  The hex value as such doesn't help
   me or anybody else very much: it will depend on your particular
   kernel setup.  What you should do is take the hex value from the EIP
   line (ignore the "0010:"), and look it up in the kernel namelist to
   see which kernel function contains the offending address.

   To find out the kernel function name, you'll need to find the system
   binary associated with the kernel that exhibited the symptom.  This is
   the file 'linux/vmlinux'.  To extract the namelist and match it against
   the EIP from the kernel crash, do:

     nm vmlinux | sort | less

   This will give you a list of kernel addresses sorted in ascending
   order, from which it is simple to find the function that contains the
   offending address.  Note that the address given by the kernel
   debugging messages will not necessarily match exactly with the
   function addresses (in fact, that is very unlikely), so you can't
   just 'grep' the list: the list will, however, give you the starting
   point of each kernel function, so by looking for the function that
   has a starting address lower than the one you are searching for but
   is followed by a function with a higher address you will find the one
   you want.  In fact, it may be a good idea to include a bit of
   "context" in your problem report, giving a few lines around the
   interesting one.

   If you for some reason cannot do the above (you have a pre-compiled
   kernel image or similar), telling me as much about your setup as
   possible will help.  Please read the REPORTING-BUGS document for details.

 - Alternatively, you can use gdb on a running kernel. (read-only; i.e. you
   cannot change values or set break points.) To do this, first compile the
   kernel with -g; edit arch/x86/Makefile appropriately, then do a "make
   clean". You'll also need to enable CONFIG_PROC_FS (via "make config").

   After you've rebooted with the new kernel, do "gdb vmlinux /proc/kcore".
   You can now use all the usual gdb commands. The command to look up the
   point where your system crashed is "l *0xXXXXXXXX". (Replace the XXXes
   with the EIP value.)

   gdb'ing a non-running kernel currently fails because gdb (wrongly)
   disregards the starting offset for which the kernel is compiled.

linux's People

Contributors

Stargazers

Watchers

Forkers

cnxsoft xenoxaos memphiz glennodotcom zehome xtitany gu1 ppc52776 jasperdb tobiassimon minux milosivanovic nikkadim heechul americanandroid ggezer dezi siretart severnt n0box gasmaster tygraen szakalit readon fjaguarete ktyng mgtekns vamanea thiakil sert00 atom-bomb bugrax medicalwei mihoelzl swehui dseifert soixanteseize ruppi megglos hellosmart-kr nspierbundel jaegyuc dsd kenwong14 pytaloud claudiobsd wom-bat carleeto yuhan70 gleloop aleksbak rzk yannayl fosk85 xmegz vittgam smod tangweiwei debo890 declanmalone smartharlan llongeri abradianu psw8888 razorbladex401 ljtale jepler narimo markuseich johnoh sungjin75 connersjm gjyoo jeonyongpyo yisuw yesdi fjtsai pyongjeon voodik nirshats kinsamanka odroid-box meaverick suriyanr hellbentv warrenb213 mewlips udemirezen ebiian parkcheoljin spud2233 osti123 yulistic m5p3nc3r quansuhui 90dsend alosk1990 josephmillsatwork bradmccormack nextpay

linux's Issues

Typo in ASV tables

While working on Odroid XU3, I noticed a typo in the ASV tables which would cause cpufreq to not work correctly on boards with ASV=5.

The typo is in https://github.com/hardkernel/linux/blob/odroidxu3-3.10.y/arch/arm/mach-exynos/include/mach/asv-exynos5422_evt0.h#L347. '98750' should be '987500', i.e., a missing zero. This leads to incorrect voltage being assigned to that frequency which then fails sanity checking in code and causes cpufreq to misbehave.

Please let me know if you'd like any more details.

Thanks.

What is the latest compatible xu3 kernel release?

Hello.
I really need to know what is the latest release for odroid xu3.
Because my friend currently has installed debian-odroid-Xu4 on his odroid-xu3 and it seems to get mac address an ip changed on every reboot, even if they were configured statically.(Maybe is there a way to fix this?) anyway kernel downgrade may fix this.
Thanks in advance.

usb-dvb modules on odroid-3.8.y kernel

Is there any specific reason why modules for most usb dvb cards and not enabled in 3.8.y kernel? Can we get enabled at least most common ones (rtl28xxu, ad9015, af9035, it913x)?

Thanks!

[ odroidxu3-3.10.y] latest changes will break Docker

Hi,

the latest changes to odroidxu3_defconfigwill break Docker support in the default kernel.

Generally Necessary:
- cgroup hierarchy: properly mounted [/sys/fs/cgroup]
- CONFIG_NAMESPACES: enabled
- CONFIG_NET_NS: enabled
- CONFIG_PID_NS: enabled
- CONFIG_IPC_NS: enabled
- CONFIG_UTS_NS: enabled
- CONFIG_DEVPTS_MULTIPLE_INSTANCES: missing
- CONFIG_CGROUPS: enabled
- CONFIG_CGROUP_CPUACCT: enabled
- CONFIG_CGROUP_DEVICE: missing
- CONFIG_CGROUP_FREEZER: enabled
- CONFIG_CGROUP_SCHED: enabled
- CONFIG_CPUSETS: missing
- CONFIG_MEMCG: missing
- CONFIG_MACVLAN: enabled (as module)
- CONFIG_VETH: enabled (as module)
- CONFIG_BRIDGE: enabled (as module)
- CONFIG_BRIDGE_NETFILTER: enabled
- CONFIG_NF_NAT_IPV4: enabled (as module)
- CONFIG_IP_NF_FILTER: enabled (as module)
- CONFIG_IP_NF_TARGET_MASQUERADE: enabled (as module)
- CONFIG_NETFILTER_XT_MATCH_ADDRTYPE: enabled (as module)
- CONFIG_NETFILTER_XT_MATCH_CONNTRACK: enabled (as module)
- CONFIG_NF_NAT: enabled (as module)
- CONFIG_NF_NAT_NEEDED: enabled
- CONFIG_POSIX_MQUEUE: enabled

Optional Features:
- CONFIG_USER_NS: enabled
- CONFIG_MEMCG_KMEM: missing
- CONFIG_MEMCG_SWAP: missing
- CONFIG_MEMCG_SWAP_ENABLED: missing
- CONFIG_RESOURCE_COUNTERS: enabled
- CONFIG_BLK_CGROUP: missing
- CONFIG_IOSCHED_CFQ: enabled
- CONFIG_BLK_DEV_THROTTLING: missing
- CONFIG_CGROUP_PERF: missing
- CONFIG_CGROUP_HUGETLB: missing
- CONFIG_NET_CLS_CGROUP: enabled (as module)
- CONFIG_NETPRIO_CGROUP: enabled (as module)
- CONFIG_CFS_BANDWIDTH: enabled
- CONFIG_FAIR_GROUP_SCHED: enabled
- CONFIG_RT_GROUP_SCHED: enabled
- CONFIG_EXT3_FS: missing
- CONFIG_EXT3_FS_XATTR: missing
- CONFIG_EXT3_FS_POSIX_ACL: missing
- CONFIG_EXT3_FS_SECURITY: missing
    (enable these ext3 configs if you are using ext3 as backing filesystem)
- CONFIG_EXT4_FS: enabled
- CONFIG_EXT4_FS_POSIX_ACL: enabled
- CONFIG_EXT4_FS_SECURITY: enabled
- Storage Drivers:
  - "aufs":
    - CONFIG_AUFS_FS: missing
  - "btrfs":
    - CONFIG_BTRFS_FS: enabled (as module)
  - "devicemapper":
    - CONFIG_BLK_DEV_DM: enabled
    - CONFIG_DM_THIN_PROVISIONING: enabled (as module)
  - "overlay":
    - CONFIG_OVERLAY_FS: missing
  - "zfs":
    - /dev/zfs: missing
    - zfs command: missing
    - zpool command: missing

HDMI might miss an IRQ on power off

The function hdmi_s_power() on hdmi_drv.c might miss the external IRQ trigger when powering off.
The function enables the external IRQ source which is triggered on EDGE. Some devices might set the signal in high before they are ready to negotiate a signal, and the board never goes into "plugged" state, since when the IRQ is enabled, the line is already high (no edge!).
The solution is to add:
queue_delayed_work(system_nrt_wq, &hdev->hpd_work_ext, 0);

immediately after the IRQ is enabled in hdmi_s_power(), to force the system to check if the signal is already high.

See this link for more details:

http://forum.odroid.com/viewtopic.php?f=73&t=3889#p32451

EDID 1366x768.bin

Cloud you guys support for 1366x768 resolution for Linux 3.10 for ODROID-XU4?
Thanks. My TV's resolution is in 1366x768.
Thanks a lot

rtl8192 issues in 3.8.13.16

I recently compiled the new kernel for my odroid u2 and noticed my TPLink TL-WN823N usb wireless adapter stopped working. I went through the commits and found the following changes to the defconfig:
-CONFIG_RTL8192CU=m
-CONFIG_RTLWIFI=m
-CONFIG_RTLWIFI_DEBUG=y
-CONFIG_RTL8192C_COMMON=m
+# CONFIG_RTL8192CU is not set
+CONFIG_RTL8192CU_V40=m

I am not sure if its an issue with the wireless driver (v4.0) or if additional settings are missing. I tried to compile 3.8.13.16 with those settings and still didn't seem to work. Not sure what you could do, but though I'd let you know.

lsmod 3.8.13.14
Module Size Used by
nfnetlink_log 7661 0
nfnetlink 4106 1 nfnetlink_log
ipv6 262878 24
dm_crypt 14809 0
dm_mod 70048 1 dm_crypt
rtl8192cu 92885 0
rtlwifi 78850 1 rtl8192cu
rtl8192c_common 59657 1 rtl8192cu
smsc95xx 19099 0
usbnet 19456 1 smsc95xx
gpio_keys 7070 0

lsmod 3.8.13.16
Module Size Used by
nfnetlink_log 7713 0
nfnetlink 4090 1 nfnetlink_log
ipv6 267433 26
dm_crypt 14855 0
rtl8192cu 521699 0
smsc95xx 19079 0
usbnet 19408 1 smsc95xx
gpio_keys 7087 0
dm_mod 70172 1 dm_crypt

Thanks,
Eric

New RTL8153 driver is causing page allocation failure

arter97/odroid@eb209c8

This is on XU4.
Any comments?

(btw, there's a typo on http://www.hardkernel.com/main/products/prdt_info.php?g_code=G143452239825 which indicates RTL8153 as RTL8135.)

odroidc needs to export fiq_bridge_pulse_trigger from plat-meson/fiq_bridge.c

This symbol is used in staging drivers that are set to build as modules and this breaks the build.

OOM killer not working

Hi,

I'm using my odroid-xu3 mainly as a build machine for a couple of large projects. I was getting the ocassional hang of the whole machine. Power cycling it was the only way to get it back.

Invesigating further I managed to write a program that hangs the odroid in the same way.

#include <stdio.h>
#include <stdlib.h>
#include <stdint.h>
#include <inttypes.h>
#include <unistd.h>
#include <string.h>
#include <sys/wait.h>

#define ONE_MEG (1024 * 1024)

static void
alloc_test (uint32_t count)
{   void * array [count] ;
    uint32_t k ;

    memset (array, 0, sizeof (array)) ;
    for (k = 0 ; k < count ; k++)
    {   if ((array [k] = malloc (ONE_MEG)) == NULL)
        {   perror ("malloc") ;
            exit (1) ;
            } ;
        memset (array [k], k, ONE_MEG) ;
        } ;

    printf ("pid %d: All memory allocated and initialized.\n", (int) getpid ()) ;
    sleep (10) ;

    for (k = 0 ; k < count ; k++)
    {   free (array [k]) ;
        array [k] = NULL ;
        } ;

    printf ("pid %d: All memory freed.\n", (int) getpid ()) ;
    return ;
}

int
main (int argc, char *argv [])
{
    uint32_t k, fork_count = 0, alloc_amount = 0 ;
    int status ;

    if (argc >= 2)
        fork_count = atoi (argv [1]) ;
    if (argc >= 3)
        alloc_amount = atoi (argv [2]) ;

    if (fork_count < 1)
        fork_count = 2 ;

    if (alloc_amount < 1)
        alloc_amount = 100 ;

    printf ("fork_count : %u\n", fork_count) ;
    printf ("alloc_amount : %u\n", alloc_amount) ;

    printf ("Allocating %u megabytes per process.\n", alloc_amount) ;

    for (k = 0 ; k < fork_count ; k++)
    {   pid_t child = fork () ;

        if (child < 0)
        {   perror ("fork:") ;
            exit (1) ;
            } ;
        if (child == 0)
        {   alloc_test (alloc_amount) ;
            _exit (0) ;
            }  ;
        } ;

    for (k = 0 ; k < fork_count ; k++)
        wait (&status) ;

    puts ("ok") ;
    return 0 ;
}

This can be compiled using:

gcc -Wall -O2 odroid-fork-alloc-test.c -o odroid-fork-alloc-test

and run using:

./odroid-fork-alloc-test <processes> <megs allocated per process>

Running this as:

./odroid-fork-alloc-test 4 400

works fine, 4 processes are generated and each of those processes allocates and writes to 400Meg of memory.

However:

./odroid-fork-alloc-test 4 450

hangs. In a situation like this, I expect the Out-Of-Memory killer would kill off one of these processes.

As it happens, I have another high end arm board (ifc6540, 4 cores, 2Gig RAM) and that doesn't hang and in fact has a dmesg message stating that the lowmemorykiller killed one of the processes.

4.2-rc1 error when using 3.10 oldconfig

make[1]: *** No rule to make target firmware/mfc_fw.bin', needed by firmware/mfc_fw.bin.gen.o'. Stop.

When I want to upgrade kernel from 3.10 to 4.1 for openvswitch-gre support, I get that error message.
Is there some way using 3.10 oldconfig?
Thanks a lot.

# copy old config file to .config
make oldconfig
# all skip for new feature
make -j4

ASIX 88179 dongle crashes XU under certain traffic loads

With XU configured as a router with both integrated NIC and Gigabit dongle, making a kernel with distcc causes the XU to shut down completely with no log messages. Sustained test with iperf does not cause the machine to crash.
Tested with master distcc host on 100Mbs side and two slave machines on the Gbit side.
More info on the forums: http://forum.odroid.com/viewtopic.php?f=73&t=5188

odroidxu4: Lockups with heavy xhci/SATA load

This is fairly vague at this point, but I have been able to reliably lock up my XU4 when doing heavy I/O load to a hard drive plugged into the cloudshell SATA connector. This is on 4.2-rc1-41.

The best way I've been able to do this consistently is by compiling the kernel on an SSD drive via:

$ make -j9 all

I've been able to reproduce on two different brands/types of SSD. It never happens when running the same command off an SD card.

When it locks up, the fan stays running and I have to unplug/replug the power cable. Oddly, the SATA drive won't be recognized until I reboot a second time. The only interesting bit of kernel log after the first reboot is:
usb 4-1.2: reset SuperSpeed USB device number 3 using xhci-hcd

Again, sorry for the vague issue, but curious if anyone else can reproduce.

Hardkernel LCD screen doesn't have backlight controls (X2/wheezy/3.8 kernel)

CONFIG_BACKLIGHT_PWM is not set in the current/latest kernel. Turning it on doesn't help

zcat /proc/config.gz |grep BACKLIGHT
CONFIG_SAMSUNG_DEV_BACKLIGHT=y
# CONFIG_FB_BACKLIGHT is not set
CONFIG_BACKLIGHT_LCD_SUPPORT=y
CONFIG_BACKLIGHT_CLASS_DEVICE=y
# CONFIG_BACKLIGHT_GENERIC is not set
CONFIG_BACKLIGHT_PWM=m   <--- turned on
# CONFIG_BACKLIGHT_ADP8860 is not set
# CONFIG_BACKLIGHT_ADP8870 is not set
# CONFIG_BACKLIGHT_LM3630 is not set
# CONFIG_BACKLIGHT_LM3639 is not set
# CONFIG_BACKLIGHT_LP855X is not set
CONFIG_HID_PICOLCD_BACKLIGHT=y
CONFIG_LEDS_TRIGGER_BACKLIGHT=y

Boot messages:

$ dmesg | grep back
[    3.977660] pwm-backlight pwm-backlight.0: unable to request PWM, trying legacy API
[    3.982264] pwm-backlight pwm-backlight.0: unable to request legacy PWM
[    4.110729] platform pwm-backlight.0: Driver pwm-backlight requests probe deferral
[    4.289334] pwm-backlight pwm-backlight.0: unable to request PWM, trying legacy API
[    4.302308] pwm-backlight pwm-backlight.0: unable to request legacy PWM
[    4.311763] platform pwm-backlight.0: Driver pwm-backlight requests probe deferral
[    4.386515] pwm-backlight pwm-backlight.0: unable to request PWM, trying legacy API
[    4.394205] pwm-backlight pwm-backlight.0: unable to request legacy PWM
[    4.400775] platform pwm-backlight.0: Driver pwm-backlight requests probe deferral

Older XU kernel (latest, 3.4.91) has /sys/class/ entry for pwm-backlight.0 with working control files. This kernel has the directory, but no controls.

rtl8192 troubles

"odroid wifi adapter 3" has a very strange behavior: it works perfectly fine with 4.3.3 kernel build of raspberry pi 2, with 4.3.3 kernel of my PC (stock archlinux kernel + BFQ) and 4.1.15 (LTS).
I'm getting big performance hit with the odroid C1+ rev0.4 20150930 (both with ping and the download speed of about 1Mbit/s when I achieve 16-17Mbit/s with the same dongle on other devices), though. I tried:

using the official v2.2 android 4.4.2 build;
using the official lxde ubuntu image;
dkms build of the 8192cu on archlinux;
stock rtl8192cu of odroid c1 branch here;
disabling the power management of one module at a time (rtl8192cu and 8192cu), either via modprobe.d/ conf and via pm-utils. No success;
changing USB ports of odroid (I was thinking about a USB malfunction since I struggle to find the reasons for my problems);
surfing the web: I found many threads in yours and archlinuxarm forums in which they were complaining about the "wifi dongle 3" issue years ago (2014). It seems to them you have fixed up the things at some point for a bunch of users. And then the troubles returned in 2015 with a fluctuating behavior between users who found workarounds and users who never got it sorted. You were never able to reproduce the issue in your office, though. But I can assure you there is a situation here;
ethernet. That one works like a charm;
another rtl8188cus dongle (low profile one, without antenna). it has the exact same behavior, again, no success;
I don't have any more dongles to try, but if you suggest me that an ath9k dongle works great in 100% of the users, I could buy that to replace your official one (I read threads of people having troubles also with that in your forums, but they are dated and not so many as the 8188cus ones).

The thing is that in the most similar device I have (raspberry pi 2) the dongle is actually great and the module shows the exact same driver version of the odroid C1 branch (v4.0.2_9000.20130911), just a different srcversion string.

I got rid of my initial project of making the odroid c1+ an android TV device for this reason. It's a pretty good device and it's a shame. I really hope for an investigation of the issue and a final fix.
Thanks for the reading.

f2fs backport

I've done an f2fs backport on 3.0.y. It's available on https://github.com/zehome/linux/tree/odroid-3.0.y-f2fs

I don't know if you are interested in merging such a backport. If you are I can make a clean pull-request. Let me know ;)

odroid u3 kernel cannot be compiled with gcc 5.2 / update u3 kernel to recent linux releases

I'm having difficulties recompiling the kernel for odroid U3 on ArchlinuxArm. The corresponding branch is odroid-3.8.y. The problem is that this kernel requires many patches (some of which I cannot find) to be able to be compiled against current gcc (version 5.2). The solution would be to either perform the corresponding patches or provide a more recent kernel for the U3, such as 4.1.

Is there any plan for doing either of these?

Enabling more TCP congestion control

Some Linux users prefer other TCP congestion control than the default "cubic".

Please enable other TCP congestion controls.

Patch-set : http://arter97.com/0001-defconfig-enable-more-TCP-congestion-controls.patch

CONFIG_MEDIA_TUNER_XC2028 is not set

Hello,

Please enable support for xc2028 tuners found in some DVB-T usb sticks. The config option is: CONFIG_MEDIA_TUNER_XC2028 and the module to be built is: tuner_xc2028.

P.s. I'm referring to the 3.4 kernel for the ODROID XU.

Thanks,
Vittorio G

LM75 temperature sensor module missing

Hi, running sensors-detect from lm-sensors in ubuntu on Odroid U3, the LM75 Texas Instruments seems to be detected but the module lm75 is not available for the kernel.

Is it the correct module?

Could you include in kernel compile build script/config?

I'd like to hopefully use sensors command from lm-sensors...

amlogic/spicc bits per word > 8

SPI transfers with word sizes > 8 bits are not supported correctly. While you can set larger word sizes, only the 8 LSBs are filled with data. I.e., sending out 4 bytes of data as a 32 bit word does not result in a 32 bit word, but in four 32 bit words with 8 bit of data in each.

Seems that cases with word size != 8 is not considered in spicc_hw_xfer().
The TXDATA register is 32bit wide, but always filled with 8 bit data.

CONFIG_PM_RUNTIME remove breaks /dev/hwrng

efa186d breaks /dev/hwrng making it only return garbage. Please fix or revert.

Support overlayfs

Would it be possible to merge in overlayfs support?

https://www.kernel.org/doc/Documentation/filesystems/overlayfs.txt

Thanks!
Christian

Kernel fails to build

$ git clone --depth=1 https://github.com/hardkernel/linux.git -b odroid-3.0.y odroid-3.0.y
$ make odroidu2_ubuntu_mali_defconfig
$ make menuconfig (leave everything as is)
$ make zImage
fs/block_dev.c: In function ‘bdev_inode_switch_bdi’:
fs/block_dev.c:67:4: error: ‘wakeup_bdi’ undeclared (first use in this function)
fs/block_dev.c:67:4: note: each undeclared identifier is reported only once for each function it appears in
make[1]: *** [fs/block_dev.o] Error 1
make[1]: *** Waiting for unfinished jobs....

Result: No kernel built into arch/arm/boot/zImage

V4l2 is not Supported

Using gstreamer 1.0 on XU4 with code from branch odroidxu3-3.10.y results in the following log indicating that V4l2 is not supported.

0:00:01.756558125 ^[[332m 1849^[[00m 0xa60088c0 ^[[31;01mERROR ^[[00m ^[[00m v4l2 gstv4l2object.c:1637:gst_v4l2_object_get_interlace_mode:^[[00m Driver bug detected - check driver with v4l2-compliance from http://git.linuxtv.org/v4l-utils.git

And ultimately, video playback fails with

0:00:01.767332875 ^[[332m 1849^[[00m 0xa60088c0 ^[[33;01mWARN ^[[00m ^[[00m v4l2 gstv4l2object.c:3006:gst_v4l2_object_acquire_format:<v4l2video6dec0>^[[00m error: Video devices uses an unsupported pixel format. 0:00:01.767387208 ^[[332m 1849^[[00m 0xa60088c0 ^[[33;01mWARN ^[[00m ^[[00m v4l2 gstv4l2object.c:3006:gst_v4l2_object_acquire_format:<v4l2video6dec0>^[[00m error: V4L2 format YM12 not supported 0:00:01.767464583 ^[[332m 1849^[[00m 0xa60088c0 ^[[36mINFO ^[[00m ^[[00;01;31;47m GST_ERROR_SYSTEM gstelement.c:1835:gst_element_message_full:<v4l2video6dec0>^[[00m posting message: Video devices uses an unsupported pixel format. 0:00:01.767634958 ^[[332m 1849^[[00m 0xa60088c0 ^[[36mINFO ^[[00m ^[[00;01;31;47m GST_ERROR_SYSTEM gstelement.c:1858:gst_element_message_full:<v4l2video6dec0>^[[00m posted error message: Video devices uses an unsupported pixel format. 0:00:01.767684250 ^[[332m 1849^[[00m 0xa60088c0 ^[[31;01mERROR ^[[00m ^[[00m v4l2videodec gstv4l2videodec.c:567:gst_v4l2_video_dec_handle_frame:<v4l2video6dec0>^[[00m not negotiated 0:00:01.768254000 ^[[332m 1849^[[00m 0xa60088c0 ^[[36mINFO ^[[00m ^[[00m task gsttask.c:300:gst_task_func:<multiqueue0:src_0>^[[00m Task going to paused

The v4l2 compliance output is as below

` Driver Info:
Driver name : MFC
Card type : decoder
Bus info :
Driver version: 1.0.0
Capabilities : 0x04003003
Video Capture
Video Capture Multiplanar
Video Output
Video Output Multiplanar
Streaming

Compliance test for device /dev/video6 (not using libv4l2):

Required ioctls:
fail: /home/spsingh/xu4mali/poky/build/tmp/work/cortexa15hf-vfp-neon-poky-linux-gnueabi/v4l-utils/1.6.2-r0/v4l-utils-1.6.2/utils/v4l2-compliance/v4l2-compliance.cpp(244): string empty
fail: /home/spsingh/xu4mali/poky/build/tmp/work/cortexa15hf-vfp-neon-poky-linux-gnueabi/v4l-utils/1.6.2-r0/v4l-utils-1.6.2/utils/v4l2-compliance/v4l2-compliance.cpp(297): check_ustring(vcap.bus_info, sizeof(vcap.bus_info))
test VIDIOC_QUERYCAP: FAIL

Allow for multiple opens:
test second video open: OK
fail: /home/spsingh/xu4mali/poky/build/tmp/work/cortexa15hf-vfp-neon-poky-linux-gnueabi/v4l-utils/1.6.2-r0/v4l-utils-1.6.2/utils/v4l2-compliance/v4l2-compliance.cpp(244): string empty
fail: /home/spsingh/xu4mali/poky/build/tmp/work/cortexa15hf-vfp-neon-poky-linux-gnueabi/v4l-utils/1.6.2-r0/v4l-utils-1.6.2/utils/v4l2-compliance/v4l2-compliance.cpp(297): check_ustring(vcap.bus_info, sizeof(vcap.bus_info))
test VIDIOC_QUERYCAP: FAIL
fail: /home/spsingh/xu4mali/poky/build/tmp/work/cortexa15hf-vfp-neon-poky-linux-gnueabi/v4l-utils/1.6.2-r0/v4l-utils-1.6.2/utils/v4l2-compliance/v4l2-compliance.cpp(365): doioctl(node, VIDIOC_G_PRIORITY, &prio)
test VIDIOC_G/S_PRIORITY: FAIL

Debug ioctls:
test VIDIOC_DBG_G/S_REGISTER: OK (Not Supported)
test VIDIOC_LOG_STATUS: OK (Not Supported)

Input ioctls:
test VIDIOC_G/S_TUNER/ENUM_FREQ_BANDS: OK (Not Supported)
test VIDIOC_G/S_FREQUENCY: OK (Not Supported)
test VIDIOC_S_HW_FREQ_SEEK: OK (Not Supported)
test VIDIOC_ENUMAUDIO: OK (Not Supported)
test VIDIOC_G/S/ENUMINPUT: OK (Not Supported)
test VIDIOC_G/S_AUDIO: OK (Not Supported)
Inputs: 0 Audio Inputs: 0 Tuners: 0

Output ioctls:
test VIDIOC_G/S_MODULATOR: OK (Not Supported)
test VIDIOC_G/S_FREQUENCY: OK (Not Supported)
test VIDIOC_ENUMAUDOUT: OK (Not Supported)
test VIDIOC_G/S/ENUMOUTPUT: OK (Not Supported)
test VIDIOC_G/S_AUDOUT: OK (Not Supported)
Outputs: 0 Audio Outputs: 0 Modulators: 0

Input/Output configuration ioctls:
test VIDIOC_ENUM/G/S/QUERY_STD: OK (Not Supported)
test VIDIOC_ENUM/G/S/QUERY_DV_TIMINGS: OK (Not Supported)
test VIDIOC_DV_TIMINGS_CAP: OK (Not Supported)
test VIDIOC_G/S_EDID: OK (Not Supported)

Control ioctls:
    test VIDIOC_QUERY_EXT_CTRL/QUERYMENU: OK (Not Supported)
    test VIDIOC_QUERYCTRL: OK
    test VIDIOC_G/S_CTRL: OK
    fail: /home/spsingh/xu4mali/poky/build/tmp/work/cortexa15hf-vfp-neon-poky-linux-gnueabi/v4l-utils/1.6.2-r0/v4l-utils-1.6.2/utils/v4l2-compliance/v4l2-test-controls.cpp(573): g_ext_ctrls does not support count == 0
    test VIDIOC_G/S/TRY_EXT_CTRLS: FAIL
    test VIDIOC_(UN)SUBSCRIBE_EVENT/DQEVENT: OK (Not Supported)
    test VIDIOC_G/S_JPEGCOMP: OK (Not Supported)
    Standard Controls: 0 Private Controls: 0

Format ioctls:
    fail: /home/spsingh/xu4mali/poky/build/tmp/work/cortexa15hf-vfp-neon-poky-linux-gnueabi/v4l-utils/1.6.2-r0/v4l-utils-1.6.2/utils/v4l2-compliance/v4l2-test-formats.cpp(287): Video Capture cap set, but no Video Capture formats defined
    test VIDIOC_ENUM_FMT/FRAMESIZES/FRAMEINTERVALS: FAIL
    test VIDIOC_G/S_PARM: OK (Not Supported)
    test VIDIOC_G_FBUF: OK (Not Supported)
    fail: /home/spsingh/xu4mali/poky/build/tmp/work/cortexa15hf-vfp-neon-poky-linux-gnueabi/v4l-utils/1.6.2-r0/v4l-utils-1.6.2/utils/v4l2-compliance/v4l2-test-formats.cpp(557): Video Capture cap set, but no Video Capture formats defined
    test VIDIOC_G_FMT: FAIL
    test VIDIOC_TRY_FMT: OK (Not Supported)
    test VIDIOC_S_FMT: OK (Not Supported)
    test VIDIOC_G_SLICED_VBI_CAP: OK (Not Supported)

Codec ioctls:
    test VIDIOC_(TRY_)ENCODER_CMD: OK (Not Supported)
    test VIDIOC_G_ENC_INDEX: OK (Not Supported)
    test VIDIOC_(TRY_)DECODER_CMD: OK (Not Supported)

Buffer ioctls:
    test VIDIOC_REQBUFS/CREATE_BUFS/QUERYBUF: OK
    test VIDIOC_EXPBUF: OK (Not Supported)

Total: 39, Succeeded: 33, Failed: 6, Warnings: 0 `

About resolution change patches.

I find the latest version for odroid 3.0.y removed all function about changing resolution on HDMI interface.
Why it should be reverted? Does it works? Is there any unpairable problem on that?

usb-dvb modules on odroid-3.8.y kernel

Is there any specific reason why modules for most usb dvb cards and not enabled in 3.8.y kernel? Can we get enabled at least most common ones (rtl28xxu, ad9015, af9035, it913x)?

Thanks!

missing defconfig: arch/arm/configs/odroidw_defconfig

there should be a defconfig for odroidw corresponding to http://odroid.com/dokuwiki/doku.php?id=en:odroidwkernelcompilation

Can you add network BONDING module?

Network BONDING is not compiled as a module in 3.8.y.
Can you include it as a module?

Thank you!

Typo in ASV tables

While working on Odroid XU3, I noticed a typo in the ASV tables which would cause cpufreq to not work correctly on boards with ASV=5.

The typo is in https://github.com/hardkernel/linux/blob/odroidxu3-3.10.y/arch/arm/mach-exynos/include/mach/asv-exynos5422_evt0.h:line #347. '98750' should be '987500', i.e., a missing zero. This leads to incorrect voltage being assigned to that frequency which then fails sanity checking in code and causes cpufreq to misbehave.

Please let me know if you'd like any more details.

Thanks.

Symbol collision on linking

When compiling the kernel for the Odroid-XU3 on branch 3.10.y if you have the right configuration you will run into this while trying link the binary:

LD arch/arm/mach-exynos/built-in.o
arch/arm/mach-exynos/secmem.o: In function exynos_ion_sync_for_device': secmem.c:(.text+0xd4): multiple definition ofexynos_ion_sync_for_device'
arch/arm/mach-exynos/mach-odroid-xu3.o:mach-odroid-xu3.c:(.text+0x0): first defined here
arch/arm/mach-exynos/secmem.o: In function exynos_ion_sync_for_cpu': secmem.c:(.text+0xec): multiple definition ofexynos_ion_sync_for_cpu'
arch/arm/mach-exynos/mach-odroid-xu3.o:mach-odroid-xu3.c:(.text+0x18): first defined here
scripts/Makefile.build:387: recipe for target 'arch/arm/mach-exynos/built-in.o' failed
make[1]: *** [arch/arm/mach-exynos/built-in.o] Error 1
Makefile:797: recipe for target 'arch/arm/mach-exynos' failed

A simple fix would be give a static context to the functions at https://github.com/hardkernel/linux/blob/odroidxu3-3.10.y/include/linux/exynos_ion.h#L131

The error occurs because both .c files bring in the exynos_ion.h header file and the void functions are declared globally. So making them static shouldn't be an issue when it comes to symbol resolution by the linker. I've tested this fix myself and can confirm it builds properly as it should.

Filesystem label corruption

We're noticing this problem lately. Using an odroid xu3 (fresh board) on a SD card (and also seen on an MMC). Using ARM (little endian), ELF binaries, cortex-a15 build configuration, EABIhf (as opposed to just EABI), and NEON/VFPv4 instructions with Thumb2.

Please let me know if any of those are not compatible.

The filesystem label seems to be corrupted in rare cases. It will be set to "layer", then on the next boot be "lager" or "la{ev". This seems like a bit flip via a timing error. Could this be caused by anything in the kernel?

This is using commit ID 30cd824 on the odroidxu3-3.10.y branch.

Issues using HW TRNG on XU4

I'm interested in using the hardware true random number generator of the Exynos 5422.
The related driver exyswd-rng under drivers/char/hw_random is disabled in the default config.
I tried to make it work however the TRNG init SMC call exynos_smc(SMC_CMD_RANDOM, HWRNG_INIT, 0, 0) returns -1.
I was discussing this with Krzysztof Kozlowski and he recommended to check with you as the firmware might have been customized.

Does the firmware provided by hardkernel support the SMC call for controling the TRNG?
If yes: What's the cmd id, the one mentioned in the driver (0x81000030)?
If not: Is there a specific reason and could it be added?

ASIX AX88179 gigabit ethernet stops working after a while/under load

I'm using a Plugable USB3-HUB3ME Gigabit Ethernet Adapter with 3 Port USB 3.0 Hub which is build around the ASIX AX88179 and VIA VL812 chipsets. While the harddrive works well on the USB 3.0 hub, the gigabit ethernet regularly stops working after a short while or under bigger load. There are no related messages in /var/log/syslog but when I un-plug and re-plug the ethernet cable after the network stopped working, I get the following messages:

Jan 16 22:49:36 *** kernel: [ 1755.845627] [c0] ax88179_178a 4-1.1:1.0 eth2: ax88179 - Link status is: 0
Jan 16 22:49:39 *** kernel: [ 1758.405614] [c0] ax88179_178a 4-1.1:1.0 eth2: ax88179 - Link status is: 1

Some basic functionality seems to be still available. But it does not reconnect.

I ran the odroid utility to update kernel, firmware, etc. but no change. At the same time the built-in ethernet works fine.

Enable CloudShell backlight in the 4.2-rc1 kernel

Please merge 82f6732 into 4.2-rc1. Thanks!

Booting kenel 3.12 on XU

Is there any file documenting procedures or ofering any kind of documentation?

Aufs kernel panics

I think there might be an issue with the aufs merge into the odroid-xu3 branch.

I looked up this error online and it was said that it was due to a buggy implementation in the kernel.

[   26.595581] [c7] aufs au_opts_verify:1602:docker[432]: dirperm1 breaks the protection by the permission bits on the lower branch
[   26.644463] [c4] aufs au_opts_verify:1602:docker[442]: dirperm1 breaks the protection by the permission bits on the lower branch
[   26.778337] [c4] cgroup: docker (442) created nested cgroup for controller "memory" which has incomplete hierarchy support. Nested cgroups may change behavior in the future.
[   26.792432] [c4] cgroup: "memory" requires setting use_hierarchy to 1 on the root.
[   26.916644] [c4] BUG: looking up invalid subclass: 8
[   26.920145] [c4] turning off the locking correctness validator.
[   26.926042] [c4] CPU: 4 PID: 629 Comm: docker Tainted: G           O 3.10.82 #1
[   26.933331] [c4] Backtrace:
[   26.936194] [c4] [<c0012e90>] (dump_backtrace+0x0/0x114) from [<c0013100>] (show_stack+0x20/0x24)
[   26.945045] [c4]  r6:c0911a5c r5:c095c99c r4:00000000 r3:00000000
[   26.951114] [c4] [<c00130e0>] (show_stack+0x0/0x24) from [<c06049c0>] (dump_stack+0x24/0x28)
[   26.959544] [c4] [<c060499c>] (dump_stack+0x0/0x28) from [<c008ef3c>] (__lock_acquire.isra.26+0x4c8/0xd24)
[   26.969171] [c4] [<c008ea74>] (__lock_acquire.isra.26+0x0/0xd24) from [<c008ffac>] (lock_acquire+0xa4/0x138)
[   26.978975] [c4] [<c008ff08>] (lock_acquire+0x0/0x138) from [<c0605d50>] (mutex_lock_nested+0x68/0x3dc)
[   26.988359] [c4] [<c0605ce8>] (mutex_lock_nested+0x0/0x3dc) from [<bf3e9d88>] (au_lkup_dentry+0x4ac/0x508 [aufs])
[   26.998597] [c4] [<bf3e98dc>] (au_lkup_dentry+0x0/0x508 [aufs]) from [<bf3f2804>] (aufs_lookup+0xd8/0x278 [aufs])
[   27.008833] [c4] [<bf3f272c>] (aufs_lookup+0x0/0x278 [aufs]) from [<c013d5c4>] (lookup_real+0x30/0x5c)
[   27.018102] [c4]  r8:00000001 r7:c5847e08 r6:c6639bd0 r5:c6639bd0 r4:c66cc888
r3:bf3f272c
[   27.026340] [c4] [<c013d594>] (lookup_real+0x0/0x5c) from [<c013e39c>] (__lookup_hash+0x48/0x50)
[   27.035108] [c4]  r5:c6639bd0 r4:00000001
[   27.039094] [c4] [<c013e354>] (__lookup_hash+0x0/0x50) from [<c013ea30>] (lookup_slow+0x4c/0xb8)
[   27.047862] [c4]  r5:c5847e10 r4:c5847e68
[   27.051851] [c4] [<c013e9e4>] (lookup_slow+0x0/0xb8) from [<c0140840>] (path_lookupat+0x23c/0x830)
[   27.060791] [c4]  r7:ffffff9c r6:c5847e08 r5:c5847e10 r4:c5846028
[   27.066860] [c4] [<c0140604>] (path_lookupat+0x0/0x830) from [<c0140e64>] (filename_lookup.isra.45+0x30/0x78)
[   27.076762] [c4] [<c0140e34>] (filename_lookup.isra.45+0x0/0x78) from [<c01432a0>] (user_path_at_empty+0x64/0x8c)
[   27.086996] [c4]  r7:c5847f00 r6:c5847e68 r5:00000001 r4:c630e000
[   27.093063] [c4] [<c014323c>] (user_path_at_empty+0x0/0x8c) from [<c01432ec>] (user_path_at+0x24/0x2c)
[   27.102353] [c4]  r8:c5847f40 r7:10c35920 r6:ffffff9c r5:00000001 r4:10c32a80
[   27.109462] [c4] [<c01432c8>] (user_path_at+0x0/0x2c) from [<c01388f8>] (vfs_fstatat+0x54/0xa8)
[   27.118150] [c4] [<c01388a4>] (vfs_fstatat+0x0/0xa8) from [<c0138974>] (vfs_stat+0x28/0x2c)
[   27.126473] [c4]  r8:c000ea64 r7:000000c3 r6:35386534 r5:00000000 r4:10c32a80
[   27.133586] [c4] [<c013894c>] (vfs_stat+0x0/0x2c) from [<c01390b4>] (SyS_stat64+0x24/0x40)
[   27.141841] [c4] [<c0139090>] (SyS_stat64+0x0/0x40) from [<c000e840>] (ret_fast_syscall+0x0/0x38)
[   27.150686] [c4]  r4:00000000
b26eb84e669fb72092415f848d54e851e38d1d8172d2526bac5821584f4b9e13

Any ideas?

ODROID kernel vulnerable to known local root exploit on Samsung phones (/dev/exynos-mem)

Hi,
While browsing the source code and defconfig, I noticed the exynos-mem block device is enabled in the kernel you provide and is also word-writable.
It is the cause of the local root exploit published last month for Samsung phones, cf. http://forum.xda-developers.com/showthread.php?t=2048511
I'm no expert on Exynos SoC, but from what I gather, that block device is only used on android, so couldn't we at least disable it on ubuntu defconfig ?

Arch linux-odroid-c1-3.10.80-16 <> linux-firmware

Hello,
I notice that my FTDI converter hang after few minutes with the latest -16 build, dmesg return ftdi_sio ttyUSB0: failed to get modem status: -110.
I have to downgrade to Arch linux-odroid-c1-3.10.80-14 where linux-firmware-20150904.6ebf5d5-1-any.pkg.tar.xz work without any hitch.
Thanks for your work

Build is broken. Exits with Error 1 when building vmlinux

I've tried multiple things and this continues to happen.

]$ make ARCH=arm -j4 zImage modules
drivers/built-in.o: In function lowmem_shrink': /home/icebrkr/odroid/odroid.3.0.y-android/drivers/staging/android/lowmemorykiller.c:163: undefined reference tocompact_nodes'
make: *** [.tmp_vmlinux1] Error 1

update odroidxu4-4.2 to rc6

I've merged Linux 4.2-rc6 to here: https://github.com/paralin/linux/tree/odroidxu4-v4.2-rc6

Suggesting to make a new branch in this repo and pull from mine.

Rc6 fixes a lot of bugs in rc1, including #125

~ Christian

Problem Buildingwith Yocto due to wrong symlink

Dear all,

I am working to build the kernel using the yocto embedded toolchain https://www.yoctoproject.org. It does not work out of the box because the build process in Kernel 3.4 creates a recursive symbolic link while building /drivers/gpu/arm/mali400/ump

The reason for this behaviour in the 3.4.y kernel is the commit 73341c8 where arch-release is added. It was removed in commit 9a3fbdc.

The following path fixes this issue.

--- linux/drivers/gpu/arm/mali400/ump/Kbuild 2014-07-30 15:44:03.984805492 +0200
+++ linux/drivers/gpu/arm/mali400/ump/Kbuild 2014-07-30 15:44:39.609139070 +0200
@@ -21,7 +21,7 @@
else

Link arch to the selected arch-config directory

$(shell [ -L $(src)/arch ] && rm $(src)/arch)
-$(shell ln -sf arch-$(CONFIG) $(src)/arch)
+$(shell ln -sf $(src)/arch-$(CONFIG) $(src)/arch)
$(shell touch $(src)/arch/config.h)
endif

Maybe add this fix to the master branch?

undefined reference to `exynos_enter_aftr'

Hello, I have with vanilla 3.17.0:

arch/arm/mach-exynos/built-in.o: In function .LANCHOR1': :(.data+0x74): undefined reference toexynos_enter_aftr'
My config file:
http://files.first-world.info/temp/config.xz
If already patched, can you say me the patch number. And say me what is the config responsive of that's.
My target it's have low power server node.

Thanks for your work on mainline, greate work. Cheers,

odroid u2 poweroff failure

running debian jessie powered by 3.8.13.14
using 8gb sdcard and a standard micro-hdmi to hdmi cable
typed in the terminal:

sudo bash
sync && poweroff

sources seem to point to this file:
vi arch/arm/mach-exynos/mach-hkdk4412.c +585

odroidxu3-3.10.y does not build without debugging options enabled

The XU3 branch fails to build with CONFIG_DEBUG_MUTEXES=n because of the harakiri merge that is 2d9cd5c . Where is it even merged from?

odroidxu4 - unregister_netdevice bug

According to this issue: moby/moby#5618

There is a bug in the current version of RC1 of Linux 4.2. Can we update to rc3? This is a pretty big bug with 4.x at the moment. It overflows the kernel log and crashes the system.

[  905.414211] unregister_netdevice: waiting for vetha472333 to become free. Usage count = 1

[backport request] 3.10.y ZRAM comp_algorithm

It's a great shame the 3.10.y C1 kernel doesn't support the lz4 compression algorithm in the zram module.

Compared to lzo, backporting the algo would yield immediate gains entirely for free (in the order of 5-10% for real-world memory-intensive tasks) .

TIA

"Section mismatch in reference from the variable max77686_regulators"

while compiling kernel with

make odroidx2_ubuntu_defconfig
make zImage CONFIG_DEBUG_SECTION_MISMATCH=y -j4

following warning is produced

WARNING: vmlinux.o(.data+0x8abc): Section mismatch in reference from the variable max77686_regulators to the (unknown reference) .init.data:(unknown)
The variable max77686_regulators references
the (unknown reference) __initdata (unknown)
If the reference is valid then annotate the
variable with __init* or __refdata (see linux/init.h) or name the variable:
*_template, *_timer, *_sht, *_ops, *_probe, *_probe_one, *_console

broken dependencies in configuration

There are multiple broken dependencies. If backports is disabled the kernel build failes with

net/core/dev_ioctl.c:562: undefined reference to `wext_handle_ioctl'

Aufs in xu4 4.0 kernel branch

How much work is required to merge aufs support into the kernel for the XU4?

hardkernel / linux Goto Github PK

linux's Introduction

linux's People

Contributors

Stargazers

Watchers

Forkers

linux's Issues

Link arch to the selected arch-config directory

Recommend Projects

Recommend Topics

Recommend Org

Jobs