On Sat, May 05, 2001 at 04:04:27PM -0700, Archie Cobbs wrote:
> Jonathan Lemon writes:
> > >Please consider the case where there are two mbuf chains being
> > >transmitted, which look like this:
> >
> > Um. "Not Possible".
>
> I thought m_copypacket() of a cluster mbuf would yield exactly
> t
Jonathan Lemon writes:
> >Please consider the case where there are two mbuf chains being
> >transmitted, which look like this:
>
> Um. "Not Possible".
I thought m_copypacket() of a cluster mbuf would yield exactly
this situation (two headers pointing to the same data region).
-Arcihe
__
In article [EMAIL PROTECTED]> you
write:
>] I would be quite interested in knowing just how you manage
>] to accomplish that, given that all the transmit control buffers
>] are arranged in a circular linked list:
>]
>] fxp_init(void *xsc)
>] {
>] ...
>] for (i = 0
] I would be quite interested in knowing just how you manage
] to accomplish that, given that all the transmit control buffers
] are arranged in a circular linked list:
]
] fxp_init(void *xsc)
] {
] ...
] for (i = 0; i < FXP_NTXCB; i++) {
] ...
In article [EMAIL PROTECTED]> you
write:
>The fxp driver is broken in a lot of places.
>
>For example, in fxp_intr():
>
>for (txp = sc->cbl_first; sc->tx_queued &&
>(txp->cb_status & FXP_CB_STATUS_C) != 0;
>txp = txp-
The fxp driver is broken in a lot of places.
For example, in fxp_intr():
for (txp = sc->cbl_first; sc->tx_queued &&
(txp->cb_status & FXP_CB_STATUS_C) != 0;
txp = txp->next) {
if (txp-
On Tue, May 01, 2001 at 02:16:33PM -0700, Peter Wemm wrote:
> On the other hand,
> you might try using dwarf2 debugging, that is pretty complete.
And what we'll be using when GCC 3.0 is imported.
--
-- David ([EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe
"Kenneth D. Merry" wrote:
> It looks like the mbuf pointer is bogus:
>
> (kgdb) print m
> $2 = (struct mbuf *) 0xf0006b00
> (kgdb) print *m
> Cannot access memory at address 0xf0006b00.
>
> Although in the next frame up the stack, the mbuf pointer looks okay:
>
> (kgdb) up
> #1 0xc018ef76 in
I'm updating a machine (Pentium II 350, 128MB RAM) to -current, and ran
into this panic in the fxp driver. Sources are from today (5/1/2001).
I believe the chip is an 82557.
I compiled and installed a kernel, rebooted and started running an
installworld over NFS. The installworld stopped here:
