May 2014 - kernel - Fedora mailing-lists

fedora 14 kernel performance with ip forwarding workload
by Jesse Brandeburg 05 Jun '15

05 Jun '15

The other day I was running the stock fedora kernel on my ip forwarding setup, to see what the performance was, and the performance wasn't very good. system is S5520HC dual socket 2.93GHz Xeon 5570 (Nehalem) with 3 quad port 82580 adapters (12 ports). Traffic is bidirectional 64 byte packets being forwarded and received on each port, basically port to port routing. I am only using 12 flows currently. The driver is igb, and I am using an affinity script that lines up each pair of ports that are forwarding traffic into optimal configurations for cache locality. I am also disabling remote_node_defrag_ratio to stop cross node traffic. With the fedora default kernel from F14 it appears that CONFIG_NETFILTER=y means that I cannot unload all of netfilter even if I stop iptables service. perf showed netfilter being prominent, and removing it gives me much higher throughput. Is there a reason CONFIG_NETFILTER=y ? Isn't it a good thing to be able to disable netfilter if you want to? Jesse

5 9

debug_dma_assert_idle - snd_hda_intel - cpu touching an active dma mapped cacheline
by poma 18 Sep '14

18 Sep '14

Sound whispers, WARNING: CPU: 3 PID: 900 at lib/dma-debug.c:593 debug_dma_assert_idle+0x159/0x1d0() snd_hda_intel 0000:00:07.0: DMA-API: cpu touching an active dma mapped cacheline [cln=0x03014000] CPU: 3 PID: 900 Comm: chronyd Not tainted 3.15.0-0.rc1.git1.1.fc21.i686 #1 Call Trace: [<c0ae256d>] dump_stack+0x48/0x60 [<c0454402>] warn_slowpath_common+0x82/0xa0 [<c0750b69>] ? debug_dma_assert_idle+0x159/0x1d0 [<c0750b69>] ? debug_dma_assert_idle+0x159/0x1d0 [<c045445e>] warn_slowpath_fmt+0x3e/0x60 [<c0750b69>] debug_dma_assert_idle+0x159/0x1d0 [<c05860b9>] ? anon_vma_prepare+0x29/0x140 [<c057a4ee>] do_wp_page+0xce/0x890 [<c0500045>] ? auditsc_get_stamp+0x45/0x70 [<c057caf2>] handle_mm_fault+0x662/0xb70 [<c0500045>] ? auditsc_get_stamp+0x45/0x70 [<c0aee507>] __do_page_fault+0x1a7/0x5d0 [<c040ace8>] ? sched_clock+0x8/0x10 [<c040ace8>] ? sched_clock+0x8/0x10 [<c04ab036>] ? lock_release_holdtime.part.28+0x96/0xf0 [<c0aee930>] ? __do_page_fault+0x5d0/0x5d0 [<c0aee94a>] do_page_fault+0x1a/0x20 [<c0aeb344>] error_code+0x6c/0x74 [<c07334b6>] ? __put_user_4+0x1a/0x24 [<c048d280>] ? schedule_tail+0x60/0xa0 [<c0af3746>] ret_from_fork+0x6/0x20 ---[ end trace d31d73481e988403 ]--- Mapped at: [<c074ec12>] debug_dma_alloc_coherent+0x22/0x70 [<f812de90>] snd_dma_alloc_pages+0x170/0x260 [snd_pcm] [<f812dfe2>] snd_dma_alloc_pages_fallback+0x62/0x90 [snd_pcm] [<f812e3b0>] snd_malloc_sgbuf_pages+0xf0/0x211 [snd_pcm] [<f812df23>] snd_dma_alloc_pages+0x203/0x260 [snd_pcm] https://bugzilla.redhat.com/show_bug.cgi?id=1087565 poma

3 11

Remove ppc32 support
by Josh Boyer 10 Jul '14

10 Jul '14

The powerpc secondary arch team has disabled all ppc32 builds in koji for F21 and beyond: https://lists.fedoraproject.org/pipermail/ppc/2014-May/002801.html There's little point in keeping support for ppc32 support in the kernel package when it will never be built. This also removes the -smp variant and with_smp* support, as that was only used on ppc32. --- Makefile.config | 12 +--- config-powerpc32-generic | 180 ----------------------------------------------- config-powerpc32-smp | 3 - filter-ppc.sh | 14 ---- kernel.spec | 72 +++---------------- 5 files changed, 10 insertions(+), 271 deletions(-) delete mode 100644 config-powerpc32-generic delete mode 100644 config-powerpc32-smp delete mode 100644 filter-ppc.sh diff --git a/Makefile.config b/Makefile.config index 3483968..63549f6 100644 --- a/Makefile.config +++ b/Makefile.config @@ -11,11 +11,10 @@ CONFIGFILES = \ $(CFG)-s390x.config \ $(CFG)-armv7hl.config $(CFG)-armv7hl-lpae.config \ $(CFG)-aarch64.config \ - $(CFG)-ppc.config $(CFG)-ppc-smp.config \ $(CFG)-ppc64.config $(CFG)-ppc64p7.config $(CFG)-ppc64-debug.config \ $(CFG)-ppc64le.config -PLATFORMS = x86 x86_64 powerpc powerpc32 powerpc64 s390x arm arm64 +PLATFORMS = x86 x86_64 powerpc powerpc64 s390x arm arm64 TEMPFILES = $(addprefix temp-, $(addsuffix -generic, $(PLATFORMS))) configs: $(CONFIGFILES) @@ -81,9 +80,6 @@ temp-powerpc-generic: config-powerpc-generic temp-generic temp-powerpc-debug-generic: config-powerpc-generic temp-debug-generic perl merge.pl $^ > $@ -temp-powerpc32-generic: config-powerpc32-generic temp-powerpc-generic - perl merge.pl $^ > $@ - temp-powerpc64-generic: config-powerpc64 temp-powerpc-generic perl merge.pl $^ > $@ @@ -134,9 +130,3 @@ $(CFG)-armv7hl-lpae.config: /dev/null temp-armv7-lpae $(CFG)-aarch64.config: /dev/null temp-arm64 perl merge.pl $^ arm64 > $@ - -$(CFG)-ppc.config: /dev/null temp-powerpc32-generic - perl merge.pl $^ powerpc > $@ - -$(CFG)-ppc-smp.config: config-powerpc32-smp temp-powerpc32-generic - perl merge.pl $^ powerpc > $@ diff --git a/config-powerpc32-generic b/config-powerpc32-generic deleted file mode 100644 index 10e02fb..0000000 --- a/config-powerpc32-generic +++ /dev/null @@ -1,180 +0,0 @@ -# CONFIG_SMP is not set -CONFIG_PPC32=y -# CONFIG_PPC64 is not set -# CONFIG_RTAS_PROC is not set -# CONFIG_PCMCIA_M8XX is not set -# CONFIG_HOTPLUG_PCI is not set -CONFIG_CPU_FREQ_PMAC=y -CONFIG_PPC_CHRP=y -CONFIG_PPC_PMAC=y -# CONFIG_PPC_MPC52xx is not set -CONFIG_PPC_PREP=y - -# CONFIG_PPC_MPC5200_SIMPLE is not set -# CONFIG_SATA_FSL is not set -# CONFIG_SATA_NV is not set - -# busted in .28git1 -# ERROR: "cacheable_memzero" [drivers/net/gianfar_driver.ko] undefined! -# CONFIG_GIANFAR is not set -# CONFIG_USB_EHCI_FSL is not set - -CONFIG_PMAC_APM_EMU=y -CONFIG_PMAC_BACKLIGHT=y - -CONFIG_HIGHMEM=y -# CONFIG_HIGHMEM_START_BOOL is not set -# CONFIG_LOWMEM_SIZE_BOOL is not set -# CONFIG_TASK_SIZE_BOOL is not set -# CONFIG_KERNEL_START_BOOL is not set -# CONFIG_PPC601_SYNC_FIX is not set -CONFIG_ADVANCED_OPTIONS=y -CONFIG_SCSI_MESH=m -CONFIG_SCSI_MESH_SYNC_RATE=5 -CONFIG_SCSI_MESH_RESET_DELAY_MS=4000 - -CONFIG_LBDAF=y - -CONFIG_SCSI_MAC53C94=m -CONFIG_ADB_CUDA=y -CONFIG_ADB_MACIO=y -CONFIG_INPUT_ADBHID=y -CONFIG_ADB_PMU_LED=y -CONFIG_ADB_PMU_LED_IDE=y - -CONFIG_PMAC_MEDIABAY=y -CONFIG_NET_VENDOR_APPLE=y -CONFIG_BMAC=m -CONFIG_MACE=m -# CONFIG_MACE_AAUI_PORT is not set -# CONFIG_MV643XX_ETH is not set -CONFIG_I2C_HYDRA=m -CONFIG_I2C_MPC=m -CONFIG_THERM_WINDTUNNEL=m -CONFIG_THERM_ADT746X=m -# CONFIG_ANSLCD is not set - -CONFIG_FB_PLATINUM=y -CONFIG_FB_VALKYRIE=y -CONFIG_FB_CT65550=y -# CONFIG_BDI_SWITCH is not set - -CONFIG_MAC_FLOPPY=m -# CONFIG_BLK_DEV_FD is not set - -CONFIG_FB_ATY128=y -CONFIG_FB_ATY=y -CONFIG_FB_MATROX=y -# CONFIG_KEXEC is not set - -# CONFIG_HVC_RTAS is not set - -# CONFIG_UDBG_RTAS_CONSOLE is not set -CONFIG_BRIQ_PANEL=m - -# CONFIG_ATA_PIIX is not set -# CONFIG_PATA_AMD is not set -# CONFIG_PATA_ATIIXP is not set -# CONFIG_PATA_MPC52xx is not set -# CONFIG_PATA_MPIIX is not set -# CONFIG_PATA_OLDPIIX is not set -# CONFIG_PATA_OPTI is not set -# CONFIG_PATA_SERVERWORKS is not set - -# CONFIG_SERIAL_MPC52xx is not set -# CONFIG_MPC5200_WDT is not set -CONFIG_8xxx_WDT=m -CONFIG_GEF_WDT=m - -# CONFIG_PPC_MPC5200_BUGFIX is not set -# CONFIG_NET_VENDOR_FREESCALE is not set -#CHECK: This may later become a tristate. -CONFIG_MDIO_GPIO=m - -CONFIG_SERIAL_OF_PLATFORM=y -CONFIG_DEBUG_STACKOVERFLOW=y - -# CONFIG_EMBEDDED6xx is not set - -# CONFIG_BLK_DEV_PLATFORM is not set -# CONFIG_BLK_DEV_4DRIVES is not set -# CONFIG_BLK_DEV_ALI14XX is not set -# CONFIG_BLK_DEV_DTC2278 is not set -# CONFIG_BLK_DEV_HT6560B is not set -# CONFIG_BLK_DEV_QD65XX is not set -# CONFIG_BLK_DEV_UMC8672 is not set - -# CONFIG_VIRQ_DEBUG is not set - -CONFIG_PPC_BESTCOMM_ATA=m -CONFIG_PPC_BESTCOMM_FEC=m -CONFIG_PPC_BESTCOMM_GEN_BD=m - -CONFIG_FORCE_MAX_ZONEORDER=11 -# CONFIG_PAGE_OFFSET_BOOL is not set -# CONFIG_FB_FSL_DIU is not set -CONFIG_IRQSTACKS=y -CONFIG_VIRTUALIZATION=y - -# CONFIG_DEBUG_GPIO is not set -# CONFIG_GPIO_PCA953X is not set -# CONFIG_GPIO_PCF857X is not set -# CONFIG_HTC_EGPIO is not set - -# CONFIG_TIFM_CORE is not set - -# CONFIG_BLK_CPQ_CISS_DA is not set -# CONFIG_CISS_SCSI_TAPE is not set - -# CONFIG_I2C_NFORCE2 is not set - -# CONFIG_SND_INTEL8X0 is not set -# CONFIG_SND_INTEL8X0M is not set - -# CONFIG_MEMSTICK is not set - -# CONFIG_IPMI_HANDLER is not set - -# PPC gets sad with debug alloc (bz 448598) -# CONFIG_DEBUG_PAGEALLOC is not set - -CONFIG_CRYPTO_DEV_TALITOS=m - -# CONFIG_FSL_EMB_PERFMON is not set -# CONFIG_MPC8272_ADS is not set -# CONFIG_PQ2FADS is not set -# CONFIG_EP8248E is not set -# CONFIG_MPC830x_RDB is not set -# CONFIG_MPC831x_RDB is not set -# CONFIG_MPC832x_MDS is not set -# CONFIG_MPC832x_RDB is not set -# CONFIG_MPC834x_MDS is not set -# CONFIG_MPC834x_ITX is not set -# CONFIG_MPC836x_MDS is not set -# CONFIG_MPC836x_RDK is not set -# CONFIG_MPC837x_MDS is not set -# CONFIG_MPC837x_RDB is not set -# CONFIG_SBC834x is not set -# CONFIG_ASP834x is not set -# CONFIG_KMETER1 is not set -# CONFIG_MPC8641_HPCN is not set -# CONFIG_SBC8641D is not set -# CONFIG_MPC8610_HPCD is not set -# CONFIG_FSL_LBC is not set -# CONFIG_MTD_NAND_FSL_UPM is not set - -# CONFIG_USB_MUSB_HDRC is not set - -# busted in 2.6.27 -# drivers/mtd/maps/sbc8240.c: In function 'init_sbc8240_mtd': -# drivers/mtd/maps/sbc8240.c:172: warning: passing argument 1 of 'simple_map_init' from incompatible pointer type -# drivers/mtd/maps/sbc8240.c:177: error: 'struct mtd_info' has no member named 'module' - -CONFIG_RCU_FANOUT=32 - -CONFIG_KVM_BOOK3S_32=m - -# CONFIG_SCSI_QLA_ISCSI is not set - -CONFIG_BATTERY_PMU=m - diff --git a/config-powerpc32-smp b/config-powerpc32-smp deleted file mode 100644 index 5dbe87f..0000000 --- a/config-powerpc32-smp +++ /dev/null @@ -1,3 +0,0 @@ -# CONFIG_HOTPLUG_CPU is not set -CONFIG_NR_CPUS=4 -# CONFIG_BATTERY_PMU is not set diff --git a/filter-ppc.sh b/filter-ppc.sh deleted file mode 100644 index 8ff7a3b..0000000 --- a/filter-ppc.sh +++ /dev/null @@ -1,14 +0,0 @@ -#! /bin/bash - -# This is the ppc override file for the core/drivers package split. The -# module directories listed here and in the generic list in filter-modules.sh -# will be moved to the resulting kernel-modules package for this arch. -# Anything not listed in those files will be in the kernel-core package. -# -# Please review the default list in filter-modules.sh before making -# modifications to the overrides below. If something should be removed across -# all arches, remove it in the default instead of per-arch. - -driverdirs="atm auxdisplay bcma bluetooth fmc infiniband isdn leds media memstick message mmc mtd nfc ntb pcmcia platform power ssb staging uio uwb" - -singlemods="ntb_netdev iscsi_ibft iscsi_boot_sysfs iscsi_tcp megaraid pmcraid qla1280 9pnet_rdma svcrdma xprtrdma hid-picolcd hid-prodikeys hwa-hc hwpoison-inject" diff --git a/kernel.spec b/kernel.spec index 11352bc..d460254 100644 --- a/kernel.spec +++ b/kernel.spec @@ -84,8 +84,6 @@ Summary: The Linux kernel # # standard kernel %define with_up %{?_without_up: 0} %{?!_without_up: 1} -# kernel-smp (only valid for ppc 32-bit) -%define with_smp %{?_without_smp: 0} %{?!_without_smp: 1} # kernel PAE (only valid for i686 (PAE) and ARM (lpae)) %define with_pae %{?_without_pae: 0} %{?!_without_pae: 1} # kernel-debug @@ -109,8 +107,6 @@ Summary: The Linux kernel # # Only build the base kernel (--with baseonly): %define with_baseonly %{?_with_baseonly: 1} %{?!_with_baseonly: 0} -# Only build the smp kernel (--with smponly): -%define with_smponly %{?_with_smponly: 1} %{?!_with_smponly: 0} # Only build the pae kernel (--with paeonly): %define with_paeonly %{?_with_paeonly: 1} %{?!_with_paeonly: 0} # Only build the debug kernel (--with dbgonly): @@ -193,14 +189,6 @@ Summary: The Linux kernel # if requested, only build base kernel %if %{with_baseonly} -%define with_smp 0 -%define with_pae 0 -%define with_debug 0 -%endif - -# if requested, only build smp kernel -%if %{with_smponly} -%define with_up 0 %define with_pae 0 %define with_debug 0 %endif @@ -208,7 +196,6 @@ Summary: The Linux kernel # if requested, only build pae kernel %if %{with_paeonly} %define with_up 0 -%define with_smp 0 %define with_debug 0 %endif @@ -218,7 +205,6 @@ Summary: The Linux kernel %define with_up 0 %define with_pae 0 %endif -%define with_smp 0 %define with_pae 0 %define with_tools 0 %define with_perf 0 @@ -228,16 +214,11 @@ Summary: The Linux kernel %if %{with_vdso_install} # These arches install vdso/ directories. -%define vdso_arches %{all_x86} x86_64 ppc ppc64 ppc64p7 s390 s390x aarch64 ppc64le +%define vdso_arches %{all_x86} x86_64 ppc64 ppc64p7 s390 s390x aarch64 ppc64le %endif # Overrides for generic default options -# only ppc needs a separate smp kernel -%ifnarch ppc -%define with_smp 0 -%endif - # don't do debug builds on anything but i686 and x86_64 %ifnarch i686 x86_64 %define with_debug 0 @@ -253,12 +234,12 @@ Summary: The Linux kernel %endif # bootwrapper is only on ppc -%ifnarch ppc ppc64 ppc64p7 ppc64le +%ifnarch ppc64 ppc64p7 ppc64le %define with_bootwrapper 0 %endif # sparse blows up on ppc64 and sparc64 -%ifarch ppc64 ppc ppc64p7 ppc64le +%ifarch ppc64 ppc64p7 ppc64le %define with_sparse 0 %endif @@ -311,16 +292,6 @@ Summary: The Linux kernel %define with_tools 0 %endif -%ifarch ppc -%define asmarch powerpc -%define hdrarch powerpc -%define all_arch_configs kernel-%{version}-ppc{-,.}*config -%define image_install_path boot -%define make_target vmlinux -%define kernel_image vmlinux -%define kernel_image_elf 1 -%endif - %ifarch %{arm} %define all_arch_configs kernel-%{version}-arm*.config %define image_install_path boot @@ -368,7 +339,6 @@ Summary: The Linux kernel %ifarch %nobuildarches %define with_up 0 -%define with_smp 0 %define with_pae 0 %define with_debuginfo 0 %define with_perf 0 @@ -382,7 +352,7 @@ Summary: The Linux kernel %endif # Architectures we build tools/cpupower on -%define cpupowerarchs %{ix86} x86_64 ppc ppc64 ppc64p7 %{arm} aarch64 ppc64le +%define cpupowerarchs %{ix86} x86_64 ppc64 ppc64p7 %{arm} aarch64 ppc64le # # Packages that need to be installed before the kernel is, because the %%post @@ -400,7 +370,7 @@ Version: %{rpmversion} Release: %{pkg_release} # DO NOT CHANGE THE 'ExclusiveArch' LINE TO TEMPORARILY EXCLUDE AN ARCHITECTURE BUILD. # SET %%nobuildarches (ABOVE) INSTEAD -ExclusiveArch: %{all_x86} x86_64 ppc ppc64 ppc64p7 s390 s390x %{arm} aarch64 ppc64le +ExclusiveArch: %{all_x86} x86_64 ppc64 ppc64p7 s390 s390x %{arm} aarch64 ppc64le ExclusiveOS: Linux Requires: kernel-%{?variant:%{variant}-}core-uname-r = %{KVERREL}%{?variant} Requires: kernel-%{?variant:%{variant}-}modules-uname-r = %{KVERREL}%{?variant} @@ -452,7 +422,6 @@ Source90: filter-x86_64.sh Source91: filter-armv7hl.sh Source92: filter-i686.sh Source93: filter-aarch64.sh -Source94: filter-ppc.sh Source95: filter-ppc64.sh Source96: filter-ppc64le.sh Source97: filter-s390x.sh @@ -473,8 +442,6 @@ Source32: config-x86-32-generic Source40: config-x86_64-generic Source50: config-powerpc-generic -Source51: config-powerpc32-generic -Source52: config-powerpc32-smp Source53: config-powerpc64 Source54: config-powerpc64p7 Source55: config-powerpc64le @@ -923,15 +890,6 @@ Provides: kernel-%{?1:%{1}-}core-uname-r = %{KVERREL}%{?1:+%{1}}\ # Now, each variant package. -%define variant_summary The Linux kernel compiled for SMP machines -%kernel_variant_package -n SMP smp -%description smp-core -This package includes a SMP version of the Linux kernel. It is -required only on machines with two or more CPUs as well as machines with -hyperthreading technology. - -Install the kernel-smp package if your machine uses two or more CPUs. - %ifnarch armv7hl %define variant_summary The Linux kernel compiled for PAE capable machines %kernel_variant_package %{pae} @@ -995,13 +953,6 @@ exit 1 %endif %endif -%if %{with_smponly} -%if !%{with_smp} -echo "Cannot build --with smponly, smp build is disabled" -exit 1 -%endif -%endif - %if "%{baserelease}" == "0" echo "baserelease must be greater than zero" exit 1 @@ -1588,7 +1539,7 @@ BuildKernel() { fi rm -f $RPM_BUILD_ROOT/lib/modules/$KernelVer/build/scripts/*.o rm -f $RPM_BUILD_ROOT/lib/modules/$KernelVer/build/scripts/*/*.o -%ifarch ppc ppc64 ppc64p7 +%ifarch ppc64 ppc64p7 cp -a --parents arch/powerpc/lib/crtsavres.[So] $RPM_BUILD_ROOT/lib/modules/$KernelVer/build/ %endif if [ -d arch/%{asmarch}/include ]; then @@ -1773,10 +1724,6 @@ BuildKernel %make_target %kernel_image %{pae} BuildKernel %make_target %kernel_image %endif -%if %{with_smp} -BuildKernel %make_target %kernel_image smp -%endif - %global perf_make \ make -s %{?cross_opts} %{?_smp_mflags} -C tools/perf V=1 WERROR=0 NO_LIBUNWIND=1 HAVE_CPLUS_DEMANGLE=1 NO_GTK2=1 NO_LIBNUMA=1 NO_STRLCPY=1 NO_BIONIC=1 prefix=%{_prefix} %if %{with_perf} @@ -2062,9 +2009,6 @@ fi}\ %kernel_variant_preun %kernel_variant_post -r kernel-smp -%kernel_variant_preun smp -%kernel_variant_post -v smp - %kernel_variant_preun %{pae} %kernel_variant_post -v %{pae} -r (kernel|kernel-smp) @@ -2217,7 +2161,6 @@ fi %kernel_variant_files %{with_up} -%kernel_variant_files %{with_smp} smp %kernel_variant_files %{with_debug} debug %kernel_variant_files %{with_pae} %{pae} %kernel_variant_files %{with_pae_debug} %{pae}debug @@ -2236,6 +2179,9 @@ fi # ||----w | # || || %changelog +* Fri May 16 2014 Josh Boyer <jwboyer(a)fedoraproject.org> +- Remove ppc32 support + * Thu May 15 2014 Josh Boyer <jwboyer(a)fedoraproject.org> - 3.15.0-0.rc5.git2.9 - Fix build fail on s390x -- 1.9.0

3 10

F20 Kernel 3.14.x / raid-check and freezes
by Reindl Harald 13 Jun '14

13 Jun '14

has anybody else faced complete freezes of a machine due raid-check? today the same as last thursday while the freeze seems not to happen by the raid-check itself according to running smokepings from outside which are green until i try to use the machine * last thursday morining around 8:30 while login in KDE * today around 9:45 AM while power on the screen and continue to re-use a existing KDE session however, after hard power off, the fsck, login in KDE and start the raid-check manually on TTY3 it continues ____________________________________________________ since the raid-check starts at 5:30 and all heavy IO from remote-backups and rsnapshot ends at 4:30 to not collide it's hardly IO-dependent [root@srv-rhsoft:~]$ cat /etc/cron.d/raid-check 30 5 * * Thu root /usr/sbin/raid-check

4 13

[PATCH] asus-nb-wmi: set wapf=4 for ASUSTeK COMPUTER INC. X75VBP & X550CA
by poma 11 Jun '14

11 Jun '14

Need to set wapf to 4 for ASUSTeK COMPUTER INC. X75VBP & X550CA, so that the wireless network adapter is enabled. References: - asus-nb-wmi: set wapf=4 for ASUSTeK COMPUTER INC. X75VBP http://marc.info/?l=linux-kernel&m=139819918125110 - Ath9k WiFi now disabled by radio killswitch https://bugzilla.redhat.com/show_bug.cgi?id=1089731 Reported-by: poma <pomidorabelisima(a)gmail.com> Reported-by: Andreas Utterberg <andreas.utterberg(a)thundera.se> Tested-by: poma <pomidorabelisima(a)gmail.com> Tested-by: Andreas Utterberg <andreas.utterberg(a)thundera.se> Cc: Fedora kernel development <kernel(a)lists.fedoraproject.org> Cc: Andreas Utterberg <andreas.utterberg(a)thundera.se> Cc: Josh Boyer <jwboyer(a)fedoraproject.org> Cc: Stanislaw Gruszka <sgruszka(a)redhat.com> --- drivers/platform/x86/asus-nb-wmi.c | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/drivers/platform/x86/asus-nb-wmi.c b/drivers/platform/x86/asus-nb-wmi.c index 563f59e..d3641e0 100644 --- a/drivers/platform/x86/asus-nb-wmi.c +++ b/drivers/platform/x86/asus-nb-wmi.c @@ -137,6 +137,15 @@ static struct dmi_system_id asus_quirks[] = { }, { .callback = dmi_matched, + .ident = "ASUSTeK COMPUTER INC. X550CA", + .matches = { + DMI_MATCH(DMI_SYS_VENDOR, "ASUSTeK COMPUTER INC."), + DMI_MATCH(DMI_PRODUCT_NAME, "X550CA"), + }, + .driver_data = &quirk_asus_x401u, + }, + { + .callback = dmi_matched, .ident = "ASUSTeK COMPUTER INC. X55A", .matches = { DMI_MATCH(DMI_SYS_VENDOR, "ASUSTeK COMPUTER INC."), @@ -182,6 +191,15 @@ static struct dmi_system_id asus_quirks[] = { }, { .callback = dmi_matched, + .ident = "ASUSTeK COMPUTER INC. X75VBP", + .matches = { + DMI_MATCH(DMI_SYS_VENDOR, "ASUSTeK COMPUTER INC."), + DMI_MATCH(DMI_PRODUCT_NAME, "X75VBP"), + }, + .driver_data = &quirk_asus_x401u, + }, + { + .callback = dmi_matched, .ident = "ASUSTeK COMPUTER INC. 1015E", .matches = { DMI_MATCH(DMI_SYS_VENDOR, "ASUSTeK COMPUTER INC."), -- 1.9.0

3 11

kernel*-uname-r missing in rawhide kernels?
by Sandro "red" Mathys 21 May '14

21 May '14

[red_trela@zalem ~]$ sudo yum update Error: package kernel-3.15.0-0.rc4.git3.1.fc21.x86_64 requires kernel-core-uname-r = 3.15.0-0.rc4.git3.1.fc21.x86_64, but none of the providers can be installed [red_trela@zalem ~]$ sudo yum update Downloads/kernel-* Error: package kernel-3.15.0-0.rc4.git3.1.fc21.x86_64 requires kernel-core-uname-r = 3.15.0-0.rc4.git3.1.fc21.x86_64, but none of the providers can be installed [red_trela@zalem ~]$ file Downloads/kernel-core-3.15.0-0.rc5.git3.1.fc21.x86_64.rpm Downloads/kernel-core-3.15.0-0.rc5.git3.1.fc21.x86_64.rpm: RPM v3.0 bin i386/x86_64 kernel-core-3.15.0-0.rc5.git3.1.fc21 What's up with that? According to koji, there's two weeks between these releases (why haven't they hit the rawhide repo yet?), that also means the issue's been around for a while now already. Also: [red_trela@zalem ~]$ uname -r 3.15.0-0.rc5.git1.1.fc21.x86_64 Isn't that supposed to be newer than kernel*-3.15.0-0.rc4.git3.1.fc21.x86_64? Any explanation as to why it trying to upgrade to a older version? -- Sandro

1 1

Apr/May Fedora kernel release overview
by Josh Boyer 20 May '14

20 May '14

Hi All, A brief release overview of the past several weeks below. If you have any questions, please chime in! F19: Currently at 3.13.11 but should be rebasing to the 3.14.4 kernel that has been in updates-testing very soon. F20: Currently at 3.14.4. Nothing pending. The upstream stable maintainer has been behind in doing stable releases and still has several hundred patches to wade through. More 3.14.y updates will be coming as he works through the backlog. Hans has been working on several backlight issues in F20 (and F19). There are a number of models fixed, but several still remain. If you are having backlight issues, take a look at his blog post on how to debug these: http://hansdegoede.livejournal.com/13889.html Many thanks to the reporters and testers on the existing bugs, and especially to Hans! Rawhide (F21): Currently at 3.15.0-0.rc5.git3.1. Continuing towards 3.15 final. We've had several packaging changes in rawhide over the past few weeks. The kernel-core/kernel-modules split landed and has, from all indications, been much of a non-event after the first few days. That is good to see, since it should be minimal impact. We also enabled two features that Kyle McMartin provided. The first is that the kernel packages will now have Provides(foo.ko) included for every kernel module the package provides. That lets us switch Requires from specific kernel packages (like kernel-modules-extra) to Requires on the specific kernel modules needed. With that we can move modules between packages more freely without breaking dependencies in the userspace packages that need certain modules. Kyle's other feature was to compress the installed modules with xz. The kmod utility has been able to handle compressed modules for quite some time. This actually has significant space savings on the installed size, and the performance impact on module loading is pretty negligible. Combined with the kernel packaging split, this should make the Cloud people rather happy. Thanks Kyle! As I mentioned above, if you have any questions or comments, please feel free to ask on the list. josh

2 1

[PATCH] kernel metapackage shouldn't depend on subpackages we don't build
by Dan Horák 19 May '14

19 May '14

On %{nobuildarches} we don't build the real kernel and modules, so don't set a Requires for them. The positive effect is that we can eliminate an explicit kernel Provides from the fake-build-provides package in secondary kojis. --- kernel.spec | 2 ++ 1 file changed, 2 insertions(+) diff --git a/kernel.spec b/kernel.spec index 11352bc..fb59502 100644 --- a/kernel.spec +++ b/kernel.spec @@ -402,8 +402,10 @@ Release: %{pkg_release} # SET %%nobuildarches (ABOVE) INSTEAD ExclusiveArch: %{all_x86} x86_64 ppc ppc64 ppc64p7 s390 s390x %{arm} aarch64 ppc64le ExclusiveOS: Linux +%ifnarch %{nobuildarches} Requires: kernel-%{?variant:%{variant}-}core-uname-r = %{KVERREL}%{?variant} Requires: kernel-%{?variant:%{variant}-}modules-uname-r = %{KVERREL}%{?variant} +%endif # -- 1.9.0

2 1

[PATCH] kernel metapackage shouldn't depend on subpackages we don't build
by Dan Horák 19 May '14

19 May '14

On %{nobuildarches} we don't build the real kernel and modules, so don't set a Requires for them. The positive effect is that we can eliminate an explicit kernel Provides from the fake-build-provides package in secondary kojis. --- kernel.spec | 2 ++ 1 file changed, 2 insertions(+) diff --git a/kernel.spec b/kernel.spec index 11352bc..e33aae2 100644 --- a/kernel.spec +++ b/kernel.spec @@ -402,8 +402,10 @@ Release: %{pkg_release} # SET %%nobuildarches (ABOVE) INSTEAD ExclusiveArch: %{all_x86} x86_64 ppc ppc64 ppc64p7 s390 s390x %{arm} aarch64 ppc64le ExclusiveOS: Linux +%if ! %{nobuildarches} Requires: kernel-%{?variant:%{variant}-}core-uname-r = %{KVERREL}%{?variant} Requires: kernel-%{?variant:%{variant}-}modules-uname-r = %{KVERREL}%{?variant} +%endif # -- 1.9.0

2 1

CVE-2014-0196 F19/F20
by Reindl Harald 13 May '14

13 May '14

Hi * Tue May 06 2014 Josh Boyer <jwboyer(a)fedoraproject.org> - CVE-2014-0196 pty race leading to memory corruption (rhbz 1094232 1094240) is that only missing in the kernel-3.14.3-100.fc19 but present or only kernel-3.14.3-200.fc20 for now contains that fix? there was also a warning on the CentOS list for that issue -------- Original-Nachricht -------- Betreff: [CentOS] Heads up on local root escalation Datum: Mon, 12 May 2014 19:13:12 +0100 Von: James Hogarth <james.hogarth(a)gmail.com> Antwort an: CentOS mailing list <centos(a)centos.org> An: CentOS mailing list <centos(a)centos.org> Remember to be especially aware if you have systems that can potentially have code uploaded and run (ftp to httpd vhost or improper php config and file ownership/permissions). This does not affect el5 ... an el6 update is pending. https://access.redhat.com/security/cve/CVE-2014-0196

2 2

Slow boot due to USB errors
by drago01 12 May '14

12 May '14

Hi, Startup finished in 8.394s (firmware) + 590ms (loader) + 918ms (kernel) + 19.389s (initrd) + 1.940s (userspace) = 31.234s ~19.4 seconds during initrd seems like a bit much ... looking at the log output I have noticed this: [ 3.306309] usb 1-4: new full-speed USB device number 3 using xhci_hcd [ 5.502178] usb 1-4: unable to read config index 0 descriptor/start: -71 [ 5.502190] usb 1-4: can't read configurations, error -71 [ 5.655591] usb 1-4: new full-speed USB device number 4 using xhci_hcd [ 7.699049] usb 1-4: unable to read config index 0 descriptor/start: -71 [ 7.699060] usb 1-4: can't read configurations, error -71 [ 7.851791] usb 1-4: new full-speed USB device number 5 using xhci_hcd [ 9.895842] usb 1-4: unable to read config index 0 descriptor/start: -71 [ 9.895854] usb 1-4: can't read configurations, error -71 [ 9.895997] hub 1-0:1.0: unable to enumerate USB device on port 4 [ 10.048994] usb 1-5: new high-speed USB device number 6 using xhci_hcd [ 10.363192] usb 1-5: New USB device found, idVendor=0bda, idProduct=58b1 [ 10.363202] usb 1-5: New USB device strings: Mfr=3, Product=1, SerialNumber=2 [ 10.363208] usb 1-5: Product: FJ Camera [ 10.363212] usb 1-5: Manufacturer: Generic [ 10.363215] usb 1-5: SerialNumber: 200901010001 [ 10.519824] usb 1-7: new full-speed USB device number 7 using xhci_hcd [ 10.684975] usb 1-7: New USB device found, idVendor=8087, idProduct=07dc [ 10.684986] usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 10.942675] usb 1-4: new full-speed USB device number 8 using xhci_hcd [ 13.139694] usb 1-4: unable to read config index 0 descriptor/start: -71 [ 13.139731] usb 1-4: can't read configurations, error -71 [ 13.292830] usb 1-4: new full-speed USB device number 9 using xhci_hcd [ 15.489755] usb 1-4: unable to read config index 0 descriptor/start: -71 [ 15.489766] usb 1-4: can't read configurations, error -71 [ 15.642970] usb 1-4: new full-speed USB device number 10 using xhci_hcd [ 17.687316] usb 1-4: unable to read config index 0 descriptor/start: -71 [ 17.687328] usb 1-4: can't read configurations, error -71 [ 17.840189] usb 1-4: new full-speed USB device number 11 using xhci_hcd [ 19.884509] usb 1-4: unable to read config index 0 descriptor/start: -71 [ 19.884522] usb 1-4: can't read configurations, error -71 [ 19.884617] hub 1-0:1.0: unable to enumerate USB device on port 4 [ 19.919050] PM: Starting manual resume from disk [ 19.940256] EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: (null) [ 20.172347] usb 1-4: new full-speed USB device number 12 using xhci_hcd So the questions are 1) what do those message actually mean? Seems like everything works anyway 2) why do those block the boot process ... its not like the root fs is on a usb driver or something. Kernel is 3.14.3-200.fc20.x86_64 (but does this not seem to matter it happens for pretty much every kernel for almost every but not all boot ups). Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 007: ID 8087:07dc Intel Corp. Bus 001 Device 006: ID 0bda:58b1 Realtek Semiconductor Corp. Bus 001 Device 012: ID 04f3:009b Elan Microelectronics Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Any ideas where to investigate? Those error messages are really cryptic and do not tell me anything. Thanks

5 15

[PATCH 0/4] Input: Add INPUT_PROP_TOPBUTTONPAD device property to Fedora kernels
by Hans de Goede 10 May '14

10 May '14

Hi All, Now that INPUT_PROP_TOPBUTTONPAD has landed in Linus' tree, upstream xorg-x11-drv-synaptics is relying on it as the one and only way to identify clickpads with top buttons (as found on all new lenovo laptops). Currently in Fedora we have a set of udev rules, which need to be expanded for each new model, instead of using INPUT_PROP_TOPBUTTONPAD. Now that yet another Lenovo model has surfaced with this type of touchpad: https://bugzilla.redhat.com/show_bug.cgi?id=1096436 I would like to move Fedora to the solution upstream is using. The first step for this would be to add these 4 patches to the Fedora kernels. I've also send them to stable, and Dmitry Torokhov and Greg KH are both ok with them going into stable. But Greg has a bit of a backlog atm. For now I'll just extend the udev rules in xorg-x11-drv-synaptics for this one more model, since otherwise things will break for people not using the very latest Fedora kernel. Once these changes have been in Fedora kernels for a while I plan to rebase xorg-x11-drv-synaptics to the latest upstream, making it rely on INPUT_PROP_TOPBUTTONPAD and avoiding the need to update it for each new laptop model with such a touchpad. Regards, Hans

2 7

Stable kernel testing
by poma 09 May '14

09 May '14

bodhi, autoqa, hreindl, drago01, roshi, bradw, aleph, bojan, Anonymous Tester, freddyw, dandim, amluto, csouth3, mstevens, abderrahman, amessina, bitlord, xosevp, quickbooks, gkulyk, rdieter, jforbes and arcfi. Guys, which of you uses the debug version of the kernel for testing it? poma Ref. https://admin.fedoraproject.org/updates/FEDORA-2014-5808/kernel-3.14.2-200.…

5 6

[PATCH] kernel.spec: xz compress modules on i686 and x86_64
by Kyle McMartin 07 May '14

07 May '14

Pretty grody, but it seems to be working... it has to happen after module signing (obviously) and after find-debuginfo.sh runs as well, so tacking it onto the end seems sensible, and then just fixing up the file lists as we go. Provides a nice tidy savings to the disk footprint: kyle@dreadnought:~% for i in kernel-core-3.15.0-0.rc3.git4.1.fc21.x86_64.rpm \ kernel-core-3.15.0-0.rc3.git4.1.fc21.x86_64.rpm.1; do \ rpm -qip $i | grep '^Size'; done Size : 43011603 Size : 81106737 kmod has handed .xz and .gz modules for a long time now, and can cope. I was thinking we might also %ghost the .ko, and have a %post install script that un-xz the modules in /proc/modules, but none of them are big enough for that to be worthwhile I think (maybe XFS, but I doubt it.) --Kyle --- a/kernel.spec +++ b/kernel.spec @@ -12,8 +12,14 @@ Summary: The Linux kernel # architectures are added. %ifarch %{ix86} x86_64 %global signmodules 1 +%global zipmodules 1 %else %global signmodules 0 +%global zipmodules 0 +%endif + +%if %{zipmodules} +%global zipsed -e 's/\.ko$/\.ko.xz/' %endif # % define buildid .local @@ -1713,9 +1719,9 @@ BuildKernel() { # Make sure the files lists start with absolute paths or rpmbuild fails. # Also add in the dir entries - sed -e 's/^lib*/\/lib/' $RPM_BUILD_ROOT/k-d.list > ../kernel${Flavour:+-${Flavour}}-modules.list - sed -e 's/^lib*/%dir \/lib/' $RPM_BUILD_ROOT/module-dirs.list > ../kernel${Flavour:+-${Flavour}}-core.list - sed -e 's/^lib*/\/lib/' $RPM_BUILD_ROOT/modules.list >> ../kernel${Flavour:+-${Flavour}}-core.list + sed -e 's/^lib*/\/lib/' %{?zipsed} $RPM_BUILD_ROOT/k-d.list > ../kernel${Flavour:+-${Flavour}}-modules.list + sed -e 's/^lib*/%dir \/lib/' %{?zipsed} $RPM_BUILD_ROOT/module-dirs.list > ../kernel${Flavour:+-${Flavour}}-core.list + sed -e 's/^lib*/\/lib/' %{?zipsed} $RPM_BUILD_ROOT/modules.list >> ../kernel${Flavour:+-${Flavour}}-core.list # Cleanup rm -f $RPM_BUILD_ROOT/k-d.list @@ -1836,6 +1842,9 @@ popd %{modsign_cmd} signing_key.priv.sign signing_key.x509.sign $RPM_BUILD_ROOT/lib/modules/%{KVERREL}/ \ fi \ fi \ + if [ "%{zipmodules}" -eq "1" ]; then \ + find $RPM_BUILD_ROOT/lib/modules/ -type f -name '*.ko' | xargs xz; \ + fi \ %{nil} ###

3 5

2 input + 2 backlight bug-fix patches which I would like to add to the Fedora kernels
by Hans de Goede 06 May '14

06 May '14

Hi All, FYI I've just added a patch with another set of acpi-video backlight quirks to the fedora kernel pkgs. This should be non controversial since upstream has agreed to maintain the quirk table for now, until it is certain that switch to using video.use_native_backlight=1 as default can be safely done. There are 4 more patches which I would like to add to the kernel to fix various bigs, I've attached them here. Here is the changelog from my (local) spec file modifications: - Add a patch to fix the Synaptics Touch Pad V 103S found on some keyboard docks for win8 tablets - Add a patch to fix the elantech touchpad on Gigabyte U2442 laptops - Add a patch to fix backlight control on the Samsung NC210/NC110 (rhbz#861573) - Add a patch to fix backlight & wifi on the Asus EEE PC 1015PX (rhbz#1067181) The first patch has been reviewed upstream (but not yet applied). The second and third patch should be uncontroversial and get accepted upstream. The fourth patch may turn out to be a bit controversial when someone upstream actually gets around to review it. But there seems to be no other way, and the user has been applying the same fix from the kernel cmdline for months now. All of them have a Cc: stable Regards, Hans

3 3

with_dbgonly
by poma 06 May '14

06 May '14

$ diff kernel-3.15.0-0.rc4.git0.3.fc21.src/kernel.spec \ > kernel-3.15.0-0.rc4.git0.1.fc21.src/kernel.spec 37c37 < %global baserelease 3 --- > %global baserelease 1 644,645d643 < Patch30000: cachelines-revert.patch < 1367,1368d1364 < ApplyPatch cachelines-revert.patch < 2231a2228,2231 > * Mon May 05 2014 Josh Boyer <jwboyer(a)fedoraproject.org> - 3.15.0-0.rc4.git0.1 > - Linux v3.15-rc4 > - Disable debugging options. > $ rpmbuild -ba --with dbgonly --without debuginfo --target=`uname -m` kernel.spec $ ls -1 kernel-3.15.0-0.rc4.git0.3.fc21.i686.rpm <- kernel-3.15.0-0.rc4.git0.3.fc21.src.rpm kernel-debug-3.15.0-0.rc4.git0.3.fc21.i686.rpm kernel-debug-core-3.15.0-0.rc4.git0.3.fc21.i686.rpm kernel-debug-devel-3.15.0-0.rc4.git0.3.fc21.i686.rpm kernel-debug-modules-3.15.0-0.rc4.git0.3.fc21.i686.rpm kernel-debug-modules-extra-3.15.0-0.rc4.git0.3.fc21.i686.rpm kernel-headers-3.15.0-0.rc4.git0.3.fc21.i686.rpm Is the "kernel-3.15.0-0.rc4.git0.3.fc21.i686.rpm" superfluous, given that it should belong to the 'baseonly'? poma

1 0

New package naming scheme
by poma 05 May '14

05 May '14

There is a discrepancy in the terminology of these two packages: - kernel-drivers[1] - kernel-modules-extra Are these[1] modules passed the driving test? Should I read the "Banana Split" thread, again? Perhaps the "kernel-modules" for the "kernel-drivers" is the proper name. poma

8 12

kernel-core pulls linux-firmware
by Reindl Harald 01 May '14

01 May '14

Hi where is this dependency from? after confirm you can happily "yum remove linux-firmware" without any problems and the next kernel update pulls it again which is not how a normal dependency works because it would not allow to uninstall the dependency without remove the pulling package hence why i have on our virtualized infrastructure for years a empty meta-package with provides/obsoletes but given now that we have "kernel-core" and "kernel-drivers" this dependecy should be only pulled only by "kernel-drivers" _____________________________________________________ ---> Package kernel-core.x86_64 0:3.15.0-0.rc3.git3.1.fc21 will be installed --> Processing Dependency: linux-firmware >= 20130724-29.git31f6b30 for package: kernel-core-3.15.0-0.rc3.git3.1.fc21.x86_64 ---> Package libcap-ng.x86_64 0:0.7.4-1.fc21 will be updated ---> Package libcap-ng.x86_64 0:0.7.4-2.fc21 will be an update ---> Package lyx-fonts.noarch 0:2.1.0-0.fc21 will be updated ---> Package lyx-fonts.noarch 0:2.1.0-2.fc21 will be an update ---> Package vim-minimal.x86_64 2:7.4.258-1.fc21 will be updated ---> Package vim-minimal.x86_64 2:7.4.258-2.fc21 will be an update --> Running transaction check ---> Package linux-firmware.noarch 0:20140317-37.gitdec41bce.fc21 will be installed --> Finished Dependency Resolution --> Finding unneeded leftover dependencies Found and removing 0 unneeded dependencies _____________________________________________________ Name : linux-firmware Arch : noarch Version : 20140317 Release : 37.gitdec41bce.fc21 Size : 50 M Repo : installed _____________________________________________________ [root@rawhide ~]# rpm -qa | grep kernel kernel-core-3.15.0-0.rc3.git3.1.fc21.x86_64 kernel-core-3.15.0-0.rc3.git1.10.fc21.x86_64 _____________________________________________________ Is this ok [y/N]: y Downloading packages: Running transaction check Running transaction test Transaction test succeeded Running transaction Erasing : linux-firmware-20140317-37.gitdec41bce.fc21.noarch 1/1 Verifying : linux-firmware-20140317-37.gitdec41bce.fc21.noarch 1/1 Removed: linux-firmware.noarch 0:20140317-37.gitdec41bce.fc21 _____________________________________________________ [root@rawhide ~]# rpm -qa | grep kernel kernel-core-3.15.0-0.rc3.git3.1.fc21.x86_64 kernel-core-3.15.0-0.rc3.git1.10.fc21.x86_64

2 2

RFE: enable uas in 3.15 kernels
by Hans de Goede 01 May '14

01 May '14

Hi All, I would like to suggest to enable uas in the 3.15 kernel: CONFIG_USB_UAS=m For all platforms. Usb Attached Scsi is a standard, much improved usb storage protocol allowing the use of NCQ over usb, and slowly more devices are hitting the market supporting it. Besides being a whole lot faster, I also put 1.5 months of full-time work in getting it into shape and getting it of the CONFIG_BROKEN list upstream, which has now all finally landed. So I also have a small personal bias towards enabling it :) Regards, Hans

2 3

Re: [kernel] Add use_native_backlight quirk for 4 laptops (rhbz 983342 1093120)
by Josh Boyer 01 May '14

01 May '14

On Thu, May 1, 2014 at 8:51 AM, Hans de Goede <jwrdegoede(a)fedoraproject.org> wrote: > commit f22ebd0b2b7a7d5d07367c5c50f81185b9fa672b > Author: Hans de Goede <hdegoede(a)redhat.com> > Date: Thu May 1 14:51:32 2014 +0200 > > Add use_native_backlight quirk for 4 laptops (rhbz 983342 1093120) > > ...Add-4-new-models-to-the-use_native_backli.patch | 89 ++++++++++++++++++++ > kernel.spec | 9 ++ > 2 files changed, 98 insertions(+), 0 deletions(-) Hi Hans, In the future, could you please refrain from committing patches like this directly without any heads up or discussion? A quick post to this list with a link to the upstream submission is ideal. I really appreciate the effort your putting in on the backlight stuff here, but this patch was committed before it was even reviewed upstream. The previous incarnation of it was rejected because a supposed fix is coming in 3.16. It's certainly reasonable for Fedora to carry this until 3.16 lands, but I'd like it if we can get some agreement from upstream one way or another. There's no major rush at this point, particularly for rawhide. Thanks. josh

2 1

kernel-3.15.0-0.rc3.git1.10.fc21 - noarch
by poma 01 May '14

01 May '14

kernel-3.15.0-0.rc3.git1.10.fc21.noarch.rpm 'noarch', what is it for? ... Package: kernel-3.15.0-0.rc3.git1.10.fc21.noarch - can't co-install with kernel-3.15.0-0.rc3.git1.10.fc21.x86_64 Resolving Dependencies --> Running transaction check ---> Package kernel.x86_64 0:3.15.0-0.rc3.git1.10.fc21 will be installed --> Processing Dependency: kernel-drivers-uname-r = 3.15.0-0.rc3.git1.10.fc21.x86_64 for package: kernel-3.15.0-0.rc3.git1.10.fc21.x86_64 --> Processing Dependency: kernel-core-uname-r = 3.15.0-0.rc3.git1.10.fc21.x86_64 for package: kernel-3.15.0-0.rc3.git1.10.fc21.x86_64 ... ... Package: kernel-3.15.0-0.rc3.git1.10.fc21.noarch - can't co-install with kernel-3.15.0-0.rc3.git1.10.fc21.i686 Resolving Dependencies --> Running transaction check ---> Package kernel.i686 0:3.15.0-0.rc3.git1.10.fc21 will be installed --> Processing Dependency: kernel-drivers-uname-r = 3.15.0-0.rc3.git1.10.fc21.i686 for package: kernel-3.15.0-0.rc3.git1.10.fc21.i686 --> Processing Dependency: kernel-core-uname-r = 3.15.0-0.rc3.git1.10.fc21.i686 for package: kernel-3.15.0-0.rc3.git1.10.fc21.i686 ... Thanks. poma

4 4

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

kernel May 2014