* [PATCH 0/5] linux-yocto: consolidated pull request
@ 2020-05-03 15:44 Bruce Ashfield
2020-05-03 15:44 ` [PATCH 1/5] linux-yocto/5.4: update to v5.4.28 Bruce Ashfield
` (5 more replies)
0 siblings, 6 replies; 64+ messages in thread
From: Bruce Ashfield @ 2020-05-03 15:44 UTC (permalink / raw)
To: richard.purdie; +Cc: openembedded-core, steve
From: Bruce Ashfield <bruce.ashfield@gmail.com>
Hi all,
Here are the -stable updates I've collected since m3 of dunfell. I ran
things through the autobuilder, and no new kernel issues were picked up.
The -dev bump is good for master, while all of the 5.4-stable bumps are
good for both master and dunfell.
Cheers,
Bruce
The following changes since commit 2e11d97b6c95e89aa1f9d3603a966c94c442469e:
oeqa/qemurunner: Clean up failure handling (2020-04-26 14:00:51 +0100)
are available in the Git repository at:
git://git.yoctoproject.org/poky-contrib zedd/kernel
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Bruce Ashfield (5):
linux-yocto/5.4: update to v5.4.28
linux-yocto/5.4: update to v5.4.32
linux-yocto/5.4: update to v5.4.34
linux-yocto/5.4: update to v5.4.38
linux-yocto-dev: bump to v5.7-rc
meta/recipes-kernel/linux/linux-yocto-dev.bb | 2 +-
.../linux/linux-yocto-rt_5.4.bb | 6 ++---
.../linux/linux-yocto-tiny_5.4.bb | 8 +++----
meta/recipes-kernel/linux/linux-yocto_5.4.bb | 22 +++++++++----------
4 files changed, 19 insertions(+), 19 deletions(-)
--
2.19.1
^ permalink raw reply [flat|nested] 64+ messages in thread
* [PATCH 1/5] linux-yocto/5.4: update to v5.4.28
2020-05-03 15:44 [PATCH 0/5] linux-yocto: consolidated pull request Bruce Ashfield
@ 2020-05-03 15:44 ` Bruce Ashfield
2020-05-03 15:44 ` [PATCH 2/5] linux-yocto/5.4: update to v5.4.32 Bruce Ashfield
` (4 subsequent siblings)
5 siblings, 0 replies; 64+ messages in thread
From: Bruce Ashfield @ 2020-05-03 15:44 UTC (permalink / raw)
To: richard.purdie; +Cc: openembedded-core, steve
From: Bruce Ashfield <bruce.ashfield@gmail.com>
Updating linux-yocto/5.4 to the latest korg -stable release that comprises
the following commits:
462afcd6e7ea Linux 5.4.28
7b2cdbd67ff0 staging: greybus: loopback_test: fix potential path truncations
8e79f440edb5 staging: greybus: loopback_test: fix potential path truncation
58ffe6b0245e drm/bridge: dw-hdmi: fix AVI frame colorimetry
c965a0299c61 nvmet-tcp: set MSG_MORE only if we actually have more to send
d3eb4daa333f arm64: smp: fix crash_smp_send_stop() behaviour
6080e0a9d107 arm64: smp: fix smp_send_stop() behaviour
c61417fef99a ALSA: hda/realtek: Fix pop noise on ALC225
163489b64361 futex: Unbreak futex hashing
553d46b07dc4 futex: Fix inode life-time issue
66f28e110565 x86/mm: split vmalloc_sync_all()
9dfed456e1eb page-flags: fix a crash at SetPageError(THP_SWAP)
32991c960d0b mm, slub: prevent kmalloc_node crashes and memory leaks
623515739282 mm: slub: be more careful about the double cmpxchg of freelist
8e709bbe41d6 epoll: fix possible lost wakeup on epoll_ctl() path
69f434a05fb4 mm: do not allow MADV_PAGEOUT for CoW pages
c3f54f0a68bf mm/hotplug: fix hot remove failure in SPARSEMEM|!VMEMMAP case
61cfbcce9e09 mm, memcg: throttle allocators based on ancestral memory.high
77c4bc4bf612 mm, memcg: fix corruption on 64-bit divisor in memory.high throttling
ceca26903bd7 memcg: fix NULL pointer dereference in __mem_cgroup_usage_unregister_event
2439259c32c8 stm class: sys-t: Fix the use of time_after()
f7ef7a020f3b drm/lease: fix WARNING in idr_destroy
b4e798cab8e9 drm/amd/amdgpu: Fix GPR read from debugfs (v2)
eaa7fe20231a btrfs: fix log context list corruption after rename whiteout error
039547fbd1e8 xhci: Do not open code __print_symbolic() in xhci trace events
ac9d3279514c arm64: compat: Fix syscall number of compat_clock_getres
70ca8a95df81 rtc: max8907: add missing select REGMAP_IRQ
eba75a365f55 modpost: move the namespace field in Module.symvers last
69a9b971406f intel_th: pci: Add Elkhart Lake CPU support
3bdc0f68a170 intel_th: Fix user-visible error codes
97097054a1f0 intel_th: msu: Fix the unexpected state warning
07c70054ba24 staging/speakup: fix get_word non-space look-ahead
35da67a8a50c staging: greybus: loopback_test: fix poll-mask build breakage
fbe68a636982 staging: rtl8188eu: Add device id for MERCUSYS MW150US v2
5f9579641df2 kbuild: Disable -Wpointer-to-enum-cast
0f5be2f69e89 CIFS: fiemap: do not return EINVAL if get nothing
48a9bc9534f3 mmc: sdhci-cadence: set SDHCI_QUIRK2_PRESET_VALUE_BROKEN for UniPhier
8aafd5a0c63c mmc: sdhci-of-at91: fix cd-gpios for SAMA5D2
0c4e0f0d2e51 mmc: rtsx_pci: Fix support for speed-modes that relies on tuning
dbb328d1a87d iio: light: vcnl4000: update sampling periods for vcnl4040
c3540b094edb iio: light: vcnl4000: update sampling periods for vcnl4200
7ad22950caf5 iio: adc: at91-sama5d2_adc: fix differential channels in triggered mode
4d71a4f76179 iio: adc: stm32-dfsdm: fix sleep in atomic context
a79f53a2f5af iio: magnetometer: ak8974: Fix negative raw values in sysfs
6387b4002357 iio: accel: adxl372: Set iio_chan BE
3c69b794f96e iio: trigger: stm32-timer: disable master mode when stopping
eb5f46b0cc55 iio: st_sensors: remap SMO8840 to LIS2DH12
69399842e4a9 iio: chemical: sps30: fix missing triggered buffer dependency
51d590fadc14 tty: fix compat TIOCGSERIAL checking wrong function ptr
a754de70f6d6 tty: fix compat TIOCGSERIAL leaking uninitialized memory
279cdccb6dc7 ALSA: pcm: oss: Remove WARNING from snd_pcm_plug_alloc() checks
07ec940ceda5 ALSA: pcm: oss: Avoid plugin buffer overflow
59e4624e664c ALSA: seq: oss: Fix running status after receiving sysex
f439c2ece795 ALSA: seq: virmidi: Fix running status after receiving sysex
e2f1c2d0b6db ALSA: hda/realtek - Enable the headset of Acer N50-600 with ALC662
f0e819900968 ALSA: hda/realtek - Enable headset mic of Acer X2660G with ALC662
2d994c9cefc4 ALSA: line6: Fix endless MIDI read loop
64ab82cf614f USB: cdc-acm: fix rounding error in TIOCSSERIAL
9ed83da8cd97 USB: cdc-acm: fix close_delay and closing_wait units in TIOCSSERIAL
186b9564cf5e usb: typec: ucsi: displayport: Fix a potential race during registration
ff1d876e9f4f usb: typec: ucsi: displayport: Fix NULL pointer dereference
7b5aab752efc usb: xhci: apply XHCI_SUSPEND_DELAY to AMD XHCI controller 1022:145c
6e1167db8d21 USB: serial: pl2303: add device-id for HP LD381
ade2ca96e7a6 usb: host: xhci-plat: add a shutdown
bace91138933 USB: serial: option: add ME910G1 ECM composition 0x110b
2601053cafb4 usb: quirks: add NO_LPM quirk for RTL8153 based ethernet adapters
d742e9874048 USB: Disable LPM on WD19's Realtek Hub
712d9c2e92ea Revert "drm/fbdev: Fallback to non tiled mode if all tiles not present"
c71986d18dea binderfs: use refcount for binder control devices too
169bf660646a parse-maintainers: Mark as executable
4db2f87e15c8 block, bfq: fix overwrite of bfq_group pointer in bfq_find_set_group()
5d33ba6f385f xenbus: req->err should be updated before req->state
7a79e217e3a5 xenbus: req->body should be updated before req->state
25c3f96370a1 drm/amd/display: fix dcc swath size calculations on dcn1
46c5b0d8dfbb drm/amd/display: Clear link settings on MST disable connector
e53a333014a3 drm/amdgpu: clean wptr on wb when gpu recovery
b557b2f00682 riscv: Fix range looking for kernel image memblock
1c2106d2d9c1 riscv: Force flat memory model with no-mmu
0bc9de1b1c1b spi: spi_register_controller(): free bus id on error paths
af7dd05d7c8f ASoC: stm32: sai: manage rebind issue
a3f349393eed riscv: avoid the PIC offset of static percpu data in module beyond 2G limits
1804cdf99fdb dm integrity: use dm_bio_record and dm_bio_restore
2e7e6de9ae38 dm bio record: save/restore bi_end_io and bi_integrity
886a8fb13d0c altera-stapl: altera_get_note: prevent write beyond end of 'key'
2c4e36033ace drivers/perf: arm_pmu_acpi: Fix incorrect checking of gicc pointer
1002a094e066 drivers/perf: fsl_imx8_ddr: Correct the CLEAR bit definition
0f6ae2cba3b8 drm/exynos: hdmi: don't leak enable HDMI_EN regulator if probe fails
53138bea67b2 drm/exynos: dsi: fix workaround for the legacy clock name
41f88dc1adcc drm/exynos: dsi: propagate error value and silence meaningless warning
0c30297dddc0 spi/zynqmp: remove entry that causes a cs glitch
b8ba4d74f9f3 spi: pxa2xx: Add CS control clock quirk
416e1f433c70 ARM: dts: dra7: Add "dma-ranges" property to PCIe RC DT nodes
74219d52d4e7 cifs: add missing mount option to /proc/mounts
ddd8b3ed509a cifs: fix potential mismatch of UNC paths
a7393e6f2ecf powerpc: Include .BTF section
9eee3e21a59d spi: qup: call spi_qup_pm_resume_runtime before suspending
1d4f214c8820 ARM: dts: dra7-l4: mark timer13-16 as pwm capable
5f657e5303d3 phy: ti: gmii-sel: do not fail in case of gmii
ee1245396b6e phy: ti: gmii-sel: fix set of copy-paste errors
4d9020c3d802 drm/mediatek: Find the cursor plane instead of hard coding it
61c895d0f726 spi: spi-omap2-mcspi: Support probe deferral for DMA channels
f9f635c04769 locks: reinstate locks_delete_block optimization
384e15fc4226 locks: fix a potential use-after-free problem when wakeup a waiter
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
---
.../linux/linux-yocto-rt_5.4.bb | 6 ++---
.../linux/linux-yocto-tiny_5.4.bb | 8 +++----
meta/recipes-kernel/linux/linux-yocto_5.4.bb | 22 +++++++++----------
3 files changed, 18 insertions(+), 18 deletions(-)
diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb b/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb
index 9e74ec17af..bc0c30986d 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb
@@ -11,13 +11,13 @@ python () {
raise bb.parse.SkipRecipe("Set PREFERRED_PROVIDER_virtual/kernel to linux-yocto-rt to enable it")
}
-SRCREV_machine ?= "79037ae58e6b0dfd0c63d4a0e131f1bd5efe7e53"
-SRCREV_meta ?= "bee554e595e49c963900d1c78c01ab2d041382e7"
+SRCREV_machine ?= "79b7c0fa5b69a99037cafa959077c4bbb46ebddd"
+SRCREV_meta ?= "32041dcb06c23ae4d2e9872c284b8c0500f3d5a4"
SRC_URI = "git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine \
git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-5.4;destsuffix=${KMETA}"
-LINUX_VERSION ?= "5.4.27"
+LINUX_VERSION ?= "5.4.28"
LIC_FILES_CHKSUM = "file://COPYING;md5=bbea815ee2795b2f4230826c0c6b8814"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb b/meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb
index ba5e668d73..5a86edac60 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb
@@ -6,7 +6,7 @@ KCONFIG_MODE = "--allnoconfig"
require recipes-kernel/linux/linux-yocto.inc
-LINUX_VERSION ?= "5.4.27"
+LINUX_VERSION ?= "5.4.28"
LIC_FILES_CHKSUM = "file://COPYING;md5=bbea815ee2795b2f4230826c0c6b8814"
DEPENDS += "${@bb.utils.contains('ARCH', 'x86', 'elfutils-native', '', d)}"
@@ -15,9 +15,9 @@ DEPENDS += "openssl-native util-linux-native"
KMETA = "kernel-meta"
KCONF_BSP_AUDIT_LEVEL = "2"
-SRCREV_machine_qemuarm ?= "5c2d35eeb4be0e8bae4cf5ee0733e41ff1262ff3"
-SRCREV_machine ?= "03142acba06e8b33888410a518358a626dceb720"
-SRCREV_meta ?= "bee554e595e49c963900d1c78c01ab2d041382e7"
+SRCREV_machine_qemuarm ?= "044058d79ab16a29429ce0163496da599bd83c33"
+SRCREV_machine ?= "5ebd77b70931f1fec5dbae6ca9168b0471e9083e"
+SRCREV_meta ?= "32041dcb06c23ae4d2e9872c284b8c0500f3d5a4"
PV = "${LINUX_VERSION}+git${SRCPV}"
diff --git a/meta/recipes-kernel/linux/linux-yocto_5.4.bb b/meta/recipes-kernel/linux/linux-yocto_5.4.bb
index 25e933d683..13b8085547 100644
--- a/meta/recipes-kernel/linux/linux-yocto_5.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_5.4.bb
@@ -12,16 +12,16 @@ KBRANCH_qemux86 ?= "v5.4/standard/base"
KBRANCH_qemux86-64 ?= "v5.4/standard/base"
KBRANCH_qemumips64 ?= "v5.4/standard/mti-malta64"
-SRCREV_machine_qemuarm ?= "ab849248b45403c7d6f1fb8e8f57840cc2880618"
-SRCREV_machine_qemuarm64 ?= "03142acba06e8b33888410a518358a626dceb720"
-SRCREV_machine_qemumips ?= "967a1708cbbfe1b524dc28f04fa5e0d79a270bf5"
-SRCREV_machine_qemuppc ?= "03142acba06e8b33888410a518358a626dceb720"
-SRCREV_machine_qemuriscv64 ?= "03142acba06e8b33888410a518358a626dceb720"
-SRCREV_machine_qemux86 ?= "03142acba06e8b33888410a518358a626dceb720"
-SRCREV_machine_qemux86-64 ?= "03142acba06e8b33888410a518358a626dceb720"
-SRCREV_machine_qemumips64 ?= "d3e850da830241c424d557a6a072527e09e784ab"
-SRCREV_machine ?= "03142acba06e8b33888410a518358a626dceb720"
-SRCREV_meta ?= "bee554e595e49c963900d1c78c01ab2d041382e7"
+SRCREV_machine_qemuarm ?= "f7412afb66c40e1c9944f115bc499fc395520c7c"
+SRCREV_machine_qemuarm64 ?= "5ebd77b70931f1fec5dbae6ca9168b0471e9083e"
+SRCREV_machine_qemumips ?= "4aba5a90caa5dd43098e3317e121497e4ce4bcaa"
+SRCREV_machine_qemuppc ?= "5ebd77b70931f1fec5dbae6ca9168b0471e9083e"
+SRCREV_machine_qemuriscv64 ?= "5ebd77b70931f1fec5dbae6ca9168b0471e9083e"
+SRCREV_machine_qemux86 ?= "5ebd77b70931f1fec5dbae6ca9168b0471e9083e"
+SRCREV_machine_qemux86-64 ?= "5ebd77b70931f1fec5dbae6ca9168b0471e9083e"
+SRCREV_machine_qemumips64 ?= "a72caa2030fa17491f4013025b598f76b7efe39b"
+SRCREV_machine ?= "5ebd77b70931f1fec5dbae6ca9168b0471e9083e"
+SRCREV_meta ?= "32041dcb06c23ae4d2e9872c284b8c0500f3d5a4"
# remap qemuarm to qemuarma15 for the 5.4 kernel
# KMACHINE_qemuarm ?= "qemuarma15"
@@ -30,7 +30,7 @@ SRC_URI = "git://git.yoctoproject.org/linux-yocto.git;name=machine;branch=${KBRA
git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-5.4;destsuffix=${KMETA}"
LIC_FILES_CHKSUM = "file://COPYING;md5=bbea815ee2795b2f4230826c0c6b8814"
-LINUX_VERSION ?= "5.4.27"
+LINUX_VERSION ?= "5.4.28"
DEPENDS += "${@bb.utils.contains('ARCH', 'x86', 'elfutils-native', '', d)}"
DEPENDS += "openssl-native util-linux-native"
--
2.19.1
^ permalink raw reply related [flat|nested] 64+ messages in thread
* [PATCH 2/5] linux-yocto/5.4: update to v5.4.32
2020-05-03 15:44 [PATCH 0/5] linux-yocto: consolidated pull request Bruce Ashfield
2020-05-03 15:44 ` [PATCH 1/5] linux-yocto/5.4: update to v5.4.28 Bruce Ashfield
@ 2020-05-03 15:44 ` Bruce Ashfield
2020-05-03 15:44 ` [PATCH 3/5] linux-yocto/5.4: update to v5.4.34 Bruce Ashfield
` (3 subsequent siblings)
5 siblings, 0 replies; 64+ messages in thread
From: Bruce Ashfield @ 2020-05-03 15:44 UTC (permalink / raw)
To: richard.purdie; +Cc: openembedded-core, steve
From: Bruce Ashfield <bruce.ashfield@gmail.com>
Updating linux-yocto/5.4 to the latest korg -stable release that comprises
the following commits:
bc844d58f697 Linux 5.4.32
ad5676629a12 iommu/vt-d: Allow devices with RMRRs to use identity domain
04ad505eed58 drm/i915: Fix ref->mutex deadlock in i915_active_wait()
047affa0ef00 fbcon: fix null-ptr-deref in fbcon_switch
d4083258db04 blk-mq: Keep set->nr_hw_queues and set->map[].nr_queues in sync
d020ff5060a4 RDMA/cm: Update num_paths in cma_resolve_iboe_route error flow
b40f1ae359f2 Bluetooth: RFCOMM: fix ODEBUG bug in rfcomm_dev_ioctl
7f5432c2f446 RDMA/siw: Fix passive connection establishment
09583e3f0402 RDMA/cma: Teach lockdep about the order of rtnl and lock
51795bcf595d RDMA/ucma: Put a lock around every call to the rdma_cm layer
ab6ee4330288 include/uapi/linux/swab.h: fix userspace breakage, use __BITS_PER_LONG for swap
193490dbe5ba ceph: canonicalize server path in place
56385788f7f6 ceph: remove the extra slashes in the server path
7dafb2c6fb46 ARM: imx: only select ARM_ERRATA_814220 for ARMv7-A
cf7005662673 ARM: imx: Enable ARM_ERRATA_814220 for i.MX6UL and i.MX7D
4ac80b02f10d IB/mlx5: Replace tunnel mpls capability bits for tunnel_offloads
ccc2b645de20 IB/hfi1: Fix memory leaks in sysfs registration and unregistration
cd38d8b231f1 IB/hfi1: Call kobject_put() when kobject_init_and_add() fails
9351dee1cc24 ASoC: jz4740-i2s: Fix divider written at incorrect offset in register
e30a21c6fea5 platform/x86: intel_int0002_vgpio: Use acpi_register_wakeup_handler()
9da847d65f37 ACPI: PM: Add acpi_[un]register_wakeup_handler()
41a0cfa05c05 hwrng: imx-rngc - fix an error path
dfa210cf9f94 tools/accounting/getdelays.c: fix netlink attribute length
ea84a26ab633 slub: improve bit diffusion for freelist ptr obfuscation
8b0f08036659 uapi: rename ext2_swab() to swab() and share globally in swab.h
94d2d84bcafa usb: dwc3: gadget: Wrap around when skip TRBs
170f88a47b9f random: always use batched entropy for get_random_u{32,64}
5e331978200e s390: prevent leaking kernel address in BEAR
74107d56d1e8 r8169: change back SG and TSO to be disabled by default
5249653d971d mlxsw: spectrum_flower: Do not stop at FLOW_ACTION_VLAN_MANGLE
671331c11c39 tun: Don't put_page() for all negative return values from XDP program
fdb6a094ba41 slcan: Don't transmit uninitialized stack data in padding
feed32e3d6fe net: stmmac: dwmac1000: fix out-of-bounds mac address reg setting
049b9fa3ef65 net_sched: fix a missing refcnt in tcindex_init()
1891d57f89aa net_sched: add a temporary refcnt for struct tcindex_data
1189ba9eedac net: phy: micrel: kszphy_resume(): add delay after genphy_resume() before accessing PHY registers
7d3d99f579e8 net: dsa: mt7530: fix null pointer dereferencing in port5 setup
bce7ce18bd18 net: dsa: bcm_sf2: Ensure correct sub-node is parsed
040f7a27583f net: dsa: bcm_sf2: Do not register slave MDIO bus with OF
bbbdd7956bab ipv6: don't auto-add link-local address to lag ports
77cf80793692 cxgb4: fix MPS index overwrite when setting MAC address
3fcd53b1d859 net: phy: realtek: fix handling of RTL8105e-integrated PHY
de850633a01f Linux 5.4.31
c3f87e03f90f mm: mempolicy: require at least one nodeid for MPOL_PREFERRED
c3d4e6fc4b37 padata: always acquire cpu_hotplug_lock before pinst->lock
238112fcf391 net: Fix Tx hash bound checking
15ee8da79ee3 i2c: i801: Do not add ICH_RES_IO_SMI for the iTCO_wdt device
079c8da9e5ac watchdog: iTCO_wdt: Make ICH_RES_IO_SMI optional
b42afa3475bf watchdog: iTCO_wdt: Export vendorsupport
4ebd16641797 tcp: fix TFO SYNACK undo to avoid double-timestamp-undo
a6b1820d3330 IB/hfi1: Ensure pq is not left on waitlist
c4168080f1d4 rxrpc: Fix sendmsg(MSG_WAITALL) handling
be8a3aecd21a iwlwifi: dbg: don't abort if sending DBGC_SUSPEND_RESUME fails
b4190809a17b iwlwifi: yoyo: don't add TLV offset when reading FIFOs
00e332e42bbe iwlwifi: consider HE capability when setting LDPC
5f843cb77142 net/mlx5e: kTLS, Fix wrong value in record tracker enum
ea26f82a0422 soc: mediatek: knows_txdone needs to be set in Mediatek CMDQ helper
f6c8f128856b ALSA: hda/ca0132 - Add Recon3Di quirk to handle integrated sound on EVGA X99 Classified motherboard
2892100bc85a Revert "dm: always call blk_queue_split() in dm_process_bio()"
7c6ae8ae0ac5 power: supply: axp288_charger: Add special handling for HP Pavilion x2 10
899c38d93000 extcon: axp288: Add wakeup support
4d60b72514c2 nvmem: check for NULL reg_read and reg_write before dereferencing
98b32db072e9 mei: me: add cedar fork device ids
1843cba24aef coresight: do not use the BIT() macro in the UAPI header
b5212116392e PCI: sysfs: Revert "rescan" file renames
aa98c16a5b7c misc: pci_endpoint_test: Avoid using module parameter to determine irqtype
a5d697c1e92d misc: pci_endpoint_test: Fix to support > 10 pci-endpoint-test devices
82f6c72e5d4d misc: rtsx: set correct pcr_ops for rts522A
cec4be18d136 brcmfmac: abort and release host after error
625b940a28e0 padata: fix uninitialized return value in padata_replace()
16696ee7b581 XArray: Fix xa_find_next for large multi-index entries
4eb33cb9b566 net/mlx5e: kTLS, Fix TCP seq off-by-1 issue in TX resync flow
8792e1ac5f48 tools/power turbostat: Fix 32-bit capabilities warning
09116eeea6a5 tools/power turbostat: Fix missing SYS_LPI counter on some Chromebooks
0ba0ce3cbb86 tools/power turbostat: Fix gcc build warnings
7ebc1e53a46b drm/amdgpu: fix typo for vcn1 idle check
d2faee42f9e7 initramfs: restore default compression behavior
4a8ba74c1c64 drm/bochs: downgrade pci_request_region failure from error to warning
f8abcff4fd0d drm/amd/display: Add link_rate quirk for Apple 15" MBP 2017
205b5f80c74f kconfig: introduce m32-flag and m64-flag
91358d0f36fa nvme-rdma: Avoid double freeing of async event data
ad13e142e024 Linux 5.4.30
9e62b6673d14 arm64: dts: ls1046ardb: set RGMII interfaces to RGMII_ID mode
c399a50ae878 arm64: dts: ls1043a-rdb: correct RGMII delay mode to rgmii-id
5aa29219206a ARM: dts: sun8i: r40: Move AHCI device node based on address order
8f1199341837 ARM: dts: N900: fix onenand timings
89ecba47b391 ARM: dts: imx6: phycore-som: fix arm and soc minimum voltage
bb4ec20d1687 ARM: bcm2835-rpi-zero-w: Add missing pinctrl name
e58eb564e1fc ARM: dts: oxnas: Fix clear-mask property
a1081413e834 perf map: Fix off by one in strncpy() size argument
451bf4d9592a arm64: alternative: fix build with clang integrated assembler
693860e79552 libceph: fix alloc_msg_with_page_vector() memory leaks
61bbc823a17a clk: ti: am43xx: Fix clock parent for RTC clock
b2efabe3f88c clk: imx: Align imx sc clock parent msg structs to 4
4a3c7e1c807f clk: imx: Align imx sc clock msg structs to 4
08479b1391cb net: ks8851-ml: Fix IO operations, again
62465fd66323 gpiolib: acpi: Add quirk to ignore EC wakeups on HP x2 10 CHT + AXP288 model
877f28596da2 bpf: Explicitly memset some bpf info structures declared on the stack
e92528a8984e bpf: Explicitly memset the bpf_attr structure
d3e215554a6c platform/x86: pmc_atom: Add Lex 2I385SW to critclk_systems DMI table
3f4ba176c623 vt: vt_ioctl: fix use-after-free in vt_in_use()
acf0e9401931 vt: vt_ioctl: fix VT_DISALLOCATE freeing in-use virtual console
d1b6ab26c850 vt: vt_ioctl: remove unnecessary console allocation checks
c897e625f94b vt: switch vt_dont_switch to bool
e7244ce86ceb vt: ioctl, switch VT_IS_IN_USE and VT_BUSY to inlines
383c71b7314f vt: selection, introduce vc_is_sel
125dd8c48b19 serial: sprd: Fix a dereference warning
5b1bd4900fed mac80211: fix authentication with iwlwifi/mvm
5863d2b27fb2 mac80211: Check port authorization in the ieee80211_tx_dequeue() case
73fea3292b49 Linux 5.4.29
f8c60f7a0051 net: Fix CONFIG_NET_CLS_ACT=n and CONFIG_NFT_FWD_NETDEV={y, m} build
5f80d17c517d media: v4l2-core: fix a use-after-free bug of sd->devnode
e7cd85f398cd media: xirlink_cit: add missing descriptor sanity checks
4490085a9e2d media: stv06xx: add missing descriptor sanity checks
d111431a4420 media: dib0700: fix rc endpoint lookup
e4af1cf37b90 media: ov519: add missing endpoint sanity checks
b25af84517de libfs: fix infoleak in simple_attr_read()
dcf2d659add5 ahci: Add Intel Comet Lake H RAID PCI ID
89d4acabb2f6 staging: wlan-ng: fix use-after-free Read in hfa384x_usbin_callback
c44ea4fe738b staging: wlan-ng: fix ODEBUG bug in prism2sta_disconnect_usb
0ec1ab1b15d2 staging: rtl8188eu: Add ASUS USB-N10 Nano B1 to device table
fea3939c6ccc staging: kpc2000: prevent underflow in cpld_reconfigure()
b958dea86c26 media: usbtv: fix control-message timeouts
275316b63165 media: flexcop-usb: fix endpoint sanity check
5102000134f4 usb: musb: fix crash with highmen PIO and usbmon
f32219427ca1 USB: serial: io_edgeport: fix slab-out-of-bounds read in edge_interrupt_callback
004b43fdfcf4 USB: cdc-acm: restore capability check order
4003d59a00e2 USB: serial: option: add Wistron Neweb D19Q1
d5fec27c54e7 USB: serial: option: add BroadMobi BM806U
6eff944ff084 USB: serial: option: add support for ASKEY WWHC050
8d62a8c7489a bpf: Undo incorrect __reg_bound_offset32 handling
f23f37fe702f clocksource/drivers/hyper-v: Untangle stimers and timesync from clocksources
791c420f4228 r8169: fix PHY driver check on platforms w/o module softdeps
d8166d4b4203 vti6: Fix memory leak of skb if input policy check fails
9c4f1506b477 ARM: dts: sun8i-a83t-tbs-a711: Fix USB OTG mode detection
7f884cb145dc bpf, sockmap: Remove bucket->lock from sock_{hash|map}_free
657559d632c2 bpf/btf: Fix BTF verification of enum members in struct/union
188aae1f3d5f bpf: Initialize storage pointers to NULL to prevent freeing garbage pointer
c68e1117f4e4 bpf, x32: Fix bug with JMP32 JSET BPF_X checking upper bits
74617178d694 i2c: nvidia-gpu: Handle timeout correctly in gpu_i2c_check_status()
6734a326cb13 netfilter: nft_fwd_netdev: allow to redirect to ifb via ingress
5be3b97a1f18 netfilter: nft_fwd_netdev: validate family and chain type
4e8bba9420e2 netfilter: flowtable: reload ip{v6}h in nf_flow_tuple_ip{v6}
0bc1c7f6358c mac80211: set IEEE80211_TX_CTRL_PORT_CTRL_PROTO for nl80211 TX
74fdc220e2f1 ieee80211: fix HE SPR size calculation
eaca61f5f850 afs: Fix unpinned address list during probing
455f5192a10d afs: Fix some tracing details
c743855a0ebe afs: Fix client call Rx-phase signal handling
21af83e17ffa xfrm: policy: Fix doulbe free in xfrm_policy_timer
160c2ffa7016 xfrm: add the missing verify_sec_ctx_len check in xfrm_add_acquire
a5c5cf6f24bb xfrm: fix uctx len check in verify_sec_ctx_len
1b92d81d4cc2 RDMA/mlx5: Block delay drop to unprivileged users
1babd2c979aa RDMA/mlx5: Fix access to wrong pointer while performing flush due to error
9961c56955a4 RDMA/mlx5: Fix the number of hwcounters of a dynamic counter
f8f90690df59 vti[6]: fix packet tx through bpf_redirect() in XinY cases
c467570443bb xfrm: handle NETDEV_UNREGISTER for xfrm device
86c7d38c2baf genirq: Fix reference leaks on irq affinity notifiers
fe6010e47ddc afs: Fix handling of an abort from a service handler
d9e974eea8f1 RDMA/core: Ensure security pkey modify is not lost
768e582a9970 bpf: Fix cgroup ref leak in cgroup_bpf_inherit on out-of-memory
0dcf81d2c12f gpiolib: acpi: Add quirk to ignore EC wakeups on HP x2 10 BYT + AXP288 model
43d2a61ceb09 gpiolib: acpi: Rework honor_wakeup option into an ignore_wake option
323a89bff42b gpiolib: acpi: Correct comment for HP x2 10 honor_wakeup quirk
159aef18f05c mm: fork: fix kernel_stack memcg stats for various stack implementations
cc5da743a456 mm/sparse: fix kernel crash with pfn_section_valid check
238dd5ab0080 drivers/base/memory.c: indicate all memory blocks as removable
da458bbfb6cf mm/swapfile.c: move inode_lock out of claim_swapfile
33c8bc8aa7b2 mac80211: mark station unauthorized before key removal
d6b1f3fc76c4 mac80211: drop data frames without key on encrypted links
4a89bb3fca20 nl80211: fix NL80211_ATTR_CHANNEL_WIDTH attribute type
b34e20c78f1c scsi: sd: Fix optimal I/O size for devices that change reported values
35b34d264cb3 scripts/dtc: Remove redundant YYLOC global declaration
683cf6637730 tools: Let O= makes handle a relative path with -C option
2fe72de89cf7 rtlwifi: rtl8188ee: Fix regression due to commit d1d1a96bdb44
a2d866c50a35 perf probe: Do not depend on dwfl_module_addrsym()
5f2b792d3125 perf probe: Fix to delete multiple probe event
94a4104bf10e x86/ioremap: Fix CONFIG_EFI=n build
174da11b6474 ARM: dts: omap5: Add bus_dma_limit for L3 bus
e41cd3b598ae ARM: dts: dra7: Add bus_dma_limit for L3 bus
7cdaa5cd79ab ceph: fix memory leak in ceph_cleanup_snapid_map()
ed24820d1b0c ceph: check POOL_FLAG_FULL/NEARFULL in addition to OSDMAP_FULL/NEARFULL
44960e1c39d8 RDMA/mad: Do not crash if the rdma device does not have a umad interface
34aa3d5b84d5 RDMA/nl: Do not permit empty devices names during RDMA_NLDEV_CMD_NEWLINK/SET
9924d9fac61b gpiolib: Fix irq_disable() semantics
10d5de234df4 RDMA/core: Fix missing error check on dev_set_name()
b0a2af91cd78 IB/rdmavt: Free kernel completion queue when done
99058b8beef5 Input: avoid BIT() macro usage in the serio.h UAPI header
597d6fb4815c Input: synaptics - enable RMI on HP Envy 13-ad105ng
381c88a6b948 Input: fix stale timestamp on key autorepeat events
cd18a7f6a789 Input: raydium_i2c_ts - fix error codes in raydium_i2c_boot_trigger()
d8f58a0f533a i2c: hix5hd2: add missed clk_disable_unprepare in remove
65047f7538ba iwlwifi: mvm: fix non-ACPI function
72a0cfeb513c iommu/vt-d: Populate debugfs if IOMMUs are detected
cb17ed60ec39 iommu/vt-d: Fix debugfs register reads
e5ea0d970f33 net: hns3: fix "tc qdisc del" failed issue
24e72d55bc0b sxgbe: Fix off by one in samsung driver strncpy size arg
753ea21f2ac3 dpaa_eth: Remove unnecessary boolean expression in dpaa_get_headroom
27030150699b mac80211: Do not send mesh HWMP PREQ if HWMP is disabled
5ecb28b15678 scsi: ipr: Fix softlockup when rescanning devices in petitboot
ee3bc486643d s390/qeth: handle error when backing RX buffer
8b6cccd9bd84 s390/qeth: don't reset default_out_queue
f8de95a236f6 iommu/vt-d: Silence RCU-list debugging warnings
957e6f437d02 drm/exynos: Fix cleanup of IOMMU related objects
70e0a720038e drm/amdgpu: correct ROM_INDEX/DATA offset for VEGA20
2e89e4e7f7e1 drm/amd/display: update soc bb for nv14
8dab286ab527 fsl/fman: detect FMan erratum A050385
406f1ac075fe arm64: dts: ls1043a: FMan erratum A050385
c211a30c1846 dt-bindings: net: FMan erratum A050385
b82e91ae6384 cgroup1: don't call release_agent when it is ""
0cd633314661 drivers/of/of_mdio.c:fix of_mdiobus_register()
dda4fca30906 cpupower: avoid multiple definition with gcc -fno-common
7f9c2d71cfd3 nfs: add minor version to nfs_server_key for fscache
b51274fabedc cgroup-v1: cgroup_pidlist_next should update position index
74f554af848d net/mlx5e: Do not recover from a non-fatal syndrome
f94d69e5f682 net/mlx5e: Fix ICOSQ recovery flow with Striding RQ
bd81b9ba546a net/mlx5e: Fix missing reset of SW metadata in Striding RQ reset
d8338b5f373a net/mlx5e: Enhance ICOSQ WQE info fields
63a0fc3b0047 net/mlx5: DR, Fix postsend actions write length
c3c9927d0a8f hsr: set .netnsok flag
1a0fdef2d52d hsr: add restart routine into hsr_get_node_list()
80aa1e38e16b hsr: use rcu_read_lock() in hsr_get_node_{list/status}()
e4723e0a858e net: ip_gre: Accept IFLA_INFO_DATA-less configuration
85aa84d3c587 net: ip_gre: Separate ERSPAN newlink / changelink callbacks
62e3ffa4ea4e bnxt_en: Reset rings if ring reservation fails during open()
0234e8ebb7f4 bnxt_en: Free context memory after disabling PCI in probe error path.
797d6f91c399 bnxt_en: Return error if bnxt_alloc_ctx_mem() fails.
ae4565168af3 bnxt_en: fix memory leaks in bnxt_dcbnl_ieee_getets()
2ac37a531115 bnxt_en: Fix Priority Bytes and Packets counters in ethtool -S.
53d0bf064c9f vxlan: check return value of gro_cells_init()
a6ce82deba5c tcp: repair: fix TCP_QUEUE_SEQ implementation
27cf5410a9e1 tcp: ensure skb->dev is NULL before leaving TCP stack
c94b94626876 tcp: also NULL skb->dev when copy was needed
49d2333f97f0 slcan: not call free_netdev before rtnl_unlock in slcan_open
4cc2498b7ebb r8169: re-enable MSI on RTL8168c
3428faf70c59 NFC: fdp: Fix a signedness bug in fdp_nci_send_patch()
3d9cc478af25 net: stmmac: dwmac-rk: fix error path in rk_gmac_probe
d23faf32e577 net_sched: keep alloc_hash updated after hash allocation
5317abb870fe net_sched: hold rtnl lock in tcindex_partial_destroy_work()
ff28c6195814 net_sched: cls_route: remove the right filter from hashtable
a631b9668460 net/sched: act_ct: Fix leak of ct zone template on replace
312805c93bf6 net: qmi_wwan: add support for ASKEY WWHC050
522d2dc17967 net: phy: mdio-mux-bcm-iproc: check clk_prepare_enable() return value
f806b9e84057 net: phy: mdio-bcm-unimac: Fix clock handling
9fe154ee3fd5 net: phy: dp83867: w/a for fld detect threshold bootstrapping issue
86137342fd4c net/packet: tpacket_rcv: avoid a producer race condition
bb8c787be0e3 net: mvneta: Fix the case where the last poll did not process all rx
a2a3baa29914 net: ena: Add PCI shutdown handler to allow safe kexec
e586427a0abb net: dsa: tag_8021q: replace dsa_8021q_remove_header with __skb_vlan_pop
0ec037c1353c net: dsa: mt7530: Change the LINK bit to reflect the link status
60e975088be8 net: dsa: Fix duplicate frames flooded by learning
7c6fe9b2af79 net: cbs: Fix software cbs to consider packet sending time
712c39d9319a net/bpfilter: fix dprintf usage for /dev/kmsg
85675064133e mlxsw: spectrum_mr: Fix list iteration in error path
5a1a00f6ac32 mlxsw: pci: Only issue reset when system is ready
6e75284e2480 macsec: restrict to ethernet devices
51db2db8fe68 ipv4: fix a RCU-list lock in inet_dump_fib()
b67aa57f4a9d hsr: fix general protection fault in hsr_addr_is_self()
6fe31c7ce0ed geneve: move debug check after netdev unregister
b5c9652ada33 cxgb4: fix Txq restart check during backpressure
e92a0e7fba68 cxgb4: fix throughput drop during Tx backpressure
b0ab8700283c ACPI: PM: s2idle: Rework ACPI events synchronization
127882d10931 mmc: sdhci-tegra: Fix busy detection by enabling MMC_CAP_NEED_RSP_BUSY
71d89344af0b mmc: sdhci-omap: Fix busy detection by enabling MMC_CAP_NEED_RSP_BUSY
bf8b920f474e mmc: core: Respect MMC_CAP_NEED_RSP_BUSY for eMMC sleep command
3b9b71adbec4 mmc: core: Respect MMC_CAP_NEED_RSP_BUSY for erase/trim/discard
d9c4f387e22a mmc: core: Allow host controllers to require R1B for CMD6
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
---
.../linux/linux-yocto-rt_5.4.bb | 6 ++---
.../linux/linux-yocto-tiny_5.4.bb | 8 +++----
meta/recipes-kernel/linux/linux-yocto_5.4.bb | 22 +++++++++----------
3 files changed, 18 insertions(+), 18 deletions(-)
diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb b/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb
index bc0c30986d..42e4bca574 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb
@@ -11,13 +11,13 @@ python () {
raise bb.parse.SkipRecipe("Set PREFERRED_PROVIDER_virtual/kernel to linux-yocto-rt to enable it")
}
-SRCREV_machine ?= "79b7c0fa5b69a99037cafa959077c4bbb46ebddd"
-SRCREV_meta ?= "32041dcb06c23ae4d2e9872c284b8c0500f3d5a4"
+SRCREV_machine ?= "2348504c2c1035e1d7227d25224c9345f7b129d3"
+SRCREV_meta ?= "fa59277b2013ec395f3beb3656becb48fdf4b555"
SRC_URI = "git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine \
git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-5.4;destsuffix=${KMETA}"
-LINUX_VERSION ?= "5.4.28"
+LINUX_VERSION ?= "5.4.32"
LIC_FILES_CHKSUM = "file://COPYING;md5=bbea815ee2795b2f4230826c0c6b8814"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb b/meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb
index 5a86edac60..ec4e7679f1 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb
@@ -6,7 +6,7 @@ KCONFIG_MODE = "--allnoconfig"
require recipes-kernel/linux/linux-yocto.inc
-LINUX_VERSION ?= "5.4.28"
+LINUX_VERSION ?= "5.4.32"
LIC_FILES_CHKSUM = "file://COPYING;md5=bbea815ee2795b2f4230826c0c6b8814"
DEPENDS += "${@bb.utils.contains('ARCH', 'x86', 'elfutils-native', '', d)}"
@@ -15,9 +15,9 @@ DEPENDS += "openssl-native util-linux-native"
KMETA = "kernel-meta"
KCONF_BSP_AUDIT_LEVEL = "2"
-SRCREV_machine_qemuarm ?= "044058d79ab16a29429ce0163496da599bd83c33"
-SRCREV_machine ?= "5ebd77b70931f1fec5dbae6ca9168b0471e9083e"
-SRCREV_meta ?= "32041dcb06c23ae4d2e9872c284b8c0500f3d5a4"
+SRCREV_machine_qemuarm ?= "63425cc3498f7f10b1571b38718ed47234d5ade7"
+SRCREV_machine ?= "d66ed1ee791577746d30b29baef734fbb9297431"
+SRCREV_meta ?= "fa59277b2013ec395f3beb3656becb48fdf4b555"
PV = "${LINUX_VERSION}+git${SRCPV}"
diff --git a/meta/recipes-kernel/linux/linux-yocto_5.4.bb b/meta/recipes-kernel/linux/linux-yocto_5.4.bb
index 13b8085547..485928bd88 100644
--- a/meta/recipes-kernel/linux/linux-yocto_5.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_5.4.bb
@@ -12,16 +12,16 @@ KBRANCH_qemux86 ?= "v5.4/standard/base"
KBRANCH_qemux86-64 ?= "v5.4/standard/base"
KBRANCH_qemumips64 ?= "v5.4/standard/mti-malta64"
-SRCREV_machine_qemuarm ?= "f7412afb66c40e1c9944f115bc499fc395520c7c"
-SRCREV_machine_qemuarm64 ?= "5ebd77b70931f1fec5dbae6ca9168b0471e9083e"
-SRCREV_machine_qemumips ?= "4aba5a90caa5dd43098e3317e121497e4ce4bcaa"
-SRCREV_machine_qemuppc ?= "5ebd77b70931f1fec5dbae6ca9168b0471e9083e"
-SRCREV_machine_qemuriscv64 ?= "5ebd77b70931f1fec5dbae6ca9168b0471e9083e"
-SRCREV_machine_qemux86 ?= "5ebd77b70931f1fec5dbae6ca9168b0471e9083e"
-SRCREV_machine_qemux86-64 ?= "5ebd77b70931f1fec5dbae6ca9168b0471e9083e"
-SRCREV_machine_qemumips64 ?= "a72caa2030fa17491f4013025b598f76b7efe39b"
-SRCREV_machine ?= "5ebd77b70931f1fec5dbae6ca9168b0471e9083e"
-SRCREV_meta ?= "32041dcb06c23ae4d2e9872c284b8c0500f3d5a4"
+SRCREV_machine_qemuarm ?= "bee6048166651d8c69327a0b0ff4f4b87d961d5c"
+SRCREV_machine_qemuarm64 ?= "d66ed1ee791577746d30b29baef734fbb9297431"
+SRCREV_machine_qemumips ?= "2180ef2ea5645cf63a1aa738f15e72c240c313ea"
+SRCREV_machine_qemuppc ?= "d66ed1ee791577746d30b29baef734fbb9297431"
+SRCREV_machine_qemuriscv64 ?= "d66ed1ee791577746d30b29baef734fbb9297431"
+SRCREV_machine_qemux86 ?= "d66ed1ee791577746d30b29baef734fbb9297431"
+SRCREV_machine_qemux86-64 ?= "d66ed1ee791577746d30b29baef734fbb9297431"
+SRCREV_machine_qemumips64 ?= "6afe026b32fd5ac553420f68052a665e3fcacd53"
+SRCREV_machine ?= "d66ed1ee791577746d30b29baef734fbb9297431"
+SRCREV_meta ?= "fa59277b2013ec395f3beb3656becb48fdf4b555"
# remap qemuarm to qemuarma15 for the 5.4 kernel
# KMACHINE_qemuarm ?= "qemuarma15"
@@ -30,7 +30,7 @@ SRC_URI = "git://git.yoctoproject.org/linux-yocto.git;name=machine;branch=${KBRA
git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-5.4;destsuffix=${KMETA}"
LIC_FILES_CHKSUM = "file://COPYING;md5=bbea815ee2795b2f4230826c0c6b8814"
-LINUX_VERSION ?= "5.4.28"
+LINUX_VERSION ?= "5.4.32"
DEPENDS += "${@bb.utils.contains('ARCH', 'x86', 'elfutils-native', '', d)}"
DEPENDS += "openssl-native util-linux-native"
--
2.19.1
^ permalink raw reply related [flat|nested] 64+ messages in thread
* [PATCH 3/5] linux-yocto/5.4: update to v5.4.34
2020-05-03 15:44 [PATCH 0/5] linux-yocto: consolidated pull request Bruce Ashfield
2020-05-03 15:44 ` [PATCH 1/5] linux-yocto/5.4: update to v5.4.28 Bruce Ashfield
2020-05-03 15:44 ` [PATCH 2/5] linux-yocto/5.4: update to v5.4.32 Bruce Ashfield
@ 2020-05-03 15:44 ` Bruce Ashfield
2020-05-03 15:44 ` [PATCH 4/5] linux-yocto/5.4: update to v5.4.38 Bruce Ashfield
` (2 subsequent siblings)
5 siblings, 0 replies; 64+ messages in thread
From: Bruce Ashfield @ 2020-05-03 15:44 UTC (permalink / raw)
To: richard.purdie; +Cc: openembedded-core, steve
From: Bruce Ashfield <bruce.ashfield@gmail.com>
Updating linux-yocto/5.4 to the latest korg -stable release that comprises
the following commits:
6ccc74c083c0 Linux 5.4.34
b538aacc9400 x86/microcode/AMD: Increase microcode PATCH_MAX_SIZE
856a74fd7e61 scsi: target: fix hang when multiple threads try to destroy the same iscsi session
992e469b4c44 scsi: target: remove boilerplate code
4b3380e007b2 x86/resctrl: Fix invalid attempt at removing the default resource group
3652782e3a87 x86/resctrl: Preserve CDP enable over CPU hotplug
6b5e8e7cbe24 irqchip/ti-sci-inta: Fix processing of masked irqs
9d2759006e29 ext4: do not zeroout extents beyond i_disksize
653b42530952 i2c: designware: platdrv: Remove DPM_FLAG_SMART_SUSPEND flag on BYT and CHT
e2b80bf26956 drm/amdgpu: fix the hw hang during perform system reboot and reset
251f13126e23 drm/amd/powerplay: force the trim of the mclk dpm_levels if OD is enabled
eecd70c77ff3 net/mlx5e: Use preactivate hook to set the indirection table
57f578bce415 net/mlx5e: Rename hw_modify to preactivate
67284c11399f net/mlx5e: Encapsulate updating netdev queues into a function
cae385538886 mac80211_hwsim: Use kstrndup() in place of kasprintf()
a8ce3412e8a2 mac80211: fix race in ieee80211_register_hw()
21350f28b226 nl80211: fix NL80211_ATTR_FTM_RESPONDER policy
aa5b11bb333c btrfs: check commit root generation in should_ignore_root
0026e356e51a tracing: Fix the race between registering 'snapshot' event trigger and triggering 'snapshot' operation
a0aaafe7ce4b keys: Fix proc_keys_next to increase position index
f32a339e0321 arm64: vdso: don't free unallocated pages
5209e5f05bf2 ALSA: usb-audio: Check mapping at creating connector controls, too
250db0305392 ALSA: usb-audio: Don't create jack controls for PCM terminals
aae6e154680f ALSA: usb-audio: Don't override ignore_ctl_error value from the map
9acfd1ac016a ALSA: usb-audio: Filter error from connector kctl ops, too
0eb7bcf3ad32 ALSA: hda/realtek - Enable the headset mic on Asus FX505DT
549a48900d8e ASoC: Intel: mrfld: return error codes when an error occurs
86ec55651fd2 ASoC: Intel: mrfld: fix incorrect check on p->sink
538b623fed6d usb: dwc3: gadget: Don't clear flags before transfer ended
3bffb20603cd arm64: dts: librem5-devkit: add a vbus supply to usb0
3a8dc1e91561 ARM: dts: imx7-colibri: fix muxing of usbc_det pin
c2c5d07090d4 clk: at91: usb: use proper usbs_mask
90c1f740ddf8 clk: at91: sam9x60: fix usb clock parents
c874d9d116d8 ext4: fix incorrect inodes per group in error message
dd7b410c9b01 ext4: fix incorrect group count in ext4_fill_super error message
44c70ed66c93 net/bpfilter: remove superfluous testing message
229563dc6b04 pwm: pca9685: Fix PWM/GPIO inter-operation
0a4c06f0db06 perf report: Fix no branch type statistics report issue
4542e583e2b8 acpi/nfit: improve bounds checking for 'func'
5815a5d70def jbd2: improve comments about freeing data buffers whose page mapping is NULL
8078d3af4af7 platform/chrome: cros_ec_rpmsg: Fix race with host event
777c8c9f11a8 scsi: ufs: Fix ufshcd_hold() caused scheduling while atomic
66458aa271b0 ovl: fix value of i_ino for lower hardlink corner case
c85a7109f905 Revert "ACPI: EC: Do not clear boot_ec_is_ecdt in acpi_ec_add()"
4f2fb2a1990a net: stmmac: dwmac-sunxi: Provide TX and RX fifo sizes
a06a51d59292 net/mlx5e: Fix pfnum in devlink port attribute
e25122586403 net/mlx5e: Fix nest_level for vlan pop action
cb8892f52ec9 net/mlx5e: Add missing release firmware call
34310505d404 net/mlx5: Fix frequent ioread PCI access during recovery
1ff0732cf805 net: ethernet: mediatek: move mt7623 settings out off the mt7530
f749a8bfdd38 net: dsa: mt7530: move mt7623 settings out off the mt7530
bb54dcca3fb5 net: tun: record RX queue in skb before do_xdp_generic()
f6b264f2a04c net: revert default NAPI poll timeout to 2 jiffies
61260486790e net: qrtr: send msgs from local of same id as broadcast
81dc4e9bff98 net: phy: micrel: use genphy_read_status for KSZ9131
a9a851f0ec67 net: ipv6: do not consider routes via gateways for anycast address check
22e56cb2f951 net: ipv4: devinet: Fix crash when add/del multicast IP with autojoin
3ca854743110 net: dsa: mt7530: fix tagged frames pass-through in VLAN-unaware mode
016e3531d5c1 l2tp: Allow management of tunnels and session in user namespace
22ea267a9cd6 hsr: check protocol version in hsr_newlink()
ced57064a085 amd-xgbe: Use __napi_schedule() in BH context
dc4059d21d87 Linux 5.4.33
484cc15ad00f scsi: lpfc: fix inlining of lpfc_sli4_cleanup_poll_list()
8dead2c275e4 ASoC: stm32: sai: Add missing cleanup
aed5ee6befcc efi/x86: Fix the deletion of variables in mixed mode
0c839eee166a mfd: dln2: Fix sanity checking for endpoints
b70eb420e96d bpf: Fix tnum constraints for 32-bit comparisons
26711cc7e064 mmc: sdhci: Refactor sdhci_set_timeout()
56a296657e4b mmc: sdhci: Convert sdhci_set_timeout_irq() to non-static
c1f3e1d8d7e6 powerpc/kasan: Fix kasan_remap_early_shadow_ro()
36b0b1f63994 drm/i915/icl+: Don't enable DDI IO power on a TypeC port in TBT mode
bdac1d76a310 drm/amdgpu: fix gfx hang during suspend with video playback (v2)
d1bbdf003c05 drm/dp_mst: Fix clearing payload state on topology disable
7676e69c67e3 Revert "drm/dp_mst: Remove VCPI while disabling topology mgr"
ba74ab0c29fc scsi: lpfc: Fix broken Credit Recovery after driver load
33ebae4f3ba6 scsi: lpfc: Fix configuration of BB credit recovery in service parameters
037b0b5521a4 scsi: lpfc: Fix Fabric hostname registration if system hostname changes
f48e7593523e scsi: lpfc: Add registration for CPU Offline/Online events
33344a7661a1 dm clone: Add missing casts to prevent overflows and data corruption
2d7eb7ee36a3 dm clone: Fix handling of partial region discards
dcf2f00b0869 dm clone: replace spin_lock_irqsave with spin_lock_irq
fddfa591da8e dm zoned: remove duplicate nr_rnd_zones increase in dmz_init_zone()
1ba26c2aedb4 arm64: Always force a branch protection mode when the compiler has one
ba7581be850b powerpc: Make setjmp/longjmp signature standard
3457b2232eaf scsi: mpt3sas: Fix kernel panic observed on soft HBA unplug
e294f8a5ad31 powerpc/64: Prevent stack protection in early boot
fc8755dc01d1 powerpc/kprobes: Ignore traps that happened in real mode
ed6f6b2b39af powerpc/xive: Fix xmon support on the PowerNV platform
1ab730b65946 powerpc/64: Setup a paca before parsing device tree etc.
9240f83aa9c7 powerpc/xive: Use XIVE_BAD_IRQ instead of zero to catch non configured IPIs
bd0fa144737c powerpc/hash64/devmap: Use H_PAGE_THP_HUGE when setting up huge devmap PTE entries
81b9336ab20e powerpc/fsl_booke: Avoid creating duplicate tlb1 entry
38aa7f32dfd8 powerpc/64/tm: Don't let userspace set regs->trap via sigreturn
0abc07d23c51 xen/blkfront: fix memory allocation flags in blkfront_setup_indirect()
5fdf01181cb8 ipmi: fix hung processes in __get_guid()
d0b9bd4804a7 libata: Return correct status in sata_pmp_eh_recover_pm() when ATA_DFLAG_DETACH is set
ec2c054e87a5 hfsplus: fix crash and filesystem corruption when deleting files
af80e6f70f72 cpufreq: powernv: Fix use-after-free
9cc4f52d34a2 kmod: make request_module() return an error when autoloading is disabled
bf4fcd52742e clk: ingenic/TCU: Fix round_rate returning error
9e8388fdf4de clk: ingenic/jz4770: Exit with error if CGU init failed
7bcca67bdee8 ftrace/kprobe: Show the maxactive number on kprobe_events
7dad5beb8dfd Input: i8042 - add Acer Aspire 5738z to nomux list
efb9e9f723f5 s390/diag: fix display of diagnose call statistics
453fb8b20db4 perf tools: Support Python 3.8+ in Makefile
beb3ef51cfd8 ocfs2: no need try to truncate file beyond i_size
47199f4b87eb fs/filesystems.c: downgrade user-reachable WARN_ONCE() to pr_warn_once()
6772387e8201 ext4: fix a data race at inode->i_blocks
699d2c4d667e NFS: Fix a page leak in nfs_destroy_unlinked_subrequests()
6b64cbd05807 NFS: Fix use-after-free issues in nfs_pageio_add_request()
98a817eda5bc nfsd: fsnotify on rmdir under nfsd/clients/
27993365c009 powerpc/pseries: Avoid NULL pointer dereference when drmem is unavailable
4e4c6760fe03 drm/amdgpu: unify fw_write_wait for new gfx9 asics
45bc323b8102 drm/amdgpu/powerplay: using the FCLK DPM table to set the MCLK
fe0ec6f90e4d drm: Remove PageReserved manipulation from drm_pci_alloc
b716a5f5ec65 drm/etnaviv: rework perfmon query infrastructure
463a2dddb4f9 drm/i915/gem: Flush all the reloc_gpu batch
cda1eda28f1d vfio: platform: Switch to platform_get_irq_optional()
b5eec37a3b85 selftests/powerpc: Add tlbie_test in .gitignore
e1ec78f93042 selftests/vm: fix map_hugetlb length used for testing read and write
336b96a68170 selftests: vm: drop dependencies on page flags from mlock2 tests
20a62e9073f3 arm64: armv8_deprecated: Fix undef_hook mask for thumb setend
3d66a67f7310 arm64: dts: ti: k3-am65: Add clocks to dwc3 nodes
9d971b0059a2 ARM: dts: exynos: Fix polarity of the LCD SPI bus on UniversalC210 board
e5b9c1027ee8 scsi: lpfc: Fix lpfc_io_buf resource leak in lpfc_get_scsi_buf_s4 error path
73a122c2636d scsi: ufs: fix Auto-Hibern8 error detection
0ad68e6212ad scsi: zfcp: fix missing erp_lock in port recovery trigger for point-to-point
8179a260313e crypto: ccree - dec auth tag size from cryptlen map
9135cd1b0f64 crypto: ccree - only try to map auth tag if needed
a86744642789 crypto: ccree - protect against empty or NULL scatterlists
f3f13f979448 crypto: caam - update xts sector size for large input length
bc8413b626dd crypto: caam/qi2 - fix chacha20 data size error
07378b099139 xarray: Fix early termination of xas_for_each_marked
8f4c8e92bdac XArray: Fix xas_pause for large multi-index entries
a1ffc47f22a8 dm clone metadata: Fix return type of dm_clone_nr_of_hydrated_regions()
996f8f1ba72a dm clone: Add overflow check for number of regions
2e703059348d dm verity fec: fix memory leak in verity_fec_dtr
833309f3fb51 dm integrity: fix a crash with unusually large tag size
bef0d2f5fdcb dm writecache: add cond_resched to avoid CPU hangs
5c84ab9c96d7 mm, memcg: do not high throttle allocators based on wraparound
935e87b20c56 arm64: dts: allwinner: h5: Fix PMU compatible
1dbfae009525 sched/core: Remove duplicate assignment in sched_tick_remote()
8b068046321f arm64: dts: allwinner: h6: Fix PMU compatible
27dbb3633809 net: qualcomm: rmnet: Allow configuration updates to existing devices
add09c86cd3e tools: gpio: Fix out-of-tree build regression
a0f079ac13be powerpc/pseries: Drop pointless static qualifier in vpa_debugfs_init()
e0ae9da3fb2f mmc: sdhci-of-esdhc: fix esdhc_reset() for different controller versions
7661469ef56e io_uring: honor original task RLIMIT_FSIZE
a181a74610e6 erofs: correct the remaining shrink objects
433868b19ce0 crypto: mxs-dcp - fix scatterlist linearization for hash
248414f50596 crypto: rng - Fix a refcounting bug in crypto_rng_reset()
6b936b1872ba remoteproc: Fix NULL pointer dereference in rproc_virtio_notify
5b677eddc547 remoteproc: qcom_q6v5_mss: Reload the mba region on coredump
241f681d19e1 remoteproc: qcom_q6v5_mss: Don't reassign mpss region on shutdown
87a9058d5552 btrfs: use nofs allocations for running delayed items
0425813c2279 btrfs: fix missing semaphore unlock in btrfs_sync_file
08e69ab983da btrfs: unset reloc control if we fail to recover
098d3da1ad30 btrfs: fix missing file extent item for hole after ranged fsync
b436fbff6fca btrfs: drop block from cache on error in relocation
dd68ba0d7355 btrfs: set update the uuid generation as soon as possible
441b83a84208 btrfs: reloc: clean dirty subvols if we fail to start a transaction
1bd44cada415 Btrfs: fix crash during unmount due to race with delayed inode workers
941dabde6c1a btrfs: Don't submit any btree write bio if the fs has errors
0297b7f9842e mtd: spinand: Do not erase the block before writing a bad block marker
4da7c98c3081 mtd: spinand: Stop using spinand->oobbuf for buffering bad block markers
c138ad0741fc CIFS: Fix bug which the return value by asynchronous read is error
9b35348318d1 smb3: fix performance regression with setting mtime
40888c31aca3 KVM: VMX: fix crash cleanup when KVM wasn't used
93a2b7368862 KVM: VMX: Add a trampoline to fix VMREAD error handling
771b9374a529 KVM: x86: Gracefully handle __vmalloc() failure during VM allocation
455f37affe13 KVM: VMX: Always VMCLEAR in-use VMCSes during crash with kexec support
bcd1d7462aba KVM: x86: Allocate new rmap and large page tracking when moving memslot
0c7fb8c91c0f KVM: s390: vsie: Fix delivery of addressing exceptions
654b70e84710 KVM: s390: vsie: Fix region 1 ASCE sanity shadow address checks
2c5bfcda8791 KVM: nVMX: Properly handle userspace interrupt window request
99a890ed7009 platform/x86: asus-wmi: Support laptops where the first battery is named BATT
bd90b96e3486 x86/entry/32: Add missing ASM_CLAC to general_protection entry
3dc06261a41f x86/tsc_msr: Make MSR derived TSC frequency more accurate
41a7f842e312 x86/tsc_msr: Fix MSR_FSB_FREQ mask for Cherry Trail devices
6c63cf15d066 x86/tsc_msr: Use named struct initializers
5f2d04139aa5 signal: Extend exec_id to 64bits
0a993df8d609 ath9k: Handle txpower changes even when TPC is disabled
d941b33bdc68 PM: sleep: wakeup: Skip wakeup_source_sysfs_remove() if device is not there
4fcbc35fab57 PM / Domains: Allow no domain-idle-states DT property in genpd when parsing
5bd5307cd264 MIPS: OCTEON: irq: Fix potential NULL pointer dereference
ed374eee8ce6 MIPS/tlbex: Fix LDDIR usage in setup_pw() for Loongson-3
4acbbe98e06a pstore: pstore_ftrace_seq_next should increase position index
38119a689766 io_uring: remove bogus RLIMIT_NOFILE check in file registration
6124e10dbc4f irqchip/versatile-fpga: Apply clear-mask earlier
3f3700c4697b genirq/debugfs: Add missing sanity checks to interrupt injection
6ecc37daf64e cpu/hotplug: Ignore pm_wakeup_pending() for disable_nonboot_cpus()
4b67e5afc2a0 KEYS: reaching the keys quotas correctly
f7384f90ecc7 tpm: tpm2_bios_measurements_next should increase position index
27544e1bdcc6 tpm: tpm1_bios_measurements_next should increase position index
96e05bb57b40 tpm: Don't make log failures fatal
524089fa70ef sched/fair: Fix enqueue_task_fair warning
8b6f8619fc96 PCI: endpoint: Fix for concurrent memory allocation in OB address region
96843346b201 PCI: qcom: Fix the fixup of PCI_VENDOR_ID_QCOM
55b61a08bf86 PCI: Add boot interrupt quirk mechanism for Xeon chipsets
72d52a779e99 PCI/ASPM: Clear the correct bits when enabling L1 substates
463181e64f5f PCI: pciehp: Fix indefinite wait on sysfs requests
c755ca32c8cd efi/x86: Add TPM related EFI tables to unencrypted mapping checks
91bed1f1fb97 nvme-fc: Revert "add module to ops template to allow module references"
0eb4d8b985be nvmet-tcp: fix maxh2cdata icresp parameter
b3c7227ad4c6 thermal: devfreq_cooling: inline all stubs for CONFIG_DEVFREQ_THERMAL=n
e7251a88d387 ACPI: PM: s2idle: Refine active GPEs check
dd993e283bc3 ACPICA: Allow acpi_any_gpe_status_set() to skip one GPE
1efd20ea57d4 acpi/x86: ignore unspecified bit positions in the ACPI global lock field
52e6985f2c91 seccomp: Add missing compat_ioctl for notify
15ae94fe2211 media: ti-vpe: cal: fix a kernel oops when unloading module
3a59d985ceb1 media: ti-vpe: cal: fix disable_irqs to only the intended target
46b0e2900ee2 media: hantro: Read be32 words starting at every fourth byte
7ac962c5b730 media: venus: firmware: Ignore secure call error on first resume
be9956bac91a ALSA: hda/realtek - Add quirk for MSI GL63
09e7b678f3e0 ALSA: hda/realtek - Add quirk for Lenovo Carbon X1 8th gen
f5462668ad94 ALSA: hda/realtek - Remove now-unnecessary XPS 13 headphone noise fixups
a92931dea6b1 ALSA: hda/realtek - Set principled PC Beep configuration for ALC256
0f18192b6924 ALSA: doc: Document PC Beep Hidden Register on Realtek ALC256
3e7167475236 ALSA: hda/realtek - a fake key event is triggered by running shutup
faea94956333 ALSA: hda/realtek: Enable mute LED on an HP system
1dfcd70d1fcc ALSA: pcm: oss: Fix regression by buffer overflow fix
e3ab9c5540e3 ALSA: ice1724: Fix invalid access for enumerated ctl items
6a9ba565b41f ALSA: hda: Fix potential access overflow in beep helper
f4f0a1f017e0 ALSA: hda: Add driver blacklist
1ee0023c340e ALSA: usb-audio: Add mixer workaround for TRX40 and co
78a92756fc2c usb: gadget: composite: Inform controller driver of self-powered
a385ebdaa4dc usb: gadget: f_fs: Fix use after free issue as part of queue failure
9a8b1ba9d41f ASoC: topology: use name_prefix for new kcontrol
f467e054c03f ASoC: dpcm: allow start or stop during pause for backend
af0b76f9f632 ASoC: dapm: connect virtual mux with default value
803db8a07868 ASoC: fix regwmask
acec0e9a916a btrfs: track reloc roots based on their commit root bytenr
9632851a5326 btrfs: restart relocate_tree_blocks properly
ddc25a38ab36 btrfs: remove a BUG_ON() from merge_reloc_roots()
679885143c04 btrfs: qgroup: ensure qgroup_rescan_running is only set when the worker is at least queued
b37de1b1e882 block, bfq: fix use-after-free in bfq_idle_slice_timer_body
bd9afea9bde7 locking/lockdep: Avoid recursion in lockdep_count_{for,back}ward_deps()
b9da72cb7019 spi: spi-fsl-dspi: Replace interruptible wait queue with a simple completion
64a97384d4f4 firmware: fix a double abort case with fw_load_sysfs_fallback
2d29a61a14fa md: check arrays is suspended in mddev_detach before call quiesce operations
6420b2e5fa66 irqchip/gic-v4: Provide irq_retrigger to avoid circular locking dependency
80e85ab88b3f usb: dwc3: core: add support for disabling SS instances in park mode
b6257832dd45 media: i2c: ov5695: Fix power on and off sequences
510b4e069508 block: Fix use-after-free issue accessing struct io_cq
b9d5ced37ac7 genirq/irqdomain: Check pointer in irq_domain_alloc_irqs_hierarchy()
bceda1dd4716 efi/x86: Ignore the memory attributes table on i386
fc427b7a0266 x86/boot: Use unsigned comparison for addresses
f6bb3ea812f0 cpufreq: imx6q: fix error handling
c5bcaacd0640 gfs2: Don't demote a glock until its revokes are written
46bbc5526dd7 gfs2: Do log_flush in gfs2_ail_empty_gl even if ail list is empty
aa547b9dc20f pstore/platform: fix potential mem leak if pstore_init_fs failed
347f091094ab libata: Remove extra scsi_host_put() in ata_scsi_add_hosts()
288761c9f0a2 media: i2c: video-i2c: fix build errors due to 'imply hwmon'
fb80a18584a4 block, bfq: move forward the getting of an extra ref in bfq_bfqq_move
d1d846fb02a8 PCI/switchtec: Fix init_completion race condition with poll_wait()
75434bcc6593 selftests/x86/ptrace_syscall_32: Fix no-vDSO segfault
dd39eadc71d4 sched: Avoid scale real weight down to zero
f7557078e16e media: allegro: fix type of gop_length in channel_create message
2902207377f8 time/sched_clock: Expire timer in hardirq context
3f755f5233a2 irqchip/versatile-fpga: Handle chained IRQs properly
c8b81c33c5cb debugfs: Check module state before warning in {full/open}_proxy_open()
fd66df97dce9 block: keep bdi->io_pages in sync with max_sectors_kb for stacked devices
e88ee287fd82 dma-mapping: Fix dma_pgprot() for unencrypted coherent pages
aa04e8d359d7 x86: Don't let pgprot_modify() change the page encryption bit
ce7a61a0d57d ACPI: EC: Do not clear boot_ec_is_ecdt in acpi_ec_add()
99e20a79d215 xhci: bail out early if driver can't accress host in resume
61ed3dcad80c media: imx: imx7-media-csi: Fix video field handling
dd051f1af594 media: imx: imx7_mipi_csis: Power off the source when stopping streaming
502b83e73e35 null_blk: fix spurious IO errors after failed past-wp access
38c1299f8c5c null_blk: Handle null_add_dev() failures properly
becd9a906657 null_blk: Fix the null_add_dev() error path
f9ee512dd913 firmware: arm_sdei: fix double-lock on hibernate with shared events
7bf2c31ba0bb media: venus: hfi_parser: Ignore HEVC encoding for V1
0d3d868b34af staging: wilc1000: avoid double unlocking of 'wilc->hif_cs' mutex
d5bc44e6b0d4 cpufreq: imx6q: Fixes unwanted cpu overclocking on i.MX6ULL
33dbe5867c39 media: rc: add keymap for Videostrong KII Pro
a5ef462303e0 i2c: pca-platform: Use platform_irq_get_optional
54d09aab81aa i2c: st: fix missing struct parameter description
28f5b6ee1c2f qlcnic: Fix bad kzalloc null test
d7f6f2b0be09 cfg80211: Do not warn on same channel at the end of CSA
068168461e68 drm/scheduler: fix rare NULL ptr race
f5429ec64f4f cxgb4/ptp: pass the sign of offset delta in FW CMD
d2037f68ae03 selftests/net: add definition for SOL_DCCP to fix compilation errors for old libc
9a3f55fc0f46 hinic: fix wrong value of MIN_SKB_LEN
a8f9fe793001 hinic: fix wrong para of wait_for_completion_timeout
243ebc24e01c hinic: fix out-of-order excution in arm cpu
5edd115ba09e hinic: fix the bug of clearing event queue
d63fac896335 hinic: fix a bug of waitting for IO stopped
ad4ad8253f89 net: vxge: fix wrong __VA_ARGS__ usage
b9c961998565 net: stmmac: platform: Fix misleading interrupt error msg
f96f2c885eda rxrpc: Fix call interruptibility handling
f8da7f442861 rxrpc: Abstract out the calculation of whether there's Tx space
96860db5c09f soc: fsl: dpio: register dpio irq handlers after dpio create
10e15e1b9297 Input: tm2-touchkey - add support for Coreriver TC360 variant
ed1c4d2ca9da iwlwifi: mvm: Fix rate scale NSS configuration
fd29a0242f86 bpf: Fix deadlock with rq_lock in bpf_send_signal()
5c234312e805 ARM: dts: Fix dm814x Ethernet by changing to use rgmii-id mode
d04ffa50f901 bus: sunxi-rsb: Return correct data when mixing 16-bit and 8-bit reads
7092cc4590c0 ARM: dts: sun8i-a83t-tbs-a711: HM5065 doesn't like such a high voltage
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
---
.../linux/linux-yocto-rt_5.4.bb | 6 ++---
.../linux/linux-yocto-tiny_5.4.bb | 8 +++----
meta/recipes-kernel/linux/linux-yocto_5.4.bb | 22 +++++++++----------
3 files changed, 18 insertions(+), 18 deletions(-)
diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb b/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb
index 42e4bca574..d550bf5371 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb
@@ -11,13 +11,13 @@ python () {
raise bb.parse.SkipRecipe("Set PREFERRED_PROVIDER_virtual/kernel to linux-yocto-rt to enable it")
}
-SRCREV_machine ?= "2348504c2c1035e1d7227d25224c9345f7b129d3"
-SRCREV_meta ?= "fa59277b2013ec395f3beb3656becb48fdf4b555"
+SRCREV_machine ?= "c7609ad17612bd59c1cadb53faf23be8fd7250ef"
+SRCREV_meta ?= "054d410d1a73e4729f1fe7540db058de69fe8cfe"
SRC_URI = "git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine \
git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-5.4;destsuffix=${KMETA}"
-LINUX_VERSION ?= "5.4.32"
+LINUX_VERSION ?= "5.4.34"
LIC_FILES_CHKSUM = "file://COPYING;md5=bbea815ee2795b2f4230826c0c6b8814"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb b/meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb
index ec4e7679f1..078a15cec0 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb
@@ -6,7 +6,7 @@ KCONFIG_MODE = "--allnoconfig"
require recipes-kernel/linux/linux-yocto.inc
-LINUX_VERSION ?= "5.4.32"
+LINUX_VERSION ?= "5.4.34"
LIC_FILES_CHKSUM = "file://COPYING;md5=bbea815ee2795b2f4230826c0c6b8814"
DEPENDS += "${@bb.utils.contains('ARCH', 'x86', 'elfutils-native', '', d)}"
@@ -15,9 +15,9 @@ DEPENDS += "openssl-native util-linux-native"
KMETA = "kernel-meta"
KCONF_BSP_AUDIT_LEVEL = "2"
-SRCREV_machine_qemuarm ?= "63425cc3498f7f10b1571b38718ed47234d5ade7"
-SRCREV_machine ?= "d66ed1ee791577746d30b29baef734fbb9297431"
-SRCREV_meta ?= "fa59277b2013ec395f3beb3656becb48fdf4b555"
+SRCREV_machine_qemuarm ?= "ba0b1e26460cb764005af5758334fc1777760dfd"
+SRCREV_machine ?= "e378a5626133c1f46c7ee4ede3785dbb805dc5ab"
+SRCREV_meta ?= "054d410d1a73e4729f1fe7540db058de69fe8cfe"
PV = "${LINUX_VERSION}+git${SRCPV}"
diff --git a/meta/recipes-kernel/linux/linux-yocto_5.4.bb b/meta/recipes-kernel/linux/linux-yocto_5.4.bb
index 485928bd88..e225094698 100644
--- a/meta/recipes-kernel/linux/linux-yocto_5.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_5.4.bb
@@ -12,16 +12,16 @@ KBRANCH_qemux86 ?= "v5.4/standard/base"
KBRANCH_qemux86-64 ?= "v5.4/standard/base"
KBRANCH_qemumips64 ?= "v5.4/standard/mti-malta64"
-SRCREV_machine_qemuarm ?= "bee6048166651d8c69327a0b0ff4f4b87d961d5c"
-SRCREV_machine_qemuarm64 ?= "d66ed1ee791577746d30b29baef734fbb9297431"
-SRCREV_machine_qemumips ?= "2180ef2ea5645cf63a1aa738f15e72c240c313ea"
-SRCREV_machine_qemuppc ?= "d66ed1ee791577746d30b29baef734fbb9297431"
-SRCREV_machine_qemuriscv64 ?= "d66ed1ee791577746d30b29baef734fbb9297431"
-SRCREV_machine_qemux86 ?= "d66ed1ee791577746d30b29baef734fbb9297431"
-SRCREV_machine_qemux86-64 ?= "d66ed1ee791577746d30b29baef734fbb9297431"
-SRCREV_machine_qemumips64 ?= "6afe026b32fd5ac553420f68052a665e3fcacd53"
-SRCREV_machine ?= "d66ed1ee791577746d30b29baef734fbb9297431"
-SRCREV_meta ?= "fa59277b2013ec395f3beb3656becb48fdf4b555"
+SRCREV_machine_qemuarm ?= "440e41f2f471ba2bb5e3c801ffc140523bdd59b1"
+SRCREV_machine_qemuarm64 ?= "e378a5626133c1f46c7ee4ede3785dbb805dc5ab"
+SRCREV_machine_qemumips ?= "941c329c8810e946840bd2f4ab983a94651e563f"
+SRCREV_machine_qemuppc ?= "e378a5626133c1f46c7ee4ede3785dbb805dc5ab"
+SRCREV_machine_qemuriscv64 ?= "e378a5626133c1f46c7ee4ede3785dbb805dc5ab"
+SRCREV_machine_qemux86 ?= "e378a5626133c1f46c7ee4ede3785dbb805dc5ab"
+SRCREV_machine_qemux86-64 ?= "e378a5626133c1f46c7ee4ede3785dbb805dc5ab"
+SRCREV_machine_qemumips64 ?= "b73834a11da2d4327cc3cb9f33fa3540f24d56aa"
+SRCREV_machine ?= "e378a5626133c1f46c7ee4ede3785dbb805dc5ab"
+SRCREV_meta ?= "054d410d1a73e4729f1fe7540db058de69fe8cfe"
# remap qemuarm to qemuarma15 for the 5.4 kernel
# KMACHINE_qemuarm ?= "qemuarma15"
@@ -30,7 +30,7 @@ SRC_URI = "git://git.yoctoproject.org/linux-yocto.git;name=machine;branch=${KBRA
git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-5.4;destsuffix=${KMETA}"
LIC_FILES_CHKSUM = "file://COPYING;md5=bbea815ee2795b2f4230826c0c6b8814"
-LINUX_VERSION ?= "5.4.32"
+LINUX_VERSION ?= "5.4.34"
DEPENDS += "${@bb.utils.contains('ARCH', 'x86', 'elfutils-native', '', d)}"
DEPENDS += "openssl-native util-linux-native"
--
2.19.1
^ permalink raw reply related [flat|nested] 64+ messages in thread
* [PATCH 4/5] linux-yocto/5.4: update to v5.4.38
2020-05-03 15:44 [PATCH 0/5] linux-yocto: consolidated pull request Bruce Ashfield
` (2 preceding siblings ...)
2020-05-03 15:44 ` [PATCH 3/5] linux-yocto/5.4: update to v5.4.34 Bruce Ashfield
@ 2020-05-03 15:44 ` Bruce Ashfield
2020-05-03 15:44 ` [PATCH 5/5] linux-yocto-dev: bump to v5.7-rc Bruce Ashfield
2020-05-04 8:30 ` [PATCH 0/5] linux-yocto: consolidated pull request Richard Purdie
5 siblings, 0 replies; 64+ messages in thread
From: Bruce Ashfield @ 2020-05-03 15:44 UTC (permalink / raw)
To: richard.purdie; +Cc: openembedded-core, steve
From: Bruce Ashfield <bruce.ashfield@gmail.com>
Updating linux-yocto/5.4 to the latest korg -stable release that comprises
the following commits:
9895e0ac338a Linux 5.4.38
5a54c69c4ef8 Revert "ASoC: meson: axg-card: fix codec-to-codec link setup"
527c60e8b7a8 Linux 5.4.37
4e7fb753e803 ASoC: stm32: spdifrx: fix regmap status check
4104faaeeda0 ASoC: soc-core: disable route checks for legacy devices
8c472abaedc7 ext4: check for non-zero journal inum in ext4_calculate_overhead
93af898b251f qed: Fix use after free in qed_chain_free
f1610480602a net: use indirect call wrappers for skb_copy_datagram_iter()
ec9cf8afcd64 Crypto: chelsio - Fixes a hang issue during driver registration
b0946b45b85a qed: Fix race condition between scheduling and destroying the slowpath workqueue
d15fc1470441 taprio: do not use BIT() in TCA_TAPRIO_ATTR_FLAG_* definitions
f37079e9ea83 hwmon: (jc42) Fix name to have no illegal characters
c7b6c51298bd blk-mq: Put driver tag in blk_mq_dispatch_rq_list() when no budget
3e9299c28fc5 ext4: convert BUG_ON's to WARN_ON's in mballoc.c
1e4281eba3ff ext4: increase wait time needed before reuse of deleted inode numbers
0fe3908e6abc ext4: use matching invalidatepage in ext4_writepage
1876e0e654b8 arm64: Delete the space separator in __emit_inst
a719f7bf5c88 mac80211: fix channel switch trigger from unknown mesh peer
9178430df3f7 net: stmmac: socfpga: Allow all RGMII modes
daafdf87b898 ALSA: hda: call runtime_allow() for all hda controllers
d9d4ea17d6d6 xen/xenbus: ensure xenbus_map_ring_valloc() returns proper grant status
8c627d4b15de objtool: Support Clang non-section symbols in ORC dump
820126d9a83d objtool: Fix CONFIG_UBSAN_TRAP unreachable warnings
1cc2460dad82 scsi: target: tcmu: reset_ring should reset TCMU_DEV_BIT_BROKEN
62d350eb31d1 scsi: target: fix PR IN / READ FULL STATUS for FC
a323f69d00c6 ALSA: hda: Explicitly permit using autosuspend if runtime PM is supported
bd074af53cb6 ALSA: hda: Keep the controller initialization even if no codecs found
135e10232fb5 ALSA: hda: Release resources at error in delayed probe
535ed3f01564 xfs: fix partially uninitialized structure in xfs_reflink_remap_extent
ec6e5792d62d afs: Fix length of dump of bad YFSFetchStatus record
16976275b929 signal: check sig before setting info in kill_pid_usb_asyncio
f88761412b90 x86: hyperv: report value of misc_features
b5da1152f716 net: fec: set GPR bit on suspend by DT configuration.
316ad98983d9 libbpf: Initialize *nl_pid so gcc 10 is happy
3c9bbe7f44f6 bpf, x86: Fix encoding for lower 8-bit registers in BPF_STX BPF_B
ab6e8af64f39 xfs: clear PF_MEMALLOC before exiting xfsaild thread
e5329fcdc907 mm: shmem: disable interrupt when acquiring info->lock in userfaultfd_copy path
309a509dabd5 bpf, x86_32: Fix logic error in BPF_LDX zero-extension
d0b8695703f2 bpf, x86_32: Fix clobbering of dst for BPF_JSET
50c5d9146100 bpf, x86_32: Fix incorrect encoding in BPF_LDX zero-extension
ca3a2ca4cfa2 um: ensure `make ARCH=um mrproper` removes arch/$(SUBARCH)/include/generated/
9c5c94c5012c blk-iocost: Fix error on iocost_ioc_vrate_adj
b9c31556c37b PM: sleep: core: Switch back to async_schedule_dev()
36c436a8e46a netfilter: nat: fix error handling upon registering inet hook
9578a8c157b4 perf/core: fix parent pid/tid in task exit events
c04d01e918d8 sched/core: Fix reset-on-fork from RT with uclamp
040287785f42 net/mlx5: Fix failing fw tracer allocation on s390
a8b5611ffee3 s390/pci: do not set affinity for floating irqs
6cfb8c2ada58 cpumap: Avoid warning when CONFIG_DEBUG_PER_CPU_MAPS is enabled
05ae98547af9 ARM: dts: bcm283x: Disable dsi0 node
764a7d0a2756 PCI: Move Apex Edge TPU class quirk to fix BAR assignment
684dba87fdd7 PCI: Add ACS quirk for Zhaoxin Root/Downstream Ports
17d166e9535c PCI: Add Zhaoxin Vendor ID
d2481b5d1257 PCI: Unify ACS quirk desired vs provided checking
981fd6ad2a5a PCI: Make ACS quirk implementations more uniform
85a9e198f124 PCI: Add ACS quirk for Zhaoxin multi-function devices
d2b631a136e8 PCI: Avoid ASMedia XHCI USB PME# from D0 defect
246ff2a6f69e net/mlx5e: Get the latest values from counters in switchdev mode
2292e4049097 net/mlx5e: Don't trigger IRQ multiple times on XSK wakeup to avoid WQ overruns
b4284efb1e14 svcrdma: Fix leak of svc_rdma_recv_ctxt objects
53dbb934dd4f svcrdma: Fix trace point use-after-free race
ccd3b4bb9944 xfs: acquire superblock freeze protection on eofblocks scans
62f1cb491552 net/cxgb4: Check the return from t4_query_params properly
ce3460b90ed9 rxrpc: Fix DATA Tx to disable nofrag for UDP on AF_INET6 socket
6cdded333de6 i2c: altera: use proper variable to hold errno
db2426f86d44 bpf: Forbid XADD on spilled pointers for unprivileged users
f1317a4a2b9b nfsd: memory corruption in nfsd4_lock()
13b28f6b6778 drivers: soc: xilinx: fix firmware driver Kconfig dependency
1157d97cfa2b ASoC: wm8960: Fix wrong clock after suspend & resume
005aa9f0af9d ASoC: meson: axg-card: fix codec-to-codec link setup
08865eb796c4 ASoC: tas571x: disable regulators on failed probe
e9058b45556b ASoC: q6dsp6: q6afe-dai: add missing channels to MI2S DAIs
37405f2963c7 s390/ftrace: fix potential crashes when switching tracers
1f107e441bde counter: 104-quad-8: Add lock guards - generic interface
db66fd5fef68 propagate_one(): mnt_set_mountpoint() needs mount_lock
f9e41e4bbe61 iio:ad7797: Use correct attribute_group
f581eff93958 afs: Fix to actually set AFS_SERVER_FL_HAVE_EPOCH
c2bdc86ec8ac afs: Make record checking use TASK_UNINTERRUPTIBLE when appropriate
9dcb1844f884 usb: gadget: udc: atmel: Fix vbus disconnect handling
7155416143dd usb: gadget: udc: bdc: Remove unnecessary NULL checks in bdc_req_complete
8f4cd6f0ea82 kbuild: fix DT binding schema rule again to avoid needless rebuilds
7067a62563d2 usb: dwc3: gadget: Do link recovery for SS and SSP
a74a5435a610 ASoC: stm32: sai: fix sai probe
4a5c9ae67b12 printk: queue wake_up_klogd irq_work only if per-CPU areas are ready
276224b7a147 ubifs: Fix ubifs_tnc_lookup() usage in do_kill_orphans()
4d23f544a328 remoteproc: Fix wrong rvring index computation
aa73bcc37686 Linux 5.4.36
44d9eb0ebe8f s390/mm: fix page table upgrade vs 2ndary address mode accesses
58b243cf2786 compat: ARM64: always include asm-generic/compat.h
3160e84abaf7 powerpc/mm: Fix CONFIG_PPC_KUAP_DEBUG on PPC32
b48331b52a28 powerpc/kuap: PPC_KUAP_DEBUG should depend on PPC_KUAP
c4606876164c Revert "serial: uartps: Register own uart console and driver structures"
02d32033b397 Revert "serial: uartps: Move Port ID to device data structure"
bbc0423c8968 Revert "serial: uartps: Change uart ID port allocation"
f7504efa6bf7 Revert "serial: uartps: Do not allow use aliases >= MAX_UART_INSTANCES"
3e64d4db7b10 Revert "serial: uartps: Fix error path when alloc failed"
6fcbf58b115c Revert "serial: uartps: Use the same dynamic major number for all ports"
1bb43b4d8c32 Revert "serial: uartps: Fix uartps_major handling"
3af0614df15c serial: sh-sci: Make sure status register SCxSR is read in correct sequence
fceab238c534 xhci: Don't clear hub TT buffer on ep0 protocol stall
54470b0bd16a xhci: prevent bus suspend if a roothub port detected a over-current condition
f385e765ac93 xhci: Fix handling halted endpoint even if endpoint ring appears empty
8dbfb11452c0 usb: typec: altmode: Fix typec_altmode_get_partner sometimes returning an invalid pointer
740c93814783 usb: typec: tcpm: Ignore CC and vbus changes in PORT_RESET change
11c2089767cd usb: f_fs: Clear OS Extended descriptor counts to zero in ffs_data_reset()
bf996950d8de usb: dwc3: gadget: Fix request completion check
a0f1f53ecd8d fpga: dfl: pci: fix return value of cci_pci_sriov_configure
22432bcf066c UAS: fix deadlock in error handling and PM flushing work
e1b656677f7d UAS: no use logging any details in case of ENODEV
f4d1cf2ef83c cdc-acm: introduce a cool down
892de572ea71 cdc-acm: close race betrween suspend() and acm_softint
23d44059bc44 staging: vt6656: Power save stop wake_up_count wrap around.
9f1a23cbef73 staging: vt6656: Fix pairwise key entry save.
0bcc6585717e staging: vt6656: Fix drivers TBTT timing counter.
74bbe9d99040 staging: vt6656: Fix calling conditions of vnt_set_bss_mode
ec5ad5e1958c staging: vt6656: Don't set RCR_MULTICAST or RCR_BROADCAST by default.
64882aa0c531 vt: don't use kmalloc() for the unicode screen buffer
b027b30d1428 vt: don't hardcode the mem allocation upper bound
8f8d7f07d951 staging: comedi: Fix comedi_device refcnt leak in comedi_open
279dd75cec55 staging: comedi: dt2815: fix writing hi byte of analog output
dba6465408b8 powerpc/setup_64: Set cache-line-size based on cache-block-size
921b7b175605 ARM: imx: provide v7_cpu_resume() only on ARM_CPU_SUSPEND=y
eabc107d20da cifs: fix uninitialised lease_key in open_shroot()
562489ba1078 iwlwifi: mvm: fix inactive TID removal return value usage
f1926b14bd8f iwlwifi: mvm: Do not declare support for ACK Enabled Aggregation
c93fb506bfaf iwlwifi: mvm: limit maximum queue appropriately
4025ac3d7fb7 iwlwifi: mvm: beacon statistics shouldn't go backwards
222722be70de iwlwifi: pcie: actually release queue memory in TVQM
7e69c9e6bbf3 SUNRPC: Fix backchannel RPC soft lockups
d62d85260ac4 mac80211: populate debugfs only after cfg80211 init
f67f3317ceb3 ASoC: dapm: fixup dapm kcontrol widget
83f82fd5552c audit: check the length of userspace generated audit records
20821047aca4 signal: Avoid corrupting si_pid and si_uid in do_notify_parent
1b4e23a945bd usb-storage: Add unusual_devs entry for JMicron JMS566
9de9003b255e tty: rocket, avoid OOB access
f1c0d3243dbe tty: hvc: fix buffer overflow during hvc_alloc().
52ca311e5f82 KVM: VMX: Enable machine check support for 32bit targets
878127ac8b70 KVM: Check validity of resolved slot when searching memslots
347125705f02 KVM: s390: Return last valid slot if approx index is out-of-bounds
3fc644fd6100 tpm: ibmvtpm: retry on H_CLOSED in tpm_ibmvtpm_send()
16244edc3bbe tpm: fix wrong return value in tpm_pcr_extend
86f1c523d422 tpm/tpm_tis: Free IRQ if probing fails
387039b25077 ALSA: usb-audio: Filter out unsupported sample rates on Focusrite devices
d5cd82153629 ALSA: usb-audio: Fix usb audio refcnt leak when getting spdif
dbb11f1d6d33 ALSA: hda/hdmi: Add module option to disable audio component binding
1e1f9d36280f ALSA: hda/realtek - Add new codec supported for ALC245
0939d06af06f ALSA: hda/realtek - Fix unexpected init_amp override
16e373fe61cb ALSA: usx2y: Fix potential NULL dereference
000515184f6f tools/vm: fix cross-compile build
5126bdeaf980 mm/ksm: fix NULL pointer dereference when KSM zero page is enabled
3c88e95cd167 mm/hugetlb: fix a addressing exception caused by huge_pte_offset
a77daafc2e37 coredump: fix null pointer dereference on coredump
fcfd63da5d82 staging: gasket: Fix incongruency in handling of sysfs entries creation
f4f235309b5c vmalloc: fix remap_vmalloc_range() bounds checks
3d15344e23c5 tty: serial: owl: add "much needed" clk_prepare_enable()
4fbf19bbba6a USB: hub: Revert commit bd0e6c9614b9 ("usb: hub: try old enumeration scheme first for high speed devices")
50ad463e20bf USB: hub: Fix handling of connect changes during sleep
b48193a7c303 USB: core: Fix free-while-in-use bug in the USB S-Glibrary
1d53402d89d7 USB: early: Handle AMD's spec-compliant identifiers, too
8409f83e3e81 USB: Add USB_QUIRK_DELAY_CTRL_MSG and USB_QUIRK_DELAY_INIT for Corsair K70 RGB RAPIDFIRE
b7758cd38b94 USB: sisusbvga: Change port variable from signed to unsigned
557f3f549217 iio: xilinx-xadc: Make sure not exceed maximum samplerate
b3e365a07016 iio: xilinx-xadc: Fix sequencer configuration for aux channels in simultaneous mode
cf2849c9ef46 iio: xilinx-xadc: Fix clearing interrupt when enabling trigger
6a956eb2e1a7 iio: xilinx-xadc: Fix ADC-B powerdown
f83a969fcb0b iio: adc: ti-ads8344: properly byte swap value
db168069b0d6 iio: adc: stm32-adc: fix sleep in atomic context
02311bc13344 iio: st_sensors: rely on odr mask to know if odr can be set
14952589c9d8 iio: core: remove extra semi-colon from devm_iio_device_register() macro
12c02c473e86 ALSA: usb-audio: Add connector notifier delegation
6ec99b94a3a0 ALSA: usb-audio: Add static mapping table for ALC1220-VB-based mobos
23abb5f2faea ALSA: hda: Remove ASUS ROG Zenith from the blacklist
419d8fb1630c KEYS: Avoid false positive ENOMEM error on key read
b1bcb485dd6b vrf: Check skb for XFRM_TRANSFORMED flag
dfbbb4557af4 xfrm: Always set XFRM_TRANSFORMED in xfrm{4,6}_output_finish
ace87b487a5f geneve: use the correct nlattr array in NL_SET_ERR_MSG_ATTR
b977fe1c9e80 vxlan: use the correct nlattr array in NL_SET_ERR_MSG_ATTR
51c935f6c6ef net: dsa: b53: b53_arl_rw_op() needs to select IVL or SVL
cb1a18a7d328 net: dsa: b53: Rework ARL bin logic
2cc27f102dcd net: dsa: b53: Fix ARL register definitions
1fae6eb0fc91 net: dsa: b53: Fix valid setting for MDB entries
2537dc9e2c03 net: dsa: b53: Lookup VID in ARL searches when VLAN is enabled
07856b2108cf vrf: Fix IPv6 with qdisc and xfrm
755425c1b004 team: fix hang in team_mode_get()
3f642d785a51 tcp: cache line align MAX_TCP_HEADER
8a60fad4495d selftests: Fix suppress test in fib_tests.sh
a3afaa5033f4 sched: etf: do not assume all sockets are full blown
5a2ddf8e5a5d net/x25: Fix x25_neigh refcnt leak when receiving frame
6885d58eb439 net: stmmac: dwmac-meson8b: Add missing boundary to RGMII TX clock array
4acc0b18f7af net: openvswitch: ovs_ct_exit to be done under ovs_lock
21b1a767eba6 net: netrom: Fix potential nr_neigh refcnt leak in nr_add_node
befd63a980cc net/mlx4_en: avoid indirect call in TX completion
49bbf322316c net: bcmgenet: correct per TX/RX ring statistics
aa6a14bc4102 mlxsw: Fix some IS_ERR() vs NULL bugs
d5ba4c22928f macvlan: fix null dereference in macvlan_device_event()
70a37b9816f3 macsec: avoid to set wrong mtu
2d197d8e1aa4 ipv6: fix restrict IPV6_ADDRFORM operation
382f57b996aa ipv4: Update fib_select_default to handle nexthop objects
3b759befd7f2 cxgb4: fix large delays in PTP synchronization
d02f4242650d cxgb4: fix adapter crash due to wrong MC size
91097eba10d3 PCI/PM: Add missing link delays required by the PCIe spec
7720fd9c679e PCI/ASPM: Allow re-enabling Clock PM
3340d011cff4 scsi: smartpqi: fix problem with unique ID for physical device
d867f2757173 scsi: smartpqi: fix call trace in device discovery
8a20fb1c9a49 scsi: smartpqi: fix controller lockup observed during force reboot
3edd55247295 virtio-blk: improve virtqueue error to BLK_STS
2390698b9dbd tracing/selftests: Turn off timeout setting
ca958fe8af20 ASoC: SOF: trace: fix unconditional free in trace release
01fad934f1bd PCI: pciehp: Prevent deadlock on disconnect
39b9a0b3d24d libbpf: Fix readelf output parsing on powerpc with recent binutils
b91ae5994725 PCI/PM: Add pcie_wait_for_link_delay()
df38cda0144a drm/amd/display: Not doing optimize bandwidth if flip pending.
2be21320076d xhci: Finetune host initiated USB3 rootport link suspend and resume
ea6f7011c42d xhci: Wait until link state trainsits to U0 after setting USB_SS_PORT_LS_U0
e650a264df6f xhci: Ensure link state is U3 after setting USB_SS_PORT_LS_U3
bdb61374da1b ALSA: usb-audio: Add Pioneer DJ DJM-250MK2 quirk
578aa47612f2 ASoC: Intel: bytcr_rt5640: Add quirk for MPMAN MPWIN895CL tablet
632d9736d215 drm/amd/display: Calculate scaling ratios on every medium/full update
16c370534d6c perf/core: Disable page faults when getting phys address
41a3e446bc56 pwm: bcm2835: Dynamically allocate base
53cdc935c912 pwm: renesas-tpu: Fix late Runtime PM enablement
1bfb6423c6fc nvme: fix compat address handling in several ioctls
de1263d4306e powerpc/pseries: Fix MCE handling on pseries
107290a8f06b Revert "powerpc/64: irq_work avoid interrupt when called with hardware irqs enabled"
1712911bfb34 loop: Better discard support for block devices
ed61eec49a70 s390/cio: avoid duplicated 'ADD' uevents
ad1187668ffe s390/cio: generate delayed uevent for vfio-ccw subchannels
8652254e96a6 lib/raid6/test: fix build on distros whose /bin/sh is not bash
e84ef75fa184 kconfig: qconf: Fix a few alignment issues
cb5d9604038c ipc/util.c: sysvipc_find_ipc() should increase position index
70638a74c52a selftests: kmod: fix handling test numbers above 9
16846f6fcbcf kernel/gcov/fs.c: gcov_seq_next() should increase position index
1edfff795d4f dma-direct: fix data truncation in dma_direct_get_required_mask()
8300465623bf drm/amd/display: Update stream adjust in dc_stream_adjust_vmin_vmax
da2c733a7180 nvme: fix deadlock caused by ANA update wrong locking
90a33c23aad8 ASoC: Intel: atom: Take the drv->lock mutex before calling sst_send_slot_map()
1310d9655be0 tools/test/nvdimm: Fix out of tree build
713ad9b9d37a scsi: iscsi: Report unbind session event when the target has been removed
f507ae6e33cb nvme-tcp: fix possible crash in write_zeroes processing
a5f036adae09 pwm: rcar: Fix late Runtime PM enablement
b71ac8086a7b ceph: don't skip updating wanted caps when cap is stale
acbfccc6a3e3 ceph: return ceph_mdsc_do_request() errors from __get_parent()
fb669262fdef scsi: libfc: If PRLI rejected, move rport to PLOGI state
8427b05a7a1f scsi: lpfc: Fix crash in target side cable pulls hitting WAIT_FOR_UNREG
0c5733a96261 scsi: lpfc: Fix crash after handling a pci error
9d1062c4dd14 scsi: lpfc: Fix kasan slab-out-of-bounds error in lpfc_unreg_login
66491dadd125 watchdog: reset last_hw_keepalive time at start
7b709f1ba800 tools/testing/nvdimm: Fix compilation failure without CONFIG_DEV_DAX_PMEM_COMPAT
810045068bda arm64: Silence clang warning on mismatched value/register sizes
aa50d567ec4a arm64: compat: Workaround Neoverse-N1 #1542419 for compat user-space
6de0c621191a arm64: Fake the IminLine size on systems affected by Neoverse-N1 #1542419
f2791551cedb arm64: errata: Hide CTR_EL0.DIC on systems affected by Neoverse-N1 #1542419
4b823bf7c2ca net, ip_tunnel: fix interface lookup with no key
5811f24abd27 f2fs: fix to avoid memory leakage in f2fs_listxattr
79ad14904152 ext4: fix extent_status fragmentation for plain files
0c418786cb3a Linux 5.4.35
a801a05ca714 bpf, test_verifier: switch bpf_get_stack's 0 s> r8 test
8781011a302b bpf: Test_progs, add test to catch retval refine error handling
37e1cdff90c1 bpf: Test_verifier, bpf_get_stack return value add <0
3bd5bcafbbf3 bpf: fix buggy r0 retval refinement for tracing helpers
f1afcf9488fc KEYS: Don't write out to userspace while holding key semaphore
5d53bfdce008 mtd: phram: fix a double free issue in error path
4191ebe1fc71 mtd: lpddr: Fix a double free in probe()
7d4adb1d3c69 docs: Fix path to MTD command line partition parser
318d5088fdfe mtd: spinand: Explicitly use MTD_OPS_RAW to write the bad block marker to OOB
700bccb8e9a2 mtd: rawnand: free the nand_device object
0c72ec11d8bd locktorture: Print ratio of acquisitions, not failures
01c9e2a9fc5c tty: evh_bytechan: Fix out of bounds accesses
f656649089a3 fbmem: Adjust indentation in fb_prepare_logo and fb_blank
47e4d791d514 iio: si1133: read 24-bit signed integer for measurement
a2a385aae551 ARM: dts: sunxi: Fix DE2 clocks register range
7e141c307834 fbdev: potential information leak in do_fb_ioctl()
f0938746879a dma-debug: fix displaying of dma allocation type
bc69709c54df net: dsa: bcm_sf2: Fix overflow checks
762d35aa906f drm/nouveau/gr/gp107,gp108: implement workaround for HW hanging during init
a156e67acf6c f2fs: fix to wait all node page writeback
f08e4e70b0ac iommu/amd: Fix the configuration of GCR3 table root pointer
436af737c3c2 libnvdimm: Out of bounds read in __nd_ioctl()
dcb122749f58 power: supply: axp288_fuel_gauge: Broaden vendor check for Intel Compute Sticks.
760eecac993b csky: Fixup init_fpu compile warning with __init
1500c7003146 sunrpc: Fix gss_unwrap_resp_integ() again
ddb8812a21e1 ext2: fix debug reference to ext2_xattr_cache
24191c8c9bd2 iommu/vt-d: Fix page request descriptor size
a5a1d567a069 iommu/vt-d: Silence RCU-list debugging warning in dmar_find_atsr()
21439dff919e ext2: fix empty body warnings when -Wextra is used
d00041a48c3e SUNRPC: fix krb5p mount to provide large enough buffer in rq_rcvsize
900cd0f6c688 iommu/vt-d: Fix mm reference leak
9c01a49a7117 iommu/virtio: Fix freeing of incomplete domains
475bec7063bc drm/vc4: Fix HDMI mode validation
b58244c482ce um: falloc.h needs to be directly included for older libc
6c3339269a8a ACPICA: Fixes for acpiExec namespace init file
9f8b1216dac9 f2fs: fix NULL pointer dereference in f2fs_write_begin()
57615a8561f0 csky: Fixup get wrong psr value from phyical reg
c848e00e3b95 NFS: Fix memory leaks in nfs_pageio_stop_mirroring()
2e03d3c569b6 drm/amdkfd: kfree the wrong pointer
e907a0d09b34 csky: Fixup cpu speculative execution to IO area
88591187bebc x86: ACPI: fix CPU hotplug deadlock
a9282e58238d leds: core: Fix warning message when init_data
ddf39dc2f7a3 drm/nouveau: workaround runpm fail by disabling PCI power management on certain intel bridges
f24d8de03b72 KVM: s390: vsie: Fix possible race when shadowing region 3 tables
3910babeac1a compiler.h: fix error in BUILD_BUG_ON() reporting
b525f94f16e5 percpu_counter: fix a data race at vm_committed_as
ffac60b8bc5f include/linux/swapops.h: correct guards for non_swap_entry()
2a40eaab1fc4 drm/nouveau/svm: fix vma range check for migration
f3955f1e58be drm/nouveau/svm: check for SVM initialized before migrating
a825ce86ebed mm/hugetlb: fix build failure with HUGETLB_PAGE but not HUGEBTLBFS
23e2519760f8 cifs: Allocate encryption header through kmalloc
6ba010ea4856 um: ubd: Prevent buffer overrun on command completion
b9f88c31b266 ext4: do not commit super on read-only bdev
4078dceb1228 s390/cpum_sf: Fix wrong page count in error message
fd80f4a6805c powerpc/maple: Fix declaration made after definition
bee9bc3e0248 powerpc/prom_init: Pass the "os-term" message to hypervisor
765052217847 btrfs: add RCU locks around block group initialization
285f25c97f24 hibernate: Allow uswsusp to write to swap
4753b111f003 s390/cpuinfo: fix wrong output when CPU0 is offline
380d12904603 f2fs: Add a new CP flag to help fsck fix resize SPO issues
066f1e4174f2 f2fs: Fix mount failure due to SPO after a successful online resize FS
ea468f37370a NFS: direct.c: Fix memory leak of dreq when nfs_get_lock_context fails
81b41f5ecc96 phy: uniphier-usb3ss: Add Pro5 support
3e85d501828c f2fs: fix to show norecovery mount option
ffbad91b66ce KVM: PPC: Book3S HV: Fix H_CEDE return code for nested guests
ea410f2a1fc8 ARM: dts: rockchip: fix lvds-encoder ports subnode for rk3188-bqedison2qc
59bafdc99440 NFSv4.2: error out when relink swapfile
264e3f1597e8 NFSv4/pnfs: Return valid stateids in nfs_layout_find_inode_by_stateid()
07cd4e8f745c NFS: alloc_nfs_open_context() must use the file cred when available
66bfacd0f302 rtc: 88pm860x: fix possible race condition
56aaa0e8c92a dma-coherent: fix integer overflow in the reserved-memory dma allocation
960bf4e436ca soc: imx: gpc: fix power up sequencing
1e7abaf24875 arm64: dts: clearfog-gt-8k: set gigabit PHY reset deassert delay
d7b59cd020f7 arm64: tegra: Fix Tegra194 PCIe compatible string
5615f66bfdfc arm64: tegra: Add PCIe endpoint controllers nodes for Tegra194
540f9620f192 clk: tegra: Fix Tegra PMC clock out parents
b7dee304aa0e power: supply: bq27xxx_battery: Silence deferred-probe error
6a7721714835 arm64: dts: allwinner: a64: Fix display clock register range
5d2861f840bb ARM: dts: rockchip: fix vqmmc-supply property name for rk3188-bqedison2qc
1321fb4320e7 f2fs: fix the panic in do_checkpoint()
6d4330391c49 net/mlx5e: Enforce setting of a single FEC mode
0d03cbfdf364 clk: at91: usb: continue if clk_hw_round_rate() return zero
04e43c7c664a clk: Don't cache errors from clk_ops::get_phase()
83321ee302e3 drm/ttm: flush the fence on the bo after we individualize the reservation object
94ebb1eea0e7 x86/Hyper-V: Free hv_panic_page when fail to register kmsg dump
d662b44161e4 rbd: call rbd_dev_unprobe() after unwatching and flushing notifies
88a57e387cf0 rbd: avoid a deadlock on header_rwsem when flushing notifies
a362482b2325 block, bfq: invoke flush_idle_tree after reparent_active_queues in pd_offline
839b7cd1d8bc block, bfq: make reparent_leaf_entity actually work only on leaf entities
ad749ca022ad block, bfq: turn put_queue into release_process_ref in __bfq_bic_change_cgroup
00d392873771 afs: Fix race between post-modification dir edit and readdir/d_revalidate
42e343cf3285 afs: Fix afs_d_validate() to set the right directory version
8c3e4ba0fa7a afs: Fix rename operation status delivery
4eba6ec9644a afs: Fix decoding of inline abort codes from version 1 status records
0604b60ef9d7 afs: Fix missing XDR advance in xdr_decode_{AFS,YFS}FSFetchStatus()
4f7b1e892ed0 x86/Hyper-V: Report crash data in die() when panic_on_oops is set
5097186b279a x86/Hyper-V: Report crash register data when sysctl_record_panic_msg is not set
31ebf98817c6 x86/Hyper-V: Report crash register data or kmsg before running crash kernel
1ed38a98478f x86/Hyper-V: Trigger crash enlightenment only once during system crash.
9f38f7b46de0 x86/Hyper-V: Unload vmbus channel in hv panic callback
4c2a34f9f448 of: overlay: kmemleak in dup_and_fixup_symbol_prop()
93ef21bb1a72 of: unittest: kmemleak in of_unittest_overlay_high_level()
a1371954ee49 of: unittest: kmemleak in of_unittest_platform_populate()
dd3dd28241e0 of: unittest: kmemleak on changeset destroy
25c9cdef5748 xsk: Add missing check on user supplied headroom size
9244c79da15c ALSA: hda: Don't release card at firmware loading error
182fa4d72a7c irqchip/mbigen: Free msi_desc on device teardown
daefa51c4353 netfilter: nf_tables: report EOPNOTSUPP on unsupported flags/object type
aea3873fb02c kbuild, btf: Fix dependencies for DEBUG_INFO_BTF
e1e5c219f033 ARM: dts: imx6: Use gpc for FEC interrupt controller to fix wake on LAN.
ed0a5355aa62 ALSA: hda: Honor PM disablement in PM freeze and thaw_noirq ops
d8b667b45d72 scsi: sg: add sg_remove_request in sg_common_write
d979eda8a72b objtool: Fix switch table detection in .text.unlikely
2613535abd3b arm, bpf: Fix offset overflow for BPF_MEM BPF_DW
d4adee8e8f2f arm, bpf: Fix bugs with ALU64 {RSH, ARSH} BPF_K shift by 0
e7f6c25bafa6 xsk: Fix out of boundary write in __xsk_rcv_memcpy
9a9eae78529c watchdog: sp805: fix restart handler
41d097c83343 ext4: use non-movable memory for superblock readahead
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
---
.../linux/linux-yocto-rt_5.4.bb | 6 ++---
.../linux/linux-yocto-tiny_5.4.bb | 8 +++----
meta/recipes-kernel/linux/linux-yocto_5.4.bb | 22 +++++++++----------
3 files changed, 18 insertions(+), 18 deletions(-)
diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb b/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb
index d550bf5371..ddd8587dc9 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb
@@ -11,13 +11,13 @@ python () {
raise bb.parse.SkipRecipe("Set PREFERRED_PROVIDER_virtual/kernel to linux-yocto-rt to enable it")
}
-SRCREV_machine ?= "c7609ad17612bd59c1cadb53faf23be8fd7250ef"
-SRCREV_meta ?= "054d410d1a73e4729f1fe7540db058de69fe8cfe"
+SRCREV_machine ?= "129f86f995aac168e041feeda764097593cace75"
+SRCREV_meta ?= "f405543442e6faae2d96b344ed229c3f37268af5"
SRC_URI = "git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine \
git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-5.4;destsuffix=${KMETA}"
-LINUX_VERSION ?= "5.4.34"
+LINUX_VERSION ?= "5.4.38"
LIC_FILES_CHKSUM = "file://COPYING;md5=bbea815ee2795b2f4230826c0c6b8814"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb b/meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb
index 078a15cec0..c841b1c58e 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb
@@ -6,7 +6,7 @@ KCONFIG_MODE = "--allnoconfig"
require recipes-kernel/linux/linux-yocto.inc
-LINUX_VERSION ?= "5.4.34"
+LINUX_VERSION ?= "5.4.38"
LIC_FILES_CHKSUM = "file://COPYING;md5=bbea815ee2795b2f4230826c0c6b8814"
DEPENDS += "${@bb.utils.contains('ARCH', 'x86', 'elfutils-native', '', d)}"
@@ -15,9 +15,9 @@ DEPENDS += "openssl-native util-linux-native"
KMETA = "kernel-meta"
KCONF_BSP_AUDIT_LEVEL = "2"
-SRCREV_machine_qemuarm ?= "ba0b1e26460cb764005af5758334fc1777760dfd"
-SRCREV_machine ?= "e378a5626133c1f46c7ee4ede3785dbb805dc5ab"
-SRCREV_meta ?= "054d410d1a73e4729f1fe7540db058de69fe8cfe"
+SRCREV_machine_qemuarm ?= "7fe31c186301aef841d44c92a03ba364c13da2f1"
+SRCREV_machine ?= "6cb5b11e832995945db63a27e999f99e5952b199"
+SRCREV_meta ?= "f405543442e6faae2d96b344ed229c3f37268af5"
PV = "${LINUX_VERSION}+git${SRCPV}"
diff --git a/meta/recipes-kernel/linux/linux-yocto_5.4.bb b/meta/recipes-kernel/linux/linux-yocto_5.4.bb
index e225094698..fd8dab1b54 100644
--- a/meta/recipes-kernel/linux/linux-yocto_5.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_5.4.bb
@@ -12,16 +12,16 @@ KBRANCH_qemux86 ?= "v5.4/standard/base"
KBRANCH_qemux86-64 ?= "v5.4/standard/base"
KBRANCH_qemumips64 ?= "v5.4/standard/mti-malta64"
-SRCREV_machine_qemuarm ?= "440e41f2f471ba2bb5e3c801ffc140523bdd59b1"
-SRCREV_machine_qemuarm64 ?= "e378a5626133c1f46c7ee4ede3785dbb805dc5ab"
-SRCREV_machine_qemumips ?= "941c329c8810e946840bd2f4ab983a94651e563f"
-SRCREV_machine_qemuppc ?= "e378a5626133c1f46c7ee4ede3785dbb805dc5ab"
-SRCREV_machine_qemuriscv64 ?= "e378a5626133c1f46c7ee4ede3785dbb805dc5ab"
-SRCREV_machine_qemux86 ?= "e378a5626133c1f46c7ee4ede3785dbb805dc5ab"
-SRCREV_machine_qemux86-64 ?= "e378a5626133c1f46c7ee4ede3785dbb805dc5ab"
-SRCREV_machine_qemumips64 ?= "b73834a11da2d4327cc3cb9f33fa3540f24d56aa"
-SRCREV_machine ?= "e378a5626133c1f46c7ee4ede3785dbb805dc5ab"
-SRCREV_meta ?= "054d410d1a73e4729f1fe7540db058de69fe8cfe"
+SRCREV_machine_qemuarm ?= "32b7ccec6c9e093f1fb21c2849dc099b735f47b3"
+SRCREV_machine_qemuarm64 ?= "6cb5b11e832995945db63a27e999f99e5952b199"
+SRCREV_machine_qemumips ?= "2f15acf8311f6c77ffe0ec5ab7dc4580d5aad5cd"
+SRCREV_machine_qemuppc ?= "6cb5b11e832995945db63a27e999f99e5952b199"
+SRCREV_machine_qemuriscv64 ?= "6cb5b11e832995945db63a27e999f99e5952b199"
+SRCREV_machine_qemux86 ?= "6cb5b11e832995945db63a27e999f99e5952b199"
+SRCREV_machine_qemux86-64 ?= "6cb5b11e832995945db63a27e999f99e5952b199"
+SRCREV_machine_qemumips64 ?= "dbec39f84a447f9d1df6c9ec27e752fd488f7bb4"
+SRCREV_machine ?= "6cb5b11e832995945db63a27e999f99e5952b199"
+SRCREV_meta ?= "f405543442e6faae2d96b344ed229c3f37268af5"
# remap qemuarm to qemuarma15 for the 5.4 kernel
# KMACHINE_qemuarm ?= "qemuarma15"
@@ -30,7 +30,7 @@ SRC_URI = "git://git.yoctoproject.org/linux-yocto.git;name=machine;branch=${KBRA
git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-5.4;destsuffix=${KMETA}"
LIC_FILES_CHKSUM = "file://COPYING;md5=bbea815ee2795b2f4230826c0c6b8814"
-LINUX_VERSION ?= "5.4.34"
+LINUX_VERSION ?= "5.4.38"
DEPENDS += "${@bb.utils.contains('ARCH', 'x86', 'elfutils-native', '', d)}"
DEPENDS += "openssl-native util-linux-native"
--
2.19.1
^ permalink raw reply related [flat|nested] 64+ messages in thread
* [PATCH 5/5] linux-yocto-dev: bump to v5.7-rc
2020-05-03 15:44 [PATCH 0/5] linux-yocto: consolidated pull request Bruce Ashfield
` (3 preceding siblings ...)
2020-05-03 15:44 ` [PATCH 4/5] linux-yocto/5.4: update to v5.4.38 Bruce Ashfield
@ 2020-05-03 15:44 ` Bruce Ashfield
2020-05-04 8:30 ` [PATCH 0/5] linux-yocto: consolidated pull request Richard Purdie
5 siblings, 0 replies; 64+ messages in thread
From: Bruce Ashfield @ 2020-05-03 15:44 UTC (permalink / raw)
To: richard.purdie; +Cc: openembedded-core, steve
From: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
---
meta/recipes-kernel/linux/linux-yocto-dev.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-kernel/linux/linux-yocto-dev.bb b/meta/recipes-kernel/linux/linux-yocto-dev.bb
index 06a9108fab..8a61b22761 100644
--- a/meta/recipes-kernel/linux/linux-yocto-dev.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-dev.bb
@@ -30,7 +30,7 @@ SRC_URI = "git://git.yoctoproject.org/linux-yocto-dev.git;branch=${KBRANCH};name
SRCREV_machine ?= '${@oe.utils.conditional("PREFERRED_PROVIDER_virtual/kernel", "linux-yocto-dev", "${AUTOREV}", "29594404d7fe73cd80eaa4ee8c43dcc53970c60e", d)}'
SRCREV_meta ?= '${@oe.utils.conditional("PREFERRED_PROVIDER_virtual/kernel", "linux-yocto-dev", "${AUTOREV}", "29594404d7fe73cd80eaa4ee8c43dcc53970c60e", d)}'
-LINUX_VERSION ?= "5.6-rc+"
+LINUX_VERSION ?= "5.7-rc+"
LINUX_VERSION_EXTENSION ?= "-yoctodev-${LINUX_KERNEL_TYPE}"
PV = "${LINUX_VERSION}+git${SRCPV}"
--
2.19.1
^ permalink raw reply related [flat|nested] 64+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2020-05-03 15:44 [PATCH 0/5] linux-yocto: consolidated pull request Bruce Ashfield
` (4 preceding siblings ...)
2020-05-03 15:44 ` [PATCH 5/5] linux-yocto-dev: bump to v5.7-rc Bruce Ashfield
@ 2020-05-04 8:30 ` Richard Purdie
2020-05-04 12:56 ` Bruce Ashfield
[not found] ` <160BD489BF65999D.29536@lists.openembedded.org>
5 siblings, 2 replies; 64+ messages in thread
From: Richard Purdie @ 2020-05-04 8:30 UTC (permalink / raw)
To: bruce.ashfield; +Cc: openembedded-core, steve
Hi Bruce,
On Sun, 2020-05-03 at 11:44 -0400, bruce.ashfield@gmail.com wrote:
> From: Bruce Ashfield <bruce.ashfield@gmail.com>
>
> Hi all,
>
> Here are the -stable updates I've collected since m3 of dunfell. I
> ran things through the autobuilder, and no new kernel issues were
> picked up.
>
> The -dev bump is good for master, while all of the 5.4-stable bumps
> are good for both master and dunfell.
I pulled these into master-next and saw reproducibility issues. I
wondered why your test build didn't show it, turns out it also did:
https://autobuilder.yoctoproject.org/typhoon/#/builders/56/builds/1024
2020-05-04 05:18:46,863 - oe-selftest - INFO - ======================================================================
2020-05-04 05:18:46,863 - oe-selftest - INFO - FAIL: reproducible.ReproducibleTests.test_reproducible_builds (subunit.RemotedTestCase)
2020-05-04 05:18:46,863 - oe-selftest - INFO - ----------------------------------------------------------------------
2020-05-04 05:18:46,864 - oe-selftest - INFO - testtools.testresult.real._StringException:
AssertionError: The following deb packages are missing or different: /home/pokybuild/yocto-worker/oe-selftest-centos/build/build-st-36044/reproducibleB/tmp/deploy/deb/./qemux86_64/kernel-module-kheaders-5.4.38-yocto-standard_5.4.38+git0+f405543442_6cb5b11e83-r0_amd64.deb
The following ipk packages are missing or different: /home/pokybuild/yocto-worker/oe-selftest-centos/build/build-st-36044/reproducibleB/tmp/deploy/ipk/./qemux86_64/kernel-module-kheaders-5.4.38-yocto-standard_5.4.38+git0+f405543442_6cb5b11e83-r0_qemux86_64.ipk
master-next was:
https://autobuilder.yoctoproject.org/typhoon/#/builders/80/builds/900
and friends.
Cheers,
Richard
^ permalink raw reply [flat|nested] 64+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2020-05-04 8:30 ` [PATCH 0/5] linux-yocto: consolidated pull request Richard Purdie
@ 2020-05-04 12:56 ` Bruce Ashfield
[not found] ` <160BD489BF65999D.29536@lists.openembedded.org>
1 sibling, 0 replies; 64+ messages in thread
From: Bruce Ashfield @ 2020-05-04 12:56 UTC (permalink / raw)
To: Richard Purdie; +Cc: Patches and discussions about the oe-core layer, steve
On Mon, May 4, 2020 at 4:31 AM Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
>
> Hi Bruce,
>
> On Sun, 2020-05-03 at 11:44 -0400, bruce.ashfield@gmail.com wrote:
> > From: Bruce Ashfield <bruce.ashfield@gmail.com>
> >
> > Hi all,
> >
> > Here are the -stable updates I've collected since m3 of dunfell. I
> > ran things through the autobuilder, and no new kernel issues were
> > picked up.
> >
> > The -dev bump is good for master, while all of the 5.4-stable bumps
> > are good for both master and dunfell.
>
> I pulled these into master-next and saw reproducibility issues. I
> wondered why your test build didn't show it, turns out it also did:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/56/builds/1024
>
> 2020-05-04 05:18:46,863 - oe-selftest - INFO - ======================================================================
> 2020-05-04 05:18:46,863 - oe-selftest - INFO - FAIL: reproducible.ReproducibleTests.test_reproducible_builds (subunit.RemotedTestCase)
> 2020-05-04 05:18:46,863 - oe-selftest - INFO - ----------------------------------------------------------------------
> 2020-05-04 05:18:46,864 - oe-selftest - INFO - testtools.testresult.real._StringException:
>
> AssertionError: The following deb packages are missing or different: /home/pokybuild/yocto-worker/oe-selftest-centos/build/build-st-36044/reproducibleB/tmp/deploy/deb/./qemux86_64/kernel-module-kheaders-5.4.38-yocto-standard_5.4.38+git0+f405543442_6cb5b11e83-r0_amd64.deb
> The following ipk packages are missing or different: /home/pokybuild/yocto-worker/oe-selftest-centos/build/build-st-36044/reproducibleB/tmp/deploy/ipk/./qemux86_64/kernel-module-kheaders-5.4.38-yocto-standard_5.4.38+git0+f405543442_6cb5b11e83-r0_qemux86_64.ipk
>
I don't see any changes in the kernels that would have triggered it,
but they never are obvious.
I unfortunately have no idea how to run reproducibility tests on the
kernels locally and my build server at home is brutally underpowered
for more than one core-image build per arch a day (hence the
autobuilder runs).
Is there a cut and paste se of instructions about the tests that I
could follow ?
Bruce
> master-next was:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/80/builds/900
>
> and friends.
>
> Cheers,
>
> Richard
>
--
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
^ permalink raw reply [flat|nested] 64+ messages in thread
* Re: [OE-core] [PATCH 0/5] linux-yocto: consolidated pull request
[not found] ` <160BD489BF65999D.29536@lists.openembedded.org>
@ 2020-05-04 13:06 ` Bruce Ashfield
2020-05-04 13:24 ` Richard Purdie
0 siblings, 1 reply; 64+ messages in thread
From: Bruce Ashfield @ 2020-05-04 13:06 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer; +Cc: Richard Purdie, steve
On Mon, May 4, 2020 at 8:56 AM Bruce Ashfield via
lists.openembedded.org
<bruce.ashfield=gmail.com@lists.openembedded.org> wrote:
>
> On Mon, May 4, 2020 at 4:31 AM Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> >
> > Hi Bruce,
> >
> > On Sun, 2020-05-03 at 11:44 -0400, bruce.ashfield@gmail.com wrote:
> > > From: Bruce Ashfield <bruce.ashfield@gmail.com>
> > >
> > > Hi all,
> > >
> > > Here are the -stable updates I've collected since m3 of dunfell. I
> > > ran things through the autobuilder, and no new kernel issues were
> > > picked up.
> > >
> > > The -dev bump is good for master, while all of the 5.4-stable bumps
> > > are good for both master and dunfell.
> >
> > I pulled these into master-next and saw reproducibility issues. I
> > wondered why your test build didn't show it, turns out it also did:
> >
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/56/builds/1024
> >
> > 2020-05-04 05:18:46,863 - oe-selftest - INFO - ======================================================================
> > 2020-05-04 05:18:46,863 - oe-selftest - INFO - FAIL: reproducible.ReproducibleTests.test_reproducible_builds (subunit.RemotedTestCase)
> > 2020-05-04 05:18:46,863 - oe-selftest - INFO - ----------------------------------------------------------------------
> > 2020-05-04 05:18:46,864 - oe-selftest - INFO - testtools.testresult.real._StringException:
> >
> > AssertionError: The following deb packages are missing or different: /home/pokybuild/yocto-worker/oe-selftest-centos/build/build-st-36044/reproducibleB/tmp/deploy/deb/./qemux86_64/kernel-module-kheaders-5.4.38-yocto-standard_5.4.38+git0+f405543442_6cb5b11e83-r0_amd64.deb
> > The following ipk packages are missing or different: /home/pokybuild/yocto-worker/oe-selftest-centos/build/build-st-36044/reproducibleB/tmp/deploy/ipk/./qemux86_64/kernel-module-kheaders-5.4.38-yocto-standard_5.4.38+git0+f405543442_6cb5b11e83-r0_qemux86_64.ipk
> >
>
> I don't see any changes in the kernels that would have triggered it,
> but they never are obvious.
I am working on some kernel reproducibility changes that were
discussed about three weeks ago.
Is the default for reproducible builds in master-next different from
what it was before dunfell was releases ? If so, that might explain
why I'm not seeing a change that would have triggered it (i.e. this is
unrelated to my -stable changes).
Like I was mentioning before, if there's a document or pastebin of
steps I can follow, I can run the tests against my pending changes and
finish them for master. They of course would not necessarily be
suitable for dunfell.
Bruce
>
> I unfortunately have no idea how to run reproducibility tests on the
> kernels locally and my build server at home is brutally underpowered
> for more than one core-image build per arch a day (hence the
> autobuilder runs).
>
> Is there a cut and paste se of instructions about the tests that I
> could follow ?
>
> Bruce
>
> > master-next was:
> >
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/80/builds/900
> >
> > and friends.
> >
> > Cheers,
> >
> > Richard
> >
>
>
> --
> - Thou shalt not follow the NULL pointer, for chaos and madness await
> thee at its end
> - "Use the force Harry" - Gandalf, Star Trek II
>
--
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
^ permalink raw reply [flat|nested] 64+ messages in thread
* Re: [OE-core] [PATCH 0/5] linux-yocto: consolidated pull request
2020-05-04 13:06 ` [OE-core] " Bruce Ashfield
@ 2020-05-04 13:24 ` Richard Purdie
2020-05-04 13:34 ` Bruce Ashfield
0 siblings, 1 reply; 64+ messages in thread
From: Richard Purdie @ 2020-05-04 13:24 UTC (permalink / raw)
To: Bruce Ashfield, Patches and discussions about the oe-core layer; +Cc: steve
On Mon, 2020-05-04 at 09:06 -0400, Bruce Ashfield wrote:
> On Mon, May 4, 2020 at 8:56 AM Bruce Ashfield via
> lists.openembedded.org
> <bruce.ashfield=gmail.com@lists.openembedded.org> wrote:
> > On Mon, May 4, 2020 at 4:31 AM Richard Purdie
> > <richard.purdie@linuxfoundation.org> wrote:
> > > Hi Bruce,
> > >
> > > On Sun, 2020-05-03 at 11:44 -0400, bruce.ashfield@gmail.com wrote:
> > > > From: Bruce Ashfield <bruce.ashfield@gmail.com>
> > > >
> > > > Hi all,
> > > >
> > > > Here are the -stable updates I've collected since m3 of dunfell. I
> > > > ran things through the autobuilder, and no new kernel issues were
> > > > picked up.
> > > >
> > > > The -dev bump is good for master, while all of the 5.4-stable bumps
> > > > are good for both master and dunfell.
> > >
> > > I pulled these into master-next and saw reproducibility issues. I
> > > wondered why your test build didn't show it, turns out it also did:
> > >
> > > https://autobuilder.yoctoproject.org/typhoon/#/builders/56/builds/1024
> > >
> > > 2020-05-04 05:18:46,863 - oe-selftest - INFO - ======================================================================
> > > 2020-05-04 05:18:46,863 - oe-selftest - INFO - FAIL: reproducible.ReproducibleTests.test_reproducible_builds (subunit.RemotedTestCase)
> > > 2020-05-04 05:18:46,863 - oe-selftest - INFO - ----------------------------------------------------------------------
> > > 2020-05-04 05:18:46,864 - oe-selftest - INFO - testtools.testresult.real._StringException:
> > >
> > > AssertionError: The following deb packages are missing or different: /home/pokybuild/yocto-worker/oe-selftest-centos/build/build-st-36044/reproducibleB/tmp/deploy/deb/./qemux86_64/kernel-module-kheaders-5.4.38-yocto-standard_5.4.38+git0+f405543442_6cb5b11e83-r0_amd64.deb
> > > The following ipk packages are missing or different: /home/pokybuild/yocto-worker/oe-selftest-centos/build/build-st-36044/reproducibleB/tmp/deploy/ipk/./qemux86_64/kernel-module-kheaders-5.4.38-yocto-standard_5.4.38+git0+f405543442_6cb5b11e83-r0_qemux86_64.ipk
> > >
> >
> > I don't see any changes in the kernels that would have triggered it,
> > but they never are obvious.
>
> I am working on some kernel reproducibility changes that were
> discussed about three weeks ago.
>
> Is the default for reproducible builds in master-next different from
> what it was before dunfell was releases ? If so, that might explain
> why I'm not seeing a change that would have triggered it (i.e. this is
> unrelated to my -stable changes).
There are no reproducibility changes between master-next and dunfell.
> Like I was mentioning before, if there's a document or pastebin of
> steps I can follow, I can run the tests against my pending changes and
> finish them for master. They of course would not necessarily be
> suitable for dunfell.
The good news is the autobuilder has some debugging built in for this
kind of problem. You can see the diffoscope output here:
https://autobuilder.yocto.io/pub/repro-fail/oe-reproducible-20200504-vhr0o_t9/packages/diff-html/
which tells us its kheaders.ko in .rodata by the looks of it. Some
changes are cause, some are effect, e.g. the build ID is different as
the sections are different so that isn't the issue but an effect of it.
It looks like diffoscope doesn't know how to decode the .rodata which
could be compressed?
The raw data is also there (the packages that differ), e.g.:
https://autobuilder.yocto.io/pub/repro-fail/oe-reproducible-20200504-vhr0o_t9/packages/reproducibleA/tmp/deploy/deb/qemux86_64/kernel-module-kheaders-5.4.38-yocto-standard_5.4.38%2Bgit0%2Bf405543442_6cb5b11e83-r0_amd64.deb
https://autobuilder.yocto.io/pub/repro-fail/oe-reproducible-20200504-vhr0o_t9/packages/reproducibleB/tmp/deploy/deb/qemux86_64/kernel-module-kheaders-5.4.38-yocto-standard_5.4.38%2Bgit0%2Bf405543442_6cb5b11e83-r0_amd64.debe
which would allow you to look further at them by hand.
You can manually run this test locally with:
oe-selftest -r reproducible.ReproducibleTests.test_reproducible_builds
but it will take a while to run as it has to run two builds and compare
them and only uses sstate for one of them. To make it faster since you
know where the issue is, edit
meta/lib/oeqa/selftest/cases/reproducible.py to change images (core-
image-sato, core-image-minimal and friends to simply "virtual/kernel".
Cheers,
Richard
^ permalink raw reply [flat|nested] 64+ messages in thread
* Re: [OE-core] [PATCH 0/5] linux-yocto: consolidated pull request
2020-05-04 13:24 ` Richard Purdie
@ 2020-05-04 13:34 ` Bruce Ashfield
2020-05-07 18:14 ` Steve Sakoman
0 siblings, 1 reply; 64+ messages in thread
From: Bruce Ashfield @ 2020-05-04 13:34 UTC (permalink / raw)
To: Richard Purdie; +Cc: Patches and discussions about the oe-core layer, steve
On Mon, May 4, 2020 at 9:24 AM Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
>
> On Mon, 2020-05-04 at 09:06 -0400, Bruce Ashfield wrote:
> > On Mon, May 4, 2020 at 8:56 AM Bruce Ashfield via
> > lists.openembedded.org
> > <bruce.ashfield=gmail.com@lists.openembedded.org> wrote:
> > > On Mon, May 4, 2020 at 4:31 AM Richard Purdie
> > > <richard.purdie@linuxfoundation.org> wrote:
> > > > Hi Bruce,
> > > >
> > > > On Sun, 2020-05-03 at 11:44 -0400, bruce.ashfield@gmail.com wrote:
> > > > > From: Bruce Ashfield <bruce.ashfield@gmail.com>
> > > > >
> > > > > Hi all,
> > > > >
> > > > > Here are the -stable updates I've collected since m3 of dunfell. I
> > > > > ran things through the autobuilder, and no new kernel issues were
> > > > > picked up.
> > > > >
> > > > > The -dev bump is good for master, while all of the 5.4-stable bumps
> > > > > are good for both master and dunfell.
> > > >
> > > > I pulled these into master-next and saw reproducibility issues. I
> > > > wondered why your test build didn't show it, turns out it also did:
> > > >
> > > > https://autobuilder.yoctoproject.org/typhoon/#/builders/56/builds/1024
> > > >
> > > > 2020-05-04 05:18:46,863 - oe-selftest - INFO - ======================================================================
> > > > 2020-05-04 05:18:46,863 - oe-selftest - INFO - FAIL: reproducible.ReproducibleTests.test_reproducible_builds (subunit.RemotedTestCase)
> > > > 2020-05-04 05:18:46,863 - oe-selftest - INFO - ----------------------------------------------------------------------
> > > > 2020-05-04 05:18:46,864 - oe-selftest - INFO - testtools.testresult.real._StringException:
> > > >
> > > > AssertionError: The following deb packages are missing or different: /home/pokybuild/yocto-worker/oe-selftest-centos/build/build-st-36044/reproducibleB/tmp/deploy/deb/./qemux86_64/kernel-module-kheaders-5.4.38-yocto-standard_5.4.38+git0+f405543442_6cb5b11e83-r0_amd64.deb
> > > > The following ipk packages are missing or different: /home/pokybuild/yocto-worker/oe-selftest-centos/build/build-st-36044/reproducibleB/tmp/deploy/ipk/./qemux86_64/kernel-module-kheaders-5.4.38-yocto-standard_5.4.38+git0+f405543442_6cb5b11e83-r0_qemux86_64.ipk
> > > >
> > >
> > > I don't see any changes in the kernels that would have triggered it,
> > > but they never are obvious.
> >
> > I am working on some kernel reproducibility changes that were
> > discussed about three weeks ago.
> >
> > Is the default for reproducible builds in master-next different from
> > what it was before dunfell was releases ? If so, that might explain
> > why I'm not seeing a change that would have triggered it (i.e. this is
> > unrelated to my -stable changes).
>
> There are no reproducibility changes between master-next and dunfell.
interesting. I'll take a closer look at the changes again and see what
might pop up as a culprit.
>
> > Like I was mentioning before, if there's a document or pastebin of
> > steps I can follow, I can run the tests against my pending changes and
> > finish them for master. They of course would not necessarily be
> > suitable for dunfell.
>
> The good news is the autobuilder has some debugging built in for this
> kind of problem. You can see the diffoscope output here:
>
> https://autobuilder.yocto.io/pub/repro-fail/oe-reproducible-20200504-vhr0o_t9/packages/diff-html/
>
> which tells us its kheaders.ko in .rodata by the looks of it. Some
> changes are cause, some are effect, e.g. the build ID is different as
> the sections are different so that isn't the issue but an effect of it.
> It looks like diffoscope doesn't know how to decode the .rodata which
> could be compressed?
>
> The raw data is also there (the packages that differ), e.g.:
>
> https://autobuilder.yocto.io/pub/repro-fail/oe-reproducible-20200504-vhr0o_t9/packages/reproducibleA/tmp/deploy/deb/qemux86_64/kernel-module-kheaders-5.4.38-yocto-standard_5.4.38%2Bgit0%2Bf405543442_6cb5b11e83-r0_amd64.deb
>
> https://autobuilder.yocto.io/pub/repro-fail/oe-reproducible-20200504-vhr0o_t9/packages/reproducibleB/tmp/deploy/deb/qemux86_64/kernel-module-kheaders-5.4.38-yocto-standard_5.4.38%2Bgit0%2Bf405543442_6cb5b11e83-r0_amd64.debe
>
cool. That's definitely useful, I'll have a look.
At the same time, I'll try and clean up the documented kernel
reproducible changes and trigger another run to see if they help.
> which would allow you to look further at them by hand.
>
> You can manually run this test locally with:
>
> oe-selftest -r reproducible.ReproducibleTests.test_reproducible_builds
>
> but it will take a while to run as it has to run two builds and compare
> them and only uses sstate for one of them. To make it faster since you
> know where the issue is, edit
> meta/lib/oeqa/selftest/cases/reproducible.py to change images (core-
> image-sato, core-image-minimal and friends to simply "virtual/kernel".
I'll do that cut down of the tests and see if I can trigger it here ..
With those full builds, I'd be at about an 8 hour cycle to see the
results!
Bruce
>
> Cheers,
>
> Richard
>
>
>
>
>
>
>
>
--
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
^ permalink raw reply [flat|nested] 64+ messages in thread
* Re: [OE-core] [PATCH 0/5] linux-yocto: consolidated pull request
2020-05-04 13:34 ` Bruce Ashfield
@ 2020-05-07 18:14 ` Steve Sakoman
2020-05-07 19:18 ` Bruce Ashfield
0 siblings, 1 reply; 64+ messages in thread
From: Steve Sakoman @ 2020-05-07 18:14 UTC (permalink / raw)
To: Bruce Ashfield
Cc: Richard Purdie, Patches and discussions about the oe-core layer
From the discussion to this point it seems that these patches aren't
quite ready for dunfell. Let me know if/when that changes, or if I'm
mistaken in that assumption!
Steve
On Mon, May 4, 2020 at 3:34 AM Bruce Ashfield <bruce.ashfield@gmail.com> wrote:
>
> On Mon, May 4, 2020 at 9:24 AM Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> >
> > On Mon, 2020-05-04 at 09:06 -0400, Bruce Ashfield wrote:
> > > On Mon, May 4, 2020 at 8:56 AM Bruce Ashfield via
> > > lists.openembedded.org
> > > <bruce.ashfield=gmail.com@lists.openembedded.org> wrote:
> > > > On Mon, May 4, 2020 at 4:31 AM Richard Purdie
> > > > <richard.purdie@linuxfoundation.org> wrote:
> > > > > Hi Bruce,
> > > > >
> > > > > On Sun, 2020-05-03 at 11:44 -0400, bruce.ashfield@gmail.com wrote:
> > > > > > From: Bruce Ashfield <bruce.ashfield@gmail.com>
> > > > > >
> > > > > > Hi all,
> > > > > >
> > > > > > Here are the -stable updates I've collected since m3 of dunfell. I
> > > > > > ran things through the autobuilder, and no new kernel issues were
> > > > > > picked up.
> > > > > >
> > > > > > The -dev bump is good for master, while all of the 5.4-stable bumps
> > > > > > are good for both master and dunfell.
> > > > >
> > > > > I pulled these into master-next and saw reproducibility issues. I
> > > > > wondered why your test build didn't show it, turns out it also did:
> > > > >
> > > > > https://autobuilder.yoctoproject.org/typhoon/#/builders/56/builds/1024
> > > > >
> > > > > 2020-05-04 05:18:46,863 - oe-selftest - INFO - ======================================================================
> > > > > 2020-05-04 05:18:46,863 - oe-selftest - INFO - FAIL: reproducible.ReproducibleTests.test_reproducible_builds (subunit.RemotedTestCase)
> > > > > 2020-05-04 05:18:46,863 - oe-selftest - INFO - ----------------------------------------------------------------------
> > > > > 2020-05-04 05:18:46,864 - oe-selftest - INFO - testtools.testresult.real._StringException:
> > > > >
> > > > > AssertionError: The following deb packages are missing or different: /home/pokybuild/yocto-worker/oe-selftest-centos/build/build-st-36044/reproducibleB/tmp/deploy/deb/./qemux86_64/kernel-module-kheaders-5.4.38-yocto-standard_5.4.38+git0+f405543442_6cb5b11e83-r0_amd64.deb
> > > > > The following ipk packages are missing or different: /home/pokybuild/yocto-worker/oe-selftest-centos/build/build-st-36044/reproducibleB/tmp/deploy/ipk/./qemux86_64/kernel-module-kheaders-5.4.38-yocto-standard_5.4.38+git0+f405543442_6cb5b11e83-r0_qemux86_64.ipk
> > > > >
> > > >
> > > > I don't see any changes in the kernels that would have triggered it,
> > > > but they never are obvious.
> > >
> > > I am working on some kernel reproducibility changes that were
> > > discussed about three weeks ago.
> > >
> > > Is the default for reproducible builds in master-next different from
> > > what it was before dunfell was releases ? If so, that might explain
> > > why I'm not seeing a change that would have triggered it (i.e. this is
> > > unrelated to my -stable changes).
> >
> > There are no reproducibility changes between master-next and dunfell.
>
> interesting. I'll take a closer look at the changes again and see what
> might pop up as a culprit.
>
> >
> > > Like I was mentioning before, if there's a document or pastebin of
> > > steps I can follow, I can run the tests against my pending changes and
> > > finish them for master. They of course would not necessarily be
> > > suitable for dunfell.
> >
> > The good news is the autobuilder has some debugging built in for this
> > kind of problem. You can see the diffoscope output here:
> >
> > https://autobuilder.yocto.io/pub/repro-fail/oe-reproducible-20200504-vhr0o_t9/packages/diff-html/
> >
> > which tells us its kheaders.ko in .rodata by the looks of it. Some
> > changes are cause, some are effect, e.g. the build ID is different as
> > the sections are different so that isn't the issue but an effect of it.
> > It looks like diffoscope doesn't know how to decode the .rodata which
> > could be compressed?
> >
> > The raw data is also there (the packages that differ), e.g.:
> >
> > https://autobuilder.yocto.io/pub/repro-fail/oe-reproducible-20200504-vhr0o_t9/packages/reproducibleA/tmp/deploy/deb/qemux86_64/kernel-module-kheaders-5.4.38-yocto-standard_5.4.38%2Bgit0%2Bf405543442_6cb5b11e83-r0_amd64.deb
> >
> > https://autobuilder.yocto.io/pub/repro-fail/oe-reproducible-20200504-vhr0o_t9/packages/reproducibleB/tmp/deploy/deb/qemux86_64/kernel-module-kheaders-5.4.38-yocto-standard_5.4.38%2Bgit0%2Bf405543442_6cb5b11e83-r0_amd64.debe
> >
>
> cool. That's definitely useful, I'll have a look.
>
> At the same time, I'll try and clean up the documented kernel
> reproducible changes and trigger another run to see if they help.
>
> > which would allow you to look further at them by hand.
> >
> > You can manually run this test locally with:
> >
> > oe-selftest -r reproducible.ReproducibleTests.test_reproducible_builds
> >
> > but it will take a while to run as it has to run two builds and compare
> > them and only uses sstate for one of them. To make it faster since you
> > know where the issue is, edit
> > meta/lib/oeqa/selftest/cases/reproducible.py to change images (core-
> > image-sato, core-image-minimal and friends to simply "virtual/kernel".
>
> I'll do that cut down of the tests and see if I can trigger it here ..
> With those full builds, I'd be at about an 8 hour cycle to see the
> results!
>
> Bruce
>
> >
> > Cheers,
> >
> > Richard
> >
> >
> >
> >
> >
> >
> >
> >
>
>
> --
> - Thou shalt not follow the NULL pointer, for chaos and madness await
> thee at its end
> - "Use the force Harry" - Gandalf, Star Trek II
>
^ permalink raw reply [flat|nested] 64+ messages in thread
* Re: [OE-core] [PATCH 0/5] linux-yocto: consolidated pull request
2020-05-07 18:14 ` Steve Sakoman
@ 2020-05-07 19:18 ` Bruce Ashfield
0 siblings, 0 replies; 64+ messages in thread
From: Bruce Ashfield @ 2020-05-07 19:18 UTC (permalink / raw)
To: Steve Sakoman
Cc: Richard Purdie, Patches and discussions about the oe-core layer
On Thu, May 7, 2020 at 2:15 PM Steve Sakoman <sakoman@gmail.com> wrote:
>
> From the discussion to this point it seems that these patches aren't
> quite ready for dunfell. Let me know if/when that changes, or if I'm
> mistaken in that assumption!
Richard merged 3 of the 4 kernel updates (up to v5.4.34), so they are
ok for dunfell.
There's just a reproducible issue that we have to look into more
(there's no runtime issues with any of them).
Bruce
>
> Steve
>
> On Mon, May 4, 2020 at 3:34 AM Bruce Ashfield <bruce.ashfield@gmail.com> wrote:
> >
> > On Mon, May 4, 2020 at 9:24 AM Richard Purdie
> > <richard.purdie@linuxfoundation.org> wrote:
> > >
> > > On Mon, 2020-05-04 at 09:06 -0400, Bruce Ashfield wrote:
> > > > On Mon, May 4, 2020 at 8:56 AM Bruce Ashfield via
> > > > lists.openembedded.org
> > > > <bruce.ashfield=gmail.com@lists.openembedded.org> wrote:
> > > > > On Mon, May 4, 2020 at 4:31 AM Richard Purdie
> > > > > <richard.purdie@linuxfoundation.org> wrote:
> > > > > > Hi Bruce,
> > > > > >
> > > > > > On Sun, 2020-05-03 at 11:44 -0400, bruce.ashfield@gmail.com wrote:
> > > > > > > From: Bruce Ashfield <bruce.ashfield@gmail.com>
> > > > > > >
> > > > > > > Hi all,
> > > > > > >
> > > > > > > Here are the -stable updates I've collected since m3 of dunfell. I
> > > > > > > ran things through the autobuilder, and no new kernel issues were
> > > > > > > picked up.
> > > > > > >
> > > > > > > The -dev bump is good for master, while all of the 5.4-stable bumps
> > > > > > > are good for both master and dunfell.
> > > > > >
> > > > > > I pulled these into master-next and saw reproducibility issues. I
> > > > > > wondered why your test build didn't show it, turns out it also did:
> > > > > >
> > > > > > https://autobuilder.yoctoproject.org/typhoon/#/builders/56/builds/1024
> > > > > >
> > > > > > 2020-05-04 05:18:46,863 - oe-selftest - INFO - ======================================================================
> > > > > > 2020-05-04 05:18:46,863 - oe-selftest - INFO - FAIL: reproducible.ReproducibleTests.test_reproducible_builds (subunit.RemotedTestCase)
> > > > > > 2020-05-04 05:18:46,863 - oe-selftest - INFO - ----------------------------------------------------------------------
> > > > > > 2020-05-04 05:18:46,864 - oe-selftest - INFO - testtools.testresult.real._StringException:
> > > > > >
> > > > > > AssertionError: The following deb packages are missing or different: /home/pokybuild/yocto-worker/oe-selftest-centos/build/build-st-36044/reproducibleB/tmp/deploy/deb/./qemux86_64/kernel-module-kheaders-5.4.38-yocto-standard_5.4.38+git0+f405543442_6cb5b11e83-r0_amd64.deb
> > > > > > The following ipk packages are missing or different: /home/pokybuild/yocto-worker/oe-selftest-centos/build/build-st-36044/reproducibleB/tmp/deploy/ipk/./qemux86_64/kernel-module-kheaders-5.4.38-yocto-standard_5.4.38+git0+f405543442_6cb5b11e83-r0_qemux86_64.ipk
> > > > > >
> > > > >
> > > > > I don't see any changes in the kernels that would have triggered it,
> > > > > but they never are obvious.
> > > >
> > > > I am working on some kernel reproducibility changes that were
> > > > discussed about three weeks ago.
> > > >
> > > > Is the default for reproducible builds in master-next different from
> > > > what it was before dunfell was releases ? If so, that might explain
> > > > why I'm not seeing a change that would have triggered it (i.e. this is
> > > > unrelated to my -stable changes).
> > >
> > > There are no reproducibility changes between master-next and dunfell.
> >
> > interesting. I'll take a closer look at the changes again and see what
> > might pop up as a culprit.
> >
> > >
> > > > Like I was mentioning before, if there's a document or pastebin of
> > > > steps I can follow, I can run the tests against my pending changes and
> > > > finish them for master. They of course would not necessarily be
> > > > suitable for dunfell.
> > >
> > > The good news is the autobuilder has some debugging built in for this
> > > kind of problem. You can see the diffoscope output here:
> > >
> > > https://autobuilder.yocto.io/pub/repro-fail/oe-reproducible-20200504-vhr0o_t9/packages/diff-html/
> > >
> > > which tells us its kheaders.ko in .rodata by the looks of it. Some
> > > changes are cause, some are effect, e.g. the build ID is different as
> > > the sections are different so that isn't the issue but an effect of it.
> > > It looks like diffoscope doesn't know how to decode the .rodata which
> > > could be compressed?
> > >
> > > The raw data is also there (the packages that differ), e.g.:
> > >
> > > https://autobuilder.yocto.io/pub/repro-fail/oe-reproducible-20200504-vhr0o_t9/packages/reproducibleA/tmp/deploy/deb/qemux86_64/kernel-module-kheaders-5.4.38-yocto-standard_5.4.38%2Bgit0%2Bf405543442_6cb5b11e83-r0_amd64.deb
> > >
> > > https://autobuilder.yocto.io/pub/repro-fail/oe-reproducible-20200504-vhr0o_t9/packages/reproducibleB/tmp/deploy/deb/qemux86_64/kernel-module-kheaders-5.4.38-yocto-standard_5.4.38%2Bgit0%2Bf405543442_6cb5b11e83-r0_amd64.debe
> > >
> >
> > cool. That's definitely useful, I'll have a look.
> >
> > At the same time, I'll try and clean up the documented kernel
> > reproducible changes and trigger another run to see if they help.
> >
> > > which would allow you to look further at them by hand.
> > >
> > > You can manually run this test locally with:
> > >
> > > oe-selftest -r reproducible.ReproducibleTests.test_reproducible_builds
> > >
> > > but it will take a while to run as it has to run two builds and compare
> > > them and only uses sstate for one of them. To make it faster since you
> > > know where the issue is, edit
> > > meta/lib/oeqa/selftest/cases/reproducible.py to change images (core-
> > > image-sato, core-image-minimal and friends to simply "virtual/kernel".
> >
> > I'll do that cut down of the tests and see if I can trigger it here ..
> > With those full builds, I'd be at about an 8 hour cycle to see the
> > results!
> >
> > Bruce
> >
> > >
> > > Cheers,
> > >
> > > Richard
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
> >
> > --
> > - Thou shalt not follow the NULL pointer, for chaos and madness await
> > thee at its end
> > - "Use the force Harry" - Gandalf, Star Trek II
> >
--
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
^ permalink raw reply [flat|nested] 64+ messages in thread
* [PATCH 0/5] linux-yocto: consolidated pull request
@ 2023-02-01 16:28 bruce.ashfield
0 siblings, 0 replies; 64+ messages in thread
From: bruce.ashfield @ 2023-02-01 16:28 UTC (permalink / raw)
To: richard.purdie; +Cc: openembedded-core
From: Bruce Ashfield <bruce.ashfield@gmail.com>
Richard,
Here's the latest round of configuration and -stable udpates that
I've collected.
Nothing major, but hopefully the virtio patches will help some of
the AB issues.
Bruce
The following changes since commit da95831d91b1265ecaee5bbfaeb1caaa2c290838:
scons: Pass MAXLINELENGTH to scons invocation (2023-01-31 17:11:07 +0000)
are available in the Git repository at:
https://git.yoctoproject.org/poky-contrib zedd/kernel
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Bruce Ashfield (5):
linux-yocto/6.1: update to v6.1.7
linux-yocto/5.15: update to v5.15.89
linux-yocto/6.1: cfg: remove depreciated configs
linux-yocto/6.1: update to v6.1.9
linux-yocto/5.15: update to v5.15.91
.../linux/linux-yocto-rt_5.15.bb | 6 ++---
.../linux/linux-yocto-rt_6.1.bb | 6 ++---
.../linux/linux-yocto-tiny_5.15.bb | 6 ++---
.../linux/linux-yocto-tiny_6.1.bb | 6 ++---
meta/recipes-kernel/linux/linux-yocto_5.15.bb | 26 +++++++++----------
meta/recipes-kernel/linux/linux-yocto_6.1.bb | 26 +++++++++----------
6 files changed, 38 insertions(+), 38 deletions(-)
--
2.34.1
^ permalink raw reply [flat|nested] 64+ messages in thread
* [PATCH 0/5] linux-yocto: consolidated pull request
@ 2020-11-19 19:17 Bruce Ashfield
0 siblings, 0 replies; 64+ messages in thread
From: Bruce Ashfield @ 2020-11-19 19:17 UTC (permalink / raw)
To: richard.purdie; +Cc: openembedded-core
From: Bruce Ashfield <bruce.ashfield@gmail.com>
Richard,
Here's my next set of collected changes for linux-yocto. I built and booted the
5.4 -stable bump .. and obviously it looks good.
I've also grabbed a pending devsrc change, that looks good to me.
Finally, I have a fix Khem sent for perf builds. I kept 5.4 and 5.8 separate
for that fix, so Steve can pick them up for Dunfell as appropriate.
Bruce
The following changes since commit d8f47a68a92802fc47f297de05a0f2817963a7ee:
kernel: relocate copy of module.lds to module compilation task (2020-11-18 13:59:27 +0000)
are available in the Git repository at:
git://git.yoctoproject.org/poky-contrib zedd/kernel
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Bruce Ashfield (4):
linux-yocto/5.4: perf: Alias SYS_futex with SYS_futex_time64 on 32-bit
arches with 64bit time_t
linux-yocto/5.8: perf: Alias SYS_futex with SYS_futex_time64 on 32-bit
arches with 64bit time_t
linux-yocto/5.8: ext4/tipc warning fixups
linux-yocto/5.4: update to v5.4.78
INC@Cisco) (1):
kernel-devsrc: improve reproducibility for arm64
meta/recipes-kernel/linux/kernel-devsrc.bb | 4 ++++
.../linux/linux-yocto-rt_5.4.bb | 6 ++---
.../linux/linux-yocto-rt_5.8.bb | 2 +-
.../linux/linux-yocto-tiny_5.4.bb | 8 +++----
.../linux/linux-yocto-tiny_5.8.bb | 4 ++--
meta/recipes-kernel/linux/linux-yocto_5.4.bb | 22 +++++++++----------
meta/recipes-kernel/linux/linux-yocto_5.8.bb | 18 +++++++--------
7 files changed, 34 insertions(+), 30 deletions(-)
--
2.19.1
^ permalink raw reply [flat|nested] 64+ messages in thread
* [PATCH 0/5] linux-yocto: consolidated pull request
@ 2020-05-29 1:29 Bruce Ashfield
0 siblings, 0 replies; 64+ messages in thread
From: Bruce Ashfield @ 2020-05-29 1:29 UTC (permalink / raw)
To: richard.purdie; +Cc: openembedded-core
From: Bruce Ashfield <bruce.ashfield@gmail.com>
Hi Richard,
As discussed earlier, this is the pull request which contains a temporary
revert of the CONFIG_IKHEADERS config change that was causing the
periodic issues.
I added a kernel feature that can be used to enable the configuration from
a recipe, that way I won't leave anyone broken while I continue to debug,
since this still is a problem for anyone that is doing reproducible builds
and wants ikheaders.
This went through AB quick and came back green.
Bruce
The following changes since commit 392ba004f42be2fd9dcf121d3dfa5b414ff83f93:
ref-manual: add PACKAGE_ADD_METADATA documentation (2020-05-27 11:05:04 +0100)
are available in the Git repository at:
git://git.yoctoproject.org/poky-contrib zedd/kernel
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Bruce Ashfield (5):
linux-yocto/5.4: update to v5.4.42
linux-yocto-rt/5.4: update to rt24
linux-yocto/5.4: temporarily revert IKHEADERS in standard kernels
linux-yocto: gather reproducibility configs into a fragment
linux-yocto/5.4: update to v5.4.43
.../linux/linux-yocto-rt_5.4.bb | 6 ++---
.../linux/linux-yocto-tiny_5.4.bb | 8 +++----
meta/recipes-kernel/linux/linux-yocto_5.4.bb | 22 +++++++++----------
3 files changed, 18 insertions(+), 18 deletions(-)
--
2.19.1
^ permalink raw reply [flat|nested] 64+ messages in thread
* [PATCH 0/5] linux-yocto: consolidated pull request
@ 2020-03-24 23:04 Bruce Ashfield
0 siblings, 0 replies; 64+ messages in thread
From: Bruce Ashfield @ 2020-03-24 23:04 UTC (permalink / raw)
To: richard.purdie; +Cc: openembedded-core
From: Bruce Ashfield <bruce.ashfield@gmail.com>
Hi all,
Here's the queued bug fixes for linux-yocto. It has khem's identified fixes
for the kernel selftest issues with the latest -stable udpates, as well as
some BSP fixes and config changes.
I ran this through the AB and everything came back green.
I've done this in multiple commits, so we'll have granularity to look
into individual fixes if we have trouble.
Cheers,
Bruce
The following changes since commit d5db9d12642e03a1d5cca5f1520dad5fcc9524c3:
archiver.py: fix typo of "ARCHIVER_MIRROR_EXCLUDE" in comment (2020-03-24 16:39:40 +0000)
are available in the Git repository at:
git://git.yoctoproject.org/poky-contrib zedd/kernel
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Bruce Ashfield (5):
linux-yocto/5.4: Revert "platform/x86: wmi: Destroy on cleanup rather
than unregister"
linux-yocto/5.4: fix kernel selftests
linux-yocto/5.4: KVM: LAPIC: Mark hrtimer for period or oneshot mode
to expire in hard interrupt context
linux-yocto/5.4: ARM: 8918/2: only build return_address() if needed
linux-yocto/5.4: configuration tweaks
.../linux/linux-yocto-rt_5.4.bb | 4 ++--
.../linux/linux-yocto-tiny_5.4.bb | 6 +++---
meta/recipes-kernel/linux/linux-yocto_5.4.bb | 20 +++++++++----------
3 files changed, 15 insertions(+), 15 deletions(-)
--
2.19.1
^ permalink raw reply [flat|nested] 64+ messages in thread
* [PATCH 0/5] linux-yocto: consolidated pull request
@ 2016-07-27 16:57 Bruce Ashfield
0 siblings, 0 replies; 64+ messages in thread
From: Bruce Ashfield @ 2016-07-27 16:57 UTC (permalink / raw)
To: richard.purdie; +Cc: openembedded-core
Hi all,
Here's the latest batch of linux-yocto (4.1 and 4.4) changes. They are
-stable updates, a memory leak fix and configuration tweaks (in particular
the removal of debug kernel from the printk fragment).
This is a slight overlap with another series that I sent before, since I
noticed some mistakes in the 4.1 and 4.4-stable update commits .. so I
rephrased them.
Cheers,
Bruce
The following changes since commit 039f47ad197a9a53109c9f3deadd9c35e62c056d:
uclibc: remove meta-yocto-bsp append (2016-07-26 08:56:32 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib zedd/kernel
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Bruce Ashfield (5):
linux-yocto/4.4: bump to v4.4.15
linux-yocto/4.1: bump to v4.1.28
linux-yocto/4.1: bug fixes and configuration changes
linux-yocto/4.4: lx-dialog and mei bug fixes
linux-yocto/4.4: mousedev and printk configuation streamlining
meta/recipes-kernel/linux/linux-yocto-rt_4.1.bb | 6 +++---
meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb | 4 ++--
meta/recipes-kernel/linux/linux-yocto-tiny_4.1.bb | 6 +++---
meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb | 6 +++---
meta/recipes-kernel/linux/linux-yocto_4.1.bb | 20 ++++++++++----------
meta/recipes-kernel/linux/linux-yocto_4.4.bb | 20 ++++++++++----------
6 files changed, 31 insertions(+), 31 deletions(-)
--
2.5.0
^ permalink raw reply [flat|nested] 64+ messages in thread
* [PATCH 0/5] linux-yocto: consolidated pull request
@ 2016-06-21 15:20 Bruce Ashfield
0 siblings, 0 replies; 64+ messages in thread
From: Bruce Ashfield @ 2016-06-21 15:20 UTC (permalink / raw)
To: richard.purdie; +Cc: openembedded-core
Hi all,
Here's the latest set of changes to the 4.1 and 4.4 linux-yocto
kernel's. Nothing particularly exciting, mainline backports and
minor fixups.
Cheers,
Bruce
The following changes since commit 84cce1d49ddb75025ec454d758fbc8d369920122:
e2fsprogs: remove the extra dot from the recipe filename (2016-06-21 13:00:17 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib zedd/kernel
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Bruce Ashfield (5):
linux-yocto/4.1: tpm2, pinctrl, powercap and watchdog backports
linux-yocto/4.1: SPI, MFD, alsa and perf backports
linux-yocto/4.1: driver, mmc and power backports
linux-yocto/4.1: pstate backports
linux-yocto/4.4: sensor driver backports
meta/recipes-kernel/linux/linux-yocto-rt_4.1.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto-tiny_4.1.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto_4.1.bb | 16 ++++++++--------
meta/recipes-kernel/linux/linux-yocto_4.4.bb | 16 ++++++++--------
5 files changed, 19 insertions(+), 19 deletions(-)
--
2.5.0
^ permalink raw reply [flat|nested] 64+ messages in thread
* [PATCH 0/5] linux-yocto: consolidated pull request
@ 2016-04-13 16:12 Bruce Ashfield
0 siblings, 0 replies; 64+ messages in thread
From: Bruce Ashfield @ 2016-04-13 16:12 UTC (permalink / raw)
To: richard.purdie; +Cc: openembedded-core
Hi all,
This series contains some changes that I've been gathering over the past
week. Nothing serious, just BSP mainline backports, configuration tweaks
to tiny (for usability) and a change to make aufs4 opt-in (versus always
on).
I've built and booted this for qemu* (standard and -rt).
Cheers,
Bruce
The following changes since commit e912c468875ffea7e8070cb7813bca262d1cbb0b:
kbd: remove uclibc-stdarg.patch (2016-04-13 10:12:53 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib zedd/kernel
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Bruce Ashfield (5):
linux-yocto/4.4: gpio-pca953x: fix the "drive" property cannot
read/write
linux-yocto/4.1: mainline SPI backports
linux-yocto/4.4: BXT enablement
linux-yocto: tiny and pin ctrl config updates
linux-yocto: make aufs4 optional
meta/recipes-kernel/linux/linux-yocto-rt_4.1.bb | 4 ++--
meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb | 4 ++--
meta/recipes-kernel/linux/linux-yocto-tiny_4.1.bb | 4 ++--
meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb | 4 ++--
meta/recipes-kernel/linux/linux-yocto_4.1.bb | 18 +++++++++---------
meta/recipes-kernel/linux/linux-yocto_4.4.bb | 18 +++++++++---------
6 files changed, 26 insertions(+), 26 deletions(-)
--
2.5.0
^ permalink raw reply [flat|nested] 64+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-06 22:49 ` Martin Jansa
@ 2015-05-07 15:33 ` Bruce Ashfield
0 siblings, 0 replies; 64+ messages in thread
From: Bruce Ashfield @ 2015-05-07 15:33 UTC (permalink / raw)
To: Martin Jansa, Richard Purdie
Cc: Patches and discussions about the oe-core layer
On 2015-05-06 06:49 PM, Martin Jansa wrote:
> I use tmpfs in most of my builds, so in most cases when I see the error
> from the build, tmpfs is already gone (purged by next build executed on
> the same sever).
ross just found something like this in one of his local builds .. I'm
pretty sure I see the race.
Fix coming shortly, and then the bigger changes I was mentioning before
as well.
Cheers,
Bruce
>
> On Wed, May 6, 2015 at 11:32 PM, Richard Purdie
> <richard.purdie@linuxfoundation.org
> <mailto:richard.purdie@linuxfoundation.org>> wrote:
>
> On Wed, 2015-05-06 at 13:46 -0400, Bruce Ashfield wrote:
> > On 2015-05-06 12:07 PM, Martin Jansa wrote:
> > > I've used master-next week or two ago (mostly to test bluez4 and python3
> > > changes) and soon after that dropped all linux-yocto related changes
> > > from it assuming that it's indeed cause for the issues I'm seeing, but
> > > it's not and it's still failing with master as well (and my
> > > jenkins/world builds are just small portion of my builds executed
> > > elsewhere where I see similar issues).
> >
> > Richard: How can we sort out the differences between the build
> > environment that Martin uses versus what the autobuilder is showing?
> >
> > There's nothing particularly complex happening during that build,
> > it's a checkout and generation of a config.
> >
> > I'm unable to reproduce any of the failures, and neither is the
> > autobuilder.
>
> This is a tough one and I'm struggling a little. We could try looking at
> the tmp/stamps/qemux86-poky-linux/linux-yocto/* files (sigdata in
> particular) as well as
> tmp/work/qemux86-poky-linux/linux-yocto/*/temp/log.task_order
>
> Martin, would you be able to share the above somewhere? I'm hoping this
> would give us a clue as to what the difference is between the builds and
> allow us to reproduce the problem.
>
> Cheers,
>
> Richard
>
>
>
^ permalink raw reply [flat|nested] 64+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-06 15:33 ` Martin Jansa
2015-05-06 15:44 ` Richard Purdie
@ 2015-05-07 6:33 ` Khem Raj
1 sibling, 0 replies; 64+ messages in thread
From: Khem Raj @ 2015-05-07 6:33 UTC (permalink / raw)
To: Martin Jansa; +Cc: openembedded-core
[-- Attachment #1: Type: text/plain, Size: 448 bytes --]
> On May 6, 2015, at 8:33 AM, Martin Jansa <martin.jansa@gmail.com> wrote:
>
> I'm considering providing simple old-style recipes for vanilla kernels
> and using them in my jenkins builds instead linux-yocto, because kernel
> shouldn't block testing other recipes from meta-oe and other layers as
> often as linux-yocto does.
just for build sake to avoid full kernel builds, having a dummy kernel recipe should be another alternative
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 211 bytes --]
^ permalink raw reply [flat|nested] 64+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-06 21:32 ` Richard Purdie
@ 2015-05-06 22:49 ` Martin Jansa
2015-05-07 15:33 ` Bruce Ashfield
0 siblings, 1 reply; 64+ messages in thread
From: Martin Jansa @ 2015-05-06 22:49 UTC (permalink / raw)
To: Richard Purdie; +Cc: Patches and discussions about the oe-core layer
[-- Attachment #1: Type: text/plain, Size: 1627 bytes --]
I use tmpfs in most of my builds, so in most cases when I see the error
from the build, tmpfs is already gone (purged by next build executed on the
same sever).
On Wed, May 6, 2015 at 11:32 PM, Richard Purdie <
richard.purdie@linuxfoundation.org> wrote:
> On Wed, 2015-05-06 at 13:46 -0400, Bruce Ashfield wrote:
> > On 2015-05-06 12:07 PM, Martin Jansa wrote:
> > > I've used master-next week or two ago (mostly to test bluez4 and
> python3
> > > changes) and soon after that dropped all linux-yocto related changes
> > > from it assuming that it's indeed cause for the issues I'm seeing, but
> > > it's not and it's still failing with master as well (and my
> > > jenkins/world builds are just small portion of my builds executed
> > > elsewhere where I see similar issues).
> >
> > Richard: How can we sort out the differences between the build
> > environment that Martin uses versus what the autobuilder is showing?
> >
> > There's nothing particularly complex happening during that build,
> > it's a checkout and generation of a config.
> >
> > I'm unable to reproduce any of the failures, and neither is the
> > autobuilder.
>
> This is a tough one and I'm struggling a little. We could try looking at
> the tmp/stamps/qemux86-poky-linux/linux-yocto/* files (sigdata in
> particular) as well as
> tmp/work/qemux86-poky-linux/linux-yocto/*/temp/log.task_order
>
> Martin, would you be able to share the above somewhere? I'm hoping this
> would give us a clue as to what the difference is between the builds and
> allow us to reproduce the problem.
>
> Cheers,
>
> Richard
>
>
>
[-- Attachment #2: Type: text/html, Size: 2142 bytes --]
^ permalink raw reply [flat|nested] 64+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-06 17:46 ` Bruce Ashfield
@ 2015-05-06 21:32 ` Richard Purdie
2015-05-06 22:49 ` Martin Jansa
0 siblings, 1 reply; 64+ messages in thread
From: Richard Purdie @ 2015-05-06 21:32 UTC (permalink / raw)
To: Bruce Ashfield; +Cc: openembedded-core
On Wed, 2015-05-06 at 13:46 -0400, Bruce Ashfield wrote:
> On 2015-05-06 12:07 PM, Martin Jansa wrote:
> > I've used master-next week or two ago (mostly to test bluez4 and python3
> > changes) and soon after that dropped all linux-yocto related changes
> > from it assuming that it's indeed cause for the issues I'm seeing, but
> > it's not and it's still failing with master as well (and my
> > jenkins/world builds are just small portion of my builds executed
> > elsewhere where I see similar issues).
>
> Richard: How can we sort out the differences between the build
> environment that Martin uses versus what the autobuilder is showing?
>
> There's nothing particularly complex happening during that build,
> it's a checkout and generation of a config.
>
> I'm unable to reproduce any of the failures, and neither is the
> autobuilder.
This is a tough one and I'm struggling a little. We could try looking at
the tmp/stamps/qemux86-poky-linux/linux-yocto/* files (sigdata in
particular) as well as
tmp/work/qemux86-poky-linux/linux-yocto/*/temp/log.task_order
Martin, would you be able to share the above somewhere? I'm hoping this
would give us a clue as to what the difference is between the builds and
allow us to reproduce the problem.
Cheers,
Richard
^ permalink raw reply [flat|nested] 64+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-06 16:07 ` Martin Jansa
@ 2015-05-06 17:46 ` Bruce Ashfield
2015-05-06 21:32 ` Richard Purdie
0 siblings, 1 reply; 64+ messages in thread
From: Bruce Ashfield @ 2015-05-06 17:46 UTC (permalink / raw)
To: Martin Jansa, Richard Purdie; +Cc: openembedded-core
On 2015-05-06 12:07 PM, Martin Jansa wrote:
> On Wed, May 06, 2015 at 04:44:46PM +0100, Richard Purdie wrote:
>> On Wed, 2015-05-06 at 17:33 +0200, Martin Jansa wrote:
>>> On Wed, May 06, 2015 at 10:58:36AM -0400, Bruce Ashfield wrote:
>>>> On 2015-05-06 10:42 AM, Martin Jansa wrote:
>>>> At this point, all I can say is file a bug. My builds of the same
>>>> board work, and the autobuilder show up green.
>>>>
>>>> That screams race condition, so I'll look into it from that angle.
>>>
>>> I'm considering providing simple old-style recipes for vanilla kernels
>>> and using them in my jenkins builds instead linux-yocto, because kernel
>>> shouldn't block testing other recipes from meta-oe and other layers as
>>> often as linux-yocto does.
>>
>> I wasn't aware of linux-yocto breaking that often?
>
> Someone can query http://errors.yoctoproject.org/ database to see how
> often (or if it's just me and my builds), unfortunately the full-text
> search for "linux-yocto" doesn't provide good overview of issues,
> because it shows 350 errors and not all are from linux-yocto recipe.
>
> http://www.openembedded.org/wiki/Bitbake_World_Status* pages and status
> on e-mail also aren't very accurate because I submit only reports from
> relatively success full builds (so I usually skip the builds with failed
> kernel, unless it's failing like that for long time).
>
>> I am aware that:
>>
>> * we have a race issue with shared_work which we're trying to resolve
>> and its proving tricky to find a patch which doesn't break builds
>>
>> * we have the newly reported issue in this thread. FWIW the builders
>> I've seen are all green
>>
>> * there are some warnings in the build which need addressing
>>
>> but on the most part I thought we'd caught the serious kernel failures
>> in advance of changes hitting master. Are you using master-next or
>> master?
>
> I've used master-next week or two ago (mostly to test bluez4 and python3
> changes) and soon after that dropped all linux-yocto related changes
> from it assuming that it's indeed cause for the issues I'm seeing, but
> it's not and it's still failing with master as well (and my
> jenkins/world builds are just small portion of my builds executed
> elsewhere where I see similar issues).
Richard: How can we sort out the differences between the build
environment that Martin uses versus what the autobuilder is showing?
There's nothing particularly complex happening during that build,
it's a checkout and generation of a config.
I'm unable to reproduce any of the failures, and neither is the
autobuilder.
I've stared at the code and can't see what could cause any of this.
That being said, I think I have a solution to what Martin is reporting
here, where I've changed the way the meta data is maintained and
build.
It will be ready in a week or so, so I'd be interested in us holding
on anything drastic until we can try that out.
Bruce
>
>> Its its -next, I can understand the problems more as that has been
>> unstable recently but then by its nature, it can be. We are rooting out
>> problems before master afaict though?
>>
>> Cheers,
>>
>> Richard
>
^ permalink raw reply [flat|nested] 64+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-06 15:44 ` Richard Purdie
@ 2015-05-06 16:07 ` Martin Jansa
2015-05-06 17:46 ` Bruce Ashfield
0 siblings, 1 reply; 64+ messages in thread
From: Martin Jansa @ 2015-05-06 16:07 UTC (permalink / raw)
To: Richard Purdie; +Cc: openembedded-core
On Wed, May 06, 2015 at 04:44:46PM +0100, Richard Purdie wrote:
> On Wed, 2015-05-06 at 17:33 +0200, Martin Jansa wrote:
> > On Wed, May 06, 2015 at 10:58:36AM -0400, Bruce Ashfield wrote:
> > > On 2015-05-06 10:42 AM, Martin Jansa wrote:
> > > At this point, all I can say is file a bug. My builds of the same
> > > board work, and the autobuilder show up green.
> > >
> > > That screams race condition, so I'll look into it from that angle.
> >
> > I'm considering providing simple old-style recipes for vanilla kernels
> > and using them in my jenkins builds instead linux-yocto, because kernel
> > shouldn't block testing other recipes from meta-oe and other layers as
> > often as linux-yocto does.
>
> I wasn't aware of linux-yocto breaking that often?
Someone can query http://errors.yoctoproject.org/ database to see how
often (or if it's just me and my builds), unfortunately the full-text
search for "linux-yocto" doesn't provide good overview of issues,
because it shows 350 errors and not all are from linux-yocto recipe.
http://www.openembedded.org/wiki/Bitbake_World_Status* pages and status
on e-mail also aren't very accurate because I submit only reports from
relatively success full builds (so I usually skip the builds with failed
kernel, unless it's failing like that for long time).
> I am aware that:
>
> * we have a race issue with shared_work which we're trying to resolve
> and its proving tricky to find a patch which doesn't break builds
>
> * we have the newly reported issue in this thread. FWIW the builders
> I've seen are all green
>
> * there are some warnings in the build which need addressing
>
> but on the most part I thought we'd caught the serious kernel failures
> in advance of changes hitting master. Are you using master-next or
> master?
I've used master-next week or two ago (mostly to test bluez4 and python3
changes) and soon after that dropped all linux-yocto related changes
from it assuming that it's indeed cause for the issues I'm seeing, but
it's not and it's still failing with master as well (and my
jenkins/world builds are just small portion of my builds executed
elsewhere where I see similar issues).
> Its its -next, I can understand the problems more as that has been
> unstable recently but then by its nature, it can be. We are rooting out
> problems before master afaict though?
>
> Cheers,
>
> Richard
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
^ permalink raw reply [flat|nested] 64+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-06 15:33 ` Martin Jansa
@ 2015-05-06 15:44 ` Richard Purdie
2015-05-06 16:07 ` Martin Jansa
2015-05-07 6:33 ` Khem Raj
1 sibling, 1 reply; 64+ messages in thread
From: Richard Purdie @ 2015-05-06 15:44 UTC (permalink / raw)
To: Martin Jansa; +Cc: openembedded-core
On Wed, 2015-05-06 at 17:33 +0200, Martin Jansa wrote:
> On Wed, May 06, 2015 at 10:58:36AM -0400, Bruce Ashfield wrote:
> > On 2015-05-06 10:42 AM, Martin Jansa wrote:
> > At this point, all I can say is file a bug. My builds of the same
> > board work, and the autobuilder show up green.
> >
> > That screams race condition, so I'll look into it from that angle.
>
> I'm considering providing simple old-style recipes for vanilla kernels
> and using them in my jenkins builds instead linux-yocto, because kernel
> shouldn't block testing other recipes from meta-oe and other layers as
> often as linux-yocto does.
I wasn't aware of linux-yocto breaking that often?
I am aware that:
* we have a race issue with shared_work which we're trying to resolve
and its proving tricky to find a patch which doesn't break builds
* we have the newly reported issue in this thread. FWIW the builders
I've seen are all green
* there are some warnings in the build which need addressing
but on the most part I thought we'd caught the serious kernel failures
in advance of changes hitting master. Are you using master-next or
master?
Its its -next, I can understand the problems more as that has been
unstable recently but then by its nature, it can be. We are rooting out
problems before master afaict though?
Cheers,
Richard
^ permalink raw reply [flat|nested] 64+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-06 14:58 ` Bruce Ashfield
@ 2015-05-06 15:33 ` Martin Jansa
2015-05-06 15:44 ` Richard Purdie
2015-05-07 6:33 ` Khem Raj
0 siblings, 2 replies; 64+ messages in thread
From: Martin Jansa @ 2015-05-06 15:33 UTC (permalink / raw)
To: Bruce Ashfield; +Cc: openembedded-core
On Wed, May 06, 2015 at 10:58:36AM -0400, Bruce Ashfield wrote:
> On 2015-05-06 10:42 AM, Martin Jansa wrote:
> > On Sat, May 02, 2015 at 10:50:53PM -0400, Bruce Ashfield wrote:
> >> On 2015-05-02 4:13 AM, Martin Jansa wrote:
> >>> On Fri, May 01, 2015 at 07:30:24PM -0400, Bruce Ashfield wrote:
> >>>> On 2015-05-01 6:59 PM, Richard Purdie wrote:
> >>>>> On Thu, 2015-04-30 at 21:34 -0400, Bruce Ashfield wrote:
> >>>>>> Here is the latest consolidated pull request for the supported linux-yocto
> >>>>>> kernels.
> >>>>>>
> >>>>>> - We have a refresh of the 3.14-rt support
> >>>>>> - bluetooh configuration changes for common-pc/qemux86
> >>>>>> - braswell BSP features and fixes
> >>>>>> - Introduction of the 4.1-rc1 -dev kernel (and associated perf fix).
> >>>>>> I've built and booted these on my local machines and qemu, and
> >>>>>> everything was sane.
> >>>
> >>> Does it fix the issue I've reported few days ago?
> >>> http://lists.openembedded.org/pipermail/openembedded-core/2015-April/104344.html
> >>
> >> Nope. But one config warning is far down on the list when I'm
> >> trying to introduce new -stable's and an entire -dev kernel.
> >>
> >> I didn't forget about it, it'll just get done in priority order.
> >
> > OK, now it fails completely in default qemux86 builds:
> >
>
> At this point, all I can say is file a bug. My builds of the same
> board work, and the autobuilder show up green.
>
> That screams race condition, so I'll look into it from that angle.
I'm considering providing simple old-style recipes for vanilla kernels
and using them in my jenkins builds instead linux-yocto, because kernel
shouldn't block testing other recipes from meta-oe and other layers as
often as linux-yocto does.
> > ERROR: Function failed: do_kernel_configme (log file is located at /home/jenkins/oe/world/shr-core/tmp-glibc/work/qemux86-oe-linux/linux-yocto/3.19.5+gitAUTOINC+7215fe4313_d5d30ba4d2-r0/temp/log.do_kernel_configme.1159)
> > ERROR: Logfile of failure stored in: /home/jenkins/oe/world/shr-core/tmp-glibc/work/qemux86-oe-linux/linux-yocto/3.19.5+gitAUTOINC+7215fe4313_d5d30ba4d2-r0/temp/log.do_kernel_configme.1159
> > Log data follows:
> > | DEBUG: Executing shell function do_kernel_configme
> > | NOTE: kernel configme
> > | [INFO] Configuring target/machine combo: "standard/qemux86"
> > | [INFO] collecting configs in .meta/meta-series
> > | [ERROR] frag /home/jenkins/oe/world/shr-core/tmp-glibc/work-shared/qemux86/kernel-source/.meta/cfg/kernel-cache/bsp/common-pc/common-pc-drivers-32.cfg does not exist
> > | Error running the meta series for collecting config data
> > | config of "standard/qemux86" failed
> > | WARNING: exit code 1 from a shell command.
> > | ERROR: Function failed: do_kernel_configme (log file is located at /home/jenkins/oe/world/shr-core/tmp-glibc/work/qemux86-oe-linux/linux-yocto/3.19.5+gitAUTOINC+7215fe4313_d5d30ba4d2-r0/temp/log.do_kernel_configme.1159)
> > NOTE: recipe linux-yocto-3.19.5+gitAUTOINC+7215fe4313_d5d30ba4d2-r0: task do_kernel_configme: Failed
> > ERROR: Task 30162 (/home/jenkins/oe/world/shr-core/openembedded-core/meta/recipes-kernel/linux/linux-yocto_3.19.bb, do_kernel_configme) failed with exit code '1'
> >
> > http://errors.yoctoproject.org/Errors/Details/10481/
> >
> >>>>>> The -dev kernel obviously isn't something for deployment yet, but
> >>>>>> it builds, and forms the base for follow up config changes, features
> >>>>>> and development work. I built and booted core-image-kernel dev with
> >>>>>> the 4.1 changes in place.
> >>>>>
> >>>>> The autobuilder showed up this for an x32 build :/.
> >>>>
> >>>> Can one of the intel folks have a look at this ? I won't be able to get
> >>>> to it until Tuesday at the earliest.
> >>>>
> >>>> Bruce
> >>>>
> >>>>>
> >>>>> https://autobuilder.yoctoproject.org/main/builders/nightly-x32/builds/282/steps/BuildImages/logs/stdio
> >>>>>
> >>>>> Cheers,
> >>>>>
> >>>>> Richard
> >>>>>
> >>>>
> >>>> --
> >>>> _______________________________________________
> >>>> Openembedded-core mailing list
> >>>> Openembedded-core@lists.openembedded.org
> >>>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
> >>>
> >>
> >
>
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
^ permalink raw reply [flat|nested] 64+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-06 14:42 ` Martin Jansa
@ 2015-05-06 14:58 ` Bruce Ashfield
2015-05-06 15:33 ` Martin Jansa
0 siblings, 1 reply; 64+ messages in thread
From: Bruce Ashfield @ 2015-05-06 14:58 UTC (permalink / raw)
To: Martin Jansa; +Cc: openembedded-core
On 2015-05-06 10:42 AM, Martin Jansa wrote:
> On Sat, May 02, 2015 at 10:50:53PM -0400, Bruce Ashfield wrote:
>> On 2015-05-02 4:13 AM, Martin Jansa wrote:
>>> On Fri, May 01, 2015 at 07:30:24PM -0400, Bruce Ashfield wrote:
>>>> On 2015-05-01 6:59 PM, Richard Purdie wrote:
>>>>> On Thu, 2015-04-30 at 21:34 -0400, Bruce Ashfield wrote:
>>>>>> Here is the latest consolidated pull request for the supported linux-yocto
>>>>>> kernels.
>>>>>>
>>>>>> - We have a refresh of the 3.14-rt support
>>>>>> - bluetooh configuration changes for common-pc/qemux86
>>>>>> - braswell BSP features and fixes
>>>>>> - Introduction of the 4.1-rc1 -dev kernel (and associated perf fix).
>>>>>> I've built and booted these on my local machines and qemu, and
>>>>>> everything was sane.
>>>
>>> Does it fix the issue I've reported few days ago?
>>> http://lists.openembedded.org/pipermail/openembedded-core/2015-April/104344.html
>>
>> Nope. But one config warning is far down on the list when I'm
>> trying to introduce new -stable's and an entire -dev kernel.
>>
>> I didn't forget about it, it'll just get done in priority order.
>
> OK, now it fails completely in default qemux86 builds:
>
At this point, all I can say is file a bug. My builds of the same
board work, and the autobuilder show up green.
That screams race condition, so I'll look into it from that angle.
Bruce
> ERROR: Function failed: do_kernel_configme (log file is located at /home/jenkins/oe/world/shr-core/tmp-glibc/work/qemux86-oe-linux/linux-yocto/3.19.5+gitAUTOINC+7215fe4313_d5d30ba4d2-r0/temp/log.do_kernel_configme.1159)
> ERROR: Logfile of failure stored in: /home/jenkins/oe/world/shr-core/tmp-glibc/work/qemux86-oe-linux/linux-yocto/3.19.5+gitAUTOINC+7215fe4313_d5d30ba4d2-r0/temp/log.do_kernel_configme.1159
> Log data follows:
> | DEBUG: Executing shell function do_kernel_configme
> | NOTE: kernel configme
> | [INFO] Configuring target/machine combo: "standard/qemux86"
> | [INFO] collecting configs in .meta/meta-series
> | [ERROR] frag /home/jenkins/oe/world/shr-core/tmp-glibc/work-shared/qemux86/kernel-source/.meta/cfg/kernel-cache/bsp/common-pc/common-pc-drivers-32.cfg does not exist
> | Error running the meta series for collecting config data
> | config of "standard/qemux86" failed
> | WARNING: exit code 1 from a shell command.
> | ERROR: Function failed: do_kernel_configme (log file is located at /home/jenkins/oe/world/shr-core/tmp-glibc/work/qemux86-oe-linux/linux-yocto/3.19.5+gitAUTOINC+7215fe4313_d5d30ba4d2-r0/temp/log.do_kernel_configme.1159)
> NOTE: recipe linux-yocto-3.19.5+gitAUTOINC+7215fe4313_d5d30ba4d2-r0: task do_kernel_configme: Failed
> ERROR: Task 30162 (/home/jenkins/oe/world/shr-core/openembedded-core/meta/recipes-kernel/linux/linux-yocto_3.19.bb, do_kernel_configme) failed with exit code '1'
>
> http://errors.yoctoproject.org/Errors/Details/10481/
>
>>>>>> The -dev kernel obviously isn't something for deployment yet, but
>>>>>> it builds, and forms the base for follow up config changes, features
>>>>>> and development work. I built and booted core-image-kernel dev with
>>>>>> the 4.1 changes in place.
>>>>>
>>>>> The autobuilder showed up this for an x32 build :/.
>>>>
>>>> Can one of the intel folks have a look at this ? I won't be able to get
>>>> to it until Tuesday at the earliest.
>>>>
>>>> Bruce
>>>>
>>>>>
>>>>> https://autobuilder.yoctoproject.org/main/builders/nightly-x32/builds/282/steps/BuildImages/logs/stdio
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Richard
>>>>>
>>>>
>>>> --
>>>> _______________________________________________
>>>> Openembedded-core mailing list
>>>> Openembedded-core@lists.openembedded.org
>>>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>>>
>>
>
^ permalink raw reply [flat|nested] 64+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-03 2:50 ` Bruce Ashfield
@ 2015-05-06 14:42 ` Martin Jansa
2015-05-06 14:58 ` Bruce Ashfield
0 siblings, 1 reply; 64+ messages in thread
From: Martin Jansa @ 2015-05-06 14:42 UTC (permalink / raw)
To: Bruce Ashfield; +Cc: openembedded-core
On Sat, May 02, 2015 at 10:50:53PM -0400, Bruce Ashfield wrote:
> On 2015-05-02 4:13 AM, Martin Jansa wrote:
> > On Fri, May 01, 2015 at 07:30:24PM -0400, Bruce Ashfield wrote:
> >> On 2015-05-01 6:59 PM, Richard Purdie wrote:
> >>> On Thu, 2015-04-30 at 21:34 -0400, Bruce Ashfield wrote:
> >>>> Here is the latest consolidated pull request for the supported linux-yocto
> >>>> kernels.
> >>>>
> >>>> - We have a refresh of the 3.14-rt support
> >>>> - bluetooh configuration changes for common-pc/qemux86
> >>>> - braswell BSP features and fixes
> >>>> - Introduction of the 4.1-rc1 -dev kernel (and associated perf fix).
> >>>> I've built and booted these on my local machines and qemu, and
> >>>> everything was sane.
> >
> > Does it fix the issue I've reported few days ago?
> > http://lists.openembedded.org/pipermail/openembedded-core/2015-April/104344.html
>
> Nope. But one config warning is far down on the list when I'm
> trying to introduce new -stable's and an entire -dev kernel.
>
> I didn't forget about it, it'll just get done in priority order.
OK, now it fails completely in default qemux86 builds:
ERROR: Function failed: do_kernel_configme (log file is located at /home/jenkins/oe/world/shr-core/tmp-glibc/work/qemux86-oe-linux/linux-yocto/3.19.5+gitAUTOINC+7215fe4313_d5d30ba4d2-r0/temp/log.do_kernel_configme.1159)
ERROR: Logfile of failure stored in: /home/jenkins/oe/world/shr-core/tmp-glibc/work/qemux86-oe-linux/linux-yocto/3.19.5+gitAUTOINC+7215fe4313_d5d30ba4d2-r0/temp/log.do_kernel_configme.1159
Log data follows:
| DEBUG: Executing shell function do_kernel_configme
| NOTE: kernel configme
| [INFO] Configuring target/machine combo: "standard/qemux86"
| [INFO] collecting configs in .meta/meta-series
| [ERROR] frag /home/jenkins/oe/world/shr-core/tmp-glibc/work-shared/qemux86/kernel-source/.meta/cfg/kernel-cache/bsp/common-pc/common-pc-drivers-32.cfg does not exist
| Error running the meta series for collecting config data
| config of "standard/qemux86" failed
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_kernel_configme (log file is located at /home/jenkins/oe/world/shr-core/tmp-glibc/work/qemux86-oe-linux/linux-yocto/3.19.5+gitAUTOINC+7215fe4313_d5d30ba4d2-r0/temp/log.do_kernel_configme.1159)
NOTE: recipe linux-yocto-3.19.5+gitAUTOINC+7215fe4313_d5d30ba4d2-r0: task do_kernel_configme: Failed
ERROR: Task 30162 (/home/jenkins/oe/world/shr-core/openembedded-core/meta/recipes-kernel/linux/linux-yocto_3.19.bb, do_kernel_configme) failed with exit code '1'
http://errors.yoctoproject.org/Errors/Details/10481/
> >>>> The -dev kernel obviously isn't something for deployment yet, but
> >>>> it builds, and forms the base for follow up config changes, features
> >>>> and development work. I built and booted core-image-kernel dev with
> >>>> the 4.1 changes in place.
> >>>
> >>> The autobuilder showed up this for an x32 build :/.
> >>
> >> Can one of the intel folks have a look at this ? I won't be able to get
> >> to it until Tuesday at the earliest.
> >>
> >> Bruce
> >>
> >>>
> >>> https://autobuilder.yoctoproject.org/main/builders/nightly-x32/builds/282/steps/BuildImages/logs/stdio
> >>>
> >>> Cheers,
> >>>
> >>> Richard
> >>>
> >>
> >> --
> >> _______________________________________________
> >> Openembedded-core mailing list
> >> Openembedded-core@lists.openembedded.org
> >> http://lists.openembedded.org/mailman/listinfo/openembedded-core
> >
>
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
^ permalink raw reply [flat|nested] 64+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-03 21:30 ` Richard Purdie
2015-05-04 4:36 ` Bruce Ashfield
@ 2015-05-04 15:01 ` Bruce Ashfield
1 sibling, 0 replies; 64+ messages in thread
From: Bruce Ashfield @ 2015-05-04 15:01 UTC (permalink / raw)
To: Richard Purdie; +Cc: openembedded-core
On 2015-05-03 05:30 PM, Richard Purdie wrote:
> On Thu, 2015-04-30 at 21:34 -0400, Bruce Ashfield wrote:
>> Here is the latest consolidated pull request for the supported linux-yocto
>> kernels.
>>
>> - We have a refresh of the 3.14-rt support
>> - bluetooh configuration changes for common-pc/qemux86
>> - braswell BSP features and fixes
>> - Introduction of the 4.1-rc1 -dev kernel (and associated perf fix).
>>
>> I've built and booted these on my local machines and qemu, and
>> everything was sane.
>>
>> The -dev kernel obviously isn't something for deployment yet, but
>> it builds, and forms the base for follow up config changes, features
>> and development work. I built and booted core-image-kernel dev with
>> the 4.1 changes in place.
>
> There was also a problem with poky-lsb. The idea (as far as I remember)
> is that it should be using LTSI rather than the default main kernel so
> we could split the testing. Unfortunately it was pointing at 3.10 which
> doesn't exist any longer so was using 3.17. I think LTSI is 3.14 so I
> updated the PREFERRED_VERSION to that.
>
> This resulted in this failure on the autobuilder:
>
> https://autobuilder.yoctoproject.org/main/builders/nightly-mips-lsb/builds/281/steps/BuildImages/logs/stdio
>
> Basically with qemumips and 3.14. Hopefully not a hard one to fix. If
> I've mixed the versions up, let me know which one poky-lsb should be
FYI: I've fixed the mips build. Looking at x86 now. SRCREV updates
to follow ASAP.
Bruce
> using.
>
> Cheers,
>
> Richard
>
^ permalink raw reply [flat|nested] 64+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-03 21:30 ` Richard Purdie
@ 2015-05-04 4:36 ` Bruce Ashfield
2015-05-04 15:01 ` Bruce Ashfield
1 sibling, 0 replies; 64+ messages in thread
From: Bruce Ashfield @ 2015-05-04 4:36 UTC (permalink / raw)
To: Richard Purdie; +Cc: openembedded-core
On 2015-05-03 5:30 PM, Richard Purdie wrote:
> On Thu, 2015-04-30 at 21:34 -0400, Bruce Ashfield wrote:
>> Here is the latest consolidated pull request for the supported linux-yocto
>> kernels.
>>
>> - We have a refresh of the 3.14-rt support
>> - bluetooh configuration changes for common-pc/qemux86
>> - braswell BSP features and fixes
>> - Introduction of the 4.1-rc1 -dev kernel (and associated perf fix).
>>
>> I've built and booted these on my local machines and qemu, and
>> everything was sane.
>>
>> The -dev kernel obviously isn't something for deployment yet, but
>> it builds, and forms the base for follow up config changes, features
>> and development work. I built and booted core-image-kernel dev with
>> the 4.1 changes in place.
>
> There was also a problem with poky-lsb. The idea (as far as I remember)
> is that it should be using LTSI rather than the default main kernel so
> we could split the testing. Unfortunately it was pointing at 3.10 which
> doesn't exist any longer so was using 3.17. I think LTSI is 3.14 so I
> updated the PREFERRED_VERSION to that.
Correct on all counts. We did want it to use LTSI, and that is 3.14
at the moment.
>
> This resulted in this failure on the autobuilder:
>
> https://autobuilder.yoctoproject.org/main/builders/nightly-mips-lsb/builds/281/steps/BuildImages/logs/stdio
>
> Basically with qemumips and 3.14. Hopefully not a hard one to fix. If
Doesn't look to bad. I'll address this one along with the x32 build
failure on Monday (assuming I get it fixed in the day).
Bruce
> I've mixed the versions up, let me know which one poky-lsb should be
> using.
>
> Cheers,
>
> Richard
>
^ permalink raw reply [flat|nested] 64+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-01 1:34 Bruce Ashfield
2015-05-01 22:59 ` Richard Purdie
@ 2015-05-03 21:30 ` Richard Purdie
2015-05-04 4:36 ` Bruce Ashfield
2015-05-04 15:01 ` Bruce Ashfield
1 sibling, 2 replies; 64+ messages in thread
From: Richard Purdie @ 2015-05-03 21:30 UTC (permalink / raw)
To: Bruce Ashfield; +Cc: openembedded-core
On Thu, 2015-04-30 at 21:34 -0400, Bruce Ashfield wrote:
> Here is the latest consolidated pull request for the supported linux-yocto
> kernels.
>
> - We have a refresh of the 3.14-rt support
> - bluetooh configuration changes for common-pc/qemux86
> - braswell BSP features and fixes
> - Introduction of the 4.1-rc1 -dev kernel (and associated perf fix).
>
> I've built and booted these on my local machines and qemu, and
> everything was sane.
>
> The -dev kernel obviously isn't something for deployment yet, but
> it builds, and forms the base for follow up config changes, features
> and development work. I built and booted core-image-kernel dev with
> the 4.1 changes in place.
There was also a problem with poky-lsb. The idea (as far as I remember)
is that it should be using LTSI rather than the default main kernel so
we could split the testing. Unfortunately it was pointing at 3.10 which
doesn't exist any longer so was using 3.17. I think LTSI is 3.14 so I
updated the PREFERRED_VERSION to that.
This resulted in this failure on the autobuilder:
https://autobuilder.yoctoproject.org/main/builders/nightly-mips-lsb/builds/281/steps/BuildImages/logs/stdio
Basically with qemumips and 3.14. Hopefully not a hard one to fix. If
I've mixed the versions up, let me know which one poky-lsb should be
using.
Cheers,
Richard
^ permalink raw reply [flat|nested] 64+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-03 3:52 ` Bruce Ashfield
@ 2015-05-03 10:48 ` Richard Purdie
0 siblings, 0 replies; 64+ messages in thread
From: Richard Purdie @ 2015-05-03 10:48 UTC (permalink / raw)
To: Bruce Ashfield; +Cc: openembedded-core
On Sat, 2015-05-02 at 23:52 -0400, Bruce Ashfield wrote:
> On 2015-05-02 5:00 AM, Richard Purdie wrote:
> > On Fri, 2015-05-01 at 19:30 -0400, Bruce Ashfield wrote:
> >> On 2015-05-01 6:59 PM, Richard Purdie wrote:
> >>> On Thu, 2015-04-30 at 21:34 -0400, Bruce Ashfield wrote:
> >>>> Here is the latest consolidated pull request for the supported linux-yocto
> >>>> kernels.
> >>>>
> >>>> - We have a refresh of the 3.14-rt support
> >>>> - bluetooh configuration changes for common-pc/qemux86
> >>>> - braswell BSP features and fixes
> >>>> - Introduction of the 4.1-rc1 -dev kernel (and associated perf fix).
> >>>>
> >>>> I've built and booted these on my local machines and qemu, and
> >>>> everything was sane.
> >>>>
> >>>> The -dev kernel obviously isn't something for deployment yet, but
> >>>> it builds, and forms the base for follow up config changes, features
> >>>> and development work. I built and booted core-image-kernel dev with
> >>>> the 4.1 changes in place.
> >>>
> >>> The autobuilder showed up this for an x32 build :/.
> >>
> >> Can one of the intel folks have a look at this ? I won't be able to get
> >> to it until Tuesday at the earliest.
> >
> > I had a look into this. The issue is that this has been applied:
> >
> > http://git.yoctoproject.org/cgit.cgi/linux-yocto-3.19/commit/?h=standard/base&id=423e98721e048f6c7b925a75448f6c4ecb2b5b69
> >
> > but it needs:
> >
> > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=ce793486e23e0162a732c605189c8028e0910e86
> >
> > and the ioapic driver also appears to need:
> >
> > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/?id=ecf5636dcd59cd5508641f995cc4c2bafedbb995
> > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/?id=62d1141ff34e35de496ba06491c8e854b23b3f3e
> >
> >
> > which meant I also had to add:
> >
> > struct resource_win {
> > struct resource res; /* In master (CPU) address space */
> > resource_size_t offset; /* Translation offset for bridge */
> > };
> >
> > to drivers/acpi/ioapic.c to make it compile which appears to be related to:
> >
> > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a49170b552423a3e85fc4f0d778c707402ee4863
> >
> > which depends on a number of patches from around that time which change acpi/resource.c:
> >
> > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/drivers/acpi/resource.c
> >
> > (from 2015/2/3)
> >
> > At this point I'm out my depth on how you want to fix this but it does
> > appear related to the Braswell changes.
> >
> > To be clear qemux86 and qemux86-64 don't build at all with this series.
> > I'll see if I can just drop the Braswell parts.
>
> I did reproduce the issue here as well, so with any luck, I can sneak
> enough time to have this fixed for Monday after all.
From my perspective there isn't a rush at this point. I've merged the
config changes which unblocked the bluez patches and things are
therefore "flowing" from my perspective, the stable update can wait
until later in the week.
Cheers,
Richard
^ permalink raw reply [flat|nested] 64+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-02 9:00 ` Richard Purdie
2015-05-03 2:53 ` Bruce Ashfield
@ 2015-05-03 3:52 ` Bruce Ashfield
2015-05-03 10:48 ` Richard Purdie
1 sibling, 1 reply; 64+ messages in thread
From: Bruce Ashfield @ 2015-05-03 3:52 UTC (permalink / raw)
To: Richard Purdie; +Cc: openembedded-core
On 2015-05-02 5:00 AM, Richard Purdie wrote:
> On Fri, 2015-05-01 at 19:30 -0400, Bruce Ashfield wrote:
>> On 2015-05-01 6:59 PM, Richard Purdie wrote:
>>> On Thu, 2015-04-30 at 21:34 -0400, Bruce Ashfield wrote:
>>>> Here is the latest consolidated pull request for the supported linux-yocto
>>>> kernels.
>>>>
>>>> - We have a refresh of the 3.14-rt support
>>>> - bluetooh configuration changes for common-pc/qemux86
>>>> - braswell BSP features and fixes
>>>> - Introduction of the 4.1-rc1 -dev kernel (and associated perf fix).
>>>>
>>>> I've built and booted these on my local machines and qemu, and
>>>> everything was sane.
>>>>
>>>> The -dev kernel obviously isn't something for deployment yet, but
>>>> it builds, and forms the base for follow up config changes, features
>>>> and development work. I built and booted core-image-kernel dev with
>>>> the 4.1 changes in place.
>>>
>>> The autobuilder showed up this for an x32 build :/.
>>
>> Can one of the intel folks have a look at this ? I won't be able to get
>> to it until Tuesday at the earliest.
>
> I had a look into this. The issue is that this has been applied:
>
> http://git.yoctoproject.org/cgit.cgi/linux-yocto-3.19/commit/?h=standard/base&id=423e98721e048f6c7b925a75448f6c4ecb2b5b69
>
> but it needs:
>
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=ce793486e23e0162a732c605189c8028e0910e86
>
> and the ioapic driver also appears to need:
>
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/?id=ecf5636dcd59cd5508641f995cc4c2bafedbb995
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/?id=62d1141ff34e35de496ba06491c8e854b23b3f3e
>
>
> which meant I also had to add:
>
> struct resource_win {
> struct resource res; /* In master (CPU) address space */
> resource_size_t offset; /* Translation offset for bridge */
> };
>
> to drivers/acpi/ioapic.c to make it compile which appears to be related to:
>
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a49170b552423a3e85fc4f0d778c707402ee4863
>
> which depends on a number of patches from around that time which change acpi/resource.c:
>
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/drivers/acpi/resource.c
>
> (from 2015/2/3)
>
> At this point I'm out my depth on how you want to fix this but it does
> appear related to the Braswell changes.
>
> To be clear qemux86 and qemux86-64 don't build at all with this series.
> I'll see if I can just drop the Braswell parts.
I did reproduce the issue here as well, so with any luck, I can sneak
enough time to have this fixed for Monday after all.
Bruce
>
> Cheers,
>
> Richard
>
^ permalink raw reply [flat|nested] 64+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-02 9:00 ` Richard Purdie
@ 2015-05-03 2:53 ` Bruce Ashfield
2015-05-03 3:52 ` Bruce Ashfield
1 sibling, 0 replies; 64+ messages in thread
From: Bruce Ashfield @ 2015-05-03 2:53 UTC (permalink / raw)
To: Richard Purdie; +Cc: openembedded-core
On 2015-05-02 5:00 AM, Richard Purdie wrote:
> On Fri, 2015-05-01 at 19:30 -0400, Bruce Ashfield wrote:
>> On 2015-05-01 6:59 PM, Richard Purdie wrote:
>>> On Thu, 2015-04-30 at 21:34 -0400, Bruce Ashfield wrote:
>>>> Here is the latest consolidated pull request for the supported linux-yocto
>>>> kernels.
>>>>
>>>> - We have a refresh of the 3.14-rt support
>>>> - bluetooh configuration changes for common-pc/qemux86
>>>> - braswell BSP features and fixes
>>>> - Introduction of the 4.1-rc1 -dev kernel (and associated perf fix).
>>>>
>>>> I've built and booted these on my local machines and qemu, and
>>>> everything was sane.
>>>>
>>>> The -dev kernel obviously isn't something for deployment yet, but
>>>> it builds, and forms the base for follow up config changes, features
>>>> and development work. I built and booted core-image-kernel dev with
>>>> the 4.1 changes in place.
>>>
>>> The autobuilder showed up this for an x32 build :/.
>>
>> Can one of the intel folks have a look at this ? I won't be able to get
>> to it until Tuesday at the earliest.
>
> I had a look into this. The issue is that this has been applied:
>
> http://git.yoctoproject.org/cgit.cgi/linux-yocto-3.19/commit/?h=standard/base&id=423e98721e048f6c7b925a75448f6c4ecb2b5b69
>
> but it needs:
>
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=ce793486e23e0162a732c605189c8028e0910e86
>
> and the ioapic driver also appears to need:
>
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/?id=ecf5636dcd59cd5508641f995cc4c2bafedbb995
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/?id=62d1141ff34e35de496ba06491c8e854b23b3f3e
>
>
> which meant I also had to add:
>
> struct resource_win {
> struct resource res; /* In master (CPU) address space */
> resource_size_t offset; /* Translation offset for bridge */
> };
>
> to drivers/acpi/ioapic.c to make it compile which appears to be related to:
>
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a49170b552423a3e85fc4f0d778c707402ee4863
>
> which depends on a number of patches from around that time which change acpi/resource.c:
>
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/drivers/acpi/resource.c
>
> (from 2015/2/3)
>
> At this point I'm out my depth on how you want to fix this but it does
> appear related to the Braswell changes.
>
> To be clear qemux86 and qemux86-64 don't build at all with this series.
> I'll see if I can just drop the Braswell parts.
Gah. It figures. That's of course the issue with any set of BSP ports ..
they get tangled up with Greg's series from time to time.
The changes are all additive, so we can't really drop the braswell parts
unless I revert the whole block of changes.
Drop those -stable updates for now, and I'll see if I can carve out some
time tomorrow to get that config building.
Bruce
>
> Cheers,
>
> Richard
>
^ permalink raw reply [flat|nested] 64+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-02 8:13 ` Martin Jansa
@ 2015-05-03 2:50 ` Bruce Ashfield
2015-05-06 14:42 ` Martin Jansa
0 siblings, 1 reply; 64+ messages in thread
From: Bruce Ashfield @ 2015-05-03 2:50 UTC (permalink / raw)
To: Martin Jansa; +Cc: openembedded-core
On 2015-05-02 4:13 AM, Martin Jansa wrote:
> On Fri, May 01, 2015 at 07:30:24PM -0400, Bruce Ashfield wrote:
>> On 2015-05-01 6:59 PM, Richard Purdie wrote:
>>> On Thu, 2015-04-30 at 21:34 -0400, Bruce Ashfield wrote:
>>>> Here is the latest consolidated pull request for the supported linux-yocto
>>>> kernels.
>>>>
>>>> - We have a refresh of the 3.14-rt support
>>>> - bluetooh configuration changes for common-pc/qemux86
>>>> - braswell BSP features and fixes
>>>> - Introduction of the 4.1-rc1 -dev kernel (and associated perf fix).
>>>> I've built and booted these on my local machines and qemu, and
>>>> everything was sane.
>
> Does it fix the issue I've reported few days ago?
> http://lists.openembedded.org/pipermail/openembedded-core/2015-April/104344.html
Nope. But one config warning is far down on the list when I'm
trying to introduce new -stable's and an entire -dev kernel.
I didn't forget about it, it'll just get done in priority order.
Bruce
>
>>>> The -dev kernel obviously isn't something for deployment yet, but
>>>> it builds, and forms the base for follow up config changes, features
>>>> and development work. I built and booted core-image-kernel dev with
>>>> the 4.1 changes in place.
>>>
>>> The autobuilder showed up this for an x32 build :/.
>>
>> Can one of the intel folks have a look at this ? I won't be able to get
>> to it until Tuesday at the earliest.
>>
>> Bruce
>>
>>>
>>> https://autobuilder.yoctoproject.org/main/builders/nightly-x32/builds/282/steps/BuildImages/logs/stdio
>>>
>>> Cheers,
>>>
>>> Richard
>>>
>>
>> --
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
^ permalink raw reply [flat|nested] 64+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-01 23:30 ` Bruce Ashfield
2015-05-02 8:13 ` Martin Jansa
@ 2015-05-02 9:00 ` Richard Purdie
2015-05-03 2:53 ` Bruce Ashfield
2015-05-03 3:52 ` Bruce Ashfield
1 sibling, 2 replies; 64+ messages in thread
From: Richard Purdie @ 2015-05-02 9:00 UTC (permalink / raw)
To: Bruce Ashfield; +Cc: openembedded-core
On Fri, 2015-05-01 at 19:30 -0400, Bruce Ashfield wrote:
> On 2015-05-01 6:59 PM, Richard Purdie wrote:
> > On Thu, 2015-04-30 at 21:34 -0400, Bruce Ashfield wrote:
> >> Here is the latest consolidated pull request for the supported linux-yocto
> >> kernels.
> >>
> >> - We have a refresh of the 3.14-rt support
> >> - bluetooh configuration changes for common-pc/qemux86
> >> - braswell BSP features and fixes
> >> - Introduction of the 4.1-rc1 -dev kernel (and associated perf fix).
> >>
> >> I've built and booted these on my local machines and qemu, and
> >> everything was sane.
> >>
> >> The -dev kernel obviously isn't something for deployment yet, but
> >> it builds, and forms the base for follow up config changes, features
> >> and development work. I built and booted core-image-kernel dev with
> >> the 4.1 changes in place.
> >
> > The autobuilder showed up this for an x32 build :/.
>
> Can one of the intel folks have a look at this ? I won't be able to get
> to it until Tuesday at the earliest.
I had a look into this. The issue is that this has been applied:
http://git.yoctoproject.org/cgit.cgi/linux-yocto-3.19/commit/?h=standard/base&id=423e98721e048f6c7b925a75448f6c4ecb2b5b69
but it needs:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=ce793486e23e0162a732c605189c8028e0910e86
and the ioapic driver also appears to need:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/?id=ecf5636dcd59cd5508641f995cc4c2bafedbb995
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/?id=62d1141ff34e35de496ba06491c8e854b23b3f3e
which meant I also had to add:
struct resource_win {
struct resource res; /* In master (CPU) address space */
resource_size_t offset; /* Translation offset for bridge */
};
to drivers/acpi/ioapic.c to make it compile which appears to be related to:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a49170b552423a3e85fc4f0d778c707402ee4863
which depends on a number of patches from around that time which change acpi/resource.c:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/drivers/acpi/resource.c
(from 2015/2/3)
At this point I'm out my depth on how you want to fix this but it does
appear related to the Braswell changes.
To be clear qemux86 and qemux86-64 don't build at all with this series.
I'll see if I can just drop the Braswell parts.
Cheers,
Richard
^ permalink raw reply [flat|nested] 64+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-01 23:30 ` Bruce Ashfield
@ 2015-05-02 8:13 ` Martin Jansa
2015-05-03 2:50 ` Bruce Ashfield
2015-05-02 9:00 ` Richard Purdie
1 sibling, 1 reply; 64+ messages in thread
From: Martin Jansa @ 2015-05-02 8:13 UTC (permalink / raw)
To: Bruce Ashfield; +Cc: openembedded-core
On Fri, May 01, 2015 at 07:30:24PM -0400, Bruce Ashfield wrote:
> On 2015-05-01 6:59 PM, Richard Purdie wrote:
> > On Thu, 2015-04-30 at 21:34 -0400, Bruce Ashfield wrote:
> >> Here is the latest consolidated pull request for the supported linux-yocto
> >> kernels.
> >>
> >> - We have a refresh of the 3.14-rt support
> >> - bluetooh configuration changes for common-pc/qemux86
> >> - braswell BSP features and fixes
> >> - Introduction of the 4.1-rc1 -dev kernel (and associated perf fix).
> >> I've built and booted these on my local machines and qemu, and
> >> everything was sane.
Does it fix the issue I've reported few days ago?
http://lists.openembedded.org/pipermail/openembedded-core/2015-April/104344.html
> >> The -dev kernel obviously isn't something for deployment yet, but
> >> it builds, and forms the base for follow up config changes, features
> >> and development work. I built and booted core-image-kernel dev with
> >> the 4.1 changes in place.
> >
> > The autobuilder showed up this for an x32 build :/.
>
> Can one of the intel folks have a look at this ? I won't be able to get
> to it until Tuesday at the earliest.
>
> Bruce
>
> >
> > https://autobuilder.yoctoproject.org/main/builders/nightly-x32/builds/282/steps/BuildImages/logs/stdio
> >
> > Cheers,
> >
> > Richard
> >
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
^ permalink raw reply [flat|nested] 64+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-01 22:59 ` Richard Purdie
@ 2015-05-01 23:30 ` Bruce Ashfield
2015-05-02 8:13 ` Martin Jansa
2015-05-02 9:00 ` Richard Purdie
0 siblings, 2 replies; 64+ messages in thread
From: Bruce Ashfield @ 2015-05-01 23:30 UTC (permalink / raw)
To: Richard Purdie; +Cc: openembedded-core
On 2015-05-01 6:59 PM, Richard Purdie wrote:
> On Thu, 2015-04-30 at 21:34 -0400, Bruce Ashfield wrote:
>> Here is the latest consolidated pull request for the supported linux-yocto
>> kernels.
>>
>> - We have a refresh of the 3.14-rt support
>> - bluetooh configuration changes for common-pc/qemux86
>> - braswell BSP features and fixes
>> - Introduction of the 4.1-rc1 -dev kernel (and associated perf fix).
>>
>> I've built and booted these on my local machines and qemu, and
>> everything was sane.
>>
>> The -dev kernel obviously isn't something for deployment yet, but
>> it builds, and forms the base for follow up config changes, features
>> and development work. I built and booted core-image-kernel dev with
>> the 4.1 changes in place.
>
> The autobuilder showed up this for an x32 build :/.
Can one of the intel folks have a look at this ? I won't be able to get
to it until Tuesday at the earliest.
Bruce
>
> https://autobuilder.yoctoproject.org/main/builders/nightly-x32/builds/282/steps/BuildImages/logs/stdio
>
> Cheers,
>
> Richard
>
^ permalink raw reply [flat|nested] 64+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-01 1:34 Bruce Ashfield
@ 2015-05-01 22:59 ` Richard Purdie
2015-05-01 23:30 ` Bruce Ashfield
2015-05-03 21:30 ` Richard Purdie
1 sibling, 1 reply; 64+ messages in thread
From: Richard Purdie @ 2015-05-01 22:59 UTC (permalink / raw)
To: Bruce Ashfield; +Cc: openembedded-core
On Thu, 2015-04-30 at 21:34 -0400, Bruce Ashfield wrote:
> Here is the latest consolidated pull request for the supported linux-yocto
> kernels.
>
> - We have a refresh of the 3.14-rt support
> - bluetooh configuration changes for common-pc/qemux86
> - braswell BSP features and fixes
> - Introduction of the 4.1-rc1 -dev kernel (and associated perf fix).
>
> I've built and booted these on my local machines and qemu, and
> everything was sane.
>
> The -dev kernel obviously isn't something for deployment yet, but
> it builds, and forms the base for follow up config changes, features
> and development work. I built and booted core-image-kernel dev with
> the 4.1 changes in place.
The autobuilder showed up this for an x32 build :/.
https://autobuilder.yoctoproject.org/main/builders/nightly-x32/builds/282/steps/BuildImages/logs/stdio
Cheers,
Richard
^ permalink raw reply [flat|nested] 64+ messages in thread
* [PATCH 0/5] linux-yocto: consolidated pull request
@ 2015-05-01 1:34 Bruce Ashfield
2015-05-01 22:59 ` Richard Purdie
2015-05-03 21:30 ` Richard Purdie
0 siblings, 2 replies; 64+ messages in thread
From: Bruce Ashfield @ 2015-05-01 1:34 UTC (permalink / raw)
To: richard.purdie; +Cc: openembedded-core
Here is the latest consolidated pull request for the supported linux-yocto
kernels.
- We have a refresh of the 3.14-rt support
- bluetooh configuration changes for common-pc/qemux86
- braswell BSP features and fixes
- Introduction of the 4.1-rc1 -dev kernel (and associated perf fix).
I've built and booted these on my local machines and qemu, and
everything was sane.
The -dev kernel obviously isn't something for deployment yet, but
it builds, and forms the base for follow up config changes, features
and development work. I built and booted core-image-kernel dev with
the 4.1 changes in place.
Cheers,
Bruce
The following changes since commit db409697db2ea0931cdcd2015d089b6b0ea39bbb:
bitbake: bitbake: reset build mtime cache before the build (2015-04-29 10:59:54 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib zedd/kernel
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Bruce Ashfield (5):
linux-yocto/3.14: refresh -rt support
linux-yocto: add core bluetooth support to qemux86* and common-pc*
linux-yocto/3.19: Braswell support and bug fixes
perf: fix build (and feature tests) for 4.1-rcX
linux-yocto-dev: introduce 4.1-rc development kernel
meta/recipes-kernel/linux/linux-yocto-dev.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto-rt_3.14.bb | 6 +++---
meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb | 4 ++--
meta/recipes-kernel/linux/linux-yocto-tiny_3.19.bb | 4 ++--
meta/recipes-kernel/linux/linux-yocto_3.14.bb | 18 +++++++++---------
meta/recipes-kernel/linux/linux-yocto_3.19.bb | 18 +++++++++---------
meta/recipes-kernel/perf/perf.bb | 3 +++
7 files changed, 29 insertions(+), 26 deletions(-)
--
2.1.0
^ permalink raw reply [flat|nested] 64+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-03-25 13:26 ` Bruce Ashfield
@ 2015-03-25 13:52 ` Richard Purdie
0 siblings, 0 replies; 64+ messages in thread
From: Richard Purdie @ 2015-03-25 13:52 UTC (permalink / raw)
To: Bruce Ashfield; +Cc: Patches and discussions about the oe-core layer
On Wed, 2015-03-25 at 09:26 -0400, Bruce Ashfield wrote:
> On Wed, Mar 25, 2015 at 8:13 AM, Bruce Ashfield
> <bruce.ashfield@gmail.com> wrote:
> > On Wed, Mar 25, 2015 at 5:26 AM, Richard Purdie
> > <richard.purdie@linuxfoundation.org> wrote:
> >> On Tue, 2015-03-24 at 14:57 -0400, Bruce Ashfield wrote:
> >>> Hi all,
> >>>
> >>> Here is the latest linux-yocto consolidated pull request. It is a mix of
> >>> kernel version -stable imports (CVEs and fixes), kernel configuration
> >>> changes, a documentation update and kernel configuration enhancement.
> >>>
> >>> The -stable updates are routine, and I build/boot tested them here
> >>> (with my fixup commits being evidence). These are ready for a round of
> >>> autobuilder/soak testing.
> >>
> >> Something in here broke lttng-modules causing cascades of failures on
> >> the autobuilder so I've updated it to the latest code on the 2.6 stable
> >> branch and am retesting.
> >
> > Gah. I built and booted here, but can't think of any reason why that didn't
> > trigger and fail here.
> >
> > I've started my own build as well, with a completely clean starting point.
>
> and sure enough, it blows up on my clean build.
>
> If your update doesn't resolve this, ping me and I'll take care of the fix.
It seemed to work, we've merged everything to master and branched for
the release. Release build now in progress so we'll see... :)
Cheers,
Richard
^ permalink raw reply [flat|nested] 64+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-03-25 12:13 ` Bruce Ashfield
@ 2015-03-25 13:26 ` Bruce Ashfield
2015-03-25 13:52 ` Richard Purdie
0 siblings, 1 reply; 64+ messages in thread
From: Bruce Ashfield @ 2015-03-25 13:26 UTC (permalink / raw)
To: Richard Purdie; +Cc: Patches and discussions about the oe-core layer
On Wed, Mar 25, 2015 at 8:13 AM, Bruce Ashfield
<bruce.ashfield@gmail.com> wrote:
> On Wed, Mar 25, 2015 at 5:26 AM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
>> On Tue, 2015-03-24 at 14:57 -0400, Bruce Ashfield wrote:
>>> Hi all,
>>>
>>> Here is the latest linux-yocto consolidated pull request. It is a mix of
>>> kernel version -stable imports (CVEs and fixes), kernel configuration
>>> changes, a documentation update and kernel configuration enhancement.
>>>
>>> The -stable updates are routine, and I build/boot tested them here
>>> (with my fixup commits being evidence). These are ready for a round of
>>> autobuilder/soak testing.
>>
>> Something in here broke lttng-modules causing cascades of failures on
>> the autobuilder so I've updated it to the latest code on the 2.6 stable
>> branch and am retesting.
>
> Gah. I built and booted here, but can't think of any reason why that didn't
> trigger and fail here.
>
> I've started my own build as well, with a completely clean starting point.
and sure enough, it blows up on my clean build.
If your update doesn't resolve this, ping me and I'll take care of the fix.
Bruce
>
> Bruce
>
>>
>> Cheers,
>>
>> Richard
>>
>> --
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
>
>
> --
> "Thou shalt not follow the NULL pointer, for chaos and madness await
> thee at its end"
--
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
^ permalink raw reply [flat|nested] 64+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-03-25 9:26 ` Richard Purdie
@ 2015-03-25 12:13 ` Bruce Ashfield
2015-03-25 13:26 ` Bruce Ashfield
0 siblings, 1 reply; 64+ messages in thread
From: Bruce Ashfield @ 2015-03-25 12:13 UTC (permalink / raw)
To: Richard Purdie; +Cc: Patches and discussions about the oe-core layer
On Wed, Mar 25, 2015 at 5:26 AM, Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
> On Tue, 2015-03-24 at 14:57 -0400, Bruce Ashfield wrote:
>> Hi all,
>>
>> Here is the latest linux-yocto consolidated pull request. It is a mix of
>> kernel version -stable imports (CVEs and fixes), kernel configuration
>> changes, a documentation update and kernel configuration enhancement.
>>
>> The -stable updates are routine, and I build/boot tested them here
>> (with my fixup commits being evidence). These are ready for a round of
>> autobuilder/soak testing.
>
> Something in here broke lttng-modules causing cascades of failures on
> the autobuilder so I've updated it to the latest code on the 2.6 stable
> branch and am retesting.
Gah. I built and booted here, but can't think of any reason why that didn't
trigger and fail here.
I've started my own build as well, with a completely clean starting point.
Bruce
>
> Cheers,
>
> Richard
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
--
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
^ permalink raw reply [flat|nested] 64+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-03-24 18:57 Bruce Ashfield
@ 2015-03-25 9:26 ` Richard Purdie
2015-03-25 12:13 ` Bruce Ashfield
0 siblings, 1 reply; 64+ messages in thread
From: Richard Purdie @ 2015-03-25 9:26 UTC (permalink / raw)
To: Bruce Ashfield; +Cc: openembedded-core
On Tue, 2015-03-24 at 14:57 -0400, Bruce Ashfield wrote:
> Hi all,
>
> Here is the latest linux-yocto consolidated pull request. It is a mix of
> kernel version -stable imports (CVEs and fixes), kernel configuration
> changes, a documentation update and kernel configuration enhancement.
>
> The -stable updates are routine, and I build/boot tested them here
> (with my fixup commits being evidence). These are ready for a round of
> autobuilder/soak testing.
Something in here broke lttng-modules causing cascades of failures on
the autobuilder so I've updated it to the latest code on the 2.6 stable
branch and am retesting.
Cheers,
Richard
^ permalink raw reply [flat|nested] 64+ messages in thread
* [PATCH 0/5] linux-yocto: consolidated pull request
@ 2015-03-24 18:57 Bruce Ashfield
2015-03-25 9:26 ` Richard Purdie
0 siblings, 1 reply; 64+ messages in thread
From: Bruce Ashfield @ 2015-03-24 18:57 UTC (permalink / raw)
To: richard.purdie; +Cc: openembedded-core
Hi all,
Here is the latest linux-yocto consolidated pull request. It is a mix of
kernel version -stable imports (CVEs and fixes), kernel configuration
changes, a documentation update and kernel configuration enhancement.
The -stable updates are routine, and I build/boot tested them here
(with my fixup commits being evidence). These are ready for a round of
autobuilder/soak testing.
The only other change is the addition of the ability to use a defconfig
that is maintained within a kernel tree. This enhacement request came
from the raspberrypi2 maintainers. We went through a few revisions and
test cycles on this (see YOCTO: 7474 for the details).
The final result has no impact on existing configuration workflows, but
does allow an in-tree config to be copied out into WORKDIR and then
incorporated with other fragments as part of kconfig processing. A new
variable is introduced for specifying the defconfig KBUILD_DEFCONFIG,
and I'll work with Scott to make sure this is documented in the
appropriate locations.
Cheers,
Bruce
The following changes since commit 369932178fe9e7aa4a6d0e2ef1e2e539be701d02:
yocto-bsp: Update templates to 3.19 kernel (2015-03-24 10:06:03 +0000)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib zedd/kernel
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Bruce Ashfield (5):
kernel-yocto: allow in-tree defconfigs
linux-yocto/3.19: configuration updates and stable import
linux-yocto/3.14: integrate korg stable and meta data changes
linux-yocto/3.19: fixes for Intel core warnings
skeleton: clarify linux-yocto-custom workflow
.../recipes-kernel/linux/linux-yocto-custom.bb | 6 ++--
meta/classes/kernel-yocto.bbclass | 39 ++++++++++++++++++++--
meta/recipes-kernel/linux/linux-yocto-rt_3.14.bb | 8 ++---
meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb | 6 ++--
meta/recipes-kernel/linux/linux-yocto-tiny_3.19.bb | 6 ++--
meta/recipes-kernel/linux/linux-yocto_3.14.bb | 20 +++++------
meta/recipes-kernel/linux/linux-yocto_3.19.bb | 20 +++++------
7 files changed, 69 insertions(+), 36 deletions(-)
--
2.1.0
^ permalink raw reply [flat|nested] 64+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2013-08-24 13:50 ` Saul Wold
` (2 preceding siblings ...)
2013-08-24 14:59 ` Bruce Ashfield
@ 2013-08-24 16:05 ` Bruce Ashfield
3 siblings, 0 replies; 64+ messages in thread
From: Bruce Ashfield @ 2013-08-24 16:05 UTC (permalink / raw)
To: Saul Wold; +Cc: openembedded-core
On 13-08-24 9:50 AM, Saul Wold wrote:
> On 08/24/2013 06:45 AM, Bruce Ashfield wrote:
>> On 13-08-24 9:34 AM, Bruce Ashfield wrote:
>>> On 13-08-24 2:33 AM, Saul Wold wrote:
>>>> On 08/23/2013 11:08 AM, Bruce Ashfield wrote:
>>>>> Richard/Saul,
>>>>>
>>>>> Here's my consolidated set of changes that represent the biggest chunk
>>>>> of work for the Yocto 1.5 release. The obvious change is that the 3.10
>>>>> kernel is now the latest linux-yocto kernel (and linux-yocto-dev will
>>>>> mark on). I've built and booted core-image-sato for all the oe-core
>>>>> qemu machines.
>>>>>
>>>>> 3.10 also the latest LTSI and will be updated with that content
>>>>> when it
>>>>> becomes available.
>>>>>
>>>>> Other features of the 3.10 kernel include:
>>>>>
>>>>> - refreshed -rt support
>>>>> - refreshed yaffs2, aufs3
>>>>> - cryptodev
>>>>> - bfs, edf, and OCF staged features
>>>>> - scrubbed and updated meta data for v3.10
>>>>> - improved tools support for meta data updates and queue
>>>>> maintenance
>>>>> - patch carry forward from all previous linux-yocto kernels and
>>>>> configuration.
>>>>>
>>>>> I've also tested linux-yocto-rt and linux-yocto-tiny for the new,
>>>>> shiny tree.
>>>>>
>>>>> I've also bumped the linux-libc-headers to 3.10 and have fixed
>>>>> gst-plugins-good
>>>>> to adapt to a changed #define in the exported headers.
>>>>>
>>>>> Other parts of this update include an uprev of guilt, and in fact, a
>>>>> restoration of "normal" guil operations, since the kernel tree is now
>>>>> manipulated and maintained via a smaller, more contained script. This
>>>>> was necessary for both usability reasons and the fact that all of
>>>>> guilts
>>>>> protections were being removed for the kernel's use .. which makes you
>>>>> ask the quesetion "why use it". It was time for a change.
>>>>>
>>>>> The patches are pretty self explanitory and all contain detailed long
>>>>> logs .. but the summary is:
>>>>>
>>>>> [PATCH 1/5] kern-tools: usability, bug fixes and no guilt
>>>>> [PATCH 2/5] guilt: update to latest git version
>>>>> [PATCH 3/5] linux-libc-headers: update to v3.10
>>>> One of the changes in 3.10 seems to have introduced a conflicting
>>>> definition of ptrace_peeksiginfo_args in linux/ptrace.h
>>>>
>>>>> In file included from ptrace.h:22:0,
>>>>> | from ptrace05.c:38:
>>>>> |
>>>>> /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/linux/ptrace.h:58:8:
>>>>>
>>>>>
>>>>>
>>>>> error: redefinition of 'struct ptrace_peeksiginfo_args'
>>>>> | struct ptrace_peeksiginfo_args {
>>>>> | ^
>>>>> | In file included from ptrace.h:9:0,
>>>>> | from ptrace05.c:38:
>>>>> |
>>>>> /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/sys/ptrace.h:191:8:
>>>>>
>>>>>
>>>>>
>>>>> note: originally defined here
>>>>> | struct ptrace_peeksiginfo_args
>>>>> | ^
>>>>
>>>> This affects ltp, valgrind and strace.
>>>>
>>>> Please check the autobuilder as I am building with this change set and
>>>> expect these failures.
>>>
>>> I'm unfortunately off for the weekend and won't have cycles to look into
>>> any failures until Monday.
>>
>> As it turns out, I may have some time to work on this tonight, since I
>> have to delete the 3.8 yocto recipe and get that patch out.
>>
>> So I've launched a LSB build in the background and will check on it
>> later.
>>
> Just FYI, it might not show up in an LSB build, since those tools
> valgrind, ltp and strace are more Dev tools, so a world build would be
> better.
>
> Also, not sure why but ARM failed to patch 3.8 kernel overnight on the
> AB. (lots of red).
FYI: I've fixed the ARM 3.8 build issue here, it'll be in my series
tonight .. regardless if I'm removing 3.8, it was worth fixing.
Cheers,
Bruce
>
> I just restarted AB with out the 3.10 headers.
>
> Sau!
>
>> If anyone else does get a fix for this, make sure to cc' me on any
>> changes, so I won't spend time trying to fix it a second time! :)
>>
>> Bruce
>>
>>>
>>> So if you want to leave the old headers in place, that's an option.
>>>
>>> I fixed the one issue that I saw with Sato .. but I am after all one
>>> person and can't possibly build and boot all the qemu boards with
>>> all image combinations! This is after all, where I'd expect other
>>> people to help out and fix build issues.
>>>
>>> Cheers,
>>>
>>> Bruce
>>>
>>>>
>>>> Sau!
>>>>
>>>> Sau!
>>>>
>>>>> [PATCH 4/5] gst-plugins-good: fix 3.10 libc-headers build failure
>>>>> [PATCH 5/5] linux-yocto: introduce v3.10
>>>>>
>>>>> ** There is one pending activity. As part of thsi update to 3.10, we
>>>>> want
>>>>> to move to the 3.4 and 3.10 kernel, dropping 3.8 support. But the
>>>>> routerstationpro BSP is still using it as its preferred version. I'm
>>>>> a one man show on this update, and I wasn't able to get the 100+
>>>>> patches
>>>>> ported to 3.10 AND get this update out before the M4 cutoff.
>>>>>
>>>>> ** I'm still attempting to udpate all the reference boards, and
>>>>> once done, I'll send a follow up patch.
>>>>>
>>>>> ** Please test, I've done my best, but things can slip through. We'll
>>>>> work issues in the stabilization period.
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Bruce
>>>>>
>>>>>
>>>>> The following changes since commit
>>>>> 501e1a321d15abd712e3a6ee6ccdb8e21c3d4ea4:
>>>>>
>>>>> bitbake: prserv/serv: Fix pid file removal (2013-08-23 17:43:40
>>>>> +0100)
>>>>>
>>>>> are available in the git repository at:
>>>>>
>>>>> git://git.pokylinux.org/poky-contrib zedd/kernel
>>>>> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
>>>>>
>>>>> Bruce Ashfield (5):
>>>>> kern-tools: usability, bug fixes and no guilt
>>>>> guilt: update to latest git version
>>>>> linux-libc-headers: update to v3.10
>>>>> gst-plugins-good: fix 3.10 libc-headers build failure
>>>>> linux-yocto: introduce v3.10
>>>>>
>>>>> meta/classes/kernel-yocto.bbclass | 2 +
>>>>> meta/conf/distro/include/tcmode-default.inc | 2 +-
>>>>> .../guilt/files/guilt-import-commit.patch | 96 ------
>>>>> meta/recipes-devtools/guilt/files/guilt-init.patch | 25 --
>>>>> meta/recipes-devtools/guilt/files/guilt-pop.patch | 73 -----
>>>>> .../guilt/files/guilt-push-no-series.patch | 29 --
>>>>> meta/recipes-devtools/guilt/files/guilt-push.patch | 42 ---
>>>>> .../guilt/files/guilt-set-git_exec_path.patch | 29 --
>>>>> ...lt-update-supported-git-versions-to-1.8.x.patch | 28 --
>>>>> meta/recipes-devtools/guilt/files/guilt.patch | 319
>>>>> --------------------
>>>>> .../guilt/files/improve_auto_header_gen.patch | 71 -----
>>>>> .../files/make_git_commands_conditional.patch | 48 ---
>>>>> .../guilt/files/optional_head_check.patch | 60 ----
>>>>> .../guilt/files/uninstall_force.patch | 14 -
>>>>> .../{guilt-native_0.33.bb => guilt-native_git.bb} | 21 +-
>>>>> .../kern-tools/kern-tools-native_git.bb | 6 +-
>>>>> .../linux-libc-headers/linux-libc-headers_3.10.bb | 7 +
>>>>> .../linux-libc-headers/linux-libc-headers_3.8.bb | 8 -
>>>>> meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb | 30 ++
>>>>> meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb | 25 ++
>>>>> meta/recipes-kernel/linux/linux-yocto_3.10.bb | 30 ++
>>>>> ...define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch | 45 +++
>>>>> .../gstreamer/gst-plugins-good_0.10.31.bb | 1 +
>>>>> 23 files changed, 150 insertions(+), 861 deletions(-)
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-import-commit.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-init.patch
>>>>> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-pop.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-push-no-series.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-push.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-set-git_exec_path.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-update-supported-git-versions-to-1.8.x.patch
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> delete mode 100644 meta/recipes-devtools/guilt/files/guilt.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/improve_auto_header_gen.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/make_git_commands_conditional.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/optional_head_check.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/uninstall_force.patch
>>>>> rename meta/recipes-devtools/guilt/{guilt-native_0.33.bb =>
>>>>> guilt-native_git.bb} (45%)
>>>>> create mode 100644
>>>>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.10.bb
>>>>> delete mode 100644
>>>>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.8.bb
>>>>> create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb
>>>>> create mode 100644
>>>>> meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb
>>>>> create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.10.bb
>>>>> create mode 100644
>>>>> meta/recipes-multimedia/gstreamer/gst-plugins-good-0.10.31/0001-v4l2_calls-define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>
>>
>>
>>
^ permalink raw reply [flat|nested] 64+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2013-08-24 13:50 ` Saul Wold
2013-08-24 13:53 ` Bruce Ashfield
2013-08-24 14:47 ` Bruce Ashfield
@ 2013-08-24 14:59 ` Bruce Ashfield
2013-08-24 16:05 ` Bruce Ashfield
3 siblings, 0 replies; 64+ messages in thread
From: Bruce Ashfield @ 2013-08-24 14:59 UTC (permalink / raw)
To: Saul Wold; +Cc: openembedded-core
On 13-08-24 9:50 AM, Saul Wold wrote:
> On 08/24/2013 06:45 AM, Bruce Ashfield wrote:
>> On 13-08-24 9:34 AM, Bruce Ashfield wrote:
>>> On 13-08-24 2:33 AM, Saul Wold wrote:
>>>> On 08/23/2013 11:08 AM, Bruce Ashfield wrote:
>>>>> Richard/Saul,
>>>>>
>>>>> Here's my consolidated set of changes that represent the biggest chunk
>>>>> of work for the Yocto 1.5 release. The obvious change is that the 3.10
>>>>> kernel is now the latest linux-yocto kernel (and linux-yocto-dev will
>>>>> mark on). I've built and booted core-image-sato for all the oe-core
>>>>> qemu machines.
>>>>>
>>>>> 3.10 also the latest LTSI and will be updated with that content
>>>>> when it
>>>>> becomes available.
>>>>>
>>>>> Other features of the 3.10 kernel include:
>>>>>
>>>>> - refreshed -rt support
>>>>> - refreshed yaffs2, aufs3
>>>>> - cryptodev
>>>>> - bfs, edf, and OCF staged features
>>>>> - scrubbed and updated meta data for v3.10
>>>>> - improved tools support for meta data updates and queue
>>>>> maintenance
>>>>> - patch carry forward from all previous linux-yocto kernels and
>>>>> configuration.
>>>>>
>>>>> I've also tested linux-yocto-rt and linux-yocto-tiny for the new,
>>>>> shiny tree.
>>>>>
>>>>> I've also bumped the linux-libc-headers to 3.10 and have fixed
>>>>> gst-plugins-good
>>>>> to adapt to a changed #define in the exported headers.
>>>>>
>>>>> Other parts of this update include an uprev of guilt, and in fact, a
>>>>> restoration of "normal" guil operations, since the kernel tree is now
>>>>> manipulated and maintained via a smaller, more contained script. This
>>>>> was necessary for both usability reasons and the fact that all of
>>>>> guilts
>>>>> protections were being removed for the kernel's use .. which makes you
>>>>> ask the quesetion "why use it". It was time for a change.
>>>>>
>>>>> The patches are pretty self explanitory and all contain detailed long
>>>>> logs .. but the summary is:
>>>>>
>>>>> [PATCH 1/5] kern-tools: usability, bug fixes and no guilt
>>>>> [PATCH 2/5] guilt: update to latest git version
>>>>> [PATCH 3/5] linux-libc-headers: update to v3.10
>>>> One of the changes in 3.10 seems to have introduced a conflicting
>>>> definition of ptrace_peeksiginfo_args in linux/ptrace.h
>>>>
>>>>> In file included from ptrace.h:22:0,
>>>>> | from ptrace05.c:38:
>>>>> |
>>>>> /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/linux/ptrace.h:58:8:
>>>>>
>>>>>
>>>>>
>>>>> error: redefinition of 'struct ptrace_peeksiginfo_args'
>>>>> | struct ptrace_peeksiginfo_args {
>>>>> | ^
>>>>> | In file included from ptrace.h:9:0,
>>>>> | from ptrace05.c:38:
>>>>> |
>>>>> /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/sys/ptrace.h:191:8:
>>>>>
>>>>>
>>>>>
>>>>> note: originally defined here
>>>>> | struct ptrace_peeksiginfo_args
>>>>> | ^
>>>>
>>>> This affects ltp, valgrind and strace.
>>>>
>>>> Please check the autobuilder as I am building with this change set and
>>>> expect these failures.
>>>
>>> I'm unfortunately off for the weekend and won't have cycles to look into
>>> any failures until Monday.
>>
>> As it turns out, I may have some time to work on this tonight, since I
>> have to delete the 3.8 yocto recipe and get that patch out.
>>
>> So I've launched a LSB build in the background and will check on it
>> later.
>>
> Just FYI, it might not show up in an LSB build, since those tools
> valgrind, ltp and strace are more Dev tools, so a world build would be
> better.
>
> Also, not sure why but ARM failed to patch 3.8 kernel overnight on the
> AB. (lots of red).
>
> I just restarted AB with out the 3.10 headers.
ok .. this time I'm REALLY going to step away for a few hours.
The mismatch is between the eglibc 2.18 sys/ptrace.h and the kernel's
definition of the structure. I wouldn't really call it a mismatch,
since they are both the same size and field types .. both simply
define it now.
I'm adding Khem: What's the right thing to do here?
I can obviously hack the kernel to remove the definition, but that make
the linux-yocto 3.10 the only kernel that will work against yocto 1.5's
eglibc for building any applications that use ptrace.h.
Falling back to the 3.8 headers will work, but again, we are avoiding
the problem and any end user that does bump to a newer set of libc-headers
will see the problem.
I'll wait for consensus on the approach and add a change if required
into my linux-yocto 3.8 removal patch tonight.
Bruce
>
> Sau!
>
>> If anyone else does get a fix for this, make sure to cc' me on any
>> changes, so I won't spend time trying to fix it a second time! :)
>>
>> Bruce
>>
>>>
>>> So if you want to leave the old headers in place, that's an option.
>>>
>>> I fixed the one issue that I saw with Sato .. but I am after all one
>>> person and can't possibly build and boot all the qemu boards with
>>> all image combinations! This is after all, where I'd expect other
>>> people to help out and fix build issues.
>>>
>>> Cheers,
>>>
>>> Bruce
>>>
>>>>
>>>> Sau!
>>>>
>>>> Sau!
>>>>
>>>>> [PATCH 4/5] gst-plugins-good: fix 3.10 libc-headers build failure
>>>>> [PATCH 5/5] linux-yocto: introduce v3.10
>>>>>
>>>>> ** There is one pending activity. As part of thsi update to 3.10, we
>>>>> want
>>>>> to move to the 3.4 and 3.10 kernel, dropping 3.8 support. But the
>>>>> routerstationpro BSP is still using it as its preferred version. I'm
>>>>> a one man show on this update, and I wasn't able to get the 100+
>>>>> patches
>>>>> ported to 3.10 AND get this update out before the M4 cutoff.
>>>>>
>>>>> ** I'm still attempting to udpate all the reference boards, and
>>>>> once done, I'll send a follow up patch.
>>>>>
>>>>> ** Please test, I've done my best, but things can slip through. We'll
>>>>> work issues in the stabilization period.
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Bruce
>>>>>
>>>>>
>>>>> The following changes since commit
>>>>> 501e1a321d15abd712e3a6ee6ccdb8e21c3d4ea4:
>>>>>
>>>>> bitbake: prserv/serv: Fix pid file removal (2013-08-23 17:43:40
>>>>> +0100)
>>>>>
>>>>> are available in the git repository at:
>>>>>
>>>>> git://git.pokylinux.org/poky-contrib zedd/kernel
>>>>> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
>>>>>
>>>>> Bruce Ashfield (5):
>>>>> kern-tools: usability, bug fixes and no guilt
>>>>> guilt: update to latest git version
>>>>> linux-libc-headers: update to v3.10
>>>>> gst-plugins-good: fix 3.10 libc-headers build failure
>>>>> linux-yocto: introduce v3.10
>>>>>
>>>>> meta/classes/kernel-yocto.bbclass | 2 +
>>>>> meta/conf/distro/include/tcmode-default.inc | 2 +-
>>>>> .../guilt/files/guilt-import-commit.patch | 96 ------
>>>>> meta/recipes-devtools/guilt/files/guilt-init.patch | 25 --
>>>>> meta/recipes-devtools/guilt/files/guilt-pop.patch | 73 -----
>>>>> .../guilt/files/guilt-push-no-series.patch | 29 --
>>>>> meta/recipes-devtools/guilt/files/guilt-push.patch | 42 ---
>>>>> .../guilt/files/guilt-set-git_exec_path.patch | 29 --
>>>>> ...lt-update-supported-git-versions-to-1.8.x.patch | 28 --
>>>>> meta/recipes-devtools/guilt/files/guilt.patch | 319
>>>>> --------------------
>>>>> .../guilt/files/improve_auto_header_gen.patch | 71 -----
>>>>> .../files/make_git_commands_conditional.patch | 48 ---
>>>>> .../guilt/files/optional_head_check.patch | 60 ----
>>>>> .../guilt/files/uninstall_force.patch | 14 -
>>>>> .../{guilt-native_0.33.bb => guilt-native_git.bb} | 21 +-
>>>>> .../kern-tools/kern-tools-native_git.bb | 6 +-
>>>>> .../linux-libc-headers/linux-libc-headers_3.10.bb | 7 +
>>>>> .../linux-libc-headers/linux-libc-headers_3.8.bb | 8 -
>>>>> meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb | 30 ++
>>>>> meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb | 25 ++
>>>>> meta/recipes-kernel/linux/linux-yocto_3.10.bb | 30 ++
>>>>> ...define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch | 45 +++
>>>>> .../gstreamer/gst-plugins-good_0.10.31.bb | 1 +
>>>>> 23 files changed, 150 insertions(+), 861 deletions(-)
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-import-commit.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-init.patch
>>>>> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-pop.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-push-no-series.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-push.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-set-git_exec_path.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-update-supported-git-versions-to-1.8.x.patch
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> delete mode 100644 meta/recipes-devtools/guilt/files/guilt.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/improve_auto_header_gen.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/make_git_commands_conditional.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/optional_head_check.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/uninstall_force.patch
>>>>> rename meta/recipes-devtools/guilt/{guilt-native_0.33.bb =>
>>>>> guilt-native_git.bb} (45%)
>>>>> create mode 100644
>>>>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.10.bb
>>>>> delete mode 100644
>>>>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.8.bb
>>>>> create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb
>>>>> create mode 100644
>>>>> meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb
>>>>> create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.10.bb
>>>>> create mode 100644
>>>>> meta/recipes-multimedia/gstreamer/gst-plugins-good-0.10.31/0001-v4l2_calls-define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>
>>
>>
>>
^ permalink raw reply [flat|nested] 64+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2013-08-24 13:50 ` Saul Wold
2013-08-24 13:53 ` Bruce Ashfield
@ 2013-08-24 14:47 ` Bruce Ashfield
2013-08-24 14:59 ` Bruce Ashfield
2013-08-24 16:05 ` Bruce Ashfield
3 siblings, 0 replies; 64+ messages in thread
From: Bruce Ashfield @ 2013-08-24 14:47 UTC (permalink / raw)
To: Saul Wold; +Cc: openembedded-core
On 13-08-24 9:50 AM, Saul Wold wrote:
> On 08/24/2013 06:45 AM, Bruce Ashfield wrote:
>> On 13-08-24 9:34 AM, Bruce Ashfield wrote:
>>> On 13-08-24 2:33 AM, Saul Wold wrote:
>>>> On 08/23/2013 11:08 AM, Bruce Ashfield wrote:
>>>>> Richard/Saul,
>>>>>
>>>>> Here's my consolidated set of changes that represent the biggest chunk
>>>>> of work for the Yocto 1.5 release. The obvious change is that the 3.10
>>>>> kernel is now the latest linux-yocto kernel (and linux-yocto-dev will
>>>>> mark on). I've built and booted core-image-sato for all the oe-core
>>>>> qemu machines.
>>>>>
>>>>> 3.10 also the latest LTSI and will be updated with that content
>>>>> when it
>>>>> becomes available.
>>>>>
>>>>> Other features of the 3.10 kernel include:
>>>>>
>>>>> - refreshed -rt support
>>>>> - refreshed yaffs2, aufs3
>>>>> - cryptodev
>>>>> - bfs, edf, and OCF staged features
>>>>> - scrubbed and updated meta data for v3.10
>>>>> - improved tools support for meta data updates and queue
>>>>> maintenance
>>>>> - patch carry forward from all previous linux-yocto kernels and
>>>>> configuration.
>>>>>
>>>>> I've also tested linux-yocto-rt and linux-yocto-tiny for the new,
>>>>> shiny tree.
>>>>>
>>>>> I've also bumped the linux-libc-headers to 3.10 and have fixed
>>>>> gst-plugins-good
>>>>> to adapt to a changed #define in the exported headers.
>>>>>
>>>>> Other parts of this update include an uprev of guilt, and in fact, a
>>>>> restoration of "normal" guil operations, since the kernel tree is now
>>>>> manipulated and maintained via a smaller, more contained script. This
>>>>> was necessary for both usability reasons and the fact that all of
>>>>> guilts
>>>>> protections were being removed for the kernel's use .. which makes you
>>>>> ask the quesetion "why use it". It was time for a change.
>>>>>
>>>>> The patches are pretty self explanitory and all contain detailed long
>>>>> logs .. but the summary is:
>>>>>
>>>>> [PATCH 1/5] kern-tools: usability, bug fixes and no guilt
>>>>> [PATCH 2/5] guilt: update to latest git version
>>>>> [PATCH 3/5] linux-libc-headers: update to v3.10
>>>> One of the changes in 3.10 seems to have introduced a conflicting
>>>> definition of ptrace_peeksiginfo_args in linux/ptrace.h
>>>>
>>>>> In file included from ptrace.h:22:0,
>>>>> | from ptrace05.c:38:
>>>>> |
>>>>> /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/linux/ptrace.h:58:8:
>>>>>
>>>>>
>>>>>
>>>>> error: redefinition of 'struct ptrace_peeksiginfo_args'
>>>>> | struct ptrace_peeksiginfo_args {
>>>>> | ^
>>>>> | In file included from ptrace.h:9:0,
>>>>> | from ptrace05.c:38:
>>>>> |
>>>>> /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/sys/ptrace.h:191:8:
>>>>>
>>>>>
>>>>>
>>>>> note: originally defined here
>>>>> | struct ptrace_peeksiginfo_args
>>>>> | ^
>>>>
>>>> This affects ltp, valgrind and strace.
>>>>
>>>> Please check the autobuilder as I am building with this change set and
>>>> expect these failures.
>>>
>>> I'm unfortunately off for the weekend and won't have cycles to look into
>>> any failures until Monday.
>>
>> As it turns out, I may have some time to work on this tonight, since I
>> have to delete the 3.8 yocto recipe and get that patch out.
>>
>> So I've launched a LSB build in the background and will check on it
>> later.
>>
> Just FYI, it might not show up in an LSB build, since those tools
> valgrind, ltp and strace are more Dev tools, so a world build would be
> better.
I reproduced the failure here via adding ptrace to my image install.
The kernel change happened in april, and the good news is that the
structure is still exactly the same size, with the same fields. So the
userspace ABI is unchanged.
I'll hunt down the conflict and adjust the packages, since that kernel
header change will be there to stay.
Has anyone checked to see if the upstream version of those packages have
already adapted to the change ? I'll do that tonight when I'm back, if
no one else has.
Cheers,
Bruce
>
> Also, not sure why but ARM failed to patch 3.8 kernel overnight on the
> AB. (lots of red).
>
> I just restarted AB with out the 3.10 headers.
>
> Sau!
>
>> If anyone else does get a fix for this, make sure to cc' me on any
>> changes, so I won't spend time trying to fix it a second time! :)
>>
>> Bruce
>>
>>>
>>> So if you want to leave the old headers in place, that's an option.
>>>
>>> I fixed the one issue that I saw with Sato .. but I am after all one
>>> person and can't possibly build and boot all the qemu boards with
>>> all image combinations! This is after all, where I'd expect other
>>> people to help out and fix build issues.
>>>
>>> Cheers,
>>>
>>> Bruce
>>>
>>>>
>>>> Sau!
>>>>
>>>> Sau!
>>>>
>>>>> [PATCH 4/5] gst-plugins-good: fix 3.10 libc-headers build failure
>>>>> [PATCH 5/5] linux-yocto: introduce v3.10
>>>>>
>>>>> ** There is one pending activity. As part of thsi update to 3.10, we
>>>>> want
>>>>> to move to the 3.4 and 3.10 kernel, dropping 3.8 support. But the
>>>>> routerstationpro BSP is still using it as its preferred version. I'm
>>>>> a one man show on this update, and I wasn't able to get the 100+
>>>>> patches
>>>>> ported to 3.10 AND get this update out before the M4 cutoff.
>>>>>
>>>>> ** I'm still attempting to udpate all the reference boards, and
>>>>> once done, I'll send a follow up patch.
>>>>>
>>>>> ** Please test, I've done my best, but things can slip through. We'll
>>>>> work issues in the stabilization period.
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Bruce
>>>>>
>>>>>
>>>>> The following changes since commit
>>>>> 501e1a321d15abd712e3a6ee6ccdb8e21c3d4ea4:
>>>>>
>>>>> bitbake: prserv/serv: Fix pid file removal (2013-08-23 17:43:40
>>>>> +0100)
>>>>>
>>>>> are available in the git repository at:
>>>>>
>>>>> git://git.pokylinux.org/poky-contrib zedd/kernel
>>>>> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
>>>>>
>>>>> Bruce Ashfield (5):
>>>>> kern-tools: usability, bug fixes and no guilt
>>>>> guilt: update to latest git version
>>>>> linux-libc-headers: update to v3.10
>>>>> gst-plugins-good: fix 3.10 libc-headers build failure
>>>>> linux-yocto: introduce v3.10
>>>>>
>>>>> meta/classes/kernel-yocto.bbclass | 2 +
>>>>> meta/conf/distro/include/tcmode-default.inc | 2 +-
>>>>> .../guilt/files/guilt-import-commit.patch | 96 ------
>>>>> meta/recipes-devtools/guilt/files/guilt-init.patch | 25 --
>>>>> meta/recipes-devtools/guilt/files/guilt-pop.patch | 73 -----
>>>>> .../guilt/files/guilt-push-no-series.patch | 29 --
>>>>> meta/recipes-devtools/guilt/files/guilt-push.patch | 42 ---
>>>>> .../guilt/files/guilt-set-git_exec_path.patch | 29 --
>>>>> ...lt-update-supported-git-versions-to-1.8.x.patch | 28 --
>>>>> meta/recipes-devtools/guilt/files/guilt.patch | 319
>>>>> --------------------
>>>>> .../guilt/files/improve_auto_header_gen.patch | 71 -----
>>>>> .../files/make_git_commands_conditional.patch | 48 ---
>>>>> .../guilt/files/optional_head_check.patch | 60 ----
>>>>> .../guilt/files/uninstall_force.patch | 14 -
>>>>> .../{guilt-native_0.33.bb => guilt-native_git.bb} | 21 +-
>>>>> .../kern-tools/kern-tools-native_git.bb | 6 +-
>>>>> .../linux-libc-headers/linux-libc-headers_3.10.bb | 7 +
>>>>> .../linux-libc-headers/linux-libc-headers_3.8.bb | 8 -
>>>>> meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb | 30 ++
>>>>> meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb | 25 ++
>>>>> meta/recipes-kernel/linux/linux-yocto_3.10.bb | 30 ++
>>>>> ...define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch | 45 +++
>>>>> .../gstreamer/gst-plugins-good_0.10.31.bb | 1 +
>>>>> 23 files changed, 150 insertions(+), 861 deletions(-)
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-import-commit.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-init.patch
>>>>> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-pop.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-push-no-series.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-push.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-set-git_exec_path.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-update-supported-git-versions-to-1.8.x.patch
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> delete mode 100644 meta/recipes-devtools/guilt/files/guilt.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/improve_auto_header_gen.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/make_git_commands_conditional.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/optional_head_check.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/uninstall_force.patch
>>>>> rename meta/recipes-devtools/guilt/{guilt-native_0.33.bb =>
>>>>> guilt-native_git.bb} (45%)
>>>>> create mode 100644
>>>>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.10.bb
>>>>> delete mode 100644
>>>>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.8.bb
>>>>> create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb
>>>>> create mode 100644
>>>>> meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb
>>>>> create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.10.bb
>>>>> create mode 100644
>>>>> meta/recipes-multimedia/gstreamer/gst-plugins-good-0.10.31/0001-v4l2_calls-define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>
>>
>>
>>
^ permalink raw reply [flat|nested] 64+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2013-08-24 13:50 ` Saul Wold
@ 2013-08-24 13:53 ` Bruce Ashfield
2013-08-24 14:47 ` Bruce Ashfield
` (2 subsequent siblings)
3 siblings, 0 replies; 64+ messages in thread
From: Bruce Ashfield @ 2013-08-24 13:53 UTC (permalink / raw)
To: Saul Wold; +Cc: openembedded-core
On 13-08-24 9:50 AM, Saul Wold wrote:
> On 08/24/2013 06:45 AM, Bruce Ashfield wrote:
>> On 13-08-24 9:34 AM, Bruce Ashfield wrote:
>>> On 13-08-24 2:33 AM, Saul Wold wrote:
>>>> On 08/23/2013 11:08 AM, Bruce Ashfield wrote:
>>>>> Richard/Saul,
>>>>>
>>>>> Here's my consolidated set of changes that represent the biggest chunk
>>>>> of work for the Yocto 1.5 release. The obvious change is that the 3.10
>>>>> kernel is now the latest linux-yocto kernel (and linux-yocto-dev will
>>>>> mark on). I've built and booted core-image-sato for all the oe-core
>>>>> qemu machines.
>>>>>
>>>>> 3.10 also the latest LTSI and will be updated with that content
>>>>> when it
>>>>> becomes available.
>>>>>
>>>>> Other features of the 3.10 kernel include:
>>>>>
>>>>> - refreshed -rt support
>>>>> - refreshed yaffs2, aufs3
>>>>> - cryptodev
>>>>> - bfs, edf, and OCF staged features
>>>>> - scrubbed and updated meta data for v3.10
>>>>> - improved tools support for meta data updates and queue
>>>>> maintenance
>>>>> - patch carry forward from all previous linux-yocto kernels and
>>>>> configuration.
>>>>>
>>>>> I've also tested linux-yocto-rt and linux-yocto-tiny for the new,
>>>>> shiny tree.
>>>>>
>>>>> I've also bumped the linux-libc-headers to 3.10 and have fixed
>>>>> gst-plugins-good
>>>>> to adapt to a changed #define in the exported headers.
>>>>>
>>>>> Other parts of this update include an uprev of guilt, and in fact, a
>>>>> restoration of "normal" guil operations, since the kernel tree is now
>>>>> manipulated and maintained via a smaller, more contained script. This
>>>>> was necessary for both usability reasons and the fact that all of
>>>>> guilts
>>>>> protections were being removed for the kernel's use .. which makes you
>>>>> ask the quesetion "why use it". It was time for a change.
>>>>>
>>>>> The patches are pretty self explanitory and all contain detailed long
>>>>> logs .. but the summary is:
>>>>>
>>>>> [PATCH 1/5] kern-tools: usability, bug fixes and no guilt
>>>>> [PATCH 2/5] guilt: update to latest git version
>>>>> [PATCH 3/5] linux-libc-headers: update to v3.10
>>>> One of the changes in 3.10 seems to have introduced a conflicting
>>>> definition of ptrace_peeksiginfo_args in linux/ptrace.h
>>>>
>>>>> In file included from ptrace.h:22:0,
>>>>> | from ptrace05.c:38:
>>>>> |
>>>>> /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/linux/ptrace.h:58:8:
>>>>>
>>>>>
>>>>>
>>>>> error: redefinition of 'struct ptrace_peeksiginfo_args'
>>>>> | struct ptrace_peeksiginfo_args {
>>>>> | ^
>>>>> | In file included from ptrace.h:9:0,
>>>>> | from ptrace05.c:38:
>>>>> |
>>>>> /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/sys/ptrace.h:191:8:
>>>>>
>>>>>
>>>>>
>>>>> note: originally defined here
>>>>> | struct ptrace_peeksiginfo_args
>>>>> | ^
>>>>
>>>> This affects ltp, valgrind and strace.
>>>>
>>>> Please check the autobuilder as I am building with this change set and
>>>> expect these failures.
>>>
>>> I'm unfortunately off for the weekend and won't have cycles to look into
>>> any failures until Monday.
>>
>> As it turns out, I may have some time to work on this tonight, since I
>> have to delete the 3.8 yocto recipe and get that patch out.
>>
>> So I've launched a LSB build in the background and will check on it
>> later.
>>
> Just FYI, it might not show up in an LSB build, since those tools
> valgrind, ltp and strace are more Dev tools, so a world build would be
> better.
Ah ok. I'll explicitly add dependencies on them here and restart
my sato build.
I'm a bit surprised that it failed, since user apis are a huge no-no
to change.
>
> Also, not sure why but ARM failed to patch 3.8 kernel overnight on the
> AB. (lots of red).
probably because I didn't look at 3.8 ... since my plan was to delete
it!
I'll follow up with a fix for that tonight, if I can see the failure
here. Always fun!! :)
Leave that one with me. Do you have a link to the failure ?
Bruce
>
> I just restarted AB with out the 3.10 headers.
>
> Sau!
>
>> If anyone else does get a fix for this, make sure to cc' me on any
>> changes, so I won't spend time trying to fix it a second time! :)
>>
>> Bruce
>>
>>>
>>> So if you want to leave the old headers in place, that's an option.
>>>
>>> I fixed the one issue that I saw with Sato .. but I am after all one
>>> person and can't possibly build and boot all the qemu boards with
>>> all image combinations! This is after all, where I'd expect other
>>> people to help out and fix build issues.
>>>
>>> Cheers,
>>>
>>> Bruce
>>>
>>>>
>>>> Sau!
>>>>
>>>> Sau!
>>>>
>>>>> [PATCH 4/5] gst-plugins-good: fix 3.10 libc-headers build failure
>>>>> [PATCH 5/5] linux-yocto: introduce v3.10
>>>>>
>>>>> ** There is one pending activity. As part of thsi update to 3.10, we
>>>>> want
>>>>> to move to the 3.4 and 3.10 kernel, dropping 3.8 support. But the
>>>>> routerstationpro BSP is still using it as its preferred version. I'm
>>>>> a one man show on this update, and I wasn't able to get the 100+
>>>>> patches
>>>>> ported to 3.10 AND get this update out before the M4 cutoff.
>>>>>
>>>>> ** I'm still attempting to udpate all the reference boards, and
>>>>> once done, I'll send a follow up patch.
>>>>>
>>>>> ** Please test, I've done my best, but things can slip through. We'll
>>>>> work issues in the stabilization period.
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Bruce
>>>>>
>>>>>
>>>>> The following changes since commit
>>>>> 501e1a321d15abd712e3a6ee6ccdb8e21c3d4ea4:
>>>>>
>>>>> bitbake: prserv/serv: Fix pid file removal (2013-08-23 17:43:40
>>>>> +0100)
>>>>>
>>>>> are available in the git repository at:
>>>>>
>>>>> git://git.pokylinux.org/poky-contrib zedd/kernel
>>>>> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
>>>>>
>>>>> Bruce Ashfield (5):
>>>>> kern-tools: usability, bug fixes and no guilt
>>>>> guilt: update to latest git version
>>>>> linux-libc-headers: update to v3.10
>>>>> gst-plugins-good: fix 3.10 libc-headers build failure
>>>>> linux-yocto: introduce v3.10
>>>>>
>>>>> meta/classes/kernel-yocto.bbclass | 2 +
>>>>> meta/conf/distro/include/tcmode-default.inc | 2 +-
>>>>> .../guilt/files/guilt-import-commit.patch | 96 ------
>>>>> meta/recipes-devtools/guilt/files/guilt-init.patch | 25 --
>>>>> meta/recipes-devtools/guilt/files/guilt-pop.patch | 73 -----
>>>>> .../guilt/files/guilt-push-no-series.patch | 29 --
>>>>> meta/recipes-devtools/guilt/files/guilt-push.patch | 42 ---
>>>>> .../guilt/files/guilt-set-git_exec_path.patch | 29 --
>>>>> ...lt-update-supported-git-versions-to-1.8.x.patch | 28 --
>>>>> meta/recipes-devtools/guilt/files/guilt.patch | 319
>>>>> --------------------
>>>>> .../guilt/files/improve_auto_header_gen.patch | 71 -----
>>>>> .../files/make_git_commands_conditional.patch | 48 ---
>>>>> .../guilt/files/optional_head_check.patch | 60 ----
>>>>> .../guilt/files/uninstall_force.patch | 14 -
>>>>> .../{guilt-native_0.33.bb => guilt-native_git.bb} | 21 +-
>>>>> .../kern-tools/kern-tools-native_git.bb | 6 +-
>>>>> .../linux-libc-headers/linux-libc-headers_3.10.bb | 7 +
>>>>> .../linux-libc-headers/linux-libc-headers_3.8.bb | 8 -
>>>>> meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb | 30 ++
>>>>> meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb | 25 ++
>>>>> meta/recipes-kernel/linux/linux-yocto_3.10.bb | 30 ++
>>>>> ...define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch | 45 +++
>>>>> .../gstreamer/gst-plugins-good_0.10.31.bb | 1 +
>>>>> 23 files changed, 150 insertions(+), 861 deletions(-)
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-import-commit.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-init.patch
>>>>> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-pop.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-push-no-series.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-push.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-set-git_exec_path.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-update-supported-git-versions-to-1.8.x.patch
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> delete mode 100644 meta/recipes-devtools/guilt/files/guilt.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/improve_auto_header_gen.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/make_git_commands_conditional.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/optional_head_check.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/uninstall_force.patch
>>>>> rename meta/recipes-devtools/guilt/{guilt-native_0.33.bb =>
>>>>> guilt-native_git.bb} (45%)
>>>>> create mode 100644
>>>>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.10.bb
>>>>> delete mode 100644
>>>>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.8.bb
>>>>> create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb
>>>>> create mode 100644
>>>>> meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb
>>>>> create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.10.bb
>>>>> create mode 100644
>>>>> meta/recipes-multimedia/gstreamer/gst-plugins-good-0.10.31/0001-v4l2_calls-define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>
>>
>>
>>
^ permalink raw reply [flat|nested] 64+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2013-08-24 13:45 ` Bruce Ashfield
@ 2013-08-24 13:50 ` Saul Wold
2013-08-24 13:53 ` Bruce Ashfield
` (3 more replies)
0 siblings, 4 replies; 64+ messages in thread
From: Saul Wold @ 2013-08-24 13:50 UTC (permalink / raw)
To: Bruce Ashfield; +Cc: openembedded-core
On 08/24/2013 06:45 AM, Bruce Ashfield wrote:
> On 13-08-24 9:34 AM, Bruce Ashfield wrote:
>> On 13-08-24 2:33 AM, Saul Wold wrote:
>>> On 08/23/2013 11:08 AM, Bruce Ashfield wrote:
>>>> Richard/Saul,
>>>>
>>>> Here's my consolidated set of changes that represent the biggest chunk
>>>> of work for the Yocto 1.5 release. The obvious change is that the 3.10
>>>> kernel is now the latest linux-yocto kernel (and linux-yocto-dev will
>>>> mark on). I've built and booted core-image-sato for all the oe-core
>>>> qemu machines.
>>>>
>>>> 3.10 also the latest LTSI and will be updated with that content when it
>>>> becomes available.
>>>>
>>>> Other features of the 3.10 kernel include:
>>>>
>>>> - refreshed -rt support
>>>> - refreshed yaffs2, aufs3
>>>> - cryptodev
>>>> - bfs, edf, and OCF staged features
>>>> - scrubbed and updated meta data for v3.10
>>>> - improved tools support for meta data updates and queue maintenance
>>>> - patch carry forward from all previous linux-yocto kernels and
>>>> configuration.
>>>>
>>>> I've also tested linux-yocto-rt and linux-yocto-tiny for the new,
>>>> shiny tree.
>>>>
>>>> I've also bumped the linux-libc-headers to 3.10 and have fixed
>>>> gst-plugins-good
>>>> to adapt to a changed #define in the exported headers.
>>>>
>>>> Other parts of this update include an uprev of guilt, and in fact, a
>>>> restoration of "normal" guil operations, since the kernel tree is now
>>>> manipulated and maintained via a smaller, more contained script. This
>>>> was necessary for both usability reasons and the fact that all of
>>>> guilts
>>>> protections were being removed for the kernel's use .. which makes you
>>>> ask the quesetion "why use it". It was time for a change.
>>>>
>>>> The patches are pretty self explanitory and all contain detailed long
>>>> logs .. but the summary is:
>>>>
>>>> [PATCH 1/5] kern-tools: usability, bug fixes and no guilt
>>>> [PATCH 2/5] guilt: update to latest git version
>>>> [PATCH 3/5] linux-libc-headers: update to v3.10
>>> One of the changes in 3.10 seems to have introduced a conflicting
>>> definition of ptrace_peeksiginfo_args in linux/ptrace.h
>>>
>>>> In file included from ptrace.h:22:0,
>>>> | from ptrace05.c:38:
>>>> |
>>>> /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/linux/ptrace.h:58:8:
>>>>
>>>>
>>>> error: redefinition of 'struct ptrace_peeksiginfo_args'
>>>> | struct ptrace_peeksiginfo_args {
>>>> | ^
>>>> | In file included from ptrace.h:9:0,
>>>> | from ptrace05.c:38:
>>>> |
>>>> /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/sys/ptrace.h:191:8:
>>>>
>>>>
>>>> note: originally defined here
>>>> | struct ptrace_peeksiginfo_args
>>>> | ^
>>>
>>> This affects ltp, valgrind and strace.
>>>
>>> Please check the autobuilder as I am building with this change set and
>>> expect these failures.
>>
>> I'm unfortunately off for the weekend and won't have cycles to look into
>> any failures until Monday.
>
> As it turns out, I may have some time to work on this tonight, since I
> have to delete the 3.8 yocto recipe and get that patch out.
>
> So I've launched a LSB build in the background and will check on it
> later.
>
Just FYI, it might not show up in an LSB build, since those tools
valgrind, ltp and strace are more Dev tools, so a world build would be
better.
Also, not sure why but ARM failed to patch 3.8 kernel overnight on the
AB. (lots of red).
I just restarted AB with out the 3.10 headers.
Sau!
> If anyone else does get a fix for this, make sure to cc' me on any
> changes, so I won't spend time trying to fix it a second time! :)
>
> Bruce
>
>>
>> So if you want to leave the old headers in place, that's an option.
>>
>> I fixed the one issue that I saw with Sato .. but I am after all one
>> person and can't possibly build and boot all the qemu boards with
>> all image combinations! This is after all, where I'd expect other
>> people to help out and fix build issues.
>>
>> Cheers,
>>
>> Bruce
>>
>>>
>>> Sau!
>>>
>>> Sau!
>>>
>>>> [PATCH 4/5] gst-plugins-good: fix 3.10 libc-headers build failure
>>>> [PATCH 5/5] linux-yocto: introduce v3.10
>>>>
>>>> ** There is one pending activity. As part of thsi update to 3.10, we
>>>> want
>>>> to move to the 3.4 and 3.10 kernel, dropping 3.8 support. But the
>>>> routerstationpro BSP is still using it as its preferred version. I'm
>>>> a one man show on this update, and I wasn't able to get the 100+
>>>> patches
>>>> ported to 3.10 AND get this update out before the M4 cutoff.
>>>>
>>>> ** I'm still attempting to udpate all the reference boards, and
>>>> once done, I'll send a follow up patch.
>>>>
>>>> ** Please test, I've done my best, but things can slip through. We'll
>>>> work issues in the stabilization period.
>>>>
>>>> Cheers,
>>>>
>>>> Bruce
>>>>
>>>>
>>>> The following changes since commit
>>>> 501e1a321d15abd712e3a6ee6ccdb8e21c3d4ea4:
>>>>
>>>> bitbake: prserv/serv: Fix pid file removal (2013-08-23 17:43:40
>>>> +0100)
>>>>
>>>> are available in the git repository at:
>>>>
>>>> git://git.pokylinux.org/poky-contrib zedd/kernel
>>>> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
>>>>
>>>> Bruce Ashfield (5):
>>>> kern-tools: usability, bug fixes and no guilt
>>>> guilt: update to latest git version
>>>> linux-libc-headers: update to v3.10
>>>> gst-plugins-good: fix 3.10 libc-headers build failure
>>>> linux-yocto: introduce v3.10
>>>>
>>>> meta/classes/kernel-yocto.bbclass | 2 +
>>>> meta/conf/distro/include/tcmode-default.inc | 2 +-
>>>> .../guilt/files/guilt-import-commit.patch | 96 ------
>>>> meta/recipes-devtools/guilt/files/guilt-init.patch | 25 --
>>>> meta/recipes-devtools/guilt/files/guilt-pop.patch | 73 -----
>>>> .../guilt/files/guilt-push-no-series.patch | 29 --
>>>> meta/recipes-devtools/guilt/files/guilt-push.patch | 42 ---
>>>> .../guilt/files/guilt-set-git_exec_path.patch | 29 --
>>>> ...lt-update-supported-git-versions-to-1.8.x.patch | 28 --
>>>> meta/recipes-devtools/guilt/files/guilt.patch | 319
>>>> --------------------
>>>> .../guilt/files/improve_auto_header_gen.patch | 71 -----
>>>> .../files/make_git_commands_conditional.patch | 48 ---
>>>> .../guilt/files/optional_head_check.patch | 60 ----
>>>> .../guilt/files/uninstall_force.patch | 14 -
>>>> .../{guilt-native_0.33.bb => guilt-native_git.bb} | 21 +-
>>>> .../kern-tools/kern-tools-native_git.bb | 6 +-
>>>> .../linux-libc-headers/linux-libc-headers_3.10.bb | 7 +
>>>> .../linux-libc-headers/linux-libc-headers_3.8.bb | 8 -
>>>> meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb | 30 ++
>>>> meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb | 25 ++
>>>> meta/recipes-kernel/linux/linux-yocto_3.10.bb | 30 ++
>>>> ...define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch | 45 +++
>>>> .../gstreamer/gst-plugins-good_0.10.31.bb | 1 +
>>>> 23 files changed, 150 insertions(+), 861 deletions(-)
>>>> delete mode 100644
>>>> meta/recipes-devtools/guilt/files/guilt-import-commit.patch
>>>> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-init.patch
>>>> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-pop.patch
>>>> delete mode 100644
>>>> meta/recipes-devtools/guilt/files/guilt-push-no-series.patch
>>>> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-push.patch
>>>> delete mode 100644
>>>> meta/recipes-devtools/guilt/files/guilt-set-git_exec_path.patch
>>>> delete mode 100644
>>>> meta/recipes-devtools/guilt/files/guilt-update-supported-git-versions-to-1.8.x.patch
>>>>
>>>>
>>>>
>>>> delete mode 100644 meta/recipes-devtools/guilt/files/guilt.patch
>>>> delete mode 100644
>>>> meta/recipes-devtools/guilt/files/improve_auto_header_gen.patch
>>>> delete mode 100644
>>>> meta/recipes-devtools/guilt/files/make_git_commands_conditional.patch
>>>> delete mode 100644
>>>> meta/recipes-devtools/guilt/files/optional_head_check.patch
>>>> delete mode 100644
>>>> meta/recipes-devtools/guilt/files/uninstall_force.patch
>>>> rename meta/recipes-devtools/guilt/{guilt-native_0.33.bb =>
>>>> guilt-native_git.bb} (45%)
>>>> create mode 100644
>>>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.10.bb
>>>> delete mode 100644
>>>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.8.bb
>>>> create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb
>>>> create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb
>>>> create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.10.bb
>>>> create mode 100644
>>>> meta/recipes-multimedia/gstreamer/gst-plugins-good-0.10.31/0001-v4l2_calls-define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch
>>>>
>>>>
>>>>
>>>>
>>
>
>
>
^ permalink raw reply [flat|nested] 64+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2013-08-24 13:34 ` Bruce Ashfield
@ 2013-08-24 13:45 ` Bruce Ashfield
2013-08-24 13:50 ` Saul Wold
0 siblings, 1 reply; 64+ messages in thread
From: Bruce Ashfield @ 2013-08-24 13:45 UTC (permalink / raw)
To: Saul Wold; +Cc: openembedded-core
On 13-08-24 9:34 AM, Bruce Ashfield wrote:
> On 13-08-24 2:33 AM, Saul Wold wrote:
>> On 08/23/2013 11:08 AM, Bruce Ashfield wrote:
>>> Richard/Saul,
>>>
>>> Here's my consolidated set of changes that represent the biggest chunk
>>> of work for the Yocto 1.5 release. The obvious change is that the 3.10
>>> kernel is now the latest linux-yocto kernel (and linux-yocto-dev will
>>> mark on). I've built and booted core-image-sato for all the oe-core
>>> qemu machines.
>>>
>>> 3.10 also the latest LTSI and will be updated with that content when it
>>> becomes available.
>>>
>>> Other features of the 3.10 kernel include:
>>>
>>> - refreshed -rt support
>>> - refreshed yaffs2, aufs3
>>> - cryptodev
>>> - bfs, edf, and OCF staged features
>>> - scrubbed and updated meta data for v3.10
>>> - improved tools support for meta data updates and queue maintenance
>>> - patch carry forward from all previous linux-yocto kernels and
>>> configuration.
>>>
>>> I've also tested linux-yocto-rt and linux-yocto-tiny for the new,
>>> shiny tree.
>>>
>>> I've also bumped the linux-libc-headers to 3.10 and have fixed
>>> gst-plugins-good
>>> to adapt to a changed #define in the exported headers.
>>>
>>> Other parts of this update include an uprev of guilt, and in fact, a
>>> restoration of "normal" guil operations, since the kernel tree is now
>>> manipulated and maintained via a smaller, more contained script. This
>>> was necessary for both usability reasons and the fact that all of guilts
>>> protections were being removed for the kernel's use .. which makes you
>>> ask the quesetion "why use it". It was time for a change.
>>>
>>> The patches are pretty self explanitory and all contain detailed long
>>> logs .. but the summary is:
>>>
>>> [PATCH 1/5] kern-tools: usability, bug fixes and no guilt
>>> [PATCH 2/5] guilt: update to latest git version
>>> [PATCH 3/5] linux-libc-headers: update to v3.10
>> One of the changes in 3.10 seems to have introduced a conflicting
>> definition of ptrace_peeksiginfo_args in linux/ptrace.h
>>
>>> In file included from ptrace.h:22:0,
>>> | from ptrace05.c:38:
>>> |
>>> /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/linux/ptrace.h:58:8:
>>>
>>> error: redefinition of 'struct ptrace_peeksiginfo_args'
>>> | struct ptrace_peeksiginfo_args {
>>> | ^
>>> | In file included from ptrace.h:9:0,
>>> | from ptrace05.c:38:
>>> |
>>> /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/sys/ptrace.h:191:8:
>>>
>>> note: originally defined here
>>> | struct ptrace_peeksiginfo_args
>>> | ^
>>
>> This affects ltp, valgrind and strace.
>>
>> Please check the autobuilder as I am building with this change set and
>> expect these failures.
>
> I'm unfortunately off for the weekend and won't have cycles to look into
> any failures until Monday.
As it turns out, I may have some time to work on this tonight, since I
have to delete the 3.8 yocto recipe and get that patch out.
So I've launched a LSB build in the background and will check on it
later.
If anyone else does get a fix for this, make sure to cc' me on any
changes, so I won't spend time trying to fix it a second time! :)
Bruce
>
> So if you want to leave the old headers in place, that's an option.
>
> I fixed the one issue that I saw with Sato .. but I am after all one
> person and can't possibly build and boot all the qemu boards with
> all image combinations! This is after all, where I'd expect other
> people to help out and fix build issues.
>
> Cheers,
>
> Bruce
>
>>
>> Sau!
>>
>> Sau!
>>
>>> [PATCH 4/5] gst-plugins-good: fix 3.10 libc-headers build failure
>>> [PATCH 5/5] linux-yocto: introduce v3.10
>>>
>>> ** There is one pending activity. As part of thsi update to 3.10, we
>>> want
>>> to move to the 3.4 and 3.10 kernel, dropping 3.8 support. But the
>>> routerstationpro BSP is still using it as its preferred version. I'm
>>> a one man show on this update, and I wasn't able to get the 100+ patches
>>> ported to 3.10 AND get this update out before the M4 cutoff.
>>>
>>> ** I'm still attempting to udpate all the reference boards, and
>>> once done, I'll send a follow up patch.
>>>
>>> ** Please test, I've done my best, but things can slip through. We'll
>>> work issues in the stabilization period.
>>>
>>> Cheers,
>>>
>>> Bruce
>>>
>>>
>>> The following changes since commit
>>> 501e1a321d15abd712e3a6ee6ccdb8e21c3d4ea4:
>>>
>>> bitbake: prserv/serv: Fix pid file removal (2013-08-23 17:43:40
>>> +0100)
>>>
>>> are available in the git repository at:
>>>
>>> git://git.pokylinux.org/poky-contrib zedd/kernel
>>> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
>>>
>>> Bruce Ashfield (5):
>>> kern-tools: usability, bug fixes and no guilt
>>> guilt: update to latest git version
>>> linux-libc-headers: update to v3.10
>>> gst-plugins-good: fix 3.10 libc-headers build failure
>>> linux-yocto: introduce v3.10
>>>
>>> meta/classes/kernel-yocto.bbclass | 2 +
>>> meta/conf/distro/include/tcmode-default.inc | 2 +-
>>> .../guilt/files/guilt-import-commit.patch | 96 ------
>>> meta/recipes-devtools/guilt/files/guilt-init.patch | 25 --
>>> meta/recipes-devtools/guilt/files/guilt-pop.patch | 73 -----
>>> .../guilt/files/guilt-push-no-series.patch | 29 --
>>> meta/recipes-devtools/guilt/files/guilt-push.patch | 42 ---
>>> .../guilt/files/guilt-set-git_exec_path.patch | 29 --
>>> ...lt-update-supported-git-versions-to-1.8.x.patch | 28 --
>>> meta/recipes-devtools/guilt/files/guilt.patch | 319
>>> --------------------
>>> .../guilt/files/improve_auto_header_gen.patch | 71 -----
>>> .../files/make_git_commands_conditional.patch | 48 ---
>>> .../guilt/files/optional_head_check.patch | 60 ----
>>> .../guilt/files/uninstall_force.patch | 14 -
>>> .../{guilt-native_0.33.bb => guilt-native_git.bb} | 21 +-
>>> .../kern-tools/kern-tools-native_git.bb | 6 +-
>>> .../linux-libc-headers/linux-libc-headers_3.10.bb | 7 +
>>> .../linux-libc-headers/linux-libc-headers_3.8.bb | 8 -
>>> meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb | 30 ++
>>> meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb | 25 ++
>>> meta/recipes-kernel/linux/linux-yocto_3.10.bb | 30 ++
>>> ...define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch | 45 +++
>>> .../gstreamer/gst-plugins-good_0.10.31.bb | 1 +
>>> 23 files changed, 150 insertions(+), 861 deletions(-)
>>> delete mode 100644
>>> meta/recipes-devtools/guilt/files/guilt-import-commit.patch
>>> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-init.patch
>>> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-pop.patch
>>> delete mode 100644
>>> meta/recipes-devtools/guilt/files/guilt-push-no-series.patch
>>> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-push.patch
>>> delete mode 100644
>>> meta/recipes-devtools/guilt/files/guilt-set-git_exec_path.patch
>>> delete mode 100644
>>> meta/recipes-devtools/guilt/files/guilt-update-supported-git-versions-to-1.8.x.patch
>>>
>>>
>>> delete mode 100644 meta/recipes-devtools/guilt/files/guilt.patch
>>> delete mode 100644
>>> meta/recipes-devtools/guilt/files/improve_auto_header_gen.patch
>>> delete mode 100644
>>> meta/recipes-devtools/guilt/files/make_git_commands_conditional.patch
>>> delete mode 100644
>>> meta/recipes-devtools/guilt/files/optional_head_check.patch
>>> delete mode 100644
>>> meta/recipes-devtools/guilt/files/uninstall_force.patch
>>> rename meta/recipes-devtools/guilt/{guilt-native_0.33.bb =>
>>> guilt-native_git.bb} (45%)
>>> create mode 100644
>>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.10.bb
>>> delete mode 100644
>>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.8.bb
>>> create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb
>>> create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb
>>> create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.10.bb
>>> create mode 100644
>>> meta/recipes-multimedia/gstreamer/gst-plugins-good-0.10.31/0001-v4l2_calls-define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch
>>>
>>>
>>>
>
^ permalink raw reply [flat|nested] 64+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2013-08-24 6:33 ` Saul Wold
@ 2013-08-24 13:34 ` Bruce Ashfield
2013-08-24 13:45 ` Bruce Ashfield
0 siblings, 1 reply; 64+ messages in thread
From: Bruce Ashfield @ 2013-08-24 13:34 UTC (permalink / raw)
To: Saul Wold; +Cc: openembedded-core
On 13-08-24 2:33 AM, Saul Wold wrote:
> On 08/23/2013 11:08 AM, Bruce Ashfield wrote:
>> Richard/Saul,
>>
>> Here's my consolidated set of changes that represent the biggest chunk
>> of work for the Yocto 1.5 release. The obvious change is that the 3.10
>> kernel is now the latest linux-yocto kernel (and linux-yocto-dev will
>> mark on). I've built and booted core-image-sato for all the oe-core
>> qemu machines.
>>
>> 3.10 also the latest LTSI and will be updated with that content when it
>> becomes available.
>>
>> Other features of the 3.10 kernel include:
>>
>> - refreshed -rt support
>> - refreshed yaffs2, aufs3
>> - cryptodev
>> - bfs, edf, and OCF staged features
>> - scrubbed and updated meta data for v3.10
>> - improved tools support for meta data updates and queue maintenance
>> - patch carry forward from all previous linux-yocto kernels and
>> configuration.
>>
>> I've also tested linux-yocto-rt and linux-yocto-tiny for the new,
>> shiny tree.
>>
>> I've also bumped the linux-libc-headers to 3.10 and have fixed
>> gst-plugins-good
>> to adapt to a changed #define in the exported headers.
>>
>> Other parts of this update include an uprev of guilt, and in fact, a
>> restoration of "normal" guil operations, since the kernel tree is now
>> manipulated and maintained via a smaller, more contained script. This
>> was necessary for both usability reasons and the fact that all of guilts
>> protections were being removed for the kernel's use .. which makes you
>> ask the quesetion "why use it". It was time for a change.
>>
>> The patches are pretty self explanitory and all contain detailed long
>> logs .. but the summary is:
>>
>> [PATCH 1/5] kern-tools: usability, bug fixes and no guilt
>> [PATCH 2/5] guilt: update to latest git version
>> [PATCH 3/5] linux-libc-headers: update to v3.10
> One of the changes in 3.10 seems to have introduced a conflicting
> definition of ptrace_peeksiginfo_args in linux/ptrace.h
>
>> In file included from ptrace.h:22:0,
>> | from ptrace05.c:38:
>> |
>> /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/linux/ptrace.h:58:8:
>> error: redefinition of 'struct ptrace_peeksiginfo_args'
>> | struct ptrace_peeksiginfo_args {
>> | ^
>> | In file included from ptrace.h:9:0,
>> | from ptrace05.c:38:
>> |
>> /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/sys/ptrace.h:191:8:
>> note: originally defined here
>> | struct ptrace_peeksiginfo_args
>> | ^
>
> This affects ltp, valgrind and strace.
>
> Please check the autobuilder as I am building with this change set and
> expect these failures.
I'm unfortunately off for the weekend and won't have cycles to look into
any failures until Monday.
So if you want to leave the old headers in place, that's an option.
I fixed the one issue that I saw with Sato .. but I am after all one
person and can't possibly build and boot all the qemu boards with
all image combinations! This is after all, where I'd expect other
people to help out and fix build issues.
Cheers,
Bruce
>
> Sau!
>
> Sau!
>
>> [PATCH 4/5] gst-plugins-good: fix 3.10 libc-headers build failure
>> [PATCH 5/5] linux-yocto: introduce v3.10
>>
>> ** There is one pending activity. As part of thsi update to 3.10, we want
>> to move to the 3.4 and 3.10 kernel, dropping 3.8 support. But the
>> routerstationpro BSP is still using it as its preferred version. I'm
>> a one man show on this update, and I wasn't able to get the 100+ patches
>> ported to 3.10 AND get this update out before the M4 cutoff.
>>
>> ** I'm still attempting to udpate all the reference boards, and
>> once done, I'll send a follow up patch.
>>
>> ** Please test, I've done my best, but things can slip through. We'll
>> work issues in the stabilization period.
>>
>> Cheers,
>>
>> Bruce
>>
>>
>> The following changes since commit
>> 501e1a321d15abd712e3a6ee6ccdb8e21c3d4ea4:
>>
>> bitbake: prserv/serv: Fix pid file removal (2013-08-23 17:43:40 +0100)
>>
>> are available in the git repository at:
>>
>> git://git.pokylinux.org/poky-contrib zedd/kernel
>> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
>>
>> Bruce Ashfield (5):
>> kern-tools: usability, bug fixes and no guilt
>> guilt: update to latest git version
>> linux-libc-headers: update to v3.10
>> gst-plugins-good: fix 3.10 libc-headers build failure
>> linux-yocto: introduce v3.10
>>
>> meta/classes/kernel-yocto.bbclass | 2 +
>> meta/conf/distro/include/tcmode-default.inc | 2 +-
>> .../guilt/files/guilt-import-commit.patch | 96 ------
>> meta/recipes-devtools/guilt/files/guilt-init.patch | 25 --
>> meta/recipes-devtools/guilt/files/guilt-pop.patch | 73 -----
>> .../guilt/files/guilt-push-no-series.patch | 29 --
>> meta/recipes-devtools/guilt/files/guilt-push.patch | 42 ---
>> .../guilt/files/guilt-set-git_exec_path.patch | 29 --
>> ...lt-update-supported-git-versions-to-1.8.x.patch | 28 --
>> meta/recipes-devtools/guilt/files/guilt.patch | 319
>> --------------------
>> .../guilt/files/improve_auto_header_gen.patch | 71 -----
>> .../files/make_git_commands_conditional.patch | 48 ---
>> .../guilt/files/optional_head_check.patch | 60 ----
>> .../guilt/files/uninstall_force.patch | 14 -
>> .../{guilt-native_0.33.bb => guilt-native_git.bb} | 21 +-
>> .../kern-tools/kern-tools-native_git.bb | 6 +-
>> .../linux-libc-headers/linux-libc-headers_3.10.bb | 7 +
>> .../linux-libc-headers/linux-libc-headers_3.8.bb | 8 -
>> meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb | 30 ++
>> meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb | 25 ++
>> meta/recipes-kernel/linux/linux-yocto_3.10.bb | 30 ++
>> ...define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch | 45 +++
>> .../gstreamer/gst-plugins-good_0.10.31.bb | 1 +
>> 23 files changed, 150 insertions(+), 861 deletions(-)
>> delete mode 100644
>> meta/recipes-devtools/guilt/files/guilt-import-commit.patch
>> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-init.patch
>> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-pop.patch
>> delete mode 100644
>> meta/recipes-devtools/guilt/files/guilt-push-no-series.patch
>> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-push.patch
>> delete mode 100644
>> meta/recipes-devtools/guilt/files/guilt-set-git_exec_path.patch
>> delete mode 100644
>> meta/recipes-devtools/guilt/files/guilt-update-supported-git-versions-to-1.8.x.patch
>>
>> delete mode 100644 meta/recipes-devtools/guilt/files/guilt.patch
>> delete mode 100644
>> meta/recipes-devtools/guilt/files/improve_auto_header_gen.patch
>> delete mode 100644
>> meta/recipes-devtools/guilt/files/make_git_commands_conditional.patch
>> delete mode 100644
>> meta/recipes-devtools/guilt/files/optional_head_check.patch
>> delete mode 100644
>> meta/recipes-devtools/guilt/files/uninstall_force.patch
>> rename meta/recipes-devtools/guilt/{guilt-native_0.33.bb =>
>> guilt-native_git.bb} (45%)
>> create mode 100644
>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.10.bb
>> delete mode 100644
>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.8.bb
>> create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb
>> create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb
>> create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.10.bb
>> create mode 100644
>> meta/recipes-multimedia/gstreamer/gst-plugins-good-0.10.31/0001-v4l2_calls-define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch
>>
>>
^ permalink raw reply [flat|nested] 64+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2013-08-23 18:08 Bruce Ashfield
2013-08-23 21:30 ` Bruce Ashfield
@ 2013-08-24 6:33 ` Saul Wold
2013-08-24 13:34 ` Bruce Ashfield
1 sibling, 1 reply; 64+ messages in thread
From: Saul Wold @ 2013-08-24 6:33 UTC (permalink / raw)
To: Bruce Ashfield; +Cc: openembedded-core
On 08/23/2013 11:08 AM, Bruce Ashfield wrote:
> Richard/Saul,
>
> Here's my consolidated set of changes that represent the biggest chunk
> of work for the Yocto 1.5 release. The obvious change is that the 3.10
> kernel is now the latest linux-yocto kernel (and linux-yocto-dev will
> mark on). I've built and booted core-image-sato for all the oe-core
> qemu machines.
>
> 3.10 also the latest LTSI and will be updated with that content when it
> becomes available.
>
> Other features of the 3.10 kernel include:
>
> - refreshed -rt support
> - refreshed yaffs2, aufs3
> - cryptodev
> - bfs, edf, and OCF staged features
> - scrubbed and updated meta data for v3.10
> - improved tools support for meta data updates and queue maintenance
> - patch carry forward from all previous linux-yocto kernels and
> configuration.
>
> I've also tested linux-yocto-rt and linux-yocto-tiny for the new, shiny tree.
>
> I've also bumped the linux-libc-headers to 3.10 and have fixed gst-plugins-good
> to adapt to a changed #define in the exported headers.
>
> Other parts of this update include an uprev of guilt, and in fact, a
> restoration of "normal" guil operations, since the kernel tree is now
> manipulated and maintained via a smaller, more contained script. This
> was necessary for both usability reasons and the fact that all of guilts
> protections were being removed for the kernel's use .. which makes you
> ask the quesetion "why use it". It was time for a change.
>
> The patches are pretty self explanitory and all contain detailed long
> logs .. but the summary is:
>
> [PATCH 1/5] kern-tools: usability, bug fixes and no guilt
> [PATCH 2/5] guilt: update to latest git version
> [PATCH 3/5] linux-libc-headers: update to v3.10
One of the changes in 3.10 seems to have introduced a conflicting
definition of ptrace_peeksiginfo_args in linux/ptrace.h
> In file included from ptrace.h:22:0,
> | from ptrace05.c:38:
> | /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/linux/ptrace.h:58:8: error: redefinition of 'struct ptrace_peeksiginfo_args'
> | struct ptrace_peeksiginfo_args {
> | ^
> | In file included from ptrace.h:9:0,
> | from ptrace05.c:38:
> | /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/sys/ptrace.h:191:8: note: originally defined here
> | struct ptrace_peeksiginfo_args
> | ^
This affects ltp, valgrind and strace.
Please check the autobuilder as I am building with this change set and
expect these failures.
Sau!
Sau!
> [PATCH 4/5] gst-plugins-good: fix 3.10 libc-headers build failure
> [PATCH 5/5] linux-yocto: introduce v3.10
>
> ** There is one pending activity. As part of thsi update to 3.10, we want
> to move to the 3.4 and 3.10 kernel, dropping 3.8 support. But the
> routerstationpro BSP is still using it as its preferred version. I'm
> a one man show on this update, and I wasn't able to get the 100+ patches
> ported to 3.10 AND get this update out before the M4 cutoff.
>
> ** I'm still attempting to udpate all the reference boards, and
> once done, I'll send a follow up patch.
>
> ** Please test, I've done my best, but things can slip through. We'll
> work issues in the stabilization period.
>
> Cheers,
>
> Bruce
>
>
> The following changes since commit 501e1a321d15abd712e3a6ee6ccdb8e21c3d4ea4:
>
> bitbake: prserv/serv: Fix pid file removal (2013-08-23 17:43:40 +0100)
>
> are available in the git repository at:
>
> git://git.pokylinux.org/poky-contrib zedd/kernel
> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
>
> Bruce Ashfield (5):
> kern-tools: usability, bug fixes and no guilt
> guilt: update to latest git version
> linux-libc-headers: update to v3.10
> gst-plugins-good: fix 3.10 libc-headers build failure
> linux-yocto: introduce v3.10
>
> meta/classes/kernel-yocto.bbclass | 2 +
> meta/conf/distro/include/tcmode-default.inc | 2 +-
> .../guilt/files/guilt-import-commit.patch | 96 ------
> meta/recipes-devtools/guilt/files/guilt-init.patch | 25 --
> meta/recipes-devtools/guilt/files/guilt-pop.patch | 73 -----
> .../guilt/files/guilt-push-no-series.patch | 29 --
> meta/recipes-devtools/guilt/files/guilt-push.patch | 42 ---
> .../guilt/files/guilt-set-git_exec_path.patch | 29 --
> ...lt-update-supported-git-versions-to-1.8.x.patch | 28 --
> meta/recipes-devtools/guilt/files/guilt.patch | 319 --------------------
> .../guilt/files/improve_auto_header_gen.patch | 71 -----
> .../files/make_git_commands_conditional.patch | 48 ---
> .../guilt/files/optional_head_check.patch | 60 ----
> .../guilt/files/uninstall_force.patch | 14 -
> .../{guilt-native_0.33.bb => guilt-native_git.bb} | 21 +-
> .../kern-tools/kern-tools-native_git.bb | 6 +-
> .../linux-libc-headers/linux-libc-headers_3.10.bb | 7 +
> .../linux-libc-headers/linux-libc-headers_3.8.bb | 8 -
> meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb | 30 ++
> meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb | 25 ++
> meta/recipes-kernel/linux/linux-yocto_3.10.bb | 30 ++
> ...define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch | 45 +++
> .../gstreamer/gst-plugins-good_0.10.31.bb | 1 +
> 23 files changed, 150 insertions(+), 861 deletions(-)
> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-import-commit.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-init.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-pop.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-push-no-series.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-push.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-set-git_exec_path.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-update-supported-git-versions-to-1.8.x.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/guilt.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/improve_auto_header_gen.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/make_git_commands_conditional.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/optional_head_check.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/uninstall_force.patch
> rename meta/recipes-devtools/guilt/{guilt-native_0.33.bb => guilt-native_git.bb} (45%)
> create mode 100644 meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.10.bb
> delete mode 100644 meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.8.bb
> create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb
> create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb
> create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.10.bb
> create mode 100644 meta/recipes-multimedia/gstreamer/gst-plugins-good-0.10.31/0001-v4l2_calls-define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch
>
^ permalink raw reply [flat|nested] 64+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2013-08-23 18:08 Bruce Ashfield
@ 2013-08-23 21:30 ` Bruce Ashfield
2013-08-24 6:33 ` Saul Wold
1 sibling, 0 replies; 64+ messages in thread
From: Bruce Ashfield @ 2013-08-23 21:30 UTC (permalink / raw)
To: Richard Purdie; +Cc: Patches and discussions about the oe-core layer
On Fri, Aug 23, 2013 at 2:08 PM, Bruce Ashfield
<bruce.ashfield@windriver.com> wrote:
> Richard/Saul,
>
> Here's my consolidated set of changes that represent the biggest chunk
> of work for the Yocto 1.5 release. The obvious change is that the 3.10
> kernel is now the latest linux-yocto kernel (and linux-yocto-dev will
> mark on). I've built and booted core-image-sato for all the oe-core
> qemu machines.
>
> 3.10 also the latest LTSI and will be updated with that content when it
> becomes available.
>
> Other features of the 3.10 kernel include:
>
> - refreshed -rt support
> - refreshed yaffs2, aufs3
> - cryptodev
> - bfs, edf, and OCF staged features
> - scrubbed and updated meta data for v3.10
> - improved tools support for meta data updates and queue maintenance
> - patch carry forward from all previous linux-yocto kernels and
> configuration.
>
> I've also tested linux-yocto-rt and linux-yocto-tiny for the new, shiny tree.
>
> I've also bumped the linux-libc-headers to 3.10 and have fixed gst-plugins-good
> to adapt to a changed #define in the exported headers.
>
> Other parts of this update include an uprev of guilt, and in fact, a
> restoration of "normal" guil operations, since the kernel tree is now
> manipulated and maintained via a smaller, more contained script. This
> was necessary for both usability reasons and the fact that all of guilts
> protections were being removed for the kernel's use .. which makes you
> ask the quesetion "why use it". It was time for a change.
>
> The patches are pretty self explanitory and all contain detailed long
> logs .. but the summary is:
>
> [PATCH 1/5] kern-tools: usability, bug fixes and no guilt
> [PATCH 2/5] guilt: update to latest git version
> [PATCH 3/5] linux-libc-headers: update to v3.10
> [PATCH 4/5] gst-plugins-good: fix 3.10 libc-headers build failure
> [PATCH 5/5] linux-yocto: introduce v3.10
>
> ** There is one pending activity. As part of thsi update to 3.10, we want
> to move to the 3.4 and 3.10 kernel, dropping 3.8 support. But the
> routerstationpro BSP is still using it as its preferred version. I'm
> a one man show on this update, and I wasn't able to get the 100+ patches
> ported to 3.10 AND get this update out before the M4 cutoff.
Good news on this front. The routerstation pro (and it's replacement after
1.5) are working on 3.10 with the patches rebased. I'll follow up later with
the update of the rsp and the removal of the 3.8 recipe.
The beagleboard and fsl board will follow after that as well, pending some
boot testing.
Cheers,
Bruce
>
> ** I'm still attempting to udpate all the reference boards, and
> once done, I'll send a follow up patch.
>
> ** Please test, I've done my best, but things can slip through. We'll
> work issues in the stabilization period.
>
> Cheers,
>
> Bruce
>
>
> The following changes since commit 501e1a321d15abd712e3a6ee6ccdb8e21c3d4ea4:
>
> bitbake: prserv/serv: Fix pid file removal (2013-08-23 17:43:40 +0100)
>
> are available in the git repository at:
>
> git://git.pokylinux.org/poky-contrib zedd/kernel
> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
>
> Bruce Ashfield (5):
> kern-tools: usability, bug fixes and no guilt
> guilt: update to latest git version
> linux-libc-headers: update to v3.10
> gst-plugins-good: fix 3.10 libc-headers build failure
> linux-yocto: introduce v3.10
>
> meta/classes/kernel-yocto.bbclass | 2 +
> meta/conf/distro/include/tcmode-default.inc | 2 +-
> .../guilt/files/guilt-import-commit.patch | 96 ------
> meta/recipes-devtools/guilt/files/guilt-init.patch | 25 --
> meta/recipes-devtools/guilt/files/guilt-pop.patch | 73 -----
> .../guilt/files/guilt-push-no-series.patch | 29 --
> meta/recipes-devtools/guilt/files/guilt-push.patch | 42 ---
> .../guilt/files/guilt-set-git_exec_path.patch | 29 --
> ...lt-update-supported-git-versions-to-1.8.x.patch | 28 --
> meta/recipes-devtools/guilt/files/guilt.patch | 319 --------------------
> .../guilt/files/improve_auto_header_gen.patch | 71 -----
> .../files/make_git_commands_conditional.patch | 48 ---
> .../guilt/files/optional_head_check.patch | 60 ----
> .../guilt/files/uninstall_force.patch | 14 -
> .../{guilt-native_0.33.bb => guilt-native_git.bb} | 21 +-
> .../kern-tools/kern-tools-native_git.bb | 6 +-
> .../linux-libc-headers/linux-libc-headers_3.10.bb | 7 +
> .../linux-libc-headers/linux-libc-headers_3.8.bb | 8 -
> meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb | 30 ++
> meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb | 25 ++
> meta/recipes-kernel/linux/linux-yocto_3.10.bb | 30 ++
> ...define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch | 45 +++
> .../gstreamer/gst-plugins-good_0.10.31.bb | 1 +
> 23 files changed, 150 insertions(+), 861 deletions(-)
> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-import-commit.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-init.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-pop.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-push-no-series.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-push.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-set-git_exec_path.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-update-supported-git-versions-to-1.8.x.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/guilt.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/improve_auto_header_gen.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/make_git_commands_conditional.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/optional_head_check.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/uninstall_force.patch
> rename meta/recipes-devtools/guilt/{guilt-native_0.33.bb => guilt-native_git.bb} (45%)
> create mode 100644 meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.10.bb
> delete mode 100644 meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.8.bb
> create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb
> create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb
> create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.10.bb
> create mode 100644 meta/recipes-multimedia/gstreamer/gst-plugins-good-0.10.31/0001-v4l2_calls-define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch
>
> --
> 1.7.10.4
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
--
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
^ permalink raw reply [flat|nested] 64+ messages in thread
* [PATCH 0/5] linux-yocto: consolidated pull request
@ 2013-08-23 18:08 Bruce Ashfield
2013-08-23 21:30 ` Bruce Ashfield
2013-08-24 6:33 ` Saul Wold
0 siblings, 2 replies; 64+ messages in thread
From: Bruce Ashfield @ 2013-08-23 18:08 UTC (permalink / raw)
To: richard.purdie; +Cc: openembedded-core
Richard/Saul,
Here's my consolidated set of changes that represent the biggest chunk
of work for the Yocto 1.5 release. The obvious change is that the 3.10
kernel is now the latest linux-yocto kernel (and linux-yocto-dev will
mark on). I've built and booted core-image-sato for all the oe-core
qemu machines.
3.10 also the latest LTSI and will be updated with that content when it
becomes available.
Other features of the 3.10 kernel include:
- refreshed -rt support
- refreshed yaffs2, aufs3
- cryptodev
- bfs, edf, and OCF staged features
- scrubbed and updated meta data for v3.10
- improved tools support for meta data updates and queue maintenance
- patch carry forward from all previous linux-yocto kernels and
configuration.
I've also tested linux-yocto-rt and linux-yocto-tiny for the new, shiny tree.
I've also bumped the linux-libc-headers to 3.10 and have fixed gst-plugins-good
to adapt to a changed #define in the exported headers.
Other parts of this update include an uprev of guilt, and in fact, a
restoration of "normal" guil operations, since the kernel tree is now
manipulated and maintained via a smaller, more contained script. This
was necessary for both usability reasons and the fact that all of guilts
protections were being removed for the kernel's use .. which makes you
ask the quesetion "why use it". It was time for a change.
The patches are pretty self explanitory and all contain detailed long
logs .. but the summary is:
[PATCH 1/5] kern-tools: usability, bug fixes and no guilt
[PATCH 2/5] guilt: update to latest git version
[PATCH 3/5] linux-libc-headers: update to v3.10
[PATCH 4/5] gst-plugins-good: fix 3.10 libc-headers build failure
[PATCH 5/5] linux-yocto: introduce v3.10
** There is one pending activity. As part of thsi update to 3.10, we want
to move to the 3.4 and 3.10 kernel, dropping 3.8 support. But the
routerstationpro BSP is still using it as its preferred version. I'm
a one man show on this update, and I wasn't able to get the 100+ patches
ported to 3.10 AND get this update out before the M4 cutoff.
** I'm still attempting to udpate all the reference boards, and
once done, I'll send a follow up patch.
** Please test, I've done my best, but things can slip through. We'll
work issues in the stabilization period.
Cheers,
Bruce
The following changes since commit 501e1a321d15abd712e3a6ee6ccdb8e21c3d4ea4:
bitbake: prserv/serv: Fix pid file removal (2013-08-23 17:43:40 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib zedd/kernel
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Bruce Ashfield (5):
kern-tools: usability, bug fixes and no guilt
guilt: update to latest git version
linux-libc-headers: update to v3.10
gst-plugins-good: fix 3.10 libc-headers build failure
linux-yocto: introduce v3.10
meta/classes/kernel-yocto.bbclass | 2 +
meta/conf/distro/include/tcmode-default.inc | 2 +-
.../guilt/files/guilt-import-commit.patch | 96 ------
meta/recipes-devtools/guilt/files/guilt-init.patch | 25 --
meta/recipes-devtools/guilt/files/guilt-pop.patch | 73 -----
.../guilt/files/guilt-push-no-series.patch | 29 --
meta/recipes-devtools/guilt/files/guilt-push.patch | 42 ---
.../guilt/files/guilt-set-git_exec_path.patch | 29 --
...lt-update-supported-git-versions-to-1.8.x.patch | 28 --
meta/recipes-devtools/guilt/files/guilt.patch | 319 --------------------
.../guilt/files/improve_auto_header_gen.patch | 71 -----
.../files/make_git_commands_conditional.patch | 48 ---
.../guilt/files/optional_head_check.patch | 60 ----
.../guilt/files/uninstall_force.patch | 14 -
.../{guilt-native_0.33.bb => guilt-native_git.bb} | 21 +-
.../kern-tools/kern-tools-native_git.bb | 6 +-
.../linux-libc-headers/linux-libc-headers_3.10.bb | 7 +
.../linux-libc-headers/linux-libc-headers_3.8.bb | 8 -
meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb | 30 ++
meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb | 25 ++
meta/recipes-kernel/linux/linux-yocto_3.10.bb | 30 ++
...define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch | 45 +++
.../gstreamer/gst-plugins-good_0.10.31.bb | 1 +
23 files changed, 150 insertions(+), 861 deletions(-)
delete mode 100644 meta/recipes-devtools/guilt/files/guilt-import-commit.patch
delete mode 100644 meta/recipes-devtools/guilt/files/guilt-init.patch
delete mode 100644 meta/recipes-devtools/guilt/files/guilt-pop.patch
delete mode 100644 meta/recipes-devtools/guilt/files/guilt-push-no-series.patch
delete mode 100644 meta/recipes-devtools/guilt/files/guilt-push.patch
delete mode 100644 meta/recipes-devtools/guilt/files/guilt-set-git_exec_path.patch
delete mode 100644 meta/recipes-devtools/guilt/files/guilt-update-supported-git-versions-to-1.8.x.patch
delete mode 100644 meta/recipes-devtools/guilt/files/guilt.patch
delete mode 100644 meta/recipes-devtools/guilt/files/improve_auto_header_gen.patch
delete mode 100644 meta/recipes-devtools/guilt/files/make_git_commands_conditional.patch
delete mode 100644 meta/recipes-devtools/guilt/files/optional_head_check.patch
delete mode 100644 meta/recipes-devtools/guilt/files/uninstall_force.patch
rename meta/recipes-devtools/guilt/{guilt-native_0.33.bb => guilt-native_git.bb} (45%)
create mode 100644 meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.10.bb
delete mode 100644 meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.8.bb
create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb
create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb
create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.10.bb
create mode 100644 meta/recipes-multimedia/gstreamer/gst-plugins-good-0.10.31/0001-v4l2_calls-define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch
--
1.7.10.4
^ permalink raw reply [flat|nested] 64+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2012-02-05 6:31 Bruce Ashfield
@ 2012-02-08 4:09 ` Saul Wold
0 siblings, 0 replies; 64+ messages in thread
From: Saul Wold @ 2012-02-08 4:09 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer; +Cc: dvhart
On 02/04/2012 10:31 PM, Bruce Ashfield wrote:
> Richard/Saul,
>
> This is a follow on to the 3.2 tree and src_patches changes that I sent
> last week.
>
> The ability to specify out of tree BSPs via single .scc files is not
> possible, as well as any automatic BSPs following the naming conventions
> of the 3.2 tree.
>
> The meta branch changes are routine, with the exception being that I got
> a report that 3.0 -rt wasn't patching. That report turned out to be true,
> and I've fixed it here.
>
> Cheers,
>
> Bruce
>
> The following changes since commit cb89d43473a91ff4cb2447d642fcd9308d7366e3:
>
> libzypp: add missing runtime dependences on gzip and gnupg (2012-02-03 17:23:34 +0000)
>
> are available in the git repository at:
> git://git.pokylinux.org/poky-contrib zedd/kernel
> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
>
> Bruce Ashfield (5):
> linux-yocto: locate and use out of tree features specified on the
> SRC_URI
> linux-yocto: meta updates for sys940x and cleanup
> linux-yocto: rt compiliation fix
> kern-tools: remove explicit 'yocto' references from auto-bsp handling
> linux-yocto: fri2: use emgd-1.10
>
> meta/classes/kernel-yocto.bbclass | 21 ++++++++++++++++++++
> .../kern-tools/kern-tools-native_git.bb | 2 +-
> meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb | 2 +-
> meta/recipes-kernel/linux/linux-yocto_3.0.bb | 2 +-
> meta/recipes-kernel/linux/linux-yocto_3.2.bb | 2 +-
> 5 files changed, 25 insertions(+), 4 deletions(-)
>
Merged into OE-core with updated patch set
Thanks
Sau!
^ permalink raw reply [flat|nested] 64+ messages in thread
* [PATCH 0/5] linux-yocto: consolidated pull request
@ 2012-02-05 6:31 Bruce Ashfield
2012-02-08 4:09 ` Saul Wold
0 siblings, 1 reply; 64+ messages in thread
From: Bruce Ashfield @ 2012-02-05 6:31 UTC (permalink / raw)
To: richard.purdie; +Cc: dvhart, openembedded-core, saul.wold
Richard/Saul,
This is a follow on to the 3.2 tree and src_patches changes that I sent
last week.
The ability to specify out of tree BSPs via single .scc files is not
possible, as well as any automatic BSPs following the naming conventions
of the 3.2 tree.
The meta branch changes are routine, with the exception being that I got
a report that 3.0 -rt wasn't patching. That report turned out to be true,
and I've fixed it here.
Cheers,
Bruce
The following changes since commit cb89d43473a91ff4cb2447d642fcd9308d7366e3:
libzypp: add missing runtime dependences on gzip and gnupg (2012-02-03 17:23:34 +0000)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib zedd/kernel
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Bruce Ashfield (5):
linux-yocto: locate and use out of tree features specified on the
SRC_URI
linux-yocto: meta updates for sys940x and cleanup
linux-yocto: rt compiliation fix
kern-tools: remove explicit 'yocto' references from auto-bsp handling
linux-yocto: fri2: use emgd-1.10
meta/classes/kernel-yocto.bbclass | 21 ++++++++++++++++++++
.../kern-tools/kern-tools-native_git.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto_3.0.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto_3.2.bb | 2 +-
5 files changed, 25 insertions(+), 4 deletions(-)
--
1.7.4.1
^ permalink raw reply [flat|nested] 64+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2012-01-11 18:52 Bruce Ashfield
@ 2012-01-17 19:28 ` Saul Wold
0 siblings, 0 replies; 64+ messages in thread
From: Saul Wold @ 2012-01-17 19:28 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
On 01/11/2012 10:52 AM, Bruce Ashfield wrote:
> Richard/Saul,
>
> Since this is a stabilization week, this probably can't be merged
> immediately, but I've been working with this enough to call it
> good enough, and me sitting on them longer doesn't help.
>
> The first change in this series is the switch of qemuppc from prep to
> mac99. With this, we'll close a whole set of issues (slow bootup) and
> close a feature gap that has existed for a while.
>
> I'm seeing a bit of strangeness with the mouse in my sato testing,
> but that's about it. Liming hasn't seen the same issues, so getting
> this into the tree will allow us to incrementally improve and debug
> this.
>
> The second change is a SRCREV update pulls in the forward looking
> fix from Khem and a fix from Zumeng that fixes a failed ltp/mm test
> that was found on the routerstationpro.
>
> Cheers,
>
> Bruce
>
> cc: Khem Raj<raj.khem@gmail.com>
> cc: Zumeng Chen<zumeng.chen@windriver.com>
> cc: Liming Wang<liming.wang@windriver.com>
>
> The following changes since commit 18c88fcec85f96d2495457928be913807971aea7:
>
> package.bbclass: per recipe PRSERV_HOST support (2012-01-11 10:37:43 +0000)
>
> are available in the git repository at:
> git://git.pokylinux.org/poky-contrib zedd/kernel
> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
>
> Bruce Ashfield (1):
> linux-yocto: consolidated fix SRCREV updates
>
> Liming Wang (4):
> qemuppc: replace emulation of qemuppc from prep to mac99
> qemuppc: add pointercal file
> qemuppc: add machconfig
> tslib: enable big endian support for qemuppc
>
> meta/conf/machine/qemuppc.conf | 2 +-
> .../formfactor/files/qemuppc/machconfig | 10 ++++++++++
> .../pointercal/files/qemuppc/pointercal | Bin 0 -> 36 bytes
> meta/recipes-graphics/tslib/tslib_1.0.bb | 1 +
> meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb | 6 +++---
> meta/recipes-kernel/linux/linux-yocto_3.0.bb | 15 ++++++++-------
> scripts/runqemu | 7 +------
> scripts/runqemu-internal | 16 ++++++++--------
> 8 files changed, 32 insertions(+), 25 deletions(-)
> create mode 100755 meta/recipes-bsp/formfactor/files/qemuppc/machconfig
> create mode 100644 meta/recipes-bsp/pointercal/files/qemuppc/pointercal
>
Merged into OE-Core
Thanks
Sau!
^ permalink raw reply [flat|nested] 64+ messages in thread
* [PATCH 0/5] linux-yocto: consolidated pull request
@ 2012-01-11 18:52 Bruce Ashfield
2012-01-17 19:28 ` Saul Wold
0 siblings, 1 reply; 64+ messages in thread
From: Bruce Ashfield @ 2012-01-11 18:52 UTC (permalink / raw)
To: richard.purdie; +Cc: openembedded-core, saul.wold
Richard/Saul,
Since this is a stabilization week, this probably can't be merged
immediately, but I've been working with this enough to call it
good enough, and me sitting on them longer doesn't help.
The first change in this series is the switch of qemuppc from prep to
mac99. With this, we'll close a whole set of issues (slow bootup) and
close a feature gap that has existed for a while.
I'm seeing a bit of strangeness with the mouse in my sato testing,
but that's about it. Liming hasn't seen the same issues, so getting
this into the tree will allow us to incrementally improve and debug
this.
The second change is a SRCREV update pulls in the forward looking
fix from Khem and a fix from Zumeng that fixes a failed ltp/mm test
that was found on the routerstationpro.
Cheers,
Bruce
cc: Khem Raj <raj.khem@gmail.com>
cc: Zumeng Chen <zumeng.chen@windriver.com>
cc: Liming Wang <liming.wang@windriver.com>
The following changes since commit 18c88fcec85f96d2495457928be913807971aea7:
package.bbclass: per recipe PRSERV_HOST support (2012-01-11 10:37:43 +0000)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib zedd/kernel
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Bruce Ashfield (1):
linux-yocto: consolidated fix SRCREV updates
Liming Wang (4):
qemuppc: replace emulation of qemuppc from prep to mac99
qemuppc: add pointercal file
qemuppc: add machconfig
tslib: enable big endian support for qemuppc
meta/conf/machine/qemuppc.conf | 2 +-
.../formfactor/files/qemuppc/machconfig | 10 ++++++++++
.../pointercal/files/qemuppc/pointercal | Bin 0 -> 36 bytes
meta/recipes-graphics/tslib/tslib_1.0.bb | 1 +
meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb | 6 +++---
meta/recipes-kernel/linux/linux-yocto_3.0.bb | 15 ++++++++-------
scripts/runqemu | 7 +------
scripts/runqemu-internal | 16 ++++++++--------
8 files changed, 32 insertions(+), 25 deletions(-)
create mode 100755 meta/recipes-bsp/formfactor/files/qemuppc/machconfig
create mode 100644 meta/recipes-bsp/pointercal/files/qemuppc/pointercal
--
1.7.4.1
^ permalink raw reply [flat|nested] 64+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2011-01-10 17:30 Bruce Ashfield
2011-01-10 21:05 ` Richard Purdie
@ 2011-01-13 6:01 ` Saul Wold
1 sibling, 0 replies; 64+ messages in thread
From: Saul Wold @ 2011-01-13 6:01 UTC (permalink / raw)
To: Bruce Ashfield; +Cc: yocto, poky
On 01/10/2011 09:30 AM, Bruce Ashfield wrote:
> It looks like some of my last pull request didn't make it
> to master, so I've repeated it here. Patches 4/5 have already
> been sent:
>
> kernel-yocto: pass the build directory to configme
> routerstation: disable command line overrides
>
> The remaining three changes are new and are:
>
> - A merge from Darren to update the default 2.6.37 configs
> to enable the debug/ftrace configs we need.
>
> - A change to make board descriptions generic. These are
> transparent to nearly everyone, but any new BSPs will be
> described with: KARCH, KMACHINE and KTYPE which are more
> generic variables and used internally during kernel
> configuration. They are differnet from yocto/poky variables
> on purpose, since the kernel tree can be cloned and used
> distinctly from any build system.
>
> - And finally an update to 2.6.37 with a port of the alternate
> RPC ports patch which reinstates usermode NFS support to
> 2.6.37.
>
> Also out of interest, the routerstation pro and fsl-mpc8315e-rdb
> have all been booted against 2.6.37 and will follow shortly.
> Next up are feature merges (lttng, etc) to match the -stable
> kernel functionality.
>
> Cheers,
>
> Bruce
>
>
> Pull URL: git://git.pokylinux.org/poky-contrib.git
> Branch: zedd/kernel
> Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
>
> Thanks,
> Bruce Ashfield<bruce.ashfield@windriver.com>
> ---
>
>
> Bruce Ashfield (5):
> kernel-yocto: pass the build directory to configme
> routerstation: disable command line overrides
> linux-yocto: update SRCREV to pickup debug/ftrace config changes
> kern-tools: create generic variables for platform/board/kernel
> linux-yocto: update to 2.6.37
>
> meta/classes/kernel-yocto.bbclass | 2 +-
> .../conf/distro/include/poky-default-revisions.inc | 28 ++++++++++----------
> 2 files changed, 15 insertions(+), 15 deletions(-)
>
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky
>
Everything got pulled this time
In Master now
Thanks
Sau!
^ permalink raw reply [flat|nested] 64+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2011-01-10 17:30 Bruce Ashfield
@ 2011-01-10 21:05 ` Richard Purdie
2011-01-13 6:01 ` Saul Wold
1 sibling, 0 replies; 64+ messages in thread
From: Richard Purdie @ 2011-01-10 21:05 UTC (permalink / raw)
To: Bruce Ashfield; +Cc: yocto, poky, saul.wold
On Mon, 2011-01-10 at 12:30 -0500, Bruce Ashfield wrote:
> It looks like some of my last pull request didn't make it
> to master, so I've repeated it here. Patches 4/5 have already
> been sent:
>
> kernel-yocto: pass the build directory to configme
> routerstation: disable command line overrides
>
> The remaining three changes are new and are:
>
> - A merge from Darren to update the default 2.6.37 configs
> to enable the debug/ftrace configs we need.
>
> - A change to make board descriptions generic. These are
> transparent to nearly everyone, but any new BSPs will be
> described with: KARCH, KMACHINE and KTYPE which are more
> generic variables and used internally during kernel
> configuration. They are differnet from yocto/poky variables
> on purpose, since the kernel tree can be cloned and used
> distinctly from any build system.
>
> - And finally an update to 2.6.37 with a port of the alternate
> RPC ports patch which reinstates usermode NFS support to
> 2.6.37.
>
> Also out of interest, the routerstation pro and fsl-mpc8315e-rdb
> have all been booted against 2.6.37 and will follow shortly.
> Next up are feature merges (lttng, etc) to match the -stable
> kernel functionality.
Merged into master, thanks!
Richard
^ permalink raw reply [flat|nested] 64+ messages in thread
* [PATCH 0/5] linux-yocto: consolidated pull request
@ 2011-01-10 17:30 Bruce Ashfield
2011-01-10 21:05 ` Richard Purdie
2011-01-13 6:01 ` Saul Wold
0 siblings, 2 replies; 64+ messages in thread
From: Bruce Ashfield @ 2011-01-10 17:30 UTC (permalink / raw)
To: rpurdie; +Cc: yocto, poky, saul.wold
It looks like some of my last pull request didn't make it
to master, so I've repeated it here. Patches 4/5 have already
been sent:
kernel-yocto: pass the build directory to configme
routerstation: disable command line overrides
The remaining three changes are new and are:
- A merge from Darren to update the default 2.6.37 configs
to enable the debug/ftrace configs we need.
- A change to make board descriptions generic. These are
transparent to nearly everyone, but any new BSPs will be
described with: KARCH, KMACHINE and KTYPE which are more
generic variables and used internally during kernel
configuration. They are differnet from yocto/poky variables
on purpose, since the kernel tree can be cloned and used
distinctly from any build system.
- And finally an update to 2.6.37 with a port of the alternate
RPC ports patch which reinstates usermode NFS support to
2.6.37.
Also out of interest, the routerstation pro and fsl-mpc8315e-rdb
have all been booted against 2.6.37 and will follow shortly.
Next up are feature merges (lttng, etc) to match the -stable
kernel functionality.
Cheers,
Bruce
Pull URL: git://git.pokylinux.org/poky-contrib.git
Branch: zedd/kernel
Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Thanks,
Bruce Ashfield <bruce.ashfield@windriver.com>
---
Bruce Ashfield (5):
kernel-yocto: pass the build directory to configme
routerstation: disable command line overrides
linux-yocto: update SRCREV to pickup debug/ftrace config changes
kern-tools: create generic variables for platform/board/kernel
linux-yocto: update to 2.6.37
meta/classes/kernel-yocto.bbclass | 2 +-
.../conf/distro/include/poky-default-revisions.inc | 28 ++++++++++----------
2 files changed, 15 insertions(+), 15 deletions(-)
^ permalink raw reply [flat|nested] 64+ messages in thread
end of thread, other threads:[~2023-02-01 16:28 UTC | newest]
Thread overview: 64+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-05-03 15:44 [PATCH 0/5] linux-yocto: consolidated pull request Bruce Ashfield
2020-05-03 15:44 ` [PATCH 1/5] linux-yocto/5.4: update to v5.4.28 Bruce Ashfield
2020-05-03 15:44 ` [PATCH 2/5] linux-yocto/5.4: update to v5.4.32 Bruce Ashfield
2020-05-03 15:44 ` [PATCH 3/5] linux-yocto/5.4: update to v5.4.34 Bruce Ashfield
2020-05-03 15:44 ` [PATCH 4/5] linux-yocto/5.4: update to v5.4.38 Bruce Ashfield
2020-05-03 15:44 ` [PATCH 5/5] linux-yocto-dev: bump to v5.7-rc Bruce Ashfield
2020-05-04 8:30 ` [PATCH 0/5] linux-yocto: consolidated pull request Richard Purdie
2020-05-04 12:56 ` Bruce Ashfield
[not found] ` <160BD489BF65999D.29536@lists.openembedded.org>
2020-05-04 13:06 ` [OE-core] " Bruce Ashfield
2020-05-04 13:24 ` Richard Purdie
2020-05-04 13:34 ` Bruce Ashfield
2020-05-07 18:14 ` Steve Sakoman
2020-05-07 19:18 ` Bruce Ashfield
-- strict thread matches above, loose matches on Subject: below --
2023-02-01 16:28 bruce.ashfield
2020-11-19 19:17 Bruce Ashfield
2020-05-29 1:29 Bruce Ashfield
2020-03-24 23:04 Bruce Ashfield
2016-07-27 16:57 Bruce Ashfield
2016-06-21 15:20 Bruce Ashfield
2016-04-13 16:12 Bruce Ashfield
2015-05-01 1:34 Bruce Ashfield
2015-05-01 22:59 ` Richard Purdie
2015-05-01 23:30 ` Bruce Ashfield
2015-05-02 8:13 ` Martin Jansa
2015-05-03 2:50 ` Bruce Ashfield
2015-05-06 14:42 ` Martin Jansa
2015-05-06 14:58 ` Bruce Ashfield
2015-05-06 15:33 ` Martin Jansa
2015-05-06 15:44 ` Richard Purdie
2015-05-06 16:07 ` Martin Jansa
2015-05-06 17:46 ` Bruce Ashfield
2015-05-06 21:32 ` Richard Purdie
2015-05-06 22:49 ` Martin Jansa
2015-05-07 15:33 ` Bruce Ashfield
2015-05-07 6:33 ` Khem Raj
2015-05-02 9:00 ` Richard Purdie
2015-05-03 2:53 ` Bruce Ashfield
2015-05-03 3:52 ` Bruce Ashfield
2015-05-03 10:48 ` Richard Purdie
2015-05-03 21:30 ` Richard Purdie
2015-05-04 4:36 ` Bruce Ashfield
2015-05-04 15:01 ` Bruce Ashfield
2015-03-24 18:57 Bruce Ashfield
2015-03-25 9:26 ` Richard Purdie
2015-03-25 12:13 ` Bruce Ashfield
2015-03-25 13:26 ` Bruce Ashfield
2015-03-25 13:52 ` Richard Purdie
2013-08-23 18:08 Bruce Ashfield
2013-08-23 21:30 ` Bruce Ashfield
2013-08-24 6:33 ` Saul Wold
2013-08-24 13:34 ` Bruce Ashfield
2013-08-24 13:45 ` Bruce Ashfield
2013-08-24 13:50 ` Saul Wold
2013-08-24 13:53 ` Bruce Ashfield
2013-08-24 14:47 ` Bruce Ashfield
2013-08-24 14:59 ` Bruce Ashfield
2013-08-24 16:05 ` Bruce Ashfield
2012-02-05 6:31 Bruce Ashfield
2012-02-08 4:09 ` Saul Wold
2012-01-11 18:52 Bruce Ashfield
2012-01-17 19:28 ` Saul Wold
2011-01-10 17:30 Bruce Ashfield
2011-01-10 21:05 ` Richard Purdie
2011-01-13 6:01 ` Saul Wold
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.