From: Jesper Juhl <jesper.juhl@gmail.com>
To: Parminder Chhabra <parminderchhabra@email.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: repeated Oops on Kernel 2.6.12.2
Date: Tue, 19 Jul 2005 03:54:13 +0200 [thread overview]
Message-ID: <9a8748490507181854416804c8@mail.gmail.com> (raw)
In-Reply-To: <20050718042523.275E41CE304@ws1-6.us4.outblaze.com>
On 7/18/05, Parminder Chhabra <parminderchhabra@email.com> wrote:
> Hi,
>
> I get repeated Oops messages on 2.6.12.2. I get the message on inserting a
Have you tested a more recent kernel like 2.6.13-rc3 or
2.6.13-rc3-git4 or 2.6.13-rc3-mm1 to see if the problem is already
solved?
> module that spawns a kernel thread to perform a task on a group of packets.
Perhaps you could provide the code for that module somewhere?
Sorry I can't be of more help.
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
prev parent reply other threads:[~2005-07-19 1:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-18 4:25 repeated Oops on Kernel 2.6.12.2 Parminder Chhabra
2005-07-19 1:54 ` Jesper Juhl [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=9a8748490507181854416804c8@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=parminderchhabra@email.com \
/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