February 2014 - kernel - Fedora mailing-lists

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

04 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

Feb. Fedora Kernel Patch Report
by Josh Boyer 31 Mar '14

31 Mar '14

It's been a while since I sent one of these. Mostly that's due to the overlap between which upstream stable version we're using in Fedora across the releases, and how fast those have been happening upstream. We're settled on 3.13.y now, and with 3.14-rc4 out there things have calmed down enough to take stock again. Here's the patches we have on top of 3.13.5. josh fs-proc-devtree-remove_proc_entry.patch - Upstream commit c1d867a54d426b45da017fbe8e585f8a3064ce8d drm-radeon-Disable-writeback-by-default-on-ppc.patch - This is superseded by upstream commit ea31bf697d27270188a93cd78cf9de4bc968aca3 but that seems to be a bit big for a stable backport dm-cache-policy-mq_fix-large-scale-table-allocation-bug.patch (rhbz 993744) - Still pending upstream (no idea why...) sunrpc-create-a-new-dummy-pipe-for-gssd-to-hold-open.patch sunrpc-replace-gssd_running-with-more-reliable-check.patch nfs-check-gssd-running-before-krb5i-auth.patch - Added to fix a 15sec mount delay - Upstream commits 4b9a445e3eeb8bd9278b1ae51c1b3a651e370cd6 89f842435c630f8426f414e6030bc2ffea0d6f81 6aa23d76a7b549521a03b63b6d5b7880ea87eab7 respectively rpc_pipe-remove-the-clntXX-dir-if-creating-the-pipe-fails.patch sunrpc-add-an-info-file-for-the-dummy-gssd-pipe.patch rpc_pipe-fix-cleanup-of-dummy-gssd-directory-when-notification-fails.patch - Fixes for some of the patches above (rhbz 1037793) - Upstream commits 3396f92f8be606ea485b0a82d4e7749a448b013b e2f0c83a9de331d9352185ca3642616c13127539 23e66ba97127ff3b064d4c6c5138aa34eafc492f respectively elantech-Properly-differentiate-between-clickpads-an.patch (rhbz 1030802) - Upstream commit c15bdfd5b9831e4cab8cfc118243956e267dd30e KVM-MMU-handle-invalid-root_hpa-at-__direct_map.patch (rhbz 924916) - Upstream commit 989c6b34f6a9480e397b170cc62237e89bf4fdb9 - Probably should grab 37f6a4e237303549c8676dfe1fd1991ceab512eb too KVM-VMX-fix-use-after-free-of-vmx-loaded_vmcs.patch (rhbz 1047892) - Upstream commit 26a865f4aa8e66a6d94958de7656f7f1b03c6c56 0001-Input-wacom-make-sure-touch_max-is-set-for-touch-dev.patch 0002-Input-wacom-add-support-for-three-new-Intuos-devices.patch 0003-Input-wacom-add-reporting-of-SW_MUTE_DEVICE-events.patch - rhbz 1003167 1046238 - Upstream commits 1d0d6df02750b4a6f466768cbfbf860e24f4c8d4 b5fd2a3e92ca5c8c1f3c20d31ac5daed3ec4d604 961794a00eab03f4344b7d5e825e8e789e55da87 Input-ALPS-add-support-for-Dolphin-devices.patch (rhbz 953211) - Upstream commit ee65d4b36de8ddf4467f788faa5d8ddd1bfcdaa2 xhci-fix-resume-issues-on-renesas-chips-in-samsung-laptops.patch (rhbz 950630) - Upstream commit 1aa9578c1a9450fb21501c4f549f5b1edb557e6d - Oddly not queued for stable? cgroup-fixes.patch (rhbz 1045755) - Upstream commits 0ab02ca8f887908152d1a96db5130fc661d36a1e - There was a 3.12 version of this patch sent to stable list from Michal Hocko. I don't remember why it wasn't applied, or why it wasn't applied for 3.13.y... ipv6-introduce-IFA_F_NOPREFIXROUTE-and-IFA_F_MANAGETEMPADDR-flags.patch ipv6-addrconf-revert-if_inet6ifa_flag-format.patch - rhbz 1064430 1056711 - Backports of commits to add this stuff in 3.14. Not suitable for stable. cifs-ensure-that-uncached-writes-handle-unmapped-areas-correctly.patch cifs-sanity-check-length-of-data-to-send-before-sending.patch cifs-mask-off-top-byte-in-get_rfc1002_length.patch - rhbz 1064253 CVE-2014-0069 rhbz 1068862 - Upstream commit 5d81de8e8667da7135d3a32a964087c0faf5483f and two additional fixes cpufreq-powernow-k8-Initialize-per-cpu-data-structures-properly.patch (rhbz 1054408) - Upstream commit c3274763bfc3bf1ececa269ed6e6c4d7ec1c3e5e - CC'd to stable but not queued e100-Fix-disabling-already-disabled-device-warning.patch (rhbz 994438) - Upstream commit 2b6e0ca175fe4a20f21ba82b1e7ccc71029c4dd4 usb-ehci-fix-deadlock-when-threadirqs-option-is-used.patch - Still pending upstream

7 9

WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:264 dev_watchdog+0x276/0x280()
by poma 08 Mar '14

08 Mar '14

Ahoy! Debugging S3 aka suspend produces 'WARNINGS': Steps to Reproduce: # echo core > /sys/power/pm_test # cat /sys/power/pm_test none [core] processors platform devices freezer # echo mem > /sys/power/state Results: - dmesg-3.14.0-0.rc3.git0.1.fc21.x86_64+debug-pm_test-core.diff https://bugzilla.redhat.com/attachment.cgi?id=864436 Steps to Reproduce: # echo processors > /sys/power/pm_test # cat /sys/power/pm_test none core [processors] platform devices freezer # echo mem > /sys/power/state Results: - dmesg-3.14.0-0.rc3.git0.1.fc21.x86_64+debug-pm_test-processors.diff https://bugzilla.redhat.com/attachment.cgi?id=864438 Steps to Reproduce: # echo platform > /sys/power/pm_test # cat /sys/power/pm_test none core processors [platform] devices freezer # echo mem > /sys/power/state Results: - dmesg-3.14.0-0.rc3.git0.1.fc21.x86_64+debug-pm_test-platform.diff https://bugzilla.redhat.com/attachment.cgi?id=864439 RHBZ 1010764: "[abrt] NETDEV WATCHDOG: em1 (e1000e): transmit queue 0 timed out" https://bugzilla.redhat.com/show_bug.cgi?id=1010764 Tested with Rawhide 'kernel-debug-3.14.0-0.rc3.git0.1.fc21.x86_64' http://koji.fedoraproject.org/koji/buildinfo?buildID=498711 poma

2 6

Bluetooth virtual HCI driver ver 1.3
by poma 06 Mar '14

06 Mar '14

3.13.0-0.rc7.git2.2.fc21.x86_64: depmod: ERROR: Module 'hci_vhci' has devname (vhci) but lacks major and minor information. Ignoring. poma

2 3

BUG: unable to handle kernel paging request at 0000000100000003 - Oops: 0000 [#1] SMP
by poma 03 Mar '14

03 Mar '14

Affected kernels - 3.14.0-0.rc3*: - 3.14.0-0.rc3.git0.1 http://koji.fedoraproject.org/koji/buildinfo?buildID=498711 - 3.14.0-0.rc3.git0.7 based on 3.14.0-0.rc3.git0.1 - 3.14.0-0.rc3.git2.1 http://koji.fedoraproject.org/koji/buildinfo?buildID=499061 - 3.14.0-0.rc3.git5.1 http://koji.fedoraproject.org/koji/buildinfo?buildID=499636 Memtest86+ 4.20 - OK http://goo.gl/1nm1nV RHBZ https://bugzilla.redhat.com/show_bug.cgi?id=1067919 messages-Oops-es-3.14.0-0.rc3 https://bugzilla.redhat.com/attachment.cgi?id=865926 poma

3 4

[PATCH] Enable USB gadget subsystem outside ARM
by Lubomir Rintel 27 Feb '14

27 Feb '14

It's generally useful. On other architectures the UDC capable hardware might not be very common, but the dummy HCD makes it possible to use such hardware for development and emulation of USB gadget driver code. --- Hi, I'm wondering if you could apply this? Thank you! Lubo config-armv7-generic | 56 ------------------------------------------------- config-debug | 5 +++++ config-generic | 59 ++++++++++++++++++++++++++++++++++++++++++++++++---- config-nodebug | 3 +++ mod-extra.list | 28 +++++++++++++++++++++++++ 5 files changed, 91 insertions(+), 60 deletions(-) diff --git a/config-armv7-generic b/config-armv7-generic index 8215e60..c43601f 100644 --- a/config-armv7-generic +++ b/config-armv7-generic @@ -180,62 +180,6 @@ CONFIG_AX88796_93CX6=y CONFIG_USB_ISP1760_HCD=m # CONFIG_USB_EHCI_HCD_ORION is not set -# usb gadget -CONFIG_USB_GADGET=m -CONFIG_USB_GADGET_MUSB_HDRC=m -CONFIG_USB_GADGET_VBUS_DRAW=100 -CONFIG_USB_GADGET_STORAGE_NUM_BUFFERS=2 -CONFIG_USB_MUSB_HDRC=m -CONFIG_USB_MUSB_DUAL_ROLE=y -CONFIG_USB_MUSB_DSPS=m -CONFIG_USB_GPIO_VBUS=m -CONFIG_USB_G_ACM_MS=m -CONFIG_USB_G_DBGP=m -CONFIG_USB_G_DBGP_PRINTK=y -CONFIG_USB_G_DBGP_SERIAL=y -CONFIG_USB_G_MULTI=m -CONFIG_USB_G_MULTI_CDC=y -# CONFIG_USB_G_MULTI_RNDIS is not set -CONFIG_USB_G_NCM=m -CONFIG_USB_G_SERIAL=m -CONFIG_USB_ETH_EEM=y -# CONFIG_USB_ETH_RNDIS is not set -CONFIG_USB_CDC_COMPOSITE=m -CONFIG_USB_GADGET_TARGET=m -CONFIG_USB_MASS_STORAGE=m -CONFIG_USB_CONFIGFS=m -CONFIG_USB_CONFIGFS_ACM=y -CONFIG_USB_CONFIGFS_ECM=y -CONFIG_USB_CONFIGFS_ECM_SUBSET=y -CONFIG_USB_CONFIGFS_EEM=y -CONFIG_USB_CONFIGFS_MASS_STORAGE=y -CONFIG_USB_CONFIGFS_NCM=y -CONFIG_USB_CONFIGFS_OBEX=y -# CONFIG_USB_CONFIGFS_RNDIS is not set -CONFIG_USB_CONFIGFS_SERIAL=y -CONFIG_USB_CONFIGFS_STORAGE=y - -# CONFIG_MUSB_PIO_ONLY is not set -# CONFIG_USB_MUSB_DEBUG is not set -# CONFIG_USB_GADGET_DEBUG is not set -# CONFIG_USB_GADGET_DEBUG_FILES is not set -# CONFIG_USB_GADGET_DEBUG_FS is not set -# CONFIG_USB_FUSB300 is not set -# CONFIG_USB_RENESAS_USBHS is not set -# CONFIG_USB_FOTG210_UDC is not set -# CONFIG_USB_R8A66597 is not set -# CONFIG_USB_PXA27X is not set -# CONFIG_USB_MV_UDC is not set -# CONFIG_USB_MV_U3D is not set -# CONFIG_USB_M66592 is not set -# CONFIG_USB_AMD5536UDC is not set -# CONFIG_USB_NET2272 is not set -# CONFIG_USB_NET2280 is not set -# CONFIG_USB_GOKU is not set -# CONFIG_USB_EG20T is not set -# CONFIG_USB_DUMMY_HCD is not set -# CONFIG_USB_ZERO_HNPTEST is not set - # Multifunction Devices CONFIG_MFD_TPS65090=y CONFIG_MFD_TPS65217=y diff --git a/config-debug b/config-debug index 8000b4e..6103fdc 100644 --- a/config-debug +++ b/config-debug @@ -126,3 +126,8 @@ CONFIG_EDAC_DEBUG=y CONFIG_X86_DEBUG_STATIC_CPU_HAS=y CONFIG_LATENCYTOP=y CONFIG_SCHEDSTATS=y + +CONFIG_USB_GADGET_DEBUG=y +CONFIG_USB_GADGET_DEBUG_FILES=y +CONFIG_USB_GADGET_DEBUG_FS=y +CONFIG_USB_GADGET_VERBOSE=y diff --git a/config-generic b/config-generic index 1624883..6e5d93a 100644 --- a/config-generic +++ b/config-generic @@ -3673,7 +3673,6 @@ CONFIG_USB_ARMLINUX=y CONFIG_USB_EPSON2888=y CONFIG_USB_KC2190=y -# CONFIG_USB_MUSB_HDRC is not set # CONFIG_USB_CHIPIDEA is not set # @@ -3764,7 +3763,6 @@ CONFIG_USB_EZUSB=y CONFIG_USB_EMI62=m CONFIG_USB_LED=m # CONFIG_USB_CYPRESS_CY7C63 is not set -CONFIG_USB_G_SERIAL=m # # USB Miscellaneous drivers @@ -3798,9 +3796,62 @@ CONFIG_USB_ETH=m CONFIG_USB_FTDI_ELAN=m CONFIG_USB_FILE_STORAGE=m # CONFIG_USB_FILE_STORAGE_TEST is not set -# CONFIG_USB_GADGET is not set + +# usb gadget +CONFIG_USB_GADGET=m +CONFIG_USB_GADGET_MUSB_HDRC=m +CONFIG_USB_GADGET_VBUS_DRAW=100 +CONFIG_USB_GADGET_STORAGE_NUM_BUFFERS=2 +CONFIG_USB_MUSB_HDRC=m +CONFIG_USB_MUSB_DUAL_ROLE=y +CONFIG_USB_MUSB_DSPS=m +CONFIG_USB_G_ACM_MS=m +CONFIG_USB_G_DBGP=m +CONFIG_USB_G_DBGP_SERIAL=y +CONFIG_USB_G_MULTI=m +CONFIG_USB_G_MULTI_CDC=y +# CONFIG_USB_G_MULTI_RNDIS is not set +CONFIG_USB_G_NCM=m +CONFIG_USB_G_SERIAL=m +CONFIG_USB_ETH_EEM=y +# CONFIG_USB_ETH_RNDIS is not set +CONFIG_USB_CDC_COMPOSITE=m +CONFIG_USB_GADGET_TARGET=m +CONFIG_USB_MASS_STORAGE=m +CONFIG_USB_CONFIGFS=m +CONFIG_USB_CONFIGFS_ACM=y +CONFIG_USB_CONFIGFS_ECM=y +CONFIG_USB_CONFIGFS_ECM_SUBSET=y +CONFIG_USB_CONFIGFS_EEM=y +CONFIG_USB_CONFIGFS_MASS_STORAGE=y +CONFIG_USB_CONFIGFS_NCM=y +CONFIG_USB_CONFIGFS_OBEX=y +# CONFIG_USB_CONFIGFS_RNDIS is not set +CONFIG_USB_CONFIGFS_SERIAL=y +CONFIG_USB_CONFIGFS_STORAGE=y + +# CONFIG_USB_RENESAS_USBHS is not set +# CONFIG_USB_FOTG210_UDC is not set +# CONFIG_USB_R8A66597 is not set +# CONFIG_USB_PXA27X is not set +# CONFIG_USB_MV_UDC is not set +# CONFIG_USB_MV_U3D is not set +# CONFIG_USB_M66592 is not set +# CONFIG_USB_NET2272 is not set +# CONFIG_USB_ZERO_HNPTEST is not set +# CONFIG_USB_FUSB300 is not set +# CONFIG_USB_AMD5536UDC is not set +# CONFIG_USB_NET2280 is not set +# CONFIG_USB_GOKU is not set +# CONFIG_USB_EG20T is not set +CONFIG_USB_DUMMY_HCD=m + # CONFIG_USB_DWC3 is not set -# CONFIG_USB_GADGETFS is not set +CONFIG_USB_GADGETFS=m +CONFIG_USB_FUNCTIONFS=m +CONFIG_USB_FUNCTIONFS_ETH=y +# CONFIG_USB_FUNCTIONFS_RNDIS is not set +CONFIG_USB_FUNCTIONFS_GENERIC=y # CONFIG_USB_OXU210HP_HCD is not set CONFIG_USB_IOWARRIOR=m CONFIG_USB_ISIGHTFW=m diff --git a/config-nodebug b/config-nodebug index f9f4309..72e0aab 100644 --- a/config-nodebug +++ b/config-nodebug @@ -130,3 +130,6 @@ CONFIG_DEBUG_KMEMLEAK_DEFAULT_OFF=y # CONFIG_SCHEDSTATS is not set # CONFIG_LATENCYTOP is not set +# CONFIG_USB_GADGET_DEBUG is not set +# CONFIG_USB_GADGET_DEBUG_FILES is not set +# CONFIG_USB_GADGET_DEBUG_FS is not set diff --git a/mod-extra.list b/mod-extra.list index 2803a43..2dfda76 100644 --- a/mod-extra.list +++ b/mod-extra.list @@ -193,3 +193,31 @@ orinoco_plx.ko orinoco_pci.ko orinoco_nortel.ko orinoco_usb.ko +dummy_hcd.ko +g_acm_ms.ko +g_cdc.ko +g_dbgp.ko +g_ether.ko +g_ffs.ko +g_mass_storage.ko +g_multi.ko +g_ncm.ko +g_serial.ko +g_zero.ko +gadgetfs.ko +libcomposite.ko +tcm_usb_gadget.ko +u_ether.ko +u_rndis.ko +u_serial.ko +udc-core.ko +usb_f_acm.ko +usb_f_ecm.ko +usb_f_ecm_subset.ko +usb_f_eem.ko +usb_f_mass_storage.ko +usb_f_ncm.ko +usb_f_obex.ko +usb_f_serial.ko +usb_f_ss_lb.ko +musb_hdrc.ko -- 1.8.5.3

2 4

[ARM] rtc fix and dts backport for 3.14 fedora kernel
by Nicolas Chauvet 27 Feb '14

27 Feb '14

Theses patches apply to the kernel package git module [PATCH 1/3] [ARM][TEGRA][PAZ00] Add TPS6586x RTC/Regulator as builtin [PATCH 2/3] [ARM][TEGRA][PAZ00] Add simple-panel support in dts for AC100 [PATCH 3/3] [ARM] [Wandboard] Add CONFIG_RTC_DRV_SNVS as builtin

4 18

linux-firmware - change in descriptions
by poma 27 Feb '14

27 Feb '14

The last occurrences of the "iwlagn", - RHEL6.2 /lib/modules/2.6.32-220.23.1.el6.x86_64/kernel/drivers/net/wireless/iwlwifi/iwlagn.ko - F16 /lib/modules/3.1.5-6.fc16.x86_64/kernel/drivers/net/wireless/iwlwifi/iwlagn.ko replaced by the "iwlwifi", - F20 /lib/modules/3.13.5-200.fc20.x86_64/kernel/drivers/net/wireless/iwlwifi/iwlwifi.ko - Rawhide /lib/modules/3.14.0-0.rc4.git1.1.fc21.x86_64/kernel/drivers/net/wireless/iwlwifi/iwlwifi.ko https://bugzilla.redhat.com/show_bug.cgi?id=1070600 poma

3 2

kernel-tests master: Add GPLv2 licensing information for testcase control scripts (07591b7)
by Josh Boyer 24 Feb '14

24 Feb '14

Repository : http://git.fedorahosted.org/cgit/kernel-tests.git On branch : master >--------------------------------------------------------------- commit 07591b795c64df1b3f07f27ace1d46a02c4f378a Author: Josh Boyer <jwboyer(a)redhat.com> Date: Mon Feb 24 16:20:47 2014 -0500 Add GPLv2 licensing information for testcase control scripts Be sure to note that individual testcases and code may be licensed under different terms. >--------------------------------------------------------------- performance/lmbench3/COPYING => LICENSE | 39 ++++++++++++++++++------------ default/cachedrop/runtest.sh | 2 + default/defaultpass/runtest.sh.example | 2 + default/libhugetlbfs/runtest.sh | 2 + default/modsign/modsign_tests.sh | 2 + default/modsign/runtest.sh | 2 + default/paxtest/runtest.sh | 2 + default/stack-randomness/runtest.sh | 3 ++ default/sysfs-perms/runtest.sh | 2 + default/timer-overhead/runtest.sh | 2 + destructive/destructivepass/runtest.sh | 2 + minimal/minimalfail/runtest.sh.example | 2 + minimal/minimalpass/runtest.sh.example | 2 + minimal/minimalskip/runtest.sh.example | 2 + performance/lmbench3/runtest.sh | 2 + runtests.sh | 2 + stress/ltp/diostress.sh | 2 + stress/ltp/fsstress.sh | 2 + stress/ltp/ipcstress.sh | 2 + stress/ltp/mmstress.sh | 2 + stress/ltp/runtest.sh | 2 + stress/stresspass/runtest.sh | 2 + utils/build-deps.sh | 2 + utils/loopback.sh | 2 + utils/mod-check.sh | 2 + utils/root-check.sh | 2 + 26 files changed, 74 insertions(+), 16 deletions(-) diff --git a/performance/lmbench3/COPYING b/LICENSE similarity index 93% copy from performance/lmbench3/COPYING copy to LICENSE index a43ea21..510a572 100644 --- a/performance/lmbench3/COPYING +++ b/LICENSE @@ -1,12 +1,19 @@ - GNU GENERAL PUBLIC LICENSE - Version 2, June 1991 +The framework and scripts contained in the kernel-tests package are licensed +under the GNU General Public License, version 2. Individual test cases or +code may be licensed under different terms and will be noted in the +directories or files of those test cases. A copy of GPLv2 is included below. - Copyright (C) 1989, 1991 Free Software Foundation, Inc. - 675 Mass Ave, Cambridge, MA 02139, USA +------------------------------------------------------------------------------- + + GNU GENERAL PUBLIC LICENSE + Version 2, June 1991 + + Copyright (C) 1989, 1991 Free Software Foundation, Inc., + 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. - Preamble + Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public @@ -15,7 +22,7 @@ software--to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by -the GNU Library General Public License instead.) You can apply it to +the GNU Lesser General Public License instead.) You can apply it to your programs, too. When we speak of free software, we are referring to freedom, not @@ -56,7 +63,7 @@ patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow. - GNU GENERAL PUBLIC LICENSE + GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License applies to any program or other work which contains @@ -255,7 +262,7 @@ make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. - NO WARRANTY + NO WARRANTY 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN @@ -277,9 +284,9 @@ YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. - END OF TERMS AND CONDITIONS + END OF TERMS AND CONDITIONS - Appendix: How to Apply These Terms to Your New Programs + How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it @@ -291,7 +298,7 @@ convey the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found. <one line to give the program's name and a brief idea of what it does.> - Copyright (C) 19yy <name of author> + Copyright (C) <year> <name of author> This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by @@ -303,16 +310,16 @@ the "copyright" line and a pointer to where the full notice is found. MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. - You should have received a copy of the GNU General Public License - along with this program; if not, write to the Free Software - Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. + You should have received a copy of the GNU General Public License along + with this program; if not, write to the Free Software Foundation, Inc., + 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA. Also add information on how to contact you by electronic and paper mail. If the program is interactive, make it output a short notice like this when it starts in an interactive mode: - Gnomovision version 69, Copyright (C) 19yy name of author + Gnomovision version 69, Copyright (C) year name of author Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details. @@ -335,5 +342,5 @@ necessary. Here is a sample; alter the names: This General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the -library. If this is what you want to do, use the GNU Library General +library. If this is what you want to do, use the GNU Lesser General Public License instead of this License. diff --git a/default/cachedrop/runtest.sh b/default/cachedrop/runtest.sh index e565dea..aac8623 100755 --- a/default/cachedrop/runtest.sh +++ b/default/cachedrop/runtest.sh @@ -1,4 +1,6 @@ #!/bin/sh +# +# Licensed under the terms of the GNU GPL License version 2 source ../../utils/root-check.sh diff --git a/default/defaultpass/runtest.sh.example b/default/defaultpass/runtest.sh.example index b44a7a7..729175f 100755 --- a/default/defaultpass/runtest.sh.example +++ b/default/defaultpass/runtest.sh.example @@ -1,4 +1,6 @@ #!/bin/bash +# +# Licensed under the terms of the GNU GPL License version 2 echo "sample test from the default directory, should always pass" diff --git a/default/libhugetlbfs/runtest.sh b/default/libhugetlbfs/runtest.sh index 88a45ca..18fa2c1 100755 --- a/default/libhugetlbfs/runtest.sh +++ b/default/libhugetlbfs/runtest.sh @@ -1,4 +1,6 @@ #!/bin/sh +# +# Licensed under the terms of the GNU GPL License version 2 source ../../utils/root-check.sh diff --git a/default/modsign/modsign_tests.sh b/default/modsign/modsign_tests.sh index c29124f..b0bab67 100755 --- a/default/modsign/modsign_tests.sh +++ b/default/modsign/modsign_tests.sh @@ -1,4 +1,6 @@ #!/bin/bash +# +# Licensed under the terms of the GNU GPL License version 2 modsign_check_modules() { diff --git a/default/modsign/runtest.sh b/default/modsign/runtest.sh index c6e2451..9907bb0 100755 --- a/default/modsign/runtest.sh +++ b/default/modsign/runtest.sh @@ -1,4 +1,6 @@ #!/bin/sh +# +# Licensed under the terms of the GNU GPL License version 2 source ../../utils/root-check.sh diff --git a/default/paxtest/runtest.sh b/default/paxtest/runtest.sh index 0e8e8b1..8b44626 100755 --- a/default/paxtest/runtest.sh +++ b/default/paxtest/runtest.sh @@ -1,4 +1,6 @@ #!/bin/sh +# +# Licensed under the terms of the GNU GPL License version 2 check_kill() { diff --git a/default/stack-randomness/runtest.sh b/default/stack-randomness/runtest.sh index ac519a7..77d17de 100755 --- a/default/stack-randomness/runtest.sh +++ b/default/stack-randomness/runtest.sh @@ -1,4 +1,7 @@ #!/bin/sh +# +# Licensed under the terms of the GNU GPL License version 2 + COUNT=$(for i in `seq 1 1000` ; do grep stack /proc/self/maps; done | sort -u | uniq -c | wc -l) if [ $COUNT -lt 950 ]; then diff --git a/default/sysfs-perms/runtest.sh b/default/sysfs-perms/runtest.sh index 69f5e6b..351af76 100755 --- a/default/sysfs-perms/runtest.sh +++ b/default/sysfs-perms/runtest.sh @@ -1,4 +1,6 @@ #!/bin/sh +# +# Licensed under the terms of the GNU GPL License version 2 COUNT=$(find /sys -type f -perm 666 | ./ignore-files.sh | wc -l) diff --git a/default/timer-overhead/runtest.sh b/default/timer-overhead/runtest.sh index ac43f9c..42b37df 100755 --- a/default/timer-overhead/runtest.sh +++ b/default/timer-overhead/runtest.sh @@ -1,4 +1,6 @@ #!/bin/sh +# +# Licensed under the terms of the GNU GPL License version 2 if [ ! -f ./timer-test ]; then make diff --git a/destructive/destructivepass/runtest.sh b/destructive/destructivepass/runtest.sh index 53a6967..e1fae7d 100755 --- a/destructive/destructivepass/runtest.sh +++ b/destructive/destructivepass/runtest.sh @@ -1,4 +1,6 @@ #!/bin/bash +# +# Licensed under the terms of the GNU GPL License version 2 echo "sample test from the destructive directory, should always pass" diff --git a/minimal/minimalfail/runtest.sh.example b/minimal/minimalfail/runtest.sh.example index 1efb53e..d957453 100755 --- a/minimal/minimalfail/runtest.sh.example +++ b/minimal/minimalfail/runtest.sh.example @@ -1,4 +1,6 @@ #!/bin/bash +# +# Licensed under the terms of the GNU GPL License version 2 echo "sample test from the minimal directory, should always fail" diff --git a/minimal/minimalpass/runtest.sh.example b/minimal/minimalpass/runtest.sh.example index 20905d4..783e6dc 100755 --- a/minimal/minimalpass/runtest.sh.example +++ b/minimal/minimalpass/runtest.sh.example @@ -1,4 +1,6 @@ #!/bin/bash +# +# Licensed under the terms of the GNU GPL License version 2 echo "sample test from the minimal directory, should always pass" diff --git a/minimal/minimalskip/runtest.sh.example b/minimal/minimalskip/runtest.sh.example index bc139dc..0e59579 100755 --- a/minimal/minimalskip/runtest.sh.example +++ b/minimal/minimalskip/runtest.sh.example @@ -1,4 +1,6 @@ #!/bin/bash +# +# Licensed under the terms of the GNU GPL License version 2 echo "sample test from the minimal directory, should always skip" diff --git a/performance/lmbench3/runtest.sh b/performance/lmbench3/runtest.sh index 3a81c6d..87b211d 100755 --- a/performance/lmbench3/runtest.sh +++ b/performance/lmbench3/runtest.sh @@ -1,4 +1,6 @@ #!/bin/sh +# +# Licensed under the terms of the GNU GPL License version 2 if [ -f bin/$(uname -m)-linux-gnu/$(scripts/config) ]; then make rerun diff --git a/runtests.sh b/runtests.sh index b3f7de0..1d9ad98 100755 --- a/runtests.sh +++ b/runtests.sh @@ -1,4 +1,6 @@ #!/bin/bash +# +# Licensed under the terms of the GNU GPL License version 2 date=$(date +%s) topdir=$(pwd) diff --git a/stress/ltp/diostress.sh b/stress/ltp/diostress.sh index 0bbde18..bc907de 100755 --- a/stress/ltp/diostress.sh +++ b/stress/ltp/diostress.sh @@ -1,4 +1,6 @@ #!/bin/bash +# +# Licensed under the terms of the GNU GPL License version 2 source ../../utils/loopback.sh diff --git a/stress/ltp/fsstress.sh b/stress/ltp/fsstress.sh index d4ba22f..371dcb8 100755 --- a/stress/ltp/fsstress.sh +++ b/stress/ltp/fsstress.sh @@ -1,4 +1,6 @@ #!/bin/bash +# +# Licensed under the terms of the GNU GPL License version 2 #set -e diff --git a/stress/ltp/ipcstress.sh b/stress/ltp/ipcstress.sh index 5388f66..c84f592 100755 --- a/stress/ltp/ipcstress.sh +++ b/stress/ltp/ipcstress.sh @@ -1,4 +1,6 @@ #!/bin/bash +# +# Licensed under the terms of the GNU GPL License version 2 pushd ltp/testcases/kernel/ipc/ipc_stress ./testall diff --git a/stress/ltp/mmstress.sh b/stress/ltp/mmstress.sh index 7e81563..0c5ad44 100755 --- a/stress/ltp/mmstress.sh +++ b/stress/ltp/mmstress.sh @@ -1,4 +1,6 @@ #!/bin/bash +# +# Licensed under the terms of the GNU GPL License version 2 set -e diff --git a/stress/ltp/runtest.sh b/stress/ltp/runtest.sh index e2a4560..3e4ec2f 100755 --- a/stress/ltp/runtest.sh +++ b/stress/ltp/runtest.sh @@ -1,4 +1,6 @@ #!/bin/bash +# +# Licensed under the terms of the GNU GPL License version 2 source ../../utils/root-check.sh source ../../utils/build-deps.sh diff --git a/stress/stresspass/runtest.sh b/stress/stresspass/runtest.sh index 1bebc72..cd7c75b 100755 --- a/stress/stresspass/runtest.sh +++ b/stress/stresspass/runtest.sh @@ -1,4 +1,6 @@ #!/bin/bash +# +# Licensed under the terms of the GNU GPL License version 2 echo "sample test from the stress directory, should always pass" diff --git a/utils/build-deps.sh b/utils/build-deps.sh index 5754fdc..d85eece 100644 --- a/utils/build-deps.sh +++ b/utils/build-deps.sh @@ -1,4 +1,6 @@ #!/bin/bash +# +# Licensed under the terms of the GNU GPL License version 2 install_dep() { yum install -y $1; diff --git a/utils/loopback.sh b/utils/loopback.sh index 3179c43..dbc9f5a 100644 --- a/utils/loopback.sh +++ b/utils/loopback.sh @@ -1,4 +1,6 @@ #!/bin/bash +# +# Licensed under the terms of the GNU GPL License version 2 create_sparse_file() { dd if=/dev/zero of=$1 bs=1 count=0 seek=$2M ; diff --git a/utils/mod-check.sh b/utils/mod-check.sh index f706ee0..9815e9b 100644 --- a/utils/mod-check.sh +++ b/utils/mod-check.sh @@ -1,4 +1,6 @@ #!/bin/bash +# +# Licensed under the terms of the GNU GPL License version 2 # This function will check to see if a module is loaded. It is usefule # for tests which require specific modules or hardware. If a module diff --git a/utils/root-check.sh b/utils/root-check.sh index 9014e44..b8d0314 100644 --- a/utils/root-check.sh +++ b/utils/root-check.sh @@ -1,4 +1,6 @@ #!/bin/bash +# +# Licensed under the terms of the GNU GPL License version 2 check_root() { if [ $(id -u) -ne 0 ]

1 0

3.13.5
by poma 24 Feb '14

24 Feb '14

$ uname -r 3.13.5-200.fc20.x86_64+debug 2 patch down, 1 arrive, 57 more to go. Recon team, done. All clear. poma

1 0

3.14-rc4
by poma 24 Feb '14

24 Feb '14

$ uname -r 3.14.0-0.rc4.git0.1.fc20.x86_64 1 patch down 35 more to go. poma

2 3

kernel-3.13.4-200.fc20 build hangs
by Reindl Harald 21 Feb '14

21 Feb '14

i doubt that it really still builds :-) http://koji.fedoraproject.org/koji/buildinfo?buildID=499639 State: building Started: Thu, 20 Feb 2014 22:20:26 UTC Est. Completion: Fri, 21 Feb 2014 00:50:54 UTC Task: build (f20-candidate, /kernel:1a62f620b7b425c605803acdfd8fd7caafde1dc3)

2 1

3.13.3-100.fc19.x86_64 fine on VMware with LUKS
by Reindl Harald 20 Feb '14

20 Feb '14

Feb 20 12:27:20 Installed: kernel-3.13.3-100.fc19.x86_64 installed a view hours ago on a storage VM with around 2 TB luks-encrypted disks, so far all fine

2 3

RE: Latest kernel in F20 leads to read only file system
by Erinn Looney-Triggs 20 Feb '14

20 Feb '14

Well you get a cell picture this time. Couldn't even log in. I am using btrfs at the moment as you can see from the exception. Erinn -----Original Message----- From: "Eric Sandeen" <sandeen(a)redhat.com> Sent: ‎2/‎19/‎2014 20:45 To: "Erinn Looney-Triggs" <erinn.looneytriggs(a)gmail.com>; "kernel(a)lists.fedoraproject.org" <kernel(a)lists.fedoraproject.org> Subject: Re: Latest kernel in F20 leads to read only file system On 2/19/14, 11:19 PM, Erinn Looney-Triggs wrote: > On 2/19/2014 6:36 PM, Eric Sandeen wrote: >> On 2/19/14, 6:02 PM, Erinn Looney-Triggs wrote: >>> kernel-3.13.3-201.fc20.x86_64 seems to lead to file system failures >>> for me. Kernels < 3.13 however do not have this issue. >>> >>> At first I thought it was just file system corruption. However, after >>> approximately 5 reinstalls today the issue continues to surface every >>> time I move to the 3.13 kernel, whether using BTRFS or ext4. >>> >>> Behavior for both file systems differs slightly, ext4 complains about >>> a fair number of errors (sorry I don't have the specifics) >> We'll need those specifics. ;) dmesg and/or kernel logs in a bugzilla >> would probably be best. >> >> -Eric >> > > Ok given that I don't have a writeable file system, is there any reasonably smart way to go about getting these error messages to you other than writing them down and typing them up? > > -Erinn You wouldn't be the first to submit a cellphone photo :) -Eric

2 3

Latest kernel in F20 leads to read only file system
by Erinn Looney-Triggs 19 Feb '14

19 Feb '14

kernel-3.13.3-201.fc20.x86_64 seems to lead to file system failures for me. Kernels < 3.13 however do not have this issue. At first I thought it was just file system corruption. However, after approximately 5 reinstalls today the issue continues to surface every time I move to the 3.13 kernel, whether using BTRFS or ext4. Behavior for both file systems differs slightly, ext4 complains about a fair number of errors (sorry I don't have the specifics) and any user is unable to log into the system, username and password are accepted but then it immediately return to the login prompt. BTRFS on the other hand allows logins however, systemd-journal then starts to complain as the file system appears to be read only. This could of course be a hardware issue, but I reckoned I would ask y'all first. This is running on top of a Lenovo ThinkPad t440p laptop. Any pointers to how to get you folks some more data would be appreciated. As I said I have been able to consistently reproduce this issue on this system. This may or may not be related but I have experienced corruption in the EFI partition as well, specifically the grub.cfg file was truncated after the last kernel upgrade, the EFI partition waas not cleanly unmounted and the dirty bit was set thus precipitating an fsck of the partition to repair the above issues. Thanks, -Erinn

3 4

[PATCH] Build in IPMI on x86
by Matthew Garrett 19 Feb '14

19 Feb '14

The ACPI IPMI driver implements IPMI operation region support for the ACPI core. Systems that declare ACPI operation regions may reference them at any time, including during kernel initialisation. These accesses will fail unless the ACPI IPMI driver is present, and undesirable system behaviour may result. This can be avoided by building in the code rather than leaving it as modules. -- Matthew Garrett | mjg59(a)srcf.ucam.org

3 8

[dma-debug.c - DMA-API] exceeded overlapping … & sym53c8xx … tries to free DMA …
by poma 18 Feb '14

18 Feb '14

Ahoy! Perhaps this is already solved, but I made the effort to test & record all of this, therefore here you are. :) https://bugzilla.redhat.com/show_bug.cgi?id=1062833 0. VirtIO disk - virtio-pc OK: - lspci-knn-3.14.0-0.rc2.git2.1.fc21.x86_64-virtio-pc-virtio-disk-OK https://bugzilla.redhat.com/attachment.cgi?id=863135 - dmesg-3.14.0-0.rc2.git2.1.fc21.x86_64-virtio-pc-virtio-disk-OK https://bugzilla.redhat.com/attachment.cgi?id=863136 1. IDE disk - ata_piix: - lspci-knn-3.14.0-0.rc2.git2.1.fc21.x86_64-ata_piix-ide-disk https://bugzilla.redhat.com/attachment.cgi?id=863137 - dmesg-3.14.0-0.rc2.git2.1.fc21.x86_64-ata_piix-ide-disk "WARNING: CPU: 0 PID: 1328 at lib/dma-debug.c:491 add_dma_entry+0x127/0x130()" "DMA-API: exceeded 7 overlapping mappings of pfn 2137" https://bugzilla.redhat.com/attachment.cgi?id=863138 2. SATA disk - ahci: - lspci-knn-3.14.0-0.rc2.git2.1.fc21.x86_64-ahci-sata-disk https://bugzilla.redhat.com/attachment.cgi?id=863139 - dmesg-3.14.0-0.rc2.git2.1.fc21.x86_64-ahci-sata-disk "WARNING: CPU: 0 PID: 1543 at lib/dma-debug.c:491 add_dma_entry+0x127/0x130()" "DMA-API: exceeded 7 overlapping mappings of pfn 2137" https://bugzilla.redhat.com/attachment.cgi?id=863140 3. SCSI disk - sym53c8xx: - lspci-knn-3.14.0-0.rc2.git2.1.fc21.x86_64-sym53c8xx-scsi-disk https://bugzilla.redhat.com/attachment.cgi?id=863151 - dmesg-3.14.0-0.rc2.git2.1.fc21.x86_64-sym53c8xx-scsi-disk "WARNING: CPU: 1 PID: 1514 at lib/dma-debug.c:491 add_dma_entry+0x127/0x130()" "DMA-API: exceeded 7 overlapping mappings of pfn 2137" ~~ "WARNING: CPU: 1 PID: 1514 at lib/dma-debug.c:1041 check_unmap+0x8b7/0x9b0()" "sym53c8xx 0000:00:07.0: DMA-API: device driver tries to free DMA memory it has not allocated [device address=0x0000000002137000] [size=512 bytes]" https://bugzilla.redhat.com/attachment.cgi?id=863152 4. VirtIO SCSI disk - 'virtio-scsi' & sym53c8xx: - lspci-knn-3.14.0-0.rc2.git2.1.fc21.x86_64-sym53c8xx-virtio-scsi-disk https://bugzilla.redhat.com/attachment.cgi?id=863153 - dmesg-3.14.0-0.rc2.git2.1.fc21.x86_64-sym53c8xx-virtio-scsi-disk "WARNING: CPU: 0 PID: 1530 at lib/dma-debug.c:491 add_dma_entry+0x127/0x130()" "DMA-API: exceeded 7 overlapping mappings of pfn 2137" ~~ "WARNING: CPU: 0 PID: 1530 at lib/dma-debug.c:1041 check_unmap+0x8b7/0x9b0()" "sym53c8xx 0000:00:07.0: DMA-API: device driver tries to free DMA memory it has not allocated [device address=0x0000000002137000] [size=512 bytes]" https://bugzilla.redhat.com/attachment.cgi?id=863154 5. USB disk - usb-storage: - lspci-knn-3.14.0-0.rc2.git2.1.fc21.x86_64-usb-storage-usb-disk https://bugzilla.redhat.com/attachment.cgi?id=863156 - lsusb-3.14.0-0.rc2.git2.1.fc21.x86_64-usb-storage-usb-disk https://bugzilla.redhat.com/attachment.cgi?id=863157 - lsusb-t-3.14.0-0.rc2.git2.1.fc21.x86_64-usb-storage-usb-disk https://bugzilla.redhat.com/attachment.cgi?id=863158 - dmesg-3.14.0-0.rc2.git2.1.fc21.x86_64-usb-storage-usb-disk "WARNING: CPU: 0 PID: 415 at lib/dma-debug.c:491 add_dma_entry+0x127/0x130()" "DMA-API: exceeded 7 overlapping mappings of pfn 2137" https://bugzilla.redhat.com/attachment.cgi?id=863159 Tested with: http://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/x86_64/os/… boot.iso 13-Feb-2014 15:45 362M checkisomd5: boot.iso: 434371185df324e28ff5652891ae4ea8 Fragment sums: 5a3e92cebf4721fcfad3e317bff6ac4ec9df98fedd9f53c3c3f2ed55c337 Fragment count: 20 Press [Esc] to abort check. Checking: 100.0% The media check is complete, the result is: PASS. It is OK to use this media. sha256sum: 2b6aac6e9b55c5f49f251340a4c28e091998f9fe3a6bdba7542f0f9b2d69ba8c boot.iso poma

3 5

Enable CONFIG_PPC_DENORMALISATION in config-powerpc-generic
by Tony Breeds 17 Feb '14

17 Feb '14

Hi All, Could we make this small change to the powerpc config. While the scenario where I need this is on power7 the config option isn't p7 specific. Yours Tony diff --git a/config-powerpc-generic b/config-powerpc-generic index bcc30fe..9c0ad60 100644 --- a/config-powerpc-generic +++ b/config-powerpc-generic @@ -361,7 +361,7 @@ CONFIG_RCU_FANOUT_LEAF=16 # CONFIG_SPAPR_TCE_IOMMU is not set # CONFIG_TRANSPARENT_HUGEPAGE is not set -# CONFIG_PPC_DENORMALISATION is not set +CONFIG_PPC_DENORMALISATION=y # CONFIG_MDIO_BUS_MUX_MMIOREG is not set # CONFIG_GPIO_ADNP is not set # CONFIG_MFD_SYSCON is not set

2 1

Koji kernel 3.13.2-200.fc20.x86_64
by bgw2007＠comcast.net 13 Feb '14

13 Feb '14

I just downloaded and installed the new koji 3.13.2 kernel. I had to roll back to 3.12.10 since the GNOME login screen would not display. I usually download and install new koji kernels to provide karna for updates. This is probably the first time for me that seemingly won't start GNOME. -- Brad Watson MailTo:watsonbrad@comcast.net WWW: http://brad.bradwatson.net/

3 4

WARNING: CPU: 2 PID: 4415 at lib/idr.c:527 idr_remove.part.6+0x243/0x250()
by poma 12 Feb '14

12 Feb '14

Ahoy! My trace is the last one, therefore per LIFO I am sending this report to you. ------------[ cut here ]------------ WARNING: CPU: 2 PID: 4415 at lib/idr.c:527 idr_remove.part.6+0x243/0x250() idr_remove called for id=136 which is not allocated. CPU: 2 PID: 4415 Comm: systemd Not tainted 3.12.10-300.fc20.x86_64 #1 Call Trace: [<ffffffff81667ed5>] dump_stack+0x45/0x56 [<ffffffff8106903d>] warn_slowpath_common+0x7d/0xa0 [<ffffffff810690ac>] warn_slowpath_fmt+0x4c/0x50 [<ffffffff81304073>] idr_remove.part.6+0x243/0x250 [<ffffffff811c458c>] ? d_walk+0xdc/0x2a0 [<ffffffff8130408d>] idr_remove+0xd/0x10 [<ffffffff810defa6>] cgroup_destroy_css_killed+0x46/0x70 [<ffffffff810e1c98>] cgroup_destroy_locked+0x2d8/0x310 [<ffffffff810e1cf2>] cgroup_rmdir+0x22/0x40 [<ffffffff811bc108>] vfs_rmdir+0xa8/0x100 [<ffffffff811bc2dd>] do_rmdir+0x17d/0x1d0 [<ffffffff81087b6c>] ? task_work_run+0xac/0xe0 [<ffffffff81012a21>] ? do_notify_resume+0x61/0xa0 [<ffffffff811bf616>] SyS_rmdir+0x16/0x20 [<ffffffff81676ea9>] system_call_fastpath+0x16/0x1b ---[ end trace 4ebc2893b27b190d ]--- There are a bunch of here: https://bugzilla.redhat.com/show_bug.cgi?id=1045755 Thanks. poma

2 2

Koji kernel 3.13.2-200.fc20.x86_64
by Brad Watson 12 Feb '14

12 Feb '14

I just downloaded and installed the new koji 3.13.2 kernel. I had to roll back to 3.12.10 since the GNOME login screen would not display. I usually download and install new koji kernels to provide karna for updates. This is probably the first time for me that seemingly won't start GNOME. -- Brad Watson MailTo:watsonbrad@comcast.net WWW: http://brad.bradwatson.net/

1 0

Re: WARNING: CPU: 1 PID: 0 at kernel/time/tick-broadcast.c:668 tick_broadcast_oneshot_control+0x17d/0x190()
by poma 11 Feb '14

11 Feb '14

On 11.02.2014 15:25, Thomas Gleixner wrote: > On Mon, 10 Feb 2014, Thomas Gleixner wrote: >> On Mon, 10 Feb 2014, poma wrote: >> >>> [ 83.558551] [<ffffffff81025b17>] amd_e400_idle+0x87/0x130 >> >> So this seems to happen only on AMD machines which use that e400 idle >> mode. I have no idea at the moment whats wrong there. I'll find one of >> those machines and try to reproduce. > > Found it. Patch below. > > Thanks, > > tglx > ---- > Subject: tick: Clear broadcast pending bit when switching to oneshot > From: Thomas Gleixner <tglx(a)linutronix.de> > Date: Tue, 11 Feb 2014 14:35:40 +0100 > > AMD systems which use the C1E workaround in the amd_e400_idle routine > trigger the WARN_ON_ONCE in the broadcast code when onlining a CPU. > > The reason is that the idle routine of those AMD systems switches the > cpu into forced broadcast mode early on before the newly brought up > CPU can switch over to high resolution / NOHZ mode. The timer related > CPU1 bringup looks like this: > > clockevent_register_device(local_apic); > tick_setup(local_apic); > ... > idle() > tick_broadcast_on_off(FORCE); > tick_broadcast_oneshot_control(ENTER) > cpumask_set(cpu, broadcast_oneshot_mask); > halt(); > > Now the broadcast interrupt on CPU0 sets CPU1 in the > broadcast_pending_mask and wakes CPU1. So CPU1 continues: > > local_apic_timer_interrupt() > tick_handle_periodic(); > softirq() > tick_init_highres(); > cpumask_clr(cpu, broadcast_oneshot_mask); > > tick_broadcast_oneshot_control(ENTER) > WARN_ON(cpumask_test(cpu, broadcast_pending_mask); > > So while we remove CPU1 from the broadcast_oneshot_mask when we switch > over to highres mode, we do not clear the pending bit, which then > triggers the warning when we go back to idle. > > The reason why this is only visible on C1E affected AMD systems is > that the other machines enter the deep sleep states via > acpi_idle/intel_idle and exit the broadcast mode before executing the > remote triggered local_apic_timer_interrupt. So the pending bit is > already cleared when the switch over to highres mode is clearing the > oneshot mask. > > The solution is simple: Clear the pending bit together with the mask > bit when we switch over to highres mode. > > Reported-by: poma <pomidorabelisima(a)gmail.com> > Cc: stable(a)vger.kernel.org # 3.10+ > Signed-off-by: Thomas Gleixner <tglx(a)linutronix.de> > --- > kernel/time/tick-broadcast.c | 1 + > 1 file changed, 1 insertion(+) > > Index: linux-2.6/kernel/time/tick-broadcast.c > =================================================================== > --- linux-2.6.orig/kernel/time/tick-broadcast.c > +++ linux-2.6/kernel/time/tick-broadcast.c > @@ -756,6 +756,7 @@ out: > static void tick_broadcast_clear_oneshot(int cpu) > { > cpumask_clear_cpu(cpu, tick_broadcast_oneshot_mask); > + cpumask_clear_cpu(cpu, tick_broadcast_pending_mask); > } > > static void tick_broadcast_init_next_event(struct cpumask *mask, > > Thanks! poma

1 0

Re: WARNING: CPU: 1 PID: 0 at kernel/time/tick-broadcast.c:668 tick_broadcast_oneshot_control+0x17d/0x190()
by poma 11 Feb '14

11 Feb '14

On 10.02.2014 11:06, Thomas Gleixner wrote: > On Mon, 10 Feb 2014, poma wrote: > >> [ 83.558551] [<ffffffff81025b17>] amd_e400_idle+0x87/0x130 > > So this seems to happen only on AMD machines which use that e400 idle > mode. I have no idea at the moment whats wrong there. I'll find one of > those machines and try to reproduce. > > Thanks, > > tglx Thanks for your response! :) https://bugzilla.redhat.com/show_bug.cgi?id=1031296#c24 poma

3 3

WARNING: CPU: 0 PID: 2243 at mm/slub.c:1007 deactivate_slab+0x4e0/0x590()
by poma 10 Feb '14

10 Feb '14

Ahoy! "Tracking of fully allocated slabs for debugging purposes." Are this warnings expected and therefore not a bug? Thanks. [ 83.530421] WARNING: CPU: 0 PID: 2243 at mm/slub.c:1007 deactivate_slab+0x4e0/0x590() [ 83.530440] Modules linked in: ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack xt_CHECKSUM iptable_mangle fuse ip6table_filter ip6_tables ebtable_nat ebtables kvm_amd kvm ppdev microcode serio_raw nouveau mxm_wmi video i2c_algo_bit ttm edac_core edac_mce_amd drm_kms_helper k10temp drm parport_serial parport_pc parport wmi shpchp i2c_nforce2 i2c_core acpi_cpufreq nfsd auth_rpcgss nfs_acl lockd sunrpc binfmt_misc ata_generic pata_acpi pata_amd 8021q garp mrp tun bridge stp llc bonding [ 83.530441] CPU: 0 PID: 2243 Comm: systemd-sleep Tainted: G W 3.14.0-0.rc1.git5.1.fc21.1.x86_64 #1 [ 83.530442] Hardware name: Gigabyte Technology Co., Ltd. M720-US3/M720-US3, BIOS F7n 09/07/2010 [ 83.530444] 0000000000000000 00000000c8ff680f ffff8800ae5ffb28 ffffffff817cf05d [ 83.530445] 0000000000000000 ffff8800ae5ffb60 ffffffff810966cd 0000000000000002 [ 83.530447] ffff88012a003700 ffff88012a000c00 0000000000000000 ffffea0003205b80 [ 83.530447] Call Trace: [ 83.530448] [<ffffffff817cf05d>] dump_stack+0x4d/0x66 [ 83.530450] [<ffffffff810966cd>] warn_slowpath_common+0x7d/0xa0 [ 83.530451] [<ffffffff810967fa>] warn_slowpath_null+0x1a/0x20 [ 83.530452] [<ffffffff8120d870>] deactivate_slab+0x4e0/0x590 [ 83.530454] [<ffffffff810f8739>] ? mark_held_locks+0xb9/0x140 [ 83.530455] [<ffffffff8120da4c>] slab_cpuup_callback+0xcc/0x130 [ 83.530457] [<ffffffff817dd586>] notifier_call_chain+0x66/0x150 [ 83.530459] [<ffffffff810ca41e>] __raw_notifier_call_chain+0xe/0x10 [ 83.530460] [<ffffffff81096933>] cpu_notify+0x23/0x50 [ 83.530461] [<ffffffff8109696e>] cpu_notify_nofail+0xe/0x20 [ 83.530462] [<ffffffff817bf8c5>] _cpu_down+0x1d5/0x350 [ 83.530464] [<ffffffff81096fe5>] disable_nonboot_cpus+0xa5/0x150 [ 83.530465] [<ffffffff81101bad>] suspend_devices_and_enter+0x21d/0x670 [ 83.530466] [<ffffffff81102178>] pm_suspend+0x178/0x260 [ 83.530468] [<ffffffff81100b49>] state_store+0x79/0xf0 [ 83.530469] [<ffffffff813c8f6f>] kobj_attr_store+0xf/0x20 [ 83.530471] [<ffffffff812bc844>] sysfs_kf_write+0x44/0x60 [ 83.530472] [<ffffffff812c0de5>] kernfs_fop_write+0xd5/0x150 [ 83.530473] [<ffffffff81232f2d>] vfs_write+0xbd/0x1f0 [ 83.530475] [<ffffffff81255c45>] ? __fget_light+0x145/0x160 [ 83.530476] [<ffffffff812339bb>] SyS_write+0x5b/0xb0 [ 83.530477] [<ffffffff817e2ea9>] system_call_fastpath+0x16/0x1b [ 83.530478] ---[ end trace d6d150ba17d5207a ]--- [ 83.534749] kvm: disabling virtualization on CPU2 [ 83.534787] smpboot: CPU 2 is now offline [ 83.537960] kvm: disabling virtualization on CPU3 [ 83.538003] smpboot: CPU 3 is now offline [ 83.538181] ------------[ cut here ]------------ https://bugzilla.redhat.com/attachment.cgi?id=861203 https://bugzilla.redhat.com/show_bug.cgi?id=1063096 poma

2 2

WARNING: CPU: 0 PID: 9502 at lib/dma-debug.c:554 debug_dma_assert_idle+0xc4/0x140()
by poma 09 Feb '14

09 Feb '14

These two cases are associated with the use of SATA controllers, SATA_AHCI. I hope that I sent to the right people. :) Domain; /etc/libvirt/qemu/<domain>.xml: <domain type='kvm'> <os> <type arch='x86_64' machine='pc-i440fx-1.6'>hvm</type> </os> <devices> <emulator>/usr/bin/qemu-kvm</emulator> <disk type='file' device='disk'> <driver name='qemu' type='qcow2'/> <source file='/var/lib/libvirt/images/rawhide209.img'/> <target dev='sda' bus='sata'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> </controller> </devices> </domain> lspci: 00:09.0 SATA controller [0106]: Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA Controller [AHCI mode] [8086:2922] (rev 02) [ 456.462913] ------------[ cut here ]------------ [ 456.462926] WARNING: CPU: 1 PID: 3772 at lib/dma-debug.c:491 add_dma_entry+0x127/0x130() [ 456.462928] DMA-API: exceeded 7 overlapping mappings of pfn 2137 [ 456.462930] Modules linked in: xfs libcrc32c btrfs fcoe libfcoe libfc scsi_transport_fc scsi_tgt iscsi_ibft iscsi_boot_sysfs iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi dm_crypt vfat fat dm_round_robin dm_multipath raid10 raid456 async_raid6_recov async_memcpy async_pq raid6_pq async_xor xor async_tx raid1 raid0 uinput ip6t_rpfilter ip6t_REJECT xt_conntrack cfg80211 rfkill ebtable_nat ebtable_broute bridge stp llc ebtable_filter ebtables ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_security ip6table_raw ip6table_filter ip6_tables iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_security iptable_raw ppdev kvm joydev serio_raw snd_hda_intel virtio_console snd_hda_codec snd_hwdep snd_seq snd_seq_device [ 456.462997] snd_pcm parport_pc pvpanic snd_timer parport snd soundcore i2c_piix4 nfsd auth_rpcgss nfs_acl lockd isofs squashfs virtio_balloon virtio_net qxl sym53c8xx drm_kms_helper scsi_transport_spi ttm drm virtio_pci virtio_ring ata_generic i2c_core virtio pata_acpi sunrpc loop [ 456.463039] CPU: 1 PID: 3772 Comm: ext4lazyinit Not tainted 3.14.0-0.rc1.git3.1.fc21.x86_64 #1 [ 456.463042] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011 [ 456.463044] 0000000000000000 0000000084feec1b ffff88001c861898 ffffffff817cee9d [ 456.463049] ffff88001c8618e0 ffff88001c8618d0 ffffffff810967cd 0000000000002137 [ 456.463053] ffff88007288d540 0000000000000096 ffffffff82d645c0 0000000000000096 [ 456.463056] Call Trace: [ 456.463063] [<ffffffff817cee9d>] dump_stack+0x4d/0x66 [ 456.463068] [<ffffffff810967cd>] warn_slowpath_common+0x7d/0xa0 [ 456.463071] [<ffffffff8109684c>] warn_slowpath_fmt+0x5c/0x80 [ 456.463075] [<ffffffff813f373d>] ? active_pfn_read_overlap+0x2d/0x50 [ 456.463079] [<ffffffff813f3d07>] add_dma_entry+0x127/0x130 [ 456.463082] [<ffffffff813f43dd>] debug_dma_map_sg+0x13d/0x180 [ 456.463086] [<ffffffff8153f0c1>] ata_qc_issue+0x281/0x3e0 [ 456.463090] [<ffffffff81548395>] ata_scsi_queuecmd+0x135/0x420 [ 456.463094] [<ffffffff81545150>] ? ata_scsi_invalid_field+0x40/0x40 [ 456.463098] [<ffffffff8151b777>] scsi_dispatch_cmd+0xb7/0x4e0 [ 456.463101] [<ffffffff81523bcc>] scsi_request_fn+0x33c/0x540 [ 456.463106] [<ffffffff813956f3>] __blk_run_queue+0x33/0x40 [ 456.463109] [<ffffffff8139b913>] blk_queue_bio+0x343/0x4d0 [ 456.463113] [<ffffffff81395510>] generic_make_request+0xe0/0x130 [ 456.463116] [<ffffffff813955d8>] submit_bio+0x78/0x160 [ 456.463121] [<ffffffff81273628>] ? bio_alloc_bioset+0x1f8/0x2f0 [ 456.463125] [<ffffffff813a311f>] __blkdev_issue_zeroout+0x1ff/0x260 [ 456.463129] [<ffffffff813a3269>] blkdev_issue_zeroout+0xe9/0xf0 [ 456.463133] [<ffffffff81303d9e>] ? __ext4_journal_get_write_access+0x4e/0x90 [ 456.463137] [<ffffffff812ccc1c>] ext4_init_inode_table+0x17c/0x3c0 [ 456.463142] [<ffffffff812e2039>] ? ext4_lazyinit_thread+0xb9/0x320 [ 456.463145] [<ffffffff812e222d>] ext4_lazyinit_thread+0x2ad/0x320 [ 456.463149] [<ffffffff812e1f80>] ? ext4_unregister_li_request+0x70/0x70 [ 456.463153] [<ffffffff810c43ef>] kthread+0xff/0x120 [ 456.463156] [<ffffffff810c42f0>] ? insert_kthread_work+0x80/0x80 [ 456.463160] [<ffffffff817e2c3c>] ret_from_fork+0x7c/0xb0 [ 456.463163] [<ffffffff810c42f0>] ? insert_kthread_work+0x80/0x80 [ 456.463165] ---[ end trace d1e41b42a5f51fa8 ]--- https://bugzilla.redhat.com/attachment.cgi?id=861122 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Bare metal; lspci: 00:09.0 SATA controller [0106]: NVIDIA Corporation MCP78S [GeForce 8200] AHCI Controller [10de:0ad4] (rev a2) [ 72.012408] ------------[ cut here ]------------ [ 72.012418] WARNING: CPU: 0 PID: 9502 at lib/dma-debug.c:554 debug_dma_assert_idle+0xc4/0x140() [ 72.012420] ahci 0000:00:09.0: DMA-API: cpu touching an active dma mapped page [pfn=0x943ba] [ 72.012421] Modules linked in: ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack xt_CHECKSUM iptable_mangle fuse ip6table_filter ip6_tables ebtable_nat ebtables kvm_amd kvm ppdev microcode serio_raw nouveau mxm_wmi video i2c_algo_bit ttm edac_core edac_mce_amd drm_kms_helper k10temp drm parport_serial parport_pc parport wmi shpchp i2c_nforce2 i2c_core acpi_cpufreq nfsd auth_rpcgss nfs_acl lockd sunrpc binfmt_misc ata_generic pata_acpi pata_amd 8021q garp mrp tun bridge stp llc bonding [ 72.012542] CPU: 0 PID: 9502 Comm: ld-linux-x86-64 Not tainted 3.14.0-0.rc1.git5.1.fc21.1.x86_64 #1 [ 72.012544] Hardware name: Gigabyte Technology Co., Ltd. M720-US3/M720-US3, BIOS F7n 09/07/2010 [ 72.012546] 0000000000000000 00000000ff75c10e ffff8800970f3c48 ffffffff817cf05d [ 72.012550] ffff8800970f3c90 ffff8800970f3c80 ffffffff810966cd ffff8800c8dd7600 [ 72.012553] ffff8801286c2f40 00000000000943ba ffffea000255cc00 ffff8800b0756058 [ 72.012556] Call Trace: [ 72.012561] [<ffffffff817cf05d>] dump_stack+0x4d/0x66 [ 72.012565] [<ffffffff810966cd>] warn_slowpath_common+0x7d/0xa0 [ 72.012567] [<ffffffff8109674c>] warn_slowpath_fmt+0x5c/0x80 [ 72.012571] [<ffffffff810f899d>] ? trace_hardirqs_on+0xd/0x10 [ 72.012573] [<ffffffff813f5b24>] debug_dma_assert_idle+0xc4/0x140 [ 72.012576] [<ffffffff811de8b4>] do_wp_page+0xf4/0x7f0 [ 72.012578] [<ffffffff811e130c>] handle_mm_fault+0x66c/0xe90 [ 72.012582] [<ffffffff817dce53>] __do_page_fault+0x183/0x600 [ 72.012585] [<ffffffff810246c5>] ? native_sched_clock+0x35/0xa0 [ 72.012588] [<ffffffff81024739>] ? sched_clock+0x9/0x10 [ 72.012590] [<ffffffff810dd465>] ? local_clock+0x25/0x30 [ 72.012593] [<ffffffff810f5c6f>] ? lock_release_holdtime.part.29+0xf/0x190 [ 72.012595] [<ffffffff817d9018>] ? retint_swapgs+0x13/0x1b [ 72.012598] [<ffffffff813d55da>] ? trace_hardirqs_off_thunk+0x3a/0x3c [ 72.012601] [<ffffffff817dd2de>] do_page_fault+0xe/0x10 [ 72.012603] [<ffffffff817d9338>] page_fault+0x28/0x30 [ 72.012605] ---[ end trace 48bb75765e35d9de ]--- [ 72.012606] Mapped at: [ 72.012607] [<ffffffff813f42f9>] debug_dma_map_sg+0x159/0x180 [ 72.012609] [<ffffffff8153f151>] ata_qc_issue+0x281/0x3e0 [ 72.012613] [<ffffffff81548425>] ata_scsi_queuecmd+0x135/0x420 [ 72.012616] [<ffffffff8151b807>] scsi_dispatch_cmd+0xb7/0x4e0 [ 72.012619] [<ffffffff81523c5c>] scsi_request_fn+0x33c/0x540 https://bugzilla.redhat.com/show_bug.cgi?id=1063059 poma

1 0

The nodebug repo doesn't have a kernel today
by Bruno Wolff III 08 Feb '14

08 Feb '14

The nodebug repo has repo data but no kernel rpms. Maybe something went wrong with the last build?

2 1

Re: Intel Dual Band Wireless 7260AC with Bluetooth 4.0 with Fedora
by poma 07 Feb '14

07 Feb '14

On 08.02.2014 02:15, CS DBA wrote: > Anyone using Fedora with this wireless card: > Intel Dual Band Wireless 7260AC with Bluetooth 4.0 > > Works well? > > Thanks in advance This is a theoretical. $ lspci -knn; Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev 6b) Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev 63) Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev 73) $ grep CONFIG_IWLWIFI= /boot/config-$(uname -r) CONFIG_IWLWIFI=m $ modinfo iwlwifi | grep -iP '(?=.*8086)(?=.*08b1)' | wc -l 44 $ rpm -qil iwl7260-firmware Name : iwl7260-firmware Version : 22.15.8.0 Release : 35.fc20 Architecture: noarch Install Date: Sat 08 Feb 2014 03:00:35 AM CET Group : System Environment/Kernel Size : 1433769 License : Redistributable, no modification permitted Signature : RSA/SHA256, Fri 31 Jan 2014 04:46:10 PM CET, Key ID 2eb161fa246110c1 Source RPM : linux-firmware-20140131-35.gitd7f8a7c8.fc20.src.rpm Build Date : Fri 31 Jan 2014 02:09:47 PM CET Build Host : arm02-builder01.arm.fedoraproject.org Relocations : (not relocatable) Packager : Fedora Project Vendor : Fedora Project URL : http://www.kernel.org/ Summary : Firmware for Intel(R) Wireless WiFi Link 7260 Series Adapters Description : This package contains the firmware required by the iwlagn driver for Linux. Usage of the firmware is subject to the terms and conditions contained inside the provided LICENSE file. Please read it carefully. /usr/lib/firmware/iwlwifi-7260-7.ucode /usr/lib/firmware/iwlwifi-7260-8.ucode /usr/share/doc/iwl7260-firmware /usr/share/doc/iwl7260-firmware/LICENCE.iwlwifi_firmware /usr/share/doc/iwl7260-firmware/WHENCE The question is how this will work in practice[1], in your case. Josh, if this is the last occurrence of the "iwlagn", i.e. EL6.2, /usr/lib/modules/2.6.32-220.23.1.el6.x86_64/kernel/drivers/net/wireless/iwlwifi/iwlagn.ko and currently in use is the "iwlwifi", i.e. Rawhide & Fefeora 20, /usr/lib/modules/3.14.0-0.rc1.git3.1.fc21.x86_64/kernel/drivers/net/wireless/iwlwifi/iwlwifi.ko /usr/lib/modules/3.12.9-301.fc20.x86_64/kernel/drivers/net/wireless/iwlwifi/iwlwifi.ko maybe it should write: "Description : This package contains the firmware required by the *iwlwifi* driver for Linux. …" poma [1] http://search.gmane.org/?query=Intel+7260&author=&group=gmane.linux.kernel.… https://bugzilla.redhat.com/show_bug.cgi?id=1000831

1 0

Why does Red Hat and Fedora software not distinguish between AMD and Intel kernels?
by James Harrison 07 Feb '14

07 Feb '14

Hello, I remember the times when Redhat software releases (6.2, 7.3, 8, 9) had a specific kernel for AMD and Intel CPUs. Now forward on to present day and Red Hat software has one kernel build for AMD and Intel CPUs. When was the decision to switch to an all in one encompassing kernel and is there a performance hit. What allows us to have one kernel build for two different CPUs? The reason I ask these questions is that Ubuntu is still distinguishing between AMD and Intel CPUs. Why, and what is the difference between what they do and what Red Hat do to their Kernel compiles. Personally, I think that what Red Hat are doing makes maintaining kernels easier. There is a layer of abstraction that hides what the underlying technology is. Hope someone can spread some light. Thanks, James Harrison

7 16

Enabling CONFIG_MMC_UNSAFE_RESUME
by Hans de Goede 07 Feb '14

07 Feb '14

Hi, The mmc subsys has a Kconfig option which more or less mirrors CONFIG_USB_DEFAULT_PERSIST, which Fedora enables. I would like to suggest to enable the MMC variant too, without this on suspend / resume, the kernel will assume that the card was swapped by one which happens to be of exactly the same type, thus forcing an unmount off any fs which was on it and killing any apps which happen to have files open on the device. For ARM where the rootfs often is on an sdcard this is disastrous, but one PC-s it is not really userfriendly to kill any fs on an sdcard on suspend / resume either. Therefor I would like to suggest that we start enabling CONFIG_MMC_UNSAFE_RESUME just like we do for CONFIG_USB_DEFAULT_PERSIST, note that despite the "scary" naming they are in essence pretty much the same, assume if the same device is still present after suspend / resume, that it really is the same device even though we cannot be 100.1 % sure. Regards, Hans

2 2

RawhideKernelNodebug - Nosign
by poma 06 Feb '14

06 Feb '14

Who builds these kernels? Perhaps the better question is how can I actually find who builds these kernels? :) And if any exists, where is a git repo for these kernels? Thanks. poma

7 19

Kernel IRC meetings discontinued
by Josh Boyer 05 Feb '14

05 Feb '14

Hi All, We've been running an IRC meeting every other week for quite a while now (when they weren't cancelled). After talking it over with the team, we're going to discontinue these for the time being. They've mostly turned into status reports with little in the way of discussion. As a replacement, I'll send out a status report to this list every month or so with a wrap up and on-going items. If you have questions, please just send them to the list! For those of you that did attend the IRC meetings, many thanks for your participation. If we really have the need for a high bandwidth meeting, we'll schedule as needed. josh

1 0

[PATCH v2 0/2] MODSIGN: Support MOKx
by Lee, Chun-Yi 04 Feb '14

04 Feb '14

It's base on the kernel patches of Fedora 20. This patch set add the support to MODSIGN mechanism for revoke kernel module by hash or public key. As MokListRT, EFI bootloader(e.g. shim) should maintain the MokListXRT container the format the same with dbx. The patches will check the hash of kernel module before load it. I doesn't add the module hash blacklist support to dbx because UEFI BIOS of Intel DQ57TM, my development board, doesn't allow set hash of non-efi file to dbx. v2: + Use the digest generated by mod_make_digest() to avoid computing the hash twice. + Also check the hash of whole module file is not in the module hash blacklist. + Change the statements of information log. + The hash type need the same with CONFIG_MODULE_SIG_HASH. + Handle the return value of func() + Move the logic of parsing EFI signature database to parse_efi_signature_db() for collecting certificates and hashes. + Still parsing hashes when signature parsing fail on MOKx. Lee, Chun-Yi (2): MODSIGN: check hash of kernel module in blacklist MODSIGN: load hash blacklist of modules from MOKx crypto/asymmetric_keys/efi_parser.c | 80 +++++++++++++++++++---------- include/linux/efi.h | 16 ++++++ kernel/modsign_uefi.c | 97 ++++++++++++++++++++++++++++++++++- kernel/module-internal.h | 13 +++++ kernel/module_signing.c | 86 ++++++++++++++++++++++++++++++- 5 files changed, 261 insertions(+), 31 deletions(-)

1 2

Supporting Allwinner ARM SoCs in Fedora 21+ kernels
by Hans de Goede 03 Feb '14

03 Feb '14

Hi All, As you probably know in my spare time I'm working on Linux Allwinner SoC support. We (the linux-sunxi community) are currently making good progress on getting Allwinner SoCs supported in the upstream kernel. It looks like the majority of it will land in 3.14 and 3.15. As such I believe the time has come to start supporting Allwinner SoCs with the official Fedora kernels ootb for F-21. I've written a Feature page for this, which you can find here: https://fedoraproject.org/wiki/Changes/AllwinnerSunxiSupport This will likely require carrying some kernel patches for 1-2 kernel releases, until all the necessary bits for headless operation have landed upstream. As always I'm willing to put my time were my work is, and I'll maintain these patches for as long as necessary. To give you an idea of where things are going, here is a break down of the tree I'm currently using for testing and development, see: https://github.com/linux-sunxi/linux-sunxi/commits/sunxi-devel This branch contains 3.13-rc5 + the following, which should all go upstream for 3.14: https://github.com/mripard/linux/commits/sunxi-clk-for-3.13 https://github.com/mripard/linux/commits/sunxi-drivers-for-3.14 https://github.com/mripard/linux/commits/sunxi-core-for-3.14 https://github.com/mripard/linux/commits/sunxi-dt-for-3.14 sunxi-bits of: https://git.linaro.org/people/daniel.lezcano/linux.git/shortlog/refs/heads/… Emilio's "[PATCH v3 00/13] clk: sunxi: add PLL5 and PLL6 support" series + the following which is not quite ready for 3.14 yet, but people are working hard to get it ready so hopefully we will see some of it in 3.14, and the rest should make 3.15: Emilio's sunxi-clk branch: patches not part of the above set David's and mine sunxi-mmc work Chen's gmac work Oliver's ahci work Arokux' ehci work mripard's "ARM: sunxi: Add A31 High Speed Timer Support" series wens' "v2 of A20 external output clock support patch series" hansg's resistive touchscreen controller driver (rtp) including temp sensor support Of the above list, we should at a minimum carry the mmc, gmac (gigabit nic) and ahci patches if those don't get upstream in time. USB support would also be very nice, but is not a must have. The last 3 patch-sets we don't need. Regards, Hans

2 6

please update linux-firmware to include latest iwlwifi firmware
by Yu Watanabe 02 Feb '14

02 Feb '14

Dear all, I found that iwlwifi firmware for 7260 is updated on upstream. https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/co… When I use the previous firmware (provided by the current linux-firmware rpm), the connection to several hotspot is sometimes lost. So, I've tried to use the new firmware, and it seems to be work fine. I do not know what is the criteria to include latest firmware. I can not find what kind of fixes applied to the latest firmware. But, I think it might be helpful for many laptop users. I comment that the iwlwifi firmware for kernel 3.13 are also provided on upstream. https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/co… Best, Yu

4 4

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

kernel February 2014