From: Alexander Puchmayr <alexander.puchmayr@linznet.at>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Kernel freezes
Date: Sat, 6 Jun 2009 12:42:38 +0200 [thread overview]
Message-ID: <200906061242.38397.alexander.puchmayr@linznet.at> (raw)
In-Reply-To: <200906061112.47241.volkerarmin@googlemail.com>
Am Samstag 06 Juni 2009 schrieb Volker Armin Hemmann:
> *sigh* Ok, just for starters - all AMD cpus of the Athlon64 architecture
> have a builtin agpgart. This agpgart functions also as an iommu. This is
> a great hack to have a hardware iommu . Intel does not have this, so they
> rely on software. The solution came up while AMD devs and linux kernel
> devs worked together.
> Please read the following links:
>
> http://en.wikipedia.org/wiki/Iommu
>
> http://marc.info/?l=linux-kernel&m=107759901509280&w=2
>
> http://marc.info/?l=linux-kernel&m=107764033904042&w=2
>
> the iommu is needed so 32bit pci devices can live with their pci adress
> space behind 4gb and other sweet things.
>
> Sadly the iommu needs a minimum on memory for itself - and uses the agp-
> aperture. This is fine, but mobo vendors suck and make it too small/or
> not available. In that case the kernel is forced to use real memory for
> the iommu.
>
> In short, that message has nothing to do with your problem.
>
Thanks for these informative links
> The NR_CPU message is confusing - I strongly suspect that your kernel
> config is really fucked uo.
?? As I have a DualCore-Cpu, I changed NR_CPU to 2, something wrong with
that? What else can be fucked up? I Enabled Multi-core scheduler
(hyperthread is disabled)
>
> Please enable:
>
> [] Check for low memory corruption
> [] Reserve low 64K of RAM on AMI/Phoenix BIOSen
>
> in the kernel config. Also clean it up and remove stuff like
> 'hyperthreading scheduler'.
>
Already done.
> If the problem persists, start testing your hardware.
>
How? I don't have access to special test equipment to test hardware. This is
the only AM2(+) board and the only AM2 CPU I have. The RAM is also unique
to this machine.
> I would suspect the PSU.
The Powersupply? What makes you think that the PSU can be the cause of a
system crash?
Greetings
Alex
next prev parent reply other threads:[~2009-06-06 10:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-06 8:33 [gentoo-user] Kernel freezes Alexander Puchmayr
2009-06-06 9:12 ` Volker Armin Hemmann
2009-06-06 10:42 ` Alexander Puchmayr [this message]
2009-06-06 11:02 ` Volker Armin Hemmann
2009-06-06 13:49 ` Alexander Puchmayr
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=200906061242.38397.alexander.puchmayr@linznet.at \
--to=alexander.puchmayr@linznet.at \
--cc=gentoo-user@lists.gentoo.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