From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.12] helo=sc8-sf-mx2.sourceforge.net) by sc8-sf-list1.sourceforge.net with esmtp (Exim 4.30) id 1CHAii-0006fh-IR for user-mode-linux-devel@lists.sourceforge.net; Mon, 11 Oct 2004 17:40:52 -0700 Received: from p15103123.pureserver.info ([217.160.129.185] helo=sektor37.de) by sc8-sf-mx2.sourceforge.net with smtp (Exim 4.41) id 1CHAig-0002xX-HO for user-mode-linux-devel@lists.sourceforge.net; Mon, 11 Oct 2004 17:40:52 -0700 Message-ID: <416B281C.3090201@sektor37.de> From: Julian Scheid MIME-Version: 1.0 Subject: Re: [uml-devel] Default kernel configuration on 2.6.x References: <416B07AC.3030308@sektor37.de> <200410120146.06254.blaisorblade_spam@yahoo.it> In-Reply-To: <200410120146.06254.blaisorblade_spam@yahoo.it> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Sender: user-mode-linux-devel-admin@lists.sourceforge.net Errors-To: user-mode-linux-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Id: The user-mode Linux development list List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 12 Oct 2004 02:41:00 +0200 To: BlaisorBlade Cc: user-mode-linux-devel@lists.sourceforge.net, jdike@karaya.com 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