Proxmox Crash Server

D

derbe

New Member
Jul 30, 2017
10
0
1
44
Hi, there I'm running the beta proxmox cause I'm using ryzen CPU 1700.

I found out that this server is crashing like every 3-4 weeks once, is there anything I can do (look into logs etc.) to find out where the problem is ? I'm really new to proxmox dont juge me if there is any "easy" way to find this out. The server do not respone any more after crash.

Thanks!
 
Hi,
I would enable coredump.
 
Install systemd-coredump
 
Now it looks like this:

Code: 
root@ryzen:~# apt-get install systemd-coredump
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
  systemd-coredump
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 109 kB of archives.
After this operation, 210 kB of additional disk space will be used.
Get:1 http://ftp.de.debian.org/debian stretch/main amd64 systemd-coredump amd64                                   232-25+deb9u1 [109 kB]
Fetched 109 kB in 0s (606 kB/s)
Selecting previously unselected package systemd-coredump.
(Reading database ... 39782 files and directories currently installed.)
Preparing to unpack .../systemd-coredump_232-25+deb9u1_amd64.deb ...
Unpacking systemd-coredump (232-25+deb9u1) ...
Setting up systemd-coredump (232-25+deb9u1) ...
Processing triggers for man-db (2.7.6.1-2) ...

Is that okay so far?
 
Yes so far if it works you will see after the crash.

You have to make the journal persistence.

/etc/systemd/journald.conf

Storage=persistent

Than restart the journald
Code: 
systemctl restart systemd-journald
 
you can see it in the journal
Code: 
journalctl 
cordumpclt --list
 
Hi now it crashed again, I have here the log hope someone can help me :)

I came back from work and my wife told me that it was not reachable as you can see between the reboot is a big gap, I was not able to reach ther server via SSH, so I did a reboot an everythings was working again.

If full log is needed I can upload a file, cause I'm not able to post in full lenght.


Thanks!

Code: 
Sep 06 13:09:28 ryzen smartd[1020]: Device: /dev/sdb [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 60 to 59
Sep 06 13:09:28 ryzen smartd[1020]: Device: /dev/sdc [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 136 to 130
Sep 06 13:10:00 ryzen systemd[1]: Starting Proxmox VE replication runner...
Sep 06 13:10:00 ryzen systemd[1]: Started Proxmox VE replication runner.
Sep 06 13:11:00 ryzen systemd[1]: Starting Proxmox VE replication runner...
Sep 06 13:11:00 ryzen systemd[1]: Started Proxmox VE replication runner.
Sep 06 13:12:00 ryzen systemd[1]: Starting Proxmox VE replication runner...
Sep 06 13:12:00 ryzen systemd[1]: Started Proxmox VE replication runner.
Sep 06 13:13:00 ryzen systemd[1]: Starting Proxmox VE replication runner...
Sep 06 13:13:00 ryzen systemd[1]: Started Proxmox VE replication runner.
Sep 06 13:14:00 ryzen systemd[1]: Starting Proxmox VE replication runner...
Sep 06 13:14:00 ryzen systemd[1]: Started Proxmox VE replication runner.
Sep 06 13:15:00 ryzen systemd[1]: Starting Proxmox VE replication runner...
Sep 06 13:15:00 ryzen systemd[1]: Started Proxmox VE replication runner.
Sep 06 13:16:00 ryzen systemd[1]: Starting Proxmox VE replication runner...
Sep 06 13:16:00 ryzen systemd[1]: Started Proxmox VE replication runner.
Sep 06 13:17:00 ryzen systemd[1]: Starting Proxmox VE replication runner...
Sep 06 13:17:00 ryzen systemd[1]: Started Proxmox VE replication runner.
Sep 06 13:17:01 ryzen CRON[5911]: pam_unix(cron:session): session opened for user root by (uid=0)
Sep 06 13:17:01 ryzen CRON[5912]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Sep 06 13:17:01 ryzen CRON[5911]: pam_unix(cron:session): session closed for user root
Sep 06 13:18:00 ryzen systemd[1]: Starting Proxmox VE replication runner...
Sep 06 13:18:00 ryzen systemd[1]: Started Proxmox VE replication runner.
Sep 06 13:19:00 ryzen systemd[1]: Starting Proxmox VE replication runner...
Sep 06 13:19:00 ryzen systemd[1]: Started Proxmox VE replication runner.
Sep 06 13:20:00 ryzen systemd[1]: Starting Proxmox VE replication runner...
Sep 06 13:20:00 ryzen systemd[1]: Started Proxmox VE replication runner.
Sep 06 13:21:00 ryzen systemd[1]: Starting Proxmox VE replication runner...
Sep 06 13:21:00 ryzen systemd[1]: Started Proxmox VE replication runner.
Sep 06 13:22:00 ryzen systemd[1]: Starting Proxmox VE replication runner...
Sep 06 13:22:00 ryzen systemd[1]: Started Proxmox VE replication runner.
Sep 06 13:23:00 ryzen systemd[1]: Starting Proxmox VE replication runner...
Sep 06 13:23:00 ryzen systemd[1]: Started Proxmox VE replication runner.
Sep 06 13:24:00 ryzen systemd[1]: Starting Proxmox VE replication runner...
Sep 06 13:24:00 ryzen systemd[1]: Started Proxmox VE replication runner.
Sep 06 13:25:00 ryzen systemd[1]: Starting Proxmox VE replication runner...
Sep 06 13:25:00 ryzen systemd[1]: Started Proxmox VE replication runner.
Sep 06 13:26:00 ryzen systemd[1]: Starting Proxmox VE replication runner...
Sep 06 13:26:00 ryzen systemd[1]: Started Proxmox VE replication runner.
Sep 06 13:27:00 ryzen systemd[1]: Starting Proxmox VE replication runner...
Sep 06 13:27:00 ryzen systemd[1]: Started Proxmox VE replication runner.
Sep 06 13:28:00 ryzen systemd[1]: Starting Proxmox VE replication runner...
Sep 06 13:28:00 ryzen systemd[1]: Started Proxmox VE replication runner.
Sep 06 13:29:00 ryzen systemd[1]: Starting Proxmox VE replication runner...
Sep 06 13:29:00 ryzen systemd[1]: Started Proxmox VE replication runner.
Sep 06 13:30:00 ryzen systemd[1]: Starting Proxmox VE replication runner...
Sep 06 13:30:00 ryzen systemd[1]: Started Proxmox VE replication runner.
Sep 06 13:31:00 ryzen systemd[1]: Starting Proxmox VE replication runner...
Sep 06 13:31:00 ryzen systemd[1]: Started Proxmox VE replication runner.
Sep 06 13:32:00 ryzen systemd[1]: Starting Proxmox VE replication runner...
Sep 06 13:32:00 ryzen systemd[1]: Started Proxmox VE replication runner.
Sep 06 13:33:00 ryzen systemd[1]: Starting Proxmox VE replication runner...
Sep 06 13:33:00 ryzen systemd[1]: Started Proxmox VE replication runner.
Sep 06 13:34:00 ryzen systemd[1]: Starting Proxmox VE replication runner...
Sep 06 13:34:00 ryzen systemd[1]: Started Proxmox VE replication runner.
Sep 06 13:35:00 ryzen systemd[1]: Starting Proxmox VE replication runner...
Sep 06 13:35:00 ryzen systemd[1]: Started Proxmox VE replication runner.
Sep 06 13:36:00 ryzen systemd[1]: Starting Proxmox VE replication runner...
Sep 06 13:36:00 ryzen systemd[1]: Started Proxmox VE replication runner.
Sep 06 13:37:00 ryzen systemd[1]: Starting Proxmox VE replication runner...
Sep 06 13:37:00 ryzen systemd[1]: Started Proxmox VE replication runner.
Sep 06 13:38:00 ryzen systemd[1]: Starting Proxmox VE replication runner...
Sep 06 13:38:00 ryzen systemd[1]: Started Proxmox VE replication runner.
Sep 06 13:39:00 ryzen systemd[1]: Starting Proxmox VE replication runner...
Sep 06 13:39:00 ryzen systemd[1]: Started Proxmox VE replication runner.
Sep 06 13:39:25 ryzen rrdcached[1311]: flushing old values
Sep 06 13:39:25 ryzen rrdcached[1311]: rotating journals
Sep 06 13:39:25 ryzen rrdcached[1311]: started new journal /var/lib/rrdcached/journal/rrd.journal.1504697965.941928
Sep 06 13:39:25 ryzen rrdcached[1311]: removing old journal /var/lib/rrdcached/journal/rrd.journal.1504690765.942234
Sep 06 13:39:27 ryzen smartd[1020]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 139 to 136
Sep 06 13:39:28 ryzen smartd[1020]: Device: /dev/sdb [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 59 to 60
Sep 06 13:39:28 ryzen smartd[1020]: Device: /dev/sdc [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 130 to 127
Sep 06 13:40:00 ryzen systemd[1]: Starting Proxmox VE replication runner...
Sep 06 13:40:00 ryzen systemd[1]: Started Proxmox VE replication runner.
Sep 06 13:41:00 ryzen systemd[1]: Starting Proxmox VE replication runner...
Sep 06 13:41:00 ryzen systemd[1]: Started Proxmox VE replication runner.
Sep 06 13:42:00 ryzen systemd[1]: Starting Proxmox VE replication runner...
Sep 06 13:42:00 ryzen systemd[1]: Started Proxmox VE replication runner.
Sep 06 13:43:00 ryzen systemd[1]: Starting Proxmox VE replication runner...
Sep 06 13:43:00 ryzen systemd[1]: Started Proxmox VE replication runner.
Sep 06 13:44:00 ryzen systemd[1]: Starting Proxmox VE replication runner...
Sep 06 13:44:00 ryzen systemd[1]: Started Proxmox VE replication runner.
Sep 06 13:45:00 ryzen systemd[1]: Starting Proxmox VE replication runner...
Sep 06 13:45:00 ryzen systemd[1]: Started Proxmox VE replication runner.
Sep 06 13:46:00 ryzen systemd[1]: Starting Proxmox VE replication runner...
Sep 06 13:46:00 ryzen systemd[1]: Started Proxmox VE replication runner.
Sep 06 13:47:00 ryzen systemd[1]: Starting Proxmox VE replication runner...
Sep 06 13:47:00 ryzen systemd[1]: Started Proxmox VE replication runner.
Sep 06 13:48:00 ryzen systemd[1]: Starting Proxmox VE replication runner...
Sep 06 13:48:00 ryzen systemd[1]: Started Proxmox VE replication runner.
Sep 06 13:49:00 ryzen systemd[1]: Starting Proxmox VE replication runner...
Sep 06 13:49:00 ryzen systemd[1]: Started Proxmox VE replication runner.
Sep 06 13:50:00 ryzen systemd[1]: Starting Proxmox VE replication runner...
Sep 06 13:50:00 ryzen systemd[1]: Started Proxmox VE replication runner.
Sep 06 13:51:00 ryzen systemd[1]: Starting Proxmox VE replication runner...
Sep 06 13:51:00 ryzen systemd[1]: Started Proxmox VE replication runner.
-- Reboot --
Sep 06 16:26:48 ryzen kernel: Linux version 4.10.17-2-pve (root@nora) (gcc version 6.3.0 20170516 (Debian 6.3.0-18) ) #1 SMP PVE 4.10.17-20 (Mon, 14 Aug 2017 11:23:37 +0200) ()
Sep 06 16:26:48 ryzen kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-4.10.17-2-pve root=/dev/mapper/pve-root ro quiet
Sep 06 16:26:48 ryzen kernel: KERNEL supported cpus:
 
Hi happen again, this time in the night and without any action from my side:

Code: 
Sep 10 01:17:01 ryzen CRON[16002]: pam_unix(cron:session): session opened for user root by (uid=0)
Sep 10 01:17:01 ryzen CRON[16003]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Sep 10 01:17:01 ryzen CRON[16002]: pam_unix(cron:session): session closed for user root
Sep 10 01:17:01 ryzen systemd[1]: Started Proxmox VE replication runner.
Sep 10 01:18:00 ryzen systemd[1]: Starting Proxmox VE replication runner...
Sep 10 01:18:01 ryzen systemd[1]: Started Proxmox VE replication runner.
Sep 10 01:19:00 ryzen systemd[1]: Starting Proxmox VE replication runner...
Sep 10 01:19:01 ryzen systemd[1]: Started Proxmox VE replication runner.
Sep 10 01:20:00 ryzen systemd[1]: Starting Proxmox VE replication runner...
Sep 10 01:20:01 ryzen systemd[1]: Started Proxmox VE replication runner.
Sep 10 01:21:00 ryzen systemd[1]: Starting Proxmox VE replication runner...
Sep 10 01:21:01 ryzen systemd[1]: Started Proxmox VE replication runner.
Sep 10 01:22:00 ryzen systemd[1]: Starting Proxmox VE replication runner...
Sep 10 01:22:01 ryzen systemd[1]: Started Proxmox VE replication runner.
Sep 10 01:23:00 ryzen systemd[1]: Starting Proxmox VE replication runner...
Sep 10 01:23:01 ryzen systemd[1]: Started Proxmox VE replication runner.
Sep 10 01:24:00 ryzen systemd[1]: Starting Proxmox VE replication runner...
Sep 10 01:24:01 ryzen systemd[1]: Started Proxmox VE replication runner.
-- Reboot --
Sep 10 01:25:50 ryzen kernel: Linux version 4.10.17-2-pve (root@nora) (gcc version 6.3.0 20170516 (Debian 6.3.0-18) ) #1 SMP PVE 4.10.17-20 (Mon, 14 Aug 2017 11:23:37 +0200) ()
Sep 10 01:25:50 ryzen kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-4.10.17-2-pve root=/dev/mapper/pve-root ro quiet
Sep 10 01:25:50 ryzen kernel: KERNEL supported cpus:
Sep 10 01:25:50 ryzen kernel:   Intel GenuineIntel
Sep 10 01:25:50 ryzen kernel:   AMD AuthenticAMD
Sep 10 01:25:50 ryzen kernel:   Centaur CentaurHauls
 
What coredumps do you see?

Code: 
coredumpctl list
 
Hallo I have the Same Prob Proxmox seems to be a Prob with the Kernal because my System reboots at the same Prob
my System has
smpboot: CPU0: Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz (family: 0x6, model: 0x5e, stepping: 0x3)
Sep 11 12:38:54 pve kernel: Performance Events: PEBS fmt3+, Skylake events, 32-deep LBR, full-width counters, Intel PMU driver.
it seem to that Proxmox has a Prob with that CPU and Coling Control because it dident work to run High by Performance
 
Hi Cyberscitymaste,

please do not hijack this thread I dont think you have the same problem because you have a intel cpu.
There are million reason why a kernel crash.

Please open a new thread.
 
wolfgang said:
What coredumps do you see?

Code: 
coredumpctl list:

TIME                            PID   UID   GID SIG COREFILE EXE
Tue 2017-08-22 22:56:54 CEST   3342     0     0   5 missing  /usr/bin/vma
Tue 2017-08-22 22:59:12 CEST   3656     0     0   5 missing  /usr/bin/vma
Tue 2017-08-22 23:01:11 CEST   3872     0     0   5 missing  /usr/bin/vma
Tue 2017-08-22 23:01:35 CEST   3961     0     0   5 missing  /usr/bin/vma
Tue 2017-08-22 23:05:54 CEST   2037     0     0   5 missing  /usr/bin/vma
Tue 2017-08-22 23:06:57 CEST   2217     0     0   5 missing  /usr/bin/vma
Tue 2017-08-22 23:19:29 CEST   2313     0     0   5 missing  /usr/bin/vma
Tue 2017-08-22 23:19:55 CEST   2416     0     0   5 missing  /usr/bin/vma
Tue 2017-08-22 23:21:54 CEST   2709     0     0   5 missing  /usr/bin/vma
Tue 2017-08-22 23:22:21 CEST   2805     0     0   5 missing  /usr/bin/vma
Tue 2017-08-22 23:23:55 CEST   3058     0     0   5 missing  /usr/bin/vma
Tue 2017-08-22 23:24:47 CEST   3187     0     0   5 missing  /usr/bin/vma
Tue 2017-08-22 23:25:01 CEST   3268     0     0   5 missing  /usr/bin/vma
Tue 2017-08-22 23:26:10 CEST   3491     0     0   5 missing  /usr/bin/vma
Click to expand...
 
You coredump shows only vma crashes but the time do not fit to the system crash time.

derbe said:
The server do not respone any more after crash.
Click to expand...
Can you exact describe what this means?
Do you get a error message or is the input just freezing?
 
wolfgang said:
You coredump shows only vma crashes but the time do not fit to the system crash time.


Can you exact describe what this means?
Do you get a error message or is the input just freezing?
Click to expand...

Yes, that means that the webinterface is not reachable, you can't connect to the Server via SSH and there nothing shown on Display. The only way to get it working again is to reboot.
 
Its running now, how long do i need to wait?

Code: 
root@ryzen:~# ./test.sh 8 2
Install required packages
Reading package lists... Done
Building dependency tree
Reading state information... Done
build-essential is already the newest version (12.3).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Create compressed ramdisk
64G
Download GCC sources
--2017-09-12 18:42:11--  ftp://ftp.fu-berlin.de/unix/languages/gcc/releases/gcc-7.1.0/gcc-7.1.0.tar.bz2
           => 'gcc-7.1.0.tar.bz2'
Resolving ftp.fu-berlin.de (ftp.fu-berlin.de)... 130.133.3.130
Connecting to ftp.fu-berlin.de (ftp.fu-berlin.de)|130.133.3.130|:21... connected.
Logging in as anonymous ... Logged in!
==> SYST ... done.    ==> PWD ... done.
==> TYPE I ... done.  ==> CWD (1) /unix/languages/gcc/releases/gcc-7.1.0 ... done.
==> SIZE gcc-7.1.0.tar.bz2 ... 84303533
==> PASV ... done.    ==> RETR gcc-7.1.0.tar.bz2 ... done.
Length: 84303533 (80M) (unauthoritative)

gcc-7.1.0.tar.bz2                100%[==========================================================>]  80.40M  25.6MB/s    in 3.2s

2017-09-12 18:42:14 (25.0 MB/s) - 'gcc-7.1.0.tar.bz2' saved [84303533]

Extract GCC sources
Download prerequisites
2017-09-12 18:42:36 URL: ftp://gcc.gnu.org/pub/gcc/infrastructure/gmp-6.1.0.tar.bz2 [2383840] -> "./gmp-6.1.0.tar.bz2" [1]
2017-09-12 18:42:43 URL: ftp://gcc.gnu.org/pub/gcc/infrastructure/mpfr-3.1.4.tar.bz2 [1279284] -> "./mpfr-3.1.4.tar.bz2" [1]
2017-09-12 18:42:48 URL: ftp://gcc.gnu.org/pub/gcc/infrastructure/mpc-1.0.3.tar.gz [669925] -> "./mpc-1.0.3.tar.gz" [1]
2017-09-12 18:42:54 URL: ftp://gcc.gnu.org/pub/gcc/infrastructure/isl-0.16.1.tar.bz2 [1626446] -> "./isl-0.16.1.tar.bz2" [1]
gmp-6.1.0.tar.bz2: OK
mpfr-3.1.4.tar.bz2: OK
mpc-1.0.3.tar.gz: OK
isl-0.16.1.tar.bz2: OK
All prerequisites downloaded successfully.
cat /proc/cpuinfo | grep -i -E "(model name|microcode)"
model name      : AMD Ryzen 7 1700 Eight-Core Processor
microcode       : 0x8001126
model name      : AMD Ryzen 7 1700 Eight-Core Processor
microcode       : 0x8001126
model name      : AMD Ryzen 7 1700 Eight-Core Processor
microcode       : 0x8001126
model name      : AMD Ryzen 7 1700 Eight-Core Processor
microcode       : 0x8001126
model name      : AMD Ryzen 7 1700 Eight-Core Processor
microcode       : 0x8001126
model name      : AMD Ryzen 7 1700 Eight-Core Processor
microcode       : 0x8001126
model name      : AMD Ryzen 7 1700 Eight-Core Processor
microcode       : 0x8001126
model name      : AMD Ryzen 7 1700 Eight-Core Processor
microcode       : 0x8001126
model name      : AMD Ryzen 7 1700 Eight-Core Processor
microcode       : 0x8001126
model name      : AMD Ryzen 7 1700 Eight-Core Processor
microcode       : 0x8001126
model name      : AMD Ryzen 7 1700 Eight-Core Processor
microcode       : 0x8001126
model name      : AMD Ryzen 7 1700 Eight-Core Processor
microcode       : 0x8001126
model name      : AMD Ryzen 7 1700 Eight-Core Processor
microcode       : 0x8001126
model name      : AMD Ryzen 7 1700 Eight-Core Processor
microcode       : 0x8001126
model name      : AMD Ryzen 7 1700 Eight-Core Processor
microcode       : 0x8001126
model name      : AMD Ryzen 7 1700 Eight-Core Processor
microcode       : 0x8001126
 dmidecode -t memory | grep -i -E "(rank|speed|part)" | grep -v -i unknown
        Speed: 2667 MHz
        Speed: 2667 MHz
        Part Number: CMK32GX4M2A2666C16
        Rank: 2
        Configured Clock Speed: 1333 MHz
        Speed: 2667 MHz
        Speed: 2667 MHz
        Part Number: CMK32GX4M2A2666C16
        Rank: 2
        Configured Clock Speed: 1333 MHz
uname -a
Linux ryzen 4.10.17-3-pve #1 SMP PVE 4.10.17-21 (Thu, 31 Aug 2017 14:57:17 +0200) x86_64 GNU/Linux
cat /proc/sys/kernel/randomize_va_space
2
/ /mnt/ramdisk/workdir
/mnt/ramdisk/workdir
Using 8 parallel processes
[loop-0] Tue Sep 12 18:42:55 CEST 2017 start 0
[KERN] -- Logs begin at Sun 2017-07-30 19:15:32 CEST. --
[KERN] Sep 12 18:40:45 ryzen kernel: vmbr0: port 2(tap101i0) entered blocking state
[KERN] Sep 12 18:40:45 ryzen kernel: vmbr0: port 2(tap101i0) entered forwarding state
[KERN] Sep 12 18:40:49 ryzen kernel: device tap102i0 entered promiscuous mode
[KERN] Sep 12 18:40:49 ryzen kernel: vmbr0: port 3(tap102i0) entered blocking state
[KERN] Sep 12 18:40:49 ryzen kernel: vmbr0: port 3(tap102i0) entered disabled state
[KERN] Sep 12 18:40:49 ryzen kernel: vmbr0: port 3(tap102i0) entered blocking state
[KERN] Sep 12 18:40:49 ryzen kernel: vmbr0: port 3(tap102i0) entered forwarding state
[KERN] Sep 12 18:42:10 ryzen kernel: zram: Added device: zram0
[KERN] Sep 12 18:42:10 ryzen kernel: zram0: detected capacity change from 0 to 68719476736
[KERN] Sep 12 18:42:11 ryzen kernel: EXT4-fs (zram0): mounted filesystem with ordered data mode. Opts: discard
[loop-1] Tue Sep 12 18:42:56 CEST 2017 start 0
[loop-2] Tue Sep 12 18:42:57 CEST 2017 start 0
[loop-3] Tue Sep 12 18:42:58 CEST 2017 start 0
[loop-4] Tue Sep 12 18:42:59 CEST 2017 start 0
[loop-5] Tue Sep 12 18:43:00 CEST 2017 start 0
[loop-6] Tue Sep 12 18:43:01 CEST 2017 start 0
[loop-7] Tue Sep 12 18:43:02 CEST 2017 start 0


Update:

Code: 
Using 8 parallel processes
[loop-0] Tue Sep 12 18:42:55 CEST 2017 start 0
[KERN] -- Logs begin at Sun 2017-07-30 19:15:32 CEST. --
[KERN] Sep 12 18:40:45 ryzen kernel: vmbr0: port 2(tap101i0) entered blocking state
[KERN] Sep 12 18:40:45 ryzen kernel: vmbr0: port 2(tap101i0) entered forwarding state
[KERN] Sep 12 18:40:49 ryzen kernel: device tap102i0 entered promiscuous mode
[KERN] Sep 12 18:40:49 ryzen kernel: vmbr0: port 3(tap102i0) entered blocking state
[KERN] Sep 12 18:40:49 ryzen kernel: vmbr0: port 3(tap102i0) entered disabled state
[KERN] Sep 12 18:40:49 ryzen kernel: vmbr0: port 3(tap102i0) entered blocking state
[KERN] Sep 12 18:40:49 ryzen kernel: vmbr0: port 3(tap102i0) entered forwarding state
[KERN] Sep 12 18:42:10 ryzen kernel: zram: Added device: zram0
[KERN] Sep 12 18:42:10 ryzen kernel: zram0: detected capacity change from 0 to 68719476736
[KERN] Sep 12 18:42:11 ryzen kernel: EXT4-fs (zram0): mounted filesystem with ordered data mode. Opts: discard
[loop-1] Tue Sep 12 18:42:56 CEST 2017 start 0
[loop-2] Tue Sep 12 18:42:57 CEST 2017 start 0
[loop-3] Tue Sep 12 18:42:58 CEST 2017 start 0
[loop-4] Tue Sep 12 18:42:59 CEST 2017 start 0
[loop-5] Tue Sep 12 18:43:00 CEST 2017 start 0
[loop-6] Tue Sep 12 18:43:01 CEST 2017 start 0
[loop-7] Tue Sep 12 18:43:02 CEST 2017 start 0
[KERN] Sep 12 19:08:09 ryzen kernel: bash[23979]: segfault at 4f ip 0000000000435d7e sp 00007fffe18129d0 error 6 in bash[400000+100000]
[loop-2] Tue Sep 12 19:10:54 CEST 2017 build failed
[loop-2] TIME TO FAIL: 1679 s
[KERN] Sep 12 20:15:40 ryzen kernel: bash[20915]: segfault at 7f6bcaa15828 ip 00007f6bca731370 sp 00007ffd96358e08 error 4 in libc-2.24.so[7f6bca608000+195000]
[loop-3] Tue Sep 12 20:15:42 CEST 2017 build failed
[loop-3] TIME TO FAIL: 5567 s
[loop-5] Tue Sep 12 20:37:13 CEST 2017 start 1
[loop-6] Tue Sep 12 20:37:15 CEST 2017 start 1
[KERN] Sep 12 20:38:02 ryzen kernel: bash[24343]: segfault at 7fb205d681c0 ip 00007fb205a83d60 sp 00007ffc3d334b18 error 4 in libc-2.24.so[7fb205958000+195000]
[loop-6] Tue Sep 12 20:38:07 CEST 2017 build failed
[loop-6] TIME TO FAIL: 6912 s
[loop-0] Tue Sep 12 20:38:52 CEST 2017 start 1
[loop-4] Tue Sep 12 20:38:54 CEST 2017 start 1
[loop-1] Tue Sep 12 20:38:58 CEST 2017 start 1
[loop-7] Tue Sep 12 20:39:23 CEST 2017 start 1
Code: 
Using 8 parallel processes
[loop-0] Tue Sep 12 18:42:55 CEST 2017 start 0
[KERN] -- Logs begin at Sun 2017-07-30 19:15:32 CEST. --
[KERN] Sep 12 18:40:45 ryzen kernel: vmbr0: port 2(tap101i0) entered blocking state
[KERN] Sep 12 18:40:45 ryzen kernel: vmbr0: port 2(tap101i0) entered forwarding state
[KERN] Sep 12 18:40:49 ryzen kernel: device tap102i0 entered promiscuous mode
[KERN] Sep 12 18:40:49 ryzen kernel: vmbr0: port 3(tap102i0) entered blocking state
[KERN] Sep 12 18:40:49 ryzen kernel: vmbr0: port 3(tap102i0) entered disabled state
[KERN] Sep 12 18:40:49 ryzen kernel: vmbr0: port 3(tap102i0) entered blocking state
[KERN] Sep 12 18:40:49 ryzen kernel: vmbr0: port 3(tap102i0) entered forwarding state
[KERN] Sep 12 18:42:10 ryzen kernel: zram: Added device: zram0
[KERN] Sep 12 18:42:10 ryzen kernel: zram0: detected capacity change from 0 to 68719476736
[KERN] Sep 12 18:42:11 ryzen kernel: EXT4-fs (zram0): mounted filesystem with ordered data mode. Opts: discard
[loop-1] Tue Sep 12 18:42:56 CEST 2017 start 0
[loop-2] Tue Sep 12 18:42:57 CEST 2017 start 0
[loop-3] Tue Sep 12 18:42:58 CEST 2017 start 0
[loop-4] Tue Sep 12 18:42:59 CEST 2017 start 0
[loop-5] Tue Sep 12 18:43:00 CEST 2017 start 0
[loop-6] Tue Sep 12 18:43:01 CEST 2017 start 0
[loop-7] Tue Sep 12 18:43:02 CEST 2017 start 0
[KERN] Sep 12 19:08:09 ryzen kernel: bash[23979]: segfault at 4f ip 0000000000435d7e sp 00007fffe18129d0 error 6 in bash[400000+100000]
[loop-2] Tue Sep 12 19:10:54 CEST 2017 build failed
[loop-2] TIME TO FAIL: 1679 s
[KERN] Sep 12 20:15:40 ryzen kernel: bash[20915]: segfault at 7f6bcaa15828 ip 00007f6bca731370 sp 00007ffd96358e08 error 4 in libc-2.24.so[7f6bca608000+195000]
[loop-3] Tue Sep 12 20:15:42 CEST 2017 build failed
[loop-3] TIME TO FAIL: 5567 s
[loop-5] Tue Sep 12 20:37:13 CEST 2017 start 1
[loop-6] Tue Sep 12 20:37:15 CEST 2017 start 1
[KERN] Sep 12 20:38:02 ryzen kernel: bash[24343]: segfault at 7fb205d681c0 ip 00007fb205a83d60 sp 00007ffc3d334b18 error 4 in libc-2.24.so[7fb205958000+195000]
[loop-6] Tue Sep 12 20:38:07 CEST 2017 build failed
[loop-6] TIME TO FAIL: 6912 s
[loop-0] Tue Sep 12 20:38:52 CEST 2017 start 1
[loop-4] Tue Sep 12 20:38:54 CEST 2017 start 1
[loop-1] Tue Sep 12 20:38:58 CEST 2017 start 1
[loop-7] Tue Sep 12 20:39:23 CEST 2017 start 1



Logfile:

http://www.wanitzek.com/build.log


Do I need to repalce my ryzen? :( not sure but looks like?
 
Last edited:
derbe said:
Do I need to repalce my ryzen? :( not sure but looks like?
Click to expand...
Yes I think so too.

You can try to disable SMT, OPCache Control and wait may by there will be an firmware update.
But I think you need to replace it.
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back