public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64]  Re: 2.6.16 and >=4G mem
Date: Wed, 29 Mar 2006 09:14:55 -0700	[thread overview]
Message-ID: <pan.2006.03.29.16.14.55.180160@cox.net> (raw)
In-Reply-To: pan.2006.03.26.10.34.46.613270@cox.net

Duncan posted <pan.2006.03.26.10.34.46.613270@cox.net>, excerpted below, 
on Sun, 26 Mar 2006 03:34:47 -0700:

> With kernel 2.6.15, configuring IOMMU won't let me boot (without a mem=
> kernel command line).  Configuring it in but forcing it off (iommu=off on
> the kernel command line) gives me some IOMMU needed errors and it still
> won't boot (again, without a mem=).  Configuring it out, the system boots
> just fine.
> 
> With kernel 2.6.16, configuring IOMMU in or out, on or off, won't boot
> (without a mem=).

For those that may be interested, I think I may have a defective hardware
IOMMU.  Setting iommu=soft on the kernel command line works just fine. 
That's a bit disappointing for AMD hardware, where the hardware IOMMU is
supposed to be better, but I guess it's no worse than the Intel chips,
which don't have an IOMMU so emulate it in software.

It's still fairly likely that I have something not quite configured
correctly, however, and that when I figure it out, it'll work the  way
it's supposed to.  I have some research to do tho, to grok that. 
Meanwhile, with the iommu=soft switch, I can run 2.6.16 kernels with full
memory, just as I could .15 kernels.  (The .15 and apparently earlier
kernels had bounce-buffers built-in for SCSI, while .16 took them out
since there's the IOMMU in either software for Intel, or hardware for
normal AMD, anyway.)

BTW, merged KDE 3.5.2 last nite, upgraded from 3.5.1.  That's the first
time I've run a major emerge session with $PORTAGE_TMPDIR on a RAM backed
tmpfs.  VERY NICE! =8^)  I /still/ haven't used the full 8 gigabit yet,
tho.  I got upto 6.5-ish when kmail was compiling, with four other compile
jobs running in parallel (5 total), each of which was running
MAKEOPTS="-j6 -l5".  The -l5 limited load some, and KDE doesn't make as
good a use of multiple compile jobs as it could (the reason I was running
5 in parallel since the -j6 -l5 doesn't work so well with KDE), but I
/was/ running 7-10 load average for several hours (on a dual Opteron 242).
Hopefully by the time I'm compiling KDE4, I'll be doing it with dual
cores, a bit faster than the 1.6 GHz of the Opteron 242s, as well.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman in
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html


-- 
gentoo-amd64@gentoo.org mailing list



  reply	other threads:[~2006-03-29 16:18 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-25 14:35 [gentoo-amd64] 2.6.16 and ndiswrapper Mark Haney
2006-03-25 17:22 ` Beso
2006-03-25 18:46   ` [gentoo-amd64] " Michael Rock
2006-03-25 19:53     ` Mark Haney
2006-03-30 15:44       ` Karol Krizka
2006-03-25 19:52   ` [gentoo-amd64] " Mark Haney
2006-03-25 20:13   ` [gentoo-amd64] " Duncan
2006-03-25 20:27     ` Mark Haney
2006-03-25 23:12       ` [gentoo-amd64] " Duncan
2006-03-25 20:57 ` [gentoo-amd64] " Karol Krizka
2006-03-25 23:37   ` [gentoo-amd64] " Duncan
2006-03-25 23:58     ` Boyd Stephen Smith Jr.
2006-03-26  2:27       ` xcourse97
2006-03-26  2:59         ` Boyd Stephen Smith Jr.
2006-03-26 10:34           ` Beso
2006-03-28 11:31             ` Arvid Norlander
2006-03-26 10:34       ` [gentoo-amd64] Re: 2.6.16 and >=4G mem (was ndiswrapper) Duncan
2006-03-29 16:14         ` Duncan [this message]
2006-03-29 18:52           ` [gentoo-amd64] Re: 2.6.16 and >=4G mem JimD
2006-03-29 19:41             ` [gentoo-amd64] " Duncan

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=pan.2006.03.29.16.14.55.180160@cox.net \
    --to=1i5t5.duncan@cox.net \
    --cc=gentoo-amd64@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