https://bugzilla.kernel.org/show_bug.cgi?id=50681


Len Brown <l...@kernel.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |NEEDINFO
                 CC|                            |acpi-bugzilla@lists.sourcef
                   |                            |orge.net
         AssignedTo|acpi_power-processor@kernel |rui.zh...@intel.com
                   |-bugs.osdl.org              |
            Summary|kernel BUG at               |kernel BUG at
                   |kernel/sched/core.c:1654    |kernel/sched/core.c:1654 -
                   |                            |acpi_processor_set_throttli
                   |                            |ng() - HP Elitebook
                   |                            |8530w/30E7




--- Comment #2 from Len Brown <l...@kernel.org>  2012-11-20 03:04:34 ---
We appear to be failing upon a thermal event
when we try to throttle the processor.
If this is the case, then it is likely that your system
will fail more frequently when it is hot and/or under a
very heavy workload (rather than at random).

Can you reproduce this using an upstream kernel,
say 3.7?  Was this problem absent from 3.6.0?

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are watching the assignee of the bug.

------------------------------------------------------------------------------
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
_______________________________________________
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla

Reply via email to