* Re: [3/3] 2.6.23-rc6: known regressions v2 [not found] <46EB3EF8.6040103@googlemail.com> @ 2007-09-15 2:29 ` Michal Piotrowski 2007-09-15 18:20 ` Rafael J. Wysocki [not found] ` <200709152020.33179.rjw@sisk.pl> 0 siblings, 2 replies; 7+ messages in thread From: Michal Piotrowski @ 2007-09-15 2:29 UTC (permalink / raw) To: Linus Torvalds Cc: Christian Volkmann, Soeren Sonnenburg, Arkadiusz Miskiewicz, Thomas Voegtle, Greg KH, LKML, Christian Leber, Andrew Morton, linux-pm, linux-usb-devel Hi all, Here is a list of some known regressions in 2.6.23-rc6. Feel free to add new regressions/remove fixed etc. http://kernelnewbies.org/known_regressions List of Aces Name Regressions fixed since 21-Jun-2007 Adrian Bunk 10 Andi Kleen 7 Linus Torvalds 6 Alan Stern 5 Hugh Dickins 5 Trond Myklebust 5 Andrew Morton 4 David S. Miller 4 Al Viro 3 Alexey Starikovskiy 3 Cornelia Huck 3 Jens Axboe 3 Stephen Hemminger 3 Tejun Heo 3 Power management Subject : powersaving degradation, (time spend in C0 goes up after a while) References : http://lkml.org/lkml/2007/9/2/142 Last known good : ? Submitter : Christian Leber <christian@leber.de> Caused-By : ? Handled-By : ? Status : unknown Subject : something broke resume from s2ram on mbp c1d (??? :)) References : http://lkml.org/lkml/2007/8/28/67 Last known good : 2.6.23-rc3 Submitter : Soeren Sonnenburg <kernel@nn7.de> Caused-By : ? Handled-By : Rafael J. Wysocki <rjw@sisk.pl> Status : unknown Subject : 2.6.23-rc2 swsusp, suddenly increased uptime References : http://lkml.org/lkml/2007/8/12/249 Last known good : ? Submitter : Thomas Voegtle <tv@lio96.de> Caused-By : ? Handled-By : Rafael J. Wysocki <rjw@sisk.pl> Status : problem is being debugged Subject : resume from ram much slower References : http://lkml.org/lkml/2007/8/10/275 Last known good : 2.6.23-rc1 ? Submitter : Arkadiusz Miskiewicz <arekm@maven.pl> Caused-By : ? Handled-By : Rafael J. Wysocki <rjw@sisk.pl> Status : problem is being debugged USB Subject : usb 1-1: device not accepting address 2, error -62 References : http://lkml.org/lkml/2007/9/14/302 Last known good : ? Submitter : Christian Volkmann <haveaniceday@cv-sv.de> Caused-By : ? Handled-By : ? Status : unknown Farewell! Michal -- LOGOUT http://www.stardust.webpages.pl/ ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [3/3] 2.6.23-rc6: known regressions v2 2007-09-15 2:29 ` [3/3] 2.6.23-rc6: known regressions v2 Michal Piotrowski @ 2007-09-15 18:20 ` Rafael J. Wysocki [not found] ` <200709152020.33179.rjw@sisk.pl> 1 sibling, 0 replies; 7+ messages in thread From: Rafael J. Wysocki @ 2007-09-15 18:20 UTC (permalink / raw) To: Michal Piotrowski Cc: Soeren Sonnenburg, Arkadiusz Miskiewicz, Thomas Voegtle, LKML, Andrew Morton, Linus Torvalds, linux-pm On Saturday, 15 September 2007 04:29, Michal Piotrowski wrote: > Hi all, > > Here is a list of some known regressions in 2.6.23-rc6. > > Feel free to add new regressions/remove fixed etc. > http://kernelnewbies.org/known_regressions > > List of Aces > > Name Regressions fixed since 21-Jun-2007 > Adrian Bunk 10 > Andi Kleen 7 > Linus Torvalds 6 > Alan Stern 5 > Hugh Dickins 5 > Trond Myklebust 5 > Andrew Morton 4 > David S. Miller 4 > Al Viro 3 > Alexey Starikovskiy 3 > Cornelia Huck 3 > Jens Axboe 3 > Stephen Hemminger 3 > Tejun Heo 3 > > > > Power management > > Subject : powersaving degradation, (time spend in C0 goes up after a while) > References : http://lkml.org/lkml/2007/9/2/142 > Last known good : ? > Submitter : Christian Leber <christian@leber.de> > Caused-By : ? > Handled-By : ? > Status : unknown > > Subject : something broke resume from s2ram on mbp c1d (??? :)) > References : http://lkml.org/lkml/2007/8/28/67 > Last known good : 2.6.23-rc3 > Submitter : Soeren Sonnenburg <kernel@nn7.de> > Caused-By : ? > Handled-By : Rafael J. Wysocki <rjw@sisk.pl> > Status : unknown Soeren said he would bisect, but I guess he didn't have the time. > Subject : 2.6.23-rc2 swsusp, suddenly increased uptime > References : http://lkml.org/lkml/2007/8/12/249 > Last known good : ? > Submitter : Thomas Voegtle <tv@lio96.de> > Caused-By : ? > Handled-By : Rafael J. Wysocki <rjw@sisk.pl> > Status : problem is being debugged This is hard to reproduce, AFAICS, and unreproducible on any boxes I have access to. > Subject : resume from ram much slower > References : http://lkml.org/lkml/2007/8/10/275 > Last known good : 2.6.23-rc1 ? > Submitter : Arkadiusz Miskiewicz <arekm@maven.pl> > Caused-By : ? > Handled-By : Rafael J. Wysocki <rjw@sisk.pl> > Status : problem is being debugged Unresolved, bisection might be helpful. Greetings, Rafael ^ permalink raw reply [flat|nested] 7+ messages in thread
[parent not found: <200709152020.33179.rjw@sisk.pl>]
* Re: [3/3] 2.6.23-rc6: known regressions v2 [not found] ` <200709152020.33179.rjw@sisk.pl> @ 2007-09-17 19:44 ` Arkadiusz Miskiewicz [not found] ` <200709172144.43761.arekm@maven.pl> 1 sibling, 0 replies; 7+ messages in thread From: Arkadiusz Miskiewicz @ 2007-09-17 19:44 UTC (permalink / raw) To: Rafael J. Wysocki, Thomas Gleixner Cc: Soeren Sonnenburg, Michal Piotrowski, Thomas Voegtle, LKML, Andrew Morton, Linus Torvalds, linux-pm On Saturday 15 of September 2007, Rafael J. Wysocki wrote: > On Saturday, 15 September 2007 04:29, Michal Piotrowski wrote: > > Subject : resume from ram much slower > > References : http://lkml.org/lkml/2007/8/10/275 > > Last known good : 2.6.23-rc1 ? > > Submitter : Arkadiusz Miskiewicz <arekm@maven.pl> > > Caused-By : ? > > Handled-By : Rafael J. Wysocki <rjw@sisk.pl> > > Status : problem is being debugged > > Unresolved, bisection might be helpful. Took 16 hours of bisecting and playing with stuff. It looks like the problematic patch is 18de5bc4c1f1f1fa5e14f354a7603bd6e9d4e3b6. bisection was hard and I'm 95% sure that this is the problematic patch. I'm currently using 2.6.23-rc6 with this reverted and so far resume works as it should. commit 18de5bc4c1f1f1fa5e14f354a7603bd6e9d4e3b6 Author: Thomas Gleixner <tglx@linutronix.de> Date: Sat Jul 21 04:37:34 2007 -0700 clockevents: fix resume logic We need to make sure, that the clockevent devices are resumed, before the tick is resumed. The current resume logic does not guarantee this. Add CLOCK_EVT_MODE_RESUME and call the set mode functions of the clock event devices before resuming the tick / oneshot functionality. Fixup the existing users. Thanks to Nigel Cunningham for tracking down a long standing thinko, which affected the jinxed VAIO. [akpm@linux-foundation.org: xen build fix] Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Cc: john stultz <johnstul@us.ibm.com> Cc: Rusty Russell <rusty@rustcorp.com.au> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> diff --git a/arch/arm/mach-davinci/time.c b/arch/arm/mach-davinci/time.c index 4d8425d..e96a3dc 100644 --- a/arch/arm/mach-davinci/time.c +++ b/arch/arm/mach-davinci/time.c @@ -285,6 +285,8 @@ static void davinci_set_mode(enum clock_event_mode mode, case CLOCK_EVT_MODE_SHUTDOWN: t->opts = TIMER_OPTS_DISABLED; break; + case CLOCK_EVT_MODE_RESUME: + break; } } diff --git a/arch/arm/mach-imx/time.c b/arch/arm/mach-imx/time.c index 010f6fa..d86d124 100644 --- a/arch/arm/mach-imx/time.c +++ b/arch/arm/mach-imx/time.c @@ -159,6 +159,7 @@ static void imx_set_mode(enum clock_event_mode mode, struct clock_event_device * break; case CLOCK_EVT_MODE_SHUTDOWN: case CLOCK_EVT_MODE_UNUSED: + case CLOCK_EVT_MODE_RESUME: /* Left event sources disabled, no more interrupts appears */ break; } diff --git a/arch/arm/mach-ixp4xx/common.c b/arch/arm/mach-ixp4xx/common.c index 8112f72..23e7fba 100644 --- a/arch/arm/mach-ixp4xx/common.c +++ b/arch/arm/mach-ixp4xx/common.c @@ -459,6 +459,8 @@ static void ixp4xx_set_mode(enum clock_event_mode mode, default: osrt = opts = 0; break; + case CLOCK_EVT_MODE_RESUME: + break; } *IXP4XX_OSRT1 = osrt | opts; diff --git a/arch/arm/mach-omap1/time.c b/arch/arm/mach-omap1/time.c index 3705d20..237651e 100644 --- a/arch/arm/mach-omap1/time.c +++ b/arch/arm/mach-omap1/time.c @@ -156,6 +156,7 @@ static void omap_mpu_set_mode(enum clock_event_mode mode, break; case CLOCK_EVT_MODE_UNUSED: case CLOCK_EVT_MODE_SHUTDOWN: + case CLOCK_EVT_MODE_RESUME: break; } } diff --git a/arch/arm/plat-omap/timer32k.c b/arch/arm/plat-omap/timer32k.c index 2feceec..b0af014 100644 --- a/arch/arm/plat-omap/timer32k.c +++ b/arch/arm/plat-omap/timer32k.c @@ -156,6 +156,8 @@ static void omap_32k_timer_set_mode(enum clock_event_mode mode, case CLOCK_EVT_MODE_SHUTDOWN: omap_32k_timer_stop(); break; + case CLOCK_EVT_MODE_RESUME: + break; } } diff --git a/arch/i386/kernel/apic.c b/arch/i386/kernel/apic.c index 67824f3..610f44b 100644 --- a/arch/i386/kernel/apic.c +++ b/arch/i386/kernel/apic.c @@ -263,6 +263,9 @@ static void lapic_timer_setup(enum clock_event_mode mode, v |= (APIC_LVT_MASKED | LOCAL_TIMER_VECTOR); apic_write_around(APIC_LVTT, v); break; + case CLOCK_EVT_MODE_RESUME: + /* Nothing to do here */ + break; } local_irq_restore(flags); diff --git a/arch/i386/kernel/hpet.c b/arch/i386/kernel/hpet.c index 17d7345..cfbf792 100644 --- a/arch/i386/kernel/hpet.c +++ b/arch/i386/kernel/hpet.c @@ -187,6 +187,10 @@ static void hpet_set_mode(enum clock_event_mode mode, cfg &= ~HPET_TN_ENABLE; hpet_writel(cfg, HPET_T0_CFG); break; + + case CLOCK_EVT_MODE_RESUME: + hpet_enable_int(); + break; } } @@ -217,6 +221,7 @@ static struct clocksource clocksource_hpet = { .mask = HPET_MASK, .shift = HPET_SHIFT, .flags = CLOCK_SOURCE_IS_CONTINUOUS, + .resume = hpet_start_counter, }; /* @@ -291,7 +296,6 @@ int __init hpet_enable(void) clocksource_register(&clocksource_hpet); - if (id & HPET_ID_LEGSUP) { hpet_enable_int(); hpet_reserve_platform_timers(id); @@ -524,68 +528,3 @@ irqreturn_t hpet_rtc_interrupt(int irq, void *dev_id) return IRQ_HANDLED; } #endif - - -/* - * Suspend/resume part - */ - -#ifdef CONFIG_PM - -static int hpet_suspend(struct sys_device *sys_device, pm_message_t state) -{ - unsigned long cfg = hpet_readl(HPET_CFG); - - cfg &= ~(HPET_CFG_ENABLE|HPET_CFG_LEGACY); - hpet_writel(cfg, HPET_CFG); - - return 0; -} - -static int hpet_resume(struct sys_device *sys_device) -{ - unsigned int id; - - hpet_start_counter(); - - id = hpet_readl(HPET_ID); - - if (id & HPET_ID_LEGSUP) - hpet_enable_int(); - - return 0; -} - -static struct sysdev_class hpet_class = { - set_kset_name("hpet"), - .suspend = hpet_suspend, - .resume = hpet_resume, -}; - -static struct sys_device hpet_device = { - .id = 0, - .cls = &hpet_class, -}; - - -static __init int hpet_register_sysfs(void) -{ - int err; - - if (!is_hpet_capable()) - return 0; - - err = sysdev_class_register(&hpet_class); - - if (!err) { - err = sysdev_register(&hpet_device); - if (err) - sysdev_class_unregister(&hpet_class); - } - - return err; -} - -device_initcall(hpet_register_sysfs); - -#endif diff --git a/arch/i386/kernel/i8253.c b/arch/i386/kernel/i8253.c index f8a3c40..931eabe 100644 --- a/arch/i386/kernel/i8253.c +++ b/arch/i386/kernel/i8253.c @@ -3,11 +3,11 @@ * */ #include <linux/clockchips.h> -#include <linux/spinlock.h> +#include <linux/init.h> +#include <linux/interrupt.h> #include <linux/jiffies.h> -#include <linux/sysdev.h> #include <linux/module.h> -#include <linux/init.h> +#include <linux/spinlock.h> #include <asm/smp.h> #include <asm/delay.h> @@ -41,26 +41,24 @@ static void init_pit_timer(enum clock_event_mode mode, case CLOCK_EVT_MODE_PERIODIC: /* binary, mode 2, LSB/MSB, ch 0 */ outb_p(0x34, PIT_MODE); - udelay(10); outb_p(LATCH & 0xff , PIT_CH0); /* LSB */ - udelay(10); outb(LATCH >> 8 , PIT_CH0); /* MSB */ break; - /* - * Avoid unnecessary state transitions, as it confuses - * Geode / Cyrix based boxen. - */ case CLOCK_EVT_MODE_SHUTDOWN: - if (evt->mode == CLOCK_EVT_MODE_UNUSED) - break; case CLOCK_EVT_MODE_UNUSED: - if (evt->mode == CLOCK_EVT_MODE_SHUTDOWN) - break; + outb_p(0x30, PIT_MODE); + outb_p(0, PIT_CH0); /* LSB */ + outb_p(0, PIT_CH0); /* MSB */ + break; + case CLOCK_EVT_MODE_ONESHOT: /* One shot setup */ outb_p(0x38, PIT_MODE); - udelay(10); + break; + + case CLOCK_EVT_MODE_RESUME: + /* Nothing to do here */ break; } spin_unlock_irqrestore(&i8253_lock, flags); diff --git a/arch/i386/kernel/vmiclock.c b/arch/i386/kernel/vmiclock.c index f9b845f..d23077c 100644 --- a/arch/i386/kernel/vmiclock.c +++ b/arch/i386/kernel/vmiclock.c @@ -142,6 +142,7 @@ static void vmi_timer_set_mode(enum clock_event_mode mode, switch (mode) { case CLOCK_EVT_MODE_ONESHOT: + case CLOCK_EVT_MODE_RESUME: break; case CLOCK_EVT_MODE_PERIODIC: cycles_per_hz = vmi_timer_ops.get_cycle_frequency(); diff --git a/arch/i386/xen/time.c b/arch/i386/xen/time.c index 51fdabf..dfd6db6 100644 --- a/arch/i386/xen/time.c +++ b/arch/i386/xen/time.c @@ -412,6 +412,7 @@ static void xen_timerop_set_mode(enum clock_event_mode mode, break; case CLOCK_EVT_MODE_ONESHOT: + case CLOCK_EVT_MODE_RESUME: break; case CLOCK_EVT_MODE_UNUSED: @@ -474,6 +475,8 @@ static void xen_vcpuop_set_mode(enum clock_event_mode mode, HYPERVISOR_vcpu_op(VCPUOP_stop_periodic_timer, cpu, NULL)) BUG(); break; + case CLOCK_EVT_MODE_RESUME: + break; } } diff --git a/arch/sh/kernel/timers/timer-tmu.c b/arch/sh/kernel/timers/timer-tmu.c index 097ebd4..7aca37d 100644 --- a/arch/sh/kernel/timers/timer-tmu.c +++ b/arch/sh/kernel/timers/timer-tmu.c @@ -80,6 +80,7 @@ static void tmu_set_mode(enum clock_event_mode mode, break; case CLOCK_EVT_MODE_UNUSED: case CLOCK_EVT_MODE_SHUTDOWN: + case CLOCK_EVT_MODE_RESUME: break; } } diff --git a/arch/sparc64/kernel/time.c b/arch/sparc64/kernel/time.c index e340eb4..87c10a7 100644 --- a/arch/sparc64/kernel/time.c +++ b/arch/sparc64/kernel/time.c @@ -931,6 +931,7 @@ static void sparc64_timer_setup(enum clock_event_mode mode, { switch (mode) { case CLOCK_EVT_MODE_ONESHOT: + case CLOCK_EVT_MODE_RESUME: break; case CLOCK_EVT_MODE_SHUTDOWN: diff --git a/drivers/lguest/lguest.c b/drivers/lguest/lguest.c index 434fea1..18dade0 100644 --- a/drivers/lguest/lguest.c +++ b/drivers/lguest/lguest.c @@ -398,6 +398,8 @@ static void lguest_clockevent_set_mode(enum clock_event_mode mode, break; case CLOCK_EVT_MODE_PERIODIC: BUG(); + case CLOCK_EVT_MODE_RESUME: + break; } } diff --git a/include/linux/clockchips.h b/include/linux/clockchips.h index 8d7a390..e0bd46e 100644 --- a/include/linux/clockchips.h +++ b/include/linux/clockchips.h @@ -23,6 +23,7 @@ enum clock_event_mode { CLOCK_EVT_MODE_SHUTDOWN, CLOCK_EVT_MODE_PERIODIC, CLOCK_EVT_MODE_ONESHOT, + CLOCK_EVT_MODE_RESUME, }; /* Clock event notification values */ diff --git a/kernel/time/tick-broadcast.c b/kernel/time/tick-broadcast.c index 8001d37..8339af2 100644 --- a/kernel/time/tick-broadcast.c +++ b/kernel/time/tick-broadcast.c @@ -49,7 +49,7 @@ cpumask_t *tick_get_broadcast_mask(void) */ static void tick_broadcast_start_periodic(struct clock_event_device *bc) { - if (bc && bc->mode == CLOCK_EVT_MODE_SHUTDOWN) + if (bc) tick_setup_periodic(bc, 1); } @@ -299,7 +299,7 @@ void tick_suspend_broadcast(void) spin_lock_irqsave(&tick_broadcast_lock, flags); bc = tick_broadcast_device.evtdev; - if (bc && tick_broadcast_device.mode == TICKDEV_MODE_PERIODIC) + if (bc) clockevents_set_mode(bc, CLOCK_EVT_MODE_SHUTDOWN); spin_unlock_irqrestore(&tick_broadcast_lock, flags); @@ -316,6 +316,8 @@ int tick_resume_broadcast(void) bc = tick_broadcast_device.evtdev; if (bc) { + clockevents_set_mode(bc, CLOCK_EVT_MODE_RESUME); + switch (tick_broadcast_device.mode) { case TICKDEV_MODE_PERIODIC: if(!cpus_empty(tick_broadcast_mask)) diff --git a/kernel/time/tick-common.c b/kernel/time/tick-common.c index a96ec9a..77a21ab 100644 --- a/kernel/time/tick-common.c +++ b/kernel/time/tick-common.c @@ -318,12 +318,17 @@ static void tick_resume(void) { struct tick_device *td = &__get_cpu_var(tick_cpu_device); unsigned long flags; + int broadcast = tick_resume_broadcast(); spin_lock_irqsave(&tick_device_lock, flags); - if (td->mode == TICKDEV_MODE_PERIODIC) - tick_setup_periodic(td->evtdev, 0); - else - tick_resume_oneshot(); + clockevents_set_mode(td->evtdev, CLOCK_EVT_MODE_RESUME); + + if (!broadcast) { + if (td->mode == TICKDEV_MODE_PERIODIC) + tick_setup_periodic(td->evtdev, 0); + else + tick_resume_oneshot(); + } spin_unlock_irqrestore(&tick_device_lock, flags); } @@ -360,8 +365,7 @@ static int tick_notify(struct notifier_block *nb, unsigned long reason, break; case CLOCK_EVT_NOTIFY_RESUME: - if (!tick_resume_broadcast()) - tick_resume(); + tick_resume(); break; default: > > Greetings, > Rafael -- Arkadiusz Miśkiewicz PLD/Linux Team arekm / maven.pl http://ftp.pld-linux.org/ ^ permalink raw reply related [flat|nested] 7+ messages in thread
[parent not found: <200709172144.43761.arekm@maven.pl>]
* Re: [3/3] 2.6.23-rc6: known regressions v2 [not found] ` <200709172144.43761.arekm@maven.pl> @ 2007-09-17 19:47 ` Thomas Gleixner [not found] ` <1190058463.2995.14.camel@chaos> 1 sibling, 0 replies; 7+ messages in thread From: Thomas Gleixner @ 2007-09-17 19:47 UTC (permalink / raw) To: Arkadiusz Miskiewicz Cc: Soeren Sonnenburg, Michal Piotrowski, Thomas Voegtle, LKML, Andrew Morton, Linus Torvalds, linux-pm On Mon, 2007-09-17 at 21:44 +0200, Arkadiusz Miskiewicz wrote: > On Saturday 15 of September 2007, Rafael J. Wysocki wrote: > > On Saturday, 15 September 2007 04:29, Michal Piotrowski wrote: > > > > Subject : resume from ram much slower > > > References : http://lkml.org/lkml/2007/8/10/275 > > > Last known good : 2.6.23-rc1 ? > > > Submitter : Arkadiusz Miskiewicz <arekm@maven.pl> > > > Caused-By : ? > > > Handled-By : Rafael J. Wysocki <rjw@sisk.pl> > > > Status : problem is being debugged > > > > Unresolved, bisection might be helpful. > > Took 16 hours of bisecting and playing with stuff. > > It looks like the problematic patch is 18de5bc4c1f1f1fa5e14f354a7603bd6e9d4e3b6. > bisection was hard and I'm 95% sure that this is the problematic patch. > I'm currently using 2.6.23-rc6 with this reverted and so far resume works as it should. > > > commit 18de5bc4c1f1f1fa5e14f354a7603bd6e9d4e3b6 > Author: Thomas Gleixner <tglx@linutronix.de> > Date: Sat Jul 21 04:37:34 2007 -0700 > > clockevents: fix resume logic Linus pulled a series of patches which are addressing this issue into his tree yesterday. Can you please retest against current git ? tglx ^ permalink raw reply [flat|nested] 7+ messages in thread
[parent not found: <1190058463.2995.14.camel@chaos>]
* Re: [3/3] 2.6.23-rc6: known regressions v2 [not found] ` <1190058463.2995.14.camel@chaos> @ 2007-09-17 20:51 ` Arkadiusz Miskiewicz [not found] ` <200709172251.07769.arekm@maven.pl> 1 sibling, 0 replies; 7+ messages in thread From: Arkadiusz Miskiewicz @ 2007-09-17 20:51 UTC (permalink / raw) To: Thomas Gleixner Cc: Soeren Sonnenburg, Michal Piotrowski, Thomas Voegtle, LKML, Andrew Morton, Linus Torvalds, linux-pm On Monday 17 of September 2007, Thomas Gleixner wrote: > On Mon, 2007-09-17 at 21:44 +0200, Arkadiusz Miskiewicz wrote: > > On Saturday 15 of September 2007, Rafael J. Wysocki wrote: > > > On Saturday, 15 September 2007 04:29, Michal Piotrowski wrote: > > > > Subject : resume from ram much slower > > > > References : http://lkml.org/lkml/2007/8/10/275 > > > > Last known good : 2.6.23-rc1 ? > > > > Submitter : Arkadiusz Miskiewicz <arekm@maven.pl> > > > > Caused-By : ? > > > > Handled-By : Rafael J. Wysocki <rjw@sisk.pl> > > > > Status : problem is being debugged > > > > > > Unresolved, bisection might be helpful. > > > > Took 16 hours of bisecting and playing with stuff. > > > > It looks like the problematic patch is > > 18de5bc4c1f1f1fa5e14f354a7603bd6e9d4e3b6. bisection was hard and I'm 95% > > sure that this is the problematic patch. I'm currently using 2.6.23-rc6 > > with this reverted and so far resume works as it should. > > > > > > commit 18de5bc4c1f1f1fa5e14f354a7603bd6e9d4e3b6 > > Author: Thomas Gleixner <tglx@linutronix.de> > > Date: Sat Jul 21 04:37:34 2007 -0700 > > > > clockevents: fix resume logic > > Linus pulled a series of patches which are addressing this issue into > his tree yesterday. Can you please retest against current git ? Looks like the problem is fixed in current git for me. Thanks! ps. The description about vaio not resuming without key pressing matches what I was seeing here on thinkpad z60m, too. > tglx -- Arkadiusz Miśkiewicz PLD/Linux Team arekm / maven.pl http://ftp.pld-linux.org/ ^ permalink raw reply [flat|nested] 7+ messages in thread
[parent not found: <200709172251.07769.arekm@maven.pl>]
* Re: [3/3] 2.6.23-rc6: known regressions v2 [not found] ` <200709172251.07769.arekm@maven.pl> @ 2007-09-17 21:03 ` Thomas Gleixner [not found] ` <1190063028.2995.53.camel@chaos> 1 sibling, 0 replies; 7+ messages in thread From: Thomas Gleixner @ 2007-09-17 21:03 UTC (permalink / raw) To: Arkadiusz Miskiewicz Cc: Soeren Sonnenburg, Michal Piotrowski, Thomas Voegtle, LKML, Andrew Morton, Linus Torvalds, linux-pm On Mon, 2007-09-17 at 22:51 +0200, Arkadiusz Miskiewicz wrote: > > > clockevents: fix resume logic > > > > Linus pulled a series of patches which are addressing this issue into > > his tree yesterday. Can you please retest against current git ? > > Looks like the problem is fixed in current git for me. Thanks! Thanks for testing. > ps. The description about vaio not resuming without key pressing matches what > I was seeing here on thinkpad z60m, too. Sigh, there were several subtle reason why you would need to press keys during resume. The one you are referring to is the one which is the most obscure. It would be nice if you could revert that particular one and check whether it still works on your box. tglx ^ permalink raw reply [flat|nested] 7+ messages in thread
[parent not found: <1190063028.2995.53.camel@chaos>]
* Re: [3/3] 2.6.23-rc6: known regressions v2 [not found] ` <1190063028.2995.53.camel@chaos> @ 2007-09-18 7:07 ` Soeren Sonnenburg 0 siblings, 0 replies; 7+ messages in thread From: Soeren Sonnenburg @ 2007-09-18 7:07 UTC (permalink / raw) To: Thomas Gleixner Cc: Arkadiusz Miskiewicz, Thomas Voegtle, LKML, Andrew Morton, Linus Torvalds, linux-pm, Michal Piotrowski On Mon, 2007-09-17 at 23:03 +0200, Thomas Gleixner wrote: > On Mon, 2007-09-17 at 22:51 +0200, Arkadiusz Miskiewicz wrote: > > > > clockevents: fix resume logic > > > > > > Linus pulled a series of patches which are addressing this issue into > > > his tree yesterday. Can you please retest against current git ? > > > > Looks like the problem is fixed in current git for me. Thanks! > > Thanks for testing. I can confirm that the problem is fixed for me too in current git when using the free avivo driver (with the binary only fglrx driver the machine just hangs on resume or even sometimes on sleep). So it might be worth to purposely keep that such that people transit from fglrx to the free avivo/radeonhd drivers. Anyway s2ram with avivo takes 2-3 sec to suspend and 4-5 for resume (when fglrx worked it was more in the 10-20 secs). Soeren. -- Sometimes, there's a moment as you're waking, when you become aware of the real world around you, but you're still dreaming. ^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2007-09-18 7:07 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <46EB3EF8.6040103@googlemail.com>
2007-09-15 2:29 ` [3/3] 2.6.23-rc6: known regressions v2 Michal Piotrowski
2007-09-15 18:20 ` Rafael J. Wysocki
[not found] ` <200709152020.33179.rjw@sisk.pl>
2007-09-17 19:44 ` Arkadiusz Miskiewicz
[not found] ` <200709172144.43761.arekm@maven.pl>
2007-09-17 19:47 ` Thomas Gleixner
[not found] ` <1190058463.2995.14.camel@chaos>
2007-09-17 20:51 ` Arkadiusz Miskiewicz
[not found] ` <200709172251.07769.arekm@maven.pl>
2007-09-17 21:03 ` Thomas Gleixner
[not found] ` <1190063028.2995.53.camel@chaos>
2007-09-18 7:07 ` Soeren Sonnenburg
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox