linux-um archives
 help / color / mirror / Atom feed
From: Nick Craig-Wood <ncw1@axis.demon.co.uk>
To: Jeff Dike <jdike@addtoit.com>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] skas3 + 2.4.21 oops
Date: Fri, 19 Dec 2003 11:13:45 +0000	[thread overview]
Message-ID: <20031219111345.GA22779@axis.demon.co.uk> (raw)
In-Reply-To: <200312180115.hBI1F5kS007913@ccure.user-mode-linux.org>

On Wed, Dec 17, 2003 at 08:15:05PM -0500, Jeff Dike wrote:
> ncw1@axis.demon.co.uk said:
> > We are running the skas3 patch (host-skas3.patch from the uml website)
> > on top of a debian 2.4.21 kernel tree with fairsched.  We got these
> > oopses recently.  After the second the server was basically unusable -
> > any attempt to use tools like ps to access the process table just
> > never returned.
> 
> This might be incidental - one of the oopsing things might have grabbed the
> task_list semaphore before crapping out.

OK

> > Both of the oopses have write_proc_mm() in the backtrace... 
> 
> That's somewhat incriminating, but strange because no one has reported any
> trouble with skas3 for over a year.

And we've had no trouble with it either except for this one machine.

> I'm thinking maybe a bad patch interaction.  Did all the patches
> apply cleanly?

I had to check, but yes all the patches looked OK.

What is strange is that we have a lot of machines all running this
kernel, but we only have one machine exhibiting this problem.  We've
swapped all the hardware (bar the hard disks) of the problem host but
the problem has remained.

I think it is activity caused by a specific UML which triggers the
problem, but I haven't put my finger on exactly what as it doesn't
happen very often.  I have a pretty good idea which UML triggers the
problem too so we could try moving it to a different host to see if
the problem goes with it.

-- 
Nick Craig-Wood
ncw1@axis.demon.co.uk


-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

      parent reply	other threads:[~2003-12-19 11:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-16 16:31 [uml-devel] skas3 + 2.4.21 oops Nick Craig-Wood
2003-12-18  1:15 ` Jeff Dike
2003-12-18 18:58   ` BlaisorBlade
2003-12-18 19:07     ` BlaisorBlade
2003-12-19 11:13   ` Nick Craig-Wood [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=20031219111345.GA22779@axis.demon.co.uk \
    --to=ncw1@axis.demon.co.uk \
    --cc=jdike@addtoit.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox