F37 broke netupstools
by Sam Varshavchik
After updating F37 nut is unhappy, spewing this every couple of seconds:
Nov 21 06:48:28 monster.email-scan.com nut-server[1735]: Can't connect to
UPS [nutdev1] (usbhid-ups-nutdev1): No such file or directory
Interestingly enough, the XFCE desktop's panel has a widget that shows the
UPS and its charged status.
Today's project is to figure out what's broken, does anyone happen to know
what's up with this, and save me some time?
1 year, 4 months
Fedora 37: kernel: general protection fault, probably for
non-canonical address PREEMPT SMP PT
by Dario Lesca
On a Fedora 37 up to date (kernel 6.0.10-300.fc37.x86_64), sometime I
get this error[1]
This problem occur often when I use nfs server from another PC, and if
I try to restart nfs via systemctl the command it remains stuck and I
must power off the PC
Other times PC freezes and I must power off and restart it.
Could it be a hardware problem (RAM? or CPU?) or I must fill a kernel
or nfs bug?
Many thanks for your help.
Dario
[1] (https://paste.centos.org/view/c6f9c704)
dic 01 21:12:46 kernel: general protection fault, probably for non-
canonical address 0x17ffffc0000008: 0000 [#1] PREEMPT SMP PTI
dic 01 21:12:46 kernel: CPU: 5 PID: 2103 Comm: nfsd Not tainted 6.0.10-
300.fc37.x86_64 #1
dic 01 21:12:46 kernel: Hardware name: LENOVO 30BGS1BV00/103D, BIOS
S06KT40A 03/15/2019
dic 01 21:12:46 kernel: RIP: 0010:release_pages+0x46/0x590
dic 01 21:12:46 kernel: Code: 48 8d 44 24 28 48 89 44 24 28 48 89 44 24
30 85 f6 0f 8e a2 00 00 00 48 63 f6 31 db 49 89 fc 45 31 ed 48 8d 2c f7
4d 8b 3c 24 <49> 8b 47 08 a8 01 0f 85 a9 01 00 00 0f 1f 44 00 00 4d 85
ed 74 0c
dic 01 21:12:46 kernel: RSP: 0018:ffffa9a901697e40 EFLAGS: 00010206
dic 01 21:12:46 kernel: RAX: 00000000ffff8c03 RBX: 0000000000000000
RCX: 0000000000000000
dic 01 21:12:46 kernel: RDX: fffffc6305e4dd48 RSI: ffffa9a901697e68
RDI: fffffc6304df1f48
dic 01 21:12:46 kernel: RBP: ffff8c03dea64b78 R08: fffffc6305e4dd48
R09: 0000000000000000
dic 01 21:12:46 kernel: R10: 0000000000000000 R11: fffffc63043ec208
R12: ffff8c03dea64b28
dic 01 21:12:46 kernel: R13: 0000000000000000 R14: fffffc6304df1f48
R15: 0017ffffc0000000
dic 01 21:12:46 kernel: FS: 0000000000000000(0000)
GS:ffff8c0b0dd40000(0000) knlGS:0000000000000000
dic 01 21:12:46 kernel: CS: 0010 DS: 0000 ES: 0000 CR0:
0000000080050033
dic 01 21:12:46 kernel: CR2: 00007f42a3ffefff CR3: 000000035d010005
CR4: 00000000003726e0
dic 01 21:12:46 kernel: DR0: 0000000000000000 DR1: 0000000000000000
DR2: 0000000000000000
dic 01 21:12:46 kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0
DR7: 0000000000000400
dic 01 21:12:46 kernel: Call Trace:
dic 01 21:12:46 kernel: <TASK>
dic 01 21:12:46 kernel: ? nfsd_shutdown_threads+0x90/0x90 [nfsd]
dic 01 21:12:46 kernel: __pagevec_release+0x1b/0x30
dic 01 21:12:46 kernel: svc_xprt_release+0x1a1/0x200 [sunrpc]
dic 01 21:12:46 kernel: svc_send+0x59/0x160 [sunrpc]
dic 01 21:12:46 kernel: nfsd+0xd5/0x190 [nfsd]
dic 01 21:12:46 kernel: kthread+0xe6/0x110
dic 01 21:12:46 kernel: ? kthread_complete_and_exit+0x20/0x20
dic 01 21:12:46 kernel: ret_from_fork+0x1f/0x30
dic 01 21:12:46 kernel: </TASK>
dic 01 21:12:46 kernel: Modules linked in: tls snd_seq_dummy
snd_hrtimer vhost_net vhost vhost_iotlb tap xt_recent xt_conntrack
xt_hashlimit xt_addrtype xt_mark xt_TCPMSS nft_chain_nat xt_MASQUERADE
xt_REDIRECT xt_multiport xt_nat xt_CT xt_NFLOG nfnetlink_log xt_LOG
nf_log_syslog nf_nat_tftp nf_nat_snmp_basic nf_conntrack_snmp
nf_nat_sip nf_nat_pptp nf_nat_irc rpcrdma nf_nat_h323 nf_nat_ftp
nf_nat_amanda ts_kmp rdma_cm nf_conntrack_amanda nf_nat iw_cm
nf_conntrack_sane ib_cm nf_conntrack_tftp nf_conntrack_sip ib_core
nf_conntrack_pptp nf_conntrack_netlink nf_conntrack_netbios_ns
nf_conntrack_broadcast nf_conntrack_irc nf_conntrack_h323
nf_conntrack_ftp nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 tun pppoe
pppox ppp_generic slhc ipt_REJECT nf_reject_ipv4 nft_compat nf_tables
nfnetlink bridge stp llc qrtr snd_hda_codec_hdmi snd_hda_codec_realtek
intel_rapl_msr intel_rapl_common snd_hda_codec_generic iwlmvm
ledtrig_audio intel_tcc_cooling x86_pkg_temp_thermal intel_powerclamp
snd_hda_intel coretemp
dic 01 21:12:46 kernel: snd_intel_dspcfg kvm_intel snd_intel_sdw_acpi
mac80211 snd_hda_codec kvm libarc4 iTCO_wdt ee1004 mei_wdt
intel_pmc_bxt mei_hdcp iTCO_vendor_support mei_pxp snd_hda_core iwlwifi
snd_hwdep irqbypass snd_seq snd_seq_device rapl intel_cstate snd_pcm
cfg80211 snd_timer mei_me snd think_lmi intel_uncore i2c_i801
intel_wmi_thunderbolt firmware_attributes_class wmi_bmof soundcore
pcspkr rfkill i2c_smbus mei joydev intel_pch_thermal acpi_pad nfsd
auth_rpcgss nfs_acl lockd grace sunrpc zram xfs i915 crct10dif_pclmul
crc32_pclmul crc32c_intel polyval_clmulni polyval_generic raid1
ghash_clmulni_intel e1000e r8169 drm_buddy drm_display_helper cec ttm
wmi video uas usb_storage scsi_dh_rdac scsi_dh_emc scsi_dh_alua
ip6_tables ip_tables dm_multipath fuse
dic 01 21:12:46 kernel: ---[ end trace 0000000000000000 ]---
--
Dario Lesca
(inviato dal mio Linux Fedora 37 Workstation)
1 year, 4 months
Are Meta/Facebook servers using Fedora Linux?
by Turritopsis Dohrnii Teo En Ming
Subject: Are Meta/Facebook servers using Fedora Linux?
Good day from Singapore,
I have just come across this article.
Article: Fedora's FESCo Rejects The Idea Of "-fno-omit-frame-pointer"
As Default Compiler Flag
Link: https://www.phoronix.com/news/Fedora-Rejects-No-Omit-FP
[QUOTE]
As a change proposal first initiated by Meta/Facebook developers, they
wanted -fno-omit-frame-pointer and -mno-omit-leaf-frame-pointer to be
added to the default C/C++ compilation flags.
...snipped...
Meta engineers believe that any performance cost is small and worth it
while SUSE engineers previously cited around possible 5~10%
regressions.
[/QUOTE]
From the above quotes, I thought that Meta/Facebook servers are using
Fedora Linux, or at least Linux servers.
Anyone can confirm?
Regards,
Mr. Turritopsis Dohrnii Teo En Ming
Targeted Individual in Singapore
Blogs:
https://tdtemcerts.blogspot.com
https://tdtemcerts.wordpress.com
1 year, 5 months
backup/restore
by Bill Cunningham
In visiting the backup subject from some time ago, I have found that
from most environment boots that are rescue type boots, there are two
restores that seem to be available.
1. rsync, of course, and;
2. I have seen fsarchiver.
Now I have never seen restore/dump in a rescue environment. So to me
there is no reason to use it. rsync is very complicated but might be
well worth the time and effort mastering. fsarchiver seems ok.
Other than that, clonezilla seems to be that best and fastest to
me, for my purposes. As in incremental backups. dump/restore seems good,
but rescue environments do not seems to have it, not the f37 workstation
iso. Mastering find and using tar might be ok, but, no compression.
Other than these two restore types, rsync and fsarchiver, is anyone
familiar with a commonly available, rescue environment restore?
B
1 year, 5 months
audio fails under sudo
by Geoffrey Leach
I'd appreciate any suggestions of a workaround for this situation.
Works fine without the "sudo". It also fails when run in ~root
sudo mpg123 t.mp3
High Performance MPEG 1.0/2.0/2.5 Audio Player for Layers 1, 2 and 3
version 1.31.1; written and copyright by Michael Hipp and others
free software (LGPL) without any warranty but with best wishes
ALSA lib pulse.c:242:(pulse_connect) PulseAudio: Unable to connect: Connection refused
[src/libout123/modules/alsa.c:open_alsa():181] error: cannot open device default
[src/libout123/libout123.c:check_output_module():947] error: Module 'alsa' device open failed.
[src/libout123/libout123.c:out123_open():439] error: Found no driver out of [alsa] working with device <default>.
main: [src/mpg123.c:check_fatal_output():334] error: out123 error 3: failure loading driver module
1 year, 5 months
[Fedora 38] Call for Test Days
by Sumantro Mukherjee
Hi Fedora users, developers, and friends!
It's time to start thinking about Test Days for Fedora 38.
For anyone who isn't aware, a Test Day is an event usually focused
around IRC for interaction and a Wiki page for instructions and results,
with the aim being to get a bunch of interested users and developers
together to test a specific feature or area of the distribution. You can
run a Test Day on just about anything for which it would be useful to do
some fairly focused testing in 'real time' with a group of testers; it
doesn't have to be code, for instance, we often run Test Days for
l10n/i18n topics. For more information on Test Days, see
https://fedoraproject.org/wiki/QA/Test_Days .
Anyone who wants to can host their own Test Day, or you can request that
the QA group helps you out with organization or any combination of the
two. To propose a Test Day, just file a ticket in fedora-qa pagure - here's
an example https://pagure.io/fedora-qa/issue/624 . For
instructions on hosting a Test Day, see
https://fedoraproject.org/wiki/QA/SOP_Test_Day_management .
You can see the schedule at https://pagure.io/fedora-qa/issues?tags=test+days .
There are many slots open right now. Consider the development
schedule, though, in deciding when you want to run your Test Day - for
some topics you may want to avoid
the time before the Beta release or the time after the feature freeze
or the Final Freeze.
We normally aim to schedule Test Days on Thursdays; however, if you want
to run a series of related Test Days, it's often a good idea to do
something like Tuesday / Wednesday / Thursday of the same week (this is
how we usually run the X Test Week, for instance). If all the Thursday
slots fill up but more people want to run Test Days, we will open up
Tuesday slots as overflows. And finally, if you really want to run a
Test Day in a specific time frame due to the development schedule, but
the Thursday slot for that week is full, we can add a slot on another
day. We're flexible! Just put in your ticket the date or time frame you'd
like, and we'll figure it out from there.
If you don't want to run your own Test Day, but you are willing to
help with another, feel free to join one or more of already accepted
Test Days:
GNOME Test Day*
i18n Test Day*
Kernel Test Week(s)*
Upgrade Test Day*
IoT Test Week*
Cloud Test Day*
Fedora CoreOS Test Week*
And don't be afraid, there are a lot of more slots available for your
own Test Day!
[*] These are the test days we run generally to make sure everything
is working fine, the dates get announced as we move into the release
cycle.
If you have any questions about the Test Day process, please don't
hesitate to contact me or any member of the Fedora QA team on test at
lists.fedoraproject.org or in #fedora-qa on IRC. Thanks!
--
//sumantro
Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED
1 year, 5 months
housekeeping
by Bill Cunningham
What files are basically safe to remove because they are caches and
such? There is the invisible file .cache. And the /var/cache. The files
in /tmp are these safe to delete? Are there any other files you can
delete? For example if you were using rsync, what file would you not
want to backup, because they are just caches?
B
1 year, 5 months
directories in /usr
by Bill Cunningham
I have found directories in /usr that are named after architectures. So
something has changed; is it ok to delete these? One is "x86_64",
something and one is another architecture. Are these for the system
installing? They were not in f36.
B
1 year, 5 months
time for a new lenovo 12" notebook
by Robert Moskowitz
Time to install Fedora37 and on what?
I have a Lenovo x140e upgraded with 16Gb mem (even though spec says 8Gb
max) and 500GB SSD, but I am looking for something perhaps newer and
perhaps won't hang at times.
Requirements are:
12" format
eraserhead pointing device (I hate touchpads!)
VGA output (for my KVM)
Affordable from ebay or such.
Most else is negotiable.
Oh, I will be running the Xfce desktop.
And my practice is a clean install, get everything working then rsync my
home over.
thanks for any help.
1 year, 5 months
Help Needed Identifying a File and a Security Failure on it.
by Stephen Morris
Hi,
How do I identify what file
.#user-1000@7668ca11a5184a26bcf4a7c1858f9574-0000000000000a42-0005ef6078e3e7f0.journalc7d37931ac52343c
is? The component before the "@" in the file name looks like the file
may be relative to my userid. I'm using an F37 system upgraded from F36.
Also how do I determine why "journal-offline" would be denied
"relabelfrom" access on that file by selinux?
I have given journal-offline the access attempted (I know this
might be problematic given the questions I'm asking), but I'm also
trying to determine why it happened in the first place, and whether or
not, as indicated in the error details, I should be raising this as a
bug. The timing of this error seems to be indicating it occurred during
boot this morning, and the audit message is indicating the file is
potentially on device "sdd1", which is potentially my fedora root
partition, which doesn't have /boot nor /boot/efi as they are on another
device, and if it is the root device, that device is a btrfs logical
device and both the physical and logical devices have the same label.
regards,
Steve
1 year, 6 months
