Messages in this thread | | | From | "Rafael J. Wysocki" <> | Subject | Re: 2.6.13-rc3-mm3 | Date | Thu, 28 Jul 2005 23:40:57 +0200 |
| |
On Thursday, 28 of July 2005 21:16, Andrew Morton wrote: > > "Rafael J. Wysocki" <rjw@sisk.pl> wrote: > > > > There are two problems with the compilation of arch/x86_64/kernel/nmi.c. > > Thanks. > > > --- linux-2.6.13-rc3-mm3/arch/x86_64/kernel/nmi.c 2005-07-28 21:05:53.000000000 +0200 > > +++ patched/arch/x86_64/kernel/nmi.c 2005-07-28 18:58:02.000000000 +0200 > > @@ -152,8 +152,10 @@ int __init check_nmi_watchdog (void) > > > > printk(KERN_INFO "testing NMI watchdog ... "); > > > > +#ifdef CONFIG_SMP > > if (nmi_watchdog == NMI_LOCAL_APIC) > > smp_call_function(nmi_cpu_busy, (void *)&endflag, 0, 0); > > +#endif > > > > for (cpu = 0; cpu < NR_CPUS; cpu++) > > counts[cpu] = cpu_pda[cpu].__nmi_count; > > This bit is no longer needed, since > alpha-fix-statement-with-no-effect-warnings.patch got dropped.
OK
BTW, -mm3 works fine for me on two AMD64 boxes except for one thing: On Asus L5D, if I resume the box from disk on battery power (ie the box is started on battery power and resumes from disk), it hangs solid right after copying the image (100% of the time). If it is resumed on AC power, everything is fine.
Well, -mm1[1-2] did the same thing so I think I'll create a Bugzilla entry and start a binary search. :-( The -git[5-9] kernels are not affected by this issue.
Greets, Rafael
PS Could you please tell me how I can figure out the order in which the individual patches in -mm have been applied?
-- - Would you tell me, please, which way I ought to go from here? - That depends a good deal on where you want to get to. -- Lewis Carroll "Alice's Adventures in Wonderland" - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |