From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: rf@q-leap.de, linux-kernel@vger.kernel.org
Subject: Re: Trouble with swiotlb
Date: Fri, 3 Dec 2004 21:23:51 -0200 [thread overview]
Message-ID: <20041203232351.GB3289@dmt.cyclades> (raw)
In-Reply-To: <41B0FFD5.40401@osdl.org>
On Fri, Dec 03, 2004 at 04:07:49PM -0800, Randy.Dunlap wrote:
> Roland Fehrenbacher wrote:
> >>>>>>"Randy" == Randy Dunlap <Randy.Dunlap> writes:
> >
> >
> > Randy> Roland Fehrenbacher wrote:
> > >> Hi,
> > >>
> > >> when building 2.4.28 or 2.4.27 on x86_64 with IOMMU and SWIOTLB
> > >> support enabled I get unresolved symbol for 3 modules:
> > >>
> > >> depmod: *** Unresolved symbols in
> > >> /lib/modules/2.4.28/kernel/drivers/net/e1000/e1000.o depmod:
> > >> *** Unresolved symbols in
> > >> /lib/modules/2.4.28/kernel/drivers/usb/host/uhci.o depmod: ***
> > >> Unresolved symbols in
> > >> /lib/modules/2.4.28/kernel/drivers/usb/host/usb-uhci.o
> > >>
> > >> When modprobing any of the modules I get: unresolved symbol
> > >> swiotlb
> > >>
> > >> The kernel boots fine on Opterons and EM64T Xeons otherwise.
> > >>
> > >> Any ideas.
> >
> > Randy> Looks like it just needs 'swiotlb' exported (as in 2.6.x).
> > Randy> Can you test the attached patch? I don't have 2.4.x
> > Randy> booting on x8-64 yet.
> >
> >Hi Randy,
> >
> >thanks for the fast reply. Your patch solved the problem. I can boot
> >Opterons and EM64T Xeons now without any problems.
>
> Thanks for the results. Marcelo, can you rip out my garbaged patch
> header/description before applying it? :)
Done - thanks Randy.
prev parent reply other threads:[~2004-12-04 5:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-03 14:26 Roland Fehrenbacher
2004-12-03 21:36 ` Randy.Dunlap
2004-12-04 0:20 ` Roland Fehrenbacher
2004-12-04 0:07 ` Randy.Dunlap
2004-12-03 23:23 ` Marcelo Tosatti [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=20041203232351.GB3289@dmt.cyclades \
--to=marcelo.tosatti@cyclades.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
--cc=rf@q-leap.de \
/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
all inboxes | Powered by JetHome®