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

[-- Attachment #1: Type: text/plain, Size: 472 bytes --]

On 22 Jul 2003 17:26:10 +0200 Michael Troß (MT) wrote:

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

No, the lockup happens during operation. Sometimes the kernel runs only for
about one hour, sometimes for a day, but never longer before the lockups
happen.

I don't think going back to 2.4.18 will make a difference for this case,
or do you think it will?

Regards,
-Udo.

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-07-22 15:15 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 ` CPU Lockup with 2.4.21 and 2.4.22-pre Michael Troß
2003-07-22 15:30   ` Udo A. Steinberg [this message]
     [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=20030722173031.338fcf32.us15@os.inf.tu-dresden.de \
    --to=us15@os.inf.tu-dresden.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mtross@compu-shack.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;
as well as URLs for NNTP newsgroup(s).