public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Beezly <beezly@beezly.org.uk>
To: "David S. Miller" <davem@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Sun GEM card looses TX on x86 32bit PCI
Date: 11 Mar 2002 18:35:01 +0000	[thread overview]
Message-ID: <1015871701.2832.1.camel@monkey> (raw)
In-Reply-To: <20020311.042124.103955441.davem@redhat.com>
In-Reply-To: <20020310.164350.107967417.davem@redhat.com> <1015834777.1802.8.camel@monkey> <1015849164.2153.3.camel@monkey>  <20020311.042124.103955441.davem@redhat.com>

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

Hi David,

Sorry it took so long for me to get back to you. Sadly it also hung with
this patch ;) I was unable to get an oops out of it (machine was
completely hosed and in X so I couldn't even note the oops on paper :(
).

Beezly

On Mon, 2002-03-11 at 12:21, David S. Miller wrote:
>    From: Beezly <beezly@beezly.org.uk>
>    Date: 11 Mar 2002 12:19:24 +0000
> 
>    I managed to run the latest patch, but it appears to Oops when the
>    overflow condition occurs. Sadly I was not able to get the output of the
>    oops... but it was at exactly the same time that I was run my "test"
>    which causes the RX to halt.
> 
> Duh, this will fix it:
> 
> --- drivers/net/sungem.c.~1~	Mon Mar 11 04:18:58 2002
> +++ drivers/net/sungem.c	Mon Mar 11 04:24:13 2002
> @@ -317,7 +317,7 @@
>  	}
>  
>  	/* Second, disable RX DMA. */
> -	writel(0, RXDMA_CFG);
> +	writel(0, gp->regs + RXDMA_CFG);
>  	for (limit = 0; limit < 5000; limit++) {
>  		if (!(readl(gp->regs + RXDMA_CFG) & RXDMA_CFG_ENABLE))
>  			break;


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 232 bytes --]

  reply	other threads:[~2002-03-11 18:36 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-10 20:36 Sun GEM card looses TX on x86 32bit PCI Beezly
2002-03-11  0:43 ` David S. Miller
2002-03-11  8:19   ` Beezly
2002-03-11 12:19     ` Beezly
2002-03-11 12:21       ` David S. Miller
2002-03-11 18:35         ` Beezly [this message]
2002-03-11 19:02           ` David S. Miller
2002-03-11 21:11             ` Beezly
2002-03-11 21:23               ` Beezly
2002-03-11 22:51                 ` Beezly
2002-03-12 17:31                   ` David S. Miller
2002-03-12 20:34                     ` Beezly
2002-03-12 20:39                       ` David S. Miller
2002-03-14 20:43                     ` Aaron Sethman
2002-03-14 21:21                       ` Aaron Sethman
2002-03-11  1:39 ` David S. Miller
2002-03-11  1:58   ` David S. Miller
2002-03-11  8:29     ` Beezly
2002-03-11  8:42       ` David S. Miller

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=1015871701.2832.1.camel@monkey \
    --to=beezly@beezly.org.uk \
    --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