mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Benjamin Monate <Benjamin Monate" <Benjamin.Monate@lri.fr>
To: linux-kernel@vger.kernel.org
Subject: Re: Strange lockup of the timer with 2.4.0-test10 SMP (and older)
Date: Mon, 20 Nov 2000 19:11:04 +0100 (MET)	[thread overview]
Message-ID: <14873.26936.500547.975636@sun-demons> (raw)
In-Reply-To: <3A196CD9.AB946AD3@onetelnet.fr>
In-Reply-To: <14868.3329.775330.576681@sun-demons> <3A15CE34.EF2FE3CC@uow.edu.au> <14873.17358.536711.2282@sun-demons> <3A196CD9.AB946AD3@onetelnet.fr>

Dans son message du Mon 20 November, Fort David ecrit : 
> > Further investigations showed that the problem will occur only when
> > Xfree 4.0.1 is running with an smp kenel . Xfree 3.3.6 is ok. Could this
> > be a bug in X ?  I thought that the kernel should prevent such a bug
> > from locking the computer.
> What 's your video card ? Not something running with closed source drivers ?
> (namely G-force)
> The kernel cannot prevent drivers from locking PCI/AGP bus.

My video card is a matrox G200SD, source is open. I will try another
video card tomorow.  I do understand that the kernel cannot prevent a
driver from locking then PCI bus : the timer lockup does not look like
a lock of the PCI bus (as SCSI and NIC are still working). Only the
timer interrupts and NMI seem to be stuck : can a driver cause
something so "lowlevel" ?

By the way, the processors are not overclocked.
I don't know how to check if something is overheating. Both fans seem okay
to me.

Do you any way to somehow "restart" (is it unmask ?) the timer IRQ
work and the NMI ? This would at least avoid some long fsck on
reboot...

Many thanks

-- 
| Benjamin Monate         | mailto:Benjamin.Monate@lri.fr |
| LRI - Bât. 490
| Université de Paris-Sud
| F-91405 ORSAY Cedex    

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-11-20 18:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3A15CE34.EF2FE3CC@uow.edu.au>
2000-11-16 16:36 ` Benjamin Monate <Benjamin Monate
2000-11-20 15:31   ` Benjamin Monate <Benjamin Monate
2000-11-20 18:11     ` Benjamin Monate <Benjamin Monate [this message]
2000-11-20 18:13       ` Alan Cox
2000-11-21 14:31         ` Maciej W. Rozycki
2000-11-21 16:27         ` Benjamin Monate <Benjamin Monate
2000-11-21 17:35           ` Maciej W. Rozycki
2000-11-22  9:45           ` Benjamin Monate <Benjamin Monate
2000-11-23 19:39             ` Benjamin Monate <Benjamin Monate
2000-11-27 16:58               ` Benjamin Monate <Benjamin Monate
2000-11-20 18:26     ` Fort David

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=14873.26936.500547.975636@sun-demons \
    --to=benjamin.monate@lri.fr \
    --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®