From: Ingo Rohloff <lundril@gmx.net>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Problems with NFS in 2.4test10
Date: Sat, 11 Nov 2000 18:35:36 +0000 [thread overview]
Message-ID: <20001111183536.A758@flashline.chipnet> (raw)
In-Reply-To: <20001109215045.A591@flashline.chipnet> <3A0B2FAB.334D36BC@asiapacificm01.nt.com> <3A0B30F3.FA703FAD@mandrakesoft.com>
In-Reply-To: <3A0B30F3.FA703FAD@mandrakesoft.com>; from Jeff Garzik on Thu, Nov 09, 2000 at 06:19:15PM -0500
> Ingo, do you have a BP6? Make sure you have the latest BIOS for your
> motherboard, there have been many BIOS updates for some dual-Celeron
> motherboards.
I have to admit that I'm not sure what kind of dual board I got
(i have to have a closer look).
The reason is that this board is orgiginally for dual Pentium IIs.
I got two Celerons (in S370 format), and use two modified
MSI S370-to-Slot1 adaptor (aehm I hope I got this right)
cards to make the Celerons multiprocessor enabled.
I still think it is an 2.4test10 kernel issue, because
my machine won't crash (as far as I can tell) if I use
2.2.17.
(Am I correct that 2.4test10 is a lot more fine granular threaded
in the kernel than 2.2.17 ?
If this is true I suspect that there is some kind of
race/deadlock situtation in the NFS code...
)
so long
Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2000-11-11 16:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-09 21:50 Problems with NFS in 2.4test10 Ingo Rohloff
[not found] ` <3A0B2FAB.334D36BC@asiapacificm01.nt.com>
[not found] ` <3A0B30F3.FA703FAD@mandrakesoft.com>
2000-11-11 18:35 ` Ingo Rohloff [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=20001111183536.A758@flashline.chipnet \
--to=lundril@gmx.net \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.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