From: William Lee Irwin III <wli@holomorphy.com>
To: jds <jds@soltis.cc>
Cc: linux-kernel@vger.kernel.org
Subject: Re: busy_loop in compile kernel 2.5.68-mm2
Date: Thu, 24 Apr 2003 20:14:59 -0700 [thread overview]
Message-ID: <20030425031459.GR8978@holomorphy.com> (raw)
In-Reply-To: <20030425022510.M26474@soltis.cc>
On Thu, Apr 24, 2003 at 08:28:12PM -0600, jds wrote:
> I have problems when compile kernel 2.5.68-mm2 the message is:
> make -f scripts/Makefile.build obj=net/unix
[...]
> arch/i386/pci/built-in.o net/built-in.o --end-group -o .tmp_vmlinux1
> drivers/built-in.o(.text+0x9d70b): In function `busy_loop':
> : undefined reference to `save_flags'
> drivers/built-in.o(.text+0x9d710): In function `busy_loop':
> : undefined reference to `sti'
> drivers/built-in.o(.text+0x9d72d): In function `busy_loop':
> : undefined reference to `restore_flags'
> make: *** [.tmp_vmlinux1] Error 1
> Help me please
> Regards
You have an SMP-unsafe driver configured.
A little birdy called grep(1) told me:
$ grep -nr busy_loop drivers
drivers/net/pcmcia/xirc2ps_cs.c:443:busy_loop(u_long len)
drivers/net/pcmcia/xirc2ps_cs.c:1788: busy_loop(HZ/25); /* wait 40 msec */
drivers/net/pcmcia/xirc2ps_cs.c:1793: busy_loop(HZ/50); /* wait 20 msec */
drivers/net/pcmcia/xirc2ps_cs.c:1807: busy_loop(HZ/50); /* wait 20 msec */
drivers/net/pcmcia/xirc2ps_cs.c:1809: busy_loop(HZ/25); /* wait 40 msec */
drivers/net/pcmcia/xirc2ps_cs.c:1820: busy_loop(HZ/2); /* about 500ms */
drivers/net/pcmcia/xirc2ps_cs.c:1839: busy_loop(HZ/25); /* wait 40 msec to let it complete */
drivers/net/pcmcia/xirc2ps_cs.c:1898: busy_loop(HZ/50);
drivers/net/pcmcia/xirc2ps_cs.c:1907: busy_loop(HZ/25); /* wait 40 msec to let it complete */
drivers/net/pcmcia/xirc2ps_cs.c:2000: busy_loop(HZ/10); /* wait 100 msec */
-- wli
prev parent reply other threads:[~2003-04-25 3:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-25 2:28 busy_loop in compile kernel 2.5.68-mm2 jds
2003-04-25 3:14 ` William Lee Irwin III [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=20030425031459.GR8978@holomorphy.com \
--to=wli@holomorphy.com \
--cc=jds@soltis.cc \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).