[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87k5i8hrmk.fsf@duaron.myhome.or.jp>
Date: Tue, 06 May 2008 15:29:55 +0900
From: OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>
To: "Yinghai Lu" <yhlu.kernel@...il.com>
Cc: Greg KH <gregkh@...e.de>,
Linus Torvalds <torvalds@...ux-foundation.org>,
"Ingo Molnar" <mingo@...e.hu>, "Len Brown" <lenb@...nel.org>,
"linux-kernel\@vger.kernel.org" <linux-kernel@...r.kernel.org>,
linux-acpi <linux-acpi@...r.kernel.org>
Subject: Re: acpi_cpu_freq_init warning...
> calling acpi_cpufreq_init+0x0/0x68()
> sysdev: class cpu: driver (ffffffff80da0110) has already been
> registered to a class, something is wrong, but will forge on!
> ------------[ cut here ]------------
> WARNING: at drivers/base/sys.c:183 sysdev_driver_register+0x82/0x150()
> Modules linked in:
> Pid: 1, comm: swapper Not tainted
> 2.6.26-rc1-sched-devel.git-x86-latest.git-00485-g253148c-dirty #333
I've seen this too. The following patch seems to work for me.
--
OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>
[PATCH] Fix bogus warning in sysdev_driver_register()
if ((drv->entry.next != drv->entry.prev) ||
(drv->entry.next != NULL)) {
warns list_empty(&drv->entry).
Signed-off-by: OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>
---
drivers/base/sys.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN drivers/base/sys.c~fix-sys-bogus-warning drivers/base/sys.c
--- linux-2.6/drivers/base/sys.c~fix-sys-bogus-warning 2008-05-06 14:30:42.000000000 +0900
+++ linux-2.6-hirofumi/drivers/base/sys.c 2008-05-06 14:30:45.000000000 +0900
@@ -175,7 +175,7 @@ int sysdev_driver_register(struct sysdev
}
/* Check whether this driver has already been added to a class. */
- if ((drv->entry.next != drv->entry.prev) ||
+ if ((drv->entry.next != drv->entry.prev) &&
(drv->entry.next != NULL)) {
printk(KERN_WARNING "sysdev: class %s: driver (%p) has already"
" been registered to a class, something is wrong, but "
_
--
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