linux-kernel - Lockup with cpufreq that may be similar to recently fixed acpi

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1162037001.2465.14.camel@aurora.localdomain>
Date:	Sat, 28 Oct 2006 06:03:21 -0600
From:	"Trever L. Adams" <tadams-lists@...ealbox.com>
To:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Lockup with cpufreq that may be similar to recently fixed
	acpi_cpufreq

This may be a single vendor problem. I am having a difficult time
getting the vendor to respond. However, I have a dual core Turion laptop
which is locking up on resume from suspend (resume from hibernate now
works fine). Below is the DWARF2 trace back. It is showing a problem in
cpufreq_resume (if I read this correctly). I think this may be similar
to a problem that was recently fixed, that had the same symptoms, in
acpi_cpufreq. This is 2.6.18.

Oct 18 12:51:12 mysystem kernel: BUG: sleeping function called from
invalid
context at kernel/rwsem.c:20
Oct 18 12:51:12 mysystem kernel: in_atomic():0, irqs_disabled():1
Oct 18 12:51:12 mysystem kernel:  [<c04051db>] dump_trace+0x69/0x1af
Oct 18 12:51:12 mysystem kernel:  [<c0405339>] show_trace_log_lvl+0x18/0x2c
Oct 18 12:51:12 mysystem kernel:  [<c04058ed>] show_trace+0xf/0x11
Oct 18 12:51:12 mysystem kernel:  [<c04059ea>] dump_stack+0x15/0x17
Oct 18 12:51:12 mysystem kernel:  [<c0439446>] down_read+0x12/0x20
Oct 18 12:51:12 mysystem kernel:  [<c0431601>] blocking_notifier_call_chain+0xe/0x29
Oct 18 12:51:12 mysystem kernel:  [<c05a9798>] cpufreq_resume+0x118/0x135
Oct 18 12:51:12 mysystem kernel:  [<c0551440>] __sysdev_resume+0x20/0x53
Oct 18 12:51:12 mysystem kernel:  [<c0551583>] sysdev_resume+0x16/0x47
Oct 18 12:51:12 mysystem kernel:  [<c0555767>] device_power_up+0x5/0xa
Oct 18 12:51:12 mysystem kernel:  [<c04418fd>] suspend_enter+0x3b/0x44
Oct 18 12:51:12 mysystem kernel:  [<c0441a2c>] enter_state+0x126/0x176
Oct 18 12:51:12 mysystem kernel:  [<c0441b01>] state_store+0x85/0x99
Oct 18 12:51:12 mysystem kernel:  [<c04a5fe6>] subsys_attr_store+0x1e/0x22
Oct 18 12:51:14 mysystem kernel:  [<c04a60d9>] sysfs_write_file+0xa7/0xce
Oct 18 12:51:14 mysystem kernel:  [<c046f805>] vfs_write+0xa8/0x159
Oct 18 12:51:14 mysystem kernel:  [<c046fe32>] sys_write+0x41/0x67
Oct 18 12:51:14 mysystem kernel:  [<c0404013>] syscall_call+0x7/0xb
Oct 18 12:51:14 mysystem kernel: DWARF2 unwinder stuck at syscall_call+0x7/0xb
Oct 18 12:51:14 mysystem kernel: Leftover inexact backtrace:
Oct 18 12:51:14 mysystem kernel:  =======================

Thank you,
Trever Adams

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/