From: TheNop <TheNop@gmx.net>
To: linux-mips@linux-mips.org
Subject: Re: Kernel crash on yosemite
Date: Tue, 08 Feb 2005 08:20:38 +0100 [thread overview]
Message-ID: <42086846.9060709@gmx.net> (raw)
In-Reply-To: <42082C2C.5020703@mvista.com>
Hi,
I'm sorry, but all the discussion on this thread did'n help me to solve
my problem. Since more than a month I'm waitig to get a yosemite board
with 1.2 version. This still stops my development, when I can't use the
yosemite with 1.1 version.
In another therad we discuss to create a patch (slowpath) for the titan
version 1.1. the patch I apply to the the newer kernel sources
(2.6.11.rc1) but, I have the same problems. So I think the problem could
be the slowpath thing.
Have anybody an idee how to figure out what could be the problem when I
make "cp foo foo1" (foo is a lage file ~3,5 Mb)?
Best regards
TheNop
Manish Lachwani wrote:
> Ralf Baechle wrote:
>
>> On Mon, Feb 07, 2005 at 06:02:08PM -0800, Manish Lachwani wrote:
>>
>>
>>
>>> I completely agree. In any case, I dont think the CVS sources ever
>>> supported SMP for Titan < 1.2, correct?
>>>
>>
>>
>> No, that would have either meant taking a heavy performance penalty or
>> hacking mm in very ugly ways.
>
>
> How would I not know this? After all, I was the one who actually put
> this code together to get SMP to work on Titan 1.0 and 1.1, remember?
> ;) And you are right, there is no reason to put such hacks.
>
> Manish Lachwani
>
>
>> And due to the probably low numbers of
>> the early silicon and the availability of later revisions the reason
>> for such hacks was low anyway.
>>
>> Ralf
>>
>>
>>
>
>
>
>
next prev parent reply other threads:[~2005-02-08 7:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-07 22:53 Kernel crash on yosemite TheNop
2005-02-08 1:30 ` Ralf Baechle
2005-02-08 1:47 ` Manish Lachwani
2005-02-08 1:51 ` Ralf Baechle
2005-02-08 2:02 ` Manish Lachwani
2005-02-08 2:33 ` Ralf Baechle
2005-02-08 3:04 ` Manish Lachwani
2005-02-08 7:20 ` TheNop [this message]
2005-02-08 10:54 ` 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=42086846.9060709@gmx.net \
--to=thenop@gmx.net \
--cc=linux-mips@linux-mips.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox