All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Koehne <kraehe@copyleft.de>
To: BlaisorBlade <blaisorblade_spam@yahoo.it>,
	user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Unable to handle kernel paging request ...
Date: Thu, 8 Jul 2004 05:31:26 +0200	[thread overview]
Message-ID: <20040708033126.GA10586@bakunin.copyleft.de> (raw)
In-Reply-To: <200407071945.30015.blaisorblade_spam@yahoo.it> <200407071929.46294.blaisorblade_spam@yahoo.it>

Moin BlaisorBlade,

> >   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.

  the crash 2.6.1+SKAS happened on file system operations on the host,
  while UML systems had been up and running - I first seen them once
  on find, and twice on rsync directory file walks on the host. I
  upgraded to 2.6.6+SKAS and they occured seldom. My server moved
  housing also, and is now hosting the UMLs. So I only know that its
  a seldom condition that is ext3_ related, but might be related to
  the UML patch - as others dont tell about so many panics - but does
  not require an UML to touch /proc/mm.

  Yesterday I noticed some points at the kernel panic, that started at
  postmaster at crontab time, and had a lot of ext3 pointers - but I
  did'nt had the patiens to write 3 pages of kernel panic ;(

> 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

  the patch host-skas3-2.6.6-v1.patch is applied and running - but 
  /proc/mm was virgin - as there was no UML started on this machine
  for some days.

> >   or 34896138 May 25 20:45 linux-2.6.6.tar.bz2
> >    +    16182 May 25 20:35 host-skas3-2.6.6-v1.patch

  I'll stick to that combo for some more days (because of laziness ;)
  and hope to be more patient writing down the kernel panic next time.

> 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).
 
  *hm* whats the current 'best practice patch' for 2.6.x ? 

  an rsync copy of my server's UML to my laptop's UML is a nice thing I
  wont want to miss anymore, even if the Double-NAT between them was a
  bit confusing at first - and 2.4.22 SKAS server and 2.4.22 UML are
  stable like a rock - at least in my ubd over ext3 over md-raid1
  on a Dual processor environment.

> You say in the title "Unable to handle kernel paging request". It means you 
> got a panic... Have you saved somewhere the complete message? Have you 
> checked if it's inside /var/log/messages?
  
  its not in any logs - as it was ext3 related on the host file system,
  if I managed to understand the dump. The process was postmaster running
  from cron on the host - there was no UML running since boot and the
  trace mentioned a lot of ext3_ <something>.

> Does "dump was in ext3 area" means 
> that the call trace mentioned ext3_ <something>? If it speaks about 
> __init_new_context, proc_mm or such things then the SKAS patch is likely to 
> be at fault, if not it's unlikely...

  I'll look at those more closely if it happens again, any other
  pointers so I could sort out UML related areas here ?

  I'll also might find the time to try a more actual kernel+skas combo
  before - as the crash is seldom, on a machine, I'm using regulary for
  about 2-4 full load hours from compiler per day with normal background
  processes in the other time.

Bye Michael
-- 
  mailto:kraehe@copyleft.de             UNA:+.? 'CED+2+:::Linux:2.4.22'UNZ+1'
  http://www.xml-edifact.org/           CETERUM CENSEO WINDOWS ESSE DELENDAM


-------------------------------------------------------
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-08  3:31 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
2004-07-08  3:31   ` Michael Koehne [this message]
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=20040708033126.GA10586@bakunin.copyleft.de \
    --to=kraehe@copyleft.de \
    --cc=blaisorblade_spam@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 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.