On Thu, 14 Dec 2006 09:55:38 +0100 (CET)
Igmar Palsenberg <[email protected]> wrote:
>
> > > Hmm.. Switching CONFIG_HZ from 1000 to 250 seems to 'fix' the problem.
> > > I haven't seen the issue in nearly a week now. This makes Andrew's theory
> > > about missing interrupts very likely.
> > >
> > > Andrew / others : Is there a way to find out if it *is* missing
> > > interrupts ?
> > >
> >
> > umm, nasty. What's in /proc/interrupts?
>
> See below. The other machine is mostly identifical, except for i8042
> missing (probably due to running an older kernel, or small differences in
> the kernel config).
>
Does the other machine have the same problems?
Are you able to rule out a hardware failure?
> [jdiict@lnx01 ~]$ cat /proc/interrupts
> CPU0 CPU1
> 0: 73702693 74509271 IO-APIC-edge timer
> 1: 1 1 IO-APIC-edge i8042
> 4: 2289 8389 IO-APIC-edge serial
> 8: 0 1 IO-APIC-edge rtc
> 9: 0 0 IO-APIC-fasteoi acpi
> 12: 3 1 IO-APIC-edge i8042
> 16: 203127788 0 IO-APIC-fasteoi uhci_hcd:usb2, eth0
> 17: 525 492 IO-APIC-fasteoi uhci_hcd:usb4
> 18: 13000070 67584889 IO-APIC-fasteoi arcmsr
> 19: 0 0 IO-APIC-fasteoi ehci_hcd:usb1
> 20: 0 0 IO-APIC-fasteoi uhci_hcd:usb3
> NMI: 0 0
> LOC: 148127756 148133476
> ERR: 0
> MIS: 0
The disk interrupt is unshared, which rules out a few software problems, I
guess.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
