Re: 2.6.11: suspending laptop makes system randomly unstable
Andrew Morton wrote: Miguelanxo Otero Salgueiro <[EMAIL PROTECTED]> wrote: I just compiled 2.6.11 from a 2.6.10 configuration for a desktop machine (with kernel preemption activated). Doing a make oldconfig bring some new options. I selected the default value (for my system) for them, so I keep configuring "make great kernel lock preemtive" to true (complete kernel configuration follows). Apart from the ALPS touchpad thing (see "2.6.11: touchpad unresponsive"), the new kernel keeps: - Setting randomly "last battery full charge" to a huge value (example: 400 Ah when max battery capacity is 38 Ah) so I get random charging/discharging timing patterns - Locking "softly" the system: for example, preventing new proceses from spawning. For example, if I suspend the laptop while in Xwindows, resuming will keep X but new proceses can't be started. Changing to a virtual console doesn't get past the login step, as a new shell can't be started. - Disabling/enabling double-clicks in the synaptic touchpad. Randomly. All of these symthoms are more or less randomly. As far as I can tell, everything is ok before suspending but does Random Nasty Things(tm) after coming out from suspension. Well, at least system clock works better than in 2.6.10. I will try to deactivate the main kernel lock thingie and see if that helps. You appear to have about five bugs here. Do any of them remain in 2.6.12-rc1? Well, one thing outstands: the synaptic touchpad is now really comfortable to use. Almost everything works, including simple and double clicks, and scrolling. Dragging is still broken. I must note I'm now using a synaptic Xinput driver, as suggested. The system seems much more stable in regard to suspension/resuming. The USB subsystem has kept working the first time I suspended and everything came back perfect. The second one in a row, the USB subsystem was halted, but doing a "modprobe -r uhci_hcd; modprobe uhci_hcd" made my USB periferals (keyboard and mouse) work again. As for the battery charging pattern, I can't say anything definitive, but it looks good ATM. No more "Ramdom Nasty Things(tm)", the clock works ok and there are no issues with proccess spawning. 9/10? - 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: 2.6.11: suspending laptop makes system randomly unstable
Arjan van de Ven wrote: Also, I'd consider it a regression that you had to go and find new X drivers due to a kernel change. We shouldn't do that. depends really on how bad the bug in the X driver was there is limits on how bug-2-bug compatible we can and want to be... Well, all I can tell is someone suggested changing to a Synaptic Xinput driver in at the 2.6.10 -> 2.6.11 transition, cause the synaptic drivers has a lot of new functionality. 2.6.10 was OK with kernel driver, no changes to X made. 2.6.11 without the Xinput driver was a PITA. With the new driver, it was still worse than 2.6.10, but better than plain 2.6.11. One thing better: the support for scrolling. 2.6.12-rc1 is almost OK with Xinput driver, can't say a thing about plain 2.6.12-rc1. As for dragging, it was ok in 2.6.10 and previous, but currently broken. - 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: 2.6.11: suspending laptop makes system randomly unstable
> Also, I'd consider it a regression that you had to go and find new X > drivers due to a kernel change. We shouldn't do that. depends really on how bad the bug in the X driver was there is limits on how bug-2-bug compatible we can and want to be... - 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: 2.6.11: suspending laptop makes system randomly unstable
Miguelanxo Otero Salgueiro <[EMAIL PROTECTED]> wrote: > > >You appear to have about five bugs here. Do any of them remain in > >2.6.12-rc1? > > > > > Well, one thing outstands: the synaptic touchpad is now really > comfortable to use. Almost everything works, including simple and double > clicks, and scrolling. Dragging is still broken. I must note I'm now > using a synaptic Xinput driver, as suggested. > > The system seems much more stable in regard to suspension/resuming. The > USB subsystem has kept working the first time I suspended and everything > came back perfect. The second one in a row, the USB subsystem was > halted, but doing a "modprobe -r uhci_hcd; modprobe uhci_hcd" made my > USB periferals (keyboard and mouse) work again. > > As for the battery charging pattern, I can't say anything definitive, > but it looks good ATM. > > No more "Ramdom Nasty Things(tm)", the clock works ok and there are no > issues with proccess spawning. > > 9/10? Let's go for 10/10. I assume that dragging _used_ to work, yes? Also, I'd consider it a regression that you had to go and find new X drivers due to a kernel change. We shouldn't do that. - 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: 2.6.11: suspending laptop makes system randomly unstable
Miguelanxo Otero Salgueiro <[EMAIL PROTECTED]> wrote: > > I just compiled 2.6.11 from a 2.6.10 configuration for a desktop machine > (with kernel preemption activated). > Doing a make oldconfig bring some new options. I selected the default > value (for my system) for them, so I keep configuring "make great kernel > lock preemtive" to true (complete kernel configuration follows). > > Apart from the ALPS touchpad thing (see "2.6.11: touchpad > unresponsive"), the new kernel keeps: > > - Setting randomly "last battery full charge" to a huge value > (example: 400 Ah when max battery capacity is 38 Ah) so I get random > charging/discharging timing patterns > - Locking "softly" the system: for example, preventing new proceses > from spawning. For example, if I suspend the laptop while in Xwindows, > resuming will keep X but new proceses can't be started. Changing to a > virtual console doesn't get past the login step, as a new shell can't be > started. > - Disabling/enabling double-clicks in the synaptic touchpad. Randomly. > > All of these symthoms are more or less randomly. As far as I can tell, > everything is ok before suspending but does Random Nasty Things(tm) > after coming out from suspension. > > Well, at least system clock works better than in 2.6.10. > > I will try to deactivate the main kernel lock thingie and see if that helps. > You appear to have about five bugs here. Do any of them remain in 2.6.12-rc1? - 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: 2.6.11: suspending laptop makes system randomly unstable
Hi! > I just compiled 2.6.11 from a 2.6.10 configuration for a desktop > machine (with kernel preemption activated). > Doing a make oldconfig bring some new options. I selected the default > value (for my system) for them, so I keep configuring "make great > kernel lock preemtive" to true (complete kernel configuration > follows). > > Apart from the ALPS touchpad thing (see "2.6.11: touchpad > unresponsive"), the new kernel keeps: 3 different problems, I'd say. >- Setting randomly "last battery full charge" to a huge value > (example: 400 Ah when max battery capacity is 38 Ah) so I get random > charging/discharging timing patterns try echo platform > disk. >- Locking "softly" the system: for example, preventing new >proceses from spawning. For example, if I suspend the laptop while in > Xwindows, resuming will keep X but new proceses can't be started. > Changing to a virtual console doesn't get past the login step, as a > new shell can't be started. Find out what prevents them from being started or find reproducible way to trigger it... >- Disabling/enabling double-clicks in the synaptic touchpad. >Randomly. input problem, ask vojtech. -- 64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms - 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: 2.6.11: suspending laptop makes system randomly unstable
Romano Giannetti <[EMAIL PROTECTED]> wrote: > > On Wed, Mar 02, 2005 at 01:43:42PM -0800, Andrew Morton wrote: > > > > That's an ACPI problem, I assume? > > > > Probably. There is something flaky in ACPI event (it happened sometime > between 2.6.7 and 2.6.9, i tried to check all the patches, but I had find > nothing. > > Could someone please check http://bugme.osdl.org/show_bug.cgi?id=4124 and > tell me what to do to help in debugging it? > > What is very strange is why "power button" and "read battery current > capacity" > events are working ok, and "sleep button" or "CRT switch button" or "ac > plugged/unplugged" seems more or less random delayed. > Add acpi-devel to cc... - 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: 2.6.11: suspending laptop makes system randomly unstable
On Wed, Mar 02, 2005 at 01:43:42PM -0800, Andrew Morton wrote: > > That's an ACPI problem, I assume? > Probably. There is something flaky in ACPI event (it happened sometime between 2.6.7 and 2.6.9, i tried to check all the patches, but I had find nothing. Could someone please check http://bugme.osdl.org/show_bug.cgi?id=4124 and tell me what to do to help in debugging it? What is very strange is why "power button" and "read battery current capacity" events are working ok, and "sleep button" or "CRT switch button" or "ac plugged/unplugged" seems more or less random delayed. Romano -- Romano Giannetti - Univ. Pontificia Comillas (Madrid, Spain) Electronic Engineer - phone +34 915 422 800 ext 2416 fax +34 915 596 569 - 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: 2.6.11: suspending laptop makes system randomly unstable
On Wed, Mar 02, 2005 at 08:50:08PM +0100, Miguelanxo Otero Salgueiro wrote: >- Setting randomly "last battery full charge" to a huge value > (example: 400 Ah when max battery capacity is 38 Ah) so I get random > charging/discharging timing patterns Happens to me sometime (and misdetection of ac status too, although I rmmod/insmod ac on suspend script). For me is not related to suspend, nor to preempt. Try to put a for i in 1 2 3 4 5 6 7 8; do acpi > /dev/null ; done in the resume script. Works for me. More info (config, logs, dsdt...) in http://bugme.osdl.org/show_bug.cgi?id=4124 Romano -- Romano Giannetti - Univ. Pontificia Comillas (Madrid, Spain) Electronic Engineer - phone +34 915 422 800 ext 2416 fax +34 915 596 569 - 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: 2.6.11: suspending laptop makes system randomly unstable
Miguelanxo Otero Salgueiro <[EMAIL PROTECTED]> wrote: > > I just compiled 2.6.11 from a 2.6.10 configuration for a desktop machine > (with kernel preemption activated). > Doing a make oldconfig bring some new options. I selected the default > value (for my system) for them, so I keep configuring "make great kernel > lock preemtive" to true (complete kernel configuration follows). > > Apart from the ALPS touchpad thing (see "2.6.11: touchpad > unresponsive"), the new kernel keeps: > > - Setting randomly "last battery full charge" to a huge value > (example: 400 Ah when max battery capacity is 38 Ah) so I get random > charging/discharging timing patterns That's an ACPI problem, I assume? > - Locking "softly" the system: for example, preventing new proceses > from spawning. For example, if I suspend the laptop while in Xwindows, > resuming will keep X but new proceses can't be started. Changing to a > virtual console doesn't get past the login step, as a new shell can't be > started. Is there no oops trace? Could you switch to a vc, hit alt-sysrq-t and reboot, see if you get an all-task backtrace in the kernel logs and of so, send it? > - Disabling/enabling double-clicks in the synaptic touchpad. Randomly. > All of these symthoms are more or less randomly. As far as I can tell, > everything is ok before suspending but does Random Nasty Things(tm) > after coming out from suspension. - 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/
2.6.11: suspending laptop makes system randomly unstable
I just compiled 2.6.11 from a 2.6.10 configuration for a desktop machine (with kernel preemption activated). Doing a make oldconfig bring some new options. I selected the default value (for my system) for them, so I keep configuring "make great kernel lock preemtive" to true (complete kernel configuration follows). Apart from the ALPS touchpad thing (see "2.6.11: touchpad unresponsive"), the new kernel keeps: - Setting randomly "last battery full charge" to a huge value (example: 400 Ah when max battery capacity is 38 Ah) so I get random charging/discharging timing patterns - Locking "softly" the system: for example, preventing new proceses from spawning. For example, if I suspend the laptop while in Xwindows, resuming will keep X but new proceses can't be started. Changing to a virtual console doesn't get past the login step, as a new shell can't be started. - Disabling/enabling double-clicks in the synaptic touchpad. Randomly. All of these symthoms are more or less randomly. As far as I can tell, everything is ok before suspending but does Random Nasty Things(tm) after coming out from suspension. Well, at least system clock works better than in 2.6.10. I will try to deactivate the main kernel lock thingie and see if that helps. # # Automatically generated make config: don't edit # Linux kernel version: 2.6.11 # Wed Mar 2 19:22:08 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 # # General setup # CONFIG_LOCALVERSION="" CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_POSIX_MQUEUE=y # CONFIG_BSD_PROCESS_ACCT is not set CONFIG_SYSCTL=y # CONFIG_AUDIT is not set CONFIG_LOG_BUF_SHIFT=14 CONFIG_HOTPLUG=y CONFIG_KOBJECT_UEVENT=y # CONFIG_IKCONFIG is not set # CONFIG_EMBEDDED is not set CONFIG_KALLSYMS=y # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_FUTEX=y CONFIG_EPOLL=y # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set 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 # # Loadable module support # CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y # CONFIG_MODULE_FORCE_UNLOAD is not set CONFIG_OBSOLETE_MODPARM=y # CONFIG_MODVERSIONS is not set # CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_KMOD=y # # Processor type and features # CONFIG_X86_PC=y # CONFIG_X86_ELAN is not set # CONFIG_X86_VOYAGER is not set # CONFIG_X86_NUMAQ is not set # CONFIG_X86_SUMMIT is not set # CONFIG_X86_BIGSMP is not set # CONFIG_X86_VISWS is not set # CONFIG_X86_GENERICARCH is not set # CONFIG_X86_ES7000 is not set # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set # CONFIG_M586TSC is not set # CONFIG_M586MMX is not set # CONFIG_M686 is not set # CONFIG_MPENTIUMII is not set # CONFIG_MPENTIUMIII is not set # CONFIG_MPENTIUMM is not set CONFIG_MPENTIUM4=y # 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_MCYRIXIII is not set # CONFIG_MVIAC3_2 is not set # CONFIG_X86_GENERIC is not set CONFIG_X86_CMPXCHG=y CONFIG_X86_XADD=y CONFIG_X86_L1_CACHE_SHIFT=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_SMP is not set CONFIG_PREEMPT=y CONFIG_PREEMPT_BKL=y # CONFIG_X86_UP_APIC is not set CONFIG_X86_TSC=y CONFIG_X86_MCE=y # CONFIG_X86_MCE_NONFATAL is not set CONFIG_TOSHIBA=m # CONFIG_I8K is not set # CONFIG_MICROCODE is not set # CONFIG_X86_MSR is not set # CONFIG_X86_CPUID is not set # # Firmware Drivers # # CONFIG_EDD is not set CONFIG_NOHIGHMEM=y # CONFIG_HIGHMEM4G is not set # CONFIG_HIGHMEM64G is not set # CONFIG_MATH_EMULATION is not set CONFIG_MTRR=y # CONFIG_EFI is not set CONFIG_HAVE_DEC_LOCK=y # CONFIG_REGPARM is not set # # Power management options (ACPI, APM) # CONFIG_PM=y # CONFIG_PM_DEBUG is not set # CONFIG_SOFTWARE_SUSPEND is not set # # ACPI (Advanced Configuration and Power Interface) Support # CONFIG_ACPI=y CONFIG_ACPI_BOOT=y CONFIG_ACPI_INTERPRETER=y CONFIG_ACPI_SLEEP=y CONFIG_ACPI_SLEEP_PROC_FS=y CONFIG_ACPI_AC=y CONFIG_ACPI_BATTERY=y CONFIG_ACPI_BUTTON=y CONFIG_ACPI_VIDEO=m CONFIG_ACPI_FAN=y CONFIG_ACPI_PROCESSOR=y CONFIG_ACPI_THERMAL=y # CONFIG_ACPI_ASUS is not set # CONFIG_ACPI_IBM is not set CONFIG_ACPI_TOSHIBA=y CONFIG_ACPI_BLACKLIST_YEAR=0 # CONFIG_ACPI_DEBUG is not set CONFIG_ACPI_BUS=y CONFIG_ACPI_EC=y CONFIG_ACPI_POWER=y CONFIG_ACPI_PCI=y CONFIG_ACPI_SYSTEM=y CONFIG_X86_PM_TIMER=y # CONFIG_ACPI_CONTAINER is not set # # APM (Advanced Power Management) BIOS Support # # CONFIG_APM is not set # # CPU Frequenc
