From: Gerd Hoffmann <kraxel@suse.de>
To: Chris Wright <chrisw@sous-sol.org>
Cc: Virtualization Mailing List <virtualization@lists.osdl.org>
Subject: Re: Oops
Date: Thu, 11 Jan 2007 09:11:00 +0100 [thread overview]
Message-ID: <45A5F114.4010904@suse.de> (raw)
In-Reply-To: <20070110235232.GE19575@sequoia.sous-sol.org>
Chris Wright wrote:
> * Gerd Hoffmann (kraxel@suse.de) wrote:
>> Gerd Hoffmann wrote:
>>> OK, now I'm back to the old buggy state where the ttylinux rootfs fails
>>> to boot up due to init being killed instantly or something like that ...
>> That was something completely different. Machine booted up just fine,
>> but without any output. Due to initialization in link order and xen/
>> coming after serial/ in drivers/ the serial console becomes default when
>> enabled. Ouch. Move it up.
>
> This should not be needed, the console should be xcv0, completely decoupled
> from serial.
Wrong. In't not about whenever the xen console is registered as ttyS0
tty1 or xcv0, but whenever the xen console or the serial console (as in
"8250 driver") is registered first and thus becomes the default console.
drivers/char/ (with the vt code) is linked before drivers/serial/ for
the very same reason.
cheers,
Gerd
--
Gerd Hoffmann <kraxel@suse.de>
next prev parent reply other threads:[~2007-01-11 8:11 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-09 13:34 Oops Gerd Hoffmann
2007-01-09 22:46 ` Oops Jeremy Fitzhardinge
2007-01-10 8:16 ` Oops Gerd Hoffmann
2007-01-10 10:29 ` Oops Gerd Hoffmann
2007-01-10 13:05 ` Oops Gerd Hoffmann
2007-01-10 20:07 ` Oops Jeremy Fitzhardinge
2007-01-10 23:52 ` Oops Chris Wright
2007-01-10 23:53 ` Oops Jeremy Fitzhardinge
2007-01-11 8:13 ` Oops Gerd Hoffmann
2007-01-11 8:11 ` Gerd Hoffmann [this message]
2007-01-11 15:45 ` Oops Gerd Hoffmann
2007-01-11 17:41 ` Oops Chris Wright
2007-01-12 8:24 ` Oops Gerd Hoffmann
2007-01-12 2:53 ` Oops Rusty Russell
2007-01-12 4:23 ` Oops Chris Wright
2007-01-12 8:31 ` Oops Gerd Hoffmann
2007-01-10 20:06 ` Oops Jeremy Fitzhardinge
2007-01-10 21:44 ` Oops Jeremy Fitzhardinge
2007-01-11 14:12 ` Oops Gerd Hoffmann
2007-01-11 19:56 ` Oops Jeremy Fitzhardinge
2007-01-10 19:38 ` Oops Jeremy Fitzhardinge
[not found] <1aee86c7-27f2-ee81-9669-8a49aa521dfd@lockie.ca>
2020-06-23 17:28 ` oops James
-- strict thread matches above, loose matches on Subject: below --
2019-05-31 3:50 Oops Alex Elder
2007-02-18 15:47 OOPS Menny Hamburger
2006-04-26 15:15 oops Alex Orlov
2006-04-26 16:29 ` oops Erik Mouw
2006-03-05 20:53 Oops Iain William Wiseman
2005-08-16 21:49 Oops David F Barrera
2005-08-16 21:52 ` Oops Jerone Young
2005-02-28 8:04 oops Jurzitza, Dieter
2005-02-28 22:47 ` oops Richard Mortimer
2004-01-06 4:51 OOPs Nick
2004-01-11 13:50 ` OOPs Carsten Grohmann
2003-12-12 17:45 oops Cristiano De Michele
2003-11-01 8:30 Oops Mark Hindley
2003-06-29 21:58 oops Greg Stark
2003-03-09 21:52 oops Thomas Kaeding
2003-02-06 21:51 Oops Gregory Stark
2002-11-25 10:51 oops Tomasz Wrona
2002-11-25 10:35 oops Tomasz Wrona
[not found] <45F949D73F69D41198B00004AC2513FB03D5B6CD@mad00mp3.dot.state.wi.us>
2002-06-18 14:55 ` oops Russell Coker
2002-06-18 19:47 ` oops Eric Johnson
2002-06-18 21:11 ` oops Russell Coker
[not found] <Pine.GSO.4.33.0206171425590.12900-100000@raven>
2002-06-17 18:52 ` oops Russell Coker
[not found] ` <E17KXrd-0001En-00@avocet.mail.pas.earthlink.net>
2002-06-19 5:35 ` oops Russell Coker
2002-06-16 15:52 oops Russell Coker
2002-01-25 11:23 Oops Philipp Matthias Hahn
2001-11-27 13:46 Oops Mark Hindley
2001-08-21 22:36 Oops Rob McPeak
2001-05-18 16:42 Oops Andreas Bergen
[not found] <mailman.989407980.15158.linux-kernel2news@redhat.com>
2001-05-09 17:16 ` oops Pete Zaitcev
2001-05-09 19:18 ` oops Terry Shull
2001-05-09 15:33 oops Terry Shull
2001-05-05 20:43 oops Bial Attila
2001-03-20 15:08 OOPS Mircea Damian
2001-03-09 15:42 Oops Sherman Stebbins
2001-01-19 18:00 oops mkloppstech
2001-01-21 21:18 ` oops David Woodhouse
2000-11-14 16:46 oops Bill Triplett
1999-09-15 5:45 Oops Dagan Sgiath
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=45A5F114.4010904@suse.de \
--to=kraxel@suse.de \
--cc=chrisw@sous-sol.org \
--cc=virtualization@lists.osdl.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 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.