Bug 227615 - Release 10.3-p29 i386 unstable on new servers
Summary: Release 10.3-p29 i386 unstable on new servers
Status: Closed Feedback Timeout
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 10.3-RELEASE
Hardware: i386 Any
: --- Affects Some People
Assignee: freebsd-bugs (Nobody)
Depends on:
Reported: 2018-04-18 15:49 UTC by rich
Modified: 2020-07-21 05:54 UTC (History)
1 user (show)

See Also:

rc.conf file from server (689 bytes, text/plain)
2018-04-23 13:25 UTC, rich
no flags Details
dmesg for server (6.56 KB, text/plain)
2018-04-23 13:26 UTC, rich
no flags Details
sysctl -a from server (82.70 KB, text/plain)
2018-04-23 13:26 UTC, rich
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description rich 2018-04-18 15:49:03 UTC
New servers with Xeon E3-1225 V5 processors cause random reboots under loads
Release 10-3-p29 i386
No crash or errors
Servers include Dell PowerEdge T30 2 new & HP Proliant ML10 Gen9
Comment 1 Eugene Grosbein freebsd_committer 2018-04-22 09:37:54 UTC
It is nearly impossible to help you without any details given.

What is the load your servers process? Do they perform some heavy networking? Do you use GENERIC kernel or not? Do you use IPv6? IPSEC? NETGRAPH? Is ZFS involved?

Do not be afraid to supply as many information as you can.
Comment 2 rich 2018-04-23 13:15:43 UTC
(In reply to Eugene Grosbein from comment #1)
Using GENERIC i386 10.3-P29 kernel.

In Production fails with 40-50 logins  maybe 10 active in 2-4 hours

In Testing running tar to create 10 tarball files of 7-9 gb taking 1/2 hour
repeats every hour,   Fails in 1-3 days.
Comment 3 rich 2018-04-23 13:25:18 UTC
Created attachment 192749 [details]
rc.conf file from server
Comment 4 rich 2018-04-23 13:26:13 UTC
Created attachment 192750 [details]
dmesg for server
Comment 5 rich 2018-04-23 13:26:54 UTC
Created attachment 192751 [details]
sysctl -a from server
Comment 6 Eugene Grosbein freebsd_committer 2018-04-23 13:30:08 UTC
FreeBSD 10.3 official support ends April 30, 2018: https://www.freebsd.org/security/security.html#sup

10.4 has been released half a year ago, 11.1 nine months ago. Does this problem reproduce with those releases? If yes, please show exact tar commands that lead reboots.

Have you tested hardware to rule out hardware problems? Start with memory testing.
Comment 7 Eugene Grosbein freebsd_committer 2018-04-23 13:37:14 UTC
Also, for dumpdev in /etc/rc.conf please use exact swap partition name like dumpdev="/dev/ada0p2" or "/dev/ada0s1b" instead of "AUTO".
Comment 8 Eugene Grosbein freebsd_committer 2020-07-21 05:54:27 UTC
Feeback timeout over 2 years. Since then, FreeBSD 10.3 went EoL.