From: anil dahiya <ak_ait@yahoo.com>
To: linux-kernel@vger.kernel.org, kernelnewbies@nl.linux.org
Subject: Badness in sleep_on_timeout on kernel 2.6.9-1.667 ( fedora core 3)
Date: Tue, 7 Feb 2006 12:00:13 -0800 (PST) [thread overview]
Message-ID: <20060207200013.30703.qmail@web60221.mail.yahoo.com> (raw)
Hello
I am creating kernel thread on fedora core 4
(2.6.9-1.667)and my getting oops something like
Badness in sleep_on_timeout at kernel/sched.c:3022
[<02302bc3>] sleep_on_timeout+0x5d/0x23a
[<0211b919>] default_wake_function+0x0/0xc
can any suggest how i can avoid this oops.
Regards,
Anil
--- anil dahiya <ak_ait@yahoo.com> wrote:
> Hi Sam
> Thanks fop your help ..but my problem is not solved
> it
> ...i putting my real problem here below.
>
> 1>my fist need is to make module1.ko made using
> a1/a1.c , a1/a11.c & a2/a2.c a2/a22.c and all .c
> file
> use /home/include/a.h
>
>
> 2>Now my 2nd need is to make module2.ko using
> module1.ko and b/b1.c & b/b11.c (these both .c files
> use /home/include/a.h and /home/module2/include/b.h)
>
>
> In short my directory structure is as:
>
> /home/------
> |_ include _
> | |
> | a.h
> |
> |___module1_
> | |__ a1 ____________
> | | | |
> | | a1.c a11.c
> | |
> |__ a2 ___________
> | | | |
> | | a2.c a22.c
> |
> |___ moudule2_
> | |
> | |__include _
> | | |
> | | b.h
> | |___b1________
> | | |
> | b1.c b11.c
>
>
> Looking forward for ur reply
> thanks in advance
> ---- Anil
>
>
> --- anil dahiya <ak_ait@yahoo.com> wrote:
>
> > hello
> > I want to make kernel module dummy.ko using
> multiple
> > .c and .h files. In short i am telling .c and .h
> > files
> > with directory structure
> >
> > 1> dummy.ko should made be using module1.ko and
> > module2.o (i.e
> > module2.o uses module1.ko to make dummy.ko)
> >
> > 2> module1.ko made using a1/a1.c & a2/a2.c and
> both
> > .c file
> > use /home/include/a.h
> > 3> module2.o should made using b/b1.c which use
> > use /home/module2/include/b.h
> >
> > Suggest me tht should make i make module2.o or
> > module2.ko and then combine it with module1.o to
> > make
> > dummy.ko
> >
> >
> > /home/------
> > |_ include _
> > | |
> > | a.h
> > |
> > |___module1_
> > | |__ a1 ____
> > | | |
> > | | a1.c
> > | |
> > |__ a2 ____
> > | | |
> > | | a2.c
> > |
> > |___ moudule2_
> > | |
> > | |__include _
> > | | |
> > | | b.h
> > | |___b1__
> > | |
> > | b1.c
> >
> >
> > Looking forward for ur reply
> > thanks in advance
> > ---- Anil
> >
> >
> >
> > __________________________________________
> > Yahoo! DSL Something to write home about.
> > Just $16.99/mo. or less.
> > dsl.yahoo.com
> >
> >
> > --
> > Kernelnewbies: Help each other learn about the
> Linux
> > kernel.
> > Archive:
> > http://mail.nl.linux.org/kernelnewbies/
> > FAQ: http://kernelnewbies.org/faq/
> >
> >
>
>
>
>
> __________________________________________
> Yahoo! DSL Something to write home about.
> Just $16.99/mo. or less.
> dsl.yahoo.com
>
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
next reply other threads:[~2006-02-07 20:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-07 20:00 anil dahiya [this message]
2006-02-07 21:50 ` David Woodhouse
2006-02-08 5:54 ` anil dahiya
2006-02-08 6:40 ` Gaurav Dhiman
2006-02-12 13:17 ` Arjan van de Ven
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=20060207200013.30703.qmail@web60221.mail.yahoo.com \
--to=ak_ait@yahoo.com \
--cc=kernelnewbies@nl.linux.org \
--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
all inboxes | Powered by JetHome®