From: Dave Jones <davej@suse.de>
To: Nathan Walp <faceprint@faceprint.com>
Cc: Benjamin Pharr <ben@benpharr.com>,
linux-kernel@vger.kernel.org, manfred@colorfullife.com
Date: Thu, 28 Feb 2002 21:45:52 +0100 [thread overview]
Message-ID: <20020228214552.F32662@suse.de> (raw)
manfred@colorfullife.com
Bcc:
Subject: Re: Linux 2.5.5-dj1 - Bug Reports
Reply-To:
In-Reply-To: <20020228165951.GA4014@faceprint.com>; from faceprint@faceprint.com on Thu, Feb 28, 2002 at 11:59:54AM -0500
> > On Fri, Feb 22, 2002 at 02:21:49AM +0100, Dave Jones wrote:
> > > > It compiled fine. When I booted up everything looked normal with the
> > > > exception of a
> > > > eth1: going OOM
> > > > message that kept scrolling down the screen. My eth1 is a natsemi card.
> > >
> > > That's interesting. Probably moreso for Manfred. I'll double check
> > > I didn't goof merging the oom-handling patch tomorrow.
> >
> > Ditto here on my natsemi. It hasn't really spit out the error since
> > boot, about 12 hours ago. Card has been mainly idle, only used to
> > connect via crossover cable to my laptop, which hasn't been used much in
> > that time.
>
> dj2 is showing the same behavior, but I found out that the messages
> continue to be printed 100 times/second until I ping-flooded the machine
> on the other end of that card. The minimal DHCP traffic prior to the
> ping flood was not enough to make it stop.
>
> Hope this helps narrow down the problem some.
Yup, Manfred is aware of this, but hasn't had time to look into it yet.
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
reply other threads:[~2002-02-28 20:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20020228214552.F32662@suse.de \
--to=davej@suse.de \
--cc=ben@benpharr.com \
--cc=faceprint@faceprint.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.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