From: "D. Hazelton" <dhazelton@enter.net>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: oops in 2.6.13-rc6-git5
Date: Tue, 16 Aug 2005 01:51:21 -0400 [thread overview]
Message-ID: <200508160151.28999.dhazelton@enter.net> (raw)
In-Reply-To: <9a8748490508150522f6c3921@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1089 bytes --]
On Monday 15 August 2005 08:22, Jesper Juhl wrote:
> Can you reproduce the crash reliably?
> Can you reproduce the crash with a non-tainted kernel?
I've tried several times now to reproduce the oops, but there might have been
another factor that led to the oops, because just booting the kernel and
shutting down does not trigger it. I have tried reproducing all conditions up
to the time that the oops actually occurred and think it might just be my
hardware going flaky - so I have reloaded the module that taints the kernel
(have done this already and having the module loaded when the powerdown
started did not trigger the oops) and am seeing if using it for any period of
time causes the oops to occur. If it does I will try the other driver
available for the modem, although that one also contains proprietary code.
The upside is that it does not make use of any functions marked as deprecated
in any version of the kernel, where the official driver requires me to
re-enable a deprecated function that had been made non-exported by the
kernel.
DRH
[-- Attachment #1.2: 0xA6992F96300F159086FF28208F8280BB8B00C32A.asc --]
[-- Type: application/pgp-keys, Size: 1365 bytes --]
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2005-08-16 5:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-15 5:33 oops in 2.6.13-rc6-git5 D. ShadowWolf
2005-08-15 12:22 ` Jesper Juhl
2005-08-16 1:46 ` D. ShadowWolf
2005-08-16 5:51 ` D. Hazelton [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=200508160151.28999.dhazelton@enter.net \
--to=dhazelton@enter.net \
--cc=jesper.juhl@gmail.com \
--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