[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200804302100.26294.rjw@sisk.pl>
Date: Wed, 30 Apr 2008 21:00:25 +0200
From: "Rafael J. Wysocki" <rjw@...k.pl>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Len Brown <lenb@...nel.org>, torvalds@...ux-foundation.org,
linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-pm@...ts.linux-foundation.org
Subject: Re: [GIT PATCH] ACPI patches for 2.6.26-rc0
On Wednesday, 30 of April 2008, Andrew Morton wrote:
> On Wed, 30 Apr 2008 14:20:11 -0400
> Len Brown <lenb@...nel.org> wrote:
>
> > Hi Linus,
> >
> > please pull from:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux-acpi-2.6.git release
> >
> > This batch is a proper super-set of the pull request I made a week ago.
> > It will update the files shown below.
> >
>
>
> I have four acpi-related reports here from 2.6.25-rcX-mmY. Can you please check
> that they were addressed? I don't recall seeing any feedback for any of
> them.
>
> Thanks.
>
>
>
>
>
> From: "Miles Lane" <miles.lane@...il.com>
> To: "Andrew Morton" <akpm@...ux-foundation.org>, LKML <linux-kernel@...r.kernel.org>, len.brown@...el.com
> Subject: 2.6.25-rc8-mm2 -- initcall acpi_init+0x0/0x216() returned with preemption imbalance
> Date: Fri, 11 Apr 2008 15:41:17 -0400
>
> Is this indicative of a kernel or hardware problem?
>
> [ 0.279606] ACPI: Using IOAPIC for interrupt routing
> [ 0.279789] initcall acpi_init+0x0/0x216() returned with preemption imbalance
> [ 0.330789] ACPI: PCI Root Bridge [PCI0] (0000:00)
>
>
>
> From: "Dave Young" <hidave.darkstar@...il.com>
> To: "Andrew Morton" <akpm@...ux-foundation.org>
> Cc: linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org, "Len Brown" <lenb@...nel.org>
> Subject: Re: 2.6.25-rc5-mm1
> Date: Wed, 12 Mar 2008 09:14:55 +0800
>
> Hi, I got the following lockdep warning:
> (add linux-acpi to cc)
>
> [ 0.097109] ACPI: Core revision 20070126
> [ 0.097282] INFO: trying to register non-static key.
> [ 0.097355] the code is fine but needs lockdep annotation.
> [ 0.097428] turning off the locking correctness validator.
> [ 0.097503] Pid: 0, comm: swapper Not tainted 2.6.25-rc5-mm1 #3
> [ 0.097578] [<c0127bf8>] ? printk+0x18/0x20
> [ 0.097716] [<c014b01c>] __lock_acquire+0x40c/0x760
> [ 0.097822] [<c0181ba0>] ? alloc_debug_processing+0xb0/0x140
> [ 0.097959] [<c014b969>] lock_acquire+0x79/0xb0
> [ 0.098063] [<c0140204>] ? down_trylock+0x14/0x40
> [ 0.098197] [<c03df9e8>] _spin_lock_irqsave+0x48/0xa0
> [ 0.098303] [<c0140204>] ? down_trylock+0x14/0x40
> [ 0.098436] [<c0140204>] down_trylock+0x14/0x40
> [ 0.098540] [<c027c7ea>] acpi_os_wait_semaphore+0x3e/0xb9
> [ 0.098647] [<c029263e>] acpi_ut_acquire_mutex+0x34/0x72
> [ 0.098753] [<c0289ab1>] acpi_ns_root_initialize+0x19/0x250
> [ 0.098859] [<c05453e6>] acpi_initialize_subsystem+0x42/0x64
> [ 0.098966] [<c0545725>] acpi_early_init+0x50/0xef
> [ 0.099070] [<c052b7f6>] start_kernel+0x1e6/0x250
> [ 0.099175] [<c052b1a0>] ? unknown_bootoption+0x0/0x130
> [ 0.099310] [<c052b008>] __init_begin+0x8/0x10
> [ 0.099414] =======================
>
>
>
> From: Randy Dunlap <randy.dunlap@...cle.com>
> To: Andrew Morton <akpm@...ux-foundation.org>
> Cc: linux-kernel@...r.kernel.org, len.brown@...el.com
> Subject: Re: 2.6.25-rc2-mm1 (build failure)
> Date: Sat, 16 Feb 2008 21:32:25 -0800
> Organization: Oracle Linux Eng.
> X-Mailer: Sylpheed 2.4.7 (GTK+ 2.8.10; x86_64-unknown-linux-gnu)
>
> On Sat, 16 Feb 2008 00:25:22 -0800 Andrew Morton wrote:
>
> >
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.25-rc2/2.6.25-rc2-mm1/
>
> When SMP=n, x86_64 build gets:
>
> arch/x86/kernel/built-in.o: In function `acpi_save_state_mem':
> (.text+0xfd7f): undefined reference to `setup_trampoline'
> make[1]: *** [.tmp_vmlinux1] Error 1
This code has already been merged via the x86 tree, with the problem fixed
IIRC (at least it hasn't been reported against the mainline so far).
Thanks,
Rafael
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists