From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Ion Badulescu <ionut@badula.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix starfire compiler warning on PAE
Date: Mon, 06 Jan 2003 13:14:31 -0800 [thread overview]
Message-ID: <33980000.1041887671@flay> (raw)
In-Reply-To: <200301062057.h06KvJA03060@buggy.badula.org>
> Fix the compiler warning, yes; fix the driver for 64-bit dma_addr_t, no.
> It may work with PAE, by chance, if all addresses returned by pci_map_single
> and friends are < (1 << 33), but not otherwise.
Odd. It seems to work with PAE now. pci_map_single just casts an address
though ... are the things you're passing it always allocated from ZONE_NORMAL?
I run these all the time on 16Gb machines with 16 processors (ia32 NUMA-Q).
> Jeff already has an updated starfire driver in his queue, complete with
> full 64-bit support.
Cool! Sorry, I've just been seeing that warning for about 1 year, and was
sick of it.
> [the cc: to the maintainer is always appreciated...]
Sorry, missed that. But in that case, I have another question for you ;-)
Why do I get wierd errors like this:
Jan 6 10:09:53 larry kernel: eth0: Increasing Tx FIFO threshold to 80 bytes
Jan 6 10:09:56 larry kernel: eth0: Increasing Tx FIFO threshold to 96 bytes
Jan 6 10:09:56 larry kernel: eth0: Increasing Tx FIFO threshold to 112 bytes
Jan 6 10:10:09 larry kernel: eth0: Increasing Tx FIFO threshold to 128 bytes
Jan 6 10:10:09 larry kernel: eth0: Increasing Tx FIFO threshold to 144 bytes
Jan 6 10:10:12 larry kernel: eth0: Increasing Tx FIFO threshold to 160 bytes
Jan 6 10:10:12 larry kernel: eth0: Increasing Tx FIFO threshold to 176 bytes
Jan 6 10:10:14 larry kernel: eth0: Increasing Tx FIFO threshold to 192 bytes
Jan 6 10:10:30 larry kernel: eth0: Increasing Tx FIFO threshold to 208 bytes
Jan 6 10:10:32 larry kernel: eth0: Increasing Tx FIFO threshold to 224 bytes
Jan 6 10:10:39 larry kernel: eth0: Increasing Tx FIFO threshold to 240 bytes
Jan 6 10:10:39 larry kernel: eth0: Increasing Tx FIFO threshold to 256 bytes
Jan 6 10:10:39 larry kernel: eth0: Increasing Tx FIFO threshold to 272 bytes
Jan 6 10:10:46 larry kernel: eth0: Increasing Tx FIFO threshold to 288 bytes
Jan 6 10:10:46 larry kernel: eth0: Increasing Tx FIFO threshold to 304 bytes
Jan 6 10:10:47 larry kernel: eth0: Increasing Tx FIFO threshold to 320 bytes
Jan 6 10:10:47 larry kernel: eth0: Increasing Tx FIFO threshold to 336 bytes
Jan 6 10:10:57 larry kernel: eth0: Increasing Tx FIFO threshold to 352 bytes
Jan 6 10:10:57 larry kernel: eth0: Increasing Tx FIFO threshold to 368 bytes
Jan 6 10:11:22 larry kernel: eth0: Increasing Tx FIFO threshold to 384 bytes
Jan 6 10:11:37 larry kernel: eth0: Increasing Tx FIFO threshold to 400 bytes
Jan 6 10:11:58 larry kernel: eth0: Increasing Tx FIFO threshold to 416 bytes
Jan 6 10:12:29 larry kernel: eth0: Increasing Tx FIFO threshold to 432 bytes
Jan 6 10:12:29 larry kernel: eth0: Increasing Tx FIFO threshold to 448 bytes
Jan 6 10:12:29 larry kernel: eth0: Increasing Tx FIFO threshold to 464 bytes
I also recall getting errors like "Something Wicked happened", but I
don't seem to be able to find them in the log right now.
Thanks,
M.
next prev parent reply other threads:[~2003-01-06 21:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-05 5:08 [PATCH] Fix starfire compiler warning on PAE Martin J. Bligh
2003-01-06 20:57 ` Ion Badulescu
2003-01-06 21:14 ` Martin J. Bligh [this message]
2003-01-06 21:35 ` Ion Badulescu
2003-01-06 21:45 ` Martin J. Bligh
2003-01-06 22:25 ` Ion Badulescu
2003-02-10 3:34 ` Testing new starfire driver for 2.5 Martin J. Bligh
2003-02-10 21:55 ` Ion Badulescu
2003-02-10 22:24 ` Martin J. Bligh
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=33980000.1041887671@flay \
--to=mbligh@aracnet.com \
--cc=ionut@badula.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.