From: Robert Jameson <rj@open-net.org>
To: Robert Love <rml@tech9.net>
Cc: linux-kernel@vger.kernel.org, alan@lxorguk.ukuu.org.uk
Subject: Re: oops with 2.4.18-pre9-mjc2
Date: Fri, 15 Feb 2002 10:20:37 -0500 [thread overview]
Message-ID: <20020215102037.00cf2ad9.rj@open-net.org> (raw)
In-Reply-To: <1013780277.950.663.camel@phantasy>
In-Reply-To: <20020215035135.0c26b130.rj@open-net.org> <1013780277.950.663.camel@phantasy>
[-- Attachment #1: Type: text/plain, Size: 818 bytes --]
It's appears right after my PDA finishes syncing, so im guessing, its
during a device close. To answer alans question im using nVidias kernel
driver, therefor i tainted the kernel (tm) (c).
On 15 Feb 2002 08:37:52 -0500
Robert Love <rml@tech9.net> wrote:
> On Fri, 2002-02-15 at 03:51, Robert Jameson wrote:
> > I have been seeing this oops from 2.4.16 -> 2.4.18-pre9, so here we
> > go!
>
> Do you see this on device close? It looks like there may be a race
> between device closer -> usb release.
>
> Can you reproduce it without the binary module you are loading?
>
> Robert Love
--
Robert Jameson http://rj.open-net.org
C2 Village at Wexford Hwy 278, Tel: +1 (843) 757 9428
Hilton Head Isl, SC Cel: +1 (843) 298 0957
US, 29928. mailto:rj@open-net.org
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2002-02-15 15:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-15 8:51 Robert Jameson
2002-02-15 8:55 ` William Lee Irwin III
2002-02-15 13:29 ` Michael Cohen
2002-02-15 13:37 ` Robert Love
2002-02-15 20:18 ` Hard lockup with 2.4.18-pre9 + preempt + lock break + O1k[23] + rmap Mike Fedyk
2002-02-16 9:29 ` Zwane Mwaikambo
2002-02-15 22:00 ` Robert Love
2002-02-15 23:22 ` Mike Fedyk
2002-02-15 23:30 ` William Lee Irwin III
2002-02-15 23:42 ` Mike Fedyk
2002-02-15 14:26 ` oops with 2.4.18-pre9-mjc2 Alan Cox
2002-02-15 15:20 ` Robert Jameson [this message]
2002-02-15 15:30 ` Arjan van de Ven
2002-02-15 17:48 ` Alan Cox
2002-02-15 19:15 ` Robert Love
2002-02-15 16:07 ` Greg KH
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=20020215102037.00cf2ad9.rj@open-net.org \
--to=rj@open-net.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.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
all inboxes | Powered by JetHome®