2.6.16-rc2 powerpc timestamp skew
Hi folks,
When running a 2.6.16-rc2 kernel on a powerpc system (Mac Mini; Freescale 7447A):
$ date && touch f && ls -l f && rm -f f && date Sun Feb 12 12:20:14 GMT 2006 -rw-r--r-- 1 rleigh rleigh 0 2006-02-12 12:23 Sun Feb 12 12:20:14 GMT 2006
Notice the timestamp is 3 minutes in the future compared with the system time. "make" is not a very happy bunny running on this kernel due to every touched file being 3 minutes in the future.
When the same command is run on 2.6.15.3:
$ date && touch f && ls -l f && rm -f f && date Sun Feb 12 14:27:27 GMT 2006 -rw-r--r-- 1 rleigh rleigh 0 2006-02-12 14:27 Sun Feb 12 14:27:27 GMT 2006
In this case the times are identical, as you would expect.
In both these cases, the chrony NTP daemon is running, if that might be a problem.
Regards,
Roger
Signature · 4 lines
Roger Leigh
Printing on GNU/Linux? http://gutenprint.sourceforge.net/
Debian GNU/Linux http://www.debian.org/
GPG Public Key: 0x25BFB848. Please sign and encrypt your mail.Quoted 21 lines · Roger Leigh
Hi folks,
When running a 2.6.16-rc2 kernel on a powerpc system (Mac Mini; Freescale 7447A):
$ date && touch f && ls -l f && rm -f f && date Sun Feb 12 12:20:14 GMT 2006 -rw-r--r-- 1 rleigh rleigh 0 2006-02-12 12:23 Sun Feb 12 12:20:14 GMT 2006Notice the timestamp is 3 minutes in the future compared with the system time. "make" is not a very happy bunny running on this kernel due to every touched file being 3 minutes in the future.
When the same command is run on 2.6.15.3:
$ date && touch f && ls -l f && rm -f f && date Sun Feb 12 14:27:27 GMT 2006 -rw-r--r-- 1 rleigh rleigh 0 2006-02-12 14:27 Sun Feb 12 14:27:27 GMT 2006
Quoted 4 lines
In this case the times are identical, as you would expect.
In both these cases, the chrony NTP daemon is running, if that might be a problem.
I don't know whether it is reloated, but since I installed a 2.6.16-rc2 kernel on my G4/466, I have log messages that claim that the clock error rate is too large for NTP to correct (larger than 512ppm).
Gabriel
Quoted 8 lines · Roger Leigh
When running a 2.6.16-rc2 kernel on a powerpc system (Mac Mini; Freescale 7447A):
$ date && touch f && ls -l f && rm -f f && date Sun Feb 12 12:20:14 GMT 2006 -rw-r--r-- 1 rleigh rleigh 0 2006-02-12 12:23 Sun Feb 12 12:20:14 GMT 2006
Quoted 6 lines
Notice the timestamp is 3 minutes in the future compared with the system time. "make" is not a very happy bunny running on this kernel due to every touched file being 3 minutes in the future.
In both these cases, the chrony NTP daemon is running, if that might be a problem.
Some further information:
- this does not appear to affect i386 kernels
- I have
CONFIG_HZ_250=y
CONFIG_HZ=250 in my .config; the full config is at
http://people.debian.org/~rleigh/config-2.6.16-rc2
Regards,
Roger
Signature · 4 lines
Roger Leigh
Printing on GNU/Linux? http://gutenprint.sourceforge.net/
Debian GNU/Linux http://www.debian.org/
GPG Public Key: 0x25BFB848. Please sign and encrypt your mail.Quoted 17 lines · Roger Leigh
Quoted 8 lines · Roger Leigh
When running a 2.6.16-rc2 kernel on a powerpc system (Mac Mini; Freescale 7447A):
$ date && touch f && ls -l f && rm -f f && date Sun Feb 12 12:20:14 GMT 2006 -rw-r--r-- 1 rleigh rleigh 0 2006-02-12 12:23 Sun Feb 12 12:20:14 GMT 2006Quoted 6 lines
Notice the timestamp is 3 minutes in the future compared with the system time. "make" is not a very happy bunny running on this kernel due to every touched file being 3 minutes in the future.
In both these cases, the chrony NTP daemon is running, if that might be a problem.
Quoted 8 lines
Some further information:
- this does not appear to affect i386 kernels
- I haveCONFIG_HZ_250=y CONFIG_HZ=250in my .config; the full config is at
http://people.debian.org/~rleigh/config-2.6.16-rc2
I have in my config-2.6.16-rc2 (G4 1.2Ghz, 7447A)CONFIG_HZ_1000=yCONFIG_HZ=1000
and have
$ date && touch f && ls -l f && rm -f f && date Sun Feb 12 21:08:43 CET 2006 -rw-r--r-- 1 zhang zhang 0 2006-02-12 21:08 f Sun Feb 12 21:08:43 CET 2006
I don't have ntp daemon running (ntpdate at boot).
Regards,
Bin
Quoted 12 lines
Regards,
Roger--
Roger Leigh
Printing on GNU/Linux? http://gutenprint.sourceforge.net/
Debian GNU/Linux http://www.debian.org/
GPG Public Key:0x25BFB848. Please sign and encrypt your mail.
Quoted 2 lines · Roger Leigh
In both these cases, the chrony NTP daemon is running, if that might be a problem.
I dont run Debian, but:
My G4/466 has the hwclock at 1970 for some reason. The early bootscripts call klogd, which calls nanosleep. This syscall takes 3 hours to complete.
A bit userland debugging shows that hwclock is 1970, system time is also 1970 when nanosleep starts. But when it returns, the time is correct. Its already at the end of the /etc/init.d/boot.d/S* scripts, nothing else runs there. Bug exists since at least 2.6.15-git12, 2.6.15 was ok. Fatfingerd kernel debug patch and lost remote access...
Quoted 9 lines · Olaf Hering
Quoted 2 lines · Roger Leigh
In both these cases, the chrony NTP daemon is running, if that might be a problem.
I dont run Debian, but:
My G4/466 has the hwclock at 1970 for some reason. The early bootscripts call klogd, which calls nanosleep. This syscall takes 3 hours to complete.
Firmware says the date is in 2006, so its a kernel bug. Looking.
Quoted 11 lines · Olaf Hering
Quoted 9 lines · Olaf Hering
Quoted 2 lines · Roger Leigh
In both these cases, the chrony NTP daemon is running, if that might be a problem.
I dont run Debian, but:
My G4/466 has the hwclock at 1970 for some reason. The early bootscripts call klogd, which calls nanosleep. This syscall takes 3 hours to complete.
nanosleep is usually called with *rqtp <something>, *rmtp NULL. Only in the klogd case both pointers are equal.
Quoted 21 lines · Roger Leigh
Hi folks,
When running a 2.6.16-rc2 kernel on a powerpc system (Mac Mini; Freescale 7447A):
$ date && touch f && ls -l f && rm -f f && date Sun Feb 12 12:20:14 GMT 2006 -rw-r--r-- 1 rleigh rleigh 0 2006-02-12 12:23 Sun Feb 12 12:20:14 GMT 2006Notice the timestamp is 3 minutes in the future compared with the system time. "make" is not a very happy bunny running on this kernel due to every touched file being 3 minutes in the future.
When the same command is run on 2.6.15.3:
$ date && touch f && ls -l f && rm -f f && date Sun Feb 12 14:27:27 GMT 2006 -rw-r--r-- 1 rleigh rleigh 0 2006-02-12 14:27 Sun Feb 12 14:27:27 GMT 2006
Quoted 4 lines
In this case the times are identical, as you would expect.
In both these cases, the chrony NTP daemon is running, if that might be a problem.
Can you strace vs. ltrace and see if the gettimeofday or clock_gettime syscalls are ever called ? I wonder if you have a glibc new enough to use the vDSO to obtain the time or if it's using the syscall... The vDSO on ppc32 is very new.
Also, are your kernels built with ARCH=ppc or ARCH=powerpc ?
Ben.
Quoted 22 lines · Benjamin Herrenschmidt
Quoted 21 lines · Roger Leigh
Hi folks,
When running a 2.6.16-rc2 kernel on a powerpc system (Mac Mini; Freescale 7447A):
$ date && touch f && ls -l f && rm -f f && date Sun Feb 12 12:20:14 GMT 2006 -rw-r--r-- 1 rleigh rleigh 0 2006-02-12 12:23 Sun Feb 12 12:20:14 GMT 2006Notice the timestamp is 3 minutes in the future compared with the system time. "make" is not a very happy bunny running on this kernel due to every touched file being 3 minutes in the future.
When the same command is run on 2.6.15.3:
$ date && touch f && ls -l f && rm -f f && date Sun Feb 12 14:27:27 GMT 2006 -rw-r--r-- 1 rleigh rleigh 0 2006-02-12 14:27 Sun Feb 12 14:27:27 GMT 2006
Quoted 7 lines
Quoted 4 lines
In this case the times are identical, as you would expect.
In both these cases, the chrony NTP daemon is running, if that might be a problem.
Can you strace vs. ltrace and see if the gettimeofday or
clock_gettimesyscalls are ever called ?
| strace | ltrace
-----------+---------------+------------------------------------
2.6.15 | |
date | clock_gettime | clock_gettime -> SYS_clock_gettime,
| | localtime, strftime
touch | utimes | futimes -> SYS_utimes
| |
2.6.16-rc2 | |
date | clock_gettime | clock_gettime -> SYS_clock_gettime,
| | localtime, strftime
touch | utimes | futimes -> SYS_utimes[clock_gettime(CLOCK_REALTIME, {1139826613, 157402000}) = 0]
Quoted 3 lines
I wonder if you have a glibc new enough to
use the vDSO to obtain the time or if it's using the syscall... The vDSO on ppc32 is very new.
It's glibc 2.3.5 (Debian libc6 2.3.5-13).
Quoted 1 line
Also, are your kernels built with ARCH=ppc or ARCH=powerpc ?
ppc.
Thanks,
Roger
Signature · 4 lines
Roger Leigh
Printing on GNU/Linux? http://gutenprint.sourceforge.net/
Debian GNU/Linux http://www.debian.org/
GPG Public Key: 0x25BFB848. Please sign and encrypt your mail.Quoted 16 lines
Quoted 3 lines
Can you strace vs. ltrace and see if the gettimeofday or
clock_gettimesyscalls are ever called ?| strace | ltrace
-----------+---------------+------------------------------------2.6.15 | | date | clock_gettime | clock_gettime -> SYS_clock_gettime, | | localtime, strftime touch | utimes | futimes -> SYS_utimes | | 2.6.16-rc2 | | date | clock_gettime | clock_gettime -> SYS_clock_gettime, | | localtime, strftime touch | utimes | futimes -> SYS_utimes
Quoted 7 lines
[
clock_gettime(CLOCK_REALTIME, {1139826613, 157402000})= 0]Quoted 3 lines
I wonder if you have a glibc new enough to
use the vDSO to obtain the time or if it's using the syscall... The vDSO on ppc32 is very new.It's glibc 2.3.5 (Debian libc6 2.3.5-13).
Ok, does not using NTP fixes it ?
Ben.
Quoted 1 line · Benjamin Herrenschmidt
Ok, does not using NTP fixes it ?
Try this patch. With this the values from gettimeofday() or the VDSO should stay exactly in sync with xtime even if NTP is adjusting the clock.
This patch still has quite a few debugging printks in it, so it's not final by any means. I'll be interested to hear how it goes, and in particular whether or not you see any "oops, time got ahead" messages.
Paul.
arch/powerpc/kernel/sys_ppc32.c +0 -4
@@ -176,7 +176,6 @@ };extern int do_adjtimex (struct timex *); -extern void ppc_adjtimex (void );asmlinkage long compat_sys_adjtimex (struct timex32 __user *utp) {
@@ -209,9 +208,6 @@ ret =do_adjtimex (&txc); -/* adjust the conversion of TB to time of day to track adjtimex */ -ppc_adjtimex (); - if(put_user(txc.modes, &utp->modes) || __put_user(txc.offset, &utp->offset) || __put_user(txc.freq, &utp->freq) ||
arch/powerpc/kernel/time.c +109 -167
376 lines not on this page · raw message
include/linux/timex.h +3 -0
@@ -345,6 +345,9 @@#endif /* !CONFIG_TIME_INTERPOLATION */ +/* Returns how long ticks are at present, in ns / 2^(SHIFT_SCALE-10). */ +extern u64 current_tick_length (void ); +#endif /* KERNEL */ #endif /* LINUX_TIMEX_H */
kernel/timer.c +24 -0
@@ -759,6 +759,30 @@ }/* +* Return how long ticks are at the moment, that is, how much time +* update_wall_time_one_tick will add to xtime next time we call it +* (assuming no calls to do_adjtimex in the meantime). +* The return value is in fixed-point nanoseconds with SHIFT_SCALE-10 +* bits to the right of the binary point. +* This function has no side-effects. +*/ +u64 current_tick_length (void ) +{ +long time_adjust_step, delta_nsec; + +if ((time_adjust_step = time_adjust) !=0 ) { +/* +* Limit the amount of the step to be in the range +* -tickadj .. +tickadj +*/ + time_adjust_step =min (time_adjust_step, (long )tickadj); + time_adjust_step =max (time_adjust_step, (long )-tickadj); + } + delta_nsec = tick_nsec + time_adjust_step *1000 ; +return ((u64 ) delta_nsec << (SHIFT_SCALE -10 )) + time_adj; +} + +/* * Using a loop looks inefficient, but "ticks" is * usually just one (we shouldn't be losing ticks, * we're doing this this way mainly for interrupt
Quoted 11 lines · Paul Mackeras
Quoted 1 line · Benjamin Herrenschmidt
Ok, does not using NTP fixes it ?
Try this patch. With this the values from
gettimeofday()or the VDSO should stay exactly in sync with xtime even if NTP is adjusting the clock.This patch still has quite a few debugging printks in it, so it's not final by any means. I'll be interested to hear how it goes, and in particular whether or not you see any "oops, time got ahead" messages.
This fixes my hang during boot.
good.txt renamed from bad.txt +24 -14
@@ -34,12 +34,20 @@ GMT Delta read from XPRAM: 120 minutes, DST: on time_init: decrementer frequency = 33.290001 MHz time_init: processor frequency = 466.666665 MHz +HZ = 250 tb_freq = 33290001 tick_nsec = 4000000 +tb_to_xs = 810448dc5c2ca70 (old way) +ticklen_to_xs = 0 10e9155d07742ee3 +tb_to_xs = 8104491d617e483 (new way) Console: colour dummy device 80x25 pmac_zilog: i2c-modem detected, id: 1 Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) +oops, time got ahead: 1138967190.003999 > 1138959990.000000000 + xtime was 0.000000000 tb was 0 tick 909725147 + tlen 0x3d0900000 tb now 909726490 tpj 133160 + gtod tbstamp 909591987 xsec 0x43e3429600000 t2x 0x8104491d617e483 High memory: 0k -Memory: 251768k/262144k available (3416k kernel code, 10064k reserved, 556k data, 467k bss, 196k init) +Memory: 251768k/262144k available (3420k kernel code, 10072k reserved, 556k data, 467k bss, 196k init) Calibrating delay loop... 66.30 BogoMIPS (lpj=132608) Security Framework v1.0.0 initialized Mount-cache hash table entries: 512
@@ -71,7 +79,7 @@ TC classifier action (bugs to [email protected] cc [email protected]) Thermal assist unit using timers, shrink_timer: 500 jiffies audit: initializing netlink socket (disabled) -audit(1138960784.708:1): initialized +audit(1138959990.708:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) Initializing Cryptographic API
@@ -198,8 +206,8 @@ ide-floppy driver 0.99.newide hdd: No disk in drive hdd: 0kB, 0/64/32 CHS, 4096 kBps, 512 sector size, 2941 rpm -device-mapper: 4.5.0-ioctl (2005-10-04) initialised: [email protected] -dm-netlink version 0.0.2 loaded +hdc: ATAPI 32X CD-ROM CD-R/RW drive, 4096kB Cache, (U)DMA +Uniform CD-ROM driver Revision: 3.20 USB Universal Host Controller Interface driver v2.3 PCI: Enabling device 0001:10:12.0 (0014 -> 0015) PCI: Via IRQ fixup for 0001:10:12.0, from 52 to 4
@@ -241,34 +249,36 @@ usb usb5: configuration #1 chosen from 1 choice hub 5-0:1.0: USB hub found hub 5-0:1.0: 4 ports detected -hdc: ATAPI 32X CD-ROM CD-R/RW drive, 4096kB Cache, (U)DMA -Uniform CD-ROM driver Revision: 3.20 8139too Fast Ethernet driver 0.9.27 +sungem.c:v0.98 8/24/03 David S. Miller ([email protected]) PCI: Enabling device 0001:10:14.0 (0004 -> 0007) -eth0: RealTek RTL8139 at 0xd106e000, 00:50:fc:76:65:12, IRQ 54 +eth0: RealTek RTL8139 at 0xd105a000, 00:50:fc:76:65:12, IRQ 54 eth0: Identified 8139 chip type 'RTL-8100B/8139D' -8139cp: 10/100 PCI Ethernet driver v1.2 (Mar 22, 2004) -sungem.c:v0.98 8/24/03 David S. Miller ([email protected]) PHY ID: 206053, addr: 0 +eth1: Sun GEM (PCI) 10/100/1000BaseT Ethernet 00:30:65:f3:4c:ae +eth1: Found BCM5401 PHY +8139cp: 10/100 PCI Ethernet driver v1.2 (Mar 22, 2004) ieee1394: Initialized config rom entry `ip1394' +JBD: barrier-based sync failed on hda13 - disabling barriers PCI: Enabling device 0001:10:12.3 (0090 -> 0093) PCI: Via IRQ fixup for 0001:10:12.3, from 52 to 4 ohci1394: fw-host0: OHCI-1394 1.0 (PCI): IRQ=[52] MMIO=[80084000-800847ff] Max Packet=[2048] IR/IT contexts=[8/8] -eth1: Sun GEM (PCI) 10/100/1000BaseT Ethernet 00:30:65:f3:4c:ae -eth1: Found BCM5401 PHY ohci1394: fw-host1: Unexpected PCI resource length of 1000! ohci1394: fw-host1: OHCI-1394 1.0 (PCI): IRQ=[40] MMIO=[f5000000-f50007ff] Max Packet=[2048] IR/IT contexts=[8/8] -JBD: barrier-based sync failed on hda13 - disabling barriers ieee1394: Host added: ID:BUS[0-00:1023] GUID[0011060000006685] -ieee1394: Host added: ID:BUS[1-00:1023] GUID[003065fffef34cae] eth1: Link is up at 100 Mbps, full-duplex. +ieee1394: Host added: ID:BUS[1-00:1023] GUID[003065fffef34cae] +device-mapper: 4.5.0-ioctl (2005-10-04) initialised: [email protected] +dm-netlink version 0.0.2 loaded +hdd: No disk in drive loop: loaded (max 8 devices) kjournald starting. Commit interval 5 seconds EXT3 FS on hda14, internal journal EXT3-fs: mounted filesystem with ordered data mode. AppArmor: AppArmor (version 2.0-19.43r6152) initialized -audit(1138960811.468:2): AppArmor (version 2.0-19.43r6152) initialized +audit(1138960018.908:2): AppArmor (version 2.0-19.43r6152) initialized +do_settimeofday(1138963619.000000000) eth1: Link is up at 100 Mbps, full-duplex. eth1: Pause is enabled (rxfifo: 10240 off: 7168 on: 5632) NET: Registered protocol family 10
Total memory = 256MB; using 512kB for hash table (at cff80000)
Linux version 2.6.16-rc3-git3-20060215_bug149895-default (geeko@buildhost) (gcc version 4.1.0 20060210 (prerelease) (SUSE Linux)) #1 Wed Feb 15 00:20:20 UTC 2006 Found initrd at 0xc0a00000:0xc0c2a000
Found UniNorth memory controller & host bridge @ 0xf8000000 revision: 0x11
Mapped at 0xfdfc0000
Found a Keylargo mac-io controller, rev: 3, mapped at 0xfdf40000
Processor NAP mode on idle enabled.
PowerMac motherboard: PowerMac G4 Silver
Using native/NAP idle loop
Found UniNorth PCI host bridge at 0xf0000000. Firmware bus number: 0->0
Found UniNorth PCI host bridge at 0xf2000000. Firmware bus number: 0->0
Found UniNorth PCI host bridge at 0xf4000000. Firmware bus number: 0->0
via-pmu: Server Mode is disabled
PMU driver v2 initialized for Core99, firmware: 0c
nvram: Checking bank 0...
nvram: gen0=348, gen1=347
nvram: Active bank is: 0
nvram: OF partition at 0x210
nvram: XP partition at 0x1220
nvram: NR partition at 0x1320
Top of RAM: 0x10000000, Total RAM: 0x10000000
Memory hole size: 0MB
On node 0 totalpages: 65536
DMA zone: 65536 pages, LIFO batch:15
DMA32 zone: 0 pages, LIFO batch:0
Normal zone: 0 pages, LIFO batch:0
HighMem zone: 0 pages, LIFO batch:0
Built 1 zonelists
Kernel command line: root=/dev/hda13 quiet video=aty128fb:1024x768@85 sysrq=1
mpic: Setting up MPIC " MPIC 1 " version 1.2 at 80040000, max 4 CPUs
mpic: ISU size: 64, shift: 6, mask: 3f
mpic: Initializing for 64 sources
PID hash table entries: 2048 (order: 11, 32768 bytes)
GMT Delta read from XPRAM: 120 minutes, DST: ontime_init: decrementer frequency = 33.290001 MHztime_init: processor frequency = 466.666665 MHz
HZ = 250 tb_freq = 33290001 tick_nsec = 4000000tb_to_xs = 810448dc5c2ca70 (old way)ticklen_to_xs = 0 10e9155d07742ee3tb_to_xs = 8104491d617e483 (new way)
Console: colour dummy device 80x25pmac_zilog: i2c-modem detected, id: 1
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
oops, time got ahead: 1138967190.003999 > 1138959990.000000000
xtime was 0.000000000 tb was 0 tick 909725147
tlen 0x3d0900000 tb now 909726490 tpj 133160
gtod tbstamp 909591987 xsec 0x43e3429600000 t2x 0x8104491d617e483
High memory: 0k
Memory: 251768k/262144k available (3420k kernel code, 10072k reserved, 556k data, 467k bss, 196k init)
Calibrating delay loop... 66.30 BogoMIPS (lpj=132608)
Security Framework v1.0.0 initialized
Mount-cache hash table entries: 512
device-tree: property "l2-cache" name conflicts with node in /cpus/PowerPC,G4@0
checking if image is initramfs... it is
Freeing initrd memory: 2216k freed
NET: Registered protocol family 16
KeyWest i2c @0xf8001003 irq 42 /uni-n@f8000000/i2c@f8001000
channel 0 bus <multibus>
channel 1 bus <multibus>
KeyWest i2c @0x80018000 irq 26 /pci@f2000000/mac-io@17/i2c@18000
channel 0 bus <multibus>
PMU i2c /pci@f2000000/mac-io@17/via-pmu@16000
channel 1 bus <multibus>
channel 2 bus <multibus>
Installing base platform functions...
Installing MMIO functions for macio /pci@f2000000/mac-io@17
Installing GPIO functions for macio /pci@f2000000/mac-io@17
Calling initial GPIO functions for macio /pci@f2000000/mac-io@17
Installing functions for UniN /uni-n@f8000000
All base functions installed
PCI: Probing PCI hardware
PCI: Cannot allocate resource region 4 of device 0001:10:12.0
PCI: Cannot allocate resource region 4 of device 0001:10:12.1
PCI: Cannot allocate resource region 1 of device 0001:10:12.3
PCI: Cannot allocate resource region 0 of device 0001:10:14.0
usbcore: registered new driver usbfs
usbcore: registered new driver hub
TC classifier action (bugs to [email protected] cc [email protected])
Thermal assist unit using timers, shrink_timer: 500 jiffies
audit: initializing netlink socket (disabled)
audit(1138959990.708:1): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
PCI: Enabling device 0000:00:10.0 (0086 -> 0087)
aty128fb: Invalid ROM signature 1111 should be 0xaa55
aty128fb: BIOS not located, guessing timings.
aty128fb: Rage128 PF PRO AGP [chip rev 0x1] 16M 128-bit SDR SGRAM (1:1)
Console: switching to colour frame buffer device 128x48
fb0: ATY Rage128 frame buffer device on Rage128 PF PRO AGP
Generic RTC Driver v1.07
Macintosh non-volatile memory driver v1.1pmac_zilog: 0.6 (Benjamin Herrenschmidt <[email protected]>)
ttyS0 at MMIO 0x80013020 (irq = 22) is a Z85c30 ESCC - Internal modem
ttyS1 at MMIO 0x80013000 (irq = 50) is a Z85c30 ESCC - Serial port
RAMDISK driver initialized: 16 RAM disks of 123456K size 1024 blocksize
MacIO PCI driver attached to Keylargo chipset
input: Macintosh mouse button emulation as /class/input/input0apm_emu: APM Emulation 0.5 initialized.
adb: starting probe task...
adb: finished probe task...
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ide0: Found Apple KeyLargo ATA-4 controller, bus ID 2, irq 19
Probing IDE interface ide0...
hda: Maxtor 33073H3 B, ATA DISK drive
hda: Enabling Ultra DMA 4
ide0 at 0xd1024000-0xd1024007,0xd1024160 on irq 19
ide1: Found Apple KeyLargo ATA-3 controller, bus ID 0, irq 20
Probing IDE interface ide1...
hdc: SONY CD-RW CRX140E, ATAPI CD/DVD-ROM drive
hdd: IOMEGA ZIP 250 ATAPI, ATAPI FLOPPY drive
hdc: Enabling MultiWord DMA 2
ide1 at 0xd1026000-0xd1026007,0xd1026160 on irq 20
ide2: Found Apple KeyLargo ATA-3 controller, bus ID 1, irq 21
Probing IDE interface ide2...
Probing IDE interface ide2...
hda: max request size: 128KiB
hda: 60032448 sectors (30736 MB) w/2048KiB Cache, CHS=59556/16/63, UDMA(66)
hda: cache flushes not supported
hda: [mac] hda1 hda2 hda3 hda4 hda5 hda6 hda7 hda8 hda9 hda10 hda11 hda12 hda13 hda14 hda15ohci_hcd: 2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
PCI: Enabling device 0001:10:18.0 (0000 -> 0002)ohci_hcd 0001:10:18.0: OHCI Host Controllerohci_hcd 0001:10:18.0: new USB bus registered, assigned bus number 1ohci_hcd 0001:10:18.0: irq 27, io mem 0x80083000
usb usb1: new device found, idVendor=0000, idProduct=0000
usb usb1: new device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: OHCI Host Controller
usb usb1: Manufacturer: Linux 2.6.16-rc3-git3-20060215_bug149895-default ohci_hcd
usb usb1: SerialNumber: 0001:10:18.0
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
PCI: Enabling device 0001:10:19.0 (0000 -> 0002)ohci_hcd 0001:10:19.0: OHCI Host Controllerohci_hcd 0001:10:19.0: new USB bus registered, assigned bus number 2ohci_hcd 0001:10:19.0: irq 28, io mem 0x80082000
usb usb2: new device found, idVendor=0000, idProduct=0000
usb usb2: new device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: OHCI Host Controller
usb usb2: Manufacturer: Linux 2.6.16-rc3-git3-20060215_bug149895-default ohci_hcd
usb usb2: SerialNumber: 0001:10:19.0
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
usb 1-1: new full speed USB device using ohci_hcd and address 2
usb 1-1: new device found, idVendor=05ac, idProduct=1001
usb 1-1: new device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-1: Product: Hub in Apple USB Keyboard
usb 1-1: Manufacturer: Alps Electric
usb 1-1: configuration #1 chosen from 1 choice
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 3 ports detected
usb 1-1.1: new low speed USB device using ohci_hcd and address 3
usb 1-1.1: new device found, idVendor=05ac, idProduct=0202
usb 1-1.1: new device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-1.1: Product: Apple USB Keyboard
usb 1-1.1: Manufacturer: Alps Electric
usb 1-1.1: configuration #1 chosen from 1 choice
usb 1-1.3: new low speed USB device using ohci_hcd and address 4
usb 1-1.3: new device found, idVendor=05ac, idProduct=0307
usb 1-1.3: new device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-1.3: Product: Apple Optical USB Mouse
usb 1-1.3: Manufacturer: Logitech
usb 1-1.3: configuration #1 chosen from 1 choice
usbcore: registered new driver hiddev
input: Alps Electric Apple USB Keyboard as /class/input/input1
input: USB HID v1.00 Keyboard [Alps Electric Apple USB Keyboard] on usb-0001:10:18.0-1.1
input: Logitech Apple Optical USB Mouse as /class/input/input2
input: USB HID v1.10 Mouse [Logitech Apple Optical USB Mouse] on usb-0001:10:18.0-1.3
usbcore: registered new driver usbhiddrivers/usb/input/hid-core.c: v2.6:USB HID core driver
mice: PS/2 mouse device common for all mice
PowerMac i2c bus pmu 2 registered
PowerMac i2c bus pmu 1 registered
PowerMac i2c bus mac-io 0 registered
PowerMac i2c bus uni-n 1 registered
PowerMac i2c bus uni-n 0 registered
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 6, 262144 bytes)
TCP bind hash table entries: 16384 (order: 6, 327680 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
TCP reno registered
TCP westwood registered
TCP htcp registered
NET: Registered protocol family 1
NET: Registered protocol family 17
Freeing unused kernel memory: 196k init
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
Adding 131064k swap on /dev/hda12. Priority:-1 extents:1 across:131064k
EXT3 FS on hda13, internal journal
Linux agpgart interface v0.101 (c) Dave Jones
agpgart: Detected Apple UniNorth 1.5 chipset
agpgart: configuring for size idx: 4
agpgart: AGP aperture is 16M @ 0x0
ide-floppy driver 0.99.newide
hdd: No disk in drive
hdd: 0kB, 0/64/32 CHS, 4096 kBps, 512 sector size, 2941 rpm
hdc: ATAPI 32X CD-ROM CD-R/RW drive, 4096kB Cache, (U)DMA
Uniform CD-ROM driver Revision: 3.20
USB Universal Host Controller Interface driver v2.3
PCI: Enabling device 0001:10:12.0 (0014 -> 0015)
PCI: Via IRQ fixup for 0001:10:12.0, from 52 to 4uhci_hcd 0001:10:12.0: UHCI Host Controlleruhci_hcd 0001:10:12.0: new USB bus registered, assigned bus number 3uhci_hcd 0001:10:12.0: irq 52, io base 0x00010000
usb usb3: new device found, idVendor=0000, idProduct=0000
usb usb3: new device strings: Mfr=3, Product=2, SerialNumber=1
usb usb3: Product: UHCI Host Controller
usb usb3: Manufacturer: Linux 2.6.16-rc3-git3-20060215_bug149895-default uhci_hcd
usb usb3: SerialNumber: 0001:10:12.0
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
PCI: Enabling device 0001:10:12.1 (0014 -> 0015)
PCI: Via IRQ fixup for 0001:10:12.1, from 52 to 4uhci_hcd 0001:10:12.1: UHCI Host Controlleruhci_hcd 0001:10:12.1: new USB bus registered, assigned bus number 4uhci_hcd 0001:10:12.1: irq 52, io base 0x00010020
usb usb4: new device found, idVendor=0000, idProduct=0000
usb usb4: new device strings: Mfr=3, Product=2, SerialNumber=1
usb usb4: Product: UHCI Host Controller
usb usb4: Manufacturer: Linux 2.6.16-rc3-git3-20060215_bug149895-default uhci_hcd
usb usb4: SerialNumber: 0001:10:12.1
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
PCI: Enabling device 0001:10:12.2 (0014 -> 0016)
PCI: Via IRQ fixup for 0001:10:12.2, from 52 to 4ehci_hcd 0001:10:12.2: EHCI Host Controllerehci_hcd 0001:10:12.2: new USB bus registered, assigned bus number 5ehci_hcd 0001:10:12.2: irq 52, io mem 0x80081000ehci_hcd 0001:10:12.2: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb5: new device found, idVendor=0000, idProduct=0000
usb usb5: new device strings: Mfr=3, Product=2, SerialNumber=1
usb usb5: Product: EHCI Host Controller
usb usb5: Manufacturer: Linux 2.6.16-rc3-git3-20060215_bug149895-default ehci_hcd
usb usb5: SerialNumber: 0001:10:12.2
usb usb5: configuration #1 chosen from 1 choice
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 4 ports detected
8139too Fast Ethernet driver 0.9.27
sungem.c:v0.98 8/24/03 David S. Miller ([email protected])
PCI: Enabling device 0001:10:14.0 (0004 -> 0007)
eth0: RealTek RTL8139 at 0xd105a000, 00:50:fc:76:65:12, IRQ 54
eth0: Identified 8139 chip type 'RTL-8100B/8139D'
PHY ID: 206053, addr: 0
eth1: Sun GEM (PCI) 10/100/1000BaseT Ethernet 00:30:65:f3:4c:ae
eth1: Found BCM5401 PHY
8139cp: 10/100 PCI Ethernet driver v1.2 (Mar 22, 2004)
ieee1394: Initialized config rom entry `ip1394'
JBD: barrier-based sync failed on hda13 - disabling barriers
PCI: Enabling device 0001:10:12.3 (0090 -> 0093)
PCI: Via IRQ fixup for 0001:10:12.3, from 52 to 4
ohci1394: fw-host0: OHCI-1394 1.0 (PCI): IRQ=[52] MMIO=[80084000-800847ff] Max Packet=[2048] IR/IT contexts=[8/8]
ohci1394: fw-host1: Unexpected PCI resource length of 1000!
ohci1394: fw-host1: OHCI-1394 1.0 (PCI): IRQ=[40] MMIO=[f5000000-f50007ff] Max Packet=[2048] IR/IT contexts=[8/8]
ieee1394: Host added: ID:BUS[0-00:1023] GUID[0011060000006685]
eth1: Link is up at 100 Mbps, full-duplex.
ieee1394: Host added: ID:BUS[1-00:1023] GUID[003065fffef34cae]
device-mapper: 4.5.0-ioctl (2005-10-04) initialised: [email protected]
dm-netlink version 0.0.2 loaded
hdd: No disk in drive
loop: loaded (max 8 devices)
kjournald starting. Commit interval 5 seconds
EXT3 FS on hda14, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
AppArmor: AppArmor (version 2.0-19.43r6152) initialized
audit(1138960018.908:2): AppArmor (version 2.0-19.43r6152) initialized
do_settimeofday(1138963619.000000000)
eth1: Link is up at 100 Mbps, full-duplex.
eth1: Pause is enabled (rxfifo: 10240 off: 7168 on: 5632)
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
IPv6 over IPv4 tunneling driver
JBD: barrier-based sync failed on hda13 - disabling barriers
JBD: barrier-based sync failed on hda13 - disabling barriers
Quoted 11 lines · Paul Mackerras
Quoted 1 line · Benjamin Herrenschmidt
Ok, does not using NTP fixes it ?
Try this patch. With this the values from
gettimeofday()or the VDSO should stay exactly in sync with xtime even if NTP is adjusting the clock.This patch still has quite a few debugging printks in it, so it's not final by any means. I'll be interested to hear how it goes, and in particular whether or not you see any "oops, time got ahead" messages.
This patch fixed the clock skew issues (warnings from 'make' while building new kernels) my G4 eMac has been having since about 2.6.15. User-space is YDL4.0 and ntpd is used to maintain a correct clock.
/Mikael
Quoted 11 lines · Paul Mackerras
Quoted 1 line · Benjamin Herrenschmidt
Ok, does not using NTP fixes it ?
Try this patch. With this the values from
gettimeofday()or the VDSO should stay exactly in sync with xtime even if NTP is adjusting the clock.This patch still has quite a few debugging printks in it, so it's not final by any means. I'll be interested to hear how it goes, and in particular whether or not you see any "oops, time got ahead" messages.
Without your patch, the clock works perfectly when NTP is not in use, but when NTP is in use I get a large amount of skew (3 min) after about half an hour.
With your patch (tested against 2.6.16-rc3), there is no skew whether NTP is running or not, and the system has been up 90 mins so far. They two times appear to be the same.
Regards,
Roger
Signature · 4 lines
Roger Leigh
Printing on GNU/Linux? http://gutenprint.sourceforge.net/
Debian GNU/Linux http://www.debian.org/
GPG Public Key: 0x25BFB848. Please sign and encrypt your mail.Quoted 4 lines · Roger Leigh
When running a 2.6.16-rc2 kernel on a powerpc system (Mac Mini;
Freescale 7447A):
Quoted 8 lines
$ date && touch f && ls -l f && rm -f f && date Sun Feb 12 12:20:14 GMT 2006 -rw-r--r-- 1 rleigh rleigh 0 2006-02-12 12:23 Sun Feb 12 12:20:14 GMT 2006Notice the timestamp is 3 minutes in the future compared with the system time. "make" is not a very happy bunny running on this kernel due to every touched file being 3 minutes in the future.
I've had several spates of time-going-nuts on ppc64. The most recent one was because someone went and fiddled with Kconfig naming and I lost the RTC driver.
What does `grep RTC .config' say?
Quoted 14 lines · Andrew Morton
Quoted 4 lines · Roger Leigh
When running a 2.6.16-rc2 kernel on a powerpc system (Mac Mini;
Freescale 7447A):Quoted 8 lines
$ date && touch f && ls -l f && rm -f f && date Sun Feb 12 12:20:14 GMT 2006 -rw-r--r-- 1 rleigh rleigh 0 2006-02-12 12:23 Sun Feb 12 12:20:14 GMT 2006Notice the timestamp is 3 minutes in the future compared with the system time. "make" is not a very happy bunny running on this kernel due to every touched file being 3 minutes in the future.
Quoted 5 lines
I've had several spates of time-going-nuts on ppc64. The most recent one was because someone went and fiddled with
Kconfignaming and I lost the RTC driver.What does `grep RTC .config' say?
CONFIG_GEN_RTC=yCONFIG_GEN_RTC_X=yCONFIG_SENSORS_RTC8564=mCONFIG_RTC_X1205_I2C=m
This is just ppc, not ppc64, BTW:
$ uname -m ppc
Regards,
Roger
Signature · 4 lines
Roger Leigh
Printing on GNU/Linux? http://gutenprint.sourceforge.net/
Debian GNU/Linux http://www.debian.org/
GPG Public Key: 0x25BFB848. Please sign and encrypt your mail.PATCH 1/1 powerpc: dont allow old RTC to be selected
In reply to Andrew MortonQuoted 4 lines
I've had several spates of time-going-nuts on ppc64. The most recent one was because someone went and fiddled with
Kconfignaming and I lost the RTC driver.
This might help a bit:
Now powerpc uses the generic RTC stuff we should not enable the old RTC. Doing so will result in hangs at boot.
---
drivers/char/Kconfig +1 -1
@@ -695,7 +695,7 @@ config NVRAM config RTC tristate "Enhanced Real Time Clock Support" - depends on !PPC32 && !PARISC && !IA64 && !M68K && (!SPARC || PCI) && !FRV + depends on !PPC && !PARISC && !IA64 && !M68K && (!SPARC || PCI) && !FRV ---help--- If you say Y here and create a character special file /dev/rtc with major number 10 and minor number 135 using mknod ("man mknod"), you