public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Eloy A. Paris" <peloy@chapus.net>
To: "David S. Miller" <davem@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: tcpdump with CONFIG_FILTER causes Oops on Sparc
Date: Wed, 29 May 2002 10:49:14 -0400	[thread overview]
Message-ID: <20020529144913.GA17275@chapus.net> (raw)
In-Reply-To: <20020528220727.GA12229@chapus.net> <20020528.233534.27508491.davem@redhat.com>

Hi Dave,

On Tue, May 28, 2002 at 11:35:34PM -0700, David S. Miller wrote:

> What compiler was used to build this sparc64 kernel?

Whoops! Sorry I missed this bit of information; I know it's important.

'dmesg | grep gcc' reports this:

Linux version 2.4.19-pre8 (elparis@elparis-lnx) (gcc version egcs-2.92.11 19980921 (gcc2 ss-980609 experimental)) #7 Tue May 28 17:16:45 EDT 2002

Now, I have good news: Marcelo released 2.4.19-pre9 a little bit after
I started to play with 2.4.19-pre8, so today I grabbed -pre9, built it,
booted it, and now I have no problems whatsoever. Same compiler:

Linux version 2.4.19-pre9 (elparis@elparis-lnx) (gcc version egcs-2.92.11 19980921 (gcc2 ss-980609 experimental)) #9 Wed May 29 09:36:59 EDT 2002

Does this ring a bell, maybe something you fixed? (I see lots of fixes
from you in the -pre9 changelog.)

Let me know if you want further information, and thanks for whatever
magic you put into 2.4.19-pre9.

Cheers,

Eloy.-

      reply	other threads:[~2002-05-29 14:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-28 22:07 tcpdump with CONFIG_FILTER causes Oops on Sparc Eloy A. Paris
2002-05-29  6:35 ` David S. Miller
2002-05-29 14:49   ` Eloy A. Paris [this message]

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=20020529144913.GA17275@chapus.net \
    --to=peloy@chapus.net \
    --cc=davem@redhat.com \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox