From: Matthias Haase <matthias_haase@bennewitz.com>
To: Martin Josefsson <gandalf@wlug.westbo.se>
Cc: linux-kernel@vger.kernel.org
Subject: Re: repeatable SMP lockups - kernel 2.4.9
Date: Sat, 15 Sep 2001 09:20:01 +0200 [thread overview]
Message-ID: <20010915092001.08a7fe2a.matthias_haase@bennewitz.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0109141824580.453-100000@tux.rsn.bth.se>
In-Reply-To: <20010914182325.225a7211.matthias_haase@bennewitz.com> <Pine.LNX.4.21.0109141824580.453-100000@tux.rsn.bth.se>
On Fri, 14 Sep 2001 18:26:04 +0200 (CEST)
Martin Josefsson <gandalf@wlug.westbo.se> wrote:
> I don't think it sounds that stupid.. but if it had hung you wouldn't
> have
> known if it was the possible interupthandeling bug or some oghet bug in
> DRI/DRM :)
Yes, but I now (relative) sure, that's ram-timing (it's DDR-RAM on 266
mHz) and cpu-clock are right.
Have found last night, that the box lockup too, if I use the scanner and
scanning a large file.
For scanning, I use an second additional SCSI-Controller (Dawicontrol,
based on AMD 53c974 [PCscsi]). The preview scan is o.k., but the scan
itself stops (and lockup hard the machine of course), if 4-5 mb are
transfered.
Sounds like an interrupt handling error?
> I'm going to start my tests here soon.
>
> /Martin
Please let me known about your results.
regards
Matthias
--
Gruesse
Matthias Haase | Telefon +49-(0)3733-23713
Markt 2 | Telefax +49-(0)3733-22660
|
D-09456 Annaberg-Buchholz | http://www.bennewitz.com
next prev parent reply other threads:[~2001-09-15 7:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-14 12:30 Matthias Haase
2001-09-14 14:54 ` Martin Josefsson
2001-09-14 16:23 ` Matthias Haase
2001-09-14 16:26 ` Martin Josefsson
2001-09-15 7:20 ` Matthias Haase [this message]
2001-09-14 18:37 ` Andrew Morton
2001-09-15 8:32 ` Matthias Haase
[not found] <OF21F37EC6.10570427-ON88256AC7.0052A32C@boulder.ibm.com>
2001-09-14 15:46 ` Matthias Haase
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=20010915092001.08a7fe2a.matthias_haase@bennewitz.com \
--to=matthias_haase@bennewitz.com \
--cc=gandalf@wlug.westbo.se \
--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
all inboxes | Powered by JetHome®