linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Troß" <mtross@compu-shack.com>
To: "Udo A. Steinberg" <us15@os.inf.tu-dresden.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: CPU Lockup with 2.4.21 and 2.4.22-pre
Date: 22 Jul 2003 17:26:10 +0200	[thread overview]
Message-ID: <1058887570.2357.157.camel@mtross2.csintern.de> (raw)
In-Reply-To: <0001F49C@gwia.compu-shack.com>

Am Die, 2003-07-22 um 16.24 schrieb Udo A. Steinberg:

> MT> As you might know, the Compu-Shack fddi products reached end-of-life
> MT> last year.
> 
> Yes. Just thought I'd let you know that we aren't using the same
> patch as on the website, but one that has been rediffed for 2.4.21 and
> has an additional fix from you in it.

Mentioned it just to let you know that the company is no longer
providing new drivers for new kernels. Probably you better stay with
2.4.18.

[snip]

Seems that a spin lock is already held. Do you get this oops right after
opening the device? Then please try NoSelfTest.

Regards,
Michael


       reply	other threads:[~2003-07-22 15:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <0001F49C@gwia.compu-shack.com>
2003-07-22 15:26 ` Michael Troß [this message]
2003-07-22 15:30   ` CPU Lockup with 2.4.21 and 2.4.22-pre Udo A. Steinberg
     [not found] <0001F474@gwia.compu-shack.com>
2003-07-22 12:55 ` Michael Troß
2003-07-22 14:24   ` Udo A. Steinberg
     [not found] <0001F3D0@gwia.compu-shack.com>
2003-07-22 10:24 ` Michael Troß
2003-07-22 11:51   ` Udo A. Steinberg
2003-07-21 14:12 Udo A. Steinberg
2003-07-21 14:17 ` Udo A. Steinberg

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=1058887570.2357.157.camel@mtross2.csintern.de \
    --to=mtross@compu-shack.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=us15@os.inf.tu-dresden.de \
    /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;
as well as URLs for NNTP newsgroup(s).