All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julian Scheid <julian@sektor37.de>
To: BlaisorBlade <blaisorblade_spam@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net, jdike@karaya.com
Subject: Re: [uml-devel] Default kernel configuration on 2.6.x
Date: Tue, 12 Oct 2004 02:41:00 +0200	[thread overview]
Message-ID: <416B281C.3090201@sektor37.de> (raw)
In-Reply-To: <200410120146.06254.blaisorblade_spam@yahoo.it>

BlaisorBlade wrote:
> On Tuesday 12 October 2004 00:22, Julian Scheid wrote:
> 
> 
>>This is especially fatal because without a virtual character device
>>driver, stdio initialization will fail silently or with an unhelpful
>>error message ("sleeping process got unexpected signal 11"), leaving
>>unsuspecting users like me completely puzzled.
> 
> I.e. that error comes from this?????? Thanks a lot for this solution, but 
> could you explain which is exactly the wrong CONFIG_ option set for this to 
> happen?

No, not exactly, but I believe it's the file descriptor channel support.

Long answer: when I encountered this problem ("signal 11") and realized 
that my kernel config could be missing something I found that without 
exception, all UML-specific options were disabled (for the reasons 
mentioned).

I proceeded to enable most of them (except the watchdog and some virtual 
network drivers which sounded arcane) and the problem went away.

So I don't know exactly which option was necessary to get around the 
SEGV, but since it always happened around the stdio initialization and I 
was using "con=pty con0=fd:0,fd:1" I would say the culprit was the 
missing file descriptor channel support and/or pty channel support.

If you can't reproduce it like this, let me know and I will try to nail 
it down.

> [Please always avoid sending that kind of patches; you **MUST ALWAYS** use 
> unified diffs, i.e. diff -u; the preferred setting is -puNr].

I noticed that too just a minute ago, very newbie-ish. Pardon, I'm not 
submitting patches too often, I'll take more care next time.

But hey, that's no reason to shout at me, I'm just trying to be helpful ;)

> About this, see the other responses - this must be done in mainline whenever 
> we are cross-compiling.

Agree 100% with Michael and you, this is the right solution. I was 
focused on UML but in fact it's a larger issue.

Cheers,

Julian


-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  reply	other threads:[~2004-10-12  0:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-11 22:22 [uml-devel] Default kernel configuration on 2.6.x Julian Scheid
2004-10-11 22:58 ` Michael Richardson
2004-10-11 23:47   ` BlaisorBlade
2004-10-11 23:46 ` BlaisorBlade
2004-10-12  0:41   ` Julian Scheid [this message]
2004-10-12  1:01     ` BlaisorBlade
2004-10-12  1:39       ` Julian Scheid

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=416B281C.3090201@sektor37.de \
    --to=julian@sektor37.de \
    --cc=blaisorblade_spam@yahoo.it \
    --cc=jdike@karaya.com \
    --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 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.