linux-um archives
 help / color / mirror / Atom feed
From: BlaisorBlade <blaisorblade_spam@yahoo.it>
To: Michael Koehne <kraehe@copyleft.de>,
	user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Unable to handle kernel paging request ...
Date: Wed, 7 Jul 2004 19:29:46 +0200	[thread overview]
Message-ID: <200407071929.46294.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <20040707090621.GA6094@bakunin.copyleft.de>

Alle 11:06, mercoledì 7 luglio 2004, Michael Koehne ha scritto:
> Moin Guru's,
>
>   i have 2.6.x host crashes, and I dont know, if they are related to
>   UML. I have a perfectly running 2.4.22 SKAS system on a dual PPro,
>   and a laptop who requires a 2.6.x kernel because of hardware. This
>   laptop is prepared to run UML's - but it seldom does.

>   But the laptop crashes about once or twice a week. This sometimes
>   happens on operations like `find . -print | while read x; do diff
>   ../foo/$x $x; done` or rsync over large directory trees. And sometimes
>   on idle state - e.g. tonight at crontime with a 'postmaster' crash.
>   I've talked to people on IRC, and they dont encounter those kind of
>   ext3 crashes on 2.6 kernels. I dont had a camera for a screenshot,
>   but dump was in ext3 area.
What you mean with "ext3 crash"? "The dump was in ext3 area"? I don't 
understand you, sorry.

>   So it might be something with SKAS host patch - even if the system
>   also crashes, if no UML is running.
Well, the UML patch should have no influence, if you don't run UML on it (if 
it happens after you have run UML at least once, there is still a chance
>      33240033 Feb  3 06:41 linux-2.6.1.tar.bz2
>    +    15570 Feb  4 02:36 host-2.6.1-skas3.patch
>   or 34896138 May 25 20:45 linux-2.6.6.tar.bz2
>    +    16182 May 25 20:35 host-skas3-2.6.6-v1.patch

Well, since you experience them so often, try compiling a vanilla kernel, 
without the SKAS patch. Also, I'm highly suspicious of the 2.6.1 patch: it's 
likely it is an old, buggy version. Is that from Stephen D. Williams, 
distributed at this URL: http://sdw.st/src/uml/linux-2.6.1-skas3.patch? That 
is a buggy one, known to cause crashes... the second one is safe enough 
(though somebody experience memory leaks... as reported on 
http://www.user-mode-linux.org/~blaisorblade; however, they seldom happen).

-- 
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729



-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.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-07-07 17:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-07  9:06 [uml-devel] Unable to handle kernel paging request Michael Koehne
2004-07-07 17:29 ` BlaisorBlade [this message]
2004-07-08  3:31   ` Michael Koehne
2004-07-08 16:00     ` BlaisorBlade
2004-07-07 17:45 ` BlaisorBlade

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=200407071929.46294.blaisorblade_spam@yahoo.it \
    --to=blaisorblade_spam@yahoo.it \
    --cc=kraehe@copyleft.de \
    --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