From: Lee Revell <rlrevell@joe-job.com>
To: Jacek Luczak <difrost@pin.if.uz.zgora.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Oops with 2.6.15
Date: Thu, 05 Jan 2006 18:09:21 -0500 [thread overview]
Message-ID: <1136502562.847.75.camel@mindpipe> (raw)
In-Reply-To: <43BDA76F.1000906@pin.if.uz.zgora.pl>
On Fri, 2006-01-06 at 00:10 +0100, Jacek Luczak wrote:
> Jan 5 19:25:04 slawek kernel: EIP: 0060:[<c0138603>] Tainted:
> P
> VLI
It's impossible to debug this unless you can reproduce it with a clean
kernel. If you can't then it's likely that the binary kernel module is
the problem.
Lee
next prev parent reply other threads:[~2006-01-05 23:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-05 23:10 Oops with 2.6.15 Jacek Luczak
2006-01-05 23:09 ` Lee Revell [this message]
2006-01-05 23:12 ` Jesper Juhl
2006-01-05 23:30 ` Jacek Luczak
2006-01-06 16:50 ` Jacek Luczak
2006-01-06 21:10 ` Bill Davidsen
2006-01-07 0:41 ` Jacek Luczak
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=1136502562.847.75.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=difrost@pin.if.uz.zgora.pl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox