From: Mike Galbraith <efault@gmx.de>
To: Ingo Molnar <mingo@elte.hu>
Cc: Len Brown <lenb@kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: WARNING: at drivers/base/sys.c:183 sysdev_driver_register+0x7a
Date: Tue, 22 Apr 2008 11:04:26 +0200 [thread overview]
Message-ID: <1208855066.4695.17.camel@marge.simson.net> (raw)
In-Reply-To: <20080422075357.GA15651@elte.hu>
On Tue, 2008-04-22 at 09:53 +0200, Ingo Molnar wrote:
> hi Len,
>
> randconfig boot testing found this new debug warning message in the
> syslog:
Ditto with Q6600 and v2.6.25-3410-g8075014.
[ 28.360968] sysdev: class cpu: driver (ffffffff80542a70) has already been registered to a class, something is wrong, but will forge on!
[ 28.379718] ------------[ cut here ]------------
[ 28.387748] WARNING: at drivers/base/sys.c:183 sysdev_driver_register+0x75/0x12c()
[ 28.398816] Modules linked in: acpi_cpufreq(+) snd_pcm_oss snd_mixer_oss snd_seq microcode snd_seq_device nls_iso8859_1 nls_cp437 vfat fat fuse loop dm_mod tda1004x saa7134_dvb videobuf_dvb dvb_core tuner tea5767 tda8290 tda827x tuner_xc2028 tda9887 tuner_simple mt20xx tea5761 snd_hda_intel saa7134 firewire_ohci snd_pcm firewire_core compat_ioctl32 crc_itu_t videodev snd_timer v4l1_compat snd_page_alloc snd_hwdep v4l2_common snd videobuf_dma_sg ohci1394 videobuf_core usbhid usb_storage e1000e rtc_cmos ieee1394 rtc_core ir_kbd_i2c hid iTCO_wdt sr_mod soundcore ir_common rtc_lib tveeprom button i2c_i801 serio_raw cdrom intel_agp ff_memless sg i2c_core iTCO_vendor_support ehci_hcd uhci_hcd sd_mod usbcore edd ext3 mbcache jbd fan ahci libata scsi_mod dock thermal processor
[ 28.514728] Pid: 2910, comm: modprobe Not tainted 2.6.26-smp #4
[ 28.525112]
[ 28.525113] Call Trace:
[ 28.537784] [<ffffffff802327b3>] warn_on_slowpath+0x58/0x6b
[ 28.547864] [<ffffffff80233595>] ? printk+0x67/0x69
[ 28.557169] [<ffffffffa000387a>] ? :processor:acpi_processor_preregister_performance+0x40f/0x421
[ 28.570438] [<ffffffff803701ff>] sysdev_driver_register+0x75/0x12c
[ 28.581048] [<ffffffff80392ab0>] cpufreq_register_driver+0x95/0x12c
[ 28.591770] [<ffffffffa00ea03f>] :acpi_cpufreq:acpi_cpufreq_init+0x3f/0x41
[ 28.603226] [<ffffffff802543a0>] sys_init_module+0x19db/0x1b08
[ 28.614176] [<ffffffff8028dec3>] ? vfs_read+0xab/0x154
[ 28.624319] [<ffffffff8020c01b>] system_call_after_swapgs+0x7b/0x80
[ 28.624326]
[ 28.624328] ---[ end trace a40285f696d317dc ]---
next prev parent reply other threads:[~2008-04-22 9:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-22 7:53 WARNING: at drivers/base/sys.c:183 sysdev_driver_register+0x7a Ingo Molnar
2008-04-22 9:04 ` Mike Galbraith [this message]
2008-05-06 22:39 ` Rafael J. Wysocki
2008-05-07 6:16 ` Mike Galbraith
2008-05-07 18:56 ` Rafael J. Wysocki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1208855066.4695.17.camel@marge.simson.net \
--to=efault@gmx.de \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox