From: bugme-daemon@bugzilla.kernel.org
To: cpufreq@www.linux.org.uk
Subject: [Bug 9549] New: [crash] kernel BUG at drivers/cpufreq/cpufreq.c:1060!
Date: Wed, 12 Dec 2007 10:33:38 -0800 (PST) [thread overview]
Message-ID: <bug-9549-3570@http.bugzilla.kernel.org/> (raw)
http://bugzilla.kernel.org/show_bug.cgi?id=9549
Summary: [crash] kernel BUG at drivers/cpufreq/cpufreq.c:1060!
Product: Power Management
Version: 2.5
KernelVersion: 2.6.24-rc4-git5
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: cpufreq
AssignedTo: cpufreq@www.linux.org.uk
ReportedBy: rjwysocki@sisk.pl
Subject : [crash] kernel BUG at drivers/cpufreq/cpufreq.c:1060!
Submitter : Ingo Molnar <mingo@elte.hu>
References : http://lkml.org/lkml/2007/12/12/52
Handled-By : Dave Jones <davej@redhat.com>
--
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:[~2007-12-12 18:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-12 18:33 bugme-daemon [this message]
2007-12-12 18:33 ` [Bug 9549] [crash] kernel BUG at drivers/cpufreq/cpufreq.c:1060! bugme-daemon
2007-12-12 18:34 ` bugme-daemon
2007-12-12 18:56 ` bugme-daemon
2007-12-21 0:09 ` 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-9549-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox