Re: Regression: 2.6.23-rc9 okay, 2.6.23.1 resume problems
On Tue, 23 Oct 2007, Rafael J. Wysocki wrote: > On Monday, 22 October 2007 16:11, Mark Lord wrote: > > Rafael, > > > > What happens to the jiffies variable on resume from RAM, and from DISK? > > Do we restore it to the value it had at suspend, > > or just leave it be with whatever? > > > > The answer has to be "restore the value it had at suspend time", > > but I figured I'd check here anyway. > > > > ?? > > Well, frankly, I've lost track of that recently, but it seems that we just use > the pre-suspend jiffies (at least in the current -git). > > Thomas knows better, I guess. :-) We use the pre-suspend value if nothing else fiddled in the variable. tglx - 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: Regression: 2.6.23-rc9 okay, 2.6.23.1 resume problems
On Tue, 23 Oct 2007, Rafael J. Wysocki wrote: On Monday, 22 October 2007 16:11, Mark Lord wrote: Rafael, What happens to the jiffies variable on resume from RAM, and from DISK? Do we restore it to the value it had at suspend, or just leave it be with whatever? The answer has to be restore the value it had at suspend time, but I figured I'd check here anyway. ?? Well, frankly, I've lost track of that recently, but it seems that we just use the pre-suspend jiffies (at least in the current -git). Thomas knows better, I guess. :-) We use the pre-suspend value if nothing else fiddled in the variable. tglx - 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: Regression: 2.6.23-rc9 okay, 2.6.23.1 resume problems
On Monday, 22 October 2007 16:11, Mark Lord wrote: > Rafael, > > What happens to the jiffies variable on resume from RAM, and from DISK? > Do we restore it to the value it had at suspend, > or just leave it be with whatever? > > The answer has to be "restore the value it had at suspend time", > but I figured I'd check here anyway. > > ?? Well, frankly, I've lost track of that recently, but it seems that we just use the pre-suspend jiffies (at least in the current -git). Thomas knows better, I guess. :-) Greetings, Rafael - 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: Regression: 2.6.23-rc9 okay, 2.6.23.1 resume problems
Rafael, What happens to the jiffies variable on resume from RAM, and from DISK? Do we restore it to the value it had at suspend, or just leave it be with whatever? The answer has to be "restore the value it had at suspend time", but I figured I'd check here anyway. ?? - 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: Regression: 2.6.23-rc9 okay, 2.6.23.1 resume problems
Rafael, What happens to the jiffies variable on resume from RAM, and from DISK? Do we restore it to the value it had at suspend, or just leave it be with whatever? The answer has to be restore the value it had at suspend time, but I figured I'd check here anyway. ?? - 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: Regression: 2.6.23-rc9 okay, 2.6.23.1 resume problems
On Monday, 22 October 2007 16:11, Mark Lord wrote: Rafael, What happens to the jiffies variable on resume from RAM, and from DISK? Do we restore it to the value it had at suspend, or just leave it be with whatever? The answer has to be restore the value it had at suspend time, but I figured I'd check here anyway. ?? Well, frankly, I've lost track of that recently, but it seems that we just use the pre-suspend jiffies (at least in the current -git). Thomas knows better, I guess. :-) Greetings, Rafael - 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: Regression: 2.6.23-rc9 okay, 2.6.23.1 resume problems
Pavel Machek wrote: Hi! Since upgrading to 2.6.23.1 from 2.6.23-rc9, resume-from-RAM has been misbehaving here. It takes much (+5-7 seconds) longer to resume *sometimes*, but not all/most of the time. I suspend those long delays may have something to do with USB, as it takes longer for my hub + mouse to come back to life during the sequence. But I have since then re-applied the powertop patches, and the long delays vanished. Back with -rc9 I normally also had those powertop fixes, and so this problem could be much older and was never noticed until I ran without them. I'm no longer actively investigating, as the delays are gone (powertop patches), and the crashes are much less frequent since patching. Cheers - 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: Regression: 2.6.23-rc9 okay, 2.6.23.1 resume problems
Hi! > Since upgrading to 2.6.23.1 from 2.6.23-rc9, > resume-from-RAM has been misbehaving here. > > It takes much (+5-7 seconds) longer to resume > *sometimes*, but not all/most of the time. > And sometimes I get get flashing keyboard LEDs and have > to hold the power button > in for a full hard reset. > > With 2.6.23-rc8/rc9, no such troubles. > > Difficult to reproduce, other than perhaps once a day. > Anybody want to fess up with a likely candidate? Are there any .config differences between rc8 and .1? Can you try disabling nohz? -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html - 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: Regression: 2.6.23-rc9 okay, 2.6.23.1 resume problems
Hi! Since upgrading to 2.6.23.1 from 2.6.23-rc9, resume-from-RAM has been misbehaving here. It takes much (+5-7 seconds) longer to resume *sometimes*, but not all/most of the time. And sometimes I get get flashing keyboard LEDs and have to hold the power button in for a full hard reset. With 2.6.23-rc8/rc9, no such troubles. Difficult to reproduce, other than perhaps once a day. Anybody want to fess up with a likely candidate? Are there any .config differences between rc8 and .1? Can you try disabling nohz? -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html - 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: Regression: 2.6.23-rc9 okay, 2.6.23.1 resume problems
Pavel Machek wrote: Hi! Since upgrading to 2.6.23.1 from 2.6.23-rc9, resume-from-RAM has been misbehaving here. It takes much (+5-7 seconds) longer to resume *sometimes*, but not all/most of the time. I suspend those long delays may have something to do with USB, as it takes longer for my hub + mouse to come back to life during the sequence. But I have since then re-applied the powertop patches, and the long delays vanished. Back with -rc9 I normally also had those powertop fixes, and so this problem could be much older and was never noticed until I ran without them. I'm no longer actively investigating, as the delays are gone (powertop patches), and the crashes are much less frequent since patching. Cheers - 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: Regression: 2.6.23-rc9 okay, 2.6.23.1 resume problems
On Wednesday, 17 October 2007 00:10, Mark Lord wrote: > Mark Lord wrote: > > Rafael J. Wysocki wrote: > >> On Sunday, 14 October 2007 22:13, Mark Lord wrote: > >>> Since upgrading to 2.6.23.1 from 2.6.23-rc9, resume-from-RAM has been > >>> misbehaving here. > >>> > >>> It takes much (+5-7 seconds) longer to resume *sometimes*, but not > >>> all/most of the time. > >>> And sometimes I get get flashing keyboard LEDs and have to hold the > >>> power button > >>> in for a full hard reset. > >>> > >>> With 2.6.23-rc8/rc9, no such troubles. > >>> > >>> Difficult to reproduce, other than perhaps once a day. > >>> Anybody want to fess up with a likely candidate? > >> > >> Not really, but if you rule out all of the POWERPC and MIPS patches, > >> there's > >> not much left ... > > > > Yeah, I didn't see much there either. > > > > I'll keep an eye on things over the next few days, > > and post again if it persists. > > > > I was using the powertop patches with -rc9, but not with 2.6.23.1. > > Maybe they helped (???). > > It still happens. Well, I have no idea, sorry. I also have not been able to reproduce it here ... - 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: Regression: 2.6.23-rc9 okay, 2.6.23.1 resume problems
Mark Lord wrote: Rafael J. Wysocki wrote: On Sunday, 14 October 2007 22:13, Mark Lord wrote: Since upgrading to 2.6.23.1 from 2.6.23-rc9, resume-from-RAM has been misbehaving here. It takes much (+5-7 seconds) longer to resume *sometimes*, but not all/most of the time. And sometimes I get get flashing keyboard LEDs and have to hold the power button in for a full hard reset. With 2.6.23-rc8/rc9, no such troubles. Difficult to reproduce, other than perhaps once a day. Anybody want to fess up with a likely candidate? Not really, but if you rule out all of the POWERPC and MIPS patches, there's not much left ... Yeah, I didn't see much there either. I'll keep an eye on things over the next few days, and post again if it persists. I was using the powertop patches with -rc9, but not with 2.6.23.1. Maybe they helped (???). It still happens. - 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: Regression: 2.6.23-rc9 okay, 2.6.23.1 resume problems
Mark Lord wrote: Rafael J. Wysocki wrote: On Sunday, 14 October 2007 22:13, Mark Lord wrote: Since upgrading to 2.6.23.1 from 2.6.23-rc9, resume-from-RAM has been misbehaving here. It takes much (+5-7 seconds) longer to resume *sometimes*, but not all/most of the time. And sometimes I get get flashing keyboard LEDs and have to hold the power button in for a full hard reset. With 2.6.23-rc8/rc9, no such troubles. Difficult to reproduce, other than perhaps once a day. Anybody want to fess up with a likely candidate? Not really, but if you rule out all of the POWERPC and MIPS patches, there's not much left ... Yeah, I didn't see much there either. I'll keep an eye on things over the next few days, and post again if it persists. I was using the powertop patches with -rc9, but not with 2.6.23.1. Maybe they helped (???). It still happens. - 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: Regression: 2.6.23-rc9 okay, 2.6.23.1 resume problems
On Wednesday, 17 October 2007 00:10, Mark Lord wrote: Mark Lord wrote: Rafael J. Wysocki wrote: On Sunday, 14 October 2007 22:13, Mark Lord wrote: Since upgrading to 2.6.23.1 from 2.6.23-rc9, resume-from-RAM has been misbehaving here. It takes much (+5-7 seconds) longer to resume *sometimes*, but not all/most of the time. And sometimes I get get flashing keyboard LEDs and have to hold the power button in for a full hard reset. With 2.6.23-rc8/rc9, no such troubles. Difficult to reproduce, other than perhaps once a day. Anybody want to fess up with a likely candidate? Not really, but if you rule out all of the POWERPC and MIPS patches, there's not much left ... Yeah, I didn't see much there either. I'll keep an eye on things over the next few days, and post again if it persists. I was using the powertop patches with -rc9, but not with 2.6.23.1. Maybe they helped (???). It still happens. Well, I have no idea, sorry. I also have not been able to reproduce it here ... - 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: Regression: 2.6.23-rc9 okay, 2.6.23.1 resume problems
Rafael J. Wysocki wrote: On Sunday, 14 October 2007 22:13, Mark Lord wrote: Since upgrading to 2.6.23.1 from 2.6.23-rc9, resume-from-RAM has been misbehaving here. It takes much (+5-7 seconds) longer to resume *sometimes*, but not all/most of the time. And sometimes I get get flashing keyboard LEDs and have to hold the power button in for a full hard reset. With 2.6.23-rc8/rc9, no such troubles. Difficult to reproduce, other than perhaps once a day. Anybody want to fess up with a likely candidate? Not really, but if you rule out all of the POWERPC and MIPS patches, there's not much left ... Yeah, I didn't see much there either. I'll keep an eye on things over the next few days, and post again if it persists. I was using the powertop patches with -rc9, but not with 2.6.23.1. Maybe they helped (???). -ml - 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: Regression: 2.6.23-rc9 okay, 2.6.23.1 resume problems
On Sunday, 14 October 2007 22:13, Mark Lord wrote: > Since upgrading to 2.6.23.1 from 2.6.23-rc9, resume-from-RAM has been > misbehaving here. > > It takes much (+5-7 seconds) longer to resume *sometimes*, but not all/most > of the time. > And sometimes I get get flashing keyboard LEDs and have to hold the power > button > in for a full hard reset. > > With 2.6.23-rc8/rc9, no such troubles. > > Difficult to reproduce, other than perhaps once a day. > Anybody want to fess up with a likely candidate? Not really, but if you rule out all of the POWERPC and MIPS patches, there's not much left ... Greetings, Rafael - 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/
Regression: 2.6.23-rc9 okay, 2.6.23.1 resume problems
Since upgrading to 2.6.23.1 from 2.6.23-rc9, resume-from-RAM has been misbehaving here. It takes much (+5-7 seconds) longer to resume *sometimes*, but not all/most of the time. And sometimes I get get flashing keyboard LEDs and have to hold the power button in for a full hard reset. With 2.6.23-rc8/rc9, no such troubles. Difficult to reproduce, other than perhaps once a day. Anybody want to fess up with a likely candidate? Dell Inspiron 9400 Core2duo + 2GB RAM, 32-bit x86 kernel+user. .config below. - # # Automatically generated make config: don't edit # Linux kernel version: 2.6.23.1 # Sun Oct 14 09:22:05 2007 # CONFIG_X86_32=y CONFIG_GENERIC_TIME=y CONFIG_GENERIC_CMOS_UPDATE=y CONFIG_CLOCKSOURCE_WATCHDOG=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_SEMAPHORE_SLEEPERS=y CONFIG_X86=y CONFIG_MMU=y CONFIG_ZONE_DMA=y CONFIG_QUICKLIST=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_GENERIC_BUG=y CONFIG_GENERIC_HWEIGHT=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_DMI=y CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" # # General setup # CONFIG_EXPERIMENTAL=y CONFIG_LOCK_KERNEL=y CONFIG_INIT_ENV_ARG_LIMIT=32 CONFIG_LOCALVERSION="" # CONFIG_LOCALVERSION_AUTO is not set CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_SYSVIPC_SYSCTL=y CONFIG_POSIX_MQUEUE=y # CONFIG_BSD_PROCESS_ACCT is not set # CONFIG_TASKSTATS is not set # CONFIG_USER_NS is not set # CONFIG_AUDIT is not set CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y CONFIG_LOG_BUF_SHIFT=16 # CONFIG_CPUSETS is not set CONFIG_SYSFS_DEPRECATED=y # CONFIG_RELAY is not set CONFIG_BLK_DEV_INITRD=y CONFIG_INITRAMFS_SOURCE="" CONFIG_CC_OPTIMIZE_FOR_SIZE=y CONFIG_SYSCTL=y CONFIG_EMBEDDED=y CONFIG_UID16=y CONFIG_SYSCTL_SYSCALL=y CONFIG_KALLSYMS=y # CONFIG_KALLSYMS_ALL is not set # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_HOTPLUG=y CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_ELF_CORE=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_ANON_INODES=y CONFIG_EPOLL=y CONFIG_SIGNALFD=y CONFIG_EVENTFD=y CONFIG_SHMEM=y CONFIG_VM_EVENT_COUNTERS=y # CONFIG_SLUB_DEBUG is not set # CONFIG_SLAB is not set CONFIG_SLUB=y # CONFIG_SLOB is not set CONFIG_RT_MUTEXES=y # CONFIG_TINY_SHMEM is not set CONFIG_BASE_SMALL=0 CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y CONFIG_MODULE_FORCE_UNLOAD=y CONFIG_MODVERSIONS=y CONFIG_MODULE_SRCVERSION_ALL=y CONFIG_KMOD=y CONFIG_STOP_MACHINE=y CONFIG_BLOCK=y # CONFIG_LBD is not set # CONFIG_BLK_DEV_IO_TRACE is not set # CONFIG_LSF is not set CONFIG_BLK_DEV_BSG=y # # IO Schedulers # CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_AS=y # CONFIG_IOSCHED_DEADLINE is not set CONFIG_IOSCHED_CFQ=y # CONFIG_DEFAULT_AS is not set # CONFIG_DEFAULT_DEADLINE is not set CONFIG_DEFAULT_CFQ=y # CONFIG_DEFAULT_NOOP is not set CONFIG_DEFAULT_IOSCHED="cfq" # # Processor type and features # CONFIG_TICK_ONESHOT=y CONFIG_NO_HZ=y CONFIG_HIGH_RES_TIMERS=y CONFIG_SMP=y 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_PARAVIRT 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 is not set CONFIG_MCORE2=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_MGEODE_LX is not set # CONFIG_MCYRIXIII is not set # CONFIG_MVIAC3_2 is not set # CONFIG_MVIAC7 is not set # CONFIG_X86_GENERIC is not set CONFIG_X86_CMPXCHG=y CONFIG_X86_L1_CACHE_SHIFT=6 CONFIG_X86_XADD=y CONFIG_RWSEM_XCHGADD_ALGORITHM=y # CONFIG_ARCH_HAS_ILOG2_U32 is not set # CONFIG_ARCH_HAS_ILOG2_U64 is not set 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_X86_TSC=y CONFIG_X86_MINIMUM_CPU_FAMILY=4 CONFIG_HPET_TIMER=y CONFIG_NR_CPUS=2 # CONFIG_SCHED_SMT is not set CONFIG_SCHED_MC=y # CONFIG_PREEMPT_NONE is not set # CONFIG_PREEMPT_VOLUNTARY is not set CONFIG_PREEMPT=y CONFIG_PREEMPT_BKL=y CONFIG_X86_LOCAL_APIC=y CONFIG_X86_IO_APIC=y # CONFIG_X86_MCE is not set CONFIG_VM86=y # CONFIG_TOSHIBA is not set CONFIG_I8K=m CONFIG_X86_REBOOTFIXUPS=y CONFIG_MICROCODE=m CONFIG_MICROCODE_OLD_INTERFACE=y CONFIG_X86_MSR=m CONFIG_X86_CPUID=m # # Firmware Drivers # CONFIG_EDD=m CONFIG_DELL_RBU=m CONFIG_DCDBAS=m CONFIG_DMIID=y # CONFIG_NOHIGHMEM is not set CONFIG_HIGHMEM4G=y # CONFIG_HIGHMEM64G is not set CONFIG_VMSPLIT_3G=y # CONFIG_VMSPLIT_3G_OPT is
Regression: 2.6.23-rc9 okay, 2.6.23.1 resume problems
Since upgrading to 2.6.23.1 from 2.6.23-rc9, resume-from-RAM has been misbehaving here. It takes much (+5-7 seconds) longer to resume *sometimes*, but not all/most of the time. And sometimes I get get flashing keyboard LEDs and have to hold the power button in for a full hard reset. With 2.6.23-rc8/rc9, no such troubles. Difficult to reproduce, other than perhaps once a day. Anybody want to fess up with a likely candidate? Dell Inspiron 9400 Core2duo + 2GB RAM, 32-bit x86 kernel+user. .config below. - # # Automatically generated make config: don't edit # Linux kernel version: 2.6.23.1 # Sun Oct 14 09:22:05 2007 # CONFIG_X86_32=y CONFIG_GENERIC_TIME=y CONFIG_GENERIC_CMOS_UPDATE=y CONFIG_CLOCKSOURCE_WATCHDOG=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_SEMAPHORE_SLEEPERS=y CONFIG_X86=y CONFIG_MMU=y CONFIG_ZONE_DMA=y CONFIG_QUICKLIST=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_GENERIC_BUG=y CONFIG_GENERIC_HWEIGHT=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_DMI=y CONFIG_DEFCONFIG_LIST=/lib/modules/$UNAME_RELEASE/.config # # General setup # CONFIG_EXPERIMENTAL=y CONFIG_LOCK_KERNEL=y CONFIG_INIT_ENV_ARG_LIMIT=32 CONFIG_LOCALVERSION= # CONFIG_LOCALVERSION_AUTO is not set CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_SYSVIPC_SYSCTL=y CONFIG_POSIX_MQUEUE=y # CONFIG_BSD_PROCESS_ACCT is not set # CONFIG_TASKSTATS is not set # CONFIG_USER_NS is not set # CONFIG_AUDIT is not set CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y CONFIG_LOG_BUF_SHIFT=16 # CONFIG_CPUSETS is not set CONFIG_SYSFS_DEPRECATED=y # CONFIG_RELAY is not set CONFIG_BLK_DEV_INITRD=y CONFIG_INITRAMFS_SOURCE= CONFIG_CC_OPTIMIZE_FOR_SIZE=y CONFIG_SYSCTL=y CONFIG_EMBEDDED=y CONFIG_UID16=y CONFIG_SYSCTL_SYSCALL=y CONFIG_KALLSYMS=y # CONFIG_KALLSYMS_ALL is not set # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_HOTPLUG=y CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_ELF_CORE=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_ANON_INODES=y CONFIG_EPOLL=y CONFIG_SIGNALFD=y CONFIG_EVENTFD=y CONFIG_SHMEM=y CONFIG_VM_EVENT_COUNTERS=y # CONFIG_SLUB_DEBUG is not set # CONFIG_SLAB is not set CONFIG_SLUB=y # CONFIG_SLOB is not set CONFIG_RT_MUTEXES=y # CONFIG_TINY_SHMEM is not set CONFIG_BASE_SMALL=0 CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y CONFIG_MODULE_FORCE_UNLOAD=y CONFIG_MODVERSIONS=y CONFIG_MODULE_SRCVERSION_ALL=y CONFIG_KMOD=y CONFIG_STOP_MACHINE=y CONFIG_BLOCK=y # CONFIG_LBD is not set # CONFIG_BLK_DEV_IO_TRACE is not set # CONFIG_LSF is not set CONFIG_BLK_DEV_BSG=y # # IO Schedulers # CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_AS=y # CONFIG_IOSCHED_DEADLINE is not set CONFIG_IOSCHED_CFQ=y # CONFIG_DEFAULT_AS is not set # CONFIG_DEFAULT_DEADLINE is not set CONFIG_DEFAULT_CFQ=y # CONFIG_DEFAULT_NOOP is not set CONFIG_DEFAULT_IOSCHED=cfq # # Processor type and features # CONFIG_TICK_ONESHOT=y CONFIG_NO_HZ=y CONFIG_HIGH_RES_TIMERS=y CONFIG_SMP=y 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_PARAVIRT 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 is not set CONFIG_MCORE2=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_MGEODE_LX is not set # CONFIG_MCYRIXIII is not set # CONFIG_MVIAC3_2 is not set # CONFIG_MVIAC7 is not set # CONFIG_X86_GENERIC is not set CONFIG_X86_CMPXCHG=y CONFIG_X86_L1_CACHE_SHIFT=6 CONFIG_X86_XADD=y CONFIG_RWSEM_XCHGADD_ALGORITHM=y # CONFIG_ARCH_HAS_ILOG2_U32 is not set # CONFIG_ARCH_HAS_ILOG2_U64 is not set 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_X86_TSC=y CONFIG_X86_MINIMUM_CPU_FAMILY=4 CONFIG_HPET_TIMER=y CONFIG_NR_CPUS=2 # CONFIG_SCHED_SMT is not set CONFIG_SCHED_MC=y # CONFIG_PREEMPT_NONE is not set # CONFIG_PREEMPT_VOLUNTARY is not set CONFIG_PREEMPT=y CONFIG_PREEMPT_BKL=y CONFIG_X86_LOCAL_APIC=y CONFIG_X86_IO_APIC=y # CONFIG_X86_MCE is not set CONFIG_VM86=y # CONFIG_TOSHIBA is not set CONFIG_I8K=m CONFIG_X86_REBOOTFIXUPS=y CONFIG_MICROCODE=m CONFIG_MICROCODE_OLD_INTERFACE=y CONFIG_X86_MSR=m CONFIG_X86_CPUID=m # # Firmware Drivers # CONFIG_EDD=m CONFIG_DELL_RBU=m CONFIG_DCDBAS=m CONFIG_DMIID=y # CONFIG_NOHIGHMEM is not set CONFIG_HIGHMEM4G=y # CONFIG_HIGHMEM64G is not set CONFIG_VMSPLIT_3G=y # CONFIG_VMSPLIT_3G_OPT is not set
Re: Regression: 2.6.23-rc9 okay, 2.6.23.1 resume problems
On Sunday, 14 October 2007 22:13, Mark Lord wrote: Since upgrading to 2.6.23.1 from 2.6.23-rc9, resume-from-RAM has been misbehaving here. It takes much (+5-7 seconds) longer to resume *sometimes*, but not all/most of the time. And sometimes I get get flashing keyboard LEDs and have to hold the power button in for a full hard reset. With 2.6.23-rc8/rc9, no such troubles. Difficult to reproduce, other than perhaps once a day. Anybody want to fess up with a likely candidate? Not really, but if you rule out all of the POWERPC and MIPS patches, there's not much left ... Greetings, Rafael - 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: Regression: 2.6.23-rc9 okay, 2.6.23.1 resume problems
Rafael J. Wysocki wrote: On Sunday, 14 October 2007 22:13, Mark Lord wrote: Since upgrading to 2.6.23.1 from 2.6.23-rc9, resume-from-RAM has been misbehaving here. It takes much (+5-7 seconds) longer to resume *sometimes*, but not all/most of the time. And sometimes I get get flashing keyboard LEDs and have to hold the power button in for a full hard reset. With 2.6.23-rc8/rc9, no such troubles. Difficult to reproduce, other than perhaps once a day. Anybody want to fess up with a likely candidate? Not really, but if you rule out all of the POWERPC and MIPS patches, there's not much left ... Yeah, I didn't see much there either. I'll keep an eye on things over the next few days, and post again if it persists. I was using the powertop patches with -rc9, but not with 2.6.23.1. Maybe they helped (???). -ml - 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/
