From: Nicolas Bareil <nico@chdir.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.19.2 : Oops
Date: Thu, 18 Jan 2007 08:48:30 +0100 [thread overview]
Message-ID: <87sle8wzap.fsf@boz.loft.chdir.org> (raw)
In-Reply-To: 20070117233545.GA12717@kroah.com
On 18 Jan 2007, Greg KH wrote:
> > Since 2.6.19, I get the following Oops once a day, always with the same
> > process, newspipe[1] which use a lot of CPU, threads and I/O.
> > ...
> Can you reproduce it without the grsec patch applied?
I'm compiling a new kernel and will try it soon!
--
Nicolas Bareil http://chdir.org/~nico/
OpenPGP=0xAE4F7057 Fingerprint=34DB22091049FB2F33E6B71580F314DAAE4F7057
next prev parent reply other threads:[~2007-01-18 7:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-17 10:21 Linux 2.6.19.2 : Oops Nicolas Bareil
2007-01-17 23:35 ` Greg KH
2007-01-18 7:48 ` Nicolas Bareil [this message]
2007-01-22 19:37 ` Nicolas Bareil
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=87sle8wzap.fsf@boz.loft.chdir.org \
--to=nico@chdir.org \
--cc=linux-kernel@vger.kernel.org \
/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.