All of lore.kernel.org
 help / color / mirror / Atom feed
From: Blaisorblade <blaisorblade_spam@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Bodo Stroesser <bstroesser@fujitsu-siemens.com>
Subject: Re: [uml-devel] 2.6.9-bb3 on 2.6.9 host problem - triggering a host bug?
Date: Thu, 2 Dec 2004 19:42:48 +0100	[thread overview]
Message-ID: <200412021942.49285.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <41AE160D.3030807@fujitsu-siemens.com>

On Wednesday 01 December 2004 20:05, Bodo Stroesser wrote:
> Blaisorblade wrote:
> > On Monday 29 November 2004 23:15, Blaisorblade wrote:
> >
> > I pressed Enter before filling in details - this is what I get on some
> > UML versions at startup. Specifically, I get it on -bb3, and on versions
> > based on it, on startup. I've tried removing the patches I've added to
> > -bb3 and it still does not work, which is not nice.
>
> Have started to analyze the crash. If I did it right, the crash occurs at
> the beginning of kmem_cache_alloc(). It seems to be called with argument
> NULL as the pointer to the cache --> segfault.

> Hope, this helps.

> Bodo

Well, this crash (or something such) is easily repeatable if you disable TT 
mode when building and enable CONFIG_STATIC_LINK.

It is related, probably, either to some patches which went in *after* 
2.6.7-1um (at that time, there was still a separate patch to apply on top of 
the corrisponding kernel), or to some problems with the toolchain. I should 
build a 2.6.7-1um kernel with STATIC_LINK to verify that it works (and then 
that we broke it) or that it doesn't (and then it's the toolchain/build env), 
but I keep forgetting to do it.

Bye
-- 
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
http://www.user-mode-linux.org/~blaisorblade


-------------------------------------------------------
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://productguide.itmanagersjournal.com/
_______________________________________________
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-12-02 18:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-29 22:15 [uml-devel] 2.6.9-bb3 on 2.6.9 host problem - triggering a host bug? Blaisorblade
2004-11-29 22:26 ` Bodo Stroesser
2004-11-30 18:50 ` Blaisorblade
2004-12-01 18:52   ` Bodo Stroesser
2004-12-01 18:52     ` Bodo Stroesser
2004-12-01 19:05   ` Bodo Stroesser
2004-12-02 18:42     ` Blaisorblade [this message]

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=200412021942.49285.blaisorblade_spam@yahoo.it \
    --to=blaisorblade_spam@yahoo.it \
    --cc=bstroesser@fujitsu-siemens.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.