* 2.6.13-rc: ACPI_INTERPRETER=y, PCI=n compile error
@ 2005-08-24 14:44 Adrian Bunk
0 siblings, 0 replies; 3+ messages in thread
From: Adrian Bunk @ 2005-08-24 14:44 UTC (permalink / raw)
To: David Shaohua Li, Len Brown; +Cc: acpi-devel, linux-kernel
I got the following compile error in 2.6.13-rc6-mm2, but it seems to be
a problem coming from Linus' tree introduced by the
[ACPI] S3 resume: avoid kmalloc() might_sleep oops symptom
patch:
<-- snip -->
...
LD .tmp_vmlinux1
drivers/built-in.o: In function `acpi_os_allocate':
: undefined reference to `acpi_in_resume'
make: *** [.tmp_vmlinux1] Error 1
<-- snip -->
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
^ permalink raw reply [flat|nested] 3+ messages in thread
* RE: 2.6.13-rc: ACPI_INTERPRETER=y, PCI=n compile error
@ 2005-08-24 15:13 Brown, Len
2005-08-24 15:30 ` Adrian Bunk
0 siblings, 1 reply; 3+ messages in thread
From: Brown, Len @ 2005-08-24 15:13 UTC (permalink / raw)
To: Adrian Bunk, Li, Shaohua; +Cc: acpi-devel, linux-kernel
>Subject: 2.6.13-rc: ACPI_INTERPRETER=y, PCI=n compile error
>
>I got the following compile error in 2.6.13-rc6-mm2, but it
>seems to be
>a problem coming from Linus' tree introduced by the
> [ACPI] S3 resume: avoid kmalloc() might_sleep oops symptom
>patch:
>
><-- snip -->
>
>...
> LD .tmp_vmlinux1
>drivers/built-in.o: In function `acpi_os_allocate':
>: undefined reference to `acpi_in_resume'
>make: *** [.tmp_vmlinux1] Error 1
>
><-- snip -->
Do you have an ACPI-enabled machine that has no PCI?
I'm not aware of any, and would be interested to know
if one exists.
We've had problems with this theoretical build config
for some time:
http://bugzilla.kernel.org/show_bug.cgi?id=1364
because nobody, including me, tests it.
Indeed, one possible fix would be to make CONFIG_ACPI
depend on CONFIG_PCI -- which brings me back to
my origianl question.
-Len
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: 2.6.13-rc: ACPI_INTERPRETER=y, PCI=n compile error
2005-08-24 15:13 2.6.13-rc: ACPI_INTERPRETER=y, PCI=n compile error Brown, Len
@ 2005-08-24 15:30 ` Adrian Bunk
0 siblings, 0 replies; 3+ messages in thread
From: Adrian Bunk @ 2005-08-24 15:30 UTC (permalink / raw)
To: Brown, Len; +Cc: Li, Shaohua, acpi-devel, linux-kernel
On Wed, Aug 24, 2005 at 11:13:05AM -0400, Brown, Len wrote:
>
> >Subject: 2.6.13-rc: ACPI_INTERPRETER=y, PCI=n compile error
> >
> >I got the following compile error in 2.6.13-rc6-mm2, but it
> >seems to be
> >a problem coming from Linus' tree introduced by the
> > [ACPI] S3 resume: avoid kmalloc() might_sleep oops symptom
> >patch:
> >
> ><-- snip -->
> >
> >...
> > LD .tmp_vmlinux1
> >drivers/built-in.o: In function `acpi_os_allocate':
> >: undefined reference to `acpi_in_resume'
> >make: *** [.tmp_vmlinux1] Error 1
> >
> ><-- snip -->
>
> Do you have an ACPI-enabled machine that has no PCI?
> I'm not aware of any, and would be interested to know
> if one exists.
No, I don't have one.
> We've had problems with this theoretical build config
> for some time:
> http://bugzilla.kernel.org/show_bug.cgi?id=1364
> because nobody, including me, tests it.
>
> Indeed, one possible fix would be to make CONFIG_ACPI
> depend on CONFIG_PCI -- which brings me back to
> my origianl question.
Making ACPI dependent on PCI is a possible solution for this problem.
> -Len
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2005-08-24 15:30 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-08-24 15:13 2.6.13-rc: ACPI_INTERPRETER=y, PCI=n compile error Brown, Len
2005-08-24 15:30 ` Adrian Bunk
-- strict thread matches above, loose matches on Subject: below --
2005-08-24 14:44 Adrian Bunk
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox