The system stops responding

sylver

sylver

New Member
Joined
Dec 31, 2023
Messages
28
Reaction score
4
Credits
331
Hi, I use Fedora 39. The system stops responding all the time, just running office makes it crash, I open gimp and it stops responding.
 


How much RAM do you have?

Next time this happens, after the computer reboots, can you give the output of

dmesg | tail -n 50
 
to check ram a simple command should work

From the terminal run $ free
 
There‘s a couple of possible reasons. Hardware failure, configuration issues, etc.

You could install and use inxi providing a good overview of your system. After installing, run inxi -Fxz
 
Thanks, I did as they asked, all correct, but I think the problem was in my secondary memory, B, I removed her and the problem stopped.
 
1704048464457.png
 
That looks OK you have 8 GB of ram . 2.5 GB used 5.5 GB free
 
The problem seems to be an error between memory and incorrect shutdown.
 
Haui111 said:
There‘s a couple of possible reasons. Hardware failure, configuration issues, etc.

You could install and use inxi providing a good overview of your system. After installing, run inxi -Fxz
Click to expand...
sylver@sylviodjacome:~$ inxi -Fxz
System:
Kernel: 6.6.8-200.fc39.x86_64 arch: x86_64 bits: 64 compiler: gcc
v: 2.40-13.fc39 Desktop: GNOME v: 45.2 Distro: Fedora release 39 (Thirty
Nine)
Machine:
Type: Laptop System: Dell product: Inspiron 15-3567 v: N/A
serial: <superuser required>
Mobo: Dell model: 06J0HF v: A00 serial: <superuser required> UEFI: Dell
v: 2.20.0 date: 07/12/2022
CPU:
Info: dual core model: Intel Core i3-6006U bits: 64 type: MT MCP
arch: Skylake rev: 3 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB
Speed (MHz): avg: 2000 min/max: 400/2000 cores: 1: 2000 2: 2000 3: 2000
4: 2000 bogomips: 15999
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
Device-1: Intel Skylake GT2 [HD Graphics 520] vendor: Dell driver: i915
v: kernel arch: Gen-9 bus-ID: 00:02.0
Device-2: Realtek [] driver: uvcvideo type: USB bus-ID: 1-5:3
Display: wayland server: X.Org v: 23.2.3 with: Xwayland v: 23.2.3
compositor: gnome-shell driver: dri: iris gpu: i915
resolution: 1366x768~60Hz
API: OpenGL v: 4.6 vendor: intel mesa v: 23.3.1 glx-v: 1.4
direct-render: yes renderer: Mesa Intel HD Graphics 520 (SKL GT2)
API: EGL Message: EGL data requires eglinfo. Check --recommends.
Audio:
Device-1: Intel Sunrise Point-LP HD Audio vendor: Dell driver: snd_hda_intel
v: kernel bus-ID: 00:1f.3
API: ALSA v: k6.6.8-200.fc39.x86_64 status: kernel-api
Server-1: JACK v: 1.9.22 status: off
Server-2: PipeWire v: 1.0.0 status: active
Network:
Device-1: Intel Wireless 7265 driver: iwlwifi v: kernel bus-ID: 01:00.0
IF: wlp1s0 state: up mac: <filter>
Device-2: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell
driver: r8169 v: kernel port: e000 bus-ID: 02:00.0
IF: enp2s0 state: down mac: <filter>
Bluetooth:
Device-1: Intel Bluetooth wireless interface driver: btusb v: 0.8 type: USB
bus-ID: 1-8:5
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 4.2
lmp-v: 8
Drives:
Local Storage: total: 1.82 TiB used: 906 GiB (48.6%)
ID-1: /dev/sda vendor: Samsung model: HN-M101MBB size: 931.51 GiB
ID-2: /dev/sdb vendor: Toshiba model: MQ04ABF100 size: 931.51 GiB
type: USB
Partition:
ID-1: / size: 929.93 GiB used: 249.43 GiB (26.8%) fs: btrfs dev: /dev/sda3
ID-2: /boot size: 973.4 MiB used: 246.5 MiB (25.3%) fs: ext4
dev: /dev/sda2
ID-3: /boot/efi size: 598.8 MiB used: 17.4 MiB (2.9%) fs: vfat
dev: /dev/sda1
ID-4: /home size: 929.93 GiB used: 249.43 GiB (26.8%) fs: btrfs
dev: /dev/sda3
Swap:
ID-1: swap-1 type: zram size: 7.5 GiB used: 0 KiB (0.0%) dev: /dev/zram0
Sensors:
System Temperatures: cpu: 46.0 C pch: 46.0 C mobo: 45.0 C
Fan Speeds (rpm): cpu: 0
Info:
Processes: 289 Uptime: 50m Memory: total: 8 GiB available: 7.5 GiB
used: 2.27 GiB (30.3%) Init: systemd target: graphical (5) Compilers:
gcc: 13.2.1 Packages: 19 note: see --rpm Shell: Bash v: 5.2.21 inxi: 3.3.31
 
dos2unix said:
How much RAM do you have?

Next time this happens, after the computer reboots, can you give the output of

dmesg | tail -n 50
Click to expand...
[ 52.073213] wlp1s0: authenticate with 98:77:e7:0c:77:16
[ 52.073642] pcieport 0000:00:1c.0: AER: Corrected error received: 0000:00:1c.0
[ 52.073654] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 52.073658] pcieport 0000:00:1c.0: device [8086:9d14] error status/mask=00000001/00002000
[ 52.073663] pcieport 0000:00:1c.0: [ 0] RxErr (First)
[ 52.079524] wlp1s0: send auth to 98:77:e7:0c:77:16 (try 1/3)
[ 52.081137] wlp1s0: authenticated
[ 52.081332] wlp1s0: associate with 98:77:e7:0c:77:16 (try 1/3)
[ 52.082454] wlp1s0: RX AssocResp from 98:77:e7:0c:77:16 (capab=0x11 status=0 aid=2)
[ 52.085206] wlp1s0: associated
[ 52.102382] wlp1s0: Limiting TX power to 30 (30 - 0) dBm as advertised by 98:77:e7:0c:77:16
[ 79.083331] gnome-shell[1226]: memfd_create() called without MFD_EXEC or MFD_NOEXEC_SEAL set
[ 82.628862] pcieport 0000:00:1c.0: AER: Corrected error received: 0000:00:1c.0
[ 82.628874] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 82.628877] pcieport 0000:00:1c.0: device [8086:9d14] error status/mask=00000001/00002000
[ 82.628880] pcieport 0000:00:1c.0: [ 0] RxErr (First)
[ 87.824031] rfkill: input handler disabled
[ 90.204912] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
[ 93.080222] Bluetooth: RFCOMM TTY layer initialized
[ 93.080232] Bluetooth: RFCOMM socket layer initialized
[ 93.080244] Bluetooth: RFCOMM ver 1.11
[ 103.437901] systemd-journald[588]: /var/log/journal/f38d03abacdd4914bce6f780bcf29c6a/user-1000.journal: Journal file uses a different sequence number ID, rotating.
[ 103.902951] rfkill: input handler enabled
[ 107.538214] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
[ 108.130988] rfkill: input handler disabled
[ 118.143876] pcieport 0000:00:1c.0: AER: Corrected error received: 0000:00:1c.0
[ 118.143891] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 118.143895] pcieport 0000:00:1c.0: device [8086:9d14] error status/mask=00000001/00002000
[ 118.143900] pcieport 0000:00:1c.0: [ 0] RxErr (First)
[ 121.697178] warning: `kdeconnectd' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211
[ 149.553979] pcieport 0000:00:1c.0: AER: Corrected error received: 0000:00:1c.0
[ 149.553992] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 149.553995] pcieport 0000:00:1c.0: device [8086:9d14] error status/mask=00000001/00002000
[ 149.553998] pcieport 0000:00:1c.0: [ 0] RxErr (First)
[ 152.302672] pcieport 0000:00:1c.0: AER: Corrected error received: 0000:00:1c.0
[ 152.302684] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 152.302687] pcieport 0000:00:1c.0: device [8086:9d14] error status/mask=00000001/00002000
[ 152.302690] pcieport 0000:00:1c.0: [ 0] RxErr (First)
[ 187.309176] pcieport 0000:00:1c.0: AER: Multiple Corrected error received: 0000:00:1c.0
[ 187.309340] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 187.309345] pcieport 0000:00:1c.0: device [8086:9d14] error status/mask=00000001/00002000
[ 187.309349] pcieport 0000:00:1c.0: [ 0] RxErr (First)
[ 195.964833] pcieport 0000:00:1c.0: AER: Corrected error received: 0000:00:1c.0
[ 195.964845] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 195.964848] pcieport 0000:00:1c.0: device [8086:9d14] error status/mask=00000001/00002000
[ 195.964851] pcieport 0000:00:1c.0: [ 0] RxErr (First)
[ 214.808239] pcieport 0000:00:1c.0: AER: Corrected error received: 0000:00:1c.0
[ 214.808251] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 214.808254] pcieport 0000:00:1c.0: device [8086:9d14] error status/mask=00000001/00002000
[ 214.808257] pcieport 0000:00:1c.0: [ 0] RxErr (First)
 
With just the 8 GB, Try a bios purge, disconnect the power and anything plugged in, then [whilst on] press and hold the power button down for 60 seconds, release, and switch on [this can often clear niggling faults]
 
Brickwizard said:
With just the 8 GB, Try a bios purge, disconnect the power and anything plugged in, then [whilst on] press and hold the power button down for 60 seconds, release, and switch on [this can often clear niggling faults]
Click to expand...
I will try.
 
whilst on just press and hold down the power button it should turn off in about 10 seconds and continue to hold it down
 
Right what you have just done is purged the capacitors in the BIOS circuit, forcing the bios to re-set itself, after you changed the ram configuration, it may help cure your problems, This is a trick many PC engineers use, but please dont do it too often
 
You must log in or register to reply here.

Staff online

Members online

Total: 808 (members: 8, guests: 800)

Latest posts

Top