[+cc Bryan, Zhang] On Fri, Apr 19, 2013 at 8:51 AM, Scott Simpson <simpson1...@live.com> wrote: > Stack trace is here: http://www.flickr.com/photos/94373754@N06/8662259093/ > --
Hi Scott, This is an openSUSE bug, so you'll probably get more help there. I added a CC: for that, and you can look here as well: http://en.opensuse.org/openSUSE:Submitting_bug_reports Is this easy to reproduce? Do you know whether the same thing happens with an upstream kernel, e.g., v3.8 or v3.9-rc7? If it turns out that this bug still exists in the upstream kernel, Zhang will probably be interested in it. Transcribed from the screen shot: kernel BUG at /home/abuild/rpmbuild/BUILD/kernel-desktop-3.7.10/linux-3.7/kernel/sched/core.c:1465! Pid: 3742, comm: kworker/0:0 Not tainted 3.7.10-1.1-desktop #1 LENOVO 0768DCU/CAPELL VALLEY(NAPA) CRB Call Trace: schedule_timeout wait_for_common stop_one_cpu set_cpus_allowed_ptr acpi_processor_set_throttling thermal_zone_device_update process_one_work worker_thread kthread ret_from_kernel_thread kthread_create_on_node Kernel panic -- not syncing: Watchdog detected hard LOCKUP on cpu 1 Bjorn -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
