From: Roland Fehrenbacher <Roland.Fehrenbacher@transtec.de>
To: linux-kernel@vger.kernel.org
Cc: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>,
"Nakajima, Jun" <jun.nakajima@intel.com>,
"Seth, Rohit" <rohit.seth@intel.com>,
"Luck, Tony" <tony.luck@intel.com>,
"Mallick, Asit K" <asit.k.mallick@intel.com>,
"Hugh Dickins" <hugh@veritas.com>,
pk@q-leap.com
Subject: Re: Q: backport of the free_pgtables tlb fixes to 2.4
Date: Fri, 31 May 2002 15:19:56 +0200 [thread overview]
Message-ID: <15607.30844.526469.488274@transtec.de> (raw)
Hi all,
we actually also ran into this bug on a dual xeon (2GHz
Prestonia) with Hyperthreading enabled. Without Hyperthreading, it was hard to
reproduce the problem. The following script (requires bash >= 2.0.5) provokes
the problem in a very short time. With the patch from Intel, the problem is
gone (patched into 2.4.18), no side effects discovered so far.
Thanks to Hugh Dickins <hugh@veritas.com> for pointing out the patch to us.
Cheers,
Roland
Here is the script:
-----------------------
#!/bin/sh
# Small script to provoke a SIGSEV on SMP machines with kernel problem
# requires bash > 2.0.5. The script fails e.g. on dual xeon systems without
# Intel patch (Message title: Illegal instruction failures fixes for 2.4.18 in # kernel mailing list, 22.5.2002).
# Script simply executes a couple of mktemp loops in the background, and tries
# to read the generated file back.
#
# Author: Roland Fehrenbacher, rf@q-leap.com
base_out=/tmp/test-sigsev
maxprocs=5
myname=`basename $0`
pids=""
files=""
trap 'killall $myname; rm -f $files ${base_out}??????;' 0 1 2 3 15
for (( num=1; num <= $maxprocs; num++ )); do
while true; do
file=`mktemp ${base_out}XXXXXX` || { echo mktemp failed; break; }
cat $file || { echo open $file failed; break; }
rm -f $file
done > ${base_out}-${num}.out 2>&1 &
pids="$pids $!"
files="$files ${base_out}-${num}.out"
done
printf "PIDS running = $pids\n--\n"
printf "No further output should appear if no bug is present. Run script for\n"
printf "a couple of hours to be sure everything is ok. Ctrl-C to stop.\n--\n"
i=1
while true; do
echo $i: ok >> ${base_out}-${num}.out
for pid in $pids; do
ps -p $pid > /dev/null 2>&1 || \
{ echo "count = $i: Pid $pid died" >> ${base_out}-${num}.out; \
pids=`echo $pids | sed -e s/$pid//g`; }
done
sleep 10
((i++))
done &
files="$files ${base_out}-${num}.out"
sleep 1
tail -f $files | grep "count ="
next reply other threads:[~2002-05-31 13:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-31 13:19 Roland Fehrenbacher [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-23 5:14 Andrea Arcangeli
2002-05-23 6:01 ` Linus Torvalds
2002-05-23 19:57 ` Andrea Arcangeli
2002-05-23 20:05 ` Linus Torvalds
2002-05-23 20:41 ` Andrea Arcangeli
2002-05-23 19:53 ` Martin Dalecki
2002-05-23 21:15 ` Andrea Arcangeli
2002-05-23 20:40 ` Martin Dalecki
2002-05-23 22:04 ` Linus Torvalds
2002-05-23 23:22 ` Andrea Arcangeli
2002-05-23 23:51 ` Linus Torvalds
2002-05-24 0:27 ` Andrea Arcangeli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=15607.30844.526469.488274@transtec.de \
--to=roland.fehrenbacher@transtec.de \
--cc=asit.k.mallick@intel.com \
--cc=hugh@veritas.com \
--cc=jun.nakajima@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pk@q-leap.com \
--cc=rohit.seth@intel.com \
--cc=tony.luck@intel.com \
--cc=venkatesh.pallipadi@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®