From: Gerd Knorr <kraxel@bytesex.org>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Re: Fw: [patch] uml: terminal cleanup
Date: Thu, 10 Mar 2005 09:13:40 +0100 [thread overview]
Message-ID: <20050310081340.GC17880@bytesex> (raw)
In-Reply-To: <200503091938.46936.blaisorblade@yahoo.it>
> No, this does not happen... the normal situation currently is that the kernel
> skips printing part of the initial output.
>
> $ ./OldKernels/vmlinux-2.6.11-rc3
> Checking for /proc/mm...found
> Checking for the skas3 patch in the host...found
> Checking PROT_EXEC mmap in /tmp...OK
> ject_hotplug - call_usermodehelper returned -1
> io scheduler noop registered
> NET: Registered protocol family 2
> IP: routing cache hash table of 256 buckets, 4Kbytes
> TCP established hash table entries: 2048 (order: 3, 32768 bytes)
> TCP bind hash table entries: 2048 (order: 2, 24576 bytes)
> TCP: Hash tables configured (established 2048 bind 2048)
> Initialized stdio console driver
> Console initialized on /dev/tty0
> Initializing software serial port version 1
> Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(98,0)
Ouch. I've never seen that myself though, works perfectly fine for me.
Could be somehow related to the scrambled compiler logs reported a few
weeks ago, maybe the tty/line buffer handling is broken ...
> $ ./OldKernels/vmlinux-2.6.11-rc3 stderr=1
[ snip ]
as expected ...
> $ ./vmlinux-2.6.11-rc4-bk-testLock-nofix console=stderr
> Checking for /proc/mm...found
> Checking for the skas3 patch in the host...found
> Checking PROT_EXEC mmap in /tmp...OK
> [ no more messages ]
stderr=1 is needed in any case. console=stderr might be needed
additionally in case you want to sent the kernel messages to _two_
console devices, i.e. something like this (both stderr and the xterm
for tty1):
# linux con=pts con1=xterm stderr=1 console=stderr console=tty1
HTH,
Gerd
--
#define printk(args...) fprintf(stderr, ## args)
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&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 prev parent reply other threads:[~2005-03-10 8:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20041128010910.1b5478c7.akpm@osdl.org>
2005-03-05 17:58 ` [uml-devel] Re: Fw: [patch] uml: terminal cleanup Blaisorblade
2005-03-08 8:25 ` Gerd Knorr
2005-03-09 18:38 ` Blaisorblade
2005-03-10 8:13 ` Gerd Knorr [this message]
2005-03-11 3:04 ` Rob Landley
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=20050310081340.GC17880@bytesex \
--to=kraxel@bytesex.org \
--cc=blaisorblade@yahoo.it \
--cc=user-mode-linux-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox