All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: rf@q-leap.de
Cc: linux-kernel@vger.kernel.org, marcelo.tosatti@cyclades.com
Subject: Re: Trouble with swiotlb
Date: Fri, 03 Dec 2004 16:07:49 -0800	[thread overview]
Message-ID: <41B0FFD5.40401@osdl.org> (raw)
In-Reply-To: <16817.739.384632.576205@gargle.gargle.HOWL>

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?   :)


> Roland
>  
> linux-2428-work
> <description>
> 
> Signed-off-by: Your Name <email@domain.tld>
> 
> diffstat:=
>  arch/x86_64/kernel/setup.c |    1 +
>  1 files changed, 1 insertion(+)
> 
> diff -Naurp ./arch/x86_64/kernel/setup.c~swiotlb ./arch/x86_64/kernel/setup.c
> --- ./arch/x86_64/kernel/setup.c~swiotlb	2004-08-07 16:26:04.000000000 -0700
> +++ ./arch/x86_64/kernel/setup.c	2004-12-03 11:54:07.000000000 -0800
> @@ -52,6 +52,7 @@ int acpi_disabled;
>  EXPORT_SYMBOL(acpi_disabled);
>  
>  int swiotlb;
> +EXPORT_SYMBOL(swiotlb);
>  
>  extern	int phys_proc_id[NR_CPUS];


-- 
~Randy

  reply	other threads:[~2004-12-04  0:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-03 14:26 Trouble with swiotlb Roland Fehrenbacher
2004-12-03 21:36 ` Randy.Dunlap
2004-12-04  0:20   ` Roland Fehrenbacher
2004-12-04  0:07     ` Randy.Dunlap [this message]
2004-12-03 23:23       ` Marcelo Tosatti

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=41B0FFD5.40401@osdl.org \
    --to=rddunlap@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.