Re: GENERIC crash 11.3-PRERELEASE (i386)
Hi Konstantin, BINGO! 110 out of 100 possible points :-) Yes, that fixed the problem: root@blnn719x - ~ 2048 # uname -a FreeBSD blnn719x.ad001.siemens.net 11.3-PRERELEASE FreeBSD 11.3-PRERELEASE #2 r349719M: Thu Jul 11 09:12:21 CEST 2019 r...@blnn719x.ad001.siemens.net:/usr/obj/usr/src/sys/BLNN719X i386 ...and I have no doubt that this will work with the current revision as well. Thank you very much! Best regards - Matthias Am 10.07.2019 um 20:12 schrieb Konstantin Belousov: On Wed, Jul 10, 2019 at 03:02:40PM +0200, Schuendehuette, Matthias (LDA IT PLM) wrote: Sorry, wrong link... :-( See the verbose boot messages here... https://www.dropbox.com/sh/buzxekimo2h2r67/AADpUvLndhm2SHa5t9s9Ckksa?dl=0 ...in file "Boot_verbose.jpg" Can you try the following patch ? Index: sys/x86/x86/cpu_machdep.c === --- sys/x86/x86/cpu_machdep.c (revision 349890) +++ sys/x86/x86/cpu_machdep.c (working copy) @@ -953,7 +953,6 @@ * architectural state except possibly %rflags. Also, it is always * called with interrupts disabled. */ -void (*mds_handler)(void); void mds_handler_void(void); void mds_handler_verw(void); void mds_handler_ivb(void); @@ -962,6 +961,7 @@ void mds_handler_skl_avx(void); void mds_handler_skl_avx512(void); void mds_handler_silvermont(void); +void (*mds_handler)(void) = mds_handler_void; static int sysctl_hw_mds_disable_state_handler(SYSCTL_HANDLER_ARGS) ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: GENERIC crash 11.3-PRERELEASE (i386)
Sorry, wrong link... :-(
See the verbose boot messages here...
https://www.dropbox.com/sh/buzxekimo2h2r67/AADpUvLndhm2SHa5t9s9Ckksa?dl=0
...in file "Boot_verbose.jpg"
Regards - Matthias
Am 10.07.2019 um 14:47 schrieb [ext] Schuendehuette, Matthias (LDA IT PLM):
Hello Konstantin,
the 'svn' output:
*
root@blnn719x - /usr/src
2052 # svn st
? sys/i386/conf/BLNN719X
root@blnn719x - /usr/src
2053 # svn info
Path: .
Working Copy Root Path: /usr/src
URL: https://svn.freebsd.org/base/stable/11
Relative URL: ^/stable/11
Repository Root: https://svn.freebsd.org/base
Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f
Revision: 349719
Node Kind: directory
Schedule: normal
Last Changed Author: delphij
Last Changed Rev: 349718
Last Changed Date: 2019-07-04 09:32:25 +0200 (Thu, 04 Jul 2019)
*
The last lines of the verbose boot messages can be found here:
https://www.dropbox.com/preview/FreeBSD-stable/Boot_verbose.jpg
Thank you very much so far
Matthias
Am 05.07.2019 um 21:11 schrieb Konstantin Belousov:
On Fri, Jul 05, 2019 at 11:12:29AM +, Schuendehuette, Matthias
wrote:
Hello Konstantin,
***
Obviously Outlook has destroyed my last reply - here again:
***
I did what you suggested: deleted the content of /usr/src and 'svn co'
the 11-STABLE sources again.
I investigated the three
source files mentioned below and confirmed the 'svn diff' results:
"hw_mds_recalculate();" has been removed from
sys/amd64/amd64/initcpu.c and
sys/i386/i386/initcpu.c
and:
"static void
hw_mds_recalculate_boot(void *arg __unused)
{
hw_mds_recalculate();
}
SYSINIT(mds_recalc, SI_SUB_SMP, SI_ORDER_ANY,
hw_mds_recalculate_boot, NULL);"
has been inserted into 'sys/x86/x86/cpu_machdep.c'
That's still the case for 'r349719'. Also remains true that a kernel of
'r349719' crashes as described earlier.
Ok, show me
1. svn st and svn info output of the checkout you use
2. While kernel messages with verbose boot enabled, for your machine,
and
the kernel which fails to boot.
With best regards and have a nice weekend
Matthias Schuendehuette
-Ursprüngliche Nachricht-
Von: Konstantin Belousov Gesendet: Mittwoch, 3.
Juli 2019 15:55
An: Schuendehuette, Matthias (LDA IT
PLM)
Cc: 'freebsd-stable@freebsd.org';
Osipov, Michael (LDA IT PLM)
Betreff: Re: GENERIC crash 11.3-PRERELEASE (i386)
On Wed, Jul 03, 2019 at 08:42:21AM +, Schuendehuette, Matthias
wrote:
Hello Konstantin,
I did some research regarding the kernel crash with the following
results>
1) Last working kernel is:
"FreeBSD 11.3-BETA1 (BLNN719X) #8 r348361: Wed Jul 3 09:30:17
CEST 2019"
1a) DDB-Backtrace of the crashing kernel r348362 can be seen on
"Boot_BT.jpg"
in the dropbox directory
"https://www.dropbox.com/sh/buzxekimo2h2r67/AADpUvLndhm2SHa5t9s9Ckksa?dl=0;
2) Source code revision is:
root@blnn719x - /usr/src
2056 # svn info
Path: .
Working Copy Root Path: /usr/src
URL:https://svn.freebsd.org/base/stable/11
Relative URL: ^/stable/11
Repository Root:https://svn.freebsd.org/base
Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f
Revision: 348361
Node Kind: directory
Schedule: normal
Last Changed Author: jkim
Last Changed Rev: 348343
Last Changed Date: 2019-05-29 02:00:52 +0200 (Wed, 29 May 2019)
3) Diff to next revision:
root@blnn719x - /usr/src
2057 # svn diff -r 348362
Index: sys/amd64/amd64/initcpu.c
===
--- sys/amd64/amd64/initcpu.c (revision 348362)
+++ sys/amd64/amd64/initcpu.c (working copy)
@@ -247,6 +247,7 @@
}
hw_ibrs_recalculate();
hw_ssb_recalculate(false);
+ hw_mds_recalculate();
switch (cpu_vendor_id) {
case CPU_VENDOR_AMD:
init_amd();
Index: sys/i386/i386/initcpu.c
===
--- sys/i386/i386/initcpu.c (revision 348362)
+++ sys/i386/i386/initcpu.c (working copy)
@@ -769,6 +769,7 @@
elf32_nxstack = 1;
}
#endif
+ hw_mds_recalculate();
if ((amd_feature & AMDID_RDTSCP) != 0 ||
(cpu_stdext_feature2 & CPUID_STDEXT2_RDPID) != 0)
wrmsr(MSR_TSC_AUX, PCPU_GET(cpuid));
Index: sys/x86/x86/cpu_machdep.c
===
--- sys/x86/x86/cpu_machdep.c (revision 348362)
+++ sys/x86/x86/cpu_machdep.c (working copy)
@@ -1118,14 +1118,6 @@
}
}
-static void
-hw_mds_recalculate_boot(void *arg __unused)
-{
-
- hw_mds_recalculate();
-}
-SYSINIT(mds_recalc, SI_SUB_SMP, SI_ORDER_ANY,
hw_mds_recalculate_boot, NULL);
-
static int
sysctl_mds_disable_handler(SYSCTL_HANDLER_ARGS)
{
Index: .
===
--- . (revision 348362)
+++ . (working copy)
Property changes on: .
_
Re: GENERIC crash 11.3-PRERELEASE (i386)
Hello Konstantin,
the 'svn' output:
*
root@blnn719x - /usr/src
2052 # svn st
? sys/i386/conf/BLNN719X
root@blnn719x - /usr/src
2053 # svn info
Path: .
Working Copy Root Path: /usr/src
URL: https://svn.freebsd.org/base/stable/11
Relative URL: ^/stable/11
Repository Root: https://svn.freebsd.org/base
Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f
Revision: 349719
Node Kind: directory
Schedule: normal
Last Changed Author: delphij
Last Changed Rev: 349718
Last Changed Date: 2019-07-04 09:32:25 +0200 (Thu, 04 Jul 2019)
*
The last lines of the verbose boot messages can be found here:
https://www.dropbox.com/preview/FreeBSD-stable/Boot_verbose.jpg
Thank you very much so far
Matthias
Am 05.07.2019 um 21:11 schrieb Konstantin Belousov:
On Fri, Jul 05, 2019 at 11:12:29AM +, Schuendehuette, Matthias wrote:
Hello Konstantin,
***
Obviously Outlook has destroyed my last reply - here again:
***
I did what you suggested: deleted the content of /usr/src and 'svn co'
the 11-STABLE sources again.
I investigated the three
source files mentioned below and confirmed the 'svn diff' results:
"hw_mds_recalculate();" has been removed from
sys/amd64/amd64/initcpu.c and
sys/i386/i386/initcpu.c
and:
"static void
hw_mds_recalculate_boot(void *arg __unused)
{
hw_mds_recalculate();
}
SYSINIT(mds_recalc, SI_SUB_SMP, SI_ORDER_ANY, hw_mds_recalculate_boot, NULL);"
has been inserted into 'sys/x86/x86/cpu_machdep.c'
That's still the case for 'r349719'. Also remains true that a kernel of
'r349719' crashes as described earlier.
Ok, show me
1. svn st and svn info output of the checkout you use
2. While kernel messages with verbose boot enabled, for your machine, and
the kernel which fails to boot.
With best regards and have a nice weekend
Matthias Schuendehuette
-Ursprüngliche Nachricht-
Von: Konstantin Belousov
Gesendet: Mittwoch, 3. Juli 2019 15:55
An: Schuendehuette, Matthias (LDA IT PLM)
Cc: 'freebsd-stable@freebsd.org'; Osipov, Michael (LDA IT
PLM)
Betreff: Re: GENERIC crash 11.3-PRERELEASE (i386)
On Wed, Jul 03, 2019 at 08:42:21AM +0000, Schuendehuette, Matthias wrote:
Hello Konstantin,
I did some research regarding the kernel crash with the following results>
1) Last working kernel is:
"FreeBSD 11.3-BETA1 (BLNN719X) #8 r348361: Wed Jul 3 09:30:17 CEST
2019"
1a) DDB-Backtrace of the crashing kernel r348362 can be seen on "Boot_BT.jpg"
in the dropbox directory
"https://www.dropbox.com/sh/buzxekimo2h2r67/AADpUvLndhm2SHa5t9s9Ckksa?dl=0;
2) Source code revision is:
root@blnn719x - /usr/src
2056 # svn info
Path: .
Working Copy Root Path: /usr/src
URL:https://svn.freebsd.org/base/stable/11
Relative URL: ^/stable/11
Repository Root:https://svn.freebsd.org/base
Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f
Revision: 348361
Node Kind: directory
Schedule: normal
Last Changed Author: jkim
Last Changed Rev: 348343
Last Changed Date: 2019-05-29 02:00:52 +0200 (Wed, 29 May 2019)
3) Diff to next revision:
root@blnn719x - /usr/src
2057 # svn diff -r 348362
Index: sys/amd64/amd64/initcpu.c
===
--- sys/amd64/amd64/initcpu.c (revision 348362)
+++ sys/amd64/amd64/initcpu.c (working copy)
@@ -247,6 +247,7 @@
}
hw_ibrs_recalculate();
hw_ssb_recalculate(false);
+ hw_mds_recalculate();
switch (cpu_vendor_id) {
case CPU_VENDOR_AMD:
init_amd();
Index: sys/i386/i386/initcpu.c
===
--- sys/i386/i386/initcpu.c (revision 348362)
+++ sys/i386/i386/initcpu.c (working copy)
@@ -769,6 +769,7 @@
elf32_nxstack = 1;
}
#endif
+ hw_mds_recalculate();
if ((amd_feature & AMDID_RDTSCP) != 0 ||
(cpu_stdext_feature2 & CPUID_STDEXT2_RDPID) != 0)
wrmsr(MSR_TSC_AUX, PCPU_GET(cpuid));
Index: sys/x86/x86/cpu_machdep.c
===
--- sys/x86/x86/cpu_machdep.c (revision 348362)
+++ sys/x86/x86/cpu_machdep.c (working copy)
@@ -1118,14 +1118,6 @@
}
}
-static void
-hw_mds_recalculate_boot(void *arg __unused)
-{
-
- hw_mds_recalculate();
-}
-SYSINIT(mds_recalc, SI_SUB_SMP, SI_ORDER_ANY, hw_mds_recalculate_boot, NULL);
-
static int
sysctl_mds_disable_handler(SYSCTL_HANDLER_ARGS)
{
Index: .
===
--- . (revision 348362)
+++ . (working copy)
Property changes on: .
___
Modified: svn:mergeinfo
## -0,1 +0,0 ##
Reverse-merged /head:r348075
Somewhere here is the problem...
Definitely, there is some problem, but I doubt that it is due to the
revision in the svn. The diff above is the reverse o
AW: GENERIC crash 11.3-PRERELEASE (i386)
Hello Konstantin,
***
Obviously Outlook has destroyed my last reply - here again:
***
I did what you suggested: deleted the content of /usr/src and 'svn co'
the 11-STABLE sources again.
I investigated the three
source files mentioned below and confirmed the 'svn diff' results:
"hw_mds_recalculate();" has been removed from
sys/amd64/amd64/initcpu.c and
sys/i386/i386/initcpu.c
and:
"static void
hw_mds_recalculate_boot(void *arg __unused)
{
hw_mds_recalculate();
}
SYSINIT(mds_recalc, SI_SUB_SMP, SI_ORDER_ANY, hw_mds_recalculate_boot, NULL);"
has been inserted into 'sys/x86/x86/cpu_machdep.c'
That's still the case for 'r349719'. Also remains true that a kernel of
'r349719' crashes as described earlier.
With best regards and have a nice weekend
Matthias Schuendehuette
-Ursprüngliche Nachricht-
Von: Konstantin Belousov
Gesendet: Mittwoch, 3. Juli 2019 15:55
An: Schuendehuette, Matthias (LDA IT PLM)
Cc: 'freebsd-stable@freebsd.org' ; Osipov, Michael
(LDA IT PLM)
Betreff: Re: GENERIC crash 11.3-PRERELEASE (i386)
On Wed, Jul 03, 2019 at 08:42:21AM +0000, Schuendehuette, Matthias wrote:
> Hello Konstantin,
>
> I did some research regarding the kernel crash with the following results>
>
> 1) Last working kernel is:
>
> "FreeBSD 11.3-BETA1 (BLNN719X) #8 r348361: Wed Jul 3 09:30:17 CEST
> 2019"
>
> 1a) DDB-Backtrace of the crashing kernel r348362 can be seen on "Boot_BT.jpg"
> in the dropbox directory
>
> "https://www.dropbox.com/sh/buzxekimo2h2r67/AADpUvLndhm2SHa5t9s9Ckksa?dl=0;
>
>
> 2) Source code revision is:
>
> root@blnn719x - /usr/src
> 2056 # svn info
> Path: .
> Working Copy Root Path: /usr/src
> URL: https://svn.freebsd.org/base/stable/11
> Relative URL: ^/stable/11
> Repository Root: https://svn.freebsd.org/base
> Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f
> Revision: 348361
> Node Kind: directory
> Schedule: normal
> Last Changed Author: jkim
> Last Changed Rev: 348343
> Last Changed Date: 2019-05-29 02:00:52 +0200 (Wed, 29 May 2019)
>
>
> 3) Diff to next revision:
>
> root@blnn719x - /usr/src
> 2057 # svn diff -r 348362
> Index: sys/amd64/amd64/initcpu.c
> ===
> --- sys/amd64/amd64/initcpu.c (revision 348362)
> +++ sys/amd64/amd64/initcpu.c (working copy)
> @@ -247,6 +247,7 @@
> }
> hw_ibrs_recalculate();
> hw_ssb_recalculate(false);
> + hw_mds_recalculate();
> switch (cpu_vendor_id) {
> case CPU_VENDOR_AMD:
> init_amd();
> Index: sys/i386/i386/initcpu.c
> ===
> --- sys/i386/i386/initcpu.c (revision 348362)
> +++ sys/i386/i386/initcpu.c (working copy)
> @@ -769,6 +769,7 @@
> elf32_nxstack = 1;
> }
> #endif
> + hw_mds_recalculate();
> if ((amd_feature & AMDID_RDTSCP) != 0 ||
> (cpu_stdext_feature2 & CPUID_STDEXT2_RDPID) != 0)
> wrmsr(MSR_TSC_AUX, PCPU_GET(cpuid));
> Index: sys/x86/x86/cpu_machdep.c
> ===
> --- sys/x86/x86/cpu_machdep.c (revision 348362)
> +++ sys/x86/x86/cpu_machdep.c (working copy)
> @@ -1118,14 +1118,6 @@
> }
> }
>
> -static void
> -hw_mds_recalculate_boot(void *arg __unused)
> -{
> -
> - hw_mds_recalculate();
> -}
> -SYSINIT(mds_recalc, SI_SUB_SMP, SI_ORDER_ANY, hw_mds_recalculate_boot, NULL);
> -
> static int
> sysctl_mds_disable_handler(SYSCTL_HANDLER_ARGS)
> {
> Index: .
> ===
> --- . (revision 348362)
> +++ . (working copy)
>
> Property changes on: .
> ___
> Modified: svn:mergeinfo
> ## -0,1 +0,0 ##
>Reverse-merged /head:r348075
>
>
>
> Somewhere here is the problem...
Definitely, there is some problem, but I doubt that it is due to the
revision in the svn. The diff above is the reverse of the stable/11
r348362 that was committed on 2019-05-29. Indeed, the missed (or
reverted) r348362 would cause exactly the symptoms you described with
failing AP startup.
I have no idea why do you have the change reverted with merge info, in
your sources. Clean up and retry with pristine tree.
>
>
>
>
> with best regards
> Matthias Schündehütte
>
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
AW: GENERIC crash 11.3-PRERELEASE (i386)
Hello Konstantin,
I did what you suggested: deleted the content of /usr/src and 'svn co'
the 11-STABLE sources again.
Currently 'make buildworld' still runs, but I investigated the three
source files mentioned below and confirmed the 'svn diff' results:
"hw_mds_recalculate();" has been removed from
sys/amd64/amd64/initcpu.c and
sys/i386/i386/initcpu.c
and:
"static void
hw_mds_recalculate_boot(void *arg __unused)
{
hw_mds_recalculate();
}
SYSINIT(mds_recalc, SI_SUB_SMP, SI_ORDER_ANY, hw_mds_recalculate_boot, NULL);"
has been inserted into 'sys/x86/x86/cpu_machdep.c'
That's still the case for 'r349719'.
Did you misunderstand the "+" and "-" signs below?
"+" was the *working* copy, that is 'r348361'
"-" was the next revision 'r384362', which produced the kernel crash
with best regards
Matthias Schündehütte
Siemens AG
Large Drives Applications
Information Technology
Information Technology Product Lifecycle Management
LDA IT PLM
Nonnendammallee 72
13629 Berlin, Deutschland
Tel.: +49 30 386-29957
Mobil: +49 170 8162912
mailto:matthias.schuendehue...@siemens.com
www.siemens.com/ingenuityforlife
-Ursprüngliche Nachricht-
Von: Konstantin Belousov
Gesendet: Mittwoch, 3. Juli 2019 15:55
An: Schuendehuette, Matthias (LDA IT PLM)
Cc: 'freebsd-stable@freebsd.org' ; Osipov, Michael
(LDA IT PLM)
Betreff: Re: GENERIC crash 11.3-PRERELEASE (i386)
On Wed, Jul 03, 2019 at 08:42:21AM +, Schuendehuette, Matthias wrote:
> Hello Konstantin,
>
> I did some research regarding the kernel crash with the following results>
>
> 1) Last working kernel is:
>
> "FreeBSD 11.3-BETA1 (BLNN719X) #8 r348361: Wed Jul 3 09:30:17 CEST
> 2019"
>
> 1a) DDB-Backtrace of the crashing kernel r348362 can be seen on "Boot_BT.jpg"
> in the dropbox directory
>
> "https://www.dropbox.com/sh/buzxekimo2h2r67/AADpUvLndhm2SHa5t9s9Ckksa?dl=0;
>
>
> 2) Source code revision is:
>
> root@blnn719x - /usr/src
> 2056 # svn info
> Path: .
> Working Copy Root Path: /usr/src
> URL: https://svn.freebsd.org/base/stable/11
> Relative URL: ^/stable/11
> Repository Root: https://svn.freebsd.org/base
> Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f
> Revision: 348361
> Node Kind: directory
> Schedule: normal
> Last Changed Author: jkim
> Last Changed Rev: 348343
> Last Changed Date: 2019-05-29 02:00:52 +0200 (Wed, 29 May 2019)
>
>
> 3) Diff to next revision:
>
> root@blnn719x - /usr/src
> 2057 # svn diff -r 348362
> Index: sys/amd64/amd64/initcpu.c
> ===
> --- sys/amd64/amd64/initcpu.c (revision 348362)
> +++ sys/amd64/amd64/initcpu.c (working copy)
> @@ -247,6 +247,7 @@
> }
> hw_ibrs_recalculate();
> hw_ssb_recalculate(false);
> + hw_mds_recalculate();
> switch (cpu_vendor_id) {
> case CPU_VENDOR_AMD:
> init_amd();
> Index: sys/i386/i386/initcpu.c
> ===
> --- sys/i386/i386/initcpu.c (revision 348362)
> +++ sys/i386/i386/initcpu.c (working copy)
> @@ -769,6 +769,7 @@
> elf32_nxstack = 1;
> }
> #endif
> + hw_mds_recalculate();
> if ((amd_feature & AMDID_RDTSCP) != 0 ||
> (cpu_stdext_feature2 & CPUID_STDEXT2_RDPID) != 0)
> wrmsr(MSR_TSC_AUX, PCPU_GET(cpuid));
> Index: sys/x86/x86/cpu_machdep.c
> ===
> --- sys/x86/x86/cpu_machdep.c (revision 348362)
> +++ sys/x86/x86/cpu_machdep.c (working copy)
> @@ -1118,14 +1118,6 @@
> }
> }
>
> -static void
> -hw_mds_recalculate_boot(void *arg __unused)
> -{
> -
> - hw_mds_recalculate();
> -}
> -SYSINIT(mds_recalc, SI_SUB_SMP, SI_ORDER_ANY, hw_mds_recalculate_boot, NULL);
> -
> static int
> sysctl_mds_disable_handler(SYSCTL_HANDLER_ARGS)
> {
> Index: .
> ===
> --- . (revision 348362)
> +++ . (working copy)
>
> Property changes on: .
> ___
> Modified: svn:mergeinfo
> ## -0,1 +0,0 ##
>Reverse-merged /head:r348075
>
>
>
> Somewhere here is the problem...
Definitely, there is some problem, but I doubt that it is due to the
revision in the svn. The diff above is the reverse of the stable/11
r348362 that was committed on 2019-05-29. Indeed, the missed (or
reverted) r348362 would cause exactly the symptoms you described with
failing AP startup.
I have no idea why do you have
AW: GENERIC crash 11.3-PRERELEASE (i386)
Hello Konstantin,
I did some research regarding the kernel crash with the following results>
1) Last working kernel is:
"FreeBSD 11.3-BETA1 (BLNN719X) #8 r348361: Wed Jul 3 09:30:17 CEST
2019"
1a) DDB-Backtrace of the crashing kernel r348362 can be seen on "Boot_BT.jpg"
in the dropbox directory
"https://www.dropbox.com/sh/buzxekimo2h2r67/AADpUvLndhm2SHa5t9s9Ckksa?dl=0;
2) Source code revision is:
root@blnn719x - /usr/src
2056 # svn info
Path: .
Working Copy Root Path: /usr/src
URL: https://svn.freebsd.org/base/stable/11
Relative URL: ^/stable/11
Repository Root: https://svn.freebsd.org/base
Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f
Revision: 348361
Node Kind: directory
Schedule: normal
Last Changed Author: jkim
Last Changed Rev: 348343
Last Changed Date: 2019-05-29 02:00:52 +0200 (Wed, 29 May 2019)
3) Diff to next revision:
root@blnn719x - /usr/src
2057 # svn diff -r 348362
Index: sys/amd64/amd64/initcpu.c
===
--- sys/amd64/amd64/initcpu.c (revision 348362)
+++ sys/amd64/amd64/initcpu.c (working copy)
@@ -247,6 +247,7 @@
}
hw_ibrs_recalculate();
hw_ssb_recalculate(false);
+ hw_mds_recalculate();
switch (cpu_vendor_id) {
case CPU_VENDOR_AMD:
init_amd();
Index: sys/i386/i386/initcpu.c
===
--- sys/i386/i386/initcpu.c (revision 348362)
+++ sys/i386/i386/initcpu.c (working copy)
@@ -769,6 +769,7 @@
elf32_nxstack = 1;
}
#endif
+ hw_mds_recalculate();
if ((amd_feature & AMDID_RDTSCP) != 0 ||
(cpu_stdext_feature2 & CPUID_STDEXT2_RDPID) != 0)
wrmsr(MSR_TSC_AUX, PCPU_GET(cpuid));
Index: sys/x86/x86/cpu_machdep.c
===
--- sys/x86/x86/cpu_machdep.c (revision 348362)
+++ sys/x86/x86/cpu_machdep.c (working copy)
@@ -1118,14 +1118,6 @@
}
}
-static void
-hw_mds_recalculate_boot(void *arg __unused)
-{
-
- hw_mds_recalculate();
-}
-SYSINIT(mds_recalc, SI_SUB_SMP, SI_ORDER_ANY, hw_mds_recalculate_boot, NULL);
-
static int
sysctl_mds_disable_handler(SYSCTL_HANDLER_ARGS)
{
Index: .
===
--- . (revision 348362)
+++ . (working copy)
Property changes on: .
___
Modified: svn:mergeinfo
## -0,1 +0,0 ##
Reverse-merged /head:r348075
Somewhere here is the problem...
with best regards
Matthias Schündehütte
Siemens AG
Large Drives Applications
Information Technology
Information Technology Product Lifecycle Management
LDA IT PLM
Nonnendammallee 72
13629 Berlin, Deutschland
Tel.: +49 30 386-29957
Mobil: +49 170 8162912
mailto:matthias.schuendehue...@siemens.com
www.siemens.com/ingenuityforlife
-Ursprüngliche Nachricht-
Von: Konstantin Belousov
Gesendet: Donnerstag, 27. Juni 2019 21:00
An: Schuendehuette, Matthias (LDA IT PLM)
Cc: 'freebsd-stable@freebsd.org'
Betreff: Re: GENERIC crash 11.3-PRERELEASE (i386)
On Thu, Jun 27, 2019 at 07:11:40AM +, Schuendehuette, Matthias wrote:
> Hi,
>
> the missing attachments can be found here now:
>
> https://www.dropbox.com/sh/buzxekimo2h2r67/AADpUvLndhm2SHa5t9s9Ckksa?dl=0
>
So your AP (Application Processor) seems to get fault, most likely in the
trap handler. There were absolutely no changes in the stable/11 in the
area of SMP startup for quite long time.
To get anywhere, you should perhaps add ddb to your kernel configuration
and get the backtrace. The backtrace would be long, I am only interested
in the first several frames before faults go into recursion.
But, since 1 month earlier kernel worked, and there were no changes, this
might indicate either a failing hardware (your machine is quite old, it
is Core2 Xeon, am I right ?) or problems with your build environment.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
AW: GENERIC crash 11.3-PRERELEASE (i386)
Hi Konstantin, thanks for your reply. I'm in doubt if there is a hardware defect. If that would be the case, why should the slightly older kernel work? This (admittedly old) server is running fine with a kernel "r347014" of June 5th, 2019. The crashing kernel has "r349405", so quite some things have happened in between. Thanks for the hint with "DDB", I'll try that next week. As well as narrowing down the first "crashing-releasenumber". Have a nice weekend :-) with best regards Matthias Schündehütte -Ursprüngliche Nachricht- Von: Konstantin Belousov Gesendet: Donnerstag, 27. Juni 2019 21:00 An: Schuendehuette, Matthias (LDA IT PLM) Cc: 'freebsd-stable@freebsd.org' Betreff: Re: GENERIC crash 11.3-PRERELEASE (i386) On Thu, Jun 27, 2019 at 07:11:40AM +, Schuendehuette, Matthias wrote: > Hi, > > the missing attachments can be found here now: > > https://www.dropbox.com/sh/buzxekimo2h2r67/AADpUvLndhm2SHa5t9s9Ckksa?dl=0 > So your AP (Application Processor) seems to get fault, most likely in the trap handler. There were absolutely no changes in the stable/11 in the area of SMP startup for quite long time. To get anywhere, you should perhaps add ddb to your kernel configuration and get the backtrace. The backtrace would be long, I am only interested in the first several frames before faults go into recursion. But, since 1 month earlier kernel worked, and there were no changes, this might indicate either a failing hardware (your machine is quite old, it is Core2 Xeon, am I right ?) or problems with your build environment. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: GENERIC crash 11.3-PRERELEASE (i386)
Hi, the missing attachments can be found here now: https://www.dropbox.com/sh/buzxekimo2h2r67/AADpUvLndhm2SHa5t9s9Ckksa?dl=0 with best regards Matthias Schündehütte ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
GENERIC crash 11.3-PRERELEASE (i386)
Hello, for some days now the GENERIC kernel of 11.3-PRERELEASE (i386) crashes on my ProLiant DL380 G5 server. Main error message is "kernel trap 12 with interrupts disabled". Since there is no crash dump I attach some screen shots of the boot messages. I hope this does not violate the mailing list rules... The GENERIC config-file is: # $FreeBSD: stable/11/sys/i386/conf/GENERIC 323770 2017-09-19 16:51:51Z jpaetzel $ The last working kernel I have is from June 5, 2019. As always: If additional information is needed, I'll do whatever is necessary. :-) with best regards Matthias Schündehütte Siemens AG Large Drives Applications Information Technology Information Technology Product Lifecycle Management LDA IT PLM Nonnendammallee 72 13629 Berlin, Deutschland mailto:matthias.schuendehue...@siemens.com ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Stack overflow with kernel r254683
Hello, yesterday I got a kernel crash on my server (a ProLiant DL380 G5): panic: stack overflow detected; backtrace may be corrupted Kernel is 9.2-PRERELEASE FreeBSD 9.2-PRERELEASE #7 r254683 The stack trace reads: #0 doadump (textdump=1) at pcpu.h:249 249 pcpu.h: No such file or directory. in pcpu.h (kgdb) #0 doadump (textdump=1) at pcpu.h:249 #1 0xc0668a4d in kern_reboot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:449 #2 0xc0668f07 in panic (fmt=0x104 Address 0x104 out of bounds) at /usr/src/sys/kern/kern_shutdown.c:637 #3 0xc0691da2 in __stack_chk_fail () at /usr/src/sys/kern/stack_protector.c:17 #4 0xc7fdb175 in nfsrvd_setattr (nd=0xc73b4400, isdgram=-952596480, vp=0xc8001140, p=0xf405ecc8, exp=0xc07af7f0) at /usr/src/sys/modules/nfsd/../../fs/nfsserver/nfs_nfsdserv.c:371 #5 0xc7fdb6e0 in nfsrvd_releaselckown (nd=0xc7442a00, isdgram=-952596480, vp=0xc7388848, p=0xf405ecb8, exp=0x0) at /usr/src/sys/modules/nfsd/../../fs/nfsserver/nfs_nfsdserv.c:3481 #6 0xc07af7f0 in svc_run_internal (pool=0xc7de8b80, ismaster=0) at /usr/src/sys/rpc/svc.c:1109 #7 0xc07b006d in svc_thread_start (arg=0xc7de8b80) at /usr/src/sys/rpc/svc.c:1200 #8 0xc06384f7 in fork_exit (callout=0xc07b0060 svc_thread_start, arg=0xc7de8b80, frame=0xf405ed08) at /usr/src/sys/kern/kern_fork.c:992 #9 0xc08787c4 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:279 I have all the files in /var/crash, so if someone wants additional informations I should be able to deliver them. The kernel config file is customized in the sense that I have removed kernel items, that aren't used on that machine. One major difference: I use options NFSCLIENT # Network Filesystem Client options NFSSERVER # Network Filesystem Server instead of options NFSCL # New Network Filesystem Client options NFSD# New Network Filesystem Server because a kernel a few weeks ago immediately crashed with the new NFS-code. But it seems now, that the old NFS-code is also somehow damaged. Ah, and I still have from older releases of FreeBSD the following loader options - do they still make sense? geom_vinum_load=YES kern.maxdsiz=734003200 vm.pmap.shpgperproc=256 vm.pmap.pv_entry_max=3145728 'geom_vinum' is used as LVM only, no RAIDs are configured. This server is primarily a Samba server with the SMB-shares exported as NFS-shares as well for the other *nix-servers around. Because this is the most loaded production server, testing is a bit difficult, restricted to the evening and the weekends. On my two other FreeBSD machines I have no problems at all, one of them is an identical ProLiant server with a nearly identical kernel config - runs like a charm... Has someone a good advice or further questions? with best regards Matthias Schündehütte ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
RE: FreeBSD supported branches update
Hello, owner-freebsd-security-notificati...@freebsd.org wrote on : The branches supported by the FreeBSD Security Officer have been updated to reflect the EoL (end-of-life) of FreeBSD 7.0. The new list is below and at URL: http://security.freebsd.org/ . Please note that FreeBSD 7.0 was originally announced with an EoL date of February 28, 2009, but the EoL was delayed by two months in order to allow a 3 month window for systems to be upgraded to FreeBSD 7.1. I have severe problems with this, because NFS-Locking is not working on FreeBSD-7.1 and later with HP-UX clients. See several PRs which are talking about this. Same is true für FreeBSD-6.4. So all Releases with kernel-supported NFS-Locking have problems with HP-UX clients. FreeBSD-7.0 is the last release that is working and that is therefor still productive at our site. What do you recommend? with best regards Matthias Schündehütte SIEMENS AG, Industry Sector, DT LD S IT Tel. +49-30-386 29957 -- Plain text mail please HTML is considered as SPAM ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 'xl'+DP83840 broken?
Hello, I guess see PR kern/27722 on www.freebsd.org Bingo! Thanks a lot, Wilko. Since I'm tracking STABLE, I replaced revision 1.2.2.3 of nsphy.c (which was merged from current on May 14th) with 1.2.2.2 from W.Paul. This solved all my problems! IMHO the new nsphy.c has nothing to do with anything called STABLE, (BTW: it killed the connected switchport after some time - nothing that I like :-( ). And it doesn't help to fix problems with 'fxp' while breaking 'xl'. This MFC should be withdrawn. Thanks a lot again and... Ciao/BSD - Matthias To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
