2007-10-23 15:55:25

by Thomas Meyer

[permalink] [raw]
Subject: kexec: gets stuck in acpi_idle_enter_bm with 0895e91d60ef9bdef426d1ce14bb94bd5875870d

i try to kexec from 0895e91d60ef9bdef426d1ce14bb94bd5875870d into
another (older) commit kernel after 2.6.23 (bisect) and the kernel gets
stuck:

PID: 0, comm: swapper
EIP is at acpi_idle_enter_bm+0x258/0x2fa (processor)

-> cpuidle_idle_call+0x5c/0x81
-> cpuidle_idle_call+0x0/0x81
-> cpu_idle+0xab/0xcc
-> start_kernel+0x329/0x331
-> unknown_bootoption+0x0/0x196


2007-10-23 16:14:59

by Thomas Meyer

[permalink] [raw]
Subject: Re: kexec: gets stuck in acpi_idle_enter_bm with 0895e91d60ef9bdef426d1ce14bb94bd5875870d

Thomas Meyer schrieb:
> i try to kexec from 0895e91d60ef9bdef426d1ce14bb94bd5875870d into
> another (older) commit kernel after 2.6.23 (bisect) and the kernel gets
> stuck:
>
> PID: 0, comm: swapper
> EIP is at acpi_idle_enter_bm+0x258/0x2fa (processor)
>
> -> cpuidle_idle_call+0x5c/0x81
> -> cpuidle_idle_call+0x0/0x81
> -> cpu_idle+0xab/0xcc
> -> start_kernel+0x329/0x331
> -> unknown_bootoption+0x0/0x196
>
>
>
2.6.23-current-git:

http://m3y3r.de/bilder/2.6.23-rc0-kexec-stuck.jpg

this seems also to happen in 2.6.23:

http://m3y3r.de/bilder/2.6.23-kexec-stuck.jpg

2007-10-23 16:35:18

by Thomas Meyer

[permalink] [raw]
Subject: Re: kexec: gets stuck in acpi_idle_enter_bm with 0895e91d60ef9bdef426d1ce14bb94bd5875870d

Thomas Meyer schrieb:
> Thomas Meyer schrieb:
>
>> i try to kexec from 0895e91d60ef9bdef426d1ce14bb94bd5875870d into
>> another (older) commit kernel after 2.6.23 (bisect) and the kernel gets
>> stuck:
>>
>> PID: 0, comm: swapper
>> EIP is at acpi_idle_enter_bm+0x258/0x2fa (processor)
>>
>> -> cpuidle_idle_call+0x5c/0x81
>> -> cpuidle_idle_call+0x0/0x81
>> -> cpu_idle+0xab/0xcc
>> -> start_kernel+0x329/0x331
>> -> unknown_bootoption+0x0/0x196
>>
>>
>>
>>
> 2.6.23-current-git:
>
> http://m3y3r.de/bilder/2.6.23-rc0-kexec-stuck.jpg
>
> this seems also to happen in 2.6.23:
>
> http://m3y3r.de/bilder/2.6.23-kexec-stuck.jpg
>
>
>
I am sorry again.

The gentoo reboot runlevel sequence seem to stuck somewhere and who. so
the kernel is actually idleing...

This is very likely not a kernel problem.

sorry for the disturbance!