constant_tsc and TSC unstable

public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed

* constant_tsc and TSC unstable
@ 2007-11-29 16:11 Paul Rolland
  2007-11-29 19:04 ` H. Peter Anvin
                   ` (2 more replies)
  0 siblings, 3 replies; 10+ messages in thread
From: Paul Rolland @ 2007-11-29 16:11 UTC (permalink / raw)
  To: Linux Kernel; +Cc: rol

Hello,

I've a machine with a Core2Duo CPU. /proc/cpuinfo reports the flag
constant_tsc, but at boot time, I have the log :

...
Total of 2 processors activated (6919.15 BogoMIPS).
ENABLING IO-APIC IRQs
..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
checking TSC synchronization [CPU#0 -> CPU#1]:
Measured 3978592228 cycles TSC warp between CPUs, turning off TSC clock.
Marking TSC unstable due to: check_tsc_sync_source failed.
Brought up 2 CPUs
...

This machine is running 2.6.23.1-21.fc7. I know I should report to Fedora,
but I was wondering if this is a bug or a feature ;)

Regards,
Paul

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: constant_tsc and TSC unstable
  2007-11-29 16:11 constant_tsc and TSC unstable Paul Rolland
@ 2007-11-29 19:04 ` H. Peter Anvin
  2007-11-29 21:26   ` Michael Tokarev
  2007-11-29 21:36   ` Patrick McHardy
  2007-11-29 23:29 ` Pallipadi, Venkatesh
  2007-11-30  0:30 ` Frans Pop
  2 siblings, 2 replies; 10+ messages in thread
From: H. Peter Anvin @ 2007-11-29 19:04 UTC (permalink / raw)
  To: "Paul Rolland (ポール・ロラン)"
  Cc: Linux Kernel

Paul Rolland (ポール・ロラン) wrote:
> Hello,
> 
> I've a machine with a Core2Duo CPU. /proc/cpuinfo reports the flag
> constant_tsc, but at boot time, I have the log :
> 
> ...
> Total of 2 processors activated (6919.15 BogoMIPS).
> ENABLING IO-APIC IRQs
> ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
> checking TSC synchronization [CPU#0 -> CPU#1]:
> Measured 3978592228 cycles TSC warp between CPUs, turning off TSC clock.
> Marking TSC unstable due to: check_tsc_sync_source failed.
> Brought up 2 CPUs
> ...
> 
> This machine is running 2.6.23.1-21.fc7. I know I should report to Fedora,
> but I was wondering if this is a bug or a feature ;)
> 

constant_tsc means the TSC doesn't change with CPU core frequency.

The problem you're having is that the TSCs of your two cores are 
completely different, over a second apart.  This is a bug, unrelated to 
constant_tsc.

	-hpa




^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: constant_tsc and TSC unstable
  2007-11-29 19:04 ` H. Peter Anvin
@ 2007-11-29 21:26   ` Michael Tokarev
  2007-11-30  6:59     ` Paul Rolland
  2007-11-29 21:36   ` Patrick McHardy
  1 sibling, 1 reply; 10+ messages in thread
From: Michael Tokarev @ 2007-11-29 21:26 UTC (permalink / raw)
  To: H. Peter Anvin
  Cc: "Paul Rolland (ポール・ロラン)",
	Linux Kernel

H. Peter Anvin wrote:
> Paul Rolland (ポール・ロラン) wrote:
[]
>> Measured 3978592228 cycles TSC warp between CPUs, turning off TSC clock.
>> Marking TSC unstable due to: check_tsc_sync_source failed.
[]
>> but I was wondering if this is a bug or a feature ;)

> The problem you're having is that the TSCs of your two cores are
> completely different, over a second apart.  This is a bug, unrelated to
> constant_tsc.

A bug in where - in the CPU or in kernel?

The thing is that all our dual-core machines shows something like
that.

For example, dualcore PentiumD machine:
Nov  7 20:23:56 paltus kernel: Linux version 2.6.22-i686smp (mjt@paltus.tls.msk.ru) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #2.6.22.12 SMP Wed Nov 7 20:02:14 MSK 2007
...
Nov  7 20:23:56 paltus kernel: checking TSC synchronization [CPU#0 -> CPU#1]:
Nov  7 20:23:56 paltus kernel: Measured 112 cycles TSC warp between CPUs, turning off TSC clock.
Nov  7 20:23:56 paltus kernel: Marking TSC unstable due to: check_tsc_sync_source failed.
Nov  7 20:23:56 paltus kernel: Brought up 2 CPUs

(not that huge difference as Paul reported, but still "unstable".
The same happens with 2.6.23)

Note that once TSC is disabled (it's using "jiffies" as far
as I can see), ntpd constantly speeds up and slows down the
clock, it jumps +/- 0.5sec every several minutes or hours -
I guess that's when ntpd process gets moved from one core
to another for whatever reason.  And an interesting thing
is that with 64bits kernel this TSC problem does not occur
on this very machine.

Something similar is reported on AMD X2 64 machines as well --
can't check right now.

Thanks.

/mjt

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: constant_tsc and TSC unstable
  2007-11-29 21:26   ` Michael Tokarev
@ 2007-11-30  6:59     ` Paul Rolland
  2007-11-30  7:04       ` H. Peter Anvin
  0 siblings, 1 reply; 10+ messages in thread
From: Paul Rolland @ 2007-11-30  6:59 UTC (permalink / raw)
  To: Michael Tokarev; +Cc: H. Peter Anvin, Linux Kernel, rol

Hello,

On Fri, 30 Nov 2007 00:26:47 +0300
Michael Tokarev <mjt@tls.msk.ru> wrote:

> H. Peter Anvin wrote:
> > Paul Rolland (ポール・ロラン) wrote:
> []
> >> Measured 3978592228 cycles TSC warp between CPUs, turning off TSC clock.
> >> Marking TSC unstable due to: check_tsc_sync_source failed.
> []
> >> but I was wondering if this is a bug or a feature ;)
> 
> > The problem you're having is that the TSCs of your two cores are
> > completely different, over a second apart.  This is a bug, unrelated to
> > constant_tsc.
> 
> A bug in where - in the CPU or in kernel?
Good question !
 
> The thing is that all our dual-core machines shows something like
> that.
> 
> (not that huge difference as Paul reported, but still "unstable".
> The same happens with 2.6.23)
I've been checking my logs, and the difference is quite constant and
huge :
[root@tux log]# grep 'cycles TSC warp' messages*
messages:Nov 26 08:27:56 tux kernel: Measured 4078687691 cycles TSC warp between C
PUs, turning off TSC clock.
messages:Nov 26 17:21:21 tux kernel: Measured 3978592228 cycles TSC warp between C
PUs, turning off TSC clock.
messages.1:Nov 18 22:52:23 tux kernel: Measured 4063102940 cycles TSC warp between
 CPUs, turning off TSC clock.
messages.1:Nov 19 07:19:02 tux kernel: Measured 4057192061 cycles TSC warp between
 CPUs, turning off TSC clock.
messages.1:Nov 23 20:50:12 tux kernel: Measured 4064589321 cycles TSC warp between
 CPUs, turning off TSC clock.
messages.2:Nov 12 08:06:44 tux kernel: Measured 4072130361 cycles TSC warp between
 CPUs, turning off TSC clock.
messages.2:Nov 13 19:42:47 tux kernel: Measured 4049899451 cycles TSC warp between
 CPUs, turning off TSC clock.
messages.2:Nov 17 09:27:22 tux kernel: Measured 4066629060 cycles TSC warp between
 CPUs, turning off TSC clock.
messages.3:Nov  5 08:25:08 tux kernel: Measured 4086386109 cycles TSC warp between
 CPUs, turning off TSC clock.
messages.3:Nov  8 13:07:08 tux kernel: Measured 4041945934 cycles TSC warp between
 CPUs, turning off TSC clock.
messages.3:Nov  9 23:31:24 tux kernel: Measured 4092303059 cycles TSC warp between
 CPUs, turning off TSC clock.
messages.4:Oct 29 07:28:23 tux kernel: Measured 4096946373 cycles TSC warp between
 CPUs, turning off TSC clock.
messages.4:Oct 31 17:07:21 tux kernel: Measured 4046765372 cycles TSC warp between
 CPUs, turning off TSC clock.
messages.4:Oct 31 17:15:09 tux kernel: Measured 4039328228 cycles TSC warp between
 CPUs, turning off TSC clock.
messages.4:Oct 31 23:19:00 tux kernel: Measured 4069714246 cycles TSC warp between
 CPUs, turning off TSC clock.
messages.4:Nov  1 20:33:02 tux kernel: Measured 4088199726 cycles TSC warp between
 CPUs, turning off TSC clock.
messages.4:Nov  2 11:53:17 tux kernel: Measured 4079927527 cycles TSC warp between
 CPUs, turning off TSC clock.
messages.4:Nov  3 09:37:16 tux kernel: Measured 4071112656 cycles TSC warp between
 CPUs, turning off TSC clock.
messages.4:Nov  3 10:51:29 tux kernel: Measured 3986266219 cycles TSC warp between
 CPUs, turning off TSC clock.
messages.4:Nov  4 18:14:56 tux kernel: Measured 4074214144 cycles TSC warp between
 CPUs, turning off TSC clock.

> Note that once TSC is disabled (it's using "jiffies" as far
> as I can see), ntpd constantly speeds up and slows down the
> clock, it jumps +/- 0.5sec every several minutes or hours -
> I guess that's when ntpd process gets moved from one core
> to another for whatever reason.  And an interesting thing
> is that with 64bits kernel this TSC problem does not occur
> on this very machine.
Hmmmm.... That could make it a problem related to kernel rather than CPU.
 
> Something similar is reported on AMD X2 64 machines as well --
> can't check right now.
If I recall correctly, issues with AMD X2 where related to TSC being
independant for each core and not constant (speed depending of C state).
But the reason I raise the issue is that the Core2 reports constant TSC,
so there is (IMHO) no reason for that.

Paul


^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: constant_tsc and TSC unstable
  2007-11-30  6:59     ` Paul Rolland
@ 2007-11-30  7:04       ` H. Peter Anvin
  0 siblings, 0 replies; 10+ messages in thread
From: H. Peter Anvin @ 2007-11-30  7:04 UTC (permalink / raw)
  To: "Paul Rolland (ポール・ロラン)"
  Cc: Michael Tokarev, Linux Kernel

Paul Rolland (ポール・ロラン) wrote:
> 
>> Note that once TSC is disabled (it's using "jiffies" as far
>> as I can see), ntpd constantly speeds up and slows down the
>> clock, it jumps +/- 0.5sec every several minutes or hours -
>> I guess that's when ntpd process gets moved from one core
>> to another for whatever reason.  And an interesting thing
>> is that with 64bits kernel this TSC problem does not occur
>> on this very machine.
> Hmmmm.... That could make it a problem related to kernel rather than CPU.
>  
>> Something similar is reported on AMD X2 64 machines as well --
>> can't check right now.
> If I recall correctly, issues with AMD X2 where related to TSC being
> independant for each core and not constant (speed depending of C state).
> But the reason I raise the issue is that the Core2 reports constant TSC,
> so there is (IMHO) no reason for that.
> 

Well, "constant" doesn't mean "synchronized", but it might very well be 
that the Core2 could really benefit from synchronizing the TSCs manually 
like we used to.

On the other hand, I notice that most of the TSC warp values are 
relatively close to 2^32, so this could be a specific bug.

	-hpa


^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: constant_tsc and TSC unstable
  2007-11-29 19:04 ` H. Peter Anvin
  2007-11-29 21:26   ` Michael Tokarev
@ 2007-11-29 21:36   ` Patrick McHardy
  1 sibling, 0 replies; 10+ messages in thread
From: Patrick McHardy @ 2007-11-29 21:36 UTC (permalink / raw)
  To: H. Peter Anvin
  Cc: "Paul Rolland (ポール・ロラン)",
	Linux Kernel

H. Peter Anvin wrote:
> Paul Rolland (ポール・ロラン) wrote:
>> Hello,
>>
>> I've a machine with a Core2Duo CPU. /proc/cpuinfo reports the flag
>> constant_tsc, but at boot time, I have the log :
>>
>> ...
>> Total of 2 processors activated (6919.15 BogoMIPS).
>> ENABLING IO-APIC IRQs
>> ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
>> checking TSC synchronization [CPU#0 -> CPU#1]:
>> Measured 3978592228 cycles TSC warp between CPUs, turning off TSC clock.
>> Marking TSC unstable due to: check_tsc_sync_source failed.
>> Brought up 2 CPUs
>> ...
>>
>> This machine is running 2.6.23.1-21.fc7. I know I should report to 
>> Fedora,
>> but I was wondering if this is a bug or a feature ;)
>>
>
> constant_tsc means the TSC doesn't change with CPU core frequency.
>
> The problem you're having is that the TSCs of your two cores are 
> completely different, over a second apart.  This is a bug, unrelated 
> to constant_tsc.

On my core2duo I noticed that the TSC of the second core doesn't
start counting until the CPU is activated. Since they're not
synchronized manually anymore this makes the TSC check fail.



^ permalink raw reply	[flat|nested] 10+ messages in thread

* RE: constant_tsc and TSC unstable
  2007-11-29 16:11 constant_tsc and TSC unstable Paul Rolland
  2007-11-29 19:04 ` H. Peter Anvin
@ 2007-11-29 23:29 ` Pallipadi, Venkatesh
  2007-11-30  6:52   ` Paul Rolland (ポール・ロラン)
  2007-11-30  0:30 ` Frans Pop
  2 siblings, 1 reply; 10+ messages in thread
From: Pallipadi, Venkatesh @ 2007-11-29 23:29 UTC (permalink / raw)
  To: Paul Rolland (ポール・ロラン),
	Linux Kernel
  Cc: Siddha, Suresh B

 

>-----Original Message-----
>From: linux-kernel-owner@vger.kernel.org 
>[mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of Paul 
>Rolland (???・???)
>Sent: Thursday, November 29, 2007 8:12 AM
>To: Linux Kernel
>Cc: rol@witbe.net
>Subject: constant_tsc and TSC unstable
>
>Hello,
>
>I've a machine with a Core2Duo CPU. /proc/cpuinfo reports the flag
>constant_tsc, but at boot time, I have the log :
>
>...
>Total of 2 processors activated (6919.15 BogoMIPS).
>ENABLING IO-APIC IRQs
>..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
>checking TSC synchronization [CPU#0 -> CPU#1]:
>Measured 3978592228 cycles TSC warp between CPUs, turning off 
>TSC clock.
>Marking TSC unstable due to: check_tsc_sync_source failed.
>Brought up 2 CPUs
>...
>
>This machine is running 2.6.23.1-21.fc7. I know I should 
>report to Fedora,
>but I was wondering if this is a bug or a feature ;)
>

TSCs on Core 2 Duo are supposed to be in sync unless CPU supports deep idle states like C2, C3. Can you send the full /proc/cpuinfo and full dmesg.

Thanks,
Venki 

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: constant_tsc and TSC unstable
  2007-11-29 23:29 ` Pallipadi, Venkatesh
@ 2007-11-30  6:52   ` Paul Rolland (ポール・ロラン)
  2007-12-06  0:35     ` Pallipadi, Venkatesh
  0 siblings, 1 reply; 10+ messages in thread
From: Paul Rolland (ポール・ロラン) @ 2007-11-30  6:52 UTC (permalink / raw)
  To: Pallipadi, Venkatesh; +Cc: Linux Kernel, Siddha, Suresh B, rol

[-- Attachment #1: Type: text/plain, Size: 1839 bytes --]

Hello,

On Thu, 29 Nov 2007 15:29:49 -0800
"Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com> wrote:



> TSCs on Core 2 Duo are supposed to be in sync unless CPU supports deep idle
> states like C2, C3. Can you send the full /proc/cpuinfo and full dmesg.
> 
Sure I can...
[root@tux log]# cat /proc/cpuinfo 
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 15
model name      : Intel(R) Core(TM)2 CPU         T5300  @ 1.73GHz
stepping        : 2
cpu MHz         : 800.000
cache size      : 2048 KB
physical id     : 0
siblings        : 2
core id         : 0
cpu cores       : 2
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 10
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat ps
e36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmo
n pebs bts pni monitor ds_cpl est tm2 ssse3 cx16 xtpr lahf_lm
bogomips        : 3461.13
clflush size    : 64

processor       : 1
vendor_id       : GenuineIntel
cpu family      : 6
model           : 15
model name      : Intel(R) Core(TM)2 CPU         T5300  @ 1.73GHz
stepping        : 2
cpu MHz         : 800.000
cache size      : 2048 KB
physical id     : 0
siblings        : 2
core id         : 1
cpu cores       : 2
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 10
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat ps
e36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmo
n pebs bts pni monitor ds_cpl est tm2 ssse3 cx16 xtpr lahf_lm
bogomips        : 3458.02
clflush size    : 64

Regards,
Paul

[-- Attachment #2: dmesg --]
[-- Type: application/octet-stream, Size: 30696 bytes --]

Nov 26 08:27:56 tux kernel: Linux version 2.6.23.1-21.fc7 (kojibuilder@xenbuilder4.fedora.phx.redhat.com) (gcc version 4.1.2 20070925 (Red Hat 4.1.2-27)) #1 SMP Thu Nov 1 21:09:24 EDT 2007
Nov 26 08:27:56 tux kernel: BIOS-provided physical RAM map:
Nov 26 08:27:56 tux kernel:  BIOS-e820: 0000000000000000 - 000000000009f000 (usable)
Nov 26 08:27:56 tux kernel:  BIOS-e820: 000000000009f000 - 00000000000a0000 (reserved)
Nov 26 08:27:56 tux kernel:  BIOS-e820: 0000000000100000 - 000000007f6d3400 (usable)
Nov 26 08:27:56 tux kernel:  BIOS-e820: 000000007f6d3400 - 0000000080000000 (reserved)
Nov 26 08:27:56 tux kernel:  BIOS-e820: 00000000f0000000 - 00000000f4007000 (reserved)
Nov 26 08:27:56 tux kernel:  BIOS-e820: 00000000f4008000 - 00000000f400c000 (reserved)
Nov 26 08:27:56 tux kernel:  BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved)
Nov 26 08:27:56 tux kernel:  BIOS-e820: 00000000fed20000 - 00000000feda0000 (reserved)
Nov 26 08:27:56 tux kernel:  BIOS-e820: 00000000fee00000 - 00000000fee10000 (reserved)
Nov 26 08:27:56 tux kernel:  BIOS-e820: 00000000ffb00000 - 0000000100000000 (reserved)
Nov 26 08:27:56 tux kernel: 1142MB HIGHMEM available.
Nov 26 08:27:56 tux kernel: 896MB LOWMEM available.
Nov 26 08:27:56 tux kernel: Using x86 segment limits to approximate NX protection
Nov 26 08:27:56 tux kernel: Zone PFN ranges:
Nov 26 08:27:56 tux kernel:   DMA             0 ->     4096
Nov 26 08:27:56 tux kernel:   Normal       4096 ->   229376
Nov 26 08:27:56 tux kernel:   HighMem    229376 ->   521939
Nov 26 08:27:56 tux kernel: Movable zone start PFN for each node
Nov 26 08:27:56 tux kernel: early_node_map[1] active PFN ranges
Nov 26 08:27:56 tux kernel:     0:        0 ->   521939
Nov 26 08:27:56 tux kernel: DMI 2.4 present.
Nov 26 08:27:56 tux kernel: Using APIC driver default
Nov 26 08:27:56 tux kernel: ACPI: RSDP 000FC1D0, 0014 (r0 DELL  )
Nov 26 08:27:56 tux kernel: ACPI: RSDT 7F6D39CD, 0040 (r1 DELL    M07     27D70414 ASL        61)
Nov 26 08:27:56 tux kernel: ACPI: FACP 7F6D4800, 0074 (r1 DELL    M07     27D70414 ASL        61)
Nov 26 08:27:56 tux kernel: ACPI: DSDT 7F6D5400, 4766 (r1 INT430 SYSFexxx     1001 INTL 20050624)
Nov 26 08:27:56 tux kernel: ACPI: FACS 7F6E3C00, 0040
Nov 26 08:27:56 tux kernel: ACPI: HPET 7F6D4F00, 0038 (r1 DELL    M07            1 ASL        61)
Nov 26 08:27:56 tux kernel: ACPI: APIC 7F6D5000, 0068 (r1 DELL    M07     27D70414 ASL        47)
Nov 26 08:27:56 tux kernel: ACPI: MCFG 7F6D4FC0, 003E (r16 DELL    M07     27D70414 ASL        61)
Nov 26 08:27:56 tux kernel: ACPI: SLIC 7F6D509C, 0176 (r1 DELL    M07     27D70414 ASL        61)
Nov 26 08:27:56 tux kernel: ACPI: BOOT 7F6D4BC0, 0028 (r1 DELL    M07     27D70414 ASL        61)
Nov 26 08:27:56 tux kernel: ACPI: SSDT 7F6D3A0D, 04DC (r1  PmRef    CpuPm     3000 INTL 20050624)
Nov 26 08:27:56 tux kernel: ACPI: PM-Timer IO Port: 0x1008
Nov 26 08:27:56 tux kernel: ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Nov 26 08:27:56 tux kernel: Processor #0 6:15 APIC version 20
Nov 26 08:27:56 tux kernel: ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Nov 26 08:27:56 tux kernel: Processor #1 6:15 APIC version 20
Nov 26 08:27:56 tux kernel: ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Nov 26 08:27:56 tux kernel: ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Nov 26 08:27:56 tux kernel: ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
Nov 26 08:27:56 tux kernel: IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
Nov 26 08:27:56 tux kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Nov 26 08:27:56 tux kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Nov 26 08:27:56 tux kernel: Enabling APIC mode:  Flat.  Using 1 I/O APICs
Nov 26 08:27:56 tux kernel: ACPI: HPET id: 0x8086a201 base: 0xfed00000
Nov 26 08:27:56 tux kernel: Using ACPI (MADT) for SMP configuration information
Nov 26 08:27:56 tux kernel: Allocating PCI resources starting at 88000000 (gap: 80000000:70000000)
Nov 26 08:27:56 tux kernel: swsusp: Registered nosave memory region: 000000000009f000 - 00000000000a0000
Nov 26 08:27:56 tux kernel: swsusp: Registered nosave memory region: 00000000000a0000 - 0000000000100000
Nov 26 08:27:56 tux kernel: Built 1 zonelists in Zone order.  Total pages: 517862
Nov 26 08:27:56 tux kernel: Kernel command line: ro root=LABEL=/ rhgb quiet selinux=0
Nov 26 08:27:56 tux kernel: Enabling fast FPU save and restore... done.
Nov 26 08:27:56 tux kernel: Enabling unmasked SIMD FPU exception support... done.
Nov 26 08:27:56 tux kernel: Initializing CPU#0
Nov 26 08:27:56 tux kernel: CPU 0 irqstacks, hard=c07a5000 soft=c0785000
Nov 26 08:27:56 tux kernel: PID hash table entries: 4096 (order: 12, 16384 bytes)
Nov 26 08:27:56 tux kernel: Detected 1729.065 MHz processor.
Nov 26 08:27:56 tux kernel: Console: colour VGA+ 80x25
Nov 26 08:27:56 tux kernel: console [tty0] enabled
Nov 26 08:27:56 tux kernel: Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Nov 26 08:27:56 tux kernel: Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Nov 26 08:27:56 tux kernel: Memory: 2061980k/2087756k available (2175k kernel code, 24460k reserved, 1114k data, 280k init, 1170252k highmem)
Nov 26 08:27:56 tux kernel: virtual kernel memory layout:
Nov 26 08:27:56 tux kernel:     fixmap  : 0xffc53000 - 0xfffff000   (3760 kB)
Nov 26 08:27:56 tux kernel:     pkmap   : 0xff800000 - 0xffc00000   (4096 kB)
Nov 26 08:27:56 tux kernel:     vmalloc : 0xf8800000 - 0xff7fe000   ( 111 MB)
Nov 26 08:27:56 tux kernel:     lowmem  : 0xc0000000 - 0xf8000000   ( 896 MB)
Nov 26 08:27:56 tux kernel:       .init : 0xc073c000 - 0xc0782000   ( 280 kB)
Nov 26 08:27:56 tux kernel:       .data : 0xc061fcc5 - 0xc0736544   (1114 kB)
Nov 26 08:27:56 tux kernel:       .text : 0xc0400000 - 0xc061fcc5   (2175 kB)
Nov 26 08:27:56 tux kernel: Checking if this processor honours the WP bit even in supervisor mode... Ok.
Nov 26 08:27:56 tux kernel: SLUB: Genslabs=22, HWalign=64, Order=0-1, MinObjects=4, CPUs=2, Nodes=1
Nov 26 08:27:56 tux kernel: hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
Nov 26 08:27:56 tux kernel: hpet0: 3 64-bit timers, 14318180 Hz
Nov 26 08:27:56 tux kernel: Calibrating delay using timer specific routine.. 3461.12 BogoMIPS (lpj=1730564)
Nov 26 08:27:56 tux kernel: Security Framework v1.0.0 initialized
Nov 26 08:27:56 tux kernel: SELinux:  Disabled at boot.
Nov 26 08:27:56 tux kernel: Capability LSM initialized
Nov 26 08:27:56 tux kernel: Mount-cache hash table entries: 512
Nov 26 08:27:56 tux kernel: monitor/mwait feature present.
Nov 26 08:27:56 tux kernel: using mwait in idle threads.
Nov 26 08:27:56 tux kernel: CPU: L1 I cache: 32K, L1 D cache: 32K
Nov 26 08:27:56 tux kernel: CPU: L2 cache: 2048K
Nov 26 08:27:56 tux kernel: CPU: Physical Processor ID: 0
Nov 26 08:27:56 tux kernel: CPU: Processor Core ID: 0
Nov 26 08:27:56 tux kernel: Intel machine check architecture supported.
Nov 26 08:27:56 tux kernel: Intel machine check reporting enabled on CPU#0.
Nov 26 08:27:56 tux kernel: Compat vDSO mapped to ffffe000.
Nov 26 08:27:56 tux kernel: Checking 'hlt' instruction... OK.
Nov 26 08:27:56 tux kernel: SMP alternatives: switching to UP code
Nov 26 08:27:56 tux kernel: ACPI: Core revision 20070126
Nov 26 08:27:56 tux kernel: CPU0: Intel(R) Core(TM)2 CPU         T5300  @ 1.73GHz stepping 02
Nov 26 08:27:56 tux kernel: SMP alternatives: switching to SMP code
Nov 26 08:27:56 tux kernel: Booting processor 1/1 eip 3000
Nov 26 08:27:56 tux kernel: CPU 1 irqstacks, hard=c07a6000 soft=c0786000
Nov 26 08:27:56 tux kernel: Initializing CPU#1
Nov 26 08:27:56 tux kernel: Calibrating delay using timer specific routine.. 3458.01 BogoMIPS (lpj=1729007)
Nov 26 08:27:56 tux kernel: monitor/mwait feature present.
Nov 26 08:27:56 tux kernel: CPU: L1 I cache: 32K, L1 D cache: 32K
Nov 26 08:27:56 tux kernel: CPU: L2 cache: 2048K
Nov 26 08:27:56 tux kernel: CPU: Physical Processor ID: 0
Nov 26 08:27:56 tux kernel: CPU: Processor Core ID: 1
Nov 26 08:27:56 tux kernel: Intel machine check architecture supported.
Nov 26 08:27:56 tux kernel: Intel machine check reporting enabled on CPU#1.
Nov 26 08:27:56 tux kernel: CPU1: Intel(R) Core(TM)2 CPU         T5300  @ 1.73GHz stepping 02
Nov 26 08:27:56 tux kernel: Total of 2 processors activated (6919.14 BogoMIPS).
Nov 26 08:27:56 tux kernel: ENABLING IO-APIC IRQs
Nov 26 08:27:56 tux kernel: ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
Nov 26 08:27:56 tux kernel: checking TSC synchronization [CPU#0 -> CPU#1]:
Nov 26 08:27:56 tux kernel: Measured 4078687691 cycles TSC warp between CPUs, turning off TSC clock.
Nov 26 08:27:56 tux kernel: Marking TSC unstable due to: check_tsc_sync_source failed.
Nov 26 08:27:56 tux kernel: Brought up 2 CPUs
Nov 26 08:27:56 tux kernel: Booting paravirtualized kernel on bare hardware
Nov 26 08:27:56 tux kernel: Time:  7:26:15  Date: 11/26/07
Nov 26 08:27:56 tux kernel: NET: Registered protocol family 16
Nov 26 08:27:56 tux kernel: No dock devices found.
Nov 26 08:27:56 tux kernel: ACPI: bus type pci registered
Nov 26 08:27:56 tux kernel: PCI: PCI BIOS revision 2.10 entry at 0xfb336, last bus=13
Nov 26 08:27:56 tux kernel: PCI: Using configuration type 1
Nov 26 08:27:56 tux kernel: Setting up standard PCI resources
Nov 26 08:27:56 tux kernel: ACPI: Interpreter enabled
Nov 26 08:27:56 tux kernel: ACPI: (supports S0 S3 S4 S5)
Nov 26 08:27:56 tux kernel: ACPI: Using IOAPIC for interrupt routing
Nov 26 08:27:56 tux kernel: ACPI: PCI Root Bridge [PCI0] (0000:00)
Nov 26 08:27:56 tux kernel: PCI quirk: region 1000-107f claimed by ICH6 ACPI/GPIO/TCO
Nov 26 08:27:56 tux kernel: PCI quirk: region 1080-10bf claimed by ICH6 GPIO
Nov 26 08:27:56 tux kernel: PCI: Transparent bridge - 0000:00:1e.0
Nov 26 08:27:56 tux kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 9 10 *11)
Nov 26 08:27:56 tux kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 5 7) *4
Nov 26 08:27:56 tux kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 9 10 *11)
Nov 26 08:27:56 tux kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 5 7 9 10 11) *3
Nov 26 08:27:56 tux kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 *9 10 11 12 14 15)
Nov 26 08:27:56 tux kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
Nov 26 08:27:56 tux kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 *7 9 10 11 12 14 15)
Nov 26 08:27:56 tux kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 *5 6 7 9 10 11 12 14 15)
Nov 26 08:27:56 tux kernel: Linux Plug and Play Support v0.97 (c) Adam Belay
Nov 26 08:27:56 tux kernel: pnp: PnP ACPI init
Nov 26 08:27:56 tux kernel: ACPI: bus type pnp registered
Nov 26 08:27:56 tux kernel: pnp: PnP ACPI: found 12 devices
Nov 26 08:27:56 tux kernel: ACPI: ACPI bus type pnp unregistered
Nov 26 08:27:56 tux kernel: usbcore: registered new interface driver usbfs
Nov 26 08:27:56 tux kernel: usbcore: registered new interface driver hub
Nov 26 08:27:56 tux kernel: usbcore: registered new device driver usb
Nov 26 08:27:56 tux kernel: PCI: Using ACPI for IRQ routing
Nov 26 08:27:56 tux kernel: PCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a report
Nov 26 08:27:56 tux kernel: NetLabel: Initializing
Nov 26 08:27:56 tux kernel: NetLabel:  domain hash size = 128
Nov 26 08:27:56 tux kernel: NetLabel:  protocols = UNLABELED CIPSOv4
Nov 26 08:27:56 tux kernel: NetLabel:  unlabeled traffic allowed by default
Nov 26 08:27:56 tux kernel: Time: hpet clocksource has been installed.
Nov 26 08:27:56 tux kernel: Switched to high resolution mode on CPU 0
Nov 26 08:27:56 tux kernel: Switched to high resolution mode on CPU 1
Nov 26 08:27:56 tux kernel: pnp: 00:00: iomem range 0x0-0x9fbff could not be reserved
Nov 26 08:27:56 tux kernel: pnp: 00:00: iomem range 0x9fc00-0x9ffff could not be reserved
Nov 26 08:27:56 tux kernel: pnp: 00:00: iomem range 0xc0000-0xcffff could not be reserved
Nov 26 08:27:56 tux kernel: pnp: 00:00: iomem range 0xe0000-0xfffff could not be reserved
Nov 26 08:27:56 tux kernel: pnp: 00:02: ioport range 0x4d0-0x4d1 has been reserved
Nov 26 08:27:56 tux kernel: pnp: 00:02: ioport range 0x1000-0x1005 has been reserved
Nov 26 08:27:56 tux kernel: pnp: 00:02: ioport range 0x1008-0x100f has been reserved
Nov 26 08:27:56 tux kernel: pnp: 00:03: ioport range 0xf400-0xf4fe has been reserved
Nov 26 08:27:56 tux kernel: pnp: 00:03: ioport range 0x1006-0x1007 has been reserved
Nov 26 08:27:56 tux kernel: pnp: 00:03: ioport range 0x100a-0x1059 could not be reserved
Nov 26 08:27:56 tux kernel: pnp: 00:03: ioport range 0x1060-0x107f has been reserved
Nov 26 08:27:56 tux kernel: pnp: 00:03: ioport range 0x1080-0x10bf has been reserved
Nov 26 08:27:56 tux kernel: pnp: 00:03: ioport range 0x10c0-0x10df has been reserved
Nov 26 08:27:56 tux kernel: pnp: 00:08: ioport range 0xc80-0xcff could not be reserved
Nov 26 08:27:56 tux kernel: pnp: 00:08: ioport range 0x910-0x91f has been reserved
Nov 26 08:27:56 tux kernel: pnp: 00:08: ioport range 0x920-0x92f has been reserved
Nov 26 08:27:56 tux kernel: pnp: 00:08: ioport range 0xcb0-0xcbf has been reserved
Nov 26 08:27:56 tux kernel: pnp: 00:08: ioport range 0x930-0x97f has been reserved
Nov 26 08:27:56 tux kernel: pnp: 00:0b: iomem range 0xfed00000-0xfed003ff has been reserved
Nov 26 08:27:56 tux kernel: PCI: Bridge: 0000:00:1c.0
Nov 26 08:27:56 tux kernel:   IO window: disabled.
Nov 26 08:27:56 tux kernel:   MEM window: efd00000-efdfffff
Nov 26 08:27:56 tux kernel:   PREFETCH window: disabled.
Nov 26 08:27:56 tux kernel: PCI: Bridge: 0000:00:1c.3
Nov 26 08:27:56 tux kernel:   IO window: d000-dfff
Nov 26 08:27:56 tux kernel:   MEM window: efa00000-efcfffff
Nov 26 08:27:56 tux kernel:   PREFETCH window: e0000000-e01fffff
Nov 26 08:27:56 tux kernel: PCI: Bridge: 0000:00:1e.0
Nov 26 08:27:56 tux kernel:   IO window: disabled.
Nov 26 08:27:56 tux kernel:   MEM window: ef900000-ef9fffff
Nov 26 08:27:56 tux kernel:   PREFETCH window: disabled.
Nov 26 08:27:56 tux kernel: ACPI: PCI Interrupt 0000:00:1c.0[A] -> GSI 16 (level, low) -> IRQ 16
Nov 26 08:27:56 tux kernel: ACPI: PCI Interrupt 0000:00:1c.3[D] -> GSI 19 (level, low) -> IRQ 17
Nov 26 08:27:56 tux kernel: NET: Registered protocol family 2
Nov 26 08:27:56 tux kernel: IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
Nov 26 08:27:56 tux kernel: TCP established hash table entries: 131072 (order: 8, 1572864 bytes)
Nov 26 08:27:56 tux kernel: TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
Nov 26 08:27:56 tux kernel: TCP: Hash tables configured (established 131072 bind 65536)
Nov 26 08:27:56 tux automount[2270]: lookup_read_master: lookup(nisplus): couldn't locat nis+ table auto.master
Nov 26 08:27:56 tux kernel: TCP reno registered
Nov 26 08:27:56 tux kernel: checking if image is initramfs... it is
Nov 26 08:27:56 tux kernel: Freeing initrd memory: 2814k freed
Nov 26 08:27:56 tux kernel: Simple Boot Flag value 0x89 read from CMOS RAM was invalid
Nov 26 08:27:56 tux kernel: Simple Boot Flag at 0x79 set to 0x1
Nov 26 08:27:56 tux kernel: apm: BIOS not found.
Nov 26 08:27:56 tux kernel: audit: initializing netlink socket (disabled)
Nov 26 08:27:56 tux kernel: audit(1196061975.586:1): initialized
Nov 26 08:27:56 tux kernel: highmem bounce pool size: 64 pages
Nov 26 08:27:56 tux kernel: Total HugeTLB memory allocated, 0
Nov 26 08:27:56 tux kernel: VFS: Disk quotas dquot_6.5.1
Nov 26 08:27:56 tux kernel: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Nov 26 08:27:56 tux kernel: ksign: Installing public key data
Nov 26 08:27:56 tux kernel: Loading keyring
Nov 26 08:27:56 tux kernel: - Added public key F78B1579A6D2C17
Nov 26 08:27:56 tux kernel: - User ID: Red Hat, Inc. (Kernel Module GPG key)
Nov 26 08:27:56 tux kernel: io scheduler noop registered
Nov 26 08:27:56 tux kernel: io scheduler anticipatory registered
Nov 26 08:27:56 tux kernel: io scheduler deadline registered
Nov 26 08:27:56 tux kernel: io scheduler cfq registered (default)
Nov 26 08:27:56 tux kernel: assign_interrupt_mode Found MSI capability
Nov 26 08:27:56 tux kernel: assign_interrupt_mode Found MSI capability
Nov 26 08:27:56 tux kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Nov 26 08:27:56 tux kernel: ACPI: SSDT 7F6D4134, 0244 (r1  PmRef  Cpu0Ist     3000 INTL 20050624)
Nov 26 08:27:56 tux kernel: ACPI: SSDT 7F6D3EE9, 01C6 (r1  PmRef  Cpu0Cst     3001 INTL 20050624)
Nov 26 08:27:56 tux kernel: ACPI: CPU0 (power states: C1[C1] C2[C2] C3[C3])
Nov 26 08:27:56 tux kernel: ACPI: Processor [CPU0] (supports 8 throttling states)
Nov 26 08:27:56 tux kernel: ACPI: SSDT 7F6D4378, 00C4 (r1  PmRef  Cpu1Ist     3000 INTL 20050624)
Nov 26 08:27:56 tux kernel: ACPI: SSDT 7F6D40AF, 0085 (r1  PmRef  Cpu1Cst     3000 INTL 20050624)
Nov 26 08:27:56 tux kernel: ACPI: CPU1 (power states: C1[C1] C2[C2] C3[C3])
Nov 26 08:27:56 tux kernel: ACPI: Processor [CPU1] (supports 8 throttling states)
Nov 26 08:27:56 tux kernel: ACPI: Thermal Zone [THM] (35 C)
Nov 26 08:27:56 tux kernel: isapnp: Scanning for PnP cards...
Nov 26 08:27:56 tux kernel: isapnp: No Plug & Play device found
Nov 26 08:27:56 tux kernel: Real Time Clock Driver v1.12ac
Nov 26 08:27:56 tux kernel: Non-volatile memory driver v1.2
Nov 26 08:27:56 tux kernel: Linux agpgart interface v0.102
Nov 26 08:27:56 tux kernel: agpgart: Detected an Intel 945GM Chipset.
Nov 26 08:27:56 tux kernel: agpgart: Detected 7932K stolen memory.
Nov 26 08:27:56 tux kernel: agpgart: AGP aperture is 256M @ 0xd0000000
Nov 26 08:27:56 tux kernel: Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
Nov 26 08:27:56 tux kernel: RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize
Nov 26 08:27:56 tux kernel: input: Macintosh mouse button emulation as /class/input/input0
Nov 26 08:27:56 tux kernel: PNP: PS/2 Controller [PNP0303:KBC,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
Nov 26 08:27:56 tux kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
Nov 26 08:27:56 tux kernel: serio: i8042 AUX port at 0x60,0x64 irq 12
Nov 26 08:27:56 tux kernel: mice: PS/2 mouse device common for all mice
Nov 26 08:27:56 tux kernel: input: AT Translated Set 2 keyboard as /class/input/input1
Nov 26 08:27:56 tux kernel: usbcore: registered new interface driver hiddev
Nov 26 08:27:56 tux kernel: usbcore: registered new interface driver usbhid
Nov 26 08:27:57 tux kernel: drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
Nov 26 08:27:57 tux kernel: TCP cubic registered
Nov 26 08:27:57 tux kernel: Initializing XFRM netlink socket
Nov 26 08:27:57 tux kernel: NET: Registered protocol family 1
Nov 26 08:27:57 tux kernel: NET: Registered protocol family 17
Nov 26 08:27:57 tux kernel: Using IPI No-Shortcut mode
Nov 26 08:27:57 tux kernel:   Magic number: 15:100:421
Nov 26 08:27:57 tux kernel: Freeing unused kernel memory: 280k freed
Nov 26 08:27:57 tux kernel: Write protecting the kernel read-only data: 844k
Nov 26 08:27:57 tux kernel: USB Universal Host Controller Interface driver v3.0
Nov 26 08:27:57 tux kernel: ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 20 (level, low) -> IRQ 18
Nov 26 08:27:57 tux kernel: uhci_hcd 0000:00:1d.0: UHCI Host Controller
Nov 26 08:27:57 tux kernel: uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1
Nov 26 08:27:57 tux kernel: uhci_hcd 0000:00:1d.0: irq 18, io base 0x0000bf80
Nov 26 08:27:57 tux kernel: usb usb1: configuration #1 chosen from 1 choice
Nov 26 08:27:57 tux kernel: hub 1-0:1.0: USB hub found
Nov 26 08:27:57 tux kernel: hub 1-0:1.0: 2 ports detected
Nov 26 08:27:57 tux kernel: ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 21 (level, low) -> IRQ 19
Nov 26 08:27:57 tux kernel: uhci_hcd 0000:00:1d.1: UHCI Host Controller
Nov 26 08:27:57 tux kernel: uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2
Nov 26 08:27:57 tux kernel: uhci_hcd 0000:00:1d.1: irq 19, io base 0x0000bf60
Nov 26 08:27:57 tux kernel: usb usb2: configuration #1 chosen from 1 choice
Nov 26 08:27:57 tux kernel: hub 2-0:1.0: USB hub found
Nov 26 08:27:57 tux kernel: hub 2-0:1.0: 2 ports detected
Nov 26 08:27:57 tux kernel: ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 22 (level, low) -> IRQ 20
Nov 26 08:27:57 tux kernel: uhci_hcd 0000:00:1d.2: UHCI Host Controller
Nov 26 08:27:57 tux kernel: uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 3
Nov 26 08:27:57 tux kernel: uhci_hcd 0000:00:1d.2: irq 20, io base 0x0000bf40
Nov 26 08:27:57 tux kernel: usb usb3: configuration #1 chosen from 1 choice
Nov 26 08:27:57 tux kernel: hub 3-0:1.0: USB hub found
Nov 26 08:27:57 tux kernel: hub 3-0:1.0: 2 ports detected
Nov 26 08:27:57 tux kernel: ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 23 (level, low) -> IRQ 21
Nov 26 08:27:57 tux kernel: uhci_hcd 0000:00:1d.3: UHCI Host Controller
Nov 26 08:27:57 tux kernel: uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 4
Nov 26 08:27:57 tux kernel: uhci_hcd 0000:00:1d.3: irq 21, io base 0x0000bf20
Nov 26 08:27:57 tux kernel: usb usb4: configuration #1 chosen from 1 choice
Nov 26 08:27:57 tux kernel: hub 4-0:1.0: USB hub found
Nov 26 08:27:57 tux kernel: hub 4-0:1.0: 2 ports detected
Nov 26 08:27:57 tux kernel: usb 1-1: new low speed USB device using uhci_hcd and address 2
Nov 26 08:27:57 tux kernel: Synaptics Touchpad, model: 1, fw: 6.2, id: 0x180b1, caps: 0xa04713/0x200000
Nov 26 08:27:57 tux kernel: input: SynPS/2 Synaptics TouchPad as /class/input/input2
Nov 26 08:27:57 tux kernel: ACPI: PCI Interrupt 0000:00:1d.7[A] -> GSI 20 (level, low) -> IRQ 18
Nov 26 08:27:57 tux kernel: ehci_hcd 0000:00:1d.7: EHCI Host Controller
Nov 26 08:27:57 tux kernel: ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 5
Nov 26 08:27:57 tux kernel: ehci_hcd 0000:00:1d.7: debug port 1
Nov 26 08:27:57 tux kernel: ehci_hcd 0000:00:1d.7: irq 18, io mem 0xffa80000
Nov 26 08:27:57 tux kernel: ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
Nov 26 08:27:57 tux kernel: usb usb5: configuration #1 chosen from 1 choice
Nov 26 08:27:57 tux kernel: hub 5-0:1.0: USB hub found
Nov 26 08:27:57 tux kernel: hub 5-0:1.0: 8 ports detected
Nov 26 08:27:57 tux kernel: SCSI subsystem initialized
Nov 26 08:27:57 tux kernel: ata_piix 0000:00:1f.2: MAP [ P0 P2 IDE IDE ]
Nov 26 08:27:57 tux kernel: ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 17 (level, low) -> IRQ 22
Nov 26 08:27:57 tux kernel: scsi0 : ata_piix
Nov 26 08:27:57 tux kernel: scsi1 : ata_piix
Nov 26 08:27:57 tux kernel: ata1: SATA max UDMA/133 cmd 0x000101f0 ctl 0x000103f6 bmdma 0x0001bfa0 irq 14
Nov 26 08:27:57 tux kernel: ata2: PATA max UDMA/100 cmd 0x00010170 ctl 0x00010376 bmdma 0x0001bfa8 irq 15
Nov 26 08:27:57 tux kernel: ata1.00: ATA-7: Hitachi HTS541612J9SA00, SBDOC74P, max UDMA/100
Nov 26 08:27:57 tux kernel: ata1.00: 234441648 sectors, multi 8: LBA48 NCQ (depth 0/32)
Nov 26 08:27:57 tux kernel: ata1.00: configured for UDMA/100
Nov 26 08:27:57 tux kernel: usb 1-1: device not accepting address 2, error -71
Nov 26 08:27:57 tux kernel: ata2.00: ATAPI: HL-DT-ST DVD+/-RW GSA-T11N, A103, max UDMA/33
Nov 26 08:27:57 tux kernel: ata2.00: configured for UDMA/33
Nov 26 08:27:57 tux kernel: scsi 0:0:0:0: Direct-Access     ATA      Hitachi HTS54161 SBDO PQ: 0 ANSI: 5
Nov 26 08:27:57 tux kernel: sd 0:0:0:0: [sda] 234441648 512-byte hardware sectors (120034 MB)
Nov 26 08:27:57 tux kernel: sd 0:0:0:0: [sda] Write Protect is off
Nov 26 08:27:57 tux kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Nov 26 08:27:57 tux kernel: sd 0:0:0:0: [sda] 234441648 512-byte hardware sectors (120034 MB)
Nov 26 08:27:57 tux kernel: sd 0:0:0:0: [sda] Write Protect is off
Nov 26 08:27:57 tux kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Nov 26 08:27:57 tux kernel:  sda: sda1 sda2 sda3 sda4 <<6>usb 1-1: new low speed USB device using uhci_hcd and address 4
Nov 26 08:27:57 tux kernel:  sda5 sda6 >
Nov 26 08:27:57 tux kernel: sd 0:0:0:0: [sda] Attached SCSI disk
Nov 26 08:27:57 tux kernel: scsi 1:0:0:0: CD-ROM            HL-DT-ST DVD+-RW GSA-T11N A103 PQ: 0 ANSI: 5
Nov 26 08:27:57 tux kernel: usb 1-1: configuration #1 chosen from 1 choice
Nov 26 08:27:57 tux kernel: input: Microsoft Microsoft 3-Button Mouse with IntelliEye(TM) as /class/input/input3
Nov 26 08:27:57 tux kernel: input: USB HID v1.10 Mouse [Microsoft Microsoft 3-Button Mouse with IntelliEye(TM)] on usb-0000:00:1d.0-1
Nov 26 08:27:57 tux kernel: kjournald starting.  Commit interval 5 seconds
Nov 26 08:27:57 tux kernel: EXT3-fs: mounted filesystem with ordered data mode.
Nov 26 08:27:57 tux kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0
Nov 26 08:27:57 tux kernel: scsi 1:0:0:0: Attached scsi generic sg1 type 5
Nov 26 08:27:57 tux kernel: iTCO_vendor_support: vendor-support=0
Nov 26 08:27:57 tux kernel: iTCO_wdt: Intel TCO WatchDog Timer Driver v1.02 (26-Jul-2007)
Nov 26 08:27:57 tux kernel: iTCO_wdt: Found a ICH7-M TCO device (Version=2, TCOBASE=0x1060)
Nov 26 08:27:57 tux kernel: iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
Nov 26 08:27:57 tux kernel: ACPI: PCI Interrupt 0000:00:1f.3[B] -> GSI 17 (level, low) -> IRQ 22
Nov 26 08:27:57 tux hpiod: 1.7.4a accepting connections at 2208... 
Nov 26 08:27:57 tux kernel: Floppy drive(s): fd0 is 1.44M
Nov 26 08:27:57 tux kernel: input: Lid Switch as /class/input/input4
Nov 26 08:27:57 tux kernel: ACPI: Lid Switch [LID]
Nov 26 08:27:57 tux kernel: input: Power Button (CM) as /class/input/input5
Nov 26 08:27:57 tux kernel: ACPI: Power Button (CM) [PBTN]
Nov 26 08:27:57 tux kernel: input: Sleep Button (CM) as /class/input/input6
Nov 26 08:27:57 tux kernel: ACPI: Sleep Button (CM) [SBTN]
Nov 26 08:27:57 tux kernel: ACPI: AC Adapter [AC] (on-line)
Nov 26 08:27:57 tux kernel: ACPI: Battery Slot [BAT0] (battery present)
Nov 26 08:27:57 tux kernel: sr0: scsi3-mmc drive: 24x/24x writer cd/rw xa/form2 cdda tray
Nov 26 08:27:57 tux kernel: Uniform CD-ROM driver Revision: 3.20
Nov 26 08:27:57 tux kernel: input: Video Bus as /class/input/input7
Nov 26 08:27:57 tux kernel: ACPI: Video Device [VID] (multi-head: yes  rom: no  post: no)
Nov 26 08:27:57 tux kernel: input: Video Bus as /class/input/input8
Nov 26 08:27:57 tux kernel: ACPI: Video Device [VID1] (multi-head: yes  rom: no  post: no)
Nov 26 08:27:57 tux kernel: input: Video Bus as /class/input/input9
Nov 26 08:27:57 tux kernel: ACPI: Video Device [VID2] (multi-head: yes  rom: no  post: no)
Nov 26 08:27:57 tux kernel: intel_rng: FWH not detected
Nov 26 08:27:57 tux kernel: iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.1.17kds
Nov 26 08:27:57 tux kernel: iwl3945: Copyright(c) 2003-2007 Intel Corporation
Nov 26 08:27:57 tux kernel: ACPI: PCI Interrupt 0000:0b:00.0[A] -> GSI 16 (level, low) -> IRQ 16
Nov 26 08:27:57 tux kernel: iwl3945: Detected Intel PRO/Wireless 3945ABG Network Connection
Nov 26 08:27:57 tux kernel: sdhci: Secure Digital Host Controller Interface driver
Nov 26 08:27:57 tux kernel: sdhci: Copyright(c) Pierre Ossman
Nov 26 08:27:57 tux kernel: sdhci: SDHCI controller found at 0000:03:01.1 [1180:0822] (rev 19)
Nov 26 08:27:57 tux kernel: ACPI: PCI Interrupt 0000:03:01.1[B] -> GSI 18 (level, low) -> IRQ 23
Nov 26 08:27:57 tux kernel: mmc0: SDHCI at 0xef9fd400 irq 23 DMA
Nov 26 08:27:57 tux kernel: ACPI: PCI Interrupt 0000:03:01.0[A] -> GSI 19 (level, low) -> IRQ 17
Nov 26 08:27:57 tux kernel: iwl3945: Tunable channels: 13 802.11bg, 23 802.11a channels
Nov 26 08:27:57 tux kernel: firewire_ohci: Added fw-ohci device 0000:03:01.0, OHCI version 1.10
Nov 26 08:27:57 tux kernel: ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 17 (level, low) -> IRQ 22
Nov 26 08:27:57 tux kernel: ssb: Sonics Silicon Backplane found on PCI device 0000:03:00.0
Nov 26 08:27:57 tux kernel: b44.c:v2.0
Nov 26 08:27:57 tux kernel: eth0: Broadcom 44xx/47xx 10/100BaseT Ethernet 00:19:b9:77:a2:b8
Nov 26 08:27:57 tux kernel: ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 21 (level, low) -> IRQ 19
Nov 26 08:27:57 tux kernel: firewire_core: created new fw device fw0 (0 config rom retries, S400)
Nov 26 08:27:57 tux kernel: floppy0: no floppy controllers found
Nov 26 08:27:57 tux kernel: Floppy drive(s): fd0 is 1.44M
Nov 26 08:27:57 tux kernel: device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-devel@redhat.com
Nov 26 08:27:57 tux kernel: device-mapper: multipath: version 1.0.5 loaded
Nov 26 08:27:57 tux kernel: EXT3 FS on sda1, internal journal
Nov 26 08:27:57 tux kernel: kjournald starting.  Commit interval 5 seconds
Nov 26 08:27:57 tux kernel: EXT3 FS on sda3, internal journal
Nov 26 08:27:57 tux kernel: EXT3-fs: mounted filesystem with ordered data mode.
Nov 26 08:27:57 tux kernel: kjournald starting.  Commit interval 5 seconds
Nov 26 08:27:57 tux kernel: EXT3 FS on sda5, internal journal
Nov 26 08:27:57 tux kernel: EXT3-fs: mounted filesystem with ordered data mode.
Nov 26 08:27:57 tux kernel: kjournald starting.  Commit interval 5 seconds
Nov 26 08:27:57 tux kernel: EXT3 FS on sda6, internal journal
Nov 26 08:27:57 tux kernel: EXT3-fs: mounted filesystem with ordered data mode.
Nov 26 08:27:57 tux kernel: floppy0: no floppy controllers found
Nov 26 08:27:57 tux kernel: Adding 2008116k swap on /dev/sda2.  Priority:-1 extents:1 across:2008116k
Nov 26 08:27:57 tux kernel: NET: Registered protocol family 10
Nov 26 08:27:57 tux kernel: lo: Disabled Privacy Extensions
Nov 26 08:27:57 tux kernel: Bridge firewalling registered
Nov 26 08:27:57 tux kernel: br0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.
Nov 26 08:27:57 tux kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
Nov 26 08:27:57 tux kernel: device eth0 entered promiscuous mode
Nov 26 08:27:57 tux kernel: audit(1196061994.234:2): dev=eth0 prom=256 old_prom=0 auid=4294967295
Nov 26 08:27:57 tux kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Nov 26 08:27:57 tux kernel: b44: eth0: Link is up at 100 Mbps, half duplex.
Nov 26 08:27:57 tux kernel: b44: eth0: Flow control is off for TX and off for RX.
Nov 26 08:27:57 tux kernel: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Nov 26 08:27:57 tux kernel: br0: port 1(eth0) entering learning state
Nov 26 08:27:57 tux kernel: br0: topology change detected, propagating
Nov 26 08:27:57 tux kernel: br0: port 1(eth0) entering forwarding state
Nov 26 08:27:57 tux kernel: br0: port 1(eth0) entering disabled state
Nov 26 08:27:57 tux kernel: br0: port 1(eth0) entering learning state
Nov 26 08:27:57 tux kernel: audit(1196062075.859:3): audit_pid=2148 old=0 by auid=4294967295
Nov 26 08:27:57 tux kernel: tun: Universal TUN/TAP device driver, 1.6
Nov 26 08:27:57 tux kernel: tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Nov 26 08:27:57 tux kernel: device vbox0 entered promiscuous mode
Nov 26 08:27:57 tux kernel: br0: port 2(vbox0) entering learning state

^ permalink raw reply	[flat|nested] 10+ messages in thread

* RE: constant_tsc and TSC unstable
  2007-11-30  6:52   ` Paul Rolland (ポール・ロラン)
@ 2007-12-06  0:35     ` Pallipadi, Venkatesh
  0 siblings, 0 replies; 10+ messages in thread
From: Pallipadi, Venkatesh @ 2007-12-06  0:35 UTC (permalink / raw)
  To: Paul Rolland (ポール・ロラン)
  Cc: Linux Kernel, Siddha, Suresh B

 

>-----Original Message-----
>From: linux-kernel-owner@vger.kernel.org 
>[mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of Paul 
>Rolland (???・???)
>Sent: Thursday, November 29, 2007 10:53 PM
>To: Pallipadi, Venkatesh
>Cc: Linux Kernel; Siddha, Suresh B; rol@witbe.net
>Subject: Re: constant_tsc and TSC unstable
>
>Hello,
>
>On Thu, 29 Nov 2007 15:29:49 -0800
>"Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com> wrote:
>
>
>
>> TSCs on Core 2 Duo are supposed to be in sync unless CPU 
>supports deep idle
>> states like C2, C3. Can you send the full /proc/cpuinfo and 
>full dmesg.
>> 
>Sure I can...
>[root@tux log]# cat /proc/cpuinfo 
>processor       : 0
>vendor_id       : GenuineIntel
>cpu family      : 6
>model           : 15
>model name      : Intel(R) Core(TM)2 CPU         T5300  @ 1.73GHz
>stepping        : 2
>cpu MHz         : 800.000
>cache size      : 2048 KB
>physical id     : 0
>siblings        : 2
>core id         : 0
>cpu cores       : 2
>fdiv_bug        : no
>hlt_bug         : no
>f00f_bug        : no
>coma_bug        : no
>fpu             : yes
>fpu_exception   : yes
>cpuid level     : 10
>wp              : yes
>flags           : fpu vme de pse tsc msr pae mce cx8 apic mtrr 
>pge mca cmov pat ps
>e36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm 
>constant_tsc arch_perfmo
>n pebs bts pni monitor ds_cpl est tm2 ssse3 cx16 xtpr lahf_lm
>bogomips        : 3461.13
>clflush size    : 64
>

Tried reproducing this here, but on a similar system (slightly newer CPU stepping) I don’t see this happening. This error does not matter on this particular system as even with TSC synchronization passes, TSC is going to be disabled later due to C2, C3 states, with a message like this
Marking TSC unstable due to: TSC halts in idle.

Will try to reproduce it on other systems to see whether there are any bugs in sync routines.

Thanks,
Venki

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: constant_tsc and TSC unstable
  2007-11-29 16:11 constant_tsc and TSC unstable Paul Rolland
  2007-11-29 19:04 ` H. Peter Anvin
  2007-11-29 23:29 ` Pallipadi, Venkatesh
@ 2007-11-30  0:30 ` Frans Pop
  2 siblings, 0 replies; 10+ messages in thread
From: Frans Pop @ 2007-11-30  0:30 UTC (permalink / raw)
  To: Paul Rolland; +Cc: linux-kernel, rol

Paul Rolland wrote:
> Total of 2 processors activated (6919.15 BogoMIPS).
> ENABLING IO-APIC IRQs
> ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
> checking TSC synchronization [CPU#0 -> CPU#1]:
> Measured 3978592228 cycles TSC warp between CPUs, turning off TSC clock.
> Marking TSC unstable due to: check_tsc_sync_source failed.
> Brought up 2 CPUs
> ...

Not sure if this is related, but thought I'd contribute it anyway...

I've got a Pentium D system (dual core, single processor) and I on some
boots I get "Marking TSC unstable due to check_tsc_sync_source failed" with
some cycles warp between CPUs, while most boots are OK. This kind of
inconsistency seems more due to a failure in the kernel to deal with
differences between boots than with something inherent to the hardware.

I conclude that because basically I never have any problems with the system
once it has booted and the TSC has passed.

>From my kern.logs since Okt 26, I get the following data:
2.6.23+cfs:  2 passes
2.6.23.1:    1 pass;   1 failure  (48 cycles warp)
2.6.24-rc1: 15 passes
2.6.24-rc2: 13 passes; 1 failure  (8 cycles warp)
2.6.24-rc3:  5 passes; 3 failures (8, 8 and 16 cycles warp)

Note that this is not a new issue. For 2.6.21/2.6.23-RCx kernels I reported
similar data in http://lkml.org/lkml/2007/9/16/45.

Cheers,
FJP

^ permalink raw reply	[flat|nested] 10+ messages in thread

end of thread, other threads:[~2007-12-06  0:36 UTC | newest]

Thread overview: 10+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-11-29 16:11 constant_tsc and TSC unstable Paul Rolland
2007-11-29 19:04 ` H. Peter Anvin
2007-11-29 21:26   ` Michael Tokarev
2007-11-30  6:59     ` Paul Rolland
2007-11-30  7:04       ` H. Peter Anvin
2007-11-29 21:36   ` Patrick McHardy
2007-11-29 23:29 ` Pallipadi, Venkatesh
2007-11-30  6:52   ` Paul Rolland (ポール・ロラン)
2007-12-06  0:35     ` Pallipadi, Venkatesh
2007-11-30  0:30 ` Frans Pop

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox