From: Tilman Schmidt <tilman@imap.cc>
To: Dave Jones <davej@codemonkey.org.uk>, yakui.zhao@intel.com
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-acpi@vger.kernel.org
Subject: Re: [2.6.26-rc1] WARNING: at drivers/base/sys.c:183
Date: Mon, 12 May 2008 22:57:39 +0200 [thread overview]
Message-ID: <4828AF43.9030608@imap.cc> (raw)
In-Reply-To: <20080511184658.GA2087@codemonkey.org.uk>
[-- Attachment #1: Type: text/plain, Size: 2853 bytes --]
Am 11.05.2008 20:46 schrieb Dave Jones:
>
> > May 11 19:32:44 xenon kernel: [ 29.607563] sysdev: class cpu: driver (c0439804) has already been registered to a class, something is wrong, but will forge on!
> > May 11 19:32:44 xenon kernel: [ 29.611835] ------------[ cut here ]------------
> > May 11 19:32:44 xenon kernel: [ 29.616182] WARNING: at drivers/base/sys.c:183 sysdev_driver_register+0x59/0xf2()
> > May 11 19:32:44 xenon kernel: [ 29.622037] Modules linked in: acpi_cpufreq(+) speedstep_lib microcode firmware_class loop osst st sr_mod cdrom pata_acpi bas_gigaset snd_hda_intel gigaset isdn snd_pcm rtc_cmos ata_generic aic7xxx snd_timer rtc_core usblp snd slhc ohci1394 pata_marvell thermal ieee1394 rtc_lib i2c_i801 parport_pc intel_agp processor soundcore crc_ccitt iTCO_wdt button scsi_transport_spi iTCO_vendor_support parport snd_page_alloc agpgart i2c_core sg ext3 jbd mbcache linear usbhid hid sd_mod ahci libata uhci_hcd ehci_hcd scsi_mod dock usbcore dm_snapshot dm_mod
> > May 11 19:32:44 xenon kernel: [ 29.648305] Pid: 2860, comm: modprobe Not tainted 2.6.26-rc1-testing #1
> > May 11 19:32:44 xenon kernel: [ 29.653156] [<c0129d09>] warn_on_slowpath+0x41/0x6d
> > May 11 19:32:44 xenon kernel: [ 29.658026] [<c0120032>] ? push_rt_task+0xb1/0x1ab
> > May 11 19:32:44 xenon kernel: [ 29.664013] [<c012a75a>] ? vprintk+0x3a5/0x3c5
> > May 11 19:32:44 xenon kernel: [ 29.670995] [<c010b7a4>] ? native_sched_clock+0xe0/0xff
> > May 11 19:32:44 xenon kernel: [ 29.675849] [<c010b7a4>] ? native_sched_clock+0xe0/0xff
> > May 11 19:32:44 xenon kernel: [ 29.680678] [<c0143881>] ? put_lock_stats+0xd/0x21
> > May 11 19:32:44 xenon kernel: [ 29.685465] [<c012a78f>] ? printk+0x15/0x17
> > May 11 19:32:44 xenon kernel: [ 29.690406] [<c026a57a>] sysdev_driver_register+0x59/0xf2
> > May 11 19:32:44 xenon kernel: [ 29.696845] [<c02a8fe3>] cpufreq_register_driver+0x80/0xfc
> > May 11 19:32:44 xenon kernel: [ 29.701892] [<faafe034>] acpi_cpufreq_init+0x34/0x3a [acpi_cpufreq]
> > May 11 19:32:44 xenon kernel: [ 29.708279] [<c014d441>] sys_init_module+0x1883/0x1a34
> > May 11 19:32:44 xenon kernel: [ 29.713176] [<c0106b63>] sysenter_past_esp+0x78/0xd1
> > May 11 19:32:44 xenon kernel: [ 29.718586] =======================
> > May 11 19:32:44 xenon kernel: [ 29.723414] ---[ end trace da2515dc0122d0b1 ]---
>
> And then we freak out when we init the next cpufreq module, acpi-cpufreq, which gets further
> and tries to actually get registered.
>
> I don't really understand what's happening that makes sysfs so unhappy.
> I guess if we had a clue what driver 'c0439804' was me might have some clues.
> What symbols are near that address in /proc/kallsyms ?
According to /proc/kallsyms, c0439804 = cpufreq_sysdev_driver.
HTH
T.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 254 bytes --]
next prev parent reply other threads:[~2008-05-12 20:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-11 18:18 [2.6.26-rc1] WARNING: at drivers/base/sys.c:183 Tilman Schmidt
2008-05-11 18:46 ` Dave Jones
2008-05-12 20:57 ` Tilman Schmidt [this message]
2008-05-11 20:24 ` Carlos R. Mafra
2008-05-12 22:57 ` Tilman Schmidt
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=4828AF43.9030608@imap.cc \
--to=tilman@imap.cc \
--cc=davej@codemonkey.org.uk \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yakui.zhao@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.