spotify / linux Goto Github PK

Spotify's Linux kernel for Debian-based systems

License: Other

Scilab 0.01% JavaScript 0.01% Assembly 2.43% Perl 0.10% Shell 0.03% Objective-C 0.48% Python 0.01% Vim Script 0.01% C 96.77% C++ 0.18% Ruby 0.01%

linux's Introduction

	Linux kernel release 2.6.xx <http://kernel.org/>

These are the release notes for Linux version 2.6.  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, AVR32 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 (eg. your home directory) and
   unpack it:

		gzip -cd linux-2.6.XX.tar.gz | tar xvf -

   or
		bzip2 -dc linux-2.6.XX.tar.bz2 | tar xvf -


   Replace "XX" 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 2.6.xx releases by patching.  Patches are
   distributed in the traditional gzip and the newer bzip2 format.  To
   install by patching, get all the newer patch files, enter the
   top level directory of the kernel source (linux-2.6.xx) and execute:

		gzip -cd ../patch-2.6.xx.gz | patch -p1

   or
		bzip2 -dc ../patch-2.6.xx.bz2 | patch -p1

   (repeat xx for all versions bigger than the version of your current
   source tree, _in_order_) and you should be ok.  You may want to remove
   the backup files (xxx~ or xxx.orig), and make sure that there are no
   failed patches (xxx# or xxx.rej). If there are, either you or me has
   made a mistake.

   Unlike patches for the 2.6.x kernels, patches for the 2.6.x.y kernels
   (also known as the -stable kernels) are not incremental but instead apply
   directly to the base 2.6.x kernel.  Please read
   Documentation/applying-patches.txt for more information.

   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.

 - If you are upgrading between releases using the stable series patches
   (for example, patch-2.6.xx.y), note that these "dot-releases" are
   not incremental and must be applied to the 2.6.xx base tree. For
   example, if your base kernel is 2.6.12 and you want to apply the
   2.6.12.3 patch, you do not and indeed must not first apply the
   2.6.12.1 and 2.6.12.2 patches. Similarly, if you are running kernel
   version 2.6.12.2 and want to jump to 2.6.12.3, you must first
   reverse the 2.6.12.2 patch (that is, patch -R) _before_ applying
   the 2.6.12.3 patch.
   You can read more on this in Documentation/applying-patches.txt

 - 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 2.6.xx 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" allow you to specify an alternate
   place for the output files (including .config).
   Example:
     kernel source code:	/usr/src/linux-2.6.N
     build directory:		/home/name/build/kernel

   To configure and build the kernel use:
   cd /usr/src/linux-2.6.N
   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.

 - Alternate configuration commands are:
	"make config"      Plain text interface.
	"make menuconfig"  Text based color menus, radiolists & dialogs.
	"make xconfig"     X windows (Qt) based configuration tool.
	"make gconfig"     X windows (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 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.

   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
	- compiling the kernel with "Processor type" set higher than 386
	  will result in a kernel that does NOT work on a 386.  The
	  kernel will detect this on bootup, and give up.
	- 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 inserting
   "V=1" in 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/i386/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/ .
   Alternately 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.

 - Alternately, 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/i386/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

dancerindark milanjukl catufunwa ek0892 avr92 artur321 viktor1889 matteliot michael-fore javierrodriguez94 chengyil lovejavaee yagyaansh oandrew madhurrajn qrydat kaos ulriksen shubhamworks78 wshe1978 catramen rugby110 liu-tim colinrgodsey lazy-propagator fastchip xiaoshuiqiang luigizuccarelli pallavagarwal07 frangm rege1989 ericdomi65 coderfeng21 rayjk123 eddie-wang yeoncheonyi tiny1990 deepthi-lnt javineo jay0286 sharman98 ztrix renstanford uu-kishorkumara waspath srogha2 camparijet kimi8187 abhi-infrrd suplo almagjonaj jamijam rickai supernatural ivopi bigdave1357 nikita-tomilov xinyigu2 mak-454 lancemsx declanintel huqikai ksakhil shipraaa dwdrajesh sarkartanzil heartbreaker1411 kkoopa priyanshi1106 jwellbelove yuyue2013 petrz12 curtisho egoodeed amolaedarai charlesunixpro gxkevin benjunmun jhpadjustable destinywck fox0821 metalicjames autoruncd-johnny khateebnsit trung211 alyssaone prateshg dvenum jeson534m123 vakhak rkny aspadistra git-thk-ito sixiango cao-ning maleeky milawka osbornq yodaldevoid zqccc

linux's Issues

earlycon function can't be used when CONFIG_SERIAL_8250 was set m.

How to reproduce it?

Added "console=ttyS0,115200 earlycon=uart8250,mmio32,0x80300000" to bootargs parameter on device tree file.
Set CONFIG_SERIAL_8250 from y to m on kernel config file.
Useed uart8250, then built kernel.
Result: The kernel message can't be printed when this system was startuping.

Expect: The kernel message can be printed when earlycon was set.

The reason:

Checked drivers/tty/serial/Makefile file,
obj-$(CONFIG_SERIAL_8250) += 8250/

drivers/tty/serial/8250/Makefile
obj-$(CONFIG_SERIAL_8250_CONSOLE) += 8250_early.o

If CONFIG_SERIAL_8250 was set m, then 8250_early.o can't be built, so earlycon can't output any message.

I have confirmed the below tested, when 8250_early.o was not depended on CONFIG_SERIAL_8250, the message can be printed.
--- a/drivers/tty/serial/Makefile
+++ b/drivers/tty/serial/Makefile
@@ -5,7 +5,7 @@
obj-$(CONFIG_SERIAL_CORE) += serial_core.o
obj-$(CONFIG_SERIAL_21285) += 21285.o

-obj-$(CONFIG_SERIAL_EARLYCON) += earlycon.o
+obj-$(CONFIG_SERIAL_EARLYCON) += earlycon.o 8250/8250_early.o
obj-$(CONFIG_SERIAL_EARLYCON_ARM_SEMIHOST) += earlycon-arm-semihost.o

Log message:
[ESL_Start_OS]:[967L] Start to jump Linux kernel
Uncompressing Linux... done, booting the kernel.
Booting Linux on physical CPU 0x20000
Initializing cgroup subsys cpuset
Initializing cgroup subsys cpu
Initializing cgroup subsys cpuacct
Linux version 4.1.12 (fcg@linux-8kjf) (gcc version 4.9.3 20151223 (prerelease) (SDK V100R005C00SPC060B020) ) #9 SMP PREEMPT Fri May 13 06:56:26 UTC 2016
CPU: AArch64 Processor [411fd071] revision 1
Detected PIPT I-cache on CPU0
alternatives: enabling workaround for ARM erratum 832075
earlycon: Early serial console at MMIO32 0x80300000 (options '')
bootconsole [uart0] enabled
efi: Getting EFI parameters from FDT:
efi: UEFI not found.
Reserving 512MB of memory at 1532MB for crashkernel
cma: Reserved 16 MiB at 0x000000005ec00000
psci: probing for conduit method from DT.
NOTICE: [psci_smc_handler]:[239L] PSCI_VERSION CALL
NOTICE: [psci_version]:[76L] PSCI_MAJOR_VER: 0: PSCI_MINOR_VER: 2

0020:?84
psci: PSCIv0.2 detected in firmware.
psci: Using standard PSCI v0.2 function IDs
PERCPU: Embedded 17 pages/cpu @ffffffc05eac4000 s30976 r8192 d30464 u69632
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 515088
Kernel command line: console=ttyS0,115200 earlycon=uart8250,mmio32,0x80300000 initrd=0x7000000,350M cetartlb=0x40000000%0x1100000000 kbox_mem=16M@0x1080000000 ekbox=0x80000$0x1081000000 mtrc=0x1000000%0x1140000000 isolcpus=4-15 nohz_full=4-15 crashkernel=512M@1532M kmemleak=on
log_buf_len individual max cpu contribution: 4096 bytes
log_buf_len total cpu_extra contributions: 61440 bytes
log_buf_len min size: 16384 bytes
log_buf_len: 131072 bytes
early log buf free: 14200(86%)
PID hash table entries: 4096 (order: 3, 32768 bytes)
Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes)
Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes)
software IO TLB mem 0x586fc000-0x5c6fc000 mapped at [ffffffc0586fc000-ffffffc05c6fbfff]
Memory: 1079308K/2093056K available (4420K kernel code, 431K rwdata, 1724K rodata, 2608K init, 760K bss, 997364K reserved, 16384K cma-reserved)
Virtual kernel memory layout:
vmalloc : 0xffffff8000000000 - 0xffffffbdbfff0000 ( 246 GB)
fixed : 0xffffffbffabfd000 - 0xffffffbffac00000 ( 12 KB)
PCI I/O : 0xffffffbffae00000 - 0xffffffbffbe00000 ( 16 MB)
modules : 0xffffffbffc000000 - 0xffffffc000000000 ( 64 MB)
memory : 0xffffffc000000000 - 0xffffffc07fc00000 ( 2044 MB)
.init : 0xffffffc000800000 - 0xffffffc000a8c000 ( 2608 KB)
.text : 0xffffffc000080000 - 0xffffffc000800000 ( 7680 KB)
.data : 0xffffffc000a8d000 - 0xffffffc000af8e00 ( 432 KB)
SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=1
Preemptible hierarchical RCU implementation.
Additional per-CPU info printed with stalls.
RCU restricting CPUs from NR_CPUS=64 to nr_cpu_ids=16.
RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=16
NR_IRQS:64 nr_irqs:64 0
ITS: /interrupt-controller@8d000000/interrupt-controller@8c000000
ITS: allocated 65536 Devices @58080000 (psz 4K, shr 1)
ITS: allocated 512 Virtual CPUs @5802f000 (psz 4K, shr 1)
ITS: allocated 512 Interrupt Collections @58100000 (psz 4K, shr 1)
ITS: /interrupt-controller@8d000000/interrupt-controller@c6000000
ITS: allocated 65536 Devices @58180000 (psz 4K, shr 1)
ITS: allocated 512 Virtual CPUs @58109000 (psz 4K, shr 1)
ITS: allocated 512 Interrupt Collections @5810a000 (psz 4K, shr 1)
ITS: /interrupt-controller@8d000000/interrupt-controller@a3000000
ITS: allocated 65536 Devices @58200000 (psz 4K, shr 1)
ITS: allocated 512 Virtual CPUs @58123000 (psz 4K, shr 1)
ITS: allocated 512 Interrupt Collections @58124000 (psz 4K, shr 1)
ITS: /interrupt-controller@8d000000/interrupt-controller@b7000000
ITS: allocated 65536 Devices @58280000 (psz 4K, shr 1)
ITS: allocated 512 Virtual CPUs @5812d000 (psz 4K, shr 1)
ITS: allocated 512 Interrupt Collections @5812e000 (psz 4K, shr 1)
GIC: using LPI property table @0x0000000058150000
ITS: Allocated 1792 chunks for LPIs
CPU0: found redistributor 20000 region 0:0x000000008d100000
CPU0: using LPI pending table @0x0000000058160000
MBIGEN: /peripherals/interrupt-controller@8c030000
MBIGEN: /peripherals/interrupt-controller@c6030000
MBIGEN: /peripherals/interrupt-controller@a3030000
MBIGEN: /peripherals/interrupt-controller@b7030000
NO_HZ: Full dynticks CPUs: 4-15.
Offload RCU callbacks from CPUs: 4-15.
Architected cp15 timer(s) running at 50.00MHz (phys).
clocksource arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0xb8812736b, max_idle_ns: 440795202655 ns
sched_clock: 56 bits at 50MHz, resolution 20ns, wraps every 4398046511100ns
Console: colour dummy device 80x25
Calibrating delay loop (skipped), value calculated using timer frequency.. 100.00 BogoMIPS (lpj=200000)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 4096 (order: 3, 32768 bytes)
Mountpoint-cache hash table entries: 4096 (order: 3, 32768 bytes)
Initializing cgroup subsys devices
Initializing cgroup subsys freezer
Initializing cgroup subsys debug
ftrace: allocating 16087 entries in 63 pages
hw perfevents: enabled with arm/armv8-pmuv3 PMU driver, 7 counters available
EFI services will not be available.
NOTICE: [psci_smc_handler]:[297L] PSCI_CPU_ON_AARCH64 CALL
NOTICE: [psci_smc_handler]:[298L] x1=0x20001 x2=0x2007f0 x3=0x0
NOTICE: [cm_init_context]:[238L] ctx add = 7fc19790
NOTICE: [scpi_set_css_power_state]:[100L] domain_cluster=0x1
NOTICE: [scpi_set_css_power_state]:[113L] domain_cluster=0x1

0020:?AB84
NOTICE: [psci_afflvl_power_on_finish]:[496L]
NOTICE: [cm_prepare_el3_exit]:[254L] read_tpidr_el3 = 7fc1b9c0
NOTICE: [cm_prepare_el3_exit]:[298L] ctx add = 7fc19790
NOTICE: [psci_afflvl_power_on_finish]:[557L]

002007?0
NOTICE: [psci_smc_handler]:[297L] PSCI_CPU_ON_AARCH64 CALL
NOTICE: [psci_smc_handler]:[298L] x1=0x20002 x2=0x2007f0 x3=0x0
NOTICE: [cm_init_context]:[238L] ctx add = 7fc199a0
NOTICE: [scpi_set_css_power_state]:[100L] domain_cluster=0x1
NOTICE: [scpi_set_css_power_state]:[113L] domain_cluster=0x1

0020:?AB84
NOTICE: [psci_afflvl_power_on_finish]:[496L]
NOTICE: [cm_prepare_el3_exit]:[254L] read_tpidr_el3 = 7fc1ba40
NOTICE: [cm_prepare_el3_exit]:[298L] ctx add = 7fc199a0
NOTICE: [psci_afflvl_power_on_finish]:[557L]

002007?0
NOTICE: [psci_smc_handler]:[297L] PSCI_CPU_ON_AARCH64 CALL
NOTICE: [psci_smc_handler]:[298L] x1=0x20003 x2=0x2007f0 x3=0x0
NOTICE: [cm_init_context]:[238L] ctx add = 7fc19bb0
NOTICE: [scpi_set_css_power_state]:[100L] domain_cluster=0x1
NOTICE: [scpi_set_css_power_state]:[113L] domain_cluster=0x1

0020:?AB84
NOTICE: [psci_afflvl_power_on_finish]:[496L]
NOTICE: [cm_prepare_el3_exit]:[254L] read_tpidr_el3 = 7fc1bac0
NOTICE: [cm_prepare_el3_exit]:[298L] ctx add = 7fc19bb0
NOTICE: [psci_afflvl_power_on_finish]:[557L]

002007?0
NOTICE: [psci_smc_handler]:[297L] PSCI_CPU_ON_AARCH64 CALL
NOTICE: [psci_smc_handler]:[298L] x1=0x20100 x2=0x2007f0 x3=0x0
NOTICE: [cm_init_context]:[238L] ctx add = 7fc19dc0
NOTICE: [scpi_set_css_power_state]:[100L] domain_cluster=0x1
NOTICE: [scpi_set_css_power_state]:[113L] domain_cluster=0x3

0020:?AB84
NOTICE: [psci_afflvl_power_on_finish]:[496L]
NOTICE: [cm_prepare_el3_exit]:[254L] read_tpidr_el3 = 7fc1bb40
NOTICE: [cm_prepare_el3_exit]:[298L] ctx add = 7fc19dc0
NOTICE: [psci_afflvl_power_on_finish]:[557L]

002007?0
NOTICE: [psci_smc_handler]:[297L] PSCI_CPU_ON_AARCH64 CALL
NOTICE: [psci_smc_handler]:[298L] x1=0x20101 x2=0x2007f0 x3=0x0
NOTICE: [cm_init_context]:[238L] ctx add = 7fc19fd0
NOTICE: [scpi_set_css_power_state]:[100L] domain_cluster=0x3
NOTICE: [scpi_set_css_power_state]:[113L] domain_cluster=0x3

0020:?AB84
NOTICE: [psci_afflvl_power_on_finish]:[496L]
NOTICE: [cm_prepare_el3_exit]:[254L] read_tpidr_el3 = 7fc1bbc0
NOTICE: [cm_prepare_el3_exit]:[298L] ctx add = 7fc19fd0
NOTICE: [psci_afflvl_power_on_finish]:[557L]

002007?0
NOTICE: [psci_smc_handler]:[297L] PSCI_CPU_ON_AARCH64 CALL
NOTICE: [psci_smc_handler]:[298L] x1=0x20102 x2=0x2007f0 x3=0x0
NOTICE: [cm_init_context]:[238L] ctx add = 7fc1a1e0
NOTICE: [scpi_set_css_power_state]:[100L] domain_cluster=0x3
NOTICE: [scpi_set_css_power_state]:[113L] domain_cluster=0x3

0020:?AB84
NOTICE: [psci_afflvl_power_on_finish]:[496L]
NOTICE: [cm_prepare_el3_exit]:[254L] read_tpidr_el3 = 7fc1bc40
NOTICE: [cm_prepare_el3_exit]:[298L] ctx add = 7fc1a1e0
NOTICE: [psci_afflvl_power_on_finish]:[557L]

002007?0
NOTICE: [psci_smc_handler]:[297L] PSCI_CPU_ON_AARCH64 CALL
NOTICE: [psci_smc_handler]:[298L] x1=0x20103 x2=0x2007f0 x3=0x0
NOTICE: [cm_init_context]:[238L] ctx add = 7fc1a3f0
NOTICE: [scpi_set_css_power_state]:[100L] domain_cluster=0x3
NOTICE: [scpi_set_css_power_state]:[113L] domain_cluster=0x3

0020:?AB84
NOTICE: [psci_afflvl_power_on_finish]:[496L]
NOTICE: [cm_prepare_el3_exit]:[254L] read_tpidr_el3 = 7fc1bcc0
NOTICE: [cm_prepare_el3_exit]:[298L] ctx add = 7fc1a3f0
NOTICE: [psci_afflvl_power_on_finish]:[557L]

002007?0
NOTICE: [psci_smc_handler]:[297L] PSCI_CPU_ON_AARCH64 CALL
NOTICE: [psci_smc_handler]:[298L] x1=0x20200 x2=0x2007f0 x3=0x0
NOTICE: [cm_init_context]:[238L] ctx add = 7fc1a600
NOTICE: [scpi_set_css_power_state]:[100L] domain_cluster=0x3
NOTICE: [scpi_set_css_power_state]:[113L] domain_cluster=0x7

0020:?AB84
NOTICE: [psci_afflvl_power_on_finish]:[496L]
NOTICE: [cm_prepare_el3_exit]:[254L] read_tpidr_el3 = 7fc1bd40
NOTICE: [cm_prepare_el3_exit]:[298L] ctx add = 7fc1a600
NOTICE: [psci_afflvl_power_on_finish]:[557L]

002007?0
NOTICE: [psci_smc_handler]:[297L] PSCI_CPU_ON_AARCH64 CALL
NOTICE: [psci_smc_handler]:[298L] x1=0x20201 x2=0x2007f0 x3=0x0
NOTICE: [cm_init_context]:[238L] ctx add = 7fc1a810
NOTICE: [scpi_set_css_power_state]:[100L] domain_cluster=0x7
NOTICE: [scpi_set_css_power_state]:[113L] domain_cluster=0x7

0020:?AB84
NOTICE: [psci_afflvl_power_on_finish]:[496L]
NOTICE: [cm_prepare_el3_exit]:[254L] read_tpidr_el3 = 7fc1bdc0
NOTICE: [cm_prepare_el3_exit]:[298L] ctx add = 7fc1a810
NOTICE: [psci_afflvl_power_on_finish]:[557L]

002007?0
NOTICE: [psci_smc_handler]:[297L] PSCI_CPU_ON_AARCH64 CALL
NOTICE: [psci_smc_handler]:[298L] x1=0x20202 x2=0x2007f0 x3=0x0
NOTICE: [cm_init_context]:[238L] ctx add = 7fc1aa20
NOTICE: [scpi_set_css_power_state]:[100L] domain_cluster=0x7
NOTICE: [scpi_set_css_power_state]:[113L] domain_cluster=0x7

0020:?AB84
NOTICE: [psci_afflvl_power_on_finish]:[496L]
NOTICE: [cm_prepare_el3_exit]:[254L] read_tpidr_el3 = 7fc1be40
NOTICE: [cm_prepare_el3_exit]:[298L] ctx add = 7fc1aa20
NOTICE: [psci_afflvl_power_on_finish]:[557L]

002007?0
NOTICE: [psci_smc_handler]:[297L] PSCI_CPU_ON_AARCH64 CALL
NOTICE: [psci_smc_handler]:[298L] x1=0x20203 x2=0x2007f0 x3=0x0
NOTICE: [cm_init_context]:[238L] ctx add = 7fc1ac30
NOTICE: [scpi_set_css_power_state]:[100L] domain_cluster=0x7
NOTICE: [scpi_set_css_power_state]:[113L] domain_cluster=0x7

0020:?AB84
NOTICE: [psci_afflvl_power_on_finish]:[496L]
NOTICE: [cm_prepare_el3_exit]:[254L] read_tpidr_el3 = 7fc1bec0
NOTICE: [cm_prepare_el3_exit]:[298L] ctx add = 7fc1ac30
NOTICE: [psci_afflvl_power_on_finish]:[557L]

002007?0
NOTICE: [psci_smc_handler]:[297L] PSCI_CPU_ON_AARCH64 CALL
NOTICE: [psci_smc_handler]:[298L] x1=0x20300 x2=0x2007f0 x3=0x0
NOTICE: [cm_init_context]:[238L] ctx add = 7fc1ae40
NOTICE: [scpi_set_css_power_state]:[100L] domain_cluster=0x7
NOTICE: [scpi_set_css_power_state]:[113L] domain_cluster=0xf

0020:?AB84
NOTICE: [psci_afflvl_power_on_finish]:[496L]
NOTICE: [cm_prepare_el3_exit]:[254L] read_tpidr_el3 = 7fc1bf40
NOTICE: [cm_prepare_el3_exit]:[298L] ctx add = 7fc1ae40
NOTICE: [psci_afflvl_power_on_finish]:[557L]

002007?0
NOTICE: [psci_smc_handler]:[297L] PSCI_CPU_ON_AARCH64 CALL
NOTICE: [psci_smc_handler]:[298L] x1=0x20301 x2=0x2007f0 x3=0x0
NOTICE: [cm_init_context]:[238L] ctx add = 7fc1b050
NOTICE: [scpi_set_css_power_state]:[100L] domain_cluster=0xf
NOTICE: [scpi_set_css_power_state]:[113L] domain_cluster=0xf

0020:?AB84
NOTICE: [psci_afflvl_power_on_finish]:[496L]
NOTICE: [cm_prepare_el3_exit]:[254L] read_tpidr_el3 = 7fc1bfc0
NOTICE: [cm_prepare_el3_exit]:[298L] ctx add = 7fc1b050
NOTICE: [psci_afflvl_power_on_finish]:[557L]

002007?0
NOTICE: [psci_smc_handler]:[297L] PSCI_CPU_ON_AARCH64 CALL
NOTICE: [psci_smc_handler]:[298L] x1=0x20302 x2=0x2007f0 x3=0x0
NOTICE: [cm_init_context]:[238L] ctx add = 7fc1b260
NOTICE: [scpi_set_css_power_state]:[100L] domain_cluster=0xf
NOTICE: [scpi_set_css_power_state]:[113L] domain_cluster=0xf

0020:?AB84
NOTICE: [psci_afflvl_power_on_finish]:[496L]
NOTICE: [cm_prepare_el3_exit]:[254L] read_tpidr_el3 = 7fc1c040
NOTICE: [cm_prepare_el3_exit]:[298L] ctx add = 7fc1b260
NOTICE: [psci_afflvl_power_on_finish]:[557L]

002007?0
NOTICE: [psci_smc_handler]:[297L] PSCI_CPU_ON_AARCH64 CALL
NOTICE: [psci_smc_handler]:[298L] x1=0x20303 x2=0x2007f0 x3=0x0
NOTICE: [cm_init_context]:[238L] ctx add = 7fc1b470
NOTICE: [scpi_set_css_power_state]:[100L] domain_cluster=0xf
NOTICE: [scpi_set_css_power_state]:[113L] domain_cluster=0xf

0020:?AB84
NOTICE: [psci_afflvl_power_on_finish]:[496L]
NOTICE: [cm_prepare_el3_exit]:[254L] read_tpidr_el3 = 7fc1c0c0
NOTICE: [cm_prepare_el3_exit]:[298L] ctx add = 7fc1b470
NOTICE: [psci_afflvl_power_on_finish]:[557L]

002007?0
CPU1: Booted secondary processor
Detected PIPT I-cache on CPU1
CPU1: found redistributor 20001 region 0:0x000000008d130000
CPU1: using LPI pending table @0x00000000579e0000
CPU2: Booted secondary processor
Detected PIPT I-cache on CPU2
CPU2: found redistributor 20002 region 0:0x000000008d160000
CPU2: using LPI pending table @0x0000000057a10000
CPU3: Booted secondary processor
Detected PIPT I-cache on CPU3
CPU3: found redistributor 20003 region 0:0x000000008d190000
CPU3: using LPI pending table @0x0000000057a80000
CPU4: Booted secondary processor
Detected PIPT I-cache on CPU4
CPU4: found redistributor 20100 region 0:0x000000008d1c0000
CPU4: using LPI pending table @0x0000000057ad0000
CPU5: Booted secondary processor
Detected PIPT I-cache on CPU5
CPU5: found redistributor 20101 region 0:0x000000008d1f0000
CPU5: using LPI pending table @0x0000000057b30000
CPU6: Booted secondary processor
Detected PIPT I-cache on CPU6
CPU6: found redistributor 20102 region 0:0x000000008d220000
CPU6: using LPI pending table @0x0000000057bb0000
CPU7: Booted secondary processor
Detected PIPT I-cache on CPU7
CPU7: found redistributor 20103 region 0:0x000000008d250000
CPU7: using LPI pending table @0x0000000057400000
CPU8: Booted secondary processor
Detected PIPT I-cache on CPU8
CPU8: found redistributor 20200 region 0:0x000000008d280000
CPU8: using LPI pending table @0x0000000057460000
CPU9: Booted secondary processor
Detected PIPT I-cache on CPU9
CPU9: found redistributor 20201 region 0:0x000000008d2b0000
CPU9: using LPI pending table @0x00000000574e0000
CPU10: Booted secondary processor
Detected PIPT I-cache on CPU10
CPU10: found redistributor 20202 region 0:0x000000008d2e0000
CPU10: using LPI pending table @0x0000000057540000
CPU11: Booted secondary processor
Detected PIPT I-cache on CPU11
CPU11: found redistributor 20203 region 0:0x000000008d310000
CPU11: using LPI pending table @0x0000000057590000
CPU12: Booted secondary processor
Detected PIPT I-cache on CPU12
CPU12: found redistributor 20300 region 0:0x000000008d340000
CPU12: using LPI pending table @0x0000000057610000
CPU13: Booted secondary processor
Detected PIPT I-cache on CPU13
CPU13: found redistributor 20301 region 0:0x000000008d370000
CPU13: using LPI pending table @0x0000000057670000
CPU14: Booted secondary processor
Detected PIPT I-cache on CPU14
CPU14: found redistributor 20302 region 0:0x000000008d3a0000
CPU14: using LPI pending table @0x00000000576d0000
CPU15: Booted secondary processor
Detected PIPT I-cache on CPU15
CPU15: found redistributor 20303 region 0:0x000000008d3d0000
CPU15: using LPI pending table @0x0000000057730000
Brought up 16 CPUs
SMP: Total of 16 processors activated.
CPU: All CPU(s) started at EL2
alternatives: patching kernel code
devtmpfs: initialized
DMI not present or invalid.
clocksource jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
NET: Registered protocol family 16
cpuidle: using governor ladder
cpuidle: using governor menu
vdso: 2 pages (1 code @ ffffffc000a95000, 1 data @ ffffffc000a94000)
hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
DMA: preallocated 256 KiB pool for atomic allocations
Serial: AMBA PL011 UART driver
hisi-djtag peripherals:djtag@0: djtag init successfully.
ACPI: Interpreter disabled.
vgaarb: loaded
21,ffffffc00021c834
Switched to clocksource arch_sys_counter
pnp: PnP ACPI: disabled
NET: Registered protocol family 2
TCP established hash table entries: 16384 (order: 5, 131072 bytes)
TCP bind hash table entries: 16384 (order: 7, 524288 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
UDP hash table entries: 1024 (order: 4, 98304 bytes)
UDP-Lite hash table entries: 1024 (order: 4, 98304 bytes)
NET: Registered protocol family 1
Trying to unpack rootfs image as initramfs...
Freeing initrd memory: 358400K (ffffffc007000000 - ffffffc01ce00000)
LLC: /peripherals/llc@0 is initialized.
mem add: Die2 start:0x0, size:0x80000000
mem add: Die2 start:0x1000000000, size:0x200000000
mem add: Die2 start:0x200000000, size:0x100000000
mem add: Die2 start:0x300000000, size:0x100000000
LLC: mem [0x0, 0x80000000) @die2 @region0
LLC: mem [0x200000000, 0x400000000) @die2 @region1
LLC: mem [0x1000000000, 0x1200000000) @die2 @Region2
futex hash table entries: 4096 (order: 6, 262144 bytes)
audit: initializing netlink subsys (disabled)
audit: type=2000 audit(2.812:1): initialized
HugeTLB registered 2 MB page size, pre-allocated 0 pages
squashfs: version 4.0 (2009/01/31) Phillip Lougher
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
io scheduler noop registered
io scheduler cfq registered (default)
Serial: AMBA driver
Unable to detect cache hierarcy from DT for CPU 0
brd: module loaded
loop: module loaded
NET: Registered protocol family 17
bootconsole [uart0] disabled
WARNING: Unimplemented Private SMC Call: 0x83000004

0050?:<4

You are trying to access a restricted zone. Only Authorized Users allowed.
HI1610_ROUTER login: root
Password:

Hello! Welcome to RTOS!

HI1610_ROUTER ~ #
HI1610_ROUTER ~ # cat /proc/uptime
9.10 85.11
HI1610_ROUTER ~ # ifconfig eth0 128.20.120.123
ifconfig: SIOCSIFADDR: No such device
HI1610_ROUTER ~ # unset TMOUT
HI1610_ROUTER ~ # cat /proc/uptime
12.00 97.80
ROUTER ~ # cat /proc/cmdline
console=ttyS0,115200 earlycon=uart8250,mmio32,0x80300000 initrd=0x7000000,350M cetartlb=0x40000000%0x1100000000 kbox_mem=16M@0x1080000000 ekbox=0x80000$0x1081000000 mtrc=0x1000000%0x1140000000 isolcpus=4-15 nohz_full=4-15 crashkernel=512M@1532M kmemleak=on
ROUTER ~ #

Sound indicator crashing when changing the volume

I'm on Ubuntu-Mate 16.04.3, using Gnome's sound indicator. When I change the music volume using the app it crashes my sound inicator and I can't use the slide or the buttons.

segfault due to GTK2 upgrade Arch Linux

Receiving a segfault on Arch Linux with GTK2 2..24.26-1. Downgrading to 2.24.25-1 still works:
https://aur.archlinux.org/packages/spotify/

First run maxes out system sound

Basically lets say that my sound on my machine is set to 34%. When I install Spotify for Linux, without issue, I go and log in and I have no issues. And once I start a song, my sound jumps to 100%. Only seems to do this on first time run, and not on reboot or restart of the application. At first I thought it was a bug, but this is the second time it happened to me today (since I just signed up for spotify and installed it to my work and personal workstation).

OS: Debian 8

When clicking Log In With Facebook on Ubuntu, Spotify crashes or I receive the Opps login error

Error here: https://www.spotify.com/us/static/login-error/
Running Ubuntu 16.04 LTS

Recommend Projects

React

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

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

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

An Open Source Machine Learning Framework for Everyone
Django

The Web framework for perfectionists with deadlines.
Laravel

A PHP framework for web artisans
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.
Visualization

Some thing interesting about visualization, use data art
Game

Some thing interesting about game, make everyone happy.

Recommend Org

Facebook

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

Open source projects and samples from Microsoft.
Google

Google ❤️ Open Source for everyone.
Alibaba

Alibaba Open Source for everyone
D3

Data-Driven Documents codes.
Tencent

China tencent open source team.