From: Jeff Dike <jdike@addtoit.com>
To: Nick Craig-Wood <ncw1@axis.demon.co.uk>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] skas3 + 2.4.21 oops
Date: Wed, 17 Dec 2003 20:15:05 -0500 [thread overview]
Message-ID: <200312180115.hBI1F5kS007913@ccure.user-mode-linux.org> (raw)
In-Reply-To: Your message of "Tue, 16 Dec 2003 16:31:34 GMT." <20031216163134.GA30608@axis.demon.co.uk>
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.
> 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.
I'm thinking maybe a bad patch interaction. Did all the patches apply cleanly?
Jeff
-------------------------------------------------------
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
next prev parent reply other threads:[~2003-12-18 0:59 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 [this message]
2003-12-18 18:58 ` BlaisorBlade
2003-12-18 19:07 ` BlaisorBlade
2003-12-19 11:13 ` Nick Craig-Wood
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=200312180115.hBI1F5kS007913@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=ncw1@axis.demon.co.uk \
--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