Nicolas BERCHER wrote:
Thank you for your interest !
What kind of hardware (processor, chip-set) are you using?
CPU: Core 2 Duo [EMAIL PROTECTED]
Chipset: Intel MCP51 (see below for details !)
So, it seems your problem is not related to mine. And, since you have a dual
core CPU, it needs the local apic, as far as I understand. The kernel parameter
I mentioned is not applicable in your case.
What is the result of the following commands?
cat /proc/cpuinfo
lspci -vv
cat /proc/interrupts
For example, my notebook with AMD Turion 64 processor on an ATI RS480
IXP SB400 chip-set running with acpi needs the kernel parameter
'nolapic' or the clock would stop in CPU power state C3.
Since my first e-mail "Clocksource tsc unstable (delta = 51799116882
ns)", I enabled ACPI in the mainboard bios (MSI P6N SLI Platinum), but I
don't reaalyknow anything about ACPI.
Before that, I had some ACPI related warning/error messages, it seems
they have disapered since I enabled ACPI.
Here are the results of the command you asked:
----------------------------------------------------------------------------------------------------------------------------------
cat /proc/cpuinfo:
----------------------------------------------------------------------------------------------------------------------------------
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Core(TM)2 CPU 4300 @ 1.80GHz
stepping : 2
cpu MHz : 1203.000
cache size : 2048 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 2
<snip>
----------------------------------------------------------------------------------------------------------------------------------
lspci -vv
----------------------------------------------------------------------------------------------------------------------------------
<snip>
00:09.0 RAM memory: nVidia Corporation MCP51 Host Bridge (rev a2)
Subsystem: Micro-Star International Co., Ltd. Device 7350
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Capabilities: <access denied>
<snip>
Hardware as you described it already.
----------------------------------------------------------------------------------------------------------------------------------
cat /proc/interrupts
----------------------------------------------------------------------------------------------------------------------------------
CPU0 CPU1
0: 86 0 IO-APIC-edge timer
1: 2 0 IO-APIC-edge i8042
4: 2 0 IO-APIC-edge
6: 3 0 IO-APIC-edge floppy
7: 1 0 IO-APIC-edge parport0
8: 37 0 IO-APIC-edge rtc
9: 0 0 IO-APIC-fasteoi acpi
12: 4 0 IO-APIC-edge i8042
14: 445822 0 IO-APIC-edge ide0
16: 6184976 0 IO-APIC-fasteoi EMU10K1
17: 0 0 IO-APIC-fasteoi sata_sil24
18: 1737 0 IO-APIC-fasteoi firewire_ohci
19: 28286893 0 IO-APIC-fasteoi eth1, nvidia
20: 1634179 0 IO-APIC-fasteoi sata_nv
21: 382979 0 IO-APIC-fasteoi ohci_hcd:usb2
22: 4442859 0 IO-APIC-fasteoi ehci_hcd:usb1
23: 11167120 0 IO-APIC-fasteoi sata_nv, eth0
NMI: 0 0 Non-maskable interrupts
LOC: 31427276 27980641 Local timer interrupts
RES: 500712 747867 Rescheduling interrupts
CAL: 3279 5260 function call interrupts
TLB: 36152 42979 TLB shootdowns
TRM: 0 0 Thermal event interrupts
SPU: 0 0 Spurious interrupts
ERR: 1
MIS: 0
In the LOC line you can see the local timer interrupts. In case your system
slows down, maybe you could see some anomalies there or in the first line,
interrupt 0: "IO-APIC-edge timer", but I'm not an expert on this.
--
Regards,
Jörg-Volker.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
