From: Jay Cliburn <jacliburn@bellsouth.net>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: Jay Cliburn <jacliburn@bellsouth.net>,
Luca Tettamanti <kronos.it@gmail.com>,
Chris Snook <csnook@redhat.com>, Jeff Garzik <jeff@garzik.org>,
Pekka Enberg <penberg@cs.helsinki.fi>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
Christoph Lameter <clameter@sgi.com>,
torvalds@osdl.org
Subject: Re: atl1 64-bit => 32-bit DMA borkage (reproducible, bisected)
Date: Fri, 25 Apr 2008 19:57:43 -0500 [thread overview]
Message-ID: <20080425195743.2bfe66ee@osprey.hogchain.net> (raw)
In-Reply-To: <20080421210821.28053a92@osprey.hogchain.net>
On Mon, 21 Apr 2008 21:08:21 -0500
Jay Cliburn <jacliburn@bellsouth.net> wrote:
>
> Alexey, can you please try this (very minimally tested) patch?
Alexey, have you found time to try this patch yet?
Thanks.
>
> diff --git a/drivers/net/atlx/atl1.c b/drivers/net/atlx/atl1.c
> index 5586fc6..07fe5c0 100644
> --- a/drivers/net/atlx/atl1.c
> +++ b/drivers/net/atlx/atl1.c
> @@ -1115,9 +1115,6 @@ static void atl1_free_ring_resources(struct
> atl1_adapter *adapter) struct atl1_rrd_ring *rrd_ring =
> &adapter->rrd_ring; struct atl1_ring_header *ring_header =
> &adapter->ring_header;
> - atl1_clean_tx_ring(adapter);
> - atl1_clean_rx_ring(adapter);
> -
> kfree(tpd_ring->buffer_info);
> pci_free_consistent(pdev, ring_header->size,
> ring_header->desc, ring_header->dma);
> @@ -3423,6 +3420,8 @@ static int atl1_set_ringparam(struct net_device
> *netdev, adapter->rrd_ring = rrd_old;
> adapter->tpd_ring = tpd_old;
> adapter->ring_header = rhdr_old;
> + atl1_clean_tx_ring(adapter);
> + atl1_clean_rx_ring(adapter);
> atl1_free_ring_resources(adapter);
> adapter->rfd_ring = rfd_new;
> adapter->rrd_ring = rrd_new;
next prev parent reply other threads:[~2008-04-26 0:58 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-11 3:33 2.6.25-rc8-mm2 Andrew Morton
2008-04-11 6:28 ` 2.6.25-rc8-mm2: boot hang after "ACPI: using IOAPIC for interrupt routing" Alexey Dobriyan
2008-04-11 6:29 ` Alexey Dobriyan
2008-04-11 6:43 ` Pekka Enberg
2008-04-11 10:35 ` Pekka Enberg
2008-04-11 21:07 ` Alexey Dobriyan
2008-04-11 21:25 ` Pekka J Enberg
2008-04-11 23:09 ` Alexey Dobriyan
2008-04-11 9:57 ` 2.6.25-rc8-mm2 KAMEZAWA Hiroyuki
2008-04-11 10:23 ` 2.6.25-rc8-mm2 KAMEZAWA Hiroyuki
2008-04-11 10:34 ` 2.6.25-rc8-mm2 Pekka Enberg
2008-04-11 10:57 ` 2.6.25-rc8-mm2 KAMEZAWA Hiroyuki
2008-04-11 11:17 ` 2.6.25-rc8-mm2 KAMEZAWA Hiroyuki
2008-04-11 13:17 ` 2.6.25-rc8-mm2 KAMEZAWA Hiroyuki
2008-04-11 14:24 ` 2.6.25-rc8-mm2 Pekka Enberg
2008-04-14 3:13 ` 2.6.25-rc8-mm2 KAMEZAWA Hiroyuki
2008-04-11 13:40 ` 2.6.25-rc8-mm2 Adrian Bunk
2008-04-12 4:22 ` 2.6.25-rc8-mm2 Andrew Morton
2008-04-12 18:43 ` 2.6.25-rc8-mm2 Aneesh Kumar K.V
2008-04-13 7:45 ` 2.6.25-rc8-mm2 Michael Schmitz
2008-04-13 8:11 ` 2.6.25-rc8-mm2 Geert Uytterhoeven
2008-04-11 23:43 ` 2.6.25-rc8-mm2: panic involving mount_block_root and down the road Alexey Dobriyan
2008-04-12 0:59 ` 2.6.25-rc8-mm2: CONFIG_ATA_SFF: " Alexey Dobriyan
2008-04-12 6:52 ` Adrian Bunk
2008-04-12 10:02 ` Jeff Garzik
2008-04-13 0:45 ` Tejun Heo
2008-04-13 0:51 ` [mm patch] select ATA_SFF Adrian Bunk
2008-04-12 5:53 ` 2.6.25-rc8-mm2 Valdis.Kletnieks
2008-04-12 6:07 ` 2.6.25-rc8-mm2 Andrew Morton
2008-04-12 8:52 ` 2.6.25-rc8-mm2 - CONFIG_PROFILE_LIKELY broke again Valdis.Kletnieks
2008-04-12 9:41 ` 2.6.25-rc8-mm2 Valdis.Kletnieks
2008-04-12 10:47 ` 2.6.25-rc8-mm2 - ftraced chews 100% of a CPU Valdis.Kletnieks
2008-04-13 20:44 ` 2.6.25-rc8-mm2: IP: [<ffffffff802868f9>] __kmalloc+0x69/0x110 Alexey Dobriyan
2008-04-13 20:53 ` Andrew Morton
2008-04-14 16:18 ` Pekka Enberg
2008-04-14 18:00 ` Christoph Lameter
2008-04-14 9:51 ` Pekka J Enberg
2008-04-14 16:01 ` Pekka Enberg
2008-04-14 17:53 ` Christoph Lameter
2008-04-14 17:57 ` Christoph Lameter
2008-04-14 18:32 ` Alexey Dobriyan
2008-04-14 19:56 ` 2.6.25-rc8-mm2: FIX kmalloc-2048 (was Re: 2.6.25-rc8-mm2: IP: [<ffffffff802868f9>] __kmalloc+0x69/0x110) Alexey Dobriyan
2008-04-14 20:05 ` Christoph Lameter
2008-04-19 11:17 ` Alexey Dobriyan
2008-04-19 14:45 ` atl1 64-bit => 32-bit DMA borkage (reproducible, bisected) Alexey Dobriyan
2008-04-20 2:54 ` Jay Cliburn
2008-04-20 11:14 ` Alexey Dobriyan
2008-04-20 11:06 ` Jay Cliburn
2008-04-20 12:26 ` Alexey Dobriyan
2008-04-20 18:37 ` Jay Cliburn
2008-04-20 20:55 ` Alexey Dobriyan
2008-04-21 18:42 ` Chris Snook
2008-04-21 19:56 ` Alexey Dobriyan
2008-04-22 2:08 ` Jay Cliburn
2008-04-22 19:02 ` Alexey Dobriyan
2008-04-26 0:57 ` Jay Cliburn [this message]
2008-04-28 6:42 ` Alexey Dobriyan
2008-05-04 21:15 ` Alexey Dobriyan
2008-05-05 0:31 ` Jay Cliburn
2008-05-05 0:34 ` Jay Cliburn
2008-05-06 16:02 ` Jay Cliburn
2008-05-09 19:51 ` Alexey Dobriyan
2008-05-09 18:56 ` Chris Snook
2008-05-09 20:07 ` Alexey Dobriyan
2008-05-09 19:38 ` Jay Cliburn
2008-05-10 19:31 ` [PATCH] " Alexey Dobriyan
2008-05-11 1:58 ` Jay Cliburn
2008-04-14 8:07 ` BUG at __dentry_open [Was: 2.6.25-rc8-mm2] Jiri Slaby
2008-04-15 17:00 ` 2.6.25-rc8-mm2: Observed problems: Not a detailed bug report Zan Lynx
2008-04-15 18:42 ` Andrew Morton
2008-04-15 20:12 ` Rafael J. Wysocki
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=20080425195743.2bfe66ee@osprey.hogchain.net \
--to=jacliburn@bellsouth.net \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=csnook@redhat.com \
--cc=jeff@garzik.org \
--cc=kronos.it@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--cc=torvalds@osdl.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