From: Kip Macy <kmacy@fsmware.com>
To: Ian Pratt <Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel@lists.sourceforge.net
Subject: Re: problems with latest unstable
Date: Tue, 27 Apr 2004 18:24:28 -0700 (PDT) [thread overview]
Message-ID: <20040427181626.I31878@demos.bsdclusters.com> (raw)
In-Reply-To: <E1BIcvy-000260-00@mta1.cl.cam.ac.uk>
>
> What compiler are you using?
gcc 3.3.2 - I just recompiled a non-debug xen with Fedora's stock gcc
instead of one that I had compiled. It works fine for the moment, but
I haven't been running it for very long.
>
> The lack of DOM0 output with the non debug build suggests that
> Linux is dieing before its got the console subsystem up (which
> happens annoyingly late in the init sequence.
I may just be passing the wrong parameter to grub, com1 is what is
mentioned in the HOWTO, that doesn't appear to be correct.
>
> To get around this, I often add a
> 'HYPERVISOR_console_write(printk_buf, sizeof(printk_buf)' to
> printk in kernel/printk.c
If futzing with the parameters doesn't work I'll do that.
> Hmm. This may suggest that Fedora has yet another sick and
> twisted way of abusing segment registers for referencing thread
> local storage for posix threads, and we're hitting an unexpected
> (and probably slow) code path...
Probably. Might "set_tid_address()" or "set_thread_area()" be the
offender?
execve("/bin/ls", ["ls"], [/* 42 vars */]) = 0
uname({sys="Linux", node="curly.lab.netapp.com", ...}) = 0
set_tid_address(0) = -1 ENOSYS (Function not implemented)
brk(0) = 0x805a40e
<...>
set_thread_area({entry_number:-1 -> -1, base_addr:0x805a680,
limit:1048575, seg_32bit:1, contents:0, read_exec_only:0,
limit_in_pages:1, seg_not_present:0, useable:1}) = -1 ENOSYS (Function
not implemented)
<...>
-Kip
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
next prev parent reply other threads:[~2004-04-28 1:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-21 0:45 Re: Need help Neugebauer, Rolf
2004-04-21 15:29 ` I RATTAN
2004-04-21 16:05 ` Mark Williamson
2004-04-21 17:21 ` I RATTAN
2004-04-21 17:40 ` Rolf Neugebauer
2004-04-22 2:28 ` I RATTAN
2004-04-22 15:07 ` I RATTAN
2004-04-27 18:56 ` problems with latest unstable Kip Macy
2004-04-28 0:28 ` Ian Pratt
2004-04-28 1:24 ` Kip Macy [this message]
2004-04-28 2:15 ` Ian Pratt
2004-04-28 2:22 ` Nuno Silva
2004-04-28 6:52 ` Keir Fraser
2004-05-16 0:24 ` stopping a domain Kip Macy
2004-05-16 7:48 ` Keir Fraser
2004-05-16 18:53 ` Kip Macy
2004-05-31 20:38 ` scheduler panic Kip Macy
2004-05-31 21:27 ` Keir Fraser
2004-05-31 21:46 ` Kip Macy
2004-05-31 22:24 ` Ian Pratt
2004-05-31 22:39 ` Kip Macy
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=20040427181626.I31878@demos.bsdclusters.com \
--to=kmacy@fsmware.com \
--cc=Ian.Pratt@cl.cam.ac.uk \
--cc=xen-devel@lists.sourceforge.net \
/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.