From: "Quintela Carreira Juan J." <quintela@fi.udc.es>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Rik van Riel <riel@conectiva.com.br>,
Lawrence Manning <lawrence@aslak.demon.co.uk>,
Linux Kernel <linux-kernel@vger.rutgers.edu>,
linux-mm@kvack.org
Subject: Re: Basic testing shows 2.3.99-pre9-3 bad, pre9-2 good
Date: 21 May 2000 21:32:04 +0200 [thread overview]
Message-ID: <yttn1ljaedn.fsf@serpe.mitica> (raw)
In-Reply-To: Linus Torvalds's message of "Sun, 21 May 2000 12:17:25 -0700 (PDT)"
>>>>> "linus" == Linus Torvalds <torvalds@transmeta.com> writes:
linus> On Sun, 21 May 2000, Rik van Riel wrote:
>> On Sun, 21 May 2000, Lawrence Manning wrote:
>>
>> > That's my observation anyway. I did some dd and bonnie tests
>> > and got abismal results :-( Machine unusable during dd write
>> > etc. pre9-2 on the other hand is close to being as smooth as,
>> > say, 2.3.51. What happened? ;)
linus> What happened was really that I did a partial integration just to make it
linus> easier to synchronize. I wanted to basically have pre9-2 + quintela's
linus> patch, but I had too many emails to go through and too many changes of my
linus> own in this area, so I made pre9-3 available so that others could help me
linus> synchronize.
linus> So on't despair, pre9-3 is definitely just a temporary mix of patches, and
linus> is lacking the balancing that Quintela did.
Hi Linus
I am working in introducing my balancing changes in pre9-3, but I
am having problems with it. Now my machines get deadlocked and I
get a lot of Oopses. I am investigating on that. I get Oops
indeed in the pre9-3 vanilla kernel. I am studying it to write a
report of the situation.
My SMP machine is new, It has passed 6 hours of memtest86 memory
checker, but I don't know what to blame at the moment. I am
compiling for my old UP machines to test the differences.
Later, Juan.
PD.
<advertising>
Yes I am having deadlocks, Conectiva (http://www.conectiva.com.br/)and
my department in the University (http://carpanta.dc.fi.udc.es/)
have bought me an SMP machine.
</advertising>
--
In theory, practice and theory are the same, but in practice they
are different -- Larry McVoy
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/
prev parent reply other threads:[~2000-05-21 19:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.10.10005211837310.627-100000@aslak.demon.co.uk>
2000-05-21 19:11 ` Basic testing shows 2.3.99-pre9-3 bad, pre9-2 good Rik van Riel
2000-05-21 19:17 ` Linus Torvalds
2000-05-21 19:32 ` Quintela Carreira Juan J. [this message]
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=yttn1ljaedn.fsf@serpe.mitica \
--to=quintela@fi.udc.es \
--cc=lawrence@aslak.demon.co.uk \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=riel@conectiva.com.br \
--cc=torvalds@transmeta.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.