From: bugme-daemon@bugzilla.kernel.org
To: cpufreq@www.linux.org.uk
Subject: [Bug 11139] New: warning in cpufreq.c on E450
Date: Mon, 21 Jul 2008 15:02:44 -0700 (PDT) [thread overview]
Message-ID: <bug-11139-3570@http.bugzilla.kernel.org/> (raw)
http://bugzilla.kernel.org/show_bug.cgi?id=11139
Summary: warning in cpufreq.c on E450
Product: Power Management
Version: 2.5
KernelVersion: 2.6.26
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: cpufreq
AssignedTo: cpufreq@www.linux.org.uk
ReportedBy: marvin@mydatex.cz
Latest working kernel version: 2.6.24.2
Earliest failing kernel version: 2.6.26
Distribution: Debian Sid
Hardware Environment: Sun E450/2x CPU 400Mhz/1GB Ram
Software Environment: Sid
Problem Description:
After I compile 2.6.26 an boots I get this:
------------[ cut here ]------------
WARNING: at drivers/cpufreq/cpufreq.c:1391
cpufreq_register_notifier+0x50/0x60()
Modules linked in:
Call Trace:
[0000000000605270] cpufreq_register_notifier+0x58/0x60
[00000000007708e0] start_kernel+0x1f0/0x324
[0000000000680e08] auxio_probe+0x0/0xe8
[0000000000000000] 0x8
---[ end trace 139ce121c98e96c9 ]---
Steps to reproduce:
Compile kernel with cpufreq enabled and boot.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2008-07-21 22:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-21 22:02 bugme-daemon [this message]
2008-07-21 22:44 ` [Bug 11139] warning in cpufreq.c on E450 bugme-daemon
2008-07-22 23:45 ` bugme-daemon
2008-07-23 0:38 ` bugme-daemon
2008-07-23 9:04 ` bugme-daemon
2008-07-23 10:54 ` bugme-daemon
2008-07-23 18:58 ` bugme-daemon
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=bug-11139-3570@http.bugzilla.kernel.org/ \
--to=bugme-daemon@bugzilla.kernel.org \
--cc=cpufreq@www.linux.org.uk \
/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.