From: "Kevin D. Kissell" <kevink@mips.com>
To: "Ian Thompson" <iant@palmchip.com>, <linux-mips@oss.sgi.com>
Subject: Re: dcache_blast() bug?
Date: Mon, 4 Jun 2001 21:18:39 +0200 [thread overview]
Message-ID: <02a901c0ed2b$2eac6300$0deca8c0@Ulysses> (raw)
In-Reply-To: 3B1BC6B8.C58758FA@palmchip.com
What processor are you running?
Kevin K.
----- Original Message -----
From: "Ian Thompson" <iant@palmchip.com>
To: <linux-mips@oss.sgi.com>
Sent: Monday, June 04, 2001 7:34 PM
Subject: dcache_blast() bug?
>
> Hi all,
>
> I'm seeing some odd memory behavior around the time when blast_dcache()
> is called, leading me to think that the method may be a little buggy.
> It appears that memory is being corrupted (consistently so) over the
> course of flushing the dcache. This happens to my command line argument
> string - arcs_cmdline. Before the blast_dcache() call, it is
> "console=ttyS0 ramdisk_start=0x9fcf0000 load_ramdisk=1", and after the
> call, the corrupted data is "ttyS0 ra0". I take it this isn't supposed
> to happen? any ideas of why the writeback_invalidate_d cache operation
> may be losing data?
>
> thanks,
> -ian
>
>
> --
> ----------------------------------------
> Ian Thompson tel: 408.952.2023
> Firmware Engineer fax: 408.570.0910
> Palmchip Corporation www.palmchip.com
WARNING: multiple messages have this Message-ID (diff)
From: "Kevin D. Kissell" <kevink@mips.com>
To: Ian Thompson <iant@palmchip.com>, linux-mips@oss.sgi.com
Subject: Re: dcache_blast() bug?
Date: Mon, 4 Jun 2001 21:18:39 +0200 [thread overview]
Message-ID: <02a901c0ed2b$2eac6300$0deca8c0@Ulysses> (raw)
Message-ID: <20010604191839.78UJajLrDFxcbYCtnGR-1_F9J0y36kJTkuvkE_MC7_I@z> (raw)
In-Reply-To: 3B1BC6B8.C58758FA@palmchip.com
What processor are you running?
Kevin K.
----- Original Message -----
From: "Ian Thompson" <iant@palmchip.com>
To: <linux-mips@oss.sgi.com>
Sent: Monday, June 04, 2001 7:34 PM
Subject: dcache_blast() bug?
>
> Hi all,
>
> I'm seeing some odd memory behavior around the time when blast_dcache()
> is called, leading me to think that the method may be a little buggy.
> It appears that memory is being corrupted (consistently so) over the
> course of flushing the dcache. This happens to my command line argument
> string - arcs_cmdline. Before the blast_dcache() call, it is
> "console=ttyS0 ramdisk_start=0x9fcf0000 load_ramdisk=1", and after the
> call, the corrupted data is "ttyS0 ra0". I take it this isn't supposed
> to happen? any ideas of why the writeback_invalidate_d cache operation
> may be losing data?
>
> thanks,
> -ian
>
>
> --
> ----------------------------------------
> Ian Thompson tel: 408.952.2023
> Firmware Engineer fax: 408.570.0910
> Palmchip Corporation www.palmchip.com
next prev parent reply other threads:[~2001-06-04 19:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-04 17:34 dcache_blast() bug? Ian Thompson
2001-06-04 19:18 ` Kevin D. Kissell [this message]
2001-06-04 19:18 ` Kevin D. Kissell
2001-06-04 20:27 ` Ian Thompson
2001-06-04 21:21 ` Kevin D. Kissell
2001-06-04 21:21 ` Kevin D. Kissell
2001-06-04 23:33 ` Ian Thompson
2001-06-05 8:50 ` Kevin D. Kissell
2001-06-05 8:50 ` Kevin D. Kissell
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='02a901c0ed2b$2eac6300$0deca8c0@Ulysses' \
--to=kevink@mips.com \
--cc=iant@palmchip.com \
--cc=linux-mips@oss.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