High cpu usge and high io percentage
by JD
ext4-rsv-conver ??
In kernel source ..../fs/ext4/super.c
we see
/*
* The maximum number of concurrent works can be high and
* concurrency isn't really necessary. Limit it to 1.
*/
EXT4_SB(sb)->rsv_conversion_wq =
alloc_workqueue("ext4-rsv-conversion", WQ_MEM_RECLAIM |
WQ_UNBOUND, 1);
if (!EXT4_SB(sb)->rsv_conversion_wq) {
printk(KERN_ERR "EXT4-fs: failed to create workqueue\n");
ret = -ENOMEM;
goto failed_mount4;
}
However, there is no other reference to this symbol in the rest of the
kernel source.
Reason I am asking is that it is often shown using much cpu bandwidth,
and much io percentage (/bin/iotop -d 3).
7 years, 5 months
dbus spamming syslog
by Neal Becker
I've got zillions of these messages (f25):
Nov 23 12:42:11 nbecker2 dbus-daemon[776]: [system] Connection ":1.28" is
not allowed to add more match rules (increase limits in configuration file
if required; max_match_rules_per_connection=2048)
7 years, 5 months
F25-Atomic - Error creating Vagrant synced folder
by Juan Orti Alcaine
Hi,
I'm launching a fedora/25-atomic-host with Vagrant but it fails to
create the synced folder although the VM boots fine and I can ssh in
it. I haven't done any customization, just launching the box like
explained in the instructions to get Fedora 25 Atomic.
Should I open a bug?
This is the error:
---
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
mkdir -p /vagrant
Stdout from the command:
Stderr from the command:
mkdir: cannot create directory ‘/vagrant’: Operation not permitted
---
Thanks.
--
Juan Orti
https://apuntesderootblog.wordpress.com/
GPG: 61F0 8272 6882 BCA6 3A35 88F6 B630 4B72 DEEB D08B
7 years, 5 months
F25: XFCE won't start
by Marco Guazzone
Hello,
I've installed F25 Workstation x64 from Live iso (GNOME window manager).
Now I want to run XFCE window manager.
I installed it with:
dnf groupinstall Xfce
Then rebooted and tried to log in (by selecting XFCE from GDM).
But after clicking on the log in button, XFCE seems to have problems and
the screen immediately comes back to the GDM login.
Any idea?
Thanks.
Best,
-- Marco
7 years, 5 months
Umatrix Firefox Addon -
by Bob Goodwin
Does anyone know why Firefox no longer
allows the umatrix addon, not since the
update to Firefox 50 two days ago.
Umatrix was removed and would not
install. I had to downgrade to Firefox
49 and install a copy from the umatrix
web page to get it back again.
Bob
--
Bob Goodwin - Zuni, Virginia, USA
http://www.qrz.com/db/W2BOD
box10 FEDORA-25/64it LINUX XFCE Fastmail POP3
7 years, 5 months
Epson XP-332
by DB
Good evening all!
I've recently bought an Epson all-in-one & am having a pile of
difficulty to get it to work properly.
a) Connected via USB, it appears to work.
b) Connected via wifi, it'll print but not scan.
c) operating via Oracle VirtualBox it does not get recognised,
Does anyone have any ideas how one may get the scanner to operate via wifi??
Does anyone know how to get the colour corrected after scanning??
Many thanks for any suggestions
Dave
Fedora 24 4.7.9-200.fc24.x86_64
7 years, 5 months
VlC and latest kernel/nvidia update error
by fedora2015
I am getting this error message on two PC's:
Error: Transaction check error:
file /etc/ld.so.conf.d/nvidia-lib64.conf from install of
nvidia-driver-cuda-libs-2:375.20-1.fc24.x86_64 conflicts with file from
package xorg-x11-drv-nvidia-340xx-libs-1:340.96-2.fc24.x86_64
This occurs with latest kernel and nvidia update. Only way to complete
the nvidia update is to remove VLC. Since I'm not an expert, should I
file a bug report?
7 years, 5 months
F25: error on SSH logout
by SternData
After exiting from a remote SSH via terminal, I get
Inconsistency detected by ld.so: dl-close.c: 811: _dl_close: Assertion
`map->l_init_called' failed!
--
-- Steve
7 years, 5 months
"Solar" plymouth theme is broken in 25, should not be enabled
by Sam Varshavchik
One of my usual post-Fedora upgrade rituals is to reset the default plymouth
theme back to solar. There's a long-standing bug with system upgrades always
resetting the plymouth theme to the default "charge". That bug is somewhere
in Bugzilla, gathering dust.
Well, having done this again, I was dismayed to see that the solar theme is
completely broken. One of my laptops still boots, but instead of smooth
animation, the theme basically suffers from Tourette's syndrome from start
to finish, constantly flickering between two frames.
Laptop #2 doesn't even boot at all, after switching to the solar theme. That
laptop uses LUKS encryption. The solar theme briefly flickers on and off,
and that's it. Instead of the password prompt, all I get is a black VGA
screen. The LUKS password prompt doesn't appear. I was able to edit the grub
boot script, and remove the "rhgb" keyword. This allowed the laptop to boot,
at which point I went back the default "charge" theme.
Created bug 1398061 for that. Hopefully, it won't end up gathering dust like
its predecessor.
Laptop #1 also has a weird X problem where the initial login seems to work
fine (except for the laptop's fingerprint scanner no longer getting
activated, which is a different story), but if I log out, and attempt to log
back in a second time, the laptop behaves as if X comes up at first, but
then crashes immediately back to VGA mode, then going back into X mode, than
crash again, about 3 or 4 times, before X manages to come up into my desktop.
Laptop #2 does not exhibit this weirdness. I suspect this has something to
do with Wayland (sigh). #1 uses noveau, #2 uses intel. There is a blurb in
the release notes about turning off wayland from gdm, but nothing is said
about lightdm, which I'm using.
Overall, looks like 25 is shaping up to be a rough release.
7 years, 5 months
dnf system-upgrades wants to remove the running kernel
by Andras Simon
I'm trying to upgrade to F24 from F23.
# dnf system-upgrade download --releasever=24
Last metadata expiration check: 0:10:02 ago on Wed Nov 23 18:52:12 2016.
Error: cannot install both kernel-PAE-4.5.5-300.fc24.i686 and
kernel-PAE-4.7.10-100.fc23.i686
(try to add '--allowerasing' to command line to replace conflicting packages)
kernel-PAE-4.7.10-100.fc23.i686 is actually the one that's running
(and in fact the only one).
With --allowerasing I get
[...]
Removing:
kernel-PAE i686 4.7.10-100.fc23 @updates
Allowing dnf to do this seems a bit risky to me.
What's the real problem that makes dnf complain? (The error message is
not very helpful: dnf shouldn't try to install
kernel-PAE-4.7.10-100.fc23.i686, as it is installed already.) And how
do I work around it?
Thanks,
Andras
7 years, 5 months