All of lore.kernel.org
 help / color / mirror / Atom feed
From: Evan Felix <evan.felix@pnl.gov>
To: linux-ia64@vger.kernel.org
Subject: Re: ia64 2.6.0-test3 crashes on IOZone
Date: Mon, 18 Aug 2003 21:15:31 +0000	[thread overview]
Message-ID: <marc-linux-ia64-106124095917405@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106098668517415@msgid-missing>

ok, i'll try the patch, but from your change long i did not see any
issue there either.

I am using an ext3 system, which was made under 2.4.XX  before i
installed the newer kernel.  This test is run in the root filesystem if
that makes a difference.

Evan

On Mon, 2003-08-18 at 13:52, David Mosberger wrote:
> >>>>> On Sat, 16 Aug 2003 17:40:53 -0700, Evan Felix <evan.felix@pnl.gov> said:
> 
>   Evan> I compiled the kernel with the debian unstable gcc 3.2:
>   Evan> Reading specs from /usr/lib/gcc-lib/ia64-linux/3.2.3/specs
> 
> OK.  While I don't use this compiler myself, it should be OK.
> 
>   Evan> if it matters this was a bk pull from linus's tree that claimed to be
>   Evan> 2.6.0-test3...
> 
> That should be OK.  I did release an ia64-specific patch in the
> meantime.  I don't really expect it to make a difference for you
> problem, though (you might want to try it just to be on the safe
> side).
> 
>   Evan> also is there any reason i did not get more of the stack trace
>   Evan> from the kernel?
> 
> It might indicate stack corruption.  Which brings me to the next
> question: what filesystem were you using?  I used ext3.
> 
> 	--david

  parent reply	other threads:[~2003-08-18 21:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-15 22:37 ia64 2.6.0-test3 crashes on IOZone Evan Felix
2003-08-16  4:52 ` David Mosberger
2003-08-17  0:40 ` Evan Felix
2003-08-18 20:52 ` David Mosberger
2003-08-18 21:15 ` Evan Felix [this message]
2003-08-18 23:53 ` David Mosberger
2003-08-19  0:12 ` Evan Felix
2003-08-19  0:16 ` David Mosberger

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=marc-linux-ia64-106124095917405@msgid-missing \
    --to=evan.felix@pnl.gov \
    --cc=linux-ia64@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.