From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Jeff Dike <jdike@addtoit.com>,
User-mode-linux-devel
<User-mode-linux-devel@lists.sourceforge.net>
Subject: [uml-devel] problems with UML, issues with includes
Date: Mon, 01 Mar 2004 17:07:38 -0500 [thread overview]
Message-ID: <4043B42A.10803@nortelnetworks.com> (raw)
I'm having issues with UML.
I've got a rootfs that used to work with an older UML. With 2.4.24, I
try and boot with the following arguments:
./linux-2.4.24 mem=256M con0=fd:0,fd:1 con=pts ubd0=test,rootfs debug
msp_view=build_neptune_2.0_int11
The msp_view thing causes additional mounts to be created at init time.
However, I get a bunch of errors in my console window when I try to
log in:
ed Hat Linux release 8.0 (Psyche)
Plankton/CELP 2.5.0 - Kernel 2.4.24-1um on an i686
(none) login: Registering fd 47 twice
Irqs : 3, 3
Ids : 0xa022c3f8, 0xa022c3f8
Registering fd 47 twice
Irqs : 3, 3
Ids : 0xa022c3f8, 0xa022c3f8
If I then keep going, I end up with a whole bunch of lines like:
Failed to forward -1359446016 to pid 16452, err = 9
As part of my efforts to try and debug this, I wanted to dump out the
names of the processes that were calling os_set_owner(). Accordingly in
um/os/file.c I included <linux/sched.c> and wrote some code with
appropriate locking around the tasklist_lock so that I could match the
pid against the process name.
When I compiled, it grabbed the sched.h from /usr/include rather than
from the kernel build, and everything blew up.
So I guess I'm asking for help on two fronts. 1) How do I fix the build
process to pick up the kernel includes (and why doesn't it do that by
default?). 2) Any ideas why I'm getting the descriptor thing?
Thanks,
Chris
--
Chris Friesen | MailStop: 043/33/F10
Nortel Networks | work: (613) 765-0557
3500 Carling Avenue | fax: (613) 765-2986
Nepean, ON K2H 8E9 Canada | email: cfriesen@nortelnetworks.com
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next reply other threads:[~2004-03-01 22:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-01 22:07 Chris Friesen [this message]
2004-03-02 1:00 ` [uml-devel] Re: problems with UML, issues with includes Jeff Dike
2004-03-02 15:08 ` Chris Friesen
2004-03-02 18:06 ` BlaisorBlade
2004-03-02 20:54 ` Jeff Dike
2004-03-02 22:26 ` Chris Friesen
2004-03-02 23:22 ` Jeff Dike
2004-03-02 23:18 ` Chris Friesen
2004-03-02 23:37 ` [uml-devel] Re: problems with UML -- new data with memory debugging on Chris Friesen
2004-03-03 1:33 ` Jeff Dike
2004-03-03 16:49 ` Chris Friesen
2004-03-08 21:34 ` Jeff Dike
2004-03-08 21:08 ` Chris Friesen
2004-03-02 23:03 ` [uml-devel] Re: problems with UML, issues with includes Chris Friesen
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=4043B42A.10803@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=User-mode-linux-devel@lists.sourceforge.net \
--cc=jdike@addtoit.com \
/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.