You are not logged in.

#1 2019-01-17 01:00:40

Bonhomme
Member
Registered: 2018-12-15
Posts: 9

System crash while using Samba

Hello,

I recently installed Arch on an old PC dedicated for mostly using Samba and Deluge.

I am having trouble with Samba. Everytime I transfert files from that PC the transfert stops because the PC crash. All I can do is reset the physical machine. The crash is very random, I transfer 5 files in one action. They are around 2Gb each. The PC with the samba server can crash while the 1st file or the 26th file (because I do it multiple time).

I believe the hardware is not at fault. I made some memory tests and everything seems fine. I had, and still have, Windows 7 on an other hard drive. Windows 7 seems to never crash when I transfert files as a host.

Here's my entire lspci -k

00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] RS780 Host Bridge
        Subsystem: ASUSTeK Computer Inc. M3A78-EH Motherboard
00:01.0 PCI bridge: ASUSTeK Computer Inc. AMD RS780/RS880 PCI to PCI bridge (int gfx)
00:05.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780/RS880 PCI to PCI bridge (PCIE port 1)
        Kernel driver in use: pcieport
00:06.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780 PCI to PCI bridge (PCIE port 2)
        Kernel driver in use: pcieport
00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 SATA Controller [IDE mode]
        Subsystem: ASUSTeK Computer Inc. M3A78-EH Motherboard
        Kernel driver in use: ahci
        Kernel modules: ahci
00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
        Subsystem: ASUSTeK Computer Inc. M3A78-EH Motherboard
        Kernel driver in use: ohci-pci
        Kernel modules: ohci_pci
00:12.1 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0 USB OHCI1 Controller
        Subsystem: ASUSTeK Computer Inc. M3A78-EH Motherboard
        Kernel driver in use: ohci-pci
        Kernel modules: ohci_pci
00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller
        Subsystem: ASUSTeK Computer Inc. M3A78-EH Motherboard
        Kernel driver in use: ehci-pci
        Kernel modules: ehci_pci
00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
        Subsystem: ASUSTeK Computer Inc. M3A78-EH Motherboard
        Kernel driver in use: ohci-pci
        Kernel modules: ohci_pci
00:13.1 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0 USB OHCI1 Controller
        Subsystem: ASUSTeK Computer Inc. M3A78-EH Motherboard
        Kernel driver in use: ohci-pci
        Kernel modules: ohci_pci
00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller
        Subsystem: ASUSTeK Computer Inc. M3A78-EH Motherboard
        Kernel driver in use: ehci-pci
        Kernel modules: ehci_pci
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller (rev 3a)
        Subsystem: ASUSTeK Computer Inc. M3A78-EH Motherboard
        Kernel modules: i2c_piix4, sp5100_tco
00:14.1 IDE interface: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 IDE Controller
        Subsystem: ASUSTeK Computer Inc. M3A78-EH Motherboard
        Kernel driver in use: pata_atiixp
        Kernel modules: pata_atiixp, pata_acpi, ata_generic
00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA)
        Subsystem: ASUSTeK Computer Inc. SBx00 Azalia (Intel HDA)
        Kernel driver in use: snd_hda_intel
        Kernel modules: snd_hda_intel
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 LPC host controller
        Subsystem: ASUSTeK Computer Inc. M3A78-EH Motherboard
00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 PCI to PCI Bridge
00:14.5 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI2 Controller
        Subsystem: ASUSTeK Computer Inc. M3A78-EH Motherboard
        Kernel driver in use: ohci-pci
        Kernel modules: ohci_pci
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
        Kernel driver in use: k8temp
        Kernel modules: k8temp
01:05.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RS780 [Radeon HD 3200]
        Subsystem: ASUSTeK Computer Inc. RS780 [Radeon HD 3200]
        Kernel driver in use: radeon
        Kernel modules: radeon
01:05.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] RS780 HDMI Audio [Radeon 3000/3100 / HD 3200/3300]
        Subsystem: ASUSTeK Computer Inc. RS780 HDMI Audio [Radeon 3000/3100 / HD 3200/3300]
        Kernel driver in use: snd_hda_intel
        Kernel modules: snd_hda_intel
02:00.0 FireWire (IEEE 1394): JMicron Technology Corp. IEEE 1394 Host Controller
        Subsystem: ASUSTeK Computer Inc. IEEE 1394 Host Controller
        Kernel driver in use: firewire_ohci
        Kernel modules: firewire_ohci
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 02)
        Subsystem: ASUSTeK Computer Inc. M3A78 Series Motherboard
        Kernel driver in use: r8169
        Kernel modules: r8169

I read about microcode. Installed it and added it in grub.

pacman -Qqe | grep ucode

amd-ucode

sudo cat /boot/grub/grub.cfg | grep ucode

initrd  /boot/amd-ucode.img /boot/initramfs-linux.img
initrd  /boot/amd-ucode.img /boot/initramfs-linux.img

Testing microcode gives me nothing compared to what is recommended here: https://wiki.archlinux.org/index.php/mi … ed_on_boot Would it be normal ?

I found this link on Ubuntu https://askubuntu.com/questions/761706/ … -hH2C0Oxvc that seem to be a similar problem to me, but the first solution seems to use an Intel kernel parameter. I doubt it would work in my case.

Here is a part of my journal

-- Reboot --
Jan 16 18:08:04 bonhomme-server kernel: Spectre V2 : Spectre mitigation: LFENCE not serializing, switching to generic retpoline
Jan 16 18:08:04 bonhomme-server kernel: ata1: softreset failed (device not ready)
Jan 16 18:08:11 bonhomme-server smbd[312]: [2019/01/16 18:08:11.417204,  0] ../lib/util/debug.c:1063(reopen_logs_internal)
Jan 16 18:08:11 bonhomme-server smbd[312]:   Unable to open new log file '/usr/local/samba/var/log.smbd': No such file or directory
Jan 16 18:08:11 bonhomme-server smbd[312]: [2019/01/16 18:08:11.446199,  0] ../lib/util/debug.c:1063(reopen_logs_internal)
Jan 16 18:08:11 bonhomme-server smbd[312]:   Unable to open new log file '/usr/local/samba/var/log.smbd': No such file or directory
Jan 16 18:08:11 bonhomme-server smbd[312]: [2019/01/16 18:08:11.446285,  0] ../lib/util/debug.c:1063(reopen_logs_internal)
Jan 16 18:08:11 bonhomme-server smbd[312]:   Unable to open new log file '/usr/local/samba/var/log.smbd': No such file or directory
Jan 16 18:08:12 bonhomme-server smbd[312]: [2019/01/16 18:08:12.005595,  0] ../lib/util/become_daemon.c:138(daemon_ready)
Jan 16 18:08:12 bonhomme-server smbd[312]:   daemon_ready: STATUS=daemon 'smbd' finished starting up and ready to serve connections
Jan 16 18:08:12 bonhomme-server smbd[325]: [2019/01/16 18:08:12.015090,  0] ../lib/util/debug.c:1063(reopen_logs_internal)
Jan 16 18:08:12 bonhomme-server smbd[325]:   Unable to open new log file '/usr/local/samba/var/log.smbd': No such file or directory
Jan 16 18:21:58 bonhomme-server smbd[423]: [2019/01/16 18:21:58.504946,  0] ../lib/util/debug.c:1063(reopen_logs_internal)
Jan 16 18:21:58 bonhomme-server smbd[423]:   Unable to open new log file '/usr/local/samba/var/log.192.168.1.126': No such file or directory
Jan 16 18:21:58 bonhomme-server smbd[423]: [2019/01/16 18:21:58.529268,  0] ../lib/util/debug.c:1063(reopen_logs_internal)
Jan 16 18:21:58 bonhomme-server smbd[423]:   Unable to open new log file '/usr/local/samba/var/log.192.168.1.126': No such file or directory
Jan 16 18:21:58 bonhomme-server smbd[423]: [2019/01/16 18:21:58.692328,  0] ../lib/util/debug.c:1063(reopen_logs_internal)
Jan 16 18:21:58 bonhomme-server smbd[423]:   Unable to open new log file '/usr/local/samba/var/log.': No such file or directory
Jan 16 18:24:02 bonhomme-server smbd[426]: [2019/01/16 18:24:02.843250,  0] ../lib/util/debug.c:1063(reopen_logs_internal)
Jan 16 18:24:02 bonhomme-server smbd[426]:   Unable to open new log file '/usr/local/samba/var/log.192.168.1.127': No such file or directory
Jan 16 18:24:02 bonhomme-server smbd[426]: [2019/01/16 18:24:02.892623,  0] ../lib/util/debug.c:1063(reopen_logs_internal)
Jan 16 18:24:02 bonhomme-server smbd[426]:   Unable to open new log file '/usr/local/samba/var/log.192.168.1.127': No such file or directory
Jan 16 18:24:02 bonhomme-server smbd[426]: [2019/01/16 18:24:02.892799,  0] ../lib/util/debug.c:1063(reopen_logs_internal)
Jan 16 18:24:02 bonhomme-server smbd[426]:   Unable to open new log file '/usr/local/samba/var/log.192.168.1.127': No such file or directory
Jan 16 18:24:02 bonhomme-server smbd[426]: [2019/01/16 18:24:02.892929,  0] ../lib/util/debug.c:1063(reopen_logs_internal)
Jan 16 18:24:02 bonhomme-server smbd[426]:   Unable to open new log file '/usr/local/samba/var/log.192.168.1.127': No such file or directory
Jan 16 18:24:02 bonhomme-server smbd[426]: [2019/01/16 18:24:02.900098,  0] ../lib/util/debug.c:1063(reopen_logs_internal)
Jan 16 18:24:02 bonhomme-server smbd[426]:   Unable to open new log file '/usr/local/samba/var/log.192.168.1.127': No such file or directory
Jan 16 18:24:02 bonhomme-server smbd[426]: [2019/01/16 18:24:02.912708,  0] ../lib/util/debug.c:1063(reopen_logs_internal)
Jan 16 18:24:02 bonhomme-server smbd[426]:   Unable to open new log file '/usr/local/samba/var/log.bonhomme-pc-w10': No such file or directory
Jan 16 18:25:14 bonhomme-server smbd[427]: [2019/01/16 18:25:14.589475,  0] ../lib/util/debug.c:1063(reopen_logs_internal)
Jan 16 18:25:14 bonhomme-server smbd[427]:   Unable to open new log file '/usr/local/samba/var/log.192.168.1.126': No such file or directory
Jan 16 18:25:14 bonhomme-server smbd[427]: [2019/01/16 18:25:14.590418,  0] ../lib/util/debug.c:1063(reopen_logs_internal)
Jan 16 18:25:14 bonhomme-server smbd[427]:   Unable to open new log file '/usr/local/samba/var/log.192.168.1.126': No such file or directory
Jan 16 18:25:14 bonhomme-server smbd[427]: [2019/01/16 18:25:14.629232,  0] ../lib/util/debug.c:1063(reopen_logs_internal)
Jan 16 18:25:14 bonhomme-server smbd[427]:   Unable to open new log file '/usr/local/samba/var/log.': No such file or directory
Jan 16 18:29:14 bonhomme-server smbd[427]: [2019/01/16 18:29:14.592733,  0] ../lib/util/debug.c:1063(reopen_logs_internal)
Jan 16 18:29:14 bonhomme-server smbd[427]:   Unable to open new log file '/usr/local/samba/var/log.': No such file or directory
-- Reboot --
Jan 16 18:37:49 bonhomme-server kernel: Spectre V2 : Spectre mitigation: LFENCE not serializing, switching to generic retpoline
Jan 16 18:37:49 bonhomme-server kernel: ata3: softreset failed (device not ready)
Jan 16 18:37:54 bonhomme-server smbd[311]: [2019/01/16 18:37:54.727832,  0] ../lib/util/debug.c:1063(reopen_logs_internal)
Jan 16 18:37:54 bonhomme-server smbd[311]:   Unable to open new log file '/usr/local/samba/var/log.smbd': No such file or directory
Jan 16 18:37:54 bonhomme-server smbd[311]: [2019/01/16 18:37:54.749675,  0] ../lib/util/debug.c:1063(reopen_logs_internal)
Jan 16 18:37:54 bonhomme-server smbd[311]:   Unable to open new log file '/usr/local/samba/var/log.smbd': No such file or directory
Jan 16 18:37:54 bonhomme-server smbd[311]: [2019/01/16 18:37:54.749771,  0] ../lib/util/debug.c:1063(reopen_logs_internal)
Jan 16 18:37:54 bonhomme-server smbd[311]:   Unable to open new log file '/usr/local/samba/var/log.smbd': No such file or directory
Jan 16 18:37:55 bonhomme-server smbd[311]: [2019/01/16 18:37:55.177729,  0] ../lib/util/become_daemon.c:138(daemon_ready)
Jan 16 18:37:55 bonhomme-server smbd[311]:   daemon_ready: STATUS=daemon 'smbd' finished starting up and ready to serve connections
Jan 16 18:37:55 bonhomme-server smbd[324]: [2019/01/16 18:37:55.231317,  0] ../lib/util/debug.c:1063(reopen_logs_internal)
Jan 16 18:37:55 bonhomme-server smbd[324]:   Unable to open new log file '/usr/local/samba/var/log.smbd': No such file or directory
Jan 16 18:38:22 bonhomme-server smbd[418]: [2019/01/16 18:38:22.557563,  0] ../lib/util/debug.c:1063(reopen_logs_internal)
Jan 16 18:38:22 bonhomme-server smbd[418]:   Unable to open new log file '/usr/local/samba/var/log.192.168.1.126': No such file or directory
Jan 16 18:38:22 bonhomme-server smbd[419]: [2019/01/16 18:38:22.560686,  0] ../lib/util/debug.c:1063(reopen_logs_internal)
Jan 16 18:38:22 bonhomme-server smbd[419]:   Unable to open new log file '/usr/local/samba/var/log.192.168.1.126': No such file or directory
Jan 16 18:38:22 bonhomme-server smbd[419]: [2019/01/16 18:38:22.574983,  0] ../lib/util/debug.c:1063(reopen_logs_internal)
Jan 16 18:38:22 bonhomme-server smbd[419]:   Unable to open new log file '/usr/local/samba/var/log.192.168.1.126': No such file or directory
Jan 16 18:38:22 bonhomme-server smbd[419]: [2019/01/16 18:38:22.835330,  0] ../lib/util/debug.c:1063(reopen_logs_internal)
Jan 16 18:38:22 bonhomme-server smbd[419]:   Unable to open new log file '/usr/local/samba/var/log.': No such file or directory

If you have any suggestion on what could help me find the problem would be very appreciated.

Thank you and have a nice day.

Offline

#2 2019-01-17 08:58:03

seth
Member
Registered: 2012-09-03
Posts: 9,873

Re: System crash while using Samba

"part of your journal" won't do. If "All [you] can do is reset the physical machine" this will be a kernel issue, try to monitor "dmesg -w" during the transfers. Ideally avoid any graphical session and especially compositors (ie. monitor this from a linux console)
For a lucky shot, post a complete journal (from boot and covering a freeze, including all kernel messages and everything)

Also https://bbs.archlinux.org/viewtopic.php … 9#p1801619 - though this will usually not result in freezes.

Offline

#3 2019-02-03 22:22:51

Bonhomme
Member
Registered: 2018-12-15
Posts: 9

Re: System crash while using Samba

Sorry for the long reply.

I had not used the computer for a while and sometimes the crash just does not happen.

sudo journalctl --since "60 min ago" | nc termbin.com 9999:
https://termbin.com/3njw

cat dmesg-w.log | nc termbin.com 9999:
https://termbin.com/q83d3

For the dmesg, I ran it from ssh and pasted it in a file after the crash.

I believe it should be enough.

Again, if you would need anything else, just ask.


Thanks again for your time !

Offline

#4 2019-02-03 22:50:23

loqs
Member
Registered: 2014-03-06
Posts: 6,945

Re: System crash while using Samba

Feb 03 11:55:30 bonhomme-server sudo[625]: bonhomme : TTY=pts/0 ; PWD=/home/bonhomme ; USER=root ; COMMAND=/usr/bin/dmesg -w
Feb 03 11:55:30 bonhomme-server sudo[625]: pam_unix(sudo:session): session opened for user root by bonhomme(uid=0)
Feb 03 11:56:05 bonhomme-server smbd[561]: [2019/02/03 11:56:05.276445,  0] ../lib/util/debug.c:1063(reopen_logs_internal)
Feb 03 11:56:05 bonhomme-server smbd[561]:   Unable to open new log file '/usr/local/samba/var/log.': No such file or directory
Feb 03 11:59:05 bonhomme-server smbd[561]: [2019/02/03 11:59:05.277892,  0] ../lib/util/debug.c:1063(reopen_logs_internal)
Feb 03 11:59:05 bonhomme-server smbd[561]:   Unable to open new log file '/usr/local/samba/var/log.': No such file or directory
-- Reboot --
Feb 03 12:06:00 bonhomme-server kernel: Linux version 4.20.3-arch1-1-ARCH (builduser@heftig-25602) (gcc version 8.2.1 20181127 (GCC)) #1 SMP PREEMPT Wed Jan 16 22:38:58 UTC 2019

Unfortunately there is not output from the kernel indicating it has detected any issues before the system is rebooted.

Offline

#5 2019-02-04 08:46:21

seth
Member
Registered: 2012-09-03
Posts: 9,873

Re: System crash while using Samba

Feb 03 11:49:36 bonhomme-server kernel: Console: colour dummy device 80x25
…
Feb 03 11:49:38 bonhomme-server kernel: [drm] Cannot find any crtc or sizes
…
Feb 03 11:49:39 bonhomme-server systemd[1]: Reached target Graphical Interface.

Is this a headless server and do you determine "crash" by "no more network responses"?
There's a suspicious "pattern" in the log, you get an IPv6 address and the interface immediately loses the carrier.

If not, what is the graphical target?

Offline

#6 2019-02-06 03:59:02

Bonhomme
Member
Registered: 2018-12-15
Posts: 9

Re: System crash while using Samba

Yeah, I used the computer as a headless server. Except a power cord and a RJ45 cable, nothing is plugged.

Huh... I know it sounds crazy but you made me realized something. When I start the computer with a VGA monitor directly plugged into the motherboard, the computer seems to never crash. I wanted to be sure if the screen freezes or not when the computer crashes.

When I start without a monitor, the computer crashes after transferring some files. If there is already a usb keyboard, Ctrl+Alt+Del does not reboot the computer. If I plug a monitor after the crash. I cannot see anything. So I assume the computer is "dead" even if the fans and such spin.


Maybe my motherboard is old and defective.

Last edited by Bonhomme (2019-02-06 04:00:58)

Offline

#7 2019-02-06 08:10:01

seth
Member
Registered: 2012-09-03
Posts: 9,873

Re: System crash while using Samba

Odd indeed. What is the graphical.target?
What happens if you pass

systemd.unit=multi-user.target nomodeset radeon.dpm=0 radeon.aspm=0 radeon.runpm=0 radeon.bapm=0

to the kernel?

Offline

#8 2019-02-07 04:39:23

Bonhomme
Member
Registered: 2018-12-15
Posts: 9

Re: System crash while using Samba

By graphical.target, do you mean this config file ?

 $ cat /usr/lib/systemd/system/graphical.target
#  SPDX-License-Identifier: LGPL-2.1+
#
#  This file is part of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it
#  under the terms of the GNU Lesser General Public License as published by
#  the Free Software Foundation; either version 2.1 of the License, or
#  (at your option) any later version.

[Unit]
Description=Graphical Interface
Documentation=man:systemd.special(7)
Requires=multi-user.target
Wants=display-manager.service
Conflicts=rescue.service rescue.target
After=multi-user.target rescue.service rescue.target display-manager.service
AllowIsolate=yes

I added what you suggested me to grub.

 $ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=e0c615cf-d8c0-4cc0-9b27-1a542e5193b9 rw quiet systemd.unit=multi-user.target nomodeset radeon.dpm=0 radeon.aspm=0 radeon.runpm=0 radeon.bapm=0

Unfortunately, it does not seem to fix the crash. It happened again 2, 3 times.

I'll put again my logs just in case:

sudo journalctl --since "180 min ago" | nc termbin.com 9999
https://termbin.com/tkro

cat dmesg2-w.log | nc termbin.com 9999:
https://termbin.com/mtdg

Where did you find the existance of these kernel's parameters by the way (radeon.dpm, radeon.aspm, radeon.runpm, radeon.bapm) ? They are not on the doc over here: https://www.kernel.org/doc/Documentatio … meters.txt .

Offline

#9 2019-02-07 08:44:11

seth
Member
Registered: 2012-09-03
Posts: 9,873

Re: System crash while using Samba

"modinfo radeon"

No, I meant "what actually is your graphical session"? Do you start any DM or startx into a graphical session, what kind of session/desktop environment, as what user…

The crucial bit is whether this is indeed strictlyrelated to the presence of an output (vga monitor) - that seems nuts, but if it was, we'd have to follow that lead and if it's not, you could live-monitor the console messages for some better indication of why the system crashes on transfers.

Other things to check would be to kill the torrent client and check file transfers via NFS or FTP rather than SMB.

Offline

#10 2019-02-16 01:56:08

Bonhomme
Member
Registered: 2018-12-15
Posts: 9

Re: System crash while using Samba

Oh, then I simply use the bash terminal. I did not install any DM, Xorg and such. I only wanted my computer accessible via SSH.

Like I said, this only happens when no monitor at all is plugged. My main monitor (where I test) is HDMI and DVI. Perhaps I could try with those connector to see if it can crash to monitor it from a physical screen plugged...

I tried FTP from Arch to Windows 10. The crash still happens. May be the crash comes from the kernel's network drivers and my hardware insted of samba ?

The deluge's package is installed, but the services are not running. So it does not interfere.

I made extra tests. Debian (with XFCE installed at the installation) and Ubuntu Server does exactly the same thing. So like you said, it kind have no choice to come from the kernel.

I tried again Windows 7. Because I never tried it without a monitor. The crash never happens. I installed Cygwin/Openssh and deluge. It kind of does what I originally tried to do.


If you have other suggestions, I'll be very open to hear them !

Offline

#11 2019-02-16 21:04:08

seth
Member
Registered: 2012-09-03
Posts: 9,873

Re: System crash while using Samba

Some weird powersaving script?
Can you use another interface (eg. a wifi dongle or pci ethernet card)?
Also: https://aur.archlinux.org/packages/r8168-dkms/ (ensure to blacklist r8169)
https://wiki.archlinux.org/index.php/Ke … acklisting

You might have to go for a crash kernel, because there's no way to remotely check the issue and it doesn't occur w/ a local output…
https://wiki.archlinux.org/index.php/Kdump

Offline

Board footer

Powered by FluxBB