| ckCmd in Korn script Posted: 16 Sep 2021 10:31 AM PDT I'm trying to get info on what this script section does, specifically ckCmd, which isn't coming up with a good explanation when I search. echo "kermit soon" export M_PROMPT_MSG="[enter '?' to see the ftp script to be run] " if ckCmd; then echo "here kermit even sooner" # Run kermit ftp script from stdin cat <(print " Ftp2 script:") $M_SCRIPT_TMP_FILE <(print " Ftp dialog:") \ | sed -e 's/PASSWORD:.*/PASSWORD:xxxxxx/' -e 's/^/ /' >> ${LOGFILE:-/home/mcleary/k_test/michele/logs/default.log} kermit $M_SCRIPT_TMP_FILE | sed -e '/^$/d' -e 's/^/ /' >> ${LOGFILE:-/home/mcleary/k_test/michele/logs/default.log} 2>&1 cat <(print " Ftp transaction log:") $TMP/m_Ftp_trans.tmp \ | sed -e '/^$/d' -e 's/^/ /' >> ${LOGFILE:-/home/mcleary/k_test/michele/logs/default.log} 2>&1 #rm -f $M_SCRIPT_TMP_FILE $TMP/m_Ftp_trans.tmp >/dev/null 2>&1 # Note password stored (briefly) in tmp file fi
when I run it like ksh -x k_test, the output around the above is: ... M_SCRIPT_TMP_FILE: /apps/tmp/m_Ftp.tmp.26775 kermit soon here kermit even sooner + EXIT_STATUS=0 + echo 'Exit Status - m_Ftp2: 0' Exit Status - m_Ftp2: 0 + m_exit
So my question is what is the ckCmd part doing, and why would it exit without seeming to do anything? There is decent looking content for the temp file (user/pw removed): ftp open MMMM /USER:user\userftp /PASSWORD:pwpw LOG TRANSACTIONS /apps/tmp/m_Ftp_trans.tmp cd /home/mcleary/k_test/michele/ ascii put test.txt ../20210916_test.txt exit
Is there a way for me to test the file contents myself? I tried cutting/pasting to the unix command prompt and the ftp part makes it give a ftp> prompt, and the paste of the entire thing and the $ gives weird feedback (again, user/pw and other pertinent info changed for safety): [mcleary@qaaa michele]$ ftp open MMMM /USER:user\userftp /PASSWORD:pwpw usage: ftp host-name [port] ftp> LOG TRANSACTIONS /appl/tmp/m_Ftp_trans.tmp ?Invalid command ftp> cd /home/mcleary/k_test/michele/ Not connected. ftp> ascii Not connected. ftp> put test.txt ../20210916_test.txt Not connected. ftp> exit
 |
| How do I extract different fields of a filename in bash? Posted: 16 Sep 2021 10:22 AM PDT I have some log files to fuse and I have to extract the different fields of the filename inorder to compare the extracted value with the standard value so as to fuse the files corresponding to the same fieldsin the file name. For example I have files like public.primary-2021-09-15.log, public.secondary-2021-08-14.log, private.primary-2021-09-13.log and private.secondary-2021-08-14.log to extract so that all the files containing public in their names should be grouped together in a file(be it primary or secondary), those containing private in their names should be grouped together(be it primary or secondary) and finally all those files should be grouped according to a particular period(date range). I need someone to help me I'm new to bash  |
| Multi-NIC RHEL host when would we want to force bind local NIC on TCP socket connect to remote server Posted: 16 Sep 2021 10:08 AM PDT Fairly basic situation with RHEL6/7 host, and 3 eth* interfaces different IP addresses each, and a "normally" configured static route table. Coding up in C a basic socket(2) + connect(2) to a remote IP/port destination. In what situations would I normally not rely on the default kernel TCP/IP stack selection of a default IP source address, the one that matches the NIC connected to the router that is the gateway to reach the destination IP? PS: I haven't written socket code since the late 90s :-)  |
| ping from Linux distros = 20s, ping from Windows/Android = instant. Why? Posted: 16 Sep 2021 10:48 AM PDT I'm hoping this will be an interesting problem for Linux networking aficionados. In summary, I have a new broadband modem/router connected to an ISP offering a 40MBPS bandwidth. However, the initial connect to any website from a Linux distro takes a good 20s. A ping command (with domain name) too takes 20s to show ANY output at all (even the ip address). Let's focus on ping: - When pinging by ip address there is no issue. A 20s delay only when pinging by domain name
- the ping delay of 20s shows up even when I try it from a live linux USB - whether it is Manjaro or Linux Mint
- the delay is seen even if I try on another computer with live-booted Linux
- ping from the same laptop(s) running Windows returns results instantly
- ping from a terminal on a Pixel 2XL phone running Android returns results instantly
- the problem exists whether I connect my laptop via wifi or via ethernet cable to the router
- the same Linux distro on the same laptop, when connected to my mobile hotspot does not have the issue
- Ping -4 to force IPv4 does not help - the delay is still 20s
- As suggested by a senior member of the Manjaro forum I tried moving from openresolv to systemd-resolved but that increased the delay to over 2 minutes and I had to roll back the change.
This is as you realize not a "fun" question but a rather perplexing one and almost a showstopper for me. The problem is specifically with the combination of Linux and this new router and I have no idea where to look for a solution.I have of course had a long discussion on the Manjaro forum where I hit a dead end. Thanks very much for reading! Best - Ram *Examples and Test outputs: [ramkumarr@RR-W520 ~]$ ping www.google.com PING www.google.com (142.250.192.132) 56(84) bytes of data. 64 bytes from bom12s18-in-f4.1e100.net (142.250.192.132): icmp_seq=1 ttl=118 time=25.1 ms. The response starting with "PING" appears 20-30s after I type the command.*
[ramkumarr@RR-W520 ~]$ ping -n www.google.com PING www.google.com (142.250.192.100) 56(84) bytes of data. 64 bytes from 142.250.192.100: icmp_seq=1 ttl=59 time=29.4 m ---> Again a 20s delay before any output appears.
 |
| I need to zip all files and subdirectories in a folder including those that start with a dot Posted: 16 Sep 2021 10:05 AM PDT I need to zip all files and subdirectories in a folder including those that start with a . (dot). I'm in a folder called synthesis and I need to zip all the files and subdirectories under it (but not the synthesis folder itself). The synthesis folder includes a subdirectory called .sopc_builder that has a file in it. I tried the following command zip -r synthesis.zip *
I copied the resulting synthesis.zip to another folder and listed the zip contents in a file: unzip -l synthesis.zip > filelist.txt
The filelist.txt doesn't have the .sopc_builder and its file in the list. I saw on some post something about a Linux command shopt, but didn't really understand it. The version of Linux I'm using is Red Hat Enterprise Linux Server 7.9 at my company. Thanks in advance, Grady  |
| Can't add unallocated space to my root partition using parted Posted: 16 Sep 2021 09:08 AM PDT I want to extend my pop os' root partition. I shrunk my windows partition (using a third party program, easeus partition master) and created an ubuntu bootable drive. In gparted the free space shows up correctly but it's not showing up in the resize window. Please help!! 
 |
| can you install Kali Linux Bare Metal directly onto an internal hard drive partition? Posted: 16 Sep 2021 08:54 AM PDT I was wondering whether it was possible to just install (or copy over with terminal) Kali Linux directly onto a partition I made from my hard drive. I'm currently trying to dual boot macOs and Kali Linux (model is 2018 macbook Pro High Sierra 10.13.6, I had just used terminal to partition my current internal hard drive) without using any external medias, and if this is not possible, I was wondering why not (like what is the bare metal Kali Linux, is it just the os itself or an installer?). Thanks, Leo. edit: I have a T2 chip so I don't think I'll be able to use Unetbooting either.  |
| Ubuntu file system is readonly and boot in recovery Posted: 16 Sep 2021 08:52 AM PDT My Ubuntu file system suddenly became read only while I was using it. After a reboot, it boots in recovery mode. I tried fsck -fy /dev/sda6 (my file system is sda6) and it finds and fixes the issues, but after I reboot, the file system become once again read only and fails to boot. I have a dual boot with Windows, so I also tried to disable fast startup, but the issue remains anyway. I extended my Ubuntu partition yesterday, I suspect this to be the cause. What could I do now?  |
| Inability to change monitor's display Posted: 16 Sep 2021 08:51 AM PDT It seems that my monitor's display can't be changed from 1024 x 728. I read that this may be due to a new update. I use Linux Mint 20.2 Uma. Should I try updating my GPU drivers? Should I move to an older version? Is there anything else that may be the problem? I have an Intel Corporation Haswell-ULT Integrated Graphics Controller.  |
| How ext4 with data=journal differs from a CoW filesystem? Posted: 16 Sep 2021 08:34 AM PDT From reading the docs it would seem like since new data is written to the journal it is no longer updated in place, technically achieving the same "atomicity" a CoW filesystem would provide. So is there anything that makes a CoW filesystem "more atomic" than ext4 with data=journal? Are there theoretical or proven cases where one would/does provide more crash safety than the other? Or maybe CoW could be seen as an "implementation detail" which provides better performance? Seeing as data=journal is not the default due performance concerns.  |
| How to keep error messages on screen with syslinux Posted: 16 Sep 2021 08:09 AM PDT I am making the assumption that I'm using syslinux because I have a syslinux.cfg file present on my USB boot disk. The configuration of syslinux is the following: UI /linux/boot/vesamenu.c32 TIMEOUT 140 MENU ROWS 4 MENU CLEAR MENU BACKGROUND /linux/boot/bootlogo.png LABEL default MENU LABEL Run Linux KERNEL /linux/boot/vmlinuz APPEND vga=769 initrd=/linux/boot/initrfs.img load_ramdisk=1 prompt_ramdisk=0 rw printk.time=0 apparmor=0 perch LABEL default MENU LABEL Run Linux debug KERNEL /linux/boot/vmlinuz APPEND vga=769 initrd=/linux/boot/initrfs.img load_ramdisk=1 prompt_ramdisk=0 rw printk.time=0 apparmor=0 debug perch
The machine does not boot as expected. I can see the menu and choose options. However, the error message is only shown for a couple of milliseconds and the the meanu re-appears. Is there a way to configure syslinux not to display the menu again but to stay on the error message?  |
| DualBoot System (Windows/Linux) with hardware drivers installed on Windows Posted: 16 Sep 2021 08:15 AM PDT I'm thinking of making a Dual-Boot system, just for installing some hardware drivers that aren't available for Linux (neither are open-source alternatives). Will the Linux environment be able to configure the hardware using the drivers that are installed on the Windows?  |
| Really basic Samba set-up not working Posted: 16 Sep 2021 08:15 AM PDT Background: I had a Debian server running a Samba share, and it played nicely with everyone: Debian, Ubuntu, Mint, Windows 7, Windows 10, Android 8 through whatever is current, even XP (for testing purposes). One of the services (Plex) on that server was problematic, so I set up another Debian server with the same storage devices, and set up the services I want. So far, all of the services work, except for Samba. I figured I mucked up the config some how, so I copied line by line the config file from the old server to the new server, and this had no change. I know it's a problem on the server, since it's the same for all the clients (Linux, Windows, Android, etc) Win10 and Mint are both giving me the same generic error: "Permission Denied" mount error(13): Permission denied Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
Samba has these nifty logs - one for each client, but, when I try to read those logs, they're blank and all read as 0kb. It seems like a simple thing that should be working... What the heck do I do now? Any advice is appreciated; thanks in advance! (BTW in case it matters, I tried the first time using Webmin, then just the config files in /etc when Webmin didn't work) Output from grep -Ev '^\s*[#;]|^$' /etc/samba/smb.conf per roaima's request The below only contains generic information [global] workgroup = WORKGROUP dns proxy = no log file = /var/log/samba/log.%m max log size = 1000 syslog = 0 panic action = /usr/share/samba/panic-action %d server role = standalone server passdb backend = tdbsam obey pam restrictions = yes unix password sync = yes passwd program = /usr/bin/passwd %u passwd chat = Enter\snew\s\spassword:* %n\n Retype\snew\s\spassword:* %n\n password\supdated\ssuccessfully . pam password change = yes map to guest = bad user usershare allow guests = yes unix extensions = no [test]
comment = test writeable = yes path = /home/tony/test valid users = tony
 |
| korn script printing garbage for param sent to function in utils file Posted: 16 Sep 2021 07:17 AM PDT I have a korn util script that isn't receiving correct parameters. I'm not sure why. I'm new to korn, and searching for the issue online didn't help. I execute the calling script this way from calling dir: ksh test_k.ksh test_k.ksh: #!/bin/ksh # Invoke the initialization script [[ ! -r /home/mcleary/k_test/bin/init.ksh ]] \ && print -u2 "$0: /home/mcleary/k_test/bin/init.ksh not found" && exit . /home/mcleary/k_test/bin/init.ksh #I had to add -fDEV_OVR below for executing in dev env, but this is source of params and I see the resemblance to the garbage here m_F -fDEV_OVR -t'echo "No skipping"' MMMM <<! cd ${REMOTE_DIR} ! #command called here, calls utils.michele.ksh init.ksh looks like this (moved it to my dir to add #!/bin/ksh at the top):
init.ksh: #!/bin/ksh # Set up environment umask 002 # Check $M_HOME if [[ -z "$M_HOME" ]]; then print "\$M_HOME is not set" echo "setting M_HOME different way then echo" M_HOME="/appl/" echo $M_HOME echo "export and echo again next" export M_HOME="/appl/" echo $M_HOME fi echo "m_home:" $M_HOME # Read $M_HOME/etc/m.env if [[ -r ${M_HOME}/etc/m.env ]]; then . ${M_HOME}/etc/m.env echo "first case home etc m.env found" ... # Read $M_HOME/bin/utils.ksh if [[ -r /home/mcleary/k_test/bin/utils.michele.ksh ]]; then . /home/mcleary/k_test/bin/utils.michele.ksh echo "michele utils found" #it prints this else if [[ -f /home/mcleary/k_test/bin/utils.michele.ksh ]]; then print "\/home/mcleary/k_test/bin/utils.michele.ksh not readable, exiting" echo "michele utils not readable" else print "\/home/mcleary/k_test/bin/utils.michele.ksh not found, exiting" echo "michele utils not found" fi exit fi
So what happens in the init file is that it doesn't know what M_HOME is so it defaults to what I give it. It then finds $M_HOME/etc/m.env, but print garbage, shown below. There aren't any error messages otherwise. Why are the params not working? The env file doesn't have #!/bin/ksh at the top, and has a list of exports. M.env: export GROOVY_dir=${M_HOME}/dsa5/oraclev6/groovy etc
utils.michele.ksh: #!/bin/ksh #I added this, former version did not have it ... function m_F { when getopts f:t: opt; do case $opt in f) ARGVAL="OPTARG"; shift;; t) DEVCMD="OPTARG"; shift;; ?) ;; esac done M_SITE_NAME="$1" echo "M_HOME:" $M_HOME #looks good echo "M_SITE_NAME:" $M_SITE_NAME #problem..gives garbage: -techo "No skipping" # Set site, ID M_F_SITE=$(eval echo \$${M_SITE_NAME}_FSITE) #gets from env var, but not filling [[ -z "$M_F_SITE" ]] && m_Log "m_F: \$M_F_SITE not found" && m_exit echo "M_F_SITE here: $M_F_SITE" #problem..gives garbage...hBtecho No skipping_FSITE
... elif [[ "ARGVAL" == "DEV_OVR" ]]; then ...  |
| How to keep previous SSH connections alive while SSH ports get blocked by iptables? Posted: 16 Sep 2021 08:24 AM PDT I'm trying to build a SSH system that lets me in using SSH (port 22). Then If I block the port using iptables: sudo iptables -I INPUT -p tcp --destination-port 22 -j DROP
It would keep the previous connection(s) alive. Is it possible? System: Ubuntu 20  |
| ADD or SUB numbers based on op-code (directive) in the line Posted: 16 Sep 2021 10:41 AM PDT How can I write an awk script that can add or subtract based on what the line in the input file is asking? I figured out how to do either only addition or subtraction, but not either/or in one script. For example, I would want this input: ADD 5,10,20 SUB 30,5,20
to produce this output: 35 -55
This is what I have written so far: #!/bin/awk BEGIN { FS="," } { for(i=1;i<=NF;i++) sum+=$i; print sum; sum=0}
but, obviously, it does addition only, and it doesn't even get all the numbers.  |
| Dynamically update resolv.conf when created by DHCP in limited embeded environment Posted: 16 Sep 2021 09:44 AM PDT I am working with a custom Linux image for an embedded device built with yocto. It has no network management other than the interface configurations for ifup/ifdown. /etc/resolv.conf is created dhcp (dhcpcd) and the system does not have any additional software for managing these files (such as resolvconf or dnsmasq.) # Generated by dhcpcd from eth0.dhcp # /etc/resolv.conf.head can replace this line domain routername.home nameserver 192.168.0.1
With this set up what is it possible to dynamically update /etc/resolv.conf, and have the updates persist?  |
| sed : have a range finishing with the last occurrence of a pattern (greedy range) Posted: 16 Sep 2021 07:19 AM PDT Take the following file : $ cat f1 stu vwx yza uvw xyz abc abc def ghi def ghi jkl ghi jkl mno jkl mno pqr mno pqr stu pqr stu vwx stu vwx yza
To print all lines from the first one containing abc to the first one containing mno with GNU sed : $ sed -n '/abc/,/mno/p' f1 uvw xyz abc abc def ghi def ghi jkl ghi jkl mno
How could I print all lines until the last one containing mno, e.g. how could I get the following result : uvw xyz abc abc def ghi def ghi jkl ghi jkl mno jkl mno pqr mno pqr stu
In other words, is there a way to make GNU sed's range selection greedy ? Update In my setting : - If
mno is missing, it should print out everything until the end of the file. mno cannot occur before the first abc.- There's always at least one
abc, and abc and mno are never on the same line EDIT I just added a dummy stu vwx yza line at the start, so that the file doesn't start with a line including abc (to avoid solutions that start from the first line - they should start from the first line having abc in it)  |
| Deal with nbsp character in shell Posted: 16 Sep 2021 07:05 AM PDT When I use an "alt-gr" character followed by a 'space' character often I miss my input in typing in place of it the "non breaking space character" aka nbsp. Example with piped commands : mount |<space>tail vs mount |<nbsp>tail The last command will trigger an error ..." tail" command unfindable... (notice the visual space before the tail command's name which is in fact a nbsp character). So I found a solution which works perfectly in my case, to simply neutralizing the nbsp character : setxkbmap -option "nbsp:none"
But this changement gains instantly the whole system and for the proof, in LibreOffice Writer if I want to add a nbsp character between two words which must stay grouped, this does not working. From past, I lost a lot of time to determine what was the cause of a non working command or a script or a service which does not start, because of that damn character. So I asked to myself if there is a solution to make the neutralisation limited only to the shell (console, terminal, vty, tty, and so) ? In bash or other shell ... Could you give me what role this damn nbsp character have in shell ? Where and when using it and for what ? What we loose to not using it ? Another suggestion : instead of neutralize it can we reveal it by a graphic character with color ?  |
| Android studio freezing Fedora Posted: 16 Sep 2021 10:06 AM PDT Since the last upgrade to Android Studio (Android Studio Arctic Fox | 2020.3.1 Patch 2 Build #AI-203.7717.56.2031.7678000), I am experiencing frequent global system freezes in Fedora 33. Nothing responding, even the SSH server, so the only solution is a hard reboot. It always freezes while typing. In there anyone here with the same problem? EDIT By request, I'm adding the output of dmesg --level=alert,crit,err,warn. I hope the information needed is still there: [ 0.165884] MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details. [ 0.165948] #5 #6 #7 [ 0.172490] pmd_set_huge: Cannot satisfy [mem 0xf8000000-0xf8200000] with a huge-page mapping due to MTRR override. [ 0.173015] ENERGY_PERF_BIAS: Set to 'normal', was 'performance' [ 0.287753] wait_for_initramfs() called before rootfs_initcalls [ 4.213705] systemd-sysv-generator[573]: SysV service '/etc/rc.d/init.d/livesys-late' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. [ 4.214895] systemd-sysv-generator[573]: SysV service '/etc/rc.d/init.d/network' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. [ 4.216144] systemd-sysv-generator[573]: SysV service '/etc/rc.d/init.d/livesys' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. [ 4.899093] ACPI Warning: SystemIO range 0x0000000000001828-0x000000000000182F conflicts with OpRegion 0x0000000000001800-0x000000000000187F (\PMIO) (20210331/utaddress-204) [ 4.899732] ACPI Warning: SystemIO range 0x0000000000001C40-0x0000000000001C4F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR) (20210331/utaddress-204) [ 4.900844] ACPI Warning: SystemIO range 0x0000000000001C30-0x0000000000001C3F conflicts with OpRegion 0x0000000000001C00-0x0000000000001C3F (\GPRL) (20210331/utaddress-204) [ 4.901495] ACPI Warning: SystemIO range 0x0000000000001C30-0x0000000000001C3F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR) (20210331/utaddress-204) [ 4.901500] ACPI Warning: SystemIO range 0x0000000000001C00-0x0000000000001C2F conflicts with OpRegion 0x0000000000001C00-0x0000000000001C3F (\GPRL) [ 4.902664] (20210331/utaddress-204) [ 4.902704] ACPI Warning: [ 4.903893] SystemIO range 0x0000000000001C00-0x0000000000001C2F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR) (20210331/utaddress-204) [ 4.903896] lpc_ich: Resource conflict(s) found affecting gpio_ich [ 5.178789] at24 13-0050: supply vcc not found, using dummy regulator [ 5.179916] at24 13-0051: supply vcc not found, using dummy regulator [ 5.181186] at24 13-0052: supply vcc not found, using dummy regulator [ 5.182506] at24 13-0053: supply vcc not found, using dummy regulator [ 5.459435] kauditd_printk_skb: 96 callbacks suppressed [ 5.740341] ext4 filesystem being mounted at /boot supports timestamps until 2038 (0x7fffffff) [ 7.154729] Bluetooth: hci0: command 0x1005 tx timeout [ 9.202670] Bluetooth: hci0: command 0x0c23 tx timeout [ 11.250636] Bluetooth: hci0: command 0x0c14 tx timeout [ 13.298596] Bluetooth: hci0: command 0x0c25 tx timeout [ 15.346559] Bluetooth: hci0: command 0x0c38 tx timeout [ 17.394520] Bluetooth: hci0: command tx timeout [ 1832.091017] IRQ 29: no longer affine to CPU4 [ 1832.093063] IRQ 28: no longer affine to CPU5 [ 1832.093066] IRQ 30: no longer affine to CPU5 [ 1832.094878] IRQ 23: no longer affine to CPU6 [ 1832.094882] IRQ 25: no longer affine to CPU6 [ 1832.094885] IRQ 32: no longer affine to CPU6 [ 1832.096684] IRQ 18: no longer affine to CPU7 [ 1832.096687] IRQ 19: no longer affine to CPU7 [ 1832.096690] IRQ 27: no longer affine to CPU7 [ 1834.430082] Bluetooth: hci0: command 0x0c16 tx timeout [ 1836.478094] Bluetooth: hci0: command 0x2002 tx timeout [ 1837.499045] ata3: link is slow to respond, please be patient (ready=0) [ 1837.500053] ata1: link is slow to respond, please be patient (ready=0) [ 1838.525986] Bluetooth: hci0: command 0x2003 tx timeout [ 1840.574009] Bluetooth: hci0: command 0x201c tx timeout [ 1842.495776] Bluetooth: hci0: command tx timeout [18453.352264] IRQ 29: no longer affine to CPU4 [18453.354087] IRQ 23: no longer affine to CPU5 [18453.354091] IRQ 25: no longer affine to CPU5 [18453.355958] IRQ 16: no longer affine to CPU6 [18453.355963] IRQ 26: no longer affine to CPU6 [18453.355967] IRQ 32: no longer affine to CPU6 [18453.357790] IRQ 19: no longer affine to CPU7 [18453.357796] IRQ 28: no longer affine to CPU7 [18453.357799] IRQ 30: no longer affine to CPU7 [18455.781051] done. [18457.872004] Bluetooth: hci0: command 0x1001 tx timeout [18458.761887] ata1: link is slow to respond, please be patient (ready=0) [18458.762881] ata3: link is slow to respond, please be patient (ready=0) [18459.919872] Bluetooth: hci0: command 0x1009 tx timeout
EDIT 2 It just crashed again. Output of dmesg --level=alert,crit,err,warn: [ 0.165915] MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details. [ 0.165973] #5 #6 #7 [ 0.172521] pmd_set_huge: Cannot satisfy [mem 0xf8000000-0xf8200000] with a huge-page mapping due to MTRR override. [ 0.173044] ENERGY_PERF_BIAS: Set to 'normal', was 'performance' [ 0.287783] wait_for_initramfs() called before rootfs_initcalls [ 7.086711] usb 3-5: device descriptor read/64, error -110 [ 8.324313] kauditd_printk_skb: 5 callbacks suppressed [ 8.940835] systemd-sysv-generator[574]: SysV service '/etc/rc.d/init.d/livesys-late' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. [ 8.942438] systemd-sysv-generator[574]: SysV service '/etc/rc.d/init.d/network' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. [ 8.944077] systemd-sysv-generator[574]: SysV service '/etc/rc.d/init.d/livesys' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. [ 9.619007] ACPI Warning: SystemIO range 0x0000000000001828-0x000000000000182F conflicts with OpRegion 0x0000000000001800-0x000000000000187F (\PMIO) (20210331/utaddress-204) [ 9.619640] ACPI Warning: SystemIO range 0x0000000000001C40-0x0000000000001C4F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR) (20210331/utaddress-204) [ 9.621931] ACPI Warning: SystemIO range 0x0000000000001C30-0x0000000000001C3F conflicts with OpRegion 0x0000000000001C00-0x0000000000001C3F (\GPRL) (20210331/utaddress-204) [ 9.622116] ACPI Warning: SystemIO range 0x0000000000001C30-0x0000000000001C3F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR) (20210331/utaddress-204) [ 9.623233] ACPI Warning: SystemIO range 0x0000000000001C00-0x0000000000001C2F conflicts with OpRegion 0x0000000000001C00-0x0000000000001C3F (\GPRL) (20210331/utaddress-204) [ 9.624779] ACPI Warning: SystemIO range 0x0000000000001C00-0x0000000000001C2F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR) (20210331/utaddress-204) [ 9.625544] lpc_ich: Resource conflict(s) found affecting gpio_ich [ 9.786915] at24 13-0050: supply vcc not found, using dummy regulator [ 9.789823] at24 13-0051: supply vcc not found, using dummy regulator [ 9.791691] at24 13-0052: supply vcc not found, using dummy regulator [ 9.793324] at24 13-0053: supply vcc not found, using dummy regulator [ 10.174554] ext4 filesystem being mounted at /boot supports timestamps until 2038 (0x7fffffff) [ 13.354089] kauditd_printk_skb: 87 callbacks suppressed
EDIT 3 I've experienced around 10 freezes in a couple of days. I'm afraid Studio is going to harm my computer. Freezing continues despite that I upgraded the whole system to the last Fedora 34. Last output of dmesg --level=alert,crit,err,warn: [ 0.166421] MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details. [ 0.166484] #5 #6 #7 [ 0.173036] pmd_set_huge: Cannot satisfy [mem 0xf8000000-0xf8200000] with a huge-page mapping due to MTRR override. [ 0.173550] ENERGY_PERF_BIAS: Set to 'normal', was 'performance' [ 0.287346] wait_for_initramfs() called before rootfs_initcalls [ 3.397929] systemd-sysv-generator[567]: SysV service '/etc/rc.d/init.d/livesys-late' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. [ 3.399641] systemd-sysv-generator[567]: SysV service '/etc/rc.d/init.d/network' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. [ 3.400982] systemd-sysv-generator[567]: SysV service '/etc/rc.d/init.d/livesys' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. [ 3.713080] systemd-journald[593]: File /var/log/journal/9ff77e59cfd04f078e4b747742c5981e/system.journal corrupted or uncleanly shut down, renaming and replacing. [ 4.036564] ACPI Warning: SystemIO range 0x0000000000001828-0x000000000000182F conflicts with OpRegion 0x0000000000001800-0x000000000000187F (\PMIO) (20210331/utaddress-204) [ 4.037179] ACPI Warning: SystemIO range 0x0000000000001C40-0x0000000000001C4F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR) (20210331/utaddress-204) [ 4.038257] ACPI Warning: SystemIO range 0x0000000000001C30-0x0000000000001C3F conflicts with OpRegion 0x0000000000001C00-0x0000000000001C3F (\GPRL) (20210331/utaddress-204) [ 4.038808] ACPI Warning: SystemIO range 0x0000000000001C30-0x0000000000001C3F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR) (20210331/utaddress-204) [ 4.039932] ACPI Warning: SystemIO range 0x0000000000001C00-0x0000000000001C2F conflicts with OpRegion 0x0000000000001C00-0x0000000000001C3F (\GPRL) (20210331/utaddress-204) [ 4.041794] ACPI Warning: SystemIO range 0x0000000000001C00-0x0000000000001C2F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR) (20210331/utaddress-204) [ 4.042527] lpc_ich: Resource conflict(s) found affecting gpio_ich [ 4.468471] at24 13-0050: supply vcc not found, using dummy regulator [ 4.470405] at24 13-0051: supply vcc not found, using dummy regulator [ 4.474870] at24 13-0052: supply vcc not found, using dummy regulator [ 4.476069] at24 13-0053: supply vcc not found, using dummy regulator [ 4.637421] ext4 filesystem being mounted at /boot supports timestamps until 2038 (0x7fffffff) [ 5.321533] kauditd_printk_skb: 100 callbacks suppressed
EDIT 4 Another freeze. journalctl output of the kernel crash: $ journalctl -S '2021-09-16 13:30:00' 13:43:57 Orion kernel: general protection fault, probably for non-canonical address 0x108ddb743acd5eb1: 0000 [#1] SMP PTI 13:43:57 Orion kernel: CPU: 4 PID: 2724 Comm: Xorg Not tainted 5.13.15-200.fc34.x86_64 #1 13:43:57 Orion kernel: Hardware name: Dell Inc. XPS 8700/0KWVT8, BIOS A07 03/13/2014 13:43:57 Orion kernel: RIP: 0010:kmem_cache_alloc_trace+0xac/0x220 13:43:57 Orion kernel: Code: aa 20 d1 44 49 8b 00 49 83 78 10 00 48 89 44 24 08 0f 84 43 01 00 00 48 85 c0 0f 84 3a 01 00 00 8b 4d 28 48 8b 7d 00 48 01 c1 <48> 8b 19 48 89 ce 48> 13:43:57 Orion kernel: RSP: 0018:ffffb7d901f3f700 EFLAGS: 00010206 13:43:57 Orion kernel: RAX: 108ddb743acd5e81 RBX: 0000000000000002 RCX: 108ddb743acd5eb1 13:43:57 Orion kernel: RDX: 0000000000728bcf RSI: 0000000000000dc0 RDI: 00000000000300c0 13:43:57 Orion kernel: RBP: ffff8dd200042600 R08: ffff8dd50ed300c0 R09: 0000000000000018 13:43:57 Orion kernel: R10: ffff8dd12d26f208 R11: ffffb7d901f3f988 R12: 0000000000000dc0 13:43:57 Orion kernel: R13: ffff8dd200042600 R14: 0000000000003000 R15: ffffffffc06922ce 13:43:57 Orion kernel: FS: 00007f32b7bcea80(0000) GS:ffff8dd50ed00000(0000) knlGS:0000000000000000 13:43:57 Orion kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 13:43:57 Orion kernel: CR2: 00007f32b778d000 CR3: 000000010984e003 CR4: 00000000001706e0 13:43:57 Orion kernel: Call Trace: 13:43:57 Orion kernel: nvkm_mem_new_type+0xae/0x2a0 [nouveau] 13:43:57 Orion kernel: nvkm_umem_new+0x130/0x220 [nouveau] 13:43:57 Orion kernel: nvkm_ioctl_new+0x129/0x1e0 [nouveau] 13:43:57 Orion kernel: ? nvkm_umem_search+0xe0/0xe0 [nouveau] 13:43:57 Orion kernel: nvkm_ioctl+0xdc/0x180 [nouveau] 13:43:57 Orion kernel: nvif_object_ctor+0x122/0x1c0 [nouveau] 13:43:57 Orion kernel: nvif_mem_ctor_type+0xc2/0x180 [nouveau] 13:43:57 Orion kernel: ? nvkm_vmm_ptes_get_map+0x2c/0x90 [nouveau] 13:43:57 Orion kernel: ? nvkm_vmm_map+0x18d/0x350 [nouveau] 13:43:57 Orion kernel: nouveau_mem_host+0xf3/0x190 [nouveau] 13:43:57 Orion kernel: nouveau_sgdma_bind+0x30/0x80 [nouveau] 13:43:57 Orion kernel: nouveau_bo_move+0x3c1/0x820 [nouveau] 13:43:57 Orion kernel: ? ttm_pool_type_take+0x7d/0x90 [ttm] 13:43:57 Orion kernel: ? ttm_pool_alloc+0xe6/0x590 [ttm] 13:43:57 Orion kernel: ttm_bo_handle_move_mem+0x90/0x170 [ttm] 13:43:57 Orion kernel: ttm_bo_validate+0x11c/0x150 [ttm] 13:43:57 Orion kernel: ttm_bo_init_reserved+0x239/0x2c0 [ttm] 13:43:57 Orion kernel: ttm_bo_init+0x4a/0xc0 [ttm] 13:43:57 Orion kernel: ? nv10_bo_put_tile_region.isra.0+0x80/0x80 [nouveau] 13:43:57 Orion kernel: nouveau_bo_init+0x7c/0x90 [nouveau] 13:43:57 Orion kernel: ? nv10_bo_put_tile_region.isra.0+0x80/0x80 [nouveau] 13:43:57 Orion kernel: ? nouveau_gem_new+0xf0/0xf0 [nouveau] 13:43:57 Orion kernel: nouveau_gem_new+0x7f/0xf0 [nouveau] 13:43:57 Orion kernel: nouveau_gem_ioctl_new+0x45/0xe0 [nouveau] 13:43:57 Orion kernel: ? nouveau_gem_new+0xf0/0xf0 [nouveau] 13:43:57 Orion kernel: drm_ioctl_kernel+0x86/0xd0 [drm] 13:43:57 Orion kernel: drm_ioctl+0x220/0x3e0 [drm] 13:43:57 Orion kernel: ? nouveau_gem_new+0xf0/0xf0 [nouveau] 13:43:57 Orion kernel: ? __ia32_sys_timer_getoverrun+0x40/0x50 13:43:57 Orion kernel: nouveau_drm_ioctl+0x55/0xa0 [nouveau] 13:43:57 Orion kernel: __x64_sys_ioctl+0x82/0xb0 13:43:57 Orion kernel: do_syscall_64+0x40/0x80 13:43:57 Orion kernel: entry_SYSCALL_64_after_hwframe+0x44/0xae 13:43:57 Orion kernel: RIP: 0033:0x7f32b84540ab 13:43:57 Orion kernel: Code: ff ff ff 85 c0 79 9b 49 c7 c4 ff ff ff ff 5b 5d 4c 89 e0 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73> 13:43:57 Orion kernel: RSP: 002b:00007ffdd87e5148 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 13:43:57 Orion kernel: RAX: ffffffffffffffda RBX: 00007ffdd87e51a0 RCX: 00007f32b84540ab 13:43:57 Orion kernel: RDX: 00007ffdd87e51a0 RSI: 00000000c0306480 RDI: 000000000000000f 13:43:57 Orion kernel: RBP: 00000000c0306480 R08: 0000556e9a4293d0 R09: 0000000000000016 13:43:57 Orion kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 0000556e994bc7e0 13:43:57 Orion kernel: R13: 000000000000000f R14: 00007ffdd87e51a0 R15: 0000000000003000 13:43:57 Orion kernel: Modules linked in: tun cdc_acm md4 nls_utf8 cifs dns_resolver fscache netfs libdes snd_seq_dummy snd_hrtimer dm_crypt trusted asn1_encoder xt_nat iptable_> 13:43:57 Orion kernel: drm_ttm_helper ttm i2c_algo_bit mxm_wmi crct10dif_pclmul crc32_pclmul crc32c_intel wmi drm_kms_helper ghash_clmulni_intel cec drm r8169 video uas usb_sto> 13:43:57 Orion kernel: ---[ end trace 6a741c284e912584 ]--- 13:43:57 Orion kernel: RIP: 0010:kmem_cache_alloc_trace+0xac/0x220 13:43:57 Orion kernel: Code: aa 20 d1 44 49 8b 00 49 83 78 10 00 48 89 44 24 08 0f 84 43 01 00 00 48 85 c0 0f 84 3a 01 00 00 8b 4d 28 48 8b 7d 00 48 01 c1 <48> 8b 19 48 89 ce 48> 13:43:57 Orion kernel: RSP: 0018:ffffb7d901f3f700 EFLAGS: 00010206 13:43:57 Orion kernel: general protection fault, probably for non-canonical address 0x108ddb743acd5eb1: 0000 [#1] SMP PTI 13:43:57 Orion kernel: CPU: 4 PID: 2724 Comm: Xorg Not tainted 5.13.15-200.fc34.x86_64 #1 13:43:57 Orion kernel: Hardware name: Dell Inc. XPS 8700/0KWVT8, BIOS A07 03/13/2014 13:43:57 Orion kernel: RIP: 0010:kmem_cache_alloc_trace+0xac/0x220 13:43:57 Orion kernel: Code: aa 20 d1 44 49 8b 00 49 83 78 10 00 48 89 44 24 08 0f 84 43 01 00 00 48 85 c0 0f 84 3a 01 00 00 8b 4d 28 48 8b 7d 00 48 01 c1 <48> 8b 19 48 89 ce 48> 13:43:57 Orion kernel: RSP: 0018:ffffb7d901f3f700 EFLAGS: 00010206 13:43:57 Orion kernel: RAX: 108ddb743acd5e81 RBX: 0000000000000002 RCX: 108ddb743acd5eb1 13:43:57 Orion kernel: RDX: 0000000000728bcf RSI: 0000000000000dc0 RDI: 00000000000300c0 13:43:57 Orion kernel: RBP: ffff8dd200042600 R08: ffff8dd50ed300c0 R09: 0000000000000018 13:43:57 Orion kernel: R10: ffff8dd12d26f208 R11: ffffb7d901f3f988 R12: 0000000000000dc0 13:43:57 Orion kernel: R13: ffff8dd200042600 R14: 0000000000003000 R15: ffffffffc06922ce 13:43:57 Orion kernel: FS: 00007f32b7bcea80(0000) GS:ffff8dd50ed00000(0000) knlGS:0000000000000000 13:43:57 Orion kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 13:43:57 Orion kernel: CR2: 00007f32b778d000 CR3: 000000010984e003 CR4: 00000000001706e0 13:43:57 Orion kernel: Call Trace: 13:43:57 Orion kernel: nvkm_mem_new_type+0xae/0x2a0 [nouveau] 13:43:57 Orion kernel: nvkm_umem_new+0x130/0x220 [nouveau] 13:43:57 Orion kernel: nvkm_ioctl_new+0x129/0x1e0 [nouveau] 13:43:57 Orion kernel: ? nvkm_umem_search+0xe0/0xe0 [nouveau] 13:43:57 Orion kernel: nvkm_ioctl+0xdc/0x180 [nouveau] 13:43:57 Orion kernel: nvif_object_ctor+0x122/0x1c0 [nouveau] 13:43:57 Orion kernel: nvif_mem_ctor_type+0xc2/0x180 [nouveau] 13:43:57 Orion kernel: ? nvkm_vmm_ptes_get_map+0x2c/0x90 [nouveau] 13:43:57 Orion kernel: ? nvkm_vmm_map+0x18d/0x350 [nouveau] 13:43:57 Orion kernel: nouveau_mem_host+0xf3/0x190 [nouveau] 13:43:57 Orion kernel: nouveau_sgdma_bind+0x30/0x80 [nouveau] 13:43:57 Orion kernel: nouveau_bo_move+0x3c1/0x820 [nouveau] 13:43:57 Orion kernel: ? ttm_pool_type_take+0x7d/0x90 [ttm] 13:43:57 Orion kernel: ? ttm_pool_alloc+0xe6/0x590 [ttm] 13:43:57 Orion kernel: ttm_bo_handle_move_mem+0x90/0x170 [ttm] 13:43:57 Orion kernel: ttm_bo_validate+0x11c/0x150 [ttm] 13:43:57 Orion kernel: ttm_bo_init_reserved+0x239/0x2c0 [ttm] 13:43:57 Orion kernel: ttm_bo_init+0x4a/0xc0 [ttm] 13:43:57 Orion kernel: ? nv10_bo_put_tile_region.isra.0+0x80/0x80 [nouveau] 13:43:57 Orion kernel: nouveau_bo_init+0x7c/0x90 [nouveau] 13:43:57 Orion kernel: ? nv10_bo_put_tile_region.isra.0+0x80/0x80 [nouveau] 13:43:57 Orion kernel: ? nouveau_gem_new+0xf0/0xf0 [nouveau] 13:43:57 Orion kernel: nouveau_gem_new+0x7f/0xf0 [nouveau] 13:43:57 Orion kernel: nouveau_gem_ioctl_new+0x45/0xe0 [nouveau] 13:43:57 Orion kernel: ? nouveau_gem_new+0xf0/0xf0 [nouveau] 13:43:57 Orion kernel: drm_ioctl_kernel+0x86/0xd0 [drm] 13:43:57 Orion kernel: drm_ioctl+0x220/0x3e0 [drm] 13:43:57 Orion kernel: ? nouveau_gem_new+0xf0/0xf0 [nouveau] 13:43:57 Orion kernel: ? __ia32_sys_timer_getoverrun+0x40/0x50 13:43:57 Orion kernel: nouveau_drm_ioctl+0x55/0xa0 [nouveau] 13:43:57 Orion kernel: __x64_sys_ioctl+0x82/0xb0 13:43:57 Orion kernel: do_syscall_64+0x40/0x80 13:43:57 Orion kernel: entry_SYSCALL_64_after_hwframe+0x44/0xae 13:43:57 Orion kernel: RIP: 0033:0x7f32b84540ab 13:43:57 Orion kernel: Code: ff ff ff 85 c0 79 9b 49 c7 c4 ff ff ff ff 5b 5d 4c 89 e0 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73> 13:43:57 Orion kernel: RSP: 002b:00007ffdd87e5148 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 13:43:57 Orion kernel: RAX: ffffffffffffffda RBX: 00007ffdd87e51a0 RCX: 00007f32b84540ab 13:43:57 Orion kernel: RDX: 00007ffdd87e51a0 RSI: 00000000c0306480 RDI: 000000000000000f 13:43:57 Orion kernel: RBP: 00000000c0306480 R08: 0000556e9a4293d0 R09: 0000000000000016 13:43:57 Orion kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 0000556e994bc7e0 13:43:57 Orion kernel: R13: 000000000000000f R14: 00007ffdd87e51a0 R15: 0000000000003000 13:43:57 Orion kernel: Modules linked in: tun cdc_acm md4 nls_utf8 cifs dns_resolver fscache netfs libdes snd_seq_dummy snd_hrtimer dm_crypt trusted asn1_encoder xt_nat iptable_> 13:43:57 Orion kernel: drm_ttm_helper ttm i2c_algo_bit mxm_wmi crct10dif_pclmul crc32_pclmul crc32c_intel wmi drm_kms_helper ghash_clmulni_intel cec drm r8169 video uas usb_sto> 13:43:57 Orion kernel: ---[ end trace 6a741c284e912584 ]--- 13:43:57 Orion kernel: RIP: 0010:kmem_cache_alloc_trace+0xac/0x220 13:43:57 Orion kernel: Code: aa 20 d1 44 49 8b 00 49 83 78 10 00 48 89 44 24 08 0f 84 43 01 00 00 48 85 c0 0f 84 3a 01 00 00 8b 4d 28 48 8b 7d 00 48 01 c1 <48> 8b 19 48 89 ce 48> 13:43:57 Orion kernel: RSP: 0018:ffffb7d901f3f700 EFLAGS: 00010206 13:43:57 Orion kernel: RAX: 108ddb743acd5e81 RBX: 0000000000000002 RCX: 108ddb743acd5eb1 13:43:57 Orion kernel: RDX: 0000000000728bcf RSI: 0000000000000dc0 RDI: 00000000000300c0 13:43:57 Orion kernel: RBP: ffff8dd200042600 R08: ffff8dd50ed300c0 R09: 0000000000000018 13:43:57 Orion kernel: R10: ffff8dd12d26f208 R11: ffffb7d901f3f988 R12: 0000000000000dc0 13:43:57 Orion kernel: R13: ffff8dd200042600 R14: 0000000000003000 R15: ffffffffc06922ce 13:43:57 Orion kernel: FS: 00007f32b7bcea80(0000) GS:ffff8dd50ed00000(0000) knlGS:0000000000000000 13:43:57 Orion kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 13:43:57 Orion kernel: CR2: 00007f32b778d000 CR3: 000000010984e003 CR4: 00000000001706e0 13:44:32 Orion kernel: usb 4-5: USB disconnect, device number 2 13:44:32 Orion kernel: sd 6:0:0:0: [sde] Synchronizing SCSI cache 13:44:32 Orion kernel: sd 6:0:0:0: [sde] Synchronize Cache(10) failed: Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK 13:44:32 Orion kernel: usb 4-5: new SuperSpeed USB device number 3 using xhci_hcd 13:44:32 Orion kernel: usb 4-5: New USB device found, idVendor=0781, idProduct=5580, bcdDevice= 0.10 13:44:32 Orion kernel: usb 4-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3 13:44:32 Orion kernel: usb 4-5: Product: Extreme 13:44:32 Orion kernel: usb 4-5: Manufacturer: SanDisk 13:44:32 Orion kernel: usb 4-5: SerialNumber: AA010527142139551888 13:44:32 Orion kernel: usb-storage 4-5:1.0: USB Mass Storage device detected 13:44:32 Orion kernel: scsi host9: usb-storage 4-5:1.0 13:44:32 Orion mtp-probe[251591]: checking bus 4, device 3: "/sys/devices/pci0000:00/0000:00:14.0/usb4/4-5" 13:44:32 Orion mtp-probe[251591]: bus: 4, device: 3 was not an MTP device 13:44:32 Orion mtp-probe[251597]: checking bus 4, device 3: "/sys/devices/pci0000:00/0000:00:14.0/usb4/4-5" 13:44:32 Orion mtp-probe[251597]: bus: 4, device: 3 was not an MTP device 13:44:33 Orion kernel: scsi 9:0:0:0: Direct-Access SanDisk Extreme 0001 PQ: 0 ANSI: 6 13:44:33 Orion kernel: sd 9:0:0:0: Attached scsi generic sg4 type 0 13:44:33 Orion kernel: sd 9:0:0:0: [sdn] 125045424 512-byte logical blocks: (64.0 GB/59.6 GiB) 13:44:33 Orion kernel: sd 9:0:0:0: [sdn] Write Protect is off 13:44:33 Orion kernel: sd 9:0:0:0: [sdn] Mode Sense: 33 00 00 08 13:44:33 Orion kernel: sd 9:0:0:0: [sdn] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA 13:44:33 Orion kernel: sdn: sdn1 sdn2 13:44:33 Orion kernel: sd 9:0:0:0: [sdn] Attached SCSI disk 13:45:01 Orion CROND[251616]: (root) CMD ([[ "`pgrep -x each5min`" ]] || each5min >& /dev/console) 13:45:01 Orion CROND[251615]: (root) CMDEND ([[ "`pgrep -x each5min`" ]] || each5min >& /dev/console) 13:45:06 Orion sshd[251632]: rexec line 123: Deprecated option UsePrivilegeSeparation 13:45:06 Orion audit[251633]: CRYPTO_KEY_USER pid=251633 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='op=destroy kind=server fp=SHA256:ee:51:4b:d5:b0:6a:97:cd:fa:74:d8:> 13:45:06 Orion audit[251632]: CRYPTO_SESSION pid=251632 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='op=start direction=from-server cipher=aes256-gcm@openssh.com ksize=> 13:45:06 Orion audit[251632]: CRYPTO_SESSION pid=251632 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='op=start direction=from-client cipher=aes256-gcm@openssh.com ksize=> 13:45:06 Orion kernel: general protection fault, probably for non-canonical address 0x108ddb743acd5eb1: 0000 [#2] SMP PTI 13:45:06 Orion kernel: CPU: 4 PID: 251632 Comm: sshd Tainted: G D 5.13.15-200.fc34.x86_64 #1 13:45:06 Orion kernel: Hardware name: Dell Inc. XPS 8700/0KWVT8, BIOS A07 03/13/2014 13:45:06 Orion kernel: RIP: 0010:__kmalloc+0xc7/0x260 13:45:06 Orion kernel: Code: 05 de 1d d1 44 49 8b 00 49 83 78 10 00 48 89 04 24 0f 84 70 01 00 00 48 85 c0 0f 84 67 01 00 00 8b 4d 28 48 8b 7d 00 48 01 c1 <48> 8b 19 48 89 ce 48> 13:45:06 Orion kernel: RSP: 0018:ffffb7d90d6a78c0 EFLAGS: 00010206 13:45:06 Orion kernel: RAX: 108ddb743acd5e81 RBX: 0000000000000000 RCX: 108ddb743acd5eb1 13:45:06 Orion kernel: RDX: 0000000000728bcf RSI: 0000000000000d40 RDI: 00000000000300c0 13:45:06 Orion kernel: RBP: ffff8dd200042600 R08: ffff8dd50ed300c0 R09: 0000000000000002 13:45:06 Orion kernel: R10: 00000000002c4051 R11: 0000000000000001 R12: 0000000000000d40 13:45:06 Orion kernel: R13: 0000000000000060 R14: ffff8dd200042600 R15: ffffffffbb4003b1 13:45:06 Orion kernel: FS: 00007f77fe857900(0000) GS:ffff8dd50ed00000(0000) knlGS:0000000000000000 13:45:06 Orion kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 13:45:06 Orion kernel: CR2: 00007f77ff4ed49f CR3: 000000010469c002 CR4: 00000000001706e0 13:43:57 Orion kernel: general protection fault, probably for non-canonical address 0x108ddb743acd5eb1: 0000 [#1] SMP PTI 13:43:57 Orion kernel: CPU: 4 PID: 2724 Comm: Xorg Not tainted 5.13.15-200.fc34.x86_64 #1 13:43:57 Orion kernel: Hardware name: Dell Inc. XPS 8700/0KWVT8, BIOS A07 03/13/2014 13:43:57 Orion kernel: RIP: 0010:kmem_cache_alloc_trace+0xac/0x220 13:43:57 Orion kernel: Code: aa 20 d1 44 49 8b 00 49 83 78 10 00 48 89 44 24 08 0f 84 43 01 00 00 48 85 c0 0f 84 3a 01 00 00 8b 4d 28 48 8b 7d 00 48 01 c1 <48> 8b 19 48 89 ce 48> 13:43:57 Orion kernel: RSP: 0018:ffffb7d901f3f700 EFLAGS: 00010206 13:43:57 Orion kernel: RAX: 108ddb743acd5e81 RBX: 0000000000000002 RCX: 108ddb743acd5eb1 13:43:57 Orion kernel: RDX: 0000000000728bcf RSI: 0000000000000dc0 RDI: 00000000000300c0 13:43:57 Orion kernel: RBP: ffff8dd200042600 R08: ffff8dd50ed300c0 R09: 0000000000000018 13:43:57 Orion kernel: R10: ffff8dd12d26f208 R11: ffffb7d901f3f988 R12: 0000000000000dc0 13:43:57 Orion kernel: R13: ffff8dd200042600 R14: 0000000000003000 R15: ffffffffc06922ce 13:43:57 Orion kernel: FS: 00007f32b7bcea80(0000) GS:ffff8dd50ed00000(0000) knlGS:0000000000000000 13:43:57 Orion kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 13:43:57 Orion kernel: CR2: 00007f32b778d000 CR3: 000000010984e003 CR4: 00000000001706e0 13:43:57 Orion kernel: Call Trace: 13:43:57 Orion kernel: nvkm_mem_new_type+0xae/0x2a0 [nouveau] 13:43:57 Orion kernel: nvkm_umem_new+0x130/0x220 [nouveau] 13:43:57 Orion kernel: nvkm_ioctl_new+0x129/0x1e0 [nouveau] 13:43:57 Orion kernel: ? nvkm_umem_search+0xe0/0xe0 [nouveau] 13:43:57 Orion kernel: nvkm_ioctl+0xdc/0x180 [nouveau] 13:43:57 Orion kernel: nvif_object_ctor+0x122/0x1c0 [nouveau] 13:43:57 Orion kernel: nvif_mem_ctor_type+0xc2/0x180 [nouveau] 13:43:57 Orion kernel: ? nvkm_vmm_ptes_get_map+0x2c/0x90 [nouveau]
....  |
| Metered network Posted: 16 Sep 2021 10:02 AM PDT My mobile ISP handles a data limit of 12,5GB, and I'm using Manjaro Linux. I'm asking myself how a "metered" connection will save data. In the NetworkManager, there are three different options under the "edit connections" tab "general", and for the setting "metered connection" the options are: "yes", "no", "automatic". What is the difference between those three? I mean, how can "automatic" declare a data limit on the connection?  |
| bash rotation script Posted: 16 Sep 2021 08:07 AM PDT I have a directory structure as follows: backup-2018-01-12 backup-2018-01-13 backup-2018-01-14 backup-2018-01-15 backup-2018-01-16 backup-2018-01-17 backup-2018-01-18 backup-2018-01-19 backup-2018-01-20 backup-2018-01-21 backup-2018-01-22 backup-2018-01-23 backup-2018-01-24 backup-2018-01-25 backup-2018-01-26 backup-2018-01-27 backup-2018-01-28 backup-2018-01-29 backup-2018-01-30 backup-2018-01-31 backup-2018-02-01 backup-2018-02-02 backup-2018-02-03 backup-2018-02-04 backup-2018-02-05 backup-2018-02-06 backup-2018-02-07 backup-2018-02-08 backup-2018-02-09 backup-2018-02-10 backup-2018-02-11 backup-2018-02-12 backup-2018-02-13 backup-2018-02-14 backup-2018-02-15
How can I use a script to save the latest 7 days and the the last backup of each week for 4 weeks long E.g So I keep backup-2018-01-25 <-- this is 3 waeks from now and so on. backup-2018-02-02 <-- this is 2 weeks earlier from now backup-2018-02-09 backup-2018-02-10 backup-2018-02-11 backup-2018-02-12 backup-2018-02-13 backup-2018-02-14 backup-2018-02-15
So I tried find -type d -name 'backup-*' -mtime +7 -exec rm -v {} \;
and this does keep the latest 7 but removes everything older than 7 days.  |
| rm: refusing to remove '.' or '..' directory: skipping '..' Posted: 16 Sep 2021 07:05 AM PDT Why when I try to delete .. from directory I receive error: rm: refusing to remove '.' or '..' directory: skipping '..'
And before you ask why I want to do this: Just because.  |
| Get info about installed and remote packages with pacman Posted: 16 Sep 2021 09:43 AM PDT I'm using pacman 5.0.1 on Arch Linux and I'd like to get information about packages installed on my machine as well as packages in the remote repositories. Information should include a description of the package, its size, and its build date.  |
| Cannot bypass login screen with correct credentials and no errors in Kali Linux Posted: 16 Sep 2021 10:03 AM PDT Today I downloaded the latest VMware image of Kali Linux (Kali Linux 64 bit VM). After that, I configured the hostname in /etc/hostname and adapted also the /etc/hosts to set permanently a hostname. Then, I executed the following commands: apt-get upgrade && apt-get update dpkg --add-architecture i386 apt-get update apt-get install wine32 apt-get install clamav apt-get install clamav-freshclam
and rebooted afterwards. Then, something strange happened. I was no longer able to login with the default credentials root and toor. Although, I did not get the error message Sorry, that didn't work. Please try again., I could not get past the login screen. However, I noticed that I am able to login when selecting GNOME on Wayland and also booting in recovery mode. 
Any idea what is causing this issue?  |
| NAS share not mounting on linux boot through /etc/fstab Posted: 16 Sep 2021 07:05 AM PDT I have a NAS share for my Linux server which I mount using the following command. mount -t nfs 172.16.2.115:/shares/OwnCloud /eStore/
now to automate this I added the following line in /etc/fstab 172.16.2.115:/shares/OwnCloud /eStore nfs rw,addr=172.16.2.115,auto 0 0
but it is not working and I am not getting any error also. If I execute mount -a then mount is able to mount the NAS based on /etc/fstab configuration. I would like it to mount at boot.  |
| Cleaning up sources.list and sources.list.d Posted: 16 Sep 2021 08:01 AM PDT For some reason, mostly due to my incompetence, there is some invalid address ( ie 404 ) pointed by my sources.list, and from some files contained under sources.list.d ( this is an way extending sources.list, without modifying it, isn't?). Is there some command to remove not responding addresses, or should I write some script?  |
| How to use variables in substitution with vim regular expressions Posted: 16 Sep 2021 08:44 AM PDT I have a big file that contains among others serveral lines of the following form: USet07-1 USet07-2 USet08-1 USet08-2 . . . USet22-2 . . .
I want to remove the hyphen/dash - from these strings in vim. I search for the strings with: :/USet\d\d-\d
but when I try to replace these with :%s/Uset\d\d-\d/USet\d\d\d
I obviously get USetddd
for all instances. But what I want is: USet071 USet072 USet081 USet082 . . . USet222 . . .
How can this be done? Can I reuse parts of the matched string and use it in the substitution?  |
| Can I use fio on a mounted device? Posted: 16 Sep 2021 09:04 AM PDT I'm using fio to get some broad read IOPS performance data for various storage configurations like this: fio --name=readiops --filename=/dev/md1 --direct=1 --rw=randread --bs=4k --numjobs=4 --iodepth=32 --direct=1 --iodepth_batch=16 --iodepth_batch_complete=16 \ --runtime=100 --ramp_time=5 --norandommap --time_based --ioengine=libaio --group_reporting readiops: (g=0): rw=randread, bs=4K-4K/4K-4K/4K-4K, ioengine=libaio, iodepth=32 ... fio-2.1.11 Starting 4 processes Jobs: 4 (f=4): [r(4)] [100.0% done] [3504MB/0KB/0KB /s] [897K/0/0 iops] [eta 00m:00s] readiops: (groupid=0, jobs=4): err= 0: pid=10458: Thu Jan 15 05:49:28 2015 ...
I'd like to compare the figures I'm getting with an array that is in production use at a quiet time, is this possible to do without affecting the data on the array? There is a --readonly option (duplicated for some reason) in the man page but it isn't 100% clear to me that this is what I'm after: --readonly
Enable read-only safety checks.
...
--readonly
Turn on safety read-only checks, preventing any attempted write.  |
| Format the content of the file using Perl Posted: 16 Sep 2021 08:17 AM PDT I have a file with the following format: >Country1 Aus trali a >Country5 Swi tzer land >Country2 Net herland s
I want to output a file with the following format: >Country1 Australia >Country5 Switzerland >Country2 Netherlands
 |
No comments:
Post a Comment