From: Mike Shaver <shaver@netscape.com>
To: linux@cthulhu.engr.sgi.com
Subject: flush_cache_all() hoses my Indy
Date: Mon, 22 Dec 1997 01:15:59 -0800 [thread overview]
Message-ID: <349E2FCF.605C2665@netscape.com> (raw)
OK, I've been tracking a bug that only seems to appear on the Indy I
have at home right now (belongs to the housemates). After sgiseeq_init
allocates the ring buffers, it calls flush_cache_all(). On this system,
that zeroes out the ring buffer pointers (rx and tx -- likely the entire
dev->priv block and more) and then setup_tx_ring gets understandably
upset. =)
Anyway, I'm not enough of a MIPS guru to really say much more, but I'll
poke around tonight and see if I can stumble across anything useful.
Linux reports:
MIPS 4400 FPU<MIPS-R4400FPC> ICACHE DCACHE SCACHE
CPU Revision 0460
hinv tells me:
1 200 MHZ IP22 Processor
FPU: MIPS R4000 Floating Point Coprocessor Revision: 0.0
CPU: MIPS R4400 Processor Chip Revision: 6.0
Instruction cache size: 16 Kbytes
Data cache size: 16 Kbytes
More than this I do not know, but I'll run any test that doesn't risk
permanent damage.
Mike
next reply other threads:[~1997-12-22 9:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-22 9:15 Mike Shaver [this message]
1997-12-22 20:45 ` flush_cache_all() hoses my Indy Ralf Baechle
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=349E2FCF.605C2665@netscape.com \
--to=shaver@netscape.com \
--cc=linux@cthulhu.engr.sgi.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