Linaro-acpi July 2015

linaro-acpi@lists.linaro.org

27 participants
36 discussions

leg-kernel tag leg-20150716.0 released

by Graeme Gregory

The leg-kernel release has been made and tagged as leg-20150716.0 This is based on mainline kernel v4.2-rc2 Repository : http://git.linaro.org/leg/acpi/leg-kernel.git Direct Link: http://git.linaro.org/leg/acpi/leg-kernel.git/commit/d5bb60a53ff133e8d6feec… Notes :- 1) This release has re-introduces APM Mustang support from Redhat!

8 years, 9 months

APM Mustang topic branch

by Itaru Kitayama

Hi, Build of the topic branch fails with an error: CHK include/config/kernel.release CHK include/generated/uapi/linux/version.h CHK include/generated/utsrelease.h CHK include/generated/bounds.h CHK include/generated/timeconst.h CHK include/generated/asm-offsets.h CALL scripts/checksyscalls.sh CHK include/generated/compile.h CC arch/arm64/kernel/setup.o arch/arm64/kernel/setup.c: In function ‘arm64_spcr_setup’: arch/arm64/kernel/setup.c:603:3: error: implicit declaration of function ‘acpi_setup_spcr’ [-Werror=implicit-function-declaration] acpi_setup_spcr(); ^ cc1: some warnings being treated as errors scripts/Makefile.build:258: recipe for target 'arch/arm64/kernel/setup.o' failed make[1]: *** [arch/arm64/kernel/setup.o] Error 1 Makefile:943: recipe for target 'arch/arm64/kernel' failed make: *** [arch/arm64/kernel] Error 2

8 years, 9 months

[PATCH v6 0/8] Watchdog: introduce ARM SBSA watchdog driver

by fu.wei＠linaro.org

From: Fu Wei <fu.wei(a)linaro.org> This patchset: (1)Introduce Documentation/devicetree/bindings/watchdog/sbsa-gwdt.txt for FDT info of SBSA Generic Watchdog, and give two examples of adding SBSA Generic Watchdog device node into the dts files: foundation-v8.dts and amd-seattle-soc.dtsi. (2)Introduce "pretimeout" into the watchdog framework, and update Documentation/watchdog/watchdog-kernel-api.txt to introduce: (1)the new elements in the watchdog_device and watchdog_ops struct; (2)the new API "watchdog_init_timeouts". (3)Introduce ARM SBSA watchdog driver: a.Use linux kernel watchdog framework; b.Work with FDT on ARM64; c.Use "pretimeout" in watchdog framework; d.Support getting timeout and pretimeout from parameter and FDT at the driver init stage. e.In the first timeout, do panic to save system context; f.In the second stage, user can still feed the dog without cleaning WS0. By this feature, we can avoid the panic infinite loops, while backing up a large system context in a server. g.In the second stage, can trigger WS1 by setting pretimeout = 0 if necessary. (4)Introduce ACPI GTDT parser: drivers/acpi/gtdt.c Parse SBSA Generic Watchdog Structure in GTDT table of ACPI, and create a platform device with that information. This platform device can be used by This Watchdog driver. drivers/clocksource/arm_arch_timer.c is simplified by this GTDT support. This patchset has been tested with watchdog daemon (ACPI/FDT, module/build-in) on the following platforms: (1)ARM Foundation v8 model Changelog: v6: Improve the dtb example files: reduce the register frame size to 4K. Improve pretimeout support: (1) improve watchdog_init_timeouts function (2) rename watchdog_check_min_max_timeouts back to the original name (1) improve watchdog_timeout_invalid/watchdog_pretimeout_invalid Add the new features in the sbsa_gwdt driver: (1) In the second stage, user can feed the dog without cleaning WS0. (2) In the second stage, user can trigger WS1 by setting pretimeout = 0. (3) expand the max value of pretimeout, in case 10 second is not enough for a kdump kernel reboot in panic. v5: Improve pretimeout support: (1)fix typo in documentation and comments. (2)fix the timeout limits validation bug. Simplify sbsa_gwdt driver: (1)integrate all the registers access functions into caller. v4: Refactor GTDT support code: remove it from arch/arm64/kernel/acpi.c, put it into drivers/acpi/gtdt.c file. Integrate the GTDT code of drivers/clocksource/arm_arch_timer.c into drivers/acpi/gtdt.c. Improve pretimeout support, fix "pretimeout == 0" problem. Simplify sbsa_gwdt driver: (1)timeout/pretimeout limits setup; (2)keepalive function; (3)delete "clk == 0" check; (4)delete WS0 status bit check in interrupt routine; (5)sbsa_gwdt_set_wcv function. v3: Delete "export arch_timer_get_rate" patch. Driver back to use arch_timer_get_cntfrq. Improve watchdog_init_timeouts function and update relevant documentation. Improve watchdog_timeout_invalid and watchdog_pretimeout_invalid. Improve foundation-v8.dts: delete the unnecessary tag of device node. Remove "ARM64 || COMPILE_TEST" from Kconfig. Add comments in arch/arm64/kernel/acpi.c Fix typoes and incorrect comments. v2: Improve watchdog-kernel-api.txt documentation for pretimeout support. Export "arch_timer_get_rate" in arm_arch_timer.c. Add watchdog_init_timeouts API for pretimeout support in framework. Improve suspend and resume foundation in driver Improve timeout/pretimeout values init code in driver. Delete unnecessary items of the sbsa_gwdt struct and #define. Delete all unnecessary debug info in driver. Fix 64bit division bug. Use the arch_timer interface to get watchdog clock rate. Add MODULE_DEVICE_TABLE for platform device id. Fix typoes. v1: The first version upstream patchset to linux mailing list. Fu Wei (8): Documentation: add sbsa-gwdt.txt documentation ARM64: add SBSA Generic Watchdog device node in foundation-v8.dts ARM64: add SBSA Generic Watchdog device node in amd-seattle-soc.dtsi Watchdog: introdouce "pretimeout" into framework Watchdog: introduce ARM SBSA watchdog driver ACPI: add GTDT table parse driver into ACPI driver Watchdog: enable ACPI GTDT support for ARM SBSA watchdog driver clocksource: simplify ACPI code in arm_arch_timer.c .../devicetree/bindings/watchdog/sbsa-gwdt.txt | 36 ++ Documentation/watchdog/watchdog-kernel-api.txt | 47 ++- arch/arm64/boot/dts/amd/amd-seattle-soc.dtsi | 11 + arch/arm64/boot/dts/arm/foundation-v8.dts | 10 + arch/arm64/kernel/time.c | 4 +- drivers/acpi/Kconfig | 9 + drivers/acpi/Makefile | 1 + drivers/acpi/gtdt.c | 180 ++++++++ drivers/clocksource/Kconfig | 1 + drivers/clocksource/arm_arch_timer.c | 60 +-- drivers/watchdog/Kconfig | 15 + drivers/watchdog/Makefile | 1 + drivers/watchdog/sbsa_gwdt.c | 455 +++++++++++++++++++++ drivers/watchdog/watchdog_core.c | 98 +++-- drivers/watchdog/watchdog_dev.c | 53 +++ include/clocksource/arm_arch_timer.h | 8 + include/linux/acpi.h | 5 + include/linux/clocksource.h | 4 +- include/linux/watchdog.h | 39 +- 19 files changed, 947 insertions(+), 90 deletions(-) create mode 100644 Documentation/devicetree/bindings/watchdog/sbsa-gwdt.txt create mode 100644 drivers/acpi/gtdt.c create mode 100644 drivers/watchdog/sbsa_gwdt.c -- 1.9.1

8 years, 9 months

[PATCH 0/2]

by Graeme Gregory

Hi Al, Please take these as bug reports to Redhat maintained patches. I am unsure of the correct fixes in these cases. I have pushed these to the mustang topic branch and will push the SPCR one to the other topics as well. Thanks Graeme

8 years, 9 months

Garantizamos las mejores vacaciones de invierno!

by paula

Garantizamos las mejores vacaciones de invierno! Llegan las vacaciones y comienza el frío, pero en xtop te preparamos la mejor variedad en Juegos X-box360 – Ps3 – Series – Peliculas – Programas – Musica en MP3 Y DVD´S "Invierno 2015" Los mejores juegos.. 2015 todo lo nuevo. METAL GEAR SOLID V GROUND ZEROES Juego en Ps3 y X-box 360 MORTAL KOMBAT X juego de PC BATTLEFIELD HARDLINE Juego en Ps3 - X-box 360- PC DRAGON BALL XENOVERSE Juego en Ps3 - X-box 360 RESIDENT EVIL REVELATIONS 2 Juego en Ps3 - X-box 360 CALL OF DUTY BLACK OPS Juego en Ps3 - X-box 360 - PC y WII PRO EVOLUTION SOCCER 2016 Lo mejor de Cartelera de cine de la semana! CENICIENTA (2015) Tambien disponible en BLU-RAY CHAPPIE disponible también en BLU-RAY HOME (HOGAR DULCE HOGAR) INSURGENTE INTENSAMENTE JURASSIC WORLD (JURASSIC PARK IV) LOS JUEGOS DEL HAMBRE 2: EN LLAMAS LOS VENGADORES 2 (AVENGERS ERA DE ULTRON) (THE AVENGERS AGE OF ULTRON) MINIONS POLTERGEIST (JUEGOS DIABOLICOS) RAPIDOS Y FURIOSOS 7 SPY UNA ESPIA DESPISTADA TED 2 TERMINATOR 5 GENESIS TERREMOTO LA FALLA DE SAN ANDRES TOMORROWLAND EL MUNDO DEL MAÑANA Las mejores series para disfrutar estas vacaciones GAME OF THRONES FEAR THE WALKING DEAD ORANGE IS THE NEW BLACK WAYWARD PINES TEEN WOLF DRAGON BALL SUPE LOS CABALLEROS DEL ZODIACO ALMA DORADA En vacaciones de invierno, diversión asegurada con Xtop

8 years, 9 months

leg-kernel tag leg-20150710.2 released

by Graeme Gregory

The leg-kernel release has been made and tagged as leg-20150710.2 This is based on mainline kernel v4.2-rc1 Repository : http://git.linaro.org/leg/acpi/leg-kernel.git Direct Link: http://git.linaro.org/leg/acpi/leg-kernel.git/commit/d8a87deca34b7542853511… Notes :-

8 years, 9 months

[PATCH v2 0/9] Add self-probe infrastructure and stacked irqdomain support for ACPI based GICv2/3 init

by Hanjun Guo

This patch set introduce self-probe infrastructure to init IRQ controllers and stacked irqdomain support for ACPI based GICv2/3 init. The self-probe infrastructure for ACPI GIC init is similar as IRQCHIP_DECLARE() and based on the GIC version support in ACPI MADT table. we match the GIC version and GIC driver and load it. We introduce acpi_irq_domain for GICv2/3 core domain to support stacked irqdomain, and pass the gsi (global system interrupt) as the agument (void *arg) for gic_irq_domain_alloc(), then we can alloc virqs via acpi_register_gsi() with stacked irqdomain. The stacked irq domain will be: acpi_irq_domain == gicv2 or gicv3 core domain ^ | (parent) | ITS domain or GIv2m domain ^ | | MSI chip irq domain Since there is one GICD supported for now, so there will be only one irqdomain created when GICv2/3 initialized, for all the wired hardware irqs for PPI, SGI and SPI, they will have unique hardware irq number (GSI), so we can match the device to the acpi_irq_domain with unique GSI and it will work. If there will be multi GICD in the future, this will still works to follow the solution for x86 of ACPI (mutil IOAPICs). Note: patch 1~2 already merged in ACPICA core, I just send them out for helping of better understanding later 7 patches. Any comments are warmly welcomed. update from RFC version: - Consolidate all the GIC init code into drivers/irqchip/irq-gic-acpi.c v1->v2: - Remove the gicv2/v3 related driver code in drivers/irqchip/irq-gic-acpi.c which I was trying to consolidate them in one file, then arm-gic.h and arm-gic-v3.h will be used separately within parent driver only - Drop the gsi_mutex patch - Use the GIC version to match the GIC driver, then no need to test for the version in each driver - Move acpi_irq_init() to drivers/irqchip/irq-gic-acpi.c instead of in drivers/acpi/irq.c. maybe we need to rename acpi_irq_init() as acpi_gic_init() but I keep that name to accommodate of_irq_init(), any objections please let me know. Bob Moore (1): ACPICA: ACPI 6.0: Add changes for MADT table. Hanjun Guo (6): ACPICA: ACPI 6.0: Add values for MADT GIC version field. irqchip / GIC: Add GIC version support in ACPI MADT ACPI / irqchip: Add self-probe infrastructure to initialize IRQ controller irqchip / GIC / ACPI: Use IRQCHIP_ACPI_DECLARE to simplify GICv2 init code irqchip / gic: Add stacked irqdomain support for ACPI based GICv2 init irqchip / GICv3: Add stacked irqdomain support for ACPI based init Tomasz Nowicki (2): irqchip / GICv3: Refactor gic_of_init() for GICv3 driver irqchip / GICv3: Add ACPI support for GICv3+ initialization arch/arm64/Kconfig | 1 + arch/arm64/include/asm/acpi.h | 1 - arch/arm64/include/asm/irq.h | 13 -- arch/arm64/kernel/acpi.c | 25 ---- drivers/acpi/gsi.c | 28 ++-- drivers/irqchip/Kconfig | 3 + drivers/irqchip/Makefile | 1 + drivers/irqchip/irq-gic-acpi.c | 141 +++++++++++++++++++ drivers/irqchip/irq-gic-v3.c | 264 ++++++++++++++++++++++++++++------- drivers/irqchip/irq-gic.c | 35 ++--- drivers/irqchip/irqchip.h | 12 ++ include/acpi/actbl1.h | 33 ++++- include/asm-generic/vmlinux.lds.h | 13 ++ include/linux/acpi.h | 16 +++ include/linux/acpi_irq.h | 4 +- include/linux/irqchip/arm-gic-acpi.h | 10 +- include/linux/mod_devicetable.h | 8 ++ 17 files changed, 473 insertions(+), 135 deletions(-) create mode 100644 drivers/irqchip/irq-gic-acpi.c -- 1.9.1

8 years, 9 months

[PATCH v6 0/7] CPUFreq driver using CPPC methods

by Ashwin Chaugule

CPPC: ==== CPPC (Collaborative Processor Performance Control) is a new way to control CPU performance using an abstract continous scale as against a discretized P-state scale which is tied to CPU frequency only. It is defined in the ACPI 5.0+ spec. In brief, the basic operation involves: - OS makes a CPU performance request. (Can provide min and max tolerable bounds) - Platform (such as BMC) is free to optimize request within requested bounds depending on power/thermal budgets etc. - Platform conveys its decision back to OS The communication between OS and platform occurs through another medium called (PCC) Platform communication Channel. This is a generic mailbox like mechanism which includes doorbell semantics to indicate register updates. See drivers/mailbox/pcc.c This patchset introduces a CPPC based CPUFreq driver that works with existing governors such as ondemand. The CPPC table parsing and the CPPC communication semantics are abstracted into separate files to allow future CPPC based drivers to implement their own governors if required. Initial patchsets included an adaptation of the PID governor from intel_pstate.c. However recent experiments led to extensive modifications of the algorithm to calculate CPU busyness. Until it is verified that these changes are worthwhile, the existing governors should provide for a good enough starting point for ARM64 servers. Finer details about the PCC and CPPC spec are available in the latest ACPI 5.1 specification.[2] Testing: ======= This was tested on an SBSA compatible ARMv8 server with CPPCv2 firmware running on a remote processor. I verified that each CPUs performance limits were detected and that new performance requests were made by the on-demand governor proportional to the load on each CPU. I also verified that using the acpi_processor driver correctly maps the physical CPU ids to logical CPU ids, which helps in picking up the proper _CPC details from a processor object, in the case where CPU physical ids may not be contiguous. Changes since V5: - Checkpatch cleanups. - Change pss_init to pss_perf_init. Rec by Srinivas Pandruvada. - Explicit comment explaining why postcore_initcall to pcc mailbox. - Fold acpi_processor_syscore_init/exit into CONFIG_ACPI_CST. - Added patch with dummy functions used by ACPI_HOTPLUG_CPU. Changes since V4: - Misc cleanups. Addressed feedback from Rafael. - Made acpi_processor.c independent of C-states, P-states and others. - Per CPU scanning for _CPC is now made from acpi_processor.c - Added new Kconfig options for legacy C states and P states to enable future support for newer alternatives as defined in the ACPI spec 6.0. Changes since V3: - Split CPPC backend methods into separate files. - Add frontend driver which plugs into existing CPUfreq governors. - Simplify PCC driver by moving communication space mapping and read/write into client drivers. Changes since V2: - Select driver if !X86, since intel_pstate will use HWP extensions instead. - Added more comments. - Added Freq domain awareness and PSD parsing. Changes since V1: - Create a new driver based on Dirks suggestion. - Fold in CPPC backend hooks into main driver. Changes since V0: [1] - Split intel_pstate.c into a generic PID governor and platform specific backend. - Add CPPC accessors as PID backend. [1] - http://lwn.net/Articles/608715/ [2] - http://www.uefi.org/sites/default/files/resources/ACPI_5_1release.pdf [3] - https://patches.linaro.org/40705/ Ashwin Chaugule (7): PCC: Initialize PCC Mailbox earlier at boot ACPI: Make ACPI processor driver more extensible ACPI: Introduce CPU performance controls using CPPC CPPC: Add a CPUFreq driver for use with CPPC CPPC: Probe for CPPC tables for each ACPI Processor object PCC: Enable PCC only when needed ACPI: Add weak routines for ACPI CPU Hotplug drivers/acpi/Kconfig | 48 ++- drivers/acpi/Makefile | 8 +- drivers/acpi/acpi_processor.c | 18 + drivers/acpi/cppc_acpi.c | 812 ++++++++++++++++++++++++++++++++++++++++ drivers/acpi/processor_driver.c | 90 +++-- drivers/cpufreq/Kconfig | 2 +- drivers/cpufreq/Kconfig.arm | 16 + drivers/cpufreq/Kconfig.x86 | 2 + drivers/cpufreq/Makefile | 2 + drivers/cpufreq/cppc_cpufreq.c | 197 ++++++++++ drivers/mailbox/Kconfig | 2 +- drivers/mailbox/pcc.c | 8 +- include/acpi/cppc_acpi.h | 137 +++++++ include/acpi/processor.h | 129 +++++-- 14 files changed, 1397 insertions(+), 74 deletions(-) create mode 100644 drivers/acpi/cppc_acpi.c create mode 100644 drivers/cpufreq/cppc_cpufreq.c create mode 100644 include/acpi/cppc_acpi.h -- 1.9.1

8 years, 9 months

[RFC PATCH 0/7] ACPI IORT (connections of PCI, devices, ITS and SMMU)

by Itaru Kitayama

Hi, My test of your tree (HEAD as of today) on Mustang fails; see below. Any ideas? Welcome to Fedora 22 (Twenty Two)! [ 7.456756] systemd-sysv-generator[296]: Overwriting existing symlink /run/systemd/generator.late/netconsole.service with real service [ 7.469266] systemd-sysv-generator[296]: Overwriting existing symlink /run/systemd/generator.late/network.service with real service [ 8.494106] audit_printk_skb: 66 callbacks suppressed [ 8.499153] audit: type=1130 audit(1436005219.430:33): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-journald comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' [ 8.518089] audit: type=1131 audit(1436005219.450:34): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-journald comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' [ OK [ 8.538985] audit: type=1130 audit(1436005219.470:35): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=initrd-switch-root comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' ] Stopped Switch[ 8.559297] audit: type=1131 audit(1436005219.490:36): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=initrd-switch-root comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Root. Starting Create list of required st... nodes for the current kernel... [ OK ] Stopped target Switch Root. Mounting POSIX Message Queue File System... Mounting Temporary Directory... Starting Apply Kernel V[ 8.881520] audit: type=1130 audit(1436005219.820:37): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-fsck@dev-disk-by\x2duuid-3e3fef70\x2d40b1\x2d4079\x2d8611\x2d0e0fc2de0eea comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' ariables... [ audit: type=1131 audit(1436005219.840:38): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-fsck@dev-disk-by\x2duuid-3e3fef70\x2d40b1\x2d4079\x2d8611\x2d0e0fc2de0eea comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' [32m OK ] Listening on udev Kernel Socket. [ OK ] Listening on udev Control Socket. [ OK ] Stopped File System Check on /dev/d...f70-40b1-4079-8611-0e0fc2de0eea. Stopping File System Check on /dev/...0-40b1-4079-8611-0e0fc2de0eea... Starting File System Check on Root Device... [ OK ] Created slice User and Session Slice. [ OK ] Created slice system-getty.slice. Mounting NFSD configuration filesystem... [ OK ] Created slice system-serial\x2dgetty.slice. [ OK ] Stopped target Initrd File Systems. [ OK ] Reached target Encrypted Volumes. Mounting Debug File System... [ OK ] Reached target Slices. [ OK ] Listening on Delayed Shutdown Socket. [ OK ] Stopped target Initrd Root File System. Mounting Huge Pages File System... [ OK ] Listening on LVM2 metadata daemon socket. [ OK ] Reached target Paths. [ OK ] Listening on /dev/initctl Compatibility Named Pipe. [ OK[ 9.039605] audit: type=1130 audit(1436005219.970:39): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-journald comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' ] Listenin[ 9.058875] audit: type=1131 audit(1436005219.990:40): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-journald comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' g on Device-mapper event daemon FIFOs. Starting Monitoring of LVM2 mirrors... dmeventd or progress polling... [ OK ] Set up automount Arbitrary Executab...ats File System Automount Point. Starting Set Up Additional Binary Formats... [ OK ] Stopped Flush Jo[ 9.104997] audit: type=1130 audit(1436005220.040:41): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=kmod-static-nodes comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' urnal to Persistent Storage. [ OK ] Stopped Journal Service. Starting Journal Service... [ OK ] Mounted Huge Pages File System. [ OK ] Mounted POSIX Message Queue File System. [ OK ] Mounted Debug File System. [ OK ] Mounted Temporary Directory. [ OK ] Started Create list of required sta...ce nodes for the current kernel. [ OK [ 9.189881] audit: type=1130 audit(1436005220.120:42): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-sysctl comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' ] Started Apply Kernel Variables. Mounting Arbitrary Executable File Formats File System... [ OK ] Started LVM2 metadata daemon. Starting LVM2 metadata daemon... [ OK ] Started Journal Service. [ 10.062717] Unable to handle kernel paging request at virtual address 42494ea5 [ 10.070036] pgd = fffffe03db4e0000 [ OK [ 10.073524] [42494ea5] *pgd=0000000000000000] Mounted Arbitr, *pud=0000000000000000ary Executable F, *pmd=0000000000000000ile Formats File System. [ 10.087340] Internal error: Oops: 96000006 [#1] SMP [ 10.093122] Modules linked in: binfmt_misc xhci_plat_hcd [ 10.098474] CPU: 0 PID: 317 Comm: systemd-binfmt Not tainted 4.1.0+ #1 [ 10.104977] Hardware name: AppliedMicro Mustang/Mustang, BIOS 1.1.0 Apr 22 2015 [ 10.112261] task: fffffe03db938140 ti: fffffe03dbaac000 task.ti: fffffe03dbaac000 [ 10.119724] PC is at lockref_get+0xc/0xa0 [ 10.123732] LR is at bm_status_write+0x98/0x100 [binfmt_misc] [ 10.129460] pc : [<fffffe0000408e44>] lr : [<fffffdfffc080a08>] pstate: 60000145 [ 10.136826] sp : fffffe03dbaafd70 [ 10.140131] x29: fffffe03dbaafd70 x28: fffffe03dbaac000 [ 10.145453] x27: fffffe00007c2000 x26: 0000000000000040 [ 10.150774] x25: 000000000000011a x24: 0000000000000015 [ 10.156095] x23: 0000000020000000 x22: 000003ff9f500000 [ 10.161415] x21: 0000000042494e4d x20: 0000000000000003 [ 10.166734] x19: 000003ff9f500000 x18: 000003ff9f331ce8 [ 10.172054] x17: 000003ff9f397990 x16: fffffe000021b640 [ 10.177373] x15: 0000000000000008 x14: 000002aacc7ea220 [ 10.182691] x13: 000002aacc7ea3b0 x12: 0000000000000008 [ 10.188011] x11: 0101010101010101 x10: 7f7f7f7f7f7f7f7f [ 10.193330] x9 : fefeff6671646c64 x8 : 0000000000000040 [ 10.198650] x7 : fefefefefefeff09 x6 : 0080808080808080 [ 10.203969] x5 : 8080808080808000 x4 : 000003ff9f500003 [ 10.209287] x3 : 000000000000000a x2 : 0000000000000000 [ 10.214607] x1 : 0000000000000031 x0 : 0000000042494ea5 [ 10.219925] [ 10.221420] Process systemd-binfmt (pid: 317, stack limit = 0xfffffe03dbaac020) [ 10.228704] Stack: (0xfffffe03dbaafd70 to 0xfffffe03dbab0000) [ 10.234437] fd60: dbaafd90 fffffe03 fc080a08 fffffdff [ 10.242590] fd80: 9f500000 000003ff ec0a312d fffffe03 dbaafdc0 fffffe03 0021a570 fffffe00 [ 10.250741] fda0: d4a1e400 fffffe03 00000003 00000000 dbaafec8 fffffe03 0021cdbc fffffe00 [ 10.258892] fdc0: dbaafe50 fffffe03 0021ad5c fffffe00 00000003 00000000 d4a1e400 fffffe03 [ 10.267042] fde0: 9f500000 000003ff dbaafec8 fffffe03 00000003 00000000 d4a1e400 fffffe03 [ 10.275192] fe00: 9f500000 000003ff dbaafec8 fffffe03 20000000 00000000 dbaac000 fffffe03 [ 10.283341] fe20: dbaafe50 fffffe03 0021ad2c fffffe00 00000003 00000000 d4a1e400 fffffe03 [ 10.291492] fe40: 9f500000 000003ff dbaafec8 fffffe03 dbaafe90 fffffe03 0021b694 fffffe00 [ 10.299641] fe60: d4a1e400 fffffe03 d4a1e400 fffffe03 9f500000 000003ff 00000003 00000000 [ 10.307791] fe80: 20000000 00000000 00000015 00000000 dddfa1c0 000003ff 00093a0c fffffe00 [ 10.315941] fea0: 00000200 00000000 9f500000 000003ff ffffffff ffffffff 9f401f38 000003ff [ 10.324091] fec0: ffffffff ffffffff 00000000 00000000 00000004 00000000 9f500000 000003ff [ 10.332241] fee0: 00000003 00000000 00000040 00000000 0000000a 00000000 80808000 80808080 [ 10.340391] ff00: 80808080 00808080 fefeff09 fefefefe 00000040 00000000 71646c64 fefeff66 [ 10.348542] ff20: 7f7f7f7f 7f7f7f7f 01010101 01010101 00000008 00000000 cc7ea3b0 000002aa [ 10.356692] ff40: cc7ea220 000002aa 00000008 00000000 00000000 00000000 9f397990 000003ff [ 10.364842] ff60: 9f331ce8 000003ff 00000003 00000000 9f500000 000003ff cc7d00c0 000002aa [ 10.372991] ff80: 00000003 00000000 cc7e20f0 000002aa cc7d0090 000002aa dddfa310 000003ff [ 10.381141] ffa0: 9f5640e8 000003ff ca777ba8 000002aa 00000000 00000000 dddfa1c0 000003ff [ 10.389291] ffc0: 9f3a2cb0 000003ff dddfa1c0 000003ff 9f401f38 000003ff 20000000 00000000 [ 10.397441] ffe0: 00000004 00000000 00000040 00000000 63616e69 65766974 0000000a 00000000 [ 10.405583] Call trace: [ 10.408030] [<fffffe0000408e44>] lockref_get+0xc/0xa0 [ 10.413075] [<fffffdfffc080a04>] bm_status_write+0x94/0x100 [binfmt_misc] [ 10.419847] [<fffffe000021a56c>] __vfs_write+0x44/0x128 [ 10.425061] [<fffffe000021ad58>] vfs_write+0x98/0x1c8 [ 10.430101] [<fffffe000021b690>] SyS_write+0x50/0xb0 [ 10.435055] Code: d65f03c0 a9be7bfd 910003fd f9000bf3 (f9400001) [ 10.441205] ---[ end trace adb124cde588416e ]--- [FAILED] Failed to start Set Up Additional Binary Formats. See "systemctl status systemd-binfmt.service" for details. [ 10.353640] systemd-fsck[306]: rootfs: clean, 456489/30367744 files, 9706217/121456384 blocks [ OK ] Started File System Check on Root Device. Starting Remount Root and Kernel File Systems... [ 10.747231] random: nonblocking pool is initialized [ 10.950592] nfsd: Unknown symbol boot_tvec_bases (err 0) [FAILED] Failed to mount NFSD configuration filesystem. See "systemctl status proc-fs-nfsd.mount" for details. [DEPEND] Dependency failed for GSSAPI Proxy Daemon. [ 10.997174] EXT4-fs (sda4): re-mounted. Opts: (null) [ OK ] Started Remount Root and Kernel File Systems. Starting udev Coldplug all Devices... Starting Create Static Device Nodes in /dev... Starting Flush Journal to Persistent Storage... Starting Configure read-only root support... [ OK ] Started Monitoring of LVM2 mirrors,...ng dmeventd or progress polling. [ 11.265517] systemd-journald[318]: Received request to flush runtime journal from PID 1 [ OK ] Started udev Coldplug all Devices. [ OK ] Started Create Static Device Nodes in /dev. [ OK ] Reached target Local File Systems (Pre). Starting udev Kernel Device Manager... [ OK ] Started Configure read-only root support. Starting Load/Save Random Seed... [ OK ] Started Load/Save Random Seed. [ OK ] Started udev Kernel Device Manager. [ OK ] Found device /dev/ttyS0. G[ OK ] Found device ST500DM002-1BD142 EFI\x20System\x20Partition. [ OK ] Found device ST500DM002-1BD142 3. [ OK ] Found device ST500DM002-1BD142 3. Activating swap Swap Partition... [ OK ] Found device ST500DM002-1BD142 2. Starting File System Check on /dev/...0-66ce-4e1b-bdb0-e0739f97503e... [ 13.925960] Adding 2047936k swap on /dev/sda3. Priority:-1 extents:1 across:2047936k FS [ OK ] Activated swap Swap Partition. [ OK ] Activated swap /dev/disk/by-uuid/681241d1-7f1f-45db-967c-4d7ee16d3b16. [ OK ] Reached target Swap. [ OK [ 14.332241] audit_printk_skb: 36 callbacks suppressed ] Started File S[ 14.337409] audit: type=1130 audit(1436005225.270:55): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-fsck@dev-disk-by\x2duuid-e12dcd60\x2d66ce\x2d4e1b\x2dbdb0\x2de0739f97503e comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' ystem Check on /dev/d...d60-66ce-4e1b-bdb0-e0739f97503e. Mounting /boot... [ OK ] Started Flush Journal to Persistent Storage. [ 14.412127] audit: type=1130 audit(1436005225.350:56): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-journal-flush comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' [ 14.402377] systemd-fsck[390]: /dev/sda2: Superblock last write time is in the future. [ 14.403179] systemd-fsck[390]: (by less than a day, probably due to the hardware clock being incorrectly set) [ 14.403815] systemd-fsck[390]: /dev/sda2: clean, 71/102400 files, 200975/409600 blocks [ 14.585717] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null) [ OK ] Mounted /boot. Mounting /boot/efi...

8 years, 9 months

APM Mustang topic branch

by Al Stone

Howdy. I've updated the acpi-topic-mustang branch so that it now works properly again (mostly because I needed it to run some experiments and tests). It's basically our acpi.git master plus ports of patches scavenged mostly from the Fedora kernel, some of which may or may not end up in mainline in their present form. Use these patches wisely. They should not be considered final since they have not been accepted upstream. Pretty much everything on the box works. -- ciao, al ----------------------------------- Al Stone Software Engineer Linaro Enterprise Group al.stone(a)linaro.org -----------------------------------

8 years, 9 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Linaro-acpi July 2015