From: Andy Lutomirski <luto@myrealbox.com>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: Hans-Frieder Vogt <hfvogt@arcor.de>,
linux-kernel@vger.kernel.org, jgarzik@pobox.com,
netdev@oss.sgi.com
Subject: Re: 2.6.9-rc1-bk11+ and 2.6.9-rc1-mm3,4 r8169: freeze during boot (FIX included)
Date: Sun, 19 Sep 2004 14:17:39 -0700 [thread overview]
Message-ID: <414DF773.7060402@myrealbox.com> (raw)
In-Reply-To: <20040917160151.GA29337@electric-eye.fr.zoreil.com>
Francois Romieu wrote:
> Jon Mason <jdmason@us.ibm.com> :
> [...]
>
>>Before I make any sweeping comments about the performance on ppc64, I should
>>probably do some more tests. I'll have to get back to you regarding that.
>>
>>Would you like me to run the "Config2" patch on my amd64 system?
>
>
> Please do. If I read you correctly, 2.6.9-rc2-bkX works (more or less)
> on both your ppc64 and amd64 systems, right ?
No, still broken. But I don't see any change at all in 2.6.9-rc2-bk5.
This is on amd64, with 32-bit slots (I think).
BTW, the crash is not immediate. It takes several seconds after trying
to send/recieve.
I say _trying_ because I can't ping anything. I haven't had time before
the crash to figure out what's wrong, but the device at the other end
does flash that a packet came through the wire.
FWIW, it looks like init_board is setting PCIDAC in tp->cp_cmd but that
isn't updated to the card until after the rx ring is filled in
r8169_open. This seems suspicious, since DMA memory is being allocated
possibly in >32-bit addresses but the card hasn't been told to support
that. Fixing this doesn't seem to help, though...
Turning off high DMA fixes it. Maybe it just needs to be disabled until
someone figures out what's going on.
--Andy
next prev parent reply other threads:[~2004-09-19 21:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200409130035.50823.hfvogt@arcor.de>
[not found] ` <20040912232604.GC27282@electric-eye.fr.zoreil.com>
2004-09-13 12:43 ` 2.6.9-rc1-bk11+ and 2.6.9-rc1-mm3,4 r8169: freeze during boot (FIX included) Hans-Frieder Vogt
2004-09-13 22:02 ` Francois Romieu
2004-09-13 23:31 ` Hans-Frieder Vogt
2004-09-15 22:40 ` Hans-Frieder Vogt
2004-09-15 23:09 ` Francois Romieu
2004-09-15 23:32 ` Hans-Frieder Vogt
2004-09-16 7:02 ` Francois Romieu
2004-09-16 18:20 ` Jon Mason
2004-09-17 15:43 ` Jon Mason
2004-09-17 16:01 ` Francois Romieu
2004-09-19 21:17 ` Andy Lutomirski [this message]
2004-09-19 21:39 ` Francois Romieu
2004-09-19 23:51 ` Andy Lutomirski
2004-09-20 2:56 ` Jeff Garzik
2004-09-20 7:17 ` Francois Romieu
2004-09-20 17:59 ` Jeff Garzik
2004-09-20 21:15 ` Francois Romieu
2004-09-20 16:06 ` Jon Mason
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=414DF773.7060402@myrealbox.com \
--to=luto@myrealbox.com \
--cc=hfvogt@arcor.de \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=romieu@fr.zoreil.com \
/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;
as well as URLs for NNTP newsgroup(s).