Messages in this thread | | | Date | Thu, 9 Mar 2006 05:46:44 -0800 | From | "Miles Lane" <> | Subject | Re: 2.6.16-rc5-mm3 -- BUG: sleeping function called from invalid context at include/linux/rwsem.h:43 in_atomic():0, irqs_disabled():1 |
| |
On 3/9/06, Rafael J. Wysocki <rjw@sisk.pl> wrote: > On Thursday 09 March 2006 11:32, Andrew Morton wrote: > > "Miles Lane" <miles.lane@gmail.com> wrote: > > > > > > Apologies. This bug caused my video to get messed up. I was able to > > > run Gnome, but the apps weren't rendering correctly, so I couldn't be > > > sure my subject line was correct. > > > I would have edited out some of the context info, but that was tough > > > as well. Here's the BUG message by itself. Perhaps all the dmesg > > > output in the previous message will be helpful. > > > As you can see in the dmesg output, I hit this by suspending and > > > resuming. I am running Fedora Core 5 Test 3 + all yum updates. > > > Andrew, the full dmesg output is in the LKML message with the subject > > > line set to "v". Let me know if you would like me to send it directly > > > to you. > > > > > > BUG: sleeping function called from invalid context at include/linux/rwsem.h:43 > > > in_atomic():0, irqs_disabled():1 > > > <c1003f81> show_trace+0xd/0xf <c100401b> dump_stack+0x17/0x19 > > > <c1015f77> __might_sleep+0x86/0x90 <c1024738> > > > blocking_notifier_call_chain+0x1b/0x4d > > > <c1183bb2> cpufreq_resume+0xf5/0x11d <c112b27c> __sysdev_resume+0x23/0x57 > > > <c112b3c9> sysdev_resume+0x19/0x4b <c112f736> device_power_up+0x8/0xf > > > <c1033339> swsusp_suspend+0x6e/0x8b <c1033918> pm_suspend_disk+0x51/0xf3 > > > <c10328c7> enter_state+0x53/0x1c1 <c1032abe> state_store+0x89/0x97 > > > <c108af00> subsys_attr_store+0x20/0x25 <c108b020> sysfs_write_file+0xb5/0xdc > > > <c1056578> vfs_write+0xab/0x154 <c1056aa3> sys_write+0x3b/0x60 > > > <c1002b43> syscall_call+0x7/0xb > > > PM: Image restored success > > > > ho-hum. That's swsusp insisting on running things which it shouldn't run > > with local interrupts disabled. > > Well, there seems to be a bug in cpufreq_resume which should not call > sleeping functions, because it's called with irqs disabled.
# CPU Frequency scaling # CONFIG_CPU_FREQ=y CONFIG_CPU_FREQ_TABLE=y CONFIG_CPU_FREQ_DEBUG=y CONFIG_CPU_FREQ_STAT=y CONFIG_CPU_FREQ_STAT_DETAILS=y # CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE=y CONFIG_CPU_FREQ_GOV_PERFORMANCE=m CONFIG_CPU_FREQ_GOV_POWERSAVE=m CONFIG_CPU_FREQ_GOV_USERSPACE=y CONFIG_CPU_FREQ_GOV_ONDEMAND=y CONFIG_CPU_FREQ_GOV_CONSERVATIVE=m
# # CPUFreq processor drivers # CONFIG_X86_ACPI_CPUFREQ=y CONFIG_X86_SPEEDSTEP_CENTRINO=y CONFIG_X86_SPEEDSTEP_CENTRINO_ACPI=y CONFIG_X86_SPEEDSTEP_CENTRINO_TABLE=y CONFIG_X86_SPEEDSTEP_ICH=y CONFIG_X86_SPEEDSTEP_SMI=y CONFIG_X86_P4_CLOCKMOD=y - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |