2.6.14-rt21: slow-running clock

2.6.14-rt21: slow-running clock

[Jonathan Woithe]

Hi all

When running Ingo's 2.6.14-rt21 (and in fact rt kernels back to at least
2.6.13-rc days), the clock on my i915-based laptop runs slow.  The degree
of slowness appears directly related to how busy the machine is.  If
it is just sitting around doing very little the time is kept rather
well.  However, as soon as the load increases the RTC and system time
diverge significantly.  For example, running jackd for 2 minutes results
in the system time loosing as much as 20 seconds compared to the CMOS RTC.
Processes doing HDD I/O also seem to affect the system time similarly.

Selectively disabling different timer-related kernel options does not make
any difference.  However, the clock seems fine under vanilla 2.6.14,
suggesting an issue somewhere in the rt patches.

HZ is set to 1000 on this machine in case that makes any difference.  I'm
happy to apply patches and run tests to try to narrow the problem down if
it will help.  Please CC me replys to ensure I see them.

Thanks and regards
  jonathan

Re: 2.6.14-rt21: slow-running clock

[john stultz]

On Mon, 2005-12-05 at 16:56 +1030, Jonathan Woithe wrote:
> Hi all
> 
> When running Ingo's 2.6.14-rt21 (and in fact rt kernels back to at least
> 2.6.13-rc days), the clock on my i915-based laptop runs slow.  The degree
> of slowness appears directly related to how busy the machine is.  If
> it is just sitting around doing very little the time is kept rather
> well.  However, as soon as the load increases the RTC and system time
> diverge significantly.  For example, running jackd for 2 minutes results
> in the system time loosing as much as 20 seconds compared to the CMOS RTC.
> Processes doing HDD I/O also seem to affect the system time similarly.
> 
> Selectively disabling different timer-related kernel options does not make
> any difference.  However, the clock seems fine under vanilla 2.6.14,
> suggesting an issue somewhere in the rt patches.

Could you please send me your dmesg and the output of:

	cat  /sys/devices/system/clocksource/clocksource0/*


Thanks
-john

Re: 2.6.14-rt21: slow-running clock

[Jonathan Woithe]

Hi John

> > When running Ingo's 2.6.14-rt21 (and in fact rt kernels back to at least
> > 2.6.13-rc days), the clock on my i915-based laptop runs slow.  The degree
> > of slowness appears directly related to how busy the machine is.  If
> > it is just sitting around doing very little the time is kept rather
> > well.  However, as soon as the load increases the RTC and system time
> > diverge significantly.  For example, running jackd for 2 minutes results
> > in the system time loosing as much as 20 seconds compared to the CMOS RTC.
> > Processes doing HDD I/O also seem to affect the system time similarly.
> > 
> > Selectively disabling different timer-related kernel options does not make
> > any difference.  However, the clock seems fine under vanilla 2.6.14,
> > suggesting an issue somewhere in the rt patches.
> 
> Could you please send me your dmesg and the output of:
> 
> 	cat  /sys/devices/system/clocksource/clocksource0/*

First the contents of the above /sys/ files:

  /sys/devices/system/clocksource/clocksource0/current_clocksource:
    c3tsc

  /sys/devices/system/clocksource/clocksource0/available_clocksource
    acpi_pm jiffies c3tsc pit

Now follows dmesg output and the kernel .config in use presently.

Regards
  jonathan

Linux version 2.6.14-rt21 (jwoithe@halite) (gcc version 3.3.6) #6 PREEMPT Sat Dec 3 09:43:07 CST 2005
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
 BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000dc000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 000000003f670000 (usable)
 BIOS-e820: 000000003f670000 - 000000003f681000 (ACPI data)
 BIOS-e820: 000000003f681000 - 000000003f700000 (ACPI NVS)
 BIOS-e820: 000000003f700000 - 0000000040000000 (reserved)
 BIOS-e820: 00000000e0000000 - 00000000f0010000 (reserved)
 BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
118MB HIGHMEM available.
896MB LOWMEM available.
On node 0 totalpages: 259696
  DMA zone: 4096 pages, LIFO batch:1
  Normal zone: 225280 pages, LIFO batch:31
  HighMem zone: 30320 pages, LIFO batch:15
DMI 2.3 present.
ACPI: RSDP (v000 FUJ                                   ) @ 0x000f5710
ACPI: RSDT (v001 FUJ    FJNB19C  0x01050000 FUJ  0x00000100) @ 0x3f67a548
ACPI: FADT (v001 FUJ    FJNB19C  0x01050000 FUJ  0x00000100) @ 0x3f680f8c
ACPI: MADT (v001 FUJ    FJNB19C  0x01050000 FUJ  0x00000100) @ 0x3f680686
ACPI: SSDT (v001 FUJ    FJNB19C  0x01050000 INTL 0x20030522) @ 0x3f6806e0
ACPI: SSDT (v001 FUJ    FJNB19C  0x01050000 INTL 0x20030522) @ 0x3f680b25
ACPI: SSDT (v001 FUJ    FJNB19C  0x01050000 INTL 0x20030522) @ 0x3f680d01
ACPI: MCFG (v001 FUJ    FJNB19C  0x01050000 FUJ  0x00000100) @ 0x3f680f28
ACPI: BOOT (v001 FUJ    FJNB19C  0x01050000 FUJ  0x00000100) @ 0x3f680f64
ACPI: DSDT (v001 FUJ    FJNB19C  0x01050000 MSFT 0x0100000e) @ 0x00000000
ACPI: PM-Timer IO Port: 0x1008
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Processor #0 6:13 APIC version 20
ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0])
mapped IOAPIC to ffffc000 (fec00000)
IOAPIC[0]: apic_id 1, version 32, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Enabling APIC mode:  Flat.  Using 1 I/O APICs
Using ACPI (MADT) for SMP configuration information
Allocating PCI resources starting at 50000000 (gap: 40000000:a0000000)
Detected 798.098 MHz processor.
Real-Time Preemption Support (C) 2004-2005 Ingo Molnar
Built 1 zonelists
Kernel command line: auto BOOT_IMAGE=Linux-RT ro root=801
mapped APIC to ffffd000 (fee00000)
Initializing CPU#0
WARNING: experimental RCU implementation.
PID hash table entries: 4096 (order: 12, 65536 bytes)
Event source pit installed with caps set: 05
Console: colour VGA+ 80x25
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 1025528k/1038784k available (2581k kernel code, 12868k reserved, 791k data, 168k init, 121280k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 1597.10 BogoMIPS (lpj=798554)
Mount-cache hash table entries: 512
CPU: After generic identify, caps: afe9fbff 00100000 00000000 00000000 00000180 00000000 00000000
CPU: After vendor identify, caps: afe9fbff 00100000 00000000 00000000 00000180 00000000 00000000
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 2048K
CPU: After all inits, caps: afe9fbff 00100000 00000000 00000040 00000180 00000000 00000000
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
mtrr: v2.0 (20020519)
CPU: Intel(R) Pentium(R) M processor 2.00GHz stepping 08
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
softlockup thread 0 started up.
ENABLING IO-APIC IRQs
.TIMER: vector=0x31 pin1=2 pin2=-1
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: PCI BIOS revision 2.10 entry at 0xfd852, last bus=7
PCI: Using MMCONFIG
ACPI: Subsystem revision 20050902
ACPI: Interpreter enabled
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Probing PCI hardware (bus 00)
Boot video device is 0000:00:02.0
PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1
PCI: Transparent bridge - 0000:00:1e.0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCIB._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 1 3 4 5 6 7 10 12 14 15) *11
ACPI: PCI Interrupt Link [LNKB] (IRQs 1 3 4 5 6 7 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 1 3 4 5 6 7 10 12 14 15) *11
ACPI: PCI Interrupt Link [LNKD] (IRQs 1 3 4 5 6 7 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKE] (IRQs 1 3 4 5 6 7 10 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKF] (IRQs 1 3 4 5 6 7 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKG] (IRQs 1 3 4 5 6 7 10 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKH] (IRQs 1 3 4 5 6 7 *11 12 14 15)
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.EXP1._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.EXP2._PRT]
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
pnp: PnP ACPI: found 14 devices
SCSI subsystem initialized
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a report
PCI: Cannot allocate resource region 7 of bridge 0000:00:1c.1
PCI: Cannot allocate resource region 8 of bridge 0000:00:1c.1
PCI: Cannot allocate resource region 9 of bridge 0000:00:1c.1
PCI: Ignore bogus resource 6 [0:0] of 0000:00:02.0
PCI: Bridge: 0000:00:1c.0
  IO window: disabled.
  MEM window: b0100000-b01fffff
  PREFETCH window: disabled.
PCI: Bridge: 0000:00:1c.1
  IO window: disabled.
  MEM window: disabled.
  PREFETCH window: disabled.
PCI: Bus 7, cardbus bridge: 0000:06:03.0
  IO window: 00002000-000020ff
  IO window: 00002400-000024ff
  PREFETCH window: 50000000-51ffffff
  MEM window: 54000000-55ffffff
PCI: Bridge: 0000:00:1e.0
  IO window: 2000-2fff
  MEM window: b0200000-b02fffff
  PREFETCH window: 50000000-51ffffff
ACPI: PCI Interrupt 0000:00:1c.0[A] -> GSI 17 (level, low) -> IRQ 16
PCI: Setting latency timer of device 0000:00:1c.0 to 64
PCI: Device 0000:00:1c.1 not available because of resource collisions
PCI: Setting latency timer of device 0000:00:1c.1 to 64
PCI: Setting latency timer of device 0000:00:1e.0 to 64
ACPI: PCI Interrupt 0000:06:03.0[A] -> GSI 16 (level, low) -> IRQ 17
Simple Boot Flag at 0x7f set to 0x1
Machine check exception polling timer started.
highmem bounce pool size: 64 pages
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
Initializing Cryptographic API
ACPI: PCI Interrupt 0000:00:1c.0[A] -> GSI 17 (level, low) -> IRQ 16
PCI: Setting latency timer of device 0000:00:1c.0 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[pcie00]
Allocate Port Service[pcie02]
Allocate Port Service[pcie03]
PCI: Device 0000:00:1c.1 not available because of resource collisions
ACPI: AC Adapter [AC] (off-line)
ACPI: Battery Slot [CMB1] (battery present)
ACPI: Battery Slot [CMB2] (battery absent)
ACPI: Power Button (FF) [PWRF]
ACPI: Lid Switch [LID]
ACPI: Power Button (CM) [PWRB]
ACPI: CPU0 (power states: C1[C1] C2[C2] C3[C3])
Real Time Clock Driver v1.12
PNP: PS/2 Controller [PNP0303:KBC,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
i8042.c: Detected active multiplexing controller, rev 1.1.
serio: i8042 AUX0 port at 0x60,0x64 irq 12
serio: i8042 AUX1 port at 0x60,0x64 irq 12
serio: i8042 AUX2 port at 0x60,0x64 irq 12
serio: i8042 AUX3 port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ttyS3 at I/O 0x2e8 (irq = 3) is a 16550A
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
Time: tsc clocksource has been installed.
Falling back to C3 safe TSC
floppy0: no floppy controllers found
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ICH6: IDE controller at PCI slot 0000:00:1f.1
ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 18 (level, low) -> IRQ 18
ICH6: chipset revision 4
ICH6: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0x1410-0x1417, BIOS settings: hda:DMA, hdb:pio
Probing IDE interface ide0...
hda: DV-W28EA, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hda: ATAPI 24X DVD-ROM DVD-R-RAM CD-R/RW drive, 1419kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
libata version 1.12 loaded.
ata_piix version 1.04
ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 19 (level, low) -> IRQ 19
PCI: Setting latency timer of device 0000:00:1f.2 to 64
ata1: SATA max UDMA/133 cmd 0x14B8 ctl 0x140E bmdma 0x14A0 irq 19
ata2: SATA max UDMA/133 cmd 0x14B0 ctl 0x140A bmdma 0x14A8 irq 19
ata1: dev 0 cfg 49:2f00 82:346b 83:7f09 84:6063 85:3469 86:3f09 87:6063 88:203f
ata1: dev 0 ATA, max UDMA/100, 156301488 sectors: lba48
ata1: dev 0 configured for UDMA/100
scsi0 : ata_piix
ATA: abnormal status 0x7F on port 0x14B7
ata2: disabling port
scsi1 : ata_piix
  Vendor: ATA       Model: FUJITSU MHT2080B  Rev: 0000
  Type:   Direct-Access                      ANSI SCSI revision: 05
SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB)
SCSI device sda: drive cache: write back
SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB)
SCSI device sda: drive cache: write back
 sda: sda1 sda2 < sda5 sda6 sda7 sda8 >
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0,  type 0
mice: PS/2 mouse device common for all mice
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 65536 (order: 9, 2621440 bytes)
TCP bind hash table entries: 65536 (order: 9, 2359296 bytes)
TCP: Hash tables configured (established 65536 bind 65536)
TCP reno registered
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
Using IPI Shortcut mode
ACPI wakeup devices: 
PCIB UAR1 MODM AZAL EXP1 EXP2  LID 
ACPI: (supports S0 S3 S4 S5)
ReiserFS: sda1: found reiserfs format "3.6" with standard journal
ReiserFS: sda1: using ordered data mode
ReiserFS: sda1: journal params: device sda1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: sda1: checking transaction log (sda1)
ReiserFS: sda1: Using r5 hash to sort names
VFS: Mounted root (reiserfs filesystem) readonly.
Freeing unused kernel memory: 168k freed
input: AT Translated Set 2 keyboard on isa0060/serio0
Synaptics Touchpad, model: 1, fw: 5.9, id: 0xf8eb1, caps: 0xa04793/0x102000
serio: Synaptics pass-through port at isa0060/serio4/input0
input: SynPS/2 Synaptics TouchPad on isa0060/serio4
Adding 506008k swap on /dev/sda5.  Priority:-1 extents:1 across:506008k
Linux agpgart interface v0.101 (c) Dave Jones
agpgart: Detected an Intel 915GM Chipset.
agpgart: Detected 7932K stolen memory.
agpgart: AGP aperture is 256M @ 0xc0000000
[drm] Initialized drm 1.0.0 20040925
ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 16 (level, low) -> IRQ 17
[drm] Initialized i915 1.1.0 20040405 on minor 0: 
usbcore: registered new driver usbfs
usbcore: registered new driver hub
USB Universal Host Controller Interface driver v2.3
ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 23 (level, low) -> IRQ 20
PCI: Setting latency timer of device 0000:00:1d.0 to 64
uhci_hcd 0000:00:1d.0: UHCI Host Controller
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1
uhci_hcd 0000:00:1d.0: irq 20, io base 0x00001420
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 19 (level, low) -> IRQ 19
PCI: Setting latency timer of device 0000:00:1d.1 to 64
uhci_hcd 0000:00:1d.1: UHCI Host Controller
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:1d.1: irq 19, io base 0x00001440
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 18
PCI: Setting latency timer of device 0000:00:1d.2 to 64
uhci_hcd 0000:00:1d.2: UHCI Host Controller
uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:1d.2: irq 18, io base 0x00001460
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 16 (level, low) -> IRQ 17
PCI: Setting latency timer of device 0000:00:1d.3 to 64
uhci_hcd 0000:00:1d.3: UHCI Host Controller
uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 4
uhci_hcd 0000:00:1d.3: irq 17, io base 0x00001480
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1d.7[A] -> GSI 23 (level, low) -> IRQ 20
PCI: Setting latency timer of device 0000:00:1d.7 to 64
ehci_hcd 0000:00:1d.7: EHCI Host Controller
ehci_hcd 0000:00:1d.7: debug port 1
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 5
ehci_hcd 0000:00:1d.7: irq 20, io mem 0xb0004000
PCI: cache line size of 32 is not supported by device 0000:00:1d.7
ehci_hcd 0000:00:1d.7: USB 2.0 initialized, EHCI 1.00, driver 10 Dec 2004
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 8 ports detected
Initializing USB Mass Storage driver...
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
ohci1394: $Rev: 1313 $ Ben Collins <bcollins@debian.org>
ACPI: PCI Interrupt 0000:06:06.0[A] -> GSI 21 (level, low) -> IRQ 21
ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[21]  MMIO=[b0205000-b02057ff]  Max Packet=[2048]
ieee1394: Host added: ID:BUS[0-00:1023]  GUID[00000e10032944cc]
input: PS/2 Generic Mouse on synaptics-pt/serio0
ReiserFS: sda6: found reiserfs format "3.6" with standard journal
ReiserFS: sda6: using ordered data mode
ReiserFS: sda6: journal params: device sda6, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: sda6: checking transaction log (sda6)
ReiserFS: sda6: Using r5 hash to sort names
ReiserFS: sda7: found reiserfs format "3.6" with standard journal
ReiserFS: sda7: using ordered data mode
ReiserFS: sda7: journal params: device sda7, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: sda7: checking transaction log (sda7)
ReiserFS: sda7: Using r5 hash to sort names
ReiserFS: sda8: found reiserfs format "3.6" with standard journal
ReiserFS: sda8: using ordered data mode
ReiserFS: sda8: journal params: device sda8, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: sda8: checking transaction log (sda8)
ReiserFS: sda8: Using r5 hash to sort names
ACPI: PCI Interrupt 0000:06:03.0[A] -> GSI 16 (level, low) -> IRQ 17
Yenta: CardBus bridge found at 0000:06:03.0 [10cf:131e]
Yenta O2: res at 0x94/0xD4: 00/ea
Yenta O2: enabling read prefetch/write burst
Yenta: ISA IRQ mask 0x0cb8, PCI irq 17
Socket status: 30000006
pcmcia: parent PCI bridge I/O window: 0x2000 - 0x2fff
pcmcia: parent PCI bridge Memory window: 0xb0200000 - 0xb02fffff
pcmcia: parent PCI bridge Memory window: 0x50000000 - 0x51ffffff
pcmcia: Detected deprecated PCMCIA ioctl usage.
pcmcia: This interface will soon be removed from the kernel; please expect breakage unless you upgrade to new tools.
pcmcia: see http://www.kernel.org/pub/linux/utils/kernel/pcmcia/pcmcia.html for details.
ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 16 (level, low) -> IRQ 17
PCI: Setting latency timer of device 0000:00:1b.0 to 64
ALSA sound/pci/hda/hda_intel.c:624: codec_mask = 0x3
ALSA sound/pci/hda/hda_codec.c:1566: hda_codec: PCI 10cf:1326, codec config 2 is selected
usb 5-3: new high speed USB device using ehci_hcd and address 2
scsi2 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 2
usb-storage: waiting for device to settle before scanning
  Vendor: SanDisk   Model: Cruzer Mini       Rev: 0.1 
  Type:   Direct-Access                      ANSI SCSI revision: 02
SCSI device sdb: 501759 512-byte hdwr sectors (257 MB)
sdb: Write Protect is off
sdb: Mode Sense: 03 00 00 00
sdb: assuming drive cache: write through
SCSI device sdb: 501759 512-byte hdwr sectors (257 MB)
sdb: Write Protect is off
sdb: Mode Sense: 03 00 00 00
sdb: assuming drive cache: write through
 sdb: sdb1
Attached scsi removable disk sdb at scsi2, channel 0, id 0, lun 0
Attached scsi generic sg1 at scsi2, channel 0, id 0, lun 0,  type 0
usb-storage: device scan complete
ReiserFS: sdb1: found reiserfs format "3.6" with standard journal
ReiserFS: sdb1: using ordered data mode
ReiserFS: sdb1: journal params: device sdb1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: sdb1: checking transaction log (sdb1)
ReiserFS: sdb1: Using r5 hash to sort names


#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.14-rt21
# Sat Dec  3 09:38:31 2005
#
CONFIG_X86=y
CONFIG_GENERIC_TIME=y
CONFIG_SEMAPHORE_SLEEPERS=y
CONFIG_MMU=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
CONFIG_CLEAN_COMPILE=y
CONFIG_BROKEN_ON_SMP=y
CONFIG_LOCK_KERNEL=y
CONFIG_INIT_ENV_ARG_LIMIT=32

#
# General setup
#
CONFIG_LOCALVERSION=""
CONFIG_LOCALVERSION_AUTO=y
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_POSIX_MQUEUE=y
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_SYSCTL=y
# CONFIG_AUDIT is not set
CONFIG_HOTPLUG=y
CONFIG_KOBJECT_UEVENT=y
# CONFIG_IKCONFIG is not set
CONFIG_INITRAMFS_SOURCE=""
# CONFIG_EMBEDDED is not set
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_ALL is not set
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_SHMEM=y
CONFIG_CC_ALIGN_FUNCTIONS=0
CONFIG_CC_ALIGN_LABELS=0
CONFIG_CC_ALIGN_LOOPS=0
CONFIG_CC_ALIGN_JUMPS=0
# CONFIG_TINY_SHMEM is not set
CONFIG_BASE_SMALL=0

#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
CONFIG_OBSOLETE_MODPARM=y
# CONFIG_MODVERSIONS is not set
# CONFIG_MODULE_SRCVERSION_ALL is not set
CONFIG_KMOD=y

#
# Processor type and features
#
CONFIG_X86_PC=y
# CONFIG_X86_ELAN is not set
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_NUMAQ is not set
# CONFIG_X86_SUMMIT is not set
# CONFIG_X86_BIGSMP is not set
# CONFIG_X86_VISWS is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_ES7000 is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
CONFIG_MPENTIUMM=y
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MK8 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MEFFICEON is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MGEODEGX1 is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
# CONFIG_X86_GENERIC is not set
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=6
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_HPET_TIMER=y
CONFIG_HPET_EMULATE_RTC=y
# CONFIG_KTIME_SCALAR is not set
# CONFIG_HIGH_RES_TIMERS is not set
# CONFIG_SMP is not set
# CONFIG_PREEMPT_NONE is not set
# CONFIG_PREEMPT_VOLUNTARY is not set
# CONFIG_PREEMPT_DESKTOP is not set
CONFIG_PREEMPT_RT=y
CONFIG_PREEMPT=y
CONFIG_PREEMPT_SOFTIRQS=y
CONFIG_PREEMPT_HARDIRQS=y
CONFIG_PREEMPT_BKL=y
CONFIG_PREEMPT_RCU=y
CONFIG_RCU_STATS=y
CONFIG_RWSEM_GENERIC_SPINLOCK=y
CONFIG_ASM_SEMAPHORES=y
CONFIG_X86_UP_APIC=y
CONFIG_X86_UP_IOAPIC=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
# CONFIG_X86_IOAPIC_FAST is not set
CONFIG_X86_TSC=y
CONFIG_X86_MCE=y
CONFIG_X86_MCE_NONFATAL=y
CONFIG_X86_MCE_P4THERMAL=y
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
# CONFIG_X86_REBOOTFIXUPS is not set
CONFIG_MICROCODE=m
CONFIG_X86_MSR=m
CONFIG_X86_CPUID=m

#
# Firmware Drivers
#
# CONFIG_EDD is not set
# CONFIG_DELL_RBU is not set
# CONFIG_DCDBAS is not set
# CONFIG_NOHIGHMEM is not set
CONFIG_HIGHMEM4G=y
# CONFIG_HIGHMEM64G is not set
CONFIG_HIGHMEM=y
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_FLATMEM_MANUAL=y
# CONFIG_DISCONTIGMEM_MANUAL is not set
# CONFIG_SPARSEMEM_MANUAL is not set
CONFIG_FLATMEM=y
CONFIG_FLAT_NODE_MEM_MAP=y
# CONFIG_SPARSEMEM_STATIC is not set
# CONFIG_HIGHPTE is not set
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
# CONFIG_EFI is not set
# CONFIG_REGPARM is not set
# CONFIG_SECCOMP is not set
# CONFIG_HZ_100 is not set
# CONFIG_HZ_250 is not set
CONFIG_HZ_1000=y
CONFIG_HZ=1000
CONFIG_PHYSICAL_START=0x100000
# CONFIG_KEXEC is not set

#
# Power management options (ACPI, APM)
#
CONFIG_PM=y
# CONFIG_PM_DEBUG is not set
# CONFIG_SOFTWARE_SUSPEND is not set

#
# ACPI (Advanced Configuration and Power Interface) Support
#
CONFIG_ACPI=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_SLEEP_PROC_FS=y
# CONFIG_ACPI_SLEEP_PROC_SLEEP is not set
CONFIG_ACPI_AC=y
CONFIG_ACPI_BATTERY=y
CONFIG_ACPI_BUTTON=y
CONFIG_ACPI_VIDEO=m
# CONFIG_ACPI_HOTKEY is not set
CONFIG_ACPI_FAN=y
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_THERMAL=y
# CONFIG_ACPI_ASUS is not set
# CONFIG_ACPI_IBM is not set
# CONFIG_ACPI_TOSHIBA is not set
CONFIG_ACPI_BLACKLIST_YEAR=0
# CONFIG_ACPI_DEBUG is not set
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_SYSTEM=y
CONFIG_X86_PM_TIMER=y
# CONFIG_ACPI_CONTAINER is not set

#
# APM (Advanced Power Management) BIOS Support
#
# CONFIG_APM is not set

#
# CPU Frequency scaling
#
CONFIG_CPU_FREQ=y
CONFIG_CPU_FREQ_TABLE=y
# CONFIG_CPU_FREQ_DEBUG is not set
CONFIG_CPU_FREQ_STAT=y
# CONFIG_CPU_FREQ_STAT_DETAILS is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set
CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE=y
CONFIG_CPU_FREQ_GOV_PERFORMANCE=m
CONFIG_CPU_FREQ_GOV_POWERSAVE=m
CONFIG_CPU_FREQ_GOV_USERSPACE=y
CONFIG_CPU_FREQ_GOV_ONDEMAND=m
CONFIG_CPU_FREQ_GOV_CONSERVATIVE=m

#
# CPUFreq processor drivers
#
CONFIG_X86_ACPI_CPUFREQ=m
# CONFIG_X86_POWERNOW_K6 is not set
# CONFIG_X86_POWERNOW_K7 is not set
# CONFIG_X86_POWERNOW_K8 is not set
# CONFIG_X86_GX_SUSPMOD is not set
CONFIG_X86_SPEEDSTEP_CENTRINO=m
CONFIG_X86_SPEEDSTEP_CENTRINO_ACPI=y
CONFIG_X86_SPEEDSTEP_CENTRINO_TABLE=y
# CONFIG_X86_SPEEDSTEP_ICH is not set
# CONFIG_X86_SPEEDSTEP_SMI is not set
# CONFIG_X86_P4_CLOCKMOD is not set
# CONFIG_X86_CPUFREQ_NFORCE2 is not set
# CONFIG_X86_LONGRUN is not set
# CONFIG_X86_LONGHAUL is not set

#
# shared options
#
# CONFIG_X86_ACPI_CPUFREQ_PROC_INTF is not set
# CONFIG_X86_SPEEDSTEP_LIB is not set

#
# Bus options (PCI, PCMCIA, EISA, MCA, ISA)
#
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GOMMCONFIG is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
CONFIG_PCIEPORTBUS=y
# CONFIG_HOTPLUG_PCI_PCIE is not set
# CONFIG_PCI_MSI is not set
CONFIG_PCI_LEGACY_PROC=y
# CONFIG_PCI_DEBUG is not set
CONFIG_ISA_DMA_API=y
# CONFIG_ISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set

#
# PCCARD (PCMCIA/CardBus) support
#
CONFIG_PCCARD=m
# CONFIG_PCMCIA_DEBUG is not set
CONFIG_PCMCIA=m
CONFIG_PCMCIA_LOAD_CIS=y
CONFIG_PCMCIA_IOCTL=y
CONFIG_CARDBUS=y

#
# PC-card bridges
#
CONFIG_YENTA=m
CONFIG_PD6729=m
CONFIG_I82092=m
CONFIG_PCCARD_NONSTATIC=m

#
# PCI Hotplug Support
#
CONFIG_HOTPLUG_PCI=m
# CONFIG_HOTPLUG_PCI_FAKE is not set
# CONFIG_HOTPLUG_PCI_COMPAQ is not set
# CONFIG_HOTPLUG_PCI_IBM is not set
CONFIG_HOTPLUG_PCI_ACPI=m
# CONFIG_HOTPLUG_PCI_ACPI_IBM is not set
# CONFIG_HOTPLUG_PCI_CPCI is not set
# CONFIG_HOTPLUG_PCI_SHPC is not set

#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_AOUT=y
CONFIG_BINFMT_MISC=m

#
# Networking
#
CONFIG_NET=y

#
# Networking options
#
CONFIG_PACKET=y
# CONFIG_PACKET_MMAP is not set
CONFIG_UNIX=y
# CONFIG_NET_KEY is not set
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
# CONFIG_IP_ADVANCED_ROUTER is not set
CONFIG_IP_FIB_HASH=y
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_IP_MROUTE is not set
# CONFIG_ARPD is not set
# CONFIG_SYN_COOKIES is not set
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
# CONFIG_INET_TUNNEL is not set
CONFIG_INET_DIAG=y
CONFIG_INET_TCP_DIAG=y
# CONFIG_TCP_CONG_ADVANCED is not set
CONFIG_TCP_CONG_BIC=y

#
# IP: Virtual Server Configuration
#
# CONFIG_IP_VS is not set
# CONFIG_IPV6 is not set
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
# CONFIG_NETFILTER_NETLINK is not set

#
# IP: Netfilter Configuration
#
CONFIG_IP_NF_CONNTRACK=m
# CONFIG_IP_NF_CT_ACCT is not set
# CONFIG_IP_NF_CONNTRACK_MARK is not set
# CONFIG_IP_NF_CONNTRACK_EVENTS is not set
# CONFIG_IP_NF_CT_PROTO_SCTP is not set
CONFIG_IP_NF_FTP=m
# CONFIG_IP_NF_IRC is not set
# CONFIG_IP_NF_NETBIOS_NS is not set
# CONFIG_IP_NF_TFTP is not set
# CONFIG_IP_NF_AMANDA is not set
# CONFIG_IP_NF_PPTP is not set
# CONFIG_IP_NF_QUEUE is not set
CONFIG_IP_NF_IPTABLES=m
CONFIG_IP_NF_MATCH_LIMIT=m
CONFIG_IP_NF_MATCH_IPRANGE=m
CONFIG_IP_NF_MATCH_MAC=m
CONFIG_IP_NF_MATCH_PKTTYPE=m
CONFIG_IP_NF_MATCH_MARK=m
CONFIG_IP_NF_MATCH_MULTIPORT=m
CONFIG_IP_NF_MATCH_TOS=m
CONFIG_IP_NF_MATCH_RECENT=m
CONFIG_IP_NF_MATCH_ECN=m
CONFIG_IP_NF_MATCH_DSCP=m
CONFIG_IP_NF_MATCH_AH_ESP=m
CONFIG_IP_NF_MATCH_LENGTH=m
CONFIG_IP_NF_MATCH_TTL=m
CONFIG_IP_NF_MATCH_TCPMSS=m
CONFIG_IP_NF_MATCH_HELPER=m
CONFIG_IP_NF_MATCH_STATE=m
CONFIG_IP_NF_MATCH_CONNTRACK=m
CONFIG_IP_NF_MATCH_OWNER=m
# CONFIG_IP_NF_MATCH_ADDRTYPE is not set
# CONFIG_IP_NF_MATCH_REALM is not set
# CONFIG_IP_NF_MATCH_SCTP is not set
# CONFIG_IP_NF_MATCH_DCCP is not set
# CONFIG_IP_NF_MATCH_COMMENT is not set
# CONFIG_IP_NF_MATCH_HASHLIMIT is not set
# CONFIG_IP_NF_MATCH_STRING is not set
CONFIG_IP_NF_FILTER=m
CONFIG_IP_NF_TARGET_REJECT=m
CONFIG_IP_NF_TARGET_LOG=m
CONFIG_IP_NF_TARGET_ULOG=m
CONFIG_IP_NF_TARGET_TCPMSS=m
# CONFIG_IP_NF_TARGET_NFQUEUE is not set
CONFIG_IP_NF_NAT=m
CONFIG_IP_NF_NAT_NEEDED=y
CONFIG_IP_NF_TARGET_MASQUERADE=m
CONFIG_IP_NF_TARGET_REDIRECT=m
CONFIG_IP_NF_TARGET_NETMAP=m
CONFIG_IP_NF_TARGET_SAME=m
# CONFIG_IP_NF_NAT_SNMP_BASIC is not set
CONFIG_IP_NF_NAT_FTP=m
CONFIG_IP_NF_MANGLE=m
CONFIG_IP_NF_TARGET_TOS=m
CONFIG_IP_NF_TARGET_ECN=m
CONFIG_IP_NF_TARGET_DSCP=m
CONFIG_IP_NF_TARGET_MARK=m
CONFIG_IP_NF_TARGET_CLASSIFY=m
# CONFIG_IP_NF_TARGET_TTL is not set
CONFIG_IP_NF_RAW=m
CONFIG_IP_NF_TARGET_NOTRACK=m
CONFIG_IP_NF_ARPTABLES=m
CONFIG_IP_NF_ARPFILTER=m
CONFIG_IP_NF_ARP_MANGLE=m

#
# DCCP Configuration (EXPERIMENTAL)
#
# CONFIG_IP_DCCP is not set

#
# SCTP Configuration (EXPERIMENTAL)
#
# CONFIG_IP_SCTP is not set
# CONFIG_ATM is not set
# CONFIG_BRIDGE is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_DECNET is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_NET_DIVERT is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_NET_SCHED is not set
# CONFIG_NET_CLS_ROUTE is not set

#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_HAMRADIO is not set
# CONFIG_IRDA is not set
CONFIG_BT=m
CONFIG_BT_L2CAP=m
# CONFIG_BT_SCO is not set
CONFIG_BT_RFCOMM=m
# CONFIG_BT_RFCOMM_TTY is not set
CONFIG_BT_BNEP=m
# CONFIG_BT_BNEP_MC_FILTER is not set
# CONFIG_BT_BNEP_PROTO_FILTER is not set
CONFIG_BT_HIDP=m

#
# Bluetooth device drivers
#
CONFIG_BT_HCIUSB=m
# CONFIG_BT_HCIUSB_SCO is not set
CONFIG_BT_HCIUART=m
CONFIG_BT_HCIUART_H4=y
CONFIG_BT_HCIUART_BCSP=y
# CONFIG_BT_HCIUART_BCSP_TXCRC is not set
CONFIG_BT_HCIBCM203X=m
CONFIG_BT_HCIBPA10X=m
CONFIG_BT_HCIBFUSB=m
CONFIG_BT_HCIDTL1=m
CONFIG_BT_HCIBT3C=m
CONFIG_BT_HCIBLUECARD=m
CONFIG_BT_HCIBTUART=m
CONFIG_BT_HCIVHCI=m
CONFIG_IEEE80211=m
# CONFIG_IEEE80211_DEBUG is not set
CONFIG_IEEE80211_CRYPT_WEP=m
CONFIG_IEEE80211_CRYPT_CCMP=m
CONFIG_IEEE80211_CRYPT_TKIP=m

#
# Device Drivers
#

#
# Generic Driver Options
#
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=m
# CONFIG_DEBUG_DRIVER is not set

#
# Connector - unified userspace <-> kernelspace linker
#
# CONFIG_CONNECTOR is not set

#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set

#
# Parallel port support
#
# CONFIG_PARPORT is not set

#
# Plug and Play support
#
CONFIG_PNP=y
# CONFIG_PNP_DEBUG is not set

#
# Protocols
#
CONFIG_PNPACPI=y

#
# Block devices
#
CONFIG_BLK_DEV_FD=y
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
# CONFIG_BLK_DEV_COW_COMMON is not set
CONFIG_BLK_DEV_LOOP=m
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_SX8 is not set
# CONFIG_BLK_DEV_UB is not set
CONFIG_BLK_DEV_RAM=m
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=4096
CONFIG_LBD=y
CONFIG_CDROM_PKTCDVD=m
CONFIG_CDROM_PKTCDVD_BUFFERS=8
# CONFIG_CDROM_PKTCDVD_WCACHE is not set

#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_ATA_OVER_ETH is not set

#
# ATA/ATAPI/MFM/RLL support
#
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y

#
# Please see Documentation/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_IDE_SATA is not set
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
# CONFIG_BLK_DEV_IDECS is not set
CONFIG_BLK_DEV_IDECD=y
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
# CONFIG_BLK_DEV_IDESCSI is not set
# CONFIG_IDE_TASK_IOCTL is not set

#
# IDE chipset support/bugfixes
#
CONFIG_IDE_GENERIC=y
# CONFIG_BLK_DEV_CMD640 is not set
# CONFIG_BLK_DEV_IDEPNP is not set
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
# CONFIG_BLK_DEV_OFFBOARD is not set
CONFIG_BLK_DEV_GENERIC=y
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_RZ1000 is not set
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD74XX is not set
# CONFIG_BLK_DEV_ATIIXP is not set
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_TRIFLEX is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5520 is not set
# CONFIG_BLK_DEV_CS5530 is not set
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_BLK_DEV_SC1200 is not set
CONFIG_BLK_DEV_PIIX=y
# CONFIG_BLK_DEV_IT821X is not set
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_PDC202XX_OLD is not set
# CONFIG_BLK_DEV_PDC202XX_NEW is not set
# CONFIG_BLK_DEV_SVWKS is not set
# CONFIG_BLK_DEV_SIIMAGE is not set
# CONFIG_BLK_DEV_SIS5513 is not set
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
# CONFIG_BLK_DEV_VIA82CXXX is not set
# CONFIG_IDE_ARM is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_IVB is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_BLK_DEV_HD is not set

#
# SCSI device support
#
# CONFIG_RAID_ATTRS is not set
CONFIG_SCSI=y
CONFIG_SCSI_PROC_FS=y

#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
# CONFIG_BLK_DEV_SR is not set
CONFIG_CHR_DEV_SG=y
# CONFIG_CHR_DEV_SCH is not set

#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
# CONFIG_SCSI_MULTI_LUN is not set
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set

#
# SCSI Transport Attributes
#
# CONFIG_SCSI_SPI_ATTRS is not set
# CONFIG_SCSI_FC_ATTRS is not set
# CONFIG_SCSI_ISCSI_ATTRS is not set
# CONFIG_SCSI_SAS_ATTRS is not set

#
# SCSI low-level drivers
#
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_3W_9XXX is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC7XXX_OLD is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_DPT_I2O is not set
# CONFIG_MEGARAID_NEWGEN is not set
# CONFIG_MEGARAID_LEGACY is not set
# CONFIG_MEGARAID_SAS is not set
CONFIG_SCSI_SATA=y
# CONFIG_SCSI_SATA_AHCI is not set
# CONFIG_SCSI_SATA_SVW is not set
CONFIG_SCSI_ATA_PIIX=y
# CONFIG_SCSI_SATA_MV is not set
# CONFIG_SCSI_SATA_NV is not set
# CONFIG_SCSI_SATA_PROMISE is not set
# CONFIG_SCSI_SATA_QSTOR is not set
# CONFIG_SCSI_SATA_SX4 is not set
# CONFIG_SCSI_SATA_SIL is not set
# CONFIG_SCSI_SATA_SIS is not set
# CONFIG_SCSI_SATA_ULI is not set
# CONFIG_SCSI_SATA_VIA is not set
# CONFIG_SCSI_SATA_VITESSE is not set
CONFIG_SCSI_SATA_INTEL_COMBINED=y
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_IPR is not set
# CONFIG_SCSI_QLOGIC_FC is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
CONFIG_SCSI_QLA2XXX=y
# CONFIG_SCSI_QLA21XX is not set
# CONFIG_SCSI_QLA22XX is not set
# CONFIG_SCSI_QLA2300 is not set
# CONFIG_SCSI_QLA2322 is not set
# CONFIG_SCSI_QLA6312 is not set
# CONFIG_SCSI_QLA24XX is not set
# CONFIG_SCSI_LPFC is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_NSP32 is not set
# CONFIG_SCSI_DEBUG is not set

#
# PCMCIA SCSI adapter support
#
# CONFIG_PCMCIA_AHA152X is not set
# CONFIG_PCMCIA_FDOMAIN is not set
# CONFIG_PCMCIA_NINJA_SCSI is not set
# CONFIG_PCMCIA_QLOGIC is not set
# CONFIG_PCMCIA_SYM53C500 is not set

#
# Multi-device support (RAID and LVM)
#
# CONFIG_MD is not set

#
# Fusion MPT device support
#
# CONFIG_FUSION is not set
# CONFIG_FUSION_SPI is not set
# CONFIG_FUSION_FC is not set
# CONFIG_FUSION_SAS is not set

#
# IEEE 1394 (FireWire) support
#
CONFIG_IEEE1394=m

#
# Subsystem Options
#
# CONFIG_IEEE1394_VERBOSEDEBUG is not set
# CONFIG_IEEE1394_OUI_DB is not set
# CONFIG_IEEE1394_EXTRA_CONFIG_ROMS is not set
# CONFIG_IEEE1394_EXPORT_FULL_API is not set

#
# Device Drivers
#

#
# Texas Instruments PCILynx requires I2C
#
CONFIG_IEEE1394_OHCI1394=m

#
# Protocol Drivers
#
CONFIG_IEEE1394_VIDEO1394=m
CONFIG_IEEE1394_SBP2=m
# CONFIG_IEEE1394_SBP2_PHYS_DMA is not set
# CONFIG_IEEE1394_ETH1394 is not set
CONFIG_IEEE1394_DV1394=m
CONFIG_IEEE1394_RAWIO=m
CONFIG_IEEE1394_CMP=m
CONFIG_IEEE1394_AMDTP=m

#
# I2O device support
#
# CONFIG_I2O is not set

#
# Network device support
#
CONFIG_NETDEVICES=y
CONFIG_DUMMY=m
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
# CONFIG_NET_SB1000 is not set

#
# ARCnet devices
#
# CONFIG_ARCNET is not set

#
# PHY device support
#
# CONFIG_PHYLIB is not set

#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
CONFIG_MII=y
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
# CONFIG_CASSINI is not set
# CONFIG_NET_VENDOR_3COM is not set

#
# Tulip family network device support
#
# CONFIG_NET_TULIP is not set
# CONFIG_HP100 is not set
# CONFIG_NET_PCI is not set

#
# Ethernet (1000 Mbit)
#
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
# CONFIG_E1000 is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_R8169 is not set
# CONFIG_SIS190 is not set
# CONFIG_SKGE is not set
# CONFIG_SK98LIN is not set
CONFIG_TIGON3=m
# CONFIG_BNX2 is not set

#
# Ethernet (10000 Mbit)
#
# CONFIG_CHELSIO_T1 is not set
# CONFIG_IXGB is not set
# CONFIG_S2IO is not set

#
# Token Ring devices
#
# CONFIG_TR is not set

#
# Wireless LAN (non-hamradio)
#
CONFIG_NET_RADIO=y

#
# Obsolete Wireless cards support (pre-802.11)
#
# CONFIG_STRIP is not set
# CONFIG_PCMCIA_WAVELAN is not set
# CONFIG_PCMCIA_NETWAVE is not set

#
# Wireless 802.11 Frequency Hopping cards support
#
# CONFIG_PCMCIA_RAYCS is not set

#
# Wireless 802.11b ISA/PCI cards support
#
# CONFIG_IPW2100 is not set
# CONFIG_IPW_DEBUG is not set
CONFIG_IPW2200=m
# CONFIG_AIRO is not set
# CONFIG_HERMES is not set
# CONFIG_ATMEL is not set

#
# Wireless 802.11b Pcmcia/Cardbus cards support
#
# CONFIG_AIRO_CS is not set
# CONFIG_PCMCIA_WL3501 is not set

#
# Prism GT/Duette 802.11(a/b/g) PCI/Cardbus support
#
# CONFIG_PRISM54 is not set
# CONFIG_HOSTAP is not set
CONFIG_NET_WIRELESS=y

#
# PCMCIA network device support
#
# CONFIG_NET_PCMCIA is not set

#
# Wan interfaces
#
# CONFIG_WAN is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set
# CONFIG_NET_FC is not set
# CONFIG_SHAPER is not set
# CONFIG_NETCONSOLE is not set
# CONFIG_NETPOLL is not set
# CONFIG_NET_POLL_CONTROLLER is not set

#
# ISDN subsystem
#
# CONFIG_ISDN is not set

#
# Telephony Support
#
# CONFIG_PHONE is not set

#
# Input device support
#
CONFIG_INPUT=y

#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_TSDEV is not set
CONFIG_INPUT_EVDEV=m
# CONFIG_INPUT_EVBUG is not set

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
# CONFIG_MOUSE_SERIAL is not set
# CONFIG_MOUSE_VSXXXAA is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
CONFIG_INPUT_MISC=y
CONFIG_INPUT_PCSPKR=m
# CONFIG_INPUT_UINPUT is not set

#
# Hardware I/O ports
#
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
# CONFIG_SERIO_SERPORT is not set
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PCIPS2 is not set
CONFIG_SERIO_LIBPS2=y
# CONFIG_SERIO_RAW is not set
# CONFIG_GAMEPORT is not set

#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_SERIAL_NONSTANDARD is not set

#
# Serial drivers
#
CONFIG_SERIAL_8250=y
# CONFIG_SERIAL_8250_CONSOLE is not set
# CONFIG_SERIAL_8250_CS is not set
# CONFIG_SERIAL_8250_ACPI is not set
CONFIG_SERIAL_8250_NR_UARTS=4
# CONFIG_SERIAL_8250_EXTENDED is not set

#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=y
# CONFIG_SERIAL_JSM is not set
CONFIG_UNIX98_PTYS=y
# CONFIG_LEGACY_PTYS is not set

#
# IPMI
#
# CONFIG_IPMI_HANDLER is not set

#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
CONFIG_HW_RANDOM=m
CONFIG_NVRAM=m
CONFIG_RTC=y
CONFIG_RTC_HISTOGRAM=y
# CONFIG_BLOCKER is not set
# CONFIG_LPPTEST is not set
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_SONYPI is not set

#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set
CONFIG_AGP=m
# CONFIG_AGP_ALI is not set
# CONFIG_AGP_ATI is not set
# CONFIG_AGP_AMD is not set
# CONFIG_AGP_AMD64 is not set
CONFIG_AGP_INTEL=m
# CONFIG_AGP_NVIDIA is not set
# CONFIG_AGP_SIS is not set
# CONFIG_AGP_SWORKS is not set
# CONFIG_AGP_VIA is not set
# CONFIG_AGP_EFFICEON is not set
CONFIG_DRM=m
# CONFIG_DRM_TDFX is not set
# CONFIG_DRM_R128 is not set
# CONFIG_DRM_RADEON is not set
# CONFIG_DRM_I810 is not set
# CONFIG_DRM_I830 is not set
CONFIG_DRM_I915=m
# CONFIG_DRM_MGA is not set
# CONFIG_DRM_SIS is not set
# CONFIG_DRM_VIA is not set
# CONFIG_DRM_SAVAGE is not set

#
# PCMCIA character devices
#
# CONFIG_SYNCLINK_CS is not set
# CONFIG_MWAVE is not set
# CONFIG_RAW_DRIVER is not set
CONFIG_HPET=y
# CONFIG_HPET_RTC_IRQ is not set
CONFIG_HPET_MMAP=y
# CONFIG_HANGCHECK_TIMER is not set

#
# TPM devices
#
# CONFIG_TCG_TPM is not set

#
# I2C support
#
# CONFIG_I2C is not set

#
# Dallas's 1-wire bus
#
# CONFIG_W1 is not set

#
# Hardware Monitoring support
#
CONFIG_HWMON=y
# CONFIG_HWMON_VID is not set
# CONFIG_SENSORS_HDAPS is not set
# CONFIG_HWMON_DEBUG_CHIP is not set

#
# Misc devices
#
# CONFIG_IBM_ASM is not set

#
# Multimedia Capabilities Port drivers
#

#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set

#
# Digital Video Broadcasting Devices
#
# CONFIG_DVB is not set

#
# Graphics support
#
# CONFIG_FB is not set
# CONFIG_VIDEO_SELECT is not set

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
CONFIG_DUMMY_CONSOLE=y

#
# Sound
#
CONFIG_SOUND=m

#
# Advanced Linux Sound Architecture
#
CONFIG_SND=m
CONFIG_SND_TIMER=m
CONFIG_SND_PCM=m
CONFIG_SND_RAWMIDI=m
CONFIG_SND_SEQUENCER=m
# CONFIG_SND_SEQ_DUMMY is not set
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=m
CONFIG_SND_PCM_OSS=m
CONFIG_SND_SEQUENCER_OSS=y
CONFIG_SND_RTCTIMER=m
CONFIG_SND_SEQ_RTCTIMER_DEFAULT=y
CONFIG_SND_VERBOSE_PRINTK=y
CONFIG_SND_DEBUG=y
# CONFIG_SND_DEBUG_MEMORY is not set
CONFIG_SND_DEBUG_DETECT=y
CONFIG_SND_GENERIC_DRIVER=y

#
# Generic devices
#
CONFIG_SND_MPU401_UART=m
# CONFIG_SND_DUMMY is not set
CONFIG_SND_VIRMIDI=m
# CONFIG_SND_MTPAV is not set
# CONFIG_SND_SERIAL_U16550 is not set
CONFIG_SND_MPU401=m

#
# PCI devices
#
# CONFIG_SND_ALI5451 is not set
# CONFIG_SND_ATIIXP is not set
# CONFIG_SND_ATIIXP_MODEM is not set
# CONFIG_SND_AU8810 is not set
# CONFIG_SND_AU8820 is not set
# CONFIG_SND_AU8830 is not set
# CONFIG_SND_AZT3328 is not set
# CONFIG_SND_BT87X is not set
# CONFIG_SND_CS46XX is not set
# CONFIG_SND_CS4281 is not set
# CONFIG_SND_EMU10K1 is not set
# CONFIG_SND_EMU10K1X is not set
# CONFIG_SND_CA0106 is not set
# CONFIG_SND_KORG1212 is not set
# CONFIG_SND_MIXART is not set
# CONFIG_SND_NM256 is not set
# CONFIG_SND_RME32 is not set
# CONFIG_SND_RME96 is not set
# CONFIG_SND_RME9652 is not set
# CONFIG_SND_HDSP is not set
# CONFIG_SND_HDSPM is not set
# CONFIG_SND_TRIDENT is not set
# CONFIG_SND_YMFPCI is not set
# CONFIG_SND_AD1889 is not set
# CONFIG_SND_ALS4000 is not set
# CONFIG_SND_CMIPCI is not set
# CONFIG_SND_ENS1370 is not set
# CONFIG_SND_ENS1371 is not set
# CONFIG_SND_ES1938 is not set
# CONFIG_SND_ES1968 is not set
# CONFIG_SND_MAESTRO3 is not set
# CONFIG_SND_FM801 is not set
# CONFIG_SND_ICE1712 is not set
# CONFIG_SND_ICE1724 is not set
# CONFIG_SND_INTEL8X0 is not set
# CONFIG_SND_INTEL8X0M is not set
# CONFIG_SND_SONICVIBES is not set
# CONFIG_SND_VIA82XX is not set
# CONFIG_SND_VIA82XX_MODEM is not set
# CONFIG_SND_VX222 is not set
CONFIG_SND_HDA_INTEL=m

#
# USB devices
#
# CONFIG_SND_USB_AUDIO is not set
# CONFIG_SND_USB_USX2Y is not set

#
# PCMCIA devices
#

#
# Open Sound System
#
# CONFIG_SOUND_PRIME is not set

#
# USB support
#
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB=m
# CONFIG_USB_DEBUG is not set

#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
# CONFIG_USB_BANDWIDTH is not set
# CONFIG_USB_DYNAMIC_MINORS is not set
# CONFIG_USB_SUSPEND is not set
# CONFIG_USB_OTG is not set

#
# USB Host Controller Drivers
#
CONFIG_USB_EHCI_HCD=m
# CONFIG_USB_EHCI_SPLIT_ISO is not set
# CONFIG_USB_EHCI_ROOT_HUB_TT is not set
# CONFIG_USB_ISP116X_HCD is not set
CONFIG_USB_OHCI_HCD=m
# CONFIG_USB_OHCI_BIG_ENDIAN is not set
CONFIG_USB_OHCI_LITTLE_ENDIAN=y
CONFIG_USB_UHCI_HCD=m
# CONFIG_USB_SL811_HCD is not set

#
# USB Device Class drivers
#
# CONFIG_OBSOLETE_OSS_USB_DRIVER is not set

#
# USB Bluetooth TTY can only be used with disabled Bluetooth subsystem
#
# CONFIG_USB_ACM is not set
CONFIG_USB_PRINTER=m

#
# NOTE: USB_STORAGE enables SCSI, and 'SCSI disk support' may also be needed; see USB_STORAGE Help for more information
#
CONFIG_USB_STORAGE=m
# CONFIG_USB_STORAGE_DEBUG is not set
# CONFIG_USB_STORAGE_DATAFAB is not set
# CONFIG_USB_STORAGE_FREECOM is not set
# CONFIG_USB_STORAGE_ISD200 is not set
# CONFIG_USB_STORAGE_DPCM is not set
# CONFIG_USB_STORAGE_USBAT is not set
# CONFIG_USB_STORAGE_SDDR09 is not set
# CONFIG_USB_STORAGE_SDDR55 is not set
# CONFIG_USB_STORAGE_JUMPSHOT is not set
# CONFIG_USB_STORAGE_ONETOUCH is not set

#
# USB Input Devices
#
CONFIG_USB_HID=m
CONFIG_USB_HIDINPUT=y
# CONFIG_HID_FF is not set
# CONFIG_USB_HIDDEV is not set

#
# USB HID Boot Protocol drivers
#
# CONFIG_USB_KBD is not set
# CONFIG_USB_MOUSE is not set
# CONFIG_USB_AIPTEK is not set
# CONFIG_USB_WACOM is not set
# CONFIG_USB_ACECAD is not set
# CONFIG_USB_KBTAB is not set
# CONFIG_USB_POWERMATE is not set
# CONFIG_USB_MTOUCH is not set
# CONFIG_USB_ITMTOUCH is not set
# CONFIG_USB_EGALAX is not set
# CONFIG_USB_YEALINK is not set
# CONFIG_USB_XPAD is not set
# CONFIG_USB_ATI_REMOTE is not set
# CONFIG_USB_KEYSPAN_REMOTE is not set
# CONFIG_USB_APPLETOUCH is not set

#
# USB Imaging devices
#
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_MICROTEK is not set

#
# USB Multimedia devices
#
# CONFIG_USB_DABUSB is not set

#
# Video4Linux support is needed for USB Multimedia device support
#

#
# USB Network Adapters
#
# CONFIG_USB_CATC is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RTL8150 is not set
# CONFIG_USB_USBNET is not set
# CONFIG_USB_ZD1201 is not set
CONFIG_USB_MON=y

#
# USB port drivers
#

#
# USB Serial Converter support
#
# CONFIG_USB_SERIAL is not set

#
# USB Miscellaneous drivers
#
# CONFIG_USB_EMI62 is not set
# CONFIG_USB_EMI26 is not set
# CONFIG_USB_AUERSWALD is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_LEGOTOWER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_LED is not set
# CONFIG_USB_CYTHERM is not set
# CONFIG_USB_PHIDGETKIT is not set
# CONFIG_USB_PHIDGETSERVO is not set
# CONFIG_USB_IDMOUSE is not set
# CONFIG_USB_SISUSBVGA is not set
# CONFIG_USB_LD is not set
# CONFIG_USB_TEST is not set

#
# USB DSL modem support
#

#
# USB Gadget Support
#
# CONFIG_USB_GADGET is not set

#
# MMC/SD Card support
#
# CONFIG_MMC is not set

#
# InfiniBand support
#
# CONFIG_INFINIBAND is not set

#
# SN Devices
#

#
# File systems
#
CONFIG_EXT2_FS=y
# CONFIG_EXT2_FS_XATTR is not set
# CONFIG_EXT2_FS_XIP is not set
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
# CONFIG_EXT3_FS_POSIX_ACL is not set
# CONFIG_EXT3_FS_SECURITY is not set
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_FS_MBCACHE=y
CONFIG_REISERFS_FS=y
# CONFIG_REISERFS_CHECK is not set
CONFIG_REISERFS_PROC_INFO=y
# CONFIG_REISERFS_FS_XATTR is not set
# CONFIG_JFS_FS is not set
# CONFIG_FS_POSIX_ACL is not set
# CONFIG_XFS_FS is not set
CONFIG_MINIX_FS=m
# CONFIG_ROMFS_FS is not set
CONFIG_INOTIFY=y
# CONFIG_QUOTA is not set
CONFIG_DNOTIFY=y
CONFIG_AUTOFS_FS=m
CONFIG_AUTOFS4_FS=m
# CONFIG_FUSE_FS is not set

#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
# CONFIG_ZISOFS is not set
CONFIG_UDF_FS=y
CONFIG_UDF_NLS=y

#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=m
CONFIG_MSDOS_FS=m
CONFIG_VFAT_FS=m
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
# CONFIG_NTFS_FS is not set

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
# CONFIG_HUGETLBFS is not set
# CONFIG_HUGETLB_PAGE is not set
CONFIG_RAMFS=y
# CONFIG_RELAYFS_FS is not set

#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_CRAMFS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set

#
# Network File Systems
#
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
# CONFIG_NFS_V3_ACL is not set
CONFIG_NFS_V4=y
# CONFIG_NFS_DIRECTIO is not set
CONFIG_NFSD=y
CONFIG_NFSD_V3=y
# CONFIG_NFSD_V3_ACL is not set
# CONFIG_NFSD_V4 is not set
CONFIG_NFSD_TCP=y
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=y
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=y
CONFIG_SUNRPC_GSS=y
CONFIG_RPCSEC_GSS_KRB5=y
# CONFIG_RPCSEC_GSS_SPKM3 is not set
# CONFIG_SMB_FS is not set
# CONFIG_CIFS is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set
# CONFIG_9P_FS is not set

#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y

#
# Native Language Support
#
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=y
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
# CONFIG_NLS_CODEPAGE_850 is not set
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
# CONFIG_NLS_ASCII is not set
CONFIG_NLS_ISO8859_1=y
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
# CONFIG_NLS_ISO8859_15 is not set
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
# CONFIG_NLS_UTF8 is not set

#
# Profiling support
#
# CONFIG_PROFILING is not set
CONFIG_PROFILE_NMI=y

#
# Kernel hacking
#
# CONFIG_PRINTK_TIME is not set
# CONFIG_PRINTK_IGNORE_LOGLEVEL is not set
CONFIG_DEBUG_KERNEL=y
CONFIG_MAGIC_SYSRQ=y
CONFIG_LOG_BUF_SHIFT=15
# CONFIG_PARANOID_GENERIC_TIME is not set
CONFIG_DETECT_SOFTLOCKUP=y
# CONFIG_SCHEDSTATS is not set
# CONFIG_DEBUG_SLAB is not set
# CONFIG_DEBUG_PREEMPT is not set
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_WAKEUP_TIMING is not set
# CONFIG_CRITICAL_PREEMPT_TIMING is not set
# CONFIG_CRITICAL_IRQSOFF_TIMING is not set
# CONFIG_DEBUG_DEADLOCKS is not set
# CONFIG_DEBUG_RT_LOCKING_MODE is not set
# CONFIG_DEBUG_KOBJECT is not set
# CONFIG_DEBUG_HIGHMEM is not set
CONFIG_DEBUG_BUGVERBOSE=y
# CONFIG_DEBUG_INFO is not set
# CONFIG_DEBUG_FS is not set
# CONFIG_DEBUG_VM is not set
# CONFIG_RCU_TORTURE_TEST is not set
# CONFIG_USE_FRAME_POINTER is not set
CONFIG_EARLY_PRINTK=y
CONFIG_DEBUG_STACKOVERFLOW=y
# CONFIG_KPROBES is not set
# CONFIG_DEBUG_STACK_USAGE is not set
# CONFIG_DEBUG_PAGEALLOC is not set
# CONFIG_4KSTACKS is not set
CONFIG_X86_FIND_SMP_CONFIG=y
CONFIG_X86_MPPARSE=y

#
# Security options
#
# CONFIG_KEYS is not set
# CONFIG_SECURITY is not set

#
# Cryptographic options
#
CONFIG_CRYPTO=y
CONFIG_CRYPTO_HMAC=y
CONFIG_CRYPTO_NULL=m
CONFIG_CRYPTO_MD4=m
CONFIG_CRYPTO_MD5=y
CONFIG_CRYPTO_SHA1=m
CONFIG_CRYPTO_SHA256=m
CONFIG_CRYPTO_SHA512=m
CONFIG_CRYPTO_WP512=m
CONFIG_CRYPTO_TGR192=m
CONFIG_CRYPTO_DES=y
CONFIG_CRYPTO_BLOWFISH=m
CONFIG_CRYPTO_TWOFISH=m
CONFIG_CRYPTO_SERPENT=m
CONFIG_CRYPTO_AES=m
CONFIG_CRYPTO_AES_586=m
CONFIG_CRYPTO_CAST5=m
CONFIG_CRYPTO_CAST6=m
CONFIG_CRYPTO_TEA=m
CONFIG_CRYPTO_ARC4=m
CONFIG_CRYPTO_KHAZAD=m
CONFIG_CRYPTO_ANUBIS=m
CONFIG_CRYPTO_DEFLATE=m
CONFIG_CRYPTO_MICHAEL_MIC=m
CONFIG_CRYPTO_CRC32C=m
CONFIG_CRYPTO_TEST=m

#
# Hardware crypto devices
#
# CONFIG_CRYPTO_DEV_PADLOCK is not set

#
# Library routines
#
CONFIG_CRC_CCITT=m
# CONFIG_CRC16 is not set
CONFIG_CRC32=y
CONFIG_LIBCRC32C=m
CONFIG_ZLIB_INFLATE=m
CONFIG_ZLIB_DEFLATE=m
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_PC=y

Re: 2.6.14-rt21: slow-running clock

[john stultz]

On Wed, 2005-12-07 at 14:09 +1030, Jonathan Woithe wrote:
> > > When running Ingo's 2.6.14-rt21 (and in fact rt kernels back to at least
> > > 2.6.13-rc days), the clock on my i915-based laptop runs slow.  The degree
> > > of slowness appears directly related to how busy the machine is.  If
> > > it is just sitting around doing very little the time is kept rather
> > > well.  However, as soon as the load increases the RTC and system time
> > > diverge significantly.  For example, running jackd for 2 minutes results
> > > in the system time loosing as much as 20 seconds compared to the CMOS RTC.
> > > Processes doing HDD I/O also seem to affect the system time similarly.
> > > 
> > > Selectively disabling different timer-related kernel options does not make
> > > any difference.  However, the clock seems fine under vanilla 2.6.14,
> > > suggesting an issue somewhere in the rt patches.
> > 
> > Could you please send me your dmesg and the output of:
> > 
> > 	cat  /sys/devices/system/clocksource/clocksource0/*
> 
> First the contents of the above /sys/ files:
> 
>   /sys/devices/system/clocksource/clocksource0/current_clocksource:
>     c3tsc
> 
>   /sys/devices/system/clocksource/clocksource0/available_clocksource
>     acpi_pm jiffies c3tsc pit

Odd. I'm not sure why the acpi_pm wasn't chosen by default if it was
available and the TSC fell back to the c3tsc. It might be something in
the -RT tree that's changed that bit. Could you try the following and
see if it doesn't resolve the timekeeping problems you're seeing?

echo "acpi_pm" >  /sys/devices/system/clocksource/clocksource0/current_clocksource


Still it sounds like something isn't right w/ either the c3tsc code or
the cpufreq notification code. Would you be willing to test further
patches?

Also could you try booting w/ idle=poll and see if that changes the
behavior?

Thanks for the testing and feedback!
-john

Re: 2.6.14-rt21: slow-running clock

[Jonathan Woithe]

> > > > When running Ingo's 2.6.14-rt21 (and in fact rt kernels back to at least
> > > > 2.6.13-rc days), the clock on my i915-based laptop runs slow.  The degree
> > > > of slowness appears directly related to how busy the machine is.  If
> > > > it is just sitting around doing very little the time is kept rather
> > > > well.  However, as soon as the load increases the RTC and system time
> > > > diverge significantly.  For example, running jackd for 2 minutes results
> > > > in the system time loosing as much as 20 seconds compared to the CMOS RTC.
> > > > Processes doing HDD I/O also seem to affect the system time similarly.
> > > > 
> > > > Selectively disabling different timer-related kernel options does not make
> > > > any difference.  However, the clock seems fine under vanilla 2.6.14,
> > > > suggesting an issue somewhere in the rt patches.
> > > 
> > > Could you please send me your dmesg and the output of:
> > > 
> > > 	cat  /sys/devices/system/clocksource/clocksource0/*
> > 
> > First the contents of the above /sys/ files:
> > 
> >   /sys/devices/system/clocksource/clocksource0/current_clocksource:
> >     c3tsc
> > 
> >   /sys/devices/system/clocksource/clocksource0/available_clocksource
> >     acpi_pm jiffies c3tsc pit
> 
> Odd. I'm not sure why the acpi_pm wasn't chosen by default if it was
> available and the TSC fell back to the c3tsc. It might be something in
> the -RT tree that's changed that bit. Could you try the following and
> see if it doesn't resolve the timekeeping problems you're seeing?
> 
> echo "acpi_pm" >  /sys/devices/system/clocksource/clocksource0/current_clocksource

Will test it tonight.

> Still it sounds like something isn't right w/ either the c3tsc code or
> the cpufreq notification code. Would you be willing to test further
> patches?

Yes, no problem.

> Also could you try booting w/ idle=poll and see if that changes the
> behavior?

Again, it will be done tonight and I'll advise tomorrow.

Regards
  jonathan

Re: 2.6.14-rt21: slow-running clock

[Jonathan Woithe]

> > > > When running Ingo's 2.6.14-rt21 (and in fact rt kernels back to at least
> > > > 2.6.13-rc days), the clock on my i915-based laptop runs slow.  The degree
> > > > of slowness appears directly related to how busy the machine is.  If
> > > > it is just sitting around doing very little the time is kept rather
> > > > well.  However, as soon as the load increases the RTC and system time
> > > > diverge significantly.  For example, running jackd for 2 minutes results
> > > > in the system time loosing as much as 20 seconds compared to the CMOS RTC.
> > > > Processes doing HDD I/O also seem to affect the system time similarly.
> > > > 
> > > > Selectively disabling different timer-related kernel options does not make
> > > > any difference.  However, the clock seems fine under vanilla 2.6.14,
> > > > suggesting an issue somewhere in the rt patches.
> > > 
> > > Could you please send me your dmesg and the output of:
> > > 
> > > 	cat  /sys/devices/system/clocksource/clocksource0/*
> > 
> > First the contents of the above /sys/ files:
> > 
> >   /sys/devices/system/clocksource/clocksource0/current_clocksource:
> >     c3tsc
> > 
> >   /sys/devices/system/clocksource/clocksource0/available_clocksource
> >     acpi_pm jiffies c3tsc pit
> 
> Odd. I'm not sure why the acpi_pm wasn't chosen by default if it was
> available and the TSC fell back to the c3tsc. It might be something in
> the -RT tree that's changed that bit. Could you try the following and
> see if it doesn't resolve the timekeeping problems you're seeing?
> 
> echo "acpi_pm" >  /sys/devices/system/clocksource/clocksource0/current_clocksource

Upon executing the above command the system time started behaving correctly
once more.

> Still it sounds like something isn't right w/ either the c3tsc code or
> the cpufreq notification code.

That is indeed what it appears.  When c3tsc is in use timing goes haywire.

I'm also wondering whether this might be related to one other thing I
noticed a week or so back (also reported to the list, but thus far no
followups). If I enabled the (new) "High resolution timers" feature (as
distinct from HPET), things like /usr/bin/sleep run for far longer than
they should irrespective of machine load.  For example, "sleep 1" from bash
actually delays 38 seconds, not 1 second as expected.

> Would you be willing to test further patches?

Yes.

> Also could you try booting w/ idle=poll and see if that changes the
> behavior?

Booting with idle=poll did indeed alter the behaviour.  Firstly, the
current_clocksource became tsc, not c3tsc.  Secondly, the
available_clocksource listed 

  acpi_pm jiffies tsc pit

In other words, c3tsc wasn't there but tsc was.  In terms of time accuracy
it seemed that with idle=poll the system time was kept accurately in this
case as well.  I also noted in dmesg output the following:

  Time: tsc clocksource has been installed.

Unlike the normal case (where idle=poll was not specified) there was no
mention of a "fallback" to a "C3-safe tsc".

For interest I also booted a plain 2.6.14 kernel to see how the clocksources
were set up there.  However, the /sys/devices/system/clocksource/ directory
did not exist under this kernel version so I wasn't able to conclude anything
(other than the fact that /sys/devices/system/clocksource/ must be something
added by the rt patchset).  There also wasn't any dmesg output of the
form
  Time: ...

Regards
  jonathan

Re: 2.6.14-rt21: slow-running clock

[john stultz]

On Thu, 2005-12-08 at 09:24 +1030, Jonathan Woithe wrote:
> > > > > When running Ingo's 2.6.14-rt21 (and in fact rt kernels back to at least
> > > > > 2.6.13-rc days), the clock on my i915-based laptop runs slow.  The degree
> > > > > of slowness appears directly related to how busy the machine is.  If
> > > > > it is just sitting around doing very little the time is kept rather
> > > > > well.  However, as soon as the load increases the RTC and system time
> > > > > diverge significantly.  For example, running jackd for 2 minutes results
> > > > > in the system time loosing as much as 20 seconds compared to the CMOS RTC.
> > > > > Processes doing HDD I/O also seem to affect the system time similarly.
> > > > > 
> > > > > Selectively disabling different timer-related kernel options does not make
> > > > > any difference.  However, the clock seems fine under vanilla 2.6.14,
> > > > > suggesting an issue somewhere in the rt patches.
> > > > 
> > > > Could you please send me your dmesg and the output of:
> > > > 
> > > > 	cat  /sys/devices/system/clocksource/clocksource0/*
> > > 
> > > First the contents of the above /sys/ files:
> > > 
> > >   /sys/devices/system/clocksource/clocksource0/current_clocksource:
> > >     c3tsc
> > > 
> > >   /sys/devices/system/clocksource/clocksource0/available_clocksource
> > >     acpi_pm jiffies c3tsc pit
> > 
> > Odd. I'm not sure why the acpi_pm wasn't chosen by default if it was
> > available and the TSC fell back to the c3tsc. It might be something in
> > the -RT tree that's changed that bit. Could you try the following and
> > see if it doesn't resolve the timekeeping problems you're seeing?
> > 
> > echo "acpi_pm" >  /sys/devices/system/clocksource/clocksource0/current_clocksource
> 
> Upon executing the above command the system time started behaving correctly
> once more.

Ok, something in the -rt patches is probably changing the selection
order.

> > Still it sounds like something isn't right w/ either the c3tsc code or
> > the cpufreq notification code.
> 
> That is indeed what it appears.  When c3tsc is in use timing goes haywire.

That narrows it down nicely.

> I'm also wondering whether this might be related to one other thing I
> noticed a week or so back (also reported to the list, but thus far no
> followups). If I enabled the (new) "High resolution timers" feature (as
> distinct from HPET), things like /usr/bin/sleep run for far longer than
> they should irrespective of machine load.  For example, "sleep 1" from bash
> actually delays 38 seconds, not 1 second as expected.

Does disabling the "High resolution timers" feature change the behavior
all?

> > Would you be willing to test further patches?
> 
> Yes.

Great. I'll try to work out something that will give me a better idea of
what exactly is going on.

> > Also could you try booting w/ idle=poll and see if that changes the
> > behavior?
> 
> Booting with idle=poll did indeed alter the behaviour.  Firstly, the
> current_clocksource became tsc, not c3tsc.  Secondly, the
> available_clocksource listed 
> 
>   acpi_pm jiffies tsc pit

Seeing tsc instead of c3tsc is expected. idle=poll avoids letting the
cpu go into C3 mode which halts the TSC. This halting would be bad if we
used the TSC by itself for timekeeping, so we only enable the c3tsc
clocksource if the system starts entering C3 mode.


> In other words, c3tsc wasn't there but tsc was.  In terms of time accuracy
> it seemed that with idle=poll the system time was kept accurately in this
> case as well.  I also noted in dmesg output the following:
> 
>   Time: tsc clocksource has been installed.
> 
> Unlike the normal case (where idle=poll was not specified) there was no
> mention of a "fallback" to a "C3-safe tsc".

Thats very interesting that idle=poll worked around the issue. More
digging will be necessary.

Thanks so much for the great testing and feedback! 
I really appreciate it!
-john

Re: 2.6.14-rt21: slow-running clock

[Jonathan Woithe]

> On Thu, 2005-12-08 at 09:24 +1030, Jonathan Woithe wrote:
> > > Odd. I'm not sure why the acpi_pm wasn't chosen by default if it was
> > > available and the TSC fell back to the c3tsc. It might be something in
> > > the -RT tree that's changed that bit. Could you try the following and
> > > see if it doesn't resolve the timekeeping problems you're seeing?
> > > 
> > > echo "acpi_pm" >  /sys/devices/system/clocksource/clocksource0/current_clocksource
> > 
> > Upon executing the above command the system time started behaving correctly
> > once more.
> Ok, something in the -rt patches is probably changing the selection
> order.

Is there any way to change the clock source in a normal 2.6.14 kernel?  If
there was I could force the source to c3tsc in that and see if the problem
affects the c3tsc in vanilla kernels.

> > I'm also wondering whether this might be related to one other thing I
> > noticed a week or so back (also reported to the list, but thus far no
> > followups). If I enabled the (new) "High resolution timers" feature (as
> > distinct from HPET), things like /usr/bin/sleep run for far longer than
> > they should irrespective of machine load.  For example, "sleep 1" from bash
> > actually delays 38 seconds, not 1 second as expected.
> 
> Does disabling the "High resolution timers" feature change the behavior
> all?

I should clarify.  Everything I've given you thus far has been with the
"high resolution timers" feature disabled.  Two or so weeks ago I tried
enabling it and that's when "sleep 1" took 38 seconds to complete. 
Disabling "high resoltion timers" at least made "sleep 1" behave somewhat
saner.  I don't know if having the high res timers enabled affects the
accuracy of the system clock however.  I'll test this tonight.

> > In other words, c3tsc wasn't there but tsc was.  In terms of time accuracy
> > it seemed that with idle=poll the system time was kept accurately in this
> > case as well.  I also noted in dmesg output the following:
> > 
> >   Time: tsc clocksource has been installed.
> > 
> > Unlike the normal case (where idle=poll was not specified) there was no
> > mention of a "fallback" to a "C3-safe tsc".
> 
> Thats very interesting that idle=poll worked around the issue. More
> digging will be necessary.

It possibly suggests that it's the c3tsc timer which is faulty as opposed to
the tsc timer (or maybe it's just a mode thing).  Note that even with
idle=poll it was the tsc timer (instead of the acpi_pm timer) which was
selected, so "idle=poll" doesn't work around the timer selection issue.  It
seems that there might be two separate problems: timer source selection and
c3tsc accuracy.  Whether they are both present in vanilla 2.6.14 (or simply
masked due to selection of acpi_pm) is not clear.

Regards
  jonathan

Re: 2.6.14-rt21: slow-running clock

[john stultz]

On Thu, 2005-12-08 at 13:32 +1030, Jonathan Woithe wrote:
> > On Thu, 2005-12-08 at 09:24 +1030, Jonathan Woithe wrote:
> > > > Odd. I'm not sure why the acpi_pm wasn't chosen by default if it was
> > > > available and the TSC fell back to the c3tsc. It might be something in
> > > > the -RT tree that's changed that bit. Could you try the following and
> > > > see if it doesn't resolve the timekeeping problems you're seeing?
> > > > 
> > > > echo "acpi_pm" >  /sys/devices/system/clocksource/clocksource0/current_clocksource
> > > 
> > > Upon executing the above command the system time started behaving correctly
> > > once more.
> > Ok, something in the -rt patches is probably changing the selection
> > order.
> 
> Is there any way to change the clock source in a normal 2.6.14 kernel?  If
> there was I could force the source to c3tsc in that and see if the problem
> affects the c3tsc in vanilla kernels.

Not really, other then just at boot. And your options are only: tsc,
pit, pmtmr and hpet. The c3tsc is new w/ my timekeeping code.

> > > I'm also wondering whether this might be related to one other thing I
> > > noticed a week or so back (also reported to the list, but thus far no
> > > followups). If I enabled the (new) "High resolution timers" feature (as
> > > distinct from HPET), things like /usr/bin/sleep run for far longer than
> > > they should irrespective of machine load.  For example, "sleep 1" from bash
> > > actually delays 38 seconds, not 1 second as expected.
> > 
> > Does disabling the "High resolution timers" feature change the behavior
> > all?
> 
> I should clarify.  Everything I've given you thus far has been with the
> "high resolution timers" feature disabled.  Two or so weeks ago I tried
> enabling it and that's when "sleep 1" took 38 seconds to complete. 
> Disabling "high resoltion timers" at least made "sleep 1" behave somewhat
> saner.  I don't know if having the high res timers enabled affects the
> accuracy of the system clock however.  I'll test this tonight.

Ok. I think I've reproduced the issue on my laptop as well. It seems to
be a -rt issue only (I need to go back and test HRT too) as I do not see
the problem w/ my B13 patchset. 

Possibly we are getting preempted before entering or exiting C3 mode?
I'll need to look further. It isn't directly related to cpu load or
idleness (a cpu pegged box doesn't drift that badly), but it might be
io-related. 

> > > In other words, c3tsc wasn't there but tsc was.  In terms of time accuracy
> > > it seemed that with idle=poll the system time was kept accurately in this
> > > case as well.  I also noted in dmesg output the following:
> > > 
> > >   Time: tsc clocksource has been installed.
> > > 
> > > Unlike the normal case (where idle=poll was not specified) there was no
> > > mention of a "fallback" to a "C3-safe tsc".
> > 
> > Thats very interesting that idle=poll worked around the issue. More
> > digging will be necessary.
> 
> It possibly suggests that it's the c3tsc timer which is faulty as opposed to
> the tsc timer (or maybe it's just a mode thing).  Note that even with
> idle=poll it was the tsc timer (instead of the acpi_pm timer) which was
> selected, so "idle=poll" doesn't work around the timer selection issue.  It
> seems that there might be two separate problems: timer source selection and
> c3tsc accuracy.  Whether they are both present in vanilla 2.6.14 (or simply
> masked due to selection of acpi_pm) is not clear.

Ok, I might have have been confusing in my last mail. I think we're in
agreement and I understand the situation. I appreciate the
clarification.

Thanks again for the feedback!
-john

Re: 2.6.14-rt21: slow-running clock

[Jonathan Woithe]

> On Thu, 2005-12-08 at 13:32 +1030, Jonathan Woithe wrote:
> > > > I'm also wondering whether this might be related to one other thing I
> > > > noticed a week or so back (also reported to the list, but thus far no
> > > > followups). If I enabled the (new) "High resolution timers" feature (as
> > > > distinct from HPET), things like /usr/bin/sleep run for far longer than
> > > > they should irrespective of machine load.  For example, "sleep 1" from bash
> > > > actually delays 38 seconds, not 1 second as expected.
> > > 
> > > Does disabling the "High resolution timers" feature change the behavior
> > > all?
> > 
> > I should clarify.  Everything I've given you thus far has been with the
> > "high resolution timers" feature disabled.  Two or so weeks ago I tried
> > enabling it and that's when "sleep 1" took 38 seconds to complete. 
> > Disabling "high resoltion timers" at least made "sleep 1" behave somewhat
> > saner.  I don't know if having the high res timers enabled affects the
> > accuracy of the system clock however.  I'll test this tonight.
> 
> Ok. I think I've reproduced the issue on my laptop as well. It seems to
> be a -rt issue only (I need to go back and test HRT too) as I do not see
> the problem w/ my B13 patchset. 
> 
> Possibly we are getting preempted before entering or exiting C3 mode?
> I'll need to look further. It isn't directly related to cpu load or
> idleness (a cpu pegged box doesn't drift that badly), but it might be
> io-related. 

Being IO-related is believable based on what I've seen.  In the fault
condition, the system clock averages 5 seconds behind the CMOS clock
immediately after the system has booted (which requires a large amount of
IO).  If the system sits idle not doing anything the drift is almost
non-existant.  Jackd is really good at slowing the system clock down though,
but then again jackd is doing a lot of IO.

All this seems to confirm earlier idea that there are two issues: a slowdown
in the c3tsc timer, and something in RT which causes the selection of the
c3tsc timer ahead of the acpi_pm timer.

Regards
  jonathan

Re: 2.6.14-rt21: slow-running clock

[Jonathan Woithe]

John

> > > > I'm also wondering whether this might be related to one other thing I
> > > > noticed a week or so back (also reported to the list, but thus far no
> > > > followups). If I enabled the (new) "High resolution timers" feature (as
> > > > distinct from HPET), things like /usr/bin/sleep run for far longer than
> > > > they should irrespective of machine load.  For example, "sleep 1" from bash
> > > > actually delays 38 seconds, not 1 second as expected.
> > > 
> > > Does disabling the "High resolution timers" feature change the behavior
> > > all?
> > 
> > I should clarify.  Everything I've given you thus far has been with the
> > "high resolution timers" feature disabled.  Two or so weeks ago I tried
> > enabling it and that's when "sleep 1" took 38 seconds to complete. 
> > Disabling "high resoltion timers" at least made "sleep 1" behave somewhat
> > saner.  I don't know if having the high res timers enabled affects the
> > accuracy of the system clock however.  I'll test this tonight.

Some further information.  Today I enabled the Hi res timer option in
2.6.14-rt21 with a resolution of 10000ns and did a full recompile.  Under
this kernel "sleep 1" did the right thing.  The slowdown in the c3tsc
clocksource and its selection ahead of more capable timers was still the
same in this kernel - in other words, enabling the hi res timer does not
change things.

I then changed the resolution to 1000ns (the default) and recompiled.  This
is the setting I used previously, but this time around "sleep 1" behaved
itself (c3tsc still ran slow though).  Thus for the moment it seems that the
sleep misbehaviour may have been due to some transient problem with the
configure system.  I'll test again once we've sorted out the c3tsc thing,
but it seems possible at this stage that the long "sleep" thing is not a bug
as such.

Regards
  jonathan

Re: 2.6.14-rt21: slow-running clock

[john stultz]

On Fri, 2005-12-09 at 10:49 +1030, Jonathan Woithe wrote:
> John
> 
> > > > > I'm also wondering whether this might be related to one other thing I
> > > > > noticed a week or so back (also reported to the list, but thus far no
> > > > > followups). If I enabled the (new) "High resolution timers" feature (as
> > > > > distinct from HPET), things like /usr/bin/sleep run for far longer than
> > > > > they should irrespective of machine load.  For example, "sleep 1" from bash
> > > > > actually delays 38 seconds, not 1 second as expected.
> > > > 
> > > > Does disabling the "High resolution timers" feature change the behavior
> > > > all?
> > > 
> > > I should clarify.  Everything I've given you thus far has been with the
> > > "high resolution timers" feature disabled.  Two or so weeks ago I tried
> > > enabling it and that's when "sleep 1" took 38 seconds to complete. 
> > > Disabling "high resoltion timers" at least made "sleep 1" behave somewhat
> > > saner.  I don't know if having the high res timers enabled affects the
> > > accuracy of the system clock however.  I'll test this tonight.
> 
> Some further information.  Today I enabled the Hi res timer option in
> 2.6.14-rt21 with a resolution of 10000ns and did a full recompile.  Under
> this kernel "sleep 1" did the right thing.  The slowdown in the c3tsc
> clocksource and its selection ahead of more capable timers was still the
> same in this kernel - in other words, enabling the hi res timer does not
> change things.
> 
> I then changed the resolution to 1000ns (the default) and recompiled.  This
> is the setting I used previously, but this time around "sleep 1" behaved
> itself (c3tsc still ran slow though).  Thus for the moment it seems that the
> sleep misbehaviour may have been due to some transient problem with the
> configure system.  I'll test again once we've sorted out the c3tsc thing,
> but it seems possible at this stage that the long "sleep" thing is not a bug
> as such.

Ok, I went digging further and found the c3tsc selection is correct on
your hardware. I'm just too used to my own laptop where the TSC varies
with cpu speed and we lower the rating value. So that should be ok.

I'm now working on why we mis-compensate the c3tsc clocksource in the
-RT tree. 

As for the "sleep 1" bit, I'm not sure yet. This behavior does not
change with the clocksources does it?

thanks
-john

Re: 2.6.14-rt21: slow-running clock

[Jonathan Woithe]

> > > > > > I'm also wondering whether this might be related to one other thing I
> > > > > > noticed a week or so back (also reported to the list, but thus far no
> > > > > > followups). If I enabled the (new) "High resolution timers" feature (as
> > > > > > distinct from HPET), things like /usr/bin/sleep run for far longer than
> > > > > > they should irrespective of machine load.  For example, "sleep 1" from bash
> > > > > > actually delays 38 seconds, not 1 second as expected.
> > > > > 
> > > > > Does disabling the "High resolution timers" feature change the behavior
> > > > > all?
> > > > 
> > > > I should clarify.  Everything I've given you thus far has been with the
> > > > "high resolution timers" feature disabled.  Two or so weeks ago I tried
> > > > enabling it and that's when "sleep 1" took 38 seconds to complete. 
> > > > Disabling "high resoltion timers" at least made "sleep 1" behave somewhat
> > > > saner.  I don't know if having the high res timers enabled affects the
> > > > accuracy of the system clock however.  I'll test this tonight.
> > 
> > Some further information.  Today I enabled the Hi res timer option in
> > 2.6.14-rt21 with a resolution of 10000ns and did a full recompile.  Under
> > this kernel "sleep 1" did the right thing.  The slowdown in the c3tsc
> > clocksource and its selection ahead of more capable timers was still the
> > same in this kernel - in other words, enabling the hi res timer does not
> > change things.
> > 
> > I then changed the resolution to 1000ns (the default) and recompiled.  This
> > is the setting I used previously, but this time around "sleep 1" behaved
> > itself (c3tsc still ran slow though).  Thus for the moment it seems that the
> > sleep misbehaviour may have been due to some transient problem with the
> > configure system.  I'll test again once we've sorted out the c3tsc thing,
> > but it seems possible at this stage that the long "sleep" thing is not a bug
> > as such.
> 
> Ok, I went digging further and found the c3tsc selection is correct on
> your hardware. I'm just too used to my own laptop where the TSC varies
> with cpu speed and we lower the rating value. So that should be ok.

Ok, good.  That leaves the c3tsc slowdown as the only outstanding issue at
this stage.

> I'm now working on why we mis-compensate the c3tsc clocksource in the
> -RT tree. 

No problem.  Let me know when you have something to test or need further
info.

> As for the "sleep 1" bit, I'm not sure yet. This behavior does not
> change with the clocksources does it?

That I can't be sure of - I didn't know about the clock source selection at
the time I observed it.  As mentioned above, the tests I did this morning
with the hi res timer enabled did not exhibit the problem even though tests
about 2 weeks ago showed that enabling the hi res timer caused "sleep 1" to
sleep for 38 seconds (other "sleep" calls were similarly too long).  For now
I'm happy to wait until the c3tsc thing is fixed; once that's out of the way
I'll then retest everything to see if the sleep problem is reproducable.

Regards
  jonathan

Re: 2.6.14-rt21: slow-running clock

[john stultz]

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

On Fri, 2005-12-09 at 12:49 +1030, Jonathan Woithe wrote:
> > Ok, I went digging further and found the c3tsc selection is correct on
> > your hardware. I'm just too used to my own laptop where the TSC varies
> > with cpu speed and we lower the rating value. So that should be ok.
> 
> Ok, good.  That leaves the c3tsc slowdown as the only outstanding issue at
> this stage.
> 
> > I'm now working on why we mis-compensate the c3tsc clocksource in the
> > -RT tree. 
> 
> No problem.  Let me know when you have something to test or need further
> info.

Hey Jonathan,

	Attached is a test patch to see if it doesn't resolve the issue for
you. I get a maximum change in drift of 30ppm when idling between C3
states by being more careful with the C3 TSC compensation and I also
force timekeeping updates when cpufreq events occur. 

I'm not sure if this is the right fix yet, but it might help narrow down
the problem.


Also attached is a python script that will spit out the offset value
from an ntp server and calculate the drift. This also will give us a
better idea of what is going on. If you could run it with and without
the patch, that would be great!


First shutdown NTPd then run:
	./drift-test.py [-s] <timeserver> <polling interval>

Where -s will sync the clock before running.


thanks
-john




[-- Attachment #2: c3fix-test.diff --]
[-- Type: text/x-patch, Size: 3655 bytes --]

diff --git a/arch/i386/kernel/tsc.c b/arch/i386/kernel/tsc.c
--- a/arch/i386/kernel/tsc.c
+++ b/arch/i386/kernel/tsc.c
@@ -66,13 +66,13 @@ void mark_tsc_unstable(void)
 /* Code to compensate for C3 stalls */
 static u64 tsc_c3_offset;
 
-void tsc_c3_compensate(unsigned long nsecs)
+void tsc_c3_compensate(unsigned long nsecs, u64 tsc_offset)
 {
 	/* this could def be optimized */
 	u64 cycles = ((u64)nsecs * tsc_khz);
 
 	do_div(cycles, 1000000);
-	tsc_c3_offset += cycles;
+	tsc_c3_offset += cycles - tsc_offset;
 }
 
 EXPORT_SYMBOL_GPL(tsc_c3_compensate);
@@ -263,6 +263,7 @@ static int
 time_cpufreq_notifier(struct notifier_block *nb, unsigned long val, void *data)
 {
 	struct cpufreq_freqs *freq = data;
+	unsigned long old_tsc_khz = tsc_khz;
 
 	if (val != CPUFREQ_RESUMECHANGE)
 		write_seqlock_irq(&xtime_lock);
@@ -299,6 +300,9 @@ time_cpufreq_notifier(struct notifier_bl
 	if (val != CPUFREQ_RESUMECHANGE)
 		write_sequnlock_irq(&xtime_lock);
 
+	if(old_tsc_khz != tsc_khz)
+		timeofday_force_update();
+
 	return 0;
 }
 
diff --git a/drivers/acpi/processor_idle.c b/drivers/acpi/processor_idle.c
--- a/drivers/acpi/processor_idle.c
+++ b/drivers/acpi/processor_idle.c
@@ -177,7 +177,7 @@ static void acpi_safe_halt(void)
 }
 
 static atomic_t c3_cpu_count;
-extern void tsc_c3_compensate(unsigned long nsecs);
+extern void tsc_c3_compensate(unsigned long nsecs, u64 tsc_offset);
 
 static void acpi_processor_idle(void)
 {
@@ -186,6 +186,7 @@ static void acpi_processor_idle(void)
 	struct acpi_processor_cx *next_state = NULL;
 	int sleep_ticks = 0;
 	u32 t1, t2 = 0;
+	u64 tsc1, tsc2, tsc3;
 
 	pr = processors[smp_processor_id()];
 	if (!pr)
@@ -359,12 +360,15 @@ static void acpi_processor_idle(void)
 
 		/* Get start time (ticks) */
 		t1 = inl(acpi_fadt.xpm_tmr_blk.address);
+		rdtscll(tsc1);
 		/* Invoke C3 */
 		inb(cx->address);
 		/* Dummy op - must do something useless after P_LVL3 read */
 		t2 = inl(acpi_fadt.xpm_tmr_blk.address);
 		/* Get end time (ticks) */
+		rdtscll(tsc2);
 		t2 = inl(acpi_fadt.xpm_tmr_blk.address);
+		rdtscll(tsc3);
 		if (pr->flags.bm_check) {
 			/* Enable bus master arbitration */
 			atomic_dec(&c3_cpu_count);
@@ -374,7 +378,7 @@ static void acpi_processor_idle(void)
 
 #ifdef CONFIG_GENERIC_TIME
 		/* compensate for TSC pause */
-		tsc_c3_compensate((u32)(((u64)((t2-t1)&0xFFFFFF)*286070)>>10));
+		tsc_c3_compensate((u32)(((u64)((t2-t1)&0xFFFFFF)*286070)>>10), tsc3-tsc1);
 #endif
 
 		/* Re-enable interrupts */
diff --git a/include/asm-i386/tsc.h b/include/asm-i386/tsc.h
--- a/include/asm-i386/tsc.h
+++ b/include/asm-i386/tsc.h
@@ -44,7 +44,7 @@ static inline cycles_t get_cycles(void)
 }
 
 extern void tsc_init(void);
-extern void tsc_c3_compensate(unsigned long usecs);
+extern void tsc_c3_compensate(unsigned long usecs, unsigned long long tsc_offset);
 extern void mark_tsc_unstable(void);
 
 #endif
diff --git a/include/linux/timeofday.h b/include/linux/timeofday.h
--- a/include/linux/timeofday.h
+++ b/include/linux/timeofday.h
@@ -30,6 +30,7 @@ extern int do_settimeofday(struct timesp
 
 /* Internal functions */
 extern int timeofday_is_continuous(void);
+extern void timeofday_force_update(void);
 extern void timeofday_init(void);
 
 #ifndef CONFIG_IS_TICK_BASED
diff --git a/kernel/time/timeofday.c b/kernel/time/timeofday.c
--- a/kernel/time/timeofday.c
+++ b/kernel/time/timeofday.c
@@ -745,6 +745,12 @@ static void timeofday_periodic_hook(unsi
 		jiffies + 1 + msecs_to_jiffies(PERIODIC_INTERVAL_MS));
 }
 
+
+void timeofday_force_update(void)
+{
+	timeofday_periodic_hook(0);
+}
+
 /**
  * timeofday_is_continuous - check to see if timekeeping is free running
  */

[-- Attachment #3: drift-test.py --]
[-- Type: text/x-python, Size: 1523 bytes --]

#!/usr/bin/python

# Time Drift Script
#		Periodically checks and displays time drift
#		by john stultz (jstultz@us.ibm.com)

import commands
import sys
import string
import time

server_default = "yourserverhere"
sleep_time_default  = 60

server = ""
sleep_time = 0
set_time = 0

#parse args
for arg in sys.argv[1:]:
	if arg == "-s":
		set_time = 1
	elif server == "":
		server = arg
	elif sleep_time == 0:
		sleep_time = string.atoi(arg)

if server == "":
	server = server_default
if sleep_time == 0:
	sleep_time = sleep_time_default

#set time
if (set_time == 1):
	cmd = commands.getoutput('/usr/sbin/ntpdate -ub ' + server)

cmd = commands.getoutput('/usr/sbin/ntpdate -uq ' + server)
line = string.split(cmd)

#parse original offset
start_offset = string.atof(line[-2]);
#parse original time
start_time = time.localtime(time.time())
datestr = time.strftime("%d %b %Y %H:%M:%S", start_time)

time.sleep(1)
while 1:
	cmd = commands.getoutput('/usr/sbin/ntpdate -uq ' + server)
	line = string.split(cmd)

	#parse offset
	now_offset = string.atof(line[-2]);

	#parse time
	now_time = time.localtime(time.time())
	datestr = time.strftime("%d %b %Y %H:%M:%S", now_time)

	# calculate drift
	delta_time = time.mktime(now_time) - time.mktime(start_time)
	delta_offset = now_offset - start_offset
	drift =  delta_offset / delta_time * 1000000

	#print output
	print time.strftime("%d %b %H:%M:%S",now_time), 
	print "	offset:", now_offset , 
	print "	drift:", drift ,"ppm"
	sys.stdout.flush()

	#sleep 
	time.sleep(sleep_time)

Re: 2.6.14-rt21: slow-running clock

[Jonathan Woithe]

Hi John

> On Fri, 2005-12-09 at 12:49 +1030, Jonathan Woithe wrote:
> > > Ok, I went digging further and found the c3tsc selection is correct on
> > > your hardware. I'm just too used to my own laptop where the TSC varies
> > > with cpu speed and we lower the rating value. So that should be ok.
> > 
> > Ok, good.  That leaves the c3tsc slowdown as the only outstanding issue at
> > this stage.
> > 
> > > I'm now working on why we mis-compensate the c3tsc clocksource in the
> > > -RT tree. 
> > 
> > No problem.  Let me know when you have something to test or need further
> > info.
> 
> 	Attached is a test patch to see if it doesn't resolve the issue for
> you. I get a maximum change in drift of 30ppm when idling between C3
> states by being more careful with the C3 TSC compensation and I also
> force timekeeping updates when cpufreq events occur. 

Unfortunately there's still an issue.

I applied this patch to a 2.6.14-rt21 kernel.  It applied with some offsets,
and a few chunks needed a fuzz of 1.  If you think this is important let me
know what the patch is against and I'll try that.

Anyway, to the results.  Firstly, under 2.6.14-rt21 I find today that if
the computer is left to idle with the network interface enabled, the
system time actually runs *fast* compared to the CMOS clock.  Previous
observations (which have been with the NIC module not loaded) have seen
the system clock run *slow* compared to the CMOS clock.  If I run
jackd using

  /usr/local/bin/jackd -R -d alsa -d hw:0 -r 48000 -n 4 -p 512

the previous situation (system clock slower than CMOS clock) prevails: after
less than a minute of running jack we went from

  ~/tsc> /sbin/clock -r && date
  Wed Dec 14 10:49:54 2005  -0.254472 seconds
  Wed Dec 14 10:49:55 CST 2005

to

  ~/tsc> /sbin/clock -r && date
  Wed Dec 14 10:52:46 2005  -0.116721 seconds
  Wed Dec 14 10:52:40 CST 2005

Running your drift script under 2.6.14-rt21 without jack running produces
the following:

  ~/tsc> ./drift-test.py -s 192.168.0.1
  14 Dec 10:18:59         offset: 17.504476       drift: 56445.0 ppm
  14 Dec 10:19:59         offset: 17.33345        drift: -1878.37704918 ppm
  14 Dec 10:20:59         offset: 17.090538       drift: -2954.48760331 ppm
  14 Dec 10:22:00         offset: 16.847759       drift: -3298.1978022 ppm
  14 Dec 10:23:00         offset: 16.6384         drift: -3345.58264463 ppm
  14 Dec 10:24:00         offset: 16.432669       drift: -3362.12582781 ppm
  14 Dec 10:25:01         offset: 16.201893       drift: -3432.88705234 ppm
  14 Dec 10:26:01         offset: 15.926439       drift: -3597.14420804 ppm
  14 Dec 10:27:01         offset: 15.749873       drift: -3515.85507246 ppm
  14 Dec 10:28:02         offset: 15.47964        drift: -3618.36580882 ppm
  14 Dec 10:29:02         offset: 15.302595       drift: -3552.04635762 ppm
  14 Dec 10:30:03         offset: 15.063286       drift: -3586.08270677 ppm

With jackd running on a 2.6.14-rt21 kernel we see this:

  ~/tsc> ./drift-test.py -s 192.168.0.1
  14 Dec 10:55:07         offset: 30.4774         drift: 147306.0 ppm
  14 Dec 10:55:58         offset: 39.063024       drift: 167940.961538 ppm
  14 Dec 10:56:50         offset: 47.496911       drift: 165065.548077 ppm
  14 Dec 10:57:42         offset: 56.076335       drift: 165040.00641 ppm
  14 Dec 10:58:33         offset: 64.517798       drift: 165157.990338 ppm
  14 Dec 10:59:25         offset: 73.139451       drift: 165287.092664 ppm
  14 Dec 11:00:17         offset: 81.534864       drift: 164645.562701 ppm
  14 Dec 11:01:08         offset: 90.110464       drift: 165139.143646 ppm
  14 Dec 11:02:00         offset: 98.619667       drift: 164950.65942 ppm
  14 Dec 11:02:51         offset: 107.154181      drift: 165213.090323 ppm
  14 Dec 11:03:43         offset: 115.666054      drift: 165059.883946 ppm
  14 Dec 11:04:35         offset: 124.174761      drift: 164929.115993 ppm
  14 Dec 11:05:26         offset: 132.740329      drift: 165177.798387 ppm

Moving to a 2.6.14-rt21 with your patch from yesterday, the idling machine
with the tg3 module loaded had the following situation immediately
after booting:

  ~> /sbin/clock -r && date
  Wed Dec 14 11:09:54 2005  -0.662011 seconds
  Wed Dec 14 11:09:47 CST 2005

After sitting idle for a short while we had:

  jwoithe@halite:~> /sbin/clock -r && date
  Wed Dec 14 11:12:05 2005  -0.709709 seconds
  Wed Dec 14 11:11:57 CST 2005

So in this case the system clock is definitely running slower than the CMOS
clock.

The drift stats with the sc patch (ie: 2.6.14-rt21 with your patch from
yesterday), without jack running:

  ~/tsc> ./drift-test.py -s 192.168.0.1
  14 Dec 09:53:26         offset: 0.508609        drift: 62263.0 ppm
  14 Dec 09:54:26         offset: 0.677778        drift: 3793.96721311 ppm
  14 Dec 09:55:26         offset: 0.885301        drift: 3627.72727273 ppm
  14 Dec 09:56:26         offset: 1.012511        drift: 3127.98342541 ppm
  14 Dec 09:57:26         offset: 1.179381        drift: 3041.63900415 ppm
  14 Dec 09:58:26         offset: 1.275088        drift: 2753.29568106 ppm
  14 Dec 09:59:25         offset: 1.53823         drift: 3033.01111111 ppm
  14 Dec 10:00:25         offset: 1.682737        drift: 2943.78809524 ppm
  14 Dec 10:01:25         offset: 1.810167        drift: 2841.29375 ppm
  14 Dec 10:02:25         offset: 1.908942        drift: 2708.51111111 ppm
  14 Dec 10:03:25         offset: 2.101228        drift: 2758.13666667 ppm
  14 Dec 10:04:25         offset: 2.199901        drift: 2656.90151515 ppm
  14 Dec 10:05:25         offset: 2.564818        drift: 2942.32222222 ppm
  14 Dec 10:06:25         offset: 2.695642        drift: 2883.71282051 ppm
  14 Dec 10:07:25         offset: 2.859662        drift: 2872.9952381 ppm
  14 Dec 10:08:25         offset: 2.990623        drift: 2826.97444444 ppm
  14 Dec 10:09:25         offset: 3.221054        drift: 2890.32083333 ppm
  14 Dec 10:10:25         offset: 3.364036        drift: 2860.48039216 ppm
  14 Dec 10:11:25         offset: 3.526485        drift: 2851.98055556 ppm
  14 Dec 10:12:25         offset: 3.661997        drift: 2820.74649123 ppm
  14 Dec 10:13:25         offset: 3.853566        drift: 2839.35 ppm

With the tsc patch (ie: 2.6.14-rt21 + your patch) with jackd running:

  ~/tsc> ./drift-test.py -s 192.168.0.1
  14 Dec 11:14:06         offset: 158.954383      drift: 171300.0 ppm
  14 Dec 11:14:55         offset: 169.858831      drift: 221514.96 ppm
  14 Dec 11:15:44         offset: 180.577996      drift: 220150.636364 ppm
  14 Dec 11:16:33         offset: 191.516626      drift: 221172.587838 ppm
  14 Dec 11:17:23         offset: 202.295611      drift: 219760.242424 ppm
  14 Dec 11:18:12         offset: 213.217457      drift: 220382.080972 ppm
  14 Dec 11:19:02         offset: 223.900228      drift: 219249.646465 ppm
  14 Dec 11:19:51         offset: 234.819493      drift: 219758.410405 ppm
  14 Dec 11:20:40         offset: 245.524901      drift: 219599.539241 ppm
  14 Dec 11:21:29         offset: 256.4786        drift: 220034.948198 ppm
  14 Dec 11:22:19         offset: 267.234911      drift: 219538.11336 ppm

With a plain 2.6.14 kernel (for reference) without jackd running:

  ~/tsc> ./drift-test.py -s 192.168.0.1
  14 Dec 11:25:24         offset: 275.996533      drift: -18.0000000114 ppm
  14 Dec 11:26:24         offset: 275.995463      drift: -17.8360655744 ppm
  14 Dec 11:27:24         offset: 275.994522      drift: -16.7685950413 ppm
  14 Dec 11:28:25         offset: 275.993527      drift: -16.6153846156 ppm
  14 Dec 11:29:25         offset: 275.992539      drift: -16.5785123966 ppm
  14 Dec 11:30:25         offset: 275.991556      drift: -16.5397350994 ppm
  14 Dec 11:31:25         offset: 275.990544      drift: -16.593922652 ppm
  14 Dec 11:32:25         offset: 275.989575      drift: -16.5308056872 ppm
  14 Dec 11:33:25         offset: 275.988622      drift: -16.4502074689 ppm

Finally, 2.6.14 with jackd running:

  ~/tsc> ./drift-test.py -s 192.168.0.1
  14 Dec 11:34:06         offset: 275.987919      drift: -20.0000000063 ppm
  14 Dec 11:35:07         offset: 275.986933      drift: -16.225806451 ppm
  14 Dec 11:36:07         offset: 275.985932      drift: -16.4508196721 ppm
  14 Dec 11:37:07         offset: 275.984939      drift: -16.4835164834 ppm
  14 Dec 11:38:07         offset: 275.983928      drift: -16.5743801653 ppm
  14 Dec 11:39:07         offset: 275.982924      drift: -16.6059602648 ppm
  14 Dec 11:40:07         offset: 275.981923      drift: -16.6187845304 ppm
  14 Dec 11:41:07         offset: 275.980915      drift: -16.644549763 ppm
  14 Dec 11:42:07         offset: 275.97991       drift: -16.6576763485 ppm
  14 Dec 11:43:07         offset: 275.978898      drift: -16.6808118081 ppm


Regards
  jonathan

Re: 2.6.14-rt21: slow-running clock

[john stultz]

On Wed, 2005-12-14 at 11:52 +1030, Jonathan Woithe wrote:
> Hi John
> 
> > On Fri, 2005-12-09 at 12:49 +1030, Jonathan Woithe wrote:
> > > > Ok, I went digging further and found the c3tsc selection is correct on
> > > > your hardware. I'm just too used to my own laptop where the TSC varies
> > > > with cpu speed and we lower the rating value. So that should be ok.
> > > 
> > > Ok, good.  That leaves the c3tsc slowdown as the only outstanding issue at
> > > this stage.
> > > 
> > > > I'm now working on why we mis-compensate the c3tsc clocksource in the
> > > > -RT tree. 
> > > 
> > > No problem.  Let me know when you have something to test or need further
> > > info.
> > 
> > 	Attached is a test patch to see if it doesn't resolve the issue for
> > you. I get a maximum change in drift of 30ppm when idling between C3
> > states by being more careful with the C3 TSC compensation and I also
> > force timekeeping updates when cpufreq events occur. 
> 
> Unfortunately there's still an issue.

Ah, drat. 

I'm just going to dump the c3tsc clocksource for now. If C3 mode is
available, the ACPI PM timer is available (since it is used for C3
timing), so we'll just fall back to ACPI PM if we see the cpu entering
C3 mode.

I'm working to respin a new release tonight, hopefully that will make it
upstream to -rt soon and that should take care of it. Later I can look
at reworking the c3tsc clocksource, but for now things need to just
work.

Thanks again for the testing and feedback, I really appreciate your
help!
-john

Re: 2.6.14-rt21: slow-running clock

[Jonathan Woithe]

Hi John

> > > On Fri, 2005-12-09 at 12:49 +1030, Jonathan Woithe wrote:
> > > > > I'm now working on why we mis-compensate the c3tsc clocksource in the
> > > > > -RT tree. 
> > > > 
> > > > No problem.  Let me know when you have something to test or need further
> > > > info.
> > > 
> > > 	Attached is a test patch to see if it doesn't resolve the issue for
> > > you. I get a maximum change in drift of 30ppm when idling between C3
> > > states by being more careful with the C3 TSC compensation and I also
> > > force timekeeping updates when cpufreq events occur. 
> > 
> > Unfortunately there's still an issue.
> 
> Ah, drat. 
> 
> I'm just going to dump the c3tsc clocksource for now. If C3 mode is
> available, the ACPI PM timer is available (since it is used for C3
> timing), so we'll just fall back to ACPI PM if we see the cpu entering
> C3 mode.
>
> I'm working to respin a new release tonight, hopefully that will make it
> upstream to -rt soon and that should take care of it. Later I can look
> at reworking the c3tsc clocksource, but for now things need to just
> work.

Not a problem - I'll test this next release soon (perhaps via -rt) and
confirm that things "just work" for me.  I'm happy to keep testing things -
if you do need further tests done for c3tsc in future drop me a line.

Regards
  jonathan