From: Derrik Pates <demon@devrandom.net>
To: Tobias Hunger <tobias@aquazul.com>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>, xen-devel@lists.sourceforge.net
Subject: Re: Kernel crash
Date: Wed, 19 Jan 2005 11:54:45 -0500 [thread overview]
Message-ID: <41EE90D5.6060007@devrandom.net> (raw)
In-Reply-To: <200501191504.49759.tobias@aquazul.com>
Tobias Hunger wrote:
> I did. The flags reappear during make ARCH=xen and the consoles get added to
> my kernel in spite of those settings. That is why I edited the Kconfig files.
> Ugly but works...
Are you doing 'make ARCH=xen (menu|x|g)config' ? If you don't, the
config will probably not be correct for your target architecture.
> My results so far:
> extra="": crash
> extra="console=xen": no output (hoping that this turns of the other consoles)
> extra="console=tty2": crash
> extra="console=ttyS0": no output
> extra="xencons=ttyS console=ttyS0": crash
> extra="xencons=off": no output
> extra="xencons=off console=ttyS0": no output
> extra="xencons=off console=tty1": no output
> No config_vm, config_vgaconsole, etc. (nothing set in .config that contains
> "CONS"): crash
> No config_vm, ... with modified Kconfig files: no output
This is on an unprivileged domain? Unprivileged domains don't have a VGA
console, and they don't have access to serial ports; the console is
implemented through an inter-domain communication channel, like the
virtual network and block devices are.
--
Derrik Pates
demon@devrandom.net
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
next prev parent reply other threads:[~2005-01-19 16:54 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-19 12:54 Kernel crash Ian Pratt
2005-01-19 14:04 ` Tobias Hunger
2005-01-19 15:12 ` Keir Fraser
2005-01-19 16:54 ` Derrik Pates [this message]
2005-01-19 21:05 ` Tobias Hunger
2005-01-20 8:56 ` Keir Fraser
2005-01-20 10:00 ` Tobias Hunger
2005-01-20 11:30 ` Keir Fraser
2005-01-20 22:55 ` Tobias Hunger
2005-01-19 17:46 ` Philip R Auld
-- strict thread matches above, loose matches on Subject: below --
2014-01-16 10:24 Kernel Crash Nieścierowicz Adam
2012-05-30 17:35 Kernel crash Guido Winkelmann
2012-06-08 16:35 ` Tommi Virtanen
2011-10-06 21:59 kernel crash Pau Espin Pedrol
2011-09-22 18:45 M
2011-09-22 21:24 ` Dave Jones
2011-09-22 21:38 ` David Rientjes
2011-09-22 21:53 ` Dave Jones
2008-01-29 10:32 fenglg
2008-01-29 13:34 ` Patrick McHardy
2008-01-29 17:55 ` Jan Engelhardt
2008-01-29 17:59 ` Patrick McHardy
2007-12-30 18:25 Jerry Geis
2006-02-11 5:37 Kernel Crash Jayaprakash Shanmugam
2005-01-19 1:31 Kernel crash Ian Pratt
2005-01-19 10:52 ` Tobias Hunger
2005-01-18 21:50 Tobias Hunger
2004-09-05 18:51 Giuliano Pochini
2004-09-06 15:16 ` Takashi Iwai
2004-09-07 7:55 ` Giuliano Pochini
2003-05-29 20:41 kernel crash Gordon Messmer
2003-05-29 21:20 ` John M Flinchbaugh
2003-05-29 22:36 ` Martin Josefsson
2003-05-30 4:23 ` Gordon Messmer
2003-05-30 10:53 ` Martin Josefsson
2003-05-30 10:18 ` Eicke Friedrich
2002-06-26 11:02 Pavel Gulchouck
2002-06-26 19:03 ` James Stevenson
2002-06-27 8:00 ` Pavel Gulchouck
2001-04-12 15:16 Cyrille Ngalle
2001-04-12 15:31 ` Russell King
2001-04-13 13:16 ` nak
2001-04-02 16:40 Wayne.Brown
2001-04-01 10:15 nak
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=41EE90D5.6060007@devrandom.net \
--to=demon@devrandom.net \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=tobias@aquazul.com \
--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.