From: Andi Kleen <ak@muc.de>
To: Linus Torvalds <torvalds@osdl.org>
Cc: linux-kernel@vger.kernel.org, techsupport@tyan.com,
support@tyan.de, Andrew Morton <akpm@osdl.org>,
gl@fenedex.nl, land@hetlageland.nl, hans@sww.nl, sww@sww.nl
Subject: Re: Tyan Opteron boards and problems with parallel ports
Date: Wed, 25 May 2005 18:50:03 +0200 [thread overview]
Message-ID: <m1r7fvxnb8.fsf@muc.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0505191727030.2322@ppc970.osdl.org> (Linus Torvalds's message of "Thu, 19 May 2005 17:34:49 -0700 (PDT)")
Linus Torvalds <torvalds@osdl.org> writes:
> On Fri, 20 May 2005, Robert M. Stockmann wrote:
>>
>> All problems of Tyan Opteron based machines silently locking up during
>> installation and/or during normal operation of running Linux, both
>> 32bit and 64bit, without any display of kernel panic of any other
>> logging method, seem to be solved when switching off the Parallel Port
>> inside its BIOS.
The common Tyan problem case is when the machine has more than 3GB
of RAM and "memory remapping" is enabled to recover the memory
below the PCI memory hole. SOmething in that setup leads
to problems and random memory corruption. I suspect a BIOS bug
here.
Workaround is to not enable that option in the BIOS setup.
Then another older Tyan board (it might have been the K8W)
was *extremly* picky in what DIMMs it accepted and in what
slots because someone apparently didnt follow the AMD specification for
the memory controller trace lines fully. That also caused common problems.
> Can you do an install with the thing turned off, and then
> - compile the kernel with CONFIG_PCI_DEBUG
> - boot with the parallel port enabled, and send as much of the bootup
> output (and /proc/iomem and /proc/ioport) as possible
> - boot with the parallel port disabled, and send the same output for that
> working case.
>
> I have no clue why the parallel port should matter, but it could change
> some resource allocation issues.
It is the first time I heard about such a issue so it cannot be too
wide spread anyways.
-Andi
next prev parent reply other threads:[~2005-05-25 16:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-20 0:16 Tyan Opteron boards and problems with parallel ports Robert M. Stockmann
2005-05-20 0:34 ` Linus Torvalds
2005-05-25 16:50 ` Andi Kleen [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-25 17:15 YhLu
2005-05-25 20:45 ` Peter J. Stieber
2005-05-26 15:23 ` Bill Davidsen
2005-05-26 20:40 ` Peter J. Stieber
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=m1r7fvxnb8.fsf@muc.de \
--to=ak@muc.de \
--cc=akpm@osdl.org \
--cc=gl@fenedex.nl \
--cc=hans@sww.nl \
--cc=land@hetlageland.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=support@tyan.de \
--cc=sww@sww.nl \
--cc=techsupport@tyan.com \
--cc=torvalds@osdl.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