Re: [PATCH] Dynamic Tick version 050406-1

2005-04-08 Thread Tony Lindgren 
* Frank Sorenson <[EMAIL PROTECTED]> [050407 15:21]:
> Frank Sorenson wrote:
> > Tony Lindgren wrote:
> > 
> >>Thanks for trying it out. What kind of hardware do you have? Does it
> >>have HPET? It looks like no suitable timer for dyn-tick is found...
> >>Maybe the following patch helps?
> >>
> >>Tony
> > 
> > 
> > Does 'different crash' qualify as "helping"?  :)
> 
> Update:
> The patch does seem to fix the crash.  This "different crash" I
> mentioned appears to be related to the netconsole I was using (serial
> console produces stairstepping text, netconsole seems to duplicate
> lines--go figure).  Without netconsole, dynamic tick appears to be
> working, so I'm not sure whether this is a netconsole bug or a dynamic
> tick bug.

This might be because time does not run correctly, see below.

> While dynamic tick no longer panics, with dynamic tick, my system slows
> to whatever is slower than a crawl.  It now takes 6 minutes 50 seconds
> to boot all the way up, compared to 1 minute 35 seconds with my 2.6.12
> kernel without the dynamic tick patch.  I'm not sure where this slowdown
> is occurring yet.

I think I have an idea on what's going on; Your system does not wake to
APIC interrupt, and the system timer updates time only on other interrupts.
I'm experiencing the same on a loaner ThinkPad T30.

I'll try to do another patch today. Meanwhile it now should work
without lapic in cmdline.

Tony

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] Dynamic Tick version 050406-1

2005-04-08 Thread Tony Lindgren 
* Alexander Nyberg <[EMAIL PROTECTED]> [050407 02:31]:
> > > > Here's an updated dyn-tick patch. Some minor fixes:
> > > 
> > > Doesn't look so good here.  I get this with 2.6.12-rc2 (plus a few other 
> > > patches).
> > > Disabling Dynamic Tick makes everything happy again (it boots).
> > > 
> > > [4294688.655000] Unable to handle kernel NULL pointer dereference at 
> > > virtual address 
> > 
> > Thanks for trying it out. What kind of hardware do you have? Does it
> > have HPET? It looks like no suitable timer for dyn-tick is found...
> > Maybe the following patch helps?
> 
> 
> = arch/i386/kernel/Makefile 1.67 vs edited =
> --- 1.67/arch/i386/kernel/Makefile2005-01-26 06:21:13 +01:00
> +++ edited/arch/i386/kernel/Makefile  2005-04-07 11:21:19 +02:00
> @@ -32,6 +32,7 @@ obj-$(CONFIG_ACPI_SRAT) += srat.o
>  obj-$(CONFIG_HPET_TIMER) += time_hpet.o
>  obj-$(CONFIG_EFI)+= efi.o efi_stub.o
>  obj-$(CONFIG_EARLY_PRINTK)   += early_printk.o
> +obj-$(CONFIG_NO_IDLE_HZ) += dyn-tick.o
>  
>  EXTRA_AFLAGS   := -traditional

Ah, that explains :) Thanks!

Tony
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] Dynamic Tick version 050406-1

2005-04-08 Thread Tony Lindgren 
* Alexander Nyberg [EMAIL PROTECTED] [050407 02:31]:
Here's an updated dyn-tick patch. Some minor fixes:
   
   Doesn't look so good here.  I get this with 2.6.12-rc2 (plus a few other 
   patches).
   Disabling Dynamic Tick makes everything happy again (it boots).
   
   [4294688.655000] Unable to handle kernel NULL pointer dereference at 
   virtual address 
  
  Thanks for trying it out. What kind of hardware do you have? Does it
  have HPET? It looks like no suitable timer for dyn-tick is found...
  Maybe the following patch helps?
 
 
 = arch/i386/kernel/Makefile 1.67 vs edited =
 --- 1.67/arch/i386/kernel/Makefile2005-01-26 06:21:13 +01:00
 +++ edited/arch/i386/kernel/Makefile  2005-04-07 11:21:19 +02:00
 @@ -32,6 +32,7 @@ obj-$(CONFIG_ACPI_SRAT) += srat.o
  obj-$(CONFIG_HPET_TIMER) += time_hpet.o
  obj-$(CONFIG_EFI)+= efi.o efi_stub.o
  obj-$(CONFIG_EARLY_PRINTK)   += early_printk.o
 +obj-$(CONFIG_NO_IDLE_HZ) += dyn-tick.o
  
  EXTRA_AFLAGS   := -traditional

Ah, that explains :) Thanks!

Tony
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] Dynamic Tick version 050406-1

2005-04-08 Thread Tony Lindgren 
* Frank Sorenson [EMAIL PROTECTED] [050407 15:21]:
 Frank Sorenson wrote:
  Tony Lindgren wrote:
  
 Thanks for trying it out. What kind of hardware do you have? Does it
 have HPET? It looks like no suitable timer for dyn-tick is found...
 Maybe the following patch helps?
 
 Tony
  
  
  Does 'different crash' qualify as helping?  :)
 
 Update:
 The patch does seem to fix the crash.  This different crash I
 mentioned appears to be related to the netconsole I was using (serial
 console produces stairstepping text, netconsole seems to duplicate
 lines--go figure).  Without netconsole, dynamic tick appears to be
 working, so I'm not sure whether this is a netconsole bug or a dynamic
 tick bug.

This might be because time does not run correctly, see below.

 While dynamic tick no longer panics, with dynamic tick, my system slows
 to whatever is slower than a crawl.  It now takes 6 minutes 50 seconds
 to boot all the way up, compared to 1 minute 35 seconds with my 2.6.12
 kernel without the dynamic tick patch.  I'm not sure where this slowdown
 is occurring yet.

I think I have an idea on what's going on; Your system does not wake to
APIC interrupt, and the system timer updates time only on other interrupts.
I'm experiencing the same on a loaner ThinkPad T30.

I'll try to do another patch today. Meanwhile it now should work
without lapic in cmdline.

Tony

-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] Dynamic Tick version 050406-1

2005-04-07 Thread Frank Sorenson 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Frank Sorenson wrote:
> Tony Lindgren wrote:
> 
>>Thanks for trying it out. What kind of hardware do you have? Does it
>>have HPET? It looks like no suitable timer for dyn-tick is found...
>>Maybe the following patch helps?
>>
>>Tony
> 
> 
> Does 'different crash' qualify as "helping"?  :)

Update:
The patch does seem to fix the crash.  This "different crash" I
mentioned appears to be related to the netconsole I was using (serial
console produces stairstepping text, netconsole seems to duplicate
lines--go figure).  Without netconsole, dynamic tick appears to be
working, so I'm not sure whether this is a netconsole bug or a dynamic
tick bug.

While dynamic tick no longer panics, with dynamic tick, my system slows
to whatever is slower than a crawl.  It now takes 6 minutes 50 seconds
to boot all the way up, compared to 1 minute 35 seconds with my 2.6.12
kernel without the dynamic tick patch.  I'm not sure where this slowdown
is occurring yet.

Frank
- --
Frank Sorenson - KD7TZK
Systems Manager, Computer Science Department
Brigham Young University
[EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCVbJHaI0dwg4A47wRAmijAKCRgg9MTxrrNWKanMmmSS010BTWdgCeNMnJ
4YJWhHAcizMgZNH/+643Hvk=
=w9Ii
-END PGP SIGNATURE-
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] Dynamic Tick version 050406-1

2005-04-07 Thread Frank Sorenson 
Tony Lindgren wrote:
> Thanks for trying it out. What kind of hardware do you have? Does it
> have HPET? It looks like no suitable timer for dyn-tick is found...
> Maybe the following patch helps?
> 
> Tony

Does 'different crash' qualify as "helping"?  :)

With this additional patch, I get this line followed by a system hang:
[4294688.246000] dyn-tick: Maximum ticks to skip limited to 2693

With "nmi_watchdog=1", the "dyn-tick: Maximum..." line is followed by
(my serial console stops logging):
<4>[4294688.741000] NMI Watchdog detected LOCKUP on CPU0, eip c011a2ab,
registers:
Modules linked in:
CPU: 0
EIP: 0060:[] Not tainted VLI
EFLAGS: 0046  (2.6.12-rc2-dyntick)
EIP is at smp_apic_timer_interrupt
... etc ...

This is on my Dell Inspiron 9200:
/proc/cpuinfo:
processor   : 0
vendor_id   : GenuineIntel
cpu family  : 6
model   : 13
model name  : Intel(R) Pentium(R) M processor 2.00GHz
stepping: 6
cpu MHz : 598.130
cache size  : 2048 KB
fdiv_bug: no
hlt_bug : no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception   : yes
cpuid level : 2
wp  : yes
flags   : fpu vme de pse tsc msr mce cx8 apic sep mtrr pge mca
cmov pat clflush dts acpi mmx fxsr sse sse2 ss tm pbe est tm2
bogomips: 1183.74

Attached are the serial log and the .config.  HPET is enabled, and
appears to be detected.

Let me know if you need any additional info or need me to try anything
else out.

Frank
-- 
Frank Sorenson - KD7TZK
Systems Manager, Computer Science Department
Brigham Young University
[EMAIL PROTECTED]
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.12-rc2
# Thu Apr  7 13:09:54 2005
#
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=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="-dyntick"
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_POSIX_MQUEUE=y
CONFIG_BSD_PROCESS_ACCT=y
# CONFIG_BSD_PROCESS_ACCT_V3 is not set
CONFIG_SYSCTL=y
CONFIG_AUDIT=y
CONFIG_AUDITSYSCALL=y
CONFIG_HOTPLUG=y
CONFIG_KOBJECT_UEVENT=y
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
# CONFIG_EMBEDDED is not set
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_ALL is not set
CONFIG_KALLSYMS_EXTRA_PASS=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=y
# 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_MGEODE is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
CONFIG_X86_GENERIC=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=7
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
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_NO_IDLE_HZ=y
# CONFIG_SMP is not set
CONFIG_PREEMPT=y
CONFIG_PREEMPT_BKL=y
CONFIG_X86_UP_APIC=y
CONFIG_X86_UP_IOAPIC=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_TSC=y
CONFIG_X86_MCE=y
# CONFIG_X86_MCE_NONFATAL is not set
# CONFIG_X86_MCE_P4THERMAL is not set
# CONFIG_TOSHIBA is not set
CONFIG_I8K=m
CONFIG_MICROCODE=m
CONFIG_X86_MSR=m
CONFIG_X86_CPUID=m

#
# Firmware Drivers
#
CONFIG_EDD=m
# CONFIG_NOHIGHMEM is not set
CONFIG_HIGHMEM4G=y
# CONFIG_HIGHMEM64G is not set
CONFIG_HIGHMEM=y
CONFIG_HIGHPTE=y
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
# CONFIG_EFI is not set
CONFIG_HAVE_DEC_LOCK=y
CONFIG_REGPARM=y
CONFIG_SECCOMP=y

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

#
# ACPI (Advanced Configuration and Power Interface) Support
#
CONFIG_ACPI=y
CONFIG_ACPI_BOOT=y
CONFIG_ACPI_INTERPRETER=y
CONFIG_ACPI_SLEEP=y

Re: [PATCH] Dynamic Tick version 050406-1

2005-04-07 Thread Alexander Nyberg 
> > > Here's an updated dyn-tick patch. Some minor fixes:
> > 
> > Doesn't look so good here.  I get this with 2.6.12-rc2 (plus a few other 
> > patches).
> > Disabling Dynamic Tick makes everything happy again (it boots).
> > 
> > [4294688.655000] Unable to handle kernel NULL pointer dereference at 
> > virtual address 
> 
> Thanks for trying it out. What kind of hardware do you have? Does it
> have HPET? It looks like no suitable timer for dyn-tick is found...
> Maybe the following patch helps?


= arch/i386/kernel/Makefile 1.67 vs edited =
--- 1.67/arch/i386/kernel/Makefile  2005-01-26 06:21:13 +01:00
+++ edited/arch/i386/kernel/Makefile2005-04-07 11:21:19 +02:00
@@ -32,6 +32,7 @@ obj-$(CONFIG_ACPI_SRAT)   += srat.o
 obj-$(CONFIG_HPET_TIMER)   += time_hpet.o
 obj-$(CONFIG_EFI)  += efi.o efi_stub.o
 obj-$(CONFIG_EARLY_PRINTK) += early_printk.o
+obj-$(CONFIG_NO_IDLE_HZ)   += dyn-tick.o
 
 EXTRA_AFLAGS   := -traditional
 


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] Dynamic Tick version 050406-1

2005-04-07 Thread Tony Lindgren 
* Frank Sorenson <[EMAIL PROTECTED]> [050406 14:16]:
> Tony Lindgren wrote:
> > Hi all,
> > 
> > Here's an updated dyn-tick patch. Some minor fixes:
> 
> Doesn't look so good here.  I get this with 2.6.12-rc2 (plus a few other 
> patches).
> Disabling Dynamic Tick makes everything happy again (it boots).
> 
> [4294688.655000] Unable to handle kernel NULL pointer dereference at virtual 
> address 

Thanks for trying it out. What kind of hardware do you have? Does it
have HPET? It looks like no suitable timer for dyn-tick is found...
Maybe the following patch helps?

Tony
--- a/kernel/dyn-tick-timer.c   2005-03-01 16:41:05 -08:00
+++ b/kernel/dyn-tick-timer.c   2005-04-07 00:57:30 -07:00
@@ -232,10 +232,6 @@
 {
int ret = 0;
 
-   ret = sysdev_create_file(_timer, _dyn_tick_state);
-   ret = sysdev_create_file(_timer, _dyn_tick_int);
-   ret = sysdev_create_file(_timer, _dyn_tick_dbg);
-
if (dyn_tick_cfg->arch_init == NULL ||
!(dyn_tick->state & DYN_TICK_SUITABLE))
return -ENODEV;
@@ -245,6 +241,10 @@
printk(KERN_WARNING "dyn-tick: Init failed\n");
return -ENODEV;
}
+
+   ret = sysdev_create_file(_timer, _dyn_tick_state);
+   ret = sysdev_create_file(_timer, _dyn_tick_int);
+   ret = sysdev_create_file(_timer, _dyn_tick_dbg);
 
printk(KERN_INFO "dyn-tick: Timer using dynamic tick\n");

Re: [PATCH] Dynamic Tick version 050406-1

2005-04-07 Thread Tony Lindgren 
* Frank Sorenson [EMAIL PROTECTED] [050406 14:16]:
 Tony Lindgren wrote:
  Hi all,
  
  Here's an updated dyn-tick patch. Some minor fixes:
 
 Doesn't look so good here.  I get this with 2.6.12-rc2 (plus a few other 
 patches).
 Disabling Dynamic Tick makes everything happy again (it boots).
 
 [4294688.655000] Unable to handle kernel NULL pointer dereference at virtual 
 address 

Thanks for trying it out. What kind of hardware do you have? Does it
have HPET? It looks like no suitable timer for dyn-tick is found...
Maybe the following patch helps?

Tony
--- a/kernel/dyn-tick-timer.c   2005-03-01 16:41:05 -08:00
+++ b/kernel/dyn-tick-timer.c   2005-04-07 00:57:30 -07:00
@@ -232,10 +232,6 @@
 {
int ret = 0;
 
-   ret = sysdev_create_file(device_timer, attr_dyn_tick_state);
-   ret = sysdev_create_file(device_timer, attr_dyn_tick_int);
-   ret = sysdev_create_file(device_timer, attr_dyn_tick_dbg);
-
if (dyn_tick_cfg-arch_init == NULL ||
!(dyn_tick-state  DYN_TICK_SUITABLE))
return -ENODEV;
@@ -245,6 +241,10 @@
printk(KERN_WARNING dyn-tick: Init failed\n);
return -ENODEV;
}
+
+   ret = sysdev_create_file(device_timer, attr_dyn_tick_state);
+   ret = sysdev_create_file(device_timer, attr_dyn_tick_int);
+   ret = sysdev_create_file(device_timer, attr_dyn_tick_dbg);
 
printk(KERN_INFO dyn-tick: Timer using dynamic tick\n);

Re: [PATCH] Dynamic Tick version 050406-1

2005-04-07 Thread Alexander Nyberg 
   Here's an updated dyn-tick patch. Some minor fixes:
  
  Doesn't look so good here.  I get this with 2.6.12-rc2 (plus a few other 
  patches).
  Disabling Dynamic Tick makes everything happy again (it boots).
  
  [4294688.655000] Unable to handle kernel NULL pointer dereference at 
  virtual address 
 
 Thanks for trying it out. What kind of hardware do you have? Does it
 have HPET? It looks like no suitable timer for dyn-tick is found...
 Maybe the following patch helps?


= arch/i386/kernel/Makefile 1.67 vs edited =
--- 1.67/arch/i386/kernel/Makefile  2005-01-26 06:21:13 +01:00
+++ edited/arch/i386/kernel/Makefile2005-04-07 11:21:19 +02:00
@@ -32,6 +32,7 @@ obj-$(CONFIG_ACPI_SRAT)   += srat.o
 obj-$(CONFIG_HPET_TIMER)   += time_hpet.o
 obj-$(CONFIG_EFI)  += efi.o efi_stub.o
 obj-$(CONFIG_EARLY_PRINTK) += early_printk.o
+obj-$(CONFIG_NO_IDLE_HZ)   += dyn-tick.o
 
 EXTRA_AFLAGS   := -traditional
 


-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] Dynamic Tick version 050406-1

2005-04-07 Thread Frank Sorenson 
Tony Lindgren wrote:
 Thanks for trying it out. What kind of hardware do you have? Does it
 have HPET? It looks like no suitable timer for dyn-tick is found...
 Maybe the following patch helps?
 
 Tony

Does 'different crash' qualify as helping?  :)

With this additional patch, I get this line followed by a system hang:
[4294688.246000] dyn-tick: Maximum ticks to skip limited to 2693

With nmi_watchdog=1, the dyn-tick: Maximum... line is followed by
(my serial console stops logging):
4[4294688.741000] NMI Watchdog detected LOCKUP on CPU0, eip c011a2ab,
registers:
Modules linked in:
CPU: 0
EIP: 0060:[c011a2ab] Not tainted VLI
EFLAGS: 0046  (2.6.12-rc2-dyntick)
EIP is at smp_apic_timer_interrupt
... etc ...

This is on my Dell Inspiron 9200:
/proc/cpuinfo:
processor   : 0
vendor_id   : GenuineIntel
cpu family  : 6
model   : 13
model name  : Intel(R) Pentium(R) M processor 2.00GHz
stepping: 6
cpu MHz : 598.130
cache size  : 2048 KB
fdiv_bug: no
hlt_bug : no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception   : yes
cpuid level : 2
wp  : yes
flags   : fpu vme de pse tsc msr mce cx8 apic sep mtrr pge mca
cmov pat clflush dts acpi mmx fxsr sse sse2 ss tm pbe est tm2
bogomips: 1183.74

Attached are the serial log and the .config.  HPET is enabled, and
appears to be detected.

Let me know if you need any additional info or need me to try anything
else out.

Frank
-- 
Frank Sorenson - KD7TZK
Systems Manager, Computer Science Department
Brigham Young University
[EMAIL PROTECTED]
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.12-rc2
# Thu Apr  7 13:09:54 2005
#
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=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=-dyntick
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_POSIX_MQUEUE=y
CONFIG_BSD_PROCESS_ACCT=y
# CONFIG_BSD_PROCESS_ACCT_V3 is not set
CONFIG_SYSCTL=y
CONFIG_AUDIT=y
CONFIG_AUDITSYSCALL=y
CONFIG_HOTPLUG=y
CONFIG_KOBJECT_UEVENT=y
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
# CONFIG_EMBEDDED is not set
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_ALL is not set
CONFIG_KALLSYMS_EXTRA_PASS=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=y
# 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_MGEODE is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
CONFIG_X86_GENERIC=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=7
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
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_NO_IDLE_HZ=y
# CONFIG_SMP is not set
CONFIG_PREEMPT=y
CONFIG_PREEMPT_BKL=y
CONFIG_X86_UP_APIC=y
CONFIG_X86_UP_IOAPIC=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_TSC=y
CONFIG_X86_MCE=y
# CONFIG_X86_MCE_NONFATAL is not set
# CONFIG_X86_MCE_P4THERMAL is not set
# CONFIG_TOSHIBA is not set
CONFIG_I8K=m
CONFIG_MICROCODE=m
CONFIG_X86_MSR=m
CONFIG_X86_CPUID=m

#
# Firmware Drivers
#
CONFIG_EDD=m
# CONFIG_NOHIGHMEM is not set
CONFIG_HIGHMEM4G=y
# CONFIG_HIGHMEM64G is not set
CONFIG_HIGHMEM=y
CONFIG_HIGHPTE=y
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
# CONFIG_EFI is not set
CONFIG_HAVE_DEC_LOCK=y
CONFIG_REGPARM=y
CONFIG_SECCOMP=y

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

#
# ACPI (Advanced Configuration and Power Interface) Support
#
CONFIG_ACPI=y
CONFIG_ACPI_BOOT=y
CONFIG_ACPI_INTERPRETER=y
CONFIG_ACPI_SLEEP=y

Re: [PATCH] Dynamic Tick version 050406-1

2005-04-07 Thread Frank Sorenson 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Frank Sorenson wrote:
 Tony Lindgren wrote:
 
Thanks for trying it out. What kind of hardware do you have? Does it
have HPET? It looks like no suitable timer for dyn-tick is found...
Maybe the following patch helps?

Tony
 
 
 Does 'different crash' qualify as helping?  :)

Update:
The patch does seem to fix the crash.  This different crash I
mentioned appears to be related to the netconsole I was using (serial
console produces stairstepping text, netconsole seems to duplicate
lines--go figure).  Without netconsole, dynamic tick appears to be
working, so I'm not sure whether this is a netconsole bug or a dynamic
tick bug.

While dynamic tick no longer panics, with dynamic tick, my system slows
to whatever is slower than a crawl.  It now takes 6 minutes 50 seconds
to boot all the way up, compared to 1 minute 35 seconds with my 2.6.12
kernel without the dynamic tick patch.  I'm not sure where this slowdown
is occurring yet.

Frank
- --
Frank Sorenson - KD7TZK
Systems Manager, Computer Science Department
Brigham Young University
[EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCVbJHaI0dwg4A47wRAmijAKCRgg9MTxrrNWKanMmmSS010BTWdgCeNMnJ
4YJWhHAcizMgZNH/+643Hvk=
=w9Ii
-END PGP SIGNATURE-
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] Dynamic Tick version 050406-1

2005-04-06 Thread Frank Sorenson 
Tony Lindgren wrote:
> Hi all,
> 
> Here's an updated dyn-tick patch. Some minor fixes:

Doesn't look so good here.  I get this with 2.6.12-rc2 (plus a few other 
patches).
Disabling Dynamic Tick makes everything happy again (it boots).

[4294688.655000] Unable to handle kernel NULL pointer dereference at virtual 
address 
[4294688.656000]  printing eip:
[4294688.657000] c077f818
[4294688.659000] *pde = 
[4294688.66] Oops:  [#1]
[4294688.661000] PREEMPT 
[4294688.662000] Modules linked in:
[4294688.663000] CPU:0
[4294688.663000] EIP:0060:[]Not tainted VLI
[4294688.663000] EFLAGS: 00010202   (2.6.12-rc2-fs3) 
[4294688.666000] EIP is at dyn_tick_late_init+0x38/0x80
[4294688.667000] eax:    ebx: c079f0c0   ecx:    edx: f7c15d4c
[4294688.668000] esi: f7f02000   edi:    ebp: f7f03fb8   esp: f7f03fb4
[4294688.669000] ds: 007b   es: 007b   ss: 0068
[4294688.67] Process swapper (pid: 1, threadinfo=f7f02000 task=f7f01830)
[4294688.67] Stack: c077a0e2 f7f03fd8 c076a956 c019bde8 c01002a0  
c01002a0 000 
[4294688.671000] f7f03fec c01002d5 007b 007b  
 c0101365 
[4294688.672000]   
[4294688.673000] Call Trace:
[4294688.675000]  [] show_stack+0x7a/0x90
[4294688.676000]  [] show_registers+0x149/0x1c0
[4294688.677000]  [] die+0x14a/0x2d0
[4294688.678000]  [] do_page_fault+0x44e/0x633
[4294688.679000]  [] error_code+0x4f/0x54
[4294688.68]  [] do_initcalls+0x56/0xc0
[4294688.681000]  [] init+0x35/0x110
[4294688.682000]  [] kernel_thread_helper+0x5/0x10
[4294688.683000] Code: 83 ec 04 e8 3b 6b c0 ff ba 14 b7<7>eth0: no IPv6 routers 
present

Frank
-- 
Frank Sorenson - KD7TZK
Systems Manager, Computer Science Department
Brigham Young University
[EMAIL PROTECTED]
[4294667.296000] Linux version 2.6.12-rc2-fs3 ([EMAIL PROTECTED]) (gcc version 
3.4.2 20041017 (Red Hat 3.4.2-6.fc3)) #3 Wed Apr 6 13:14:48 MDT 2005
[4294667.296000] BIOS-provided physical RAM map:
[4294667.296000]  BIOS-e820:  - 0009f000 (usable)
[4294667.296000]  BIOS-e820: 0009f000 - 000a (reserved)
[4294667.296000]  BIOS-e820: 0010 - 5ffae000 (usable)
[4294667.296000]  BIOS-e820: 5ffae000 - 6000 (reserved)
[4294667.296000]  BIOS-e820: feda - fee0 (reserved)
[4294667.296000]  BIOS-e820: ffb0 - 0001 (reserved)
[4294667.296000] 639MB HIGHMEM available.
[4294667.296000] 896MB LOWMEM available.
[4294667.296000] DMI 2.3 present.
[4294667.296000] ACPI: PM-Timer IO Port: 0x808
[4294667.296000] Allocating PCI resources starting at 6000 (gap: 
6000:9eda)
[4294667.296000] Built 1 zonelists
[4294667.296000] Kernel command line: ro root=LABEL=/1 vga=794 nmi_watchdog=1 
lapic console=tty0 console=ttyUSB0,9600 psmouse.proto=exps 
i8k.ignore_dmi:bool=true [EMAIL PROTECTED]/eth0,[EMAIL PROTECTED]/ single
[4294667.296000] Unknown boot option `i8k.ignore_dmi:bool=true': ignoring
[4294667.296000] netconsole: local port 6665
[4294667.296000] netconsole: local IP 128.187.171.101
[4294667.296000] netconsole: interface eth0
[4294667.296000] netconsole: remote port 5515[4294667.296000] netconsole: 
remote IP 128.187.171.102
[4294667.[4294667.296000] Console: colour dummy device 80x25
[4294667.298[4294667.472000] Capability LSM initialized as secondary
[429466[4294667.472000] Checking 'hlt' instruction... OK.
[4294667.4830[4294667.616000] checking if image is initramfs... it is
[429466[4294667.75] Completing Region/Field/Buffer/Package 
initiali[4294667.881000] PCI: Transparent bridge - :00:1e.0
[4294667[4294668.309000] pnp: PnP ACPI: found 10 devices
[4294668.31[4294668.534000] pnp: 00:01: ioport range 0x808-0x80f could not 
[4294668.607000] audit(1112798526.606:0): initialized
[4294668.6[4294668.625000] ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 
[4294668.947000]   * connector 1 of type 2 (CRT) : 2320
[4294668[4294671.384000] radeonfb: Monitor 1 type LCD found
[4294671.384[4294671.384000]  320 x 400
[4294671.384000]  320 x 400
[4294671[4294671.384000]  1024 x 768
[4294671.384000]  1280 x 1024
[4294[4294671.384000] Setting up default mode based on panel info
[42[4294671.492000] fb1: VESA VGA frame buffer device
[4294671.4980[4294673.099000] agpgart: AGP aperture is 128M @ 0xe800
[429[4294673.156000] ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 
[4294673.205000] PPP generic driver version 2.4.2
[4294673.20800[4294676.218000] b44: eth0: Link is up at 100 Mbps, full 
duplex.[4294677.477000] ICH4: not 100% native mode: will probe irqs 
lat[4294682.079000] hda: cache flushes supported
[4294682.081000]  [4294682.253000] PCI: Enabling device :02:01.0 ( -> 
0002[4294682.646000] Badness in device_release at 
drivers/base/core.[4294682.657000] Databook TCIC-2 PCMCIA probe: not found.
[42946[4294682.683000] hub 1-0:1.0: 6 ports detected
[4294682.705000] [4294682.781000]

Re: [PATCH] Dynamic Tick version 050406-1

2005-04-06 Thread Frank Sorenson 
Tony Lindgren wrote:
 Hi all,
 
 Here's an updated dyn-tick patch. Some minor fixes:

Doesn't look so good here.  I get this with 2.6.12-rc2 (plus a few other 
patches).
Disabling Dynamic Tick makes everything happy again (it boots).

[4294688.655000] Unable to handle kernel NULL pointer dereference at virtual 
address 
[4294688.656000]  printing eip:
[4294688.657000] c077f818
[4294688.659000] *pde = 
[4294688.66] Oops:  [#1]
[4294688.661000] PREEMPT 
[4294688.662000] Modules linked in:
[4294688.663000] CPU:0
[4294688.663000] EIP:0060:[c077f818]Not tainted VLI
[4294688.663000] EFLAGS: 00010202   (2.6.12-rc2-fs3) 
[4294688.666000] EIP is at dyn_tick_late_init+0x38/0x80
[4294688.667000] eax:    ebx: c079f0c0   ecx:    edx: f7c15d4c
[4294688.668000] esi: f7f02000   edi:    ebp: f7f03fb8   esp: f7f03fb4
[4294688.669000] ds: 007b   es: 007b   ss: 0068
[4294688.67] Process swapper (pid: 1, threadinfo=f7f02000 task=f7f01830)
[4294688.67] Stack: c077a0e2 f7f03fd8 c076a956 c019bde8 c01002a0  
c01002a0 000 
[4294688.671000] f7f03fec c01002d5 007b 007b  
 c0101365 
[4294688.672000]   
[4294688.673000] Call Trace:
[4294688.675000]  [c0104bfa] show_stack+0x7a/0x90
[4294688.676000]  [c0104d79] show_registers+0x149/0x1c0
[4294688.677000]  [c0104fea] die+0x14a/0x2d0
[4294688.678000]  [c011e3ee] do_page_fault+0x44e/0x633
[4294688.679000]  [c01046e3] error_code+0x4f/0x54
[4294688.68]  [c076a956] do_initcalls+0x56/0xc0
[4294688.681000]  [c01002d5] init+0x35/0x110
[4294688.682000]  [c0101365] kernel_thread_helper+0x5/0x10
[4294688.683000] Code: 83 ec 04 e8 3b 6b c0 ff ba 14 b77eth0: no IPv6 routers 
present

Frank
-- 
Frank Sorenson - KD7TZK
Systems Manager, Computer Science Department
Brigham Young University
[EMAIL PROTECTED]
[4294667.296000] Linux version 2.6.12-rc2-fs3 ([EMAIL PROTECTED]) (gcc version 
3.4.2 20041017 (Red Hat 3.4.2-6.fc3)) #3 Wed Apr 6 13:14:48 MDT 2005
[4294667.296000] BIOS-provided physical RAM map:
[4294667.296000]  BIOS-e820:  - 0009f000 (usable)
[4294667.296000]  BIOS-e820: 0009f000 - 000a (reserved)
[4294667.296000]  BIOS-e820: 0010 - 5ffae000 (usable)
[4294667.296000]  BIOS-e820: 5ffae000 - 6000 (reserved)
[4294667.296000]  BIOS-e820: feda - fee0 (reserved)
[4294667.296000]  BIOS-e820: ffb0 - 0001 (reserved)
[4294667.296000] 639MB HIGHMEM available.
[4294667.296000] 896MB LOWMEM available.
[4294667.296000] DMI 2.3 present.
[4294667.296000] ACPI: PM-Timer IO Port: 0x808
[4294667.296000] Allocating PCI resources starting at 6000 (gap: 
6000:9eda)
[4294667.296000] Built 1 zonelists
[4294667.296000] Kernel command line: ro root=LABEL=/1 vga=794 nmi_watchdog=1 
lapic console=tty0 console=ttyUSB0,9600 psmouse.proto=exps 
i8k.ignore_dmi:bool=true [EMAIL PROTECTED]/eth0,[EMAIL PROTECTED]/ single
[4294667.296000] Unknown boot option `i8k.ignore_dmi:bool=true': ignoring
[4294667.296000] netconsole: local port 6665
[4294667.296000] netconsole: local IP 128.187.171.101
[4294667.296000] netconsole: interface eth0
[4294667.296000] netconsole: remote port 5515[4294667.296000] netconsole: 
remote IP 128.187.171.102
[4294667.[4294667.296000] Console: colour dummy device 80x25
[4294667.298[4294667.472000] Capability LSM initialized as secondary
[429466[4294667.472000] Checking 'hlt' instruction... OK.
[4294667.4830[4294667.616000] checking if image is initramfs... it is
[429466[4294667.75] Completing Region/Field/Buffer/Package 
initiali[4294667.881000] PCI: Transparent bridge - :00:1e.0
[4294667[4294668.309000] pnp: PnP ACPI: found 10 devices
[4294668.31[4294668.534000] pnp: 00:01: ioport range 0x808-0x80f could not 
[4294668.607000] audit(1112798526.606:0): initialized
[4294668.6[4294668.625000] ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 
[4294668.947000]   * connector 1 of type 2 (CRT) : 2320
[4294668[4294671.384000] radeonfb: Monitor 1 type LCD found
[4294671.384[4294671.384000]  320 x 400
[4294671.384000]  320 x 400
[4294671[4294671.384000]  1024 x 768
[4294671.384000]  1280 x 1024
[4294[4294671.384000] Setting up default mode based on panel info
[42[4294671.492000] fb1: VESA VGA frame buffer device
[4294671.4980[4294673.099000] agpgart: AGP aperture is 128M @ 0xe800
[429[4294673.156000] ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 
[4294673.205000] PPP generic driver version 2.4.2
[4294673.20800[4294676.218000] b44: eth0: Link is up at 100 Mbps, full 
duplex.[4294677.477000] ICH4: not 100% native mode: will probe irqs 
lat[4294682.079000] hda: cache flushes supported
[4294682.081000]  [4294682.253000] PCI: Enabling device :02:01.0 ( - 
0002[4294682.646000] Badness in device_release at 
drivers/base/core.[4294682.657000] Databook TCIC-2 PCMCIA probe: not found.
[42946[4294682.683000]