public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Manfred Spraul <manfred@colorfullife.com>
To: Nathan Walp <faceprint@faceprint.com>
Cc: Dave Jones <davej@suse.de>, Benjamin Pharr <ben@benpharr.com>,
	linux-kernel@vger.kernel.org, vojtech@suse.cz
Subject: Re: Linux 2.5.5-dj1 - Bug Reports
Date: Fri, 01 Mar 2002 19:12:24 +0100	[thread overview]
Message-ID: <3C7FC488.F5D348DC@colorfullife.com> (raw)
In-Reply-To: <20020221233700.GA512@hst000004380um.kincannon.olemiss.edu> <20020222022149.N5583@suse.de> <20020222063721.GA8879@faceprint.com>

[-- Attachment #1: Type: text/plain, Size: 760 bytes --]

Nathan Walp wrote:
> 
> 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.

Please apply the attached oneliner, it fixes the problem. The error was
spotted by Tim or Jeff.

--
	Manfred

[-- Attachment #2: patch-natsemi-typo --]
[-- Type: text/plain, Size: 398 bytes --]

--- 2.5/drivers/net/natsemi.c	Fri Mar  1 17:16:38 2002
+++ build-2.5/drivers/net/natsemi.c	Fri Mar  1 19:11:52 2002
@@ -1380,7 +1380,7 @@
 		np->rx_ring[entry].cmd_status =
 			cpu_to_le32(np->rx_buf_sz);
 	}
-	if (np->cur_rx - np->dirty_tx == RX_RING_SIZE) {
+	if (np->cur_rx - np->dirty_rx == RX_RING_SIZE) {
 		if (debug > 2)
 			printk(KERN_INFO "%s: going OOM.\n", dev->name);
 		np->oom = 1;

  parent reply	other threads:[~2002-03-01 18:14 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-21 23:37 Linux 2.5.5-dj1 - Bug Reports Benjamin Pharr
2002-02-22  1:21 ` Dave Jones
2002-02-22  1:23   ` Vojtech Pavlik
2002-02-23 21:28     ` Pavel Machek
2002-02-24 21:00     ` Linux 2.5.5-dj1 - problem with /dev/input/mice Ben Clifford
2002-02-24 21:27       ` Vojtech Pavlik
2002-02-24 21:42         ` Ben Clifford
2002-02-24 21:45           ` Vojtech Pavlik
2002-02-28  9:58         ` Pavel Machek
2002-02-22  6:37   ` Linux 2.5.5-dj1 - Bug Reports Nathan Walp
2002-02-28 16:59     ` Nathan Walp
2002-02-28 19:57       ` Benjamin Pharr
2002-02-28 20:47       ` Dave Jones
2002-03-01 18:12     ` Manfred Spraul [this message]
2002-02-24 21:02   ` Linux 2.5.5-dj1 - IPv6 not loading correctly Ben Clifford
2002-02-25  6:16     ` Ben Clifford
2002-02-25 21:32       ` Dave Jones
2002-02-25 22:18         ` David S. Miller
2002-02-27 20:23           ` Arnaldo Carvalho de Melo

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=3C7FC488.F5D348DC@colorfullife.com \
    --to=manfred@colorfullife.com \
    --cc=ben@benpharr.com \
    --cc=davej@suse.de \
    --cc=faceprint@faceprint.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vojtech@suse.cz \
    /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