Description of problem:<br />
Problem is located specifically to the card, a USB WiFi adapter does not have the problem. Seems to be after the machine is running for more than 20mins. Doesn't seem to be any specific cause.<br />
Loses connectivity and doesn't show any networks when scanning. System reboot seems only fix, but is temporary. Problem seems also be be distro agnostic, Win 10 Enterprise doesn't have the issue so looks like it is a Linux issue somewhere.<br />
<br />
Version-Release number of selected component:<br />
kernel<br />
<br />
Truncated backtrace:<br />
WARNING: CPU: 0 PID: 0 at drivers/net/wireless/intel/iwlwifi/pcie/trans.c:1874 iwl_trans_pcie_grab_nic_access+0xed/0x100 [iwlwifi]<br />
Timeout waiting for hardware access (CSR_GP_CNTRL 0xffffffff)<br />
Modules linked in: tcp_lp rfcomm fuse cmac xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 tun devlink drbg ansi_cprng ccm ip6t_rpfilter ipt_REJECT nf_reject_ipv4 ip6t_REJECT nf_reject_ipv6 xt_conntrack ip_set nfnetlink ebtable_nat ebtable_broute bridge stp llc ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_security ip6table_raw iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_security iptable_raw ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bnep sunrpc vfat fat arc4 iwlmvm edac_mce_amd kvm_amd kvm mac80211 irqbypass crc32_pclmul ghash_clmulni_intel dell_led snd_hda_codec_realtek dell_wmi dell_smbios sparse_keymap snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel btusb iwlwifi<br />
snd_hda_codec btrtl btbcm btintel aesni_intel snd_hda_core dcdbas bluetooth lrw gf128mul uvcvideo snd_hwdep glue_helper snd_seq ablk_helper cryptd videobuf2_vmalloc snd_seq_device videobuf2_memops videobuf2_core cfg80211 videodev snd_pcm joydev pcspkr sg snd_timer fam15h_power snd i2c_piix4 shpchp soundcore wmi video tpm_crb dell_rbtn rfkill pinctrl_amd i2c_designware_platform i2c_designware_core acpi_cpufreq ip_tables xfs libcrc32c sd_mod amdkfd crc_t10dif crct10dif_generic amd_iommu_v2 amdgpu i2c_algo_bit ahci drm_kms_helper rtsx_usb_sdmmc mmc_core libahci libata rtsx_usb syscopyarea sysfillrect sysimgblt fb_sys_fops ttm drm crct10dif_pclmul crct10dif_common crc32c_intel serio_raw r8169 mii i2c_hid i2c_core dm_mirror dm_region_hash dm_log dm_mod<br />
CPU: 0 PID: 0 Comm: swapper/0 Kdump: loaded Not tainted 3.10.0-862.el7.x86_64 #1<br />
Hardware name: Dell Inc. Inspiron 15-3565/Inspiron 15-3565, BIOS 1.7.0 10/23/2017<br />
Call Trace:<br />
<IRQ> [<ffffffffb210d768>] dump_stack+0x19/0x1b<br />
[<ffffffffb1a916d8>] __warn+0xd8/0x100<br />
[<ffffffffb1a9175f>] warn_slowpath_fmt+0x5f/0x80<br />
[<ffffffffc0b4c35d>] iwl_trans_pcie_grab_nic_access+0xed/0x100 [iwlwifi]<br />
[<ffffffffc0b3c4f8>] iwl_read_prph+0x38/0xa0 [iwlwifi]<br />
[<ffffffffc0b4fd80>] iwl_trans_pcie_log_scd_error+0x140/0x280 [iwlwifi]<br />
[<ffffffffb1ab0314>] ? wake_up_worker+0x24/0x30<br />
[<ffffffffb1ab0b42>] ? insert_work+0x62/0xa0<br />
[<ffffffffc0b45df0>] ? iwl_queue_init+0x90/0x90 [iwlwifi]<br />
[<ffffffffc0b45e3e>] iwl_pcie_txq_stuck_timer+0x4e/0x80 [iwlwifi]<br />
[<ffffffffb1aa1828>] call_timer_fn+0x38/0x110<br />
[<ffffffffc0b45df0>] ? iwl_queue_init+0x90/0x90 [iwlwifi]<br />
[<ffffffffb1aa3d1d>] run_timer_softirq+0x22d/0x310<br />
[<ffffffffb1a9a945>] __do_softirq+0xf5/0x280<br />
[<ffffffffb2122d2c>] call_softirq+0x1c/0x30<br />
[<ffffffffb1a2d625>] do_softirq+0x65/0xa0<br />
[<ffffffffb1a9acc5>] irq_exit+0x105/0x110<br />
[<ffffffffb21240a8>] smp_apic_timer_interrupt+0x48/0x60<br />
[<ffffffffb21207f2>] apic_timer_interrupt+0x162/0x170<br />
<EOI> [<ffffffffb1f69364>] ? cpuidle_enter_state+0x54/0xd0<br />
[<ffffffffb1f6935d>] ? cpuidle_enter_state+0x4d/0xd0<br />
[<ffffffffb1f694be>] cpuidle_idle_call+0xde/0x230<br />
[<ffffffffb1a352fe>] arch_cpu_idle+0xe/0x40<br />
[<ffffffffb1af2b6a>] cpu_startup_entry+0x14a/0x1e0<br />
[<ffffffffb20fc6a7>] rest_init+0x77/0x80<br />
[<ffffffffb276c1c1>] start_kernel+0x446/0x467<br />
[<ffffffffb276bb7b>] ? repair_env_string+0x5c/0x5c<br />
[<ffffffffb276b120>] ? early_idt_handler_array+0x120/0x120<br />
[<ffffffffb276b72f>] x86_64_start_reservations+0x24/0x26<br />
[<ffffffffb276b885>] x86_64_start_kernel+0x154/0x177<br />
[<ffffffffb1a000d5>] start_cpu+0x5/0x14
↧
0015142: [abrt] kernel: WARNING: CPU: 0 PID: 0 at drivers/net/wireless/intel/iwlwifi/pcie/trans.c:1874 iwl_trans_pcie_grab_nic_access+...
↧
0015349: Shim 12-2 results in unbootable system
Similar to <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1477735">https://bugzilla.redhat.com/show_bug.cgi?id=1477735</a> I found when updating from kernel-3.10.0-862.11.6.el7.x86_64 to kernel-3.10.0-862.14.4.el7.x86_64, and shim-x64-12-2 as well as mokutil-12-2, upon reboot, the shim will report "Shim was unable to measure state into the TPM", that something has gone terribly wrong, and then the system will shut down.<br />
<br />
The new kernel appears to depend on mokutil & shim 12-2, so I downgraded those as well as removing the kernel using a USB-booted recovery session, in order to get the system running again.<br />
<br />
From the yum logs, I believe one previous kernel update was performed without these ill effects.
↧
↧
0015397: Backport patch to allow tmpfiles e directive to accept glob-style wildcards
Documentation states that the e should accept wildcards,<br />
<br />
e<br />
Clean directory contents based on the age argument. Lines of this type accept shell-style globs in place of normal path names.<br />
<br />
This was opened as issue #7369 on systemd's issue tracker, <a href="https://github.com/systemd/systemd/issues/7369">https://github.com/systemd/systemd/issues/7369</a> and the patch is fairly trivial.
↧
0015398: [abrt] setroubleshoot-server: __init__.py:798::ValueError: Failed to read //etc/selinux/targeted/policy/policy.31 ...
Description of problem:<br />
I just rebooted my Centos 7 system and got this one.<br />
<br />
Version-Release number of selected component:<br />
setroubleshoot-server-3.2.24-1.1.el7<br />
<br />
Truncated backtrace:<br />
#1 <module> in /usr/lib64/python2.7/site-packages/sepolicy/__init__.py:798<br />
#2 <module> in /usr/lib64/python2.7/site-packages/setroubleshoot/util.py:291<br />
#3 <module> in /usr/sbin/setroubleshootd:30
↧
0015399: xfsaild blocks after a while
On kernel 3.10.0-862.11.6.el7.x86_64 #1 SMP Tue Aug 14 21:49:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux<br />
<br />
After a few days of operation, nvme-backed filesystem fails as follows :-<br />
<br />
Oct 19 22:31:03 aws-prod-mongocadb-060211.prod.ucds.io kernel: INFO: task xfsaild/dm-0:573 blocked for more than 120 seconds.<br />
Oct 19 22:31:03 aws-prod-mongocadb-060211.prod.ucds.io kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.<br />
Oct 19 22:31:03 aws-prod-mongocadb-060211.prod.ucds.io kernel: xfsaild/dm-0 D ffff949ddea08fd0 0 573 2 0x00000080<br />
Oct 19 22:31:03 aws-prod-mongocadb-060211.prod.ucds.io kernel: Call Trace:<br />
Oct 19 22:31:03 aws-prod-mongocadb-060211.prod.ucds.io kernel: [<ffffffffa66a697e>] ? try_to_del_timer_sync+0x5e/0x90<br />
Oct 19 22:31:03 aws-prod-mongocadb-060211.prod.ucds.io kernel: [<ffffffffa6d18db9>] schedule+0x29/0x70<br />
Oct 19 22:31:03 aws-prod-mongocadb-060211.prod.ucds.io kernel: [<ffffffffc0473e26>] _xfs_log_force+0x1c6/0x2c0 [xfs]<br />
Oct 19 22:31:03 aws-prod-mongocadb-060211.prod.ucds.io kernel: [<ffffffffa66d1fe0>] ? wake_up_state+0x20/0x20<br />
Oct 19 22:31:03 aws-prod-mongocadb-060211.prod.ucds.io kernel: [<ffffffffc047ffdc>] ? xfsaild+0x16c/0x6f0 [xfs]<br />
Oct 19 22:31:03 aws-prod-mongocadb-060211.prod.ucds.io kernel: [<ffffffffc0473f4c>] xfs_log_force+0x2c/0x70 [xfs]<br />
Oct 19 22:31:03 aws-prod-mongocadb-060211.prod.ucds.io kernel: [<ffffffffc047fe70>] ? xfs_trans_ail_cursor_first+0x90/0x90 [xfs]<br />
Oct 19 22:31:03 aws-prod-mongocadb-060211.prod.ucds.io kernel: [<ffffffffc047ffdc>] xfsaild+0x16c/0x6f0 [xfs]<br />
Oct 19 22:31:03 aws-prod-mongocadb-060211.prod.ucds.io kernel: [<ffffffffc047fe70>] ? xfs_trans_ail_cursor_first+0x90/0x90 [xfs]<br />
Oct 19 22:31:03 aws-prod-mongocadb-060211.prod.ucds.io kernel: [<ffffffffa66bdf21>] kthread+0xd1/0xe0<br />
Oct 19 22:31:03 aws-prod-mongocadb-060211.prod.ucds.io kernel: [<ffffffffa66bde50>] ? insert_kthread_work+0x40/0x40<br />
Oct 19 22:31:03 aws-prod-mongocadb-060211.prod.ucds.io kernel: [<ffffffffa6d255f7>] ret_from_fork_nospec_begin+0x21/0x21<br />
Oct 19 22:31:03 aws-prod-mongocadb-060211.prod.ucds.io kernel: [<ffffffffa66bde50>] ? insert_kthread_work+0x40/0x40<br />
Oct 19 22:31:03 aws-prod-mongocadb-060211.prod.ucds.io kernel: INFO: task repl wr.orker 4:2167 blocked for more than 120 seconds.<br />
Oct 19 22:31:03 aws-prod-mongocadb-060211.prod.ucds.io kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.<br />
Oct 19 22:31:03 aws-prod-mongocadb-060211.prod.ucds.io kernel: repl wr.orker 4 D ffff949da2b44f10 0 2167 1 0x00000080<br />
Oct 19 22:31:03 aws-prod-mongocadb-060211.prod.ucds.io kernel: Call Trace:<br />
Oct 19 22:31:03 aws-prod-mongocadb-060211.prod.ucds.io kernel: [<ffffffffa67faec2>] ? kmem_cache_alloc+0x1c2/0x1f0<br />
Oct 19 22:31:03 aws-prod-mongocadb-060211.prod.ucds.io kernel: [<ffffffffc0470387>] ? kmem_zone_alloc+0x97/0x130 [xfs]<br />
Oct 19 22:31:03 aws-prod-mongocadb-060211.prod.ucds.io kernel: [<ffffffffa6d18db9>] schedule+0x29/0x70<br />
Oct 19 22:31:03 aws-prod-mongocadb-060211.prod.ucds.io kernel: [<ffffffffa6d1a6a5>] rwsem_down_write_failed+0x225/0x3a0<br />
Oct 19 22:31:03 aws-prod-mongocadb-060211.prod.ucds.io kernel: [<ffffffffc0470ac4>] ? xlog_grant_head_check+0x54/0x100 [xfs]<br />
Oct 19 22:31:03 aws-prod-mongocadb-060211.prod.ucds.io kernel: [<ffffffffc045fabd>] ? xfs_vn_update_time+0xcd/0x150 [xfs]<br />
Oct 19 22:31:03 aws-prod-mongocadb-060211.prod.ucds.io kernel: [<ffffffffa695f2e7>] call_rwsem_down_write_failed+0x17/0x30<br />
Oct 19 22:31:03 aws-prod-mongocadb-060211.prod.ucds.io kernel: [<ffffffffa6d17f2d>] down_write+0x2d/0x3d<br />
Oct 19 22:31:03 aws-prod-mongocadb-060211.prod.ucds.io kernel: [<ffffffffc0462864>] xfs_ilock+0xc4/0x120 [xfs]<br />
Oct 19 22:31:03 aws-prod-mongocadb-060211.prod.ucds.io kernel: [<ffffffffc045fabd>] xfs_vn_update_time+0xcd/0x150 [xfs]<br />
Oct 19 22:31:03 aws-prod-mongocadb-060211.prod.ucds.io kernel: [<ffffffffa683bb68>] update_time+0x28/0xd0<br />
Oct 19 22:31:03 aws-prod-mongocadb-060211.prod.ucds.io kernel: [<ffffffffa6d16d40>] ? bit_wait+0x50/0x50<br />
Oct 19 22:31:03 aws-prod-mongocadb-060211.prod.ucds.io kernel: [<ffffffffa683bcb0>] file_update_time+0xa0/0xf0<br />
Oct 19 22:31:03 aws-prod-mongocadb-060211.prod.ucds.io kernel: [<ffffffffc0455bd5>] xfs_file_aio_write_checks+0x185/0x1f0 [xfs]<br />
Oct 19 22:31:03 aws-prod-mongocadb-060211.prod.ucds.io kernel: [<ffffffffc04561fa>] xfs_file_buffered_aio_write+0xca/0x2c0 [xfs]<br />
Oct 19 22:31:03 aws-prod-mongocadb-060211.prod.ucds.io kernel: [<ffffffffc0462bf4>] ? xfs_iunlock+0x104/0x130 [xfs]<br />
Oct 19 22:31:03 aws-prod-mongocadb-060211.prod.ucds.io kernel: [<ffffffffc045657d>] xfs_file_aio_write+0x18d/0x1b0 [xfs]<br />
Oct 19 22:31:03 aws-prod-mongocadb-060211.prod.ucds.io kernel: [<ffffffffa681e6a3>] do_sync_write+0x93/0xe0<br />
Oct 19 22:31:03 aws-prod-mongocadb-060211.prod.ucds.io kernel: [<ffffffffa681f180>] vfs_write+0xc0/0x1f0<br />
Oct 19 22:31:03 aws-prod-mongocadb-060211.prod.ucds.io kernel: [<ffffffffa6820172>] SyS_pwrite64+0x92/0xc0<br />
Oct 19 22:31:03 aws-prod-mongocadb-060211.prod.ucds.io kernel: [<ffffffffa6d2579b>] system_call_fastpath+0x22/0x27<br />
<br />
This is highly reminiscent of <a href="https://bugs.centos.org/view.php?id=13843">https://bugs.centos.org/view.php?id=13843.</a><br />
<br />
The filesystem is XFS on LVM-managed partition.
↧
↧
0015400: gnome-shell will restart or crash when an ad pops up in spotify.
Whenever an ad pops up inside the Spotify app, the x11/gnome-shell environment crashes and no multimedia players (like VLC of ffplay) are able to playback any video unless the computer restarts.
↧
0015401: mdadm raid1 freezes whole system when you grow number of disks
mdadm freezes whole system when you grow number of disks in raid1 array under heavy load<br />
<br />
on physical server is almost 100%, on virtual server with virtual disks it happens very offen, you can reproduce this even with CentOS-7-x86_64-NetInstall-1804.iso, tried it on kernel 3.10.0 862.14.4.el7 / 862.11.6.el7 / 862.3.3.el7 it's same
↧
0015402: [abrt] kernel: WARNING: CPU: 3 PID: 13670 at net/mac80211/driver-ops.c:175 drv_conf_tx+0x197/0x1b0 [mac80211]
Version-Release number of selected component:<br />
kernel<br />
<br />
Truncated backtrace:<br />
WARNING: CPU: 3 PID: 13670 at net/mac80211/driver-ops.c:175 drv_conf_tx+0x197/0x1b0 [mac80211]<br />
wlp2s0: invalid CW_min/CW_max: 0/0<br />
Modules linked in: tcp_lp nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack iptable_filter ip_tables ip6t_REJECT nf_reject_ipv6 ipt_REJECT nf_reject_ipv4 rfcomm fuse drbg ansi_cprng ccm ip_set nfnetlink bridge stp llc bnep sunrpc intel_powerclamp coretemp arc4 kvm_intel snd_hda_codec_hdmi kvm iwldvm snd_hda_codec_idt snd_hda_codec_generic mac80211 irqbypass crc32_pclmul ghash_clmulni_intel dell_wmi aesni_intel sparse_keymap ppdev lrw gf128mul iTCO_wdt glue_helper iTCO_vendor_support ablk_helper dell_rbtn cryptd dell_laptop dell_smbios dcdbas iwlwifi btusb uvcvideo btrtl btbcm btintel videobuf2_vmalloc videobuf2_memops bluetooth videobuf2_core pcspkr joydev videodev cfg80211 snd_hda_intel snd_hda_codec sg snd_hda_core<br />
snd_hwdep snd_seq rfkill snd_seq_device snd_pcm wmi parport_pc snd_timer parport snd intel_ips soundcore dell_smo8800 i2c_i801 shpchp lpc_ich acpi_cpufreq xfs libcrc32c sr_mod sd_mod cdrom crc_t10dif crct10dif_generic i915 iosf_mbi i2c_algo_bit drm_kms_helper ahci libahci syscopyarea sysfillrect sysimgblt fb_sys_fops libata crct10dif_pclmul crct10dif_common drm crc32c_intel e1000e serio_raw sdhci_pci sdhci mmc_core i2c_core ptp pps_core video dm_mirror dm_region_hash dm_log dm_mod [last unloaded: nf_defrag_ipv6]<br />
CPU: 3 PID: 13670 Comm: kworker/u16:77 Not tainted 3.10.0-862.14.4.el7.x86_64 #1<br />
Hardware name: Dell Inc. Latitude E4310/012JJ4, BIOS A08 08/23/2011<br />
Workqueue: phy0 ieee80211_iface_work [mac80211]<br />
Call Trace:<br />
[<ffffffffa8f13754>] dump_stack+0x19/0x1b<br />
[<ffffffffa88945d8>] __warn+0xd8/0x100<br />
[<ffffffffa889465f>] warn_slowpath_fmt+0x5f/0x80<br />
[<ffffffffa8897769>] ? vprintk_default+0x29/0x40<br />
[<ffffffffa8f0d436>] ? printk+0x60/0x77<br />
[<ffffffffc09db407>] drv_conf_tx+0x197/0x1b0 [mac80211]<br />
[<ffffffffc0a2b102>] ieee80211_sta_wmm_params+0x2d2/0x370 [mac80211]<br />
[<ffffffffc0a41510>] ieee80211_assoc_success+0x84e/0x133e [mac80211]<br />
[<ffffffffa889505a>] ? msg_print_text+0xea/0x1d0<br />
[<ffffffffa897fce3>] ? irq_work_queue+0x63/0x80<br />
[<ffffffffa8896b72>] ? wake_up_klogd+0x32/0x40<br />
[<ffffffffa8896de5>] ? console_unlock+0x265/0x4b0<br />
[<ffffffffa88973f4>] ? vprintk_emit+0x3c4/0x510<br />
[<ffffffffc0a0eb38>] ? ieee802_11_parse_elems_crc+0x1d8/0x700 [mac80211]<br />
[<ffffffffa8897769>] ? vprintk_default+0x29/0x40<br />
[<ffffffffc0a2fe3c>] ieee80211_rx_mgmt_assoc_resp+0x1ac/0x330 [mac80211]<br />
[<ffffffffc0a309e5>] ieee80211_sta_rx_queued_mgmt+0x1c5/0x790 [mac80211]<br />
[<ffffffffc0a08b1f>] ? ieee80211_xmit+0x8f/0xc0 [mac80211]<br />
[<ffffffffa889d057>] ? local_bh_enable+0x17/0x20<br />
[<ffffffffc0a0a3b8>] ? __ieee80211_tx_skb_tid_band+0x68/0x70 [mac80211]<br />
[<ffffffffa88db2fc>] ? update_curr+0x14c/0x1e0<br />
[<ffffffffa88d7c6e>] ? account_entity_dequeue+0xae/0xd0<br />
[<ffffffffa88db7ec>] ? dequeue_entity+0x11c/0x5e0<br />
[<ffffffffa88a766d>] ? mod_timer+0x14d/0x230<br />
[<ffffffffa88dc0ce>] ? dequeue_task_fair+0x41e/0x660<br />
[<ffffffffa88d5105>] ? sched_clock_cpu+0x85/0xc0<br />
[<ffffffffa882a59e>] ? __switch_to+0xce/0x580<br />
[<ffffffffc09ee344>] ieee80211_iface_work+0x234/0x3a0 [mac80211]<br />
[<ffffffffa88b613f>] process_one_work+0x17f/0x440<br />
[<ffffffffa88b71d6>] worker_thread+0x126/0x3c0<br />
[<ffffffffa88b70b0>] ? manage_workers.isra.24+0x2a0/0x2a0<br />
[<ffffffffa88bdf21>] kthread+0xd1/0xe0<br />
[<ffffffffa88bde50>] ? insert_kthread_work+0x40/0x40<br />
[<ffffffffa8f255f7>] ret_from_fork_nospec_begin+0x21/0x21<br />
[<ffffffffa88bde50>] ? insert_kthread_work+0x40/0x40
↧
0015403: On Next Release Kernel to be 4.x
Hi All,<br />
<br />
Is there any on next release CentOS 7.6 will the Kernel will get updated to 4.x.
↧
↧
0015404: Please create a 'duck' account on the jumphost
Quack,<br />
<br />
I'm working with the RDO infra team to improve and modernize Ansible rules. The CentOS CI nodes setup is also managed by Ansible, so I would need access to them as well.<br />
<br />
Regards.<br />
\_o<
↧
0015405: semanage fails on startup with ValueError: plural forms expression could be dangerous in the lt_LT.UTF-8 locale
# semanage<br />
Traceback (most recent call last):<br />
File "/sbin/semanage", line 32, in <module><br />
import seobject<br />
File "/usr/lib64/python2.7/site-packages/seobject/__init__.py", line 36, in <module><br />
import sepolicy<br />
File "/usr/lib64/python2.7/site-packages/sepolicy/__init__.py", line 22, in <module><br />
codeset='utf-8')<br />
File "/usr/lib64/python2.7/gettext.py", line 495, in install<br />
t = translation(domain, localedir, fallback=True, codeset=codeset)<br />
File "/usr/lib64/python2.7/gettext.py", line 480, in translation<br />
t = _translations.setdefault(key, class_(fp))<br />
File "/usr/lib64/python2.7/gettext.py", line 180, in __init__<br />
self._parse(fp)<br />
File "/usr/lib64/python2.7/gettext.py", line 317, in _parse<br />
self.plural = c2py(plural)<br />
File "/usr/lib64/python2.7/gettext.py", line 93, in c2py<br />
raise ValueError, 'plural forms expression could be dangerous'<br />
ValueError: plural forms expression could be dangerous<br />
<br />
# locale<br />
LANG=lt_LT.UTF-8<br />
LC_CTYPE=lt_LT.UTF-8<br />
LC_NUMERIC="lt_LT.UTF-8"<br />
LC_TIME="lt_LT.UTF-8"<br />
LC_COLLATE="lt_LT.UTF-8"<br />
LC_MONETARY="lt_LT.UTF-8"<br />
LC_MESSAGES="lt_LT.UTF-8"<br />
LC_PAPER="lt_LT.UTF-8"<br />
LC_NAME="lt_LT.UTF-8"<br />
LC_ADDRESS="lt_LT.UTF-8"<br />
LC_TELEPHONE="lt_LT.UTF-8"<br />
LC_MEASUREMENT="lt_LT.UTF-8"<br />
LC_IDENTIFICATION="lt_LT.UTF-8"<br />
LC_ALL=
↧
0015406: install centos7 error
kernel Bug at include/linux/dma-attrs.h:53!
↧
0015004: Please add me to fedora-atomic.ci.centos.org and jump.ci.centos.org / access to centos ci fedora atomic project
Hello, please add my ssh key to "user: fedora-atomic" for hosts:<br />
<br />
fedora-atomic.ci.centos.org<br />
jump.ci.centos.org<br />
for User fedora-atomic<br />
<br />
Key is attached to this bug-report.
↧
↧
0015082: Please add me to jump.ci.centos.org
Hello.<br />
This ticket is duplicate to for : <a href="https://bugs.centos.org/view.php?id=15004">https://bugs.centos.org/view.php?id=15004</a><br />
<a href="https://bugs.centos.org/view.php?id=15004">https://bugs.centos.org/view.php?id=15004</a> wasn't resolved.<br />
I need to get access to jump.ci.centos.org because I need to call rsync manually:<br />
Example: rsync -Pav . <a href="mailto:fedora-atomic@artifacts.ci.centos.org">fedora-atomic@artifacts.ci.centos.org</a>:~/ <br />
to change/fix files at : <a href="http://artifacts.ci.centos.org/artifacts/fedora-atomic/">http://artifacts.ci.centos.org/artifacts/fedora-atomic/</a><br />
Thank you.<br />
<br />
My public key:<br />
<br />
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDglk8nR0izKZULi2ZK2Q3AQ2nGhLx42cllRxUrgZHDta4acrgHmU2c+xNq99nuh7+u8/dQWY6buSmX+DG4SgEd3mRnGfi4/RhjlQ/SpJ/ugLPEEEdAwTjldAJo6ZtY0Mla9RJDCdr7n6rZ88AJtj/BMFzSF1/Hs5wwiwsgx39VkfWMKPnlV+ggep0k+w3aU79sChEe1M86g4+nUa/KBk8HeG1kihiXoEskU+I+9ShhNY4wdFFgpE/Z3oT5otTzJFGk2MnBR8OG4Qi3M7Pqx1s4UxWaGwlOHNLZSTotMRFTXeYchMM81jzWsQH+BikIaemTDDIlnXT7FM7BG4sbZg+N
↧
0015407: New collection: sclo-php72
As soon as rh-php72 tags will be available<br />
<br />
<br />
Notice: this is not a real collection but additional packages for rh-pĥp71 collection (so rh-php71-build needed in buildroot)<br />
<br />
Tags needed, and directory target<br />
<br />
sclo7-sclo-php71-sclo-candidate<br />
<br />
sclo7-sclo-php70-sclo-testing => <a href="http://buildlogs.centos.org/centos/7/sclo/x86_64/sclo/sclo-php71">http://buildlogs.centos.org/centos/7/sclo/x86_64/sclo/sclo-php71</a><br />
<br />
sclo7-sclo-php71-sclo-release => /pub/Mirrors/centos-7/7/sclo/x86_64/sclo/sclo-php71/
↧
0015408: Missing Centos7 latest images in sha256sum.txt
I have noticed missing sha256 hashes for the lates images:<br />
CentOS-7-x86_64-GenericCloud.qcow2 <br />
CentOS-7-x86_64-GenericCloud.qcow2.xz <br />
CentOS-7-x86_64-GenericCloud.qcow2c<br />
<br />
at <a href="http://cloud.centos.org/centos/7/images/">http://cloud.centos.org/centos/7/images/</a>
↧
0015409: [x86] speculation: additional speculation nospec patches for i686
This patch patches speculation related things which RHEL didin't backport for i686.<br />
This is rather a preventive measure, rather than a problem-driven patch.<br />
Tested on kernel-3.10.0-862.14.4.el7.centos.plus and runs on real machine and Hyper-V.<br />
<br />
This patch is a replacement of patch-nospec-32-v1.patch already included<br />
in i686 kernel source.<br />
Please replace accordingly.
↧
↧
0015410: [abrt] abrt-addon-vmcore: abrt-harvest-vmcore:34:get_augeas:AttributeError: 'module' object has no attribute 'Augeas'
Version-Release number of selected component:<br />
abrt-addon-vmcore-2.1.11-50.el7.centos<br />
<br />
Truncated backtrace:<br />
abrt-harvest-vmcore:34:get_augeas:AttributeError: 'module' object has no attribute 'Augeas'<br />
<br />
Traceback (most recent call last):<br />
File "/usr/sbin/abrt-harvest-vmcore", line 273, in <module><br />
harvest_vmcore()<br />
File "/usr/sbin/abrt-harvest-vmcore", line 154, in harvest_vmcore<br />
dump_dir = parse_kdump()<br />
File "/usr/sbin/abrt-harvest-vmcore", line 81, in parse_kdump<br />
aug_obj = get_augeas("Kdump", "/etc/kdump.conf")<br />
File "/usr/sbin/abrt-harvest-vmcore", line 34, in get_augeas<br />
aug_obj = augeas.Augeas(flags=augeas.Augeas.NO_MODL_AUTOLOAD)<br />
AttributeError: 'module' object has no attribute 'Augeas'<br />
<br />
Local variables in innermost frame:<br />
file_path: '/etc/kdump.conf'<br />
module: 'Kdump'
↧
0015386: Access request for 'systemd-pr-build' project
Hello,<br />
<br />
As a new co-maintainer of the systemd CentOS CI[0], I'd like to request an access to the systemd-pr-build project[1]. I'll ping the current owners to give<br />
additional signoff, if necessary.<br />
<br />
Thanks!<br />
<br />
[0] <a href="https://github.com/systemd/systemd-centos-ci">https://github.com/systemd/systemd-centos-ci</a><br />
[1] <a href="https://ci.centos.org/job/systemd-pr-build/">https://ci.centos.org/job/systemd-pr-build/</a>
↧
0006828: Tracking for centosplus kernels for CentOS-7
Build and maintain centosplus kernels for EL7.
↧