From: Sidik Isani <lksi@cfht.hawaii.edu>
To: linux-kernel@vger.kernel.org
Subject: PROBLEM: Timer interrupt stopped (2.2.20, 2.4.x)
Date: Tue, 26 Mar 2002 00:48:00 -1000 [thread overview]
Message-ID: <200203261048.AAA12444@otto.cfht.hawaii.edu> (raw)
Hello -
We've been seeing intermittent (~weekly) lock-ups with our PCs which
never happened with the 2.2.16 kernel. Today the console on one
of them froze shortly after booting up to the text login (no X).
But this particular time, it still accepts ssh connections, so
is there anything I should check while it is in this state?
/proc/interrupts shows one very interesting thing:
CPU0
0: 63444 IO-APIC-edge timer <-- Not incrementing anymore!
1: 2 IO-APIC-edge keyboard
2: 0 XT-PIC cascade
8: 0 IO-APIC-edge rtc
12: 245 IO-APIC-edge PS/2 Mouse
13: 1 XT-PIC fpu
14: 858 IO-APIC-edge ide0
15: 7 IO-APIC-edge ide1
19: 110413 IO-APIC-level usb-uhci, eth0
NMI: 0
ERR: 0
Mouse and keyboard interrupts are also not incrementing, but the disk
and network interrupts are. The kernel seems happy (no errors logged.)
Linux version 2.2.20-smp #1 SMP Sun Mar 24 18:35:47 HST 2002
Built with: gcc 2.7.2.3, binutils 2.11.90.0.8
Patches: Vanilla tree plus DEVFS and RAID 0.90
Machine: Dell Precision 210 Workstation
Motherboard: Dell, 440BX based (supports dual processors)
Processor: Single P-III 500 MHz
PCI Cards: Only an NVidia graphics card (but X was never started yet.)
Memory: 1GB ECC
Disks: 2x13GB Maxtor IDE's on hda,hdb
The same thing happened before with a 2.4 kernel a few months ago.
At that time the machine had 512MB of RAM. If anything useful can
be done to track down the problem while the machine is like this,
please let me know and I'll try before rebooting tomorrow.
Thanks,
- Sidik
reply other threads:[~2002-03-26 10:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200203261048.AAA12444@otto.cfht.hawaii.edu \
--to=lksi@cfht.hawaii.edu \
--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®