Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1945947AbXBBQfO (ORCPT ); Fri, 2 Feb 2007 11:35:14 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1945953AbXBBQfO (ORCPT ); Fri, 2 Feb 2007 11:35:14 -0500 Received: from wx-out-0506.google.com ([66.249.82.228]:27646 "EHLO wx-out-0506.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1945947AbXBBQfN (ORCPT ); Fri, 2 Feb 2007 11:35:13 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=tb9vFaQkTTr+/O9ZAd3bmBiWP+UE4KweAE2QEH0921abchyoNPukd2FVjtg8yC0TJcUjgpIGGCgmC29/gIV0jR0aH0I1e35K67WIBXk+wuQG99L0Kgadhu6mmthl0vVepxWEs0mlWktkD58kW8JhynerTAdY9ghtGyWxv7dEaVI= Message-ID: <3877989d0702020835i327ad339u509454ab55a3e0d5@mail.gmail.com> Date: Sat, 3 Feb 2007 00:35:12 +0800 From: "Luming Yu" To: "Henri Hunnekens" Subject: Re: kernel BUG: loading acpi_cpufreq causes segmentation fault with 2.6.20-RC7-RT3 Cc: linux-kernel@vger.kernel.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3075 Lines: 69 Please try a base kernel to verify if it is rt patch issue. > kernel BUG at drivers/acpi/osl.c:373! I never see this before. Please post dmesg && acpidump output. (It would be better to post them on bugzilla ). My guess is that ACPI is just disabled. But if acpi is disabled, acpi_cpufreq module shouldn't get installed. On 2/2/07, Henri Hunnekens wrote: > Loading the acpi_cpufreq module causes a segmentation fault with > kernel version 2.6.20-rt7-rt3. > > Does anyone know how to fix this? > > Henri > > kernel BUG at drivers/acpi/osl.c:373! > invalid opcode: 0000 [#1] > PREEMPT SMP > Modules linked in: acpi_cpufreq freq_table cap_over commoncap i2c_dev uhci_hcd i > 2c_i801 i2c_core ehci_hcd > CPU: 0 > EIP: 0060:[] Not tainted VLI > EFLAGS: 00010297 (2.6.20-rc7-rt3 #1) > EIP is at acpi_os_write_port+0x2d/0x36 > eax: 00000001 ebx: 00000832 ecx: 00000001 edx: 00000001 > esi: de561920 edi: 00000000 ebp: dd3d1c90 esp: dd3d1c8c > ds: 007b es: 007b ss: 0068 preempt: 00000001 > Process modprobe (pid: 2543, ti=dd3d0000 task=de656660 task.ti=dd3d0000) > Stack: 00000000 dd3d1cf0 e0074455 00000001 dd3d1ce0 c039bff2 dcf84940 00000000 > df40d000 00000001 00000001 dd3d1cd0 c016612f 00000002 00000001 dc010832 > 00000001 00000000 002cc108 002cc108 c03f1302 00000000 df2d0d80 e00742d0 > Call Trace: > [] show_trace_log_lvl+0x1a/0x30 > [] show_stack_log_lvl+0xb8/0xf0 > [] show_registers+0x1e0/0x300 > [] die+0x125/0x260 > [] do_trap+0x82/0xd0 > [] do_invalid_op+0x97/0xb0 > [] error_code+0x7c/0x84 > [] acpi_cpufreq_target+0x185/0x290 [acpi_cpufreq] > [] __cpufreq_driver_target+0x3f/0x50 > [] cpufreq_governor_performance+0x1e/0x30 > [] __cpufreq_governor+0x24/0xd0 > [] __cpufreq_set_policy+0xeb/0x140 > [] cpufreq_set_policy+0x4e/0x80 > [] cpufreq_add_dev+0x31a/0x3e0 > [] sysdev_driver_register+0x59/0xa0 > [] cpufreq_register_driver+0x67/0x100 > [] acpi_cpufreq_init+0x9d/0xa4 [acpi_cpufreq] > [] sys_init_module+0x137/0x1b90 > [] syscall_call+0x7/0xb > ======================= > Code: f9 10 89 e5 53 89 c3 89 d0 74 12 83 f9 20 74 16 83 f9 08 75 16 0f b6 c2 89 > da ee eb 12 0f b7 c2 89 da 66 ef eb 09 89 da ef eb 04 <0f> 0b eb fe 5b 31 c0 5d > c3 55 89 e5 5d c3 55 85 c0 89 e5 89 c1 > EIP: [] acpi_os_write_port+0x2d/0x36 SS:ESP 0068:dd3d1c8c > Segmentation fault > - > 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/ > - 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/