public inbox for linux-kernel@vger.kernel.org
 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: Tue, 21 Nov 2000 17:27:33 +0100 (MET)	[thread overview]
Message-ID: <14874.41589.359267.717984@sun-demons> (raw)
In-Reply-To: <Pine.GSO.3.96.1001121151759.19886A-100000@delta.ds2.pg.gda.pl>
In-Reply-To: <E13xvRr-0003u9-00@the-village.bc.nu> <Pine.GSO.3.96.1001121151759.19886A-100000@delta.ds2.pg.gda.pl>

>  I guess not -- the timer interrupt and the NMI use different I/O APIC
> inputs.  If both are stuck, it's probably 8254 that gets reprogrammed.  I
> suppose XFree86 might be at fault -- does it happen with the NMI watchdog
> disabled, either? 
Yes. I just enabled the nmi watchdog to try to debug the problem. It did 
not change anything.

About the 8254, the kernel log contains :

Nov 20 17:15:15 pc8-118 kernel: MP-BIOS bug: 8254 timer 
				not connected to IO-AP
IC
Nov 20 17:15:15 pc8-118 kernel: ...trying to set up timer (IRQ0)
						 through the 8259A ...  
Nov 20 17:15:15 pc8-118 kernel: ..... (found pin 0) ...works.

But this does not seem to annoy the kernel.

Is there anyway to restore the 8254 to a valid state without rebooting ?


-- 
| 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-21 16:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-16 16:36 Strange lockup of the timer with 2.4.0-test10 SMP (and older) Benjamin Monate <Benjamin Monate
     [not found] ` <3A15CE34.EF2FE3CC@uow.edu.au>
2000-11-20 15:31   ` Benjamin Monate <Benjamin Monate
2000-11-20 18:26     ` Fort David
2000-11-20 18:11       ` Benjamin Monate <Benjamin Monate
2000-11-20 18:13         ` Alan Cox
2000-11-21 14:31           ` Maciej W. Rozycki
2000-11-21 16:27             ` Benjamin Monate <Benjamin Monate [this message]
2000-11-21 17:35               ` Maciej W. Rozycki
2000-11-22  9:45                 ` Benjamin Monate <Benjamin Monate
     [not found]                   ` <Pine.GSO.3.96.1001123183522.6381H-100000@delta.ds2.pg.gda.pl>
2000-11-23 19:39                     ` Benjamin Monate <Benjamin Monate
     [not found]                       ` <Pine.GSO.3.96.1001127154910.13774O-100000@delta.ds2.pg.gda.pl>
2000-11-27 16:58                         ` Benjamin Monate <Benjamin Monate

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=14874.41589.359267.717984@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