http://bugzilla.kernel.org/show_bug.cgi?id=10093
--- Comment #28 from [EMAIL PROTECTED] 2008-04-04 16:31 ---
Soeren,
Can you try
git + (patch in comment #13) + (patch in comment #26) + (patch in comment #27)
And see whether you still see the hang.
If you still see the hang
{
wha
http://bugzilla.kernel.org/show_bug.cgi?id=10093
--- Comment #27 from [EMAIL PROTECTED] 2008-04-04 16:27 ---
Created an attachment (id=15608)
--> (http://bugzilla.kernel.org/attachment.cgi?id=15608&action=view)
Remove poll idle from cpuidle
--
Configure bugmail: http://bugzilla.ke
http://bugzilla.kernel.org/show_bug.cgi?id=10093
--- Comment #26 from [EMAIL PROTECTED] 2008-04-04 16:26 ---
Created an attachment (id=15607)
--> (http://bugzilla.kernel.org/attachment.cgi?id=15607&action=view)
Add few debug printk in cpuidle
--
Configure bugmail: http://bugzilla.
http://bugzilla.kernel.org/show_bug.cgi?id=10093
--- Comment #25 from [EMAIL PROTECTED] 2008-04-03 23:58 ---
Created an attachment (id=15604)
--> (http://bugzilla.kernel.org/attachment.cgi?id=15604&action=view)
max.cstate=1 15 sec hang at ladder
--
Configure bugmail: http://bugzil
http://bugzilla.kernel.org/show_bug.cgi?id=10093
--- Comment #24 from [EMAIL PROTECTED] 2008-04-03 23:57 ---
No this was the dmesg for the *normal boot* with debug on the cmdline. It
always waits at ladder governor. I am attaching the max_cstate=1 15sec dmesg
now.
--
Configure bugm
http://bugzilla.kernel.org/show_bug.cgi?id=10093
--- Comment #23 from [EMAIL PROTECTED] 2008-04-03 23:51 ---
Was this the dmesg of the boot during which it waited for 15 sec?
If not, can you post the dmesg when that happens with max_cstate=1.
And also, exactly after what msg did it wa
http://bugzilla.kernel.org/show_bug.cgi?id=10093
--- Comment #22 from [EMAIL PROTECTED] 2008-04-03 23:36 ---
Created an attachment (id=15603)
--> (http://bugzilla.kernel.org/attachment.cgi?id=15603&action=view)
dmesg of normal boot with debug on
--
Configure bugmail: http://bugzil
http://bugzilla.kernel.org/show_bug.cgi?id=10093
--- Comment #21 from [EMAIL PROTECTED] 2008-04-03 23:35 ---
I've now booted with processor.max_cstate=1 - short hang was there again. I am
attaching the dmesg with debug on a normal boot.
--
Configure bugmail: http://bugzilla.kernel.
http://bugzilla.kernel.org/show_bug.cgi?id=10093
--- Comment #20 from [EMAIL PROTECTED] 2008-04-02 13:40 ---
I just recognized that it will continue booting whether I press a key or not.
It is just that it might wait for 5-10 seconds *sometimes* before continuing.
--
Configure bugm
http://bugzilla.kernel.org/show_bug.cgi?id=10093
--- Comment #19 from [EMAIL PROTECTED] 2008-03-31 10:12 ---
One more qn:
Can you boot with parameter "debug" and attach the dmesg output when the system
fully boots.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?ta
http://bugzilla.kernel.org/show_bug.cgi?id=10093
--- Comment #18 from [EMAIL PROTECTED] 2008-03-31 10:08 ---
Venkatesh,
I will do this experiment. Regarding the 3 hangs of comment #14: Yes they
always happened with the ladder governor message being last.
--
Configure bugmail: http
http://bugzilla.kernel.org/show_bug.cgi?id=10093
--- Comment #17 from [EMAIL PROTECTED] 2008-03-31 09:58 ---
Soeren,
With the patch from comment #13, can you try processor.max_cstate parameter
experiment again. With that patch applied, expectation is that it should never
hang with p
http://bugzilla.kernel.org/show_bug.cgi?id=10093
--- Comment #16 from [EMAIL PROTECTED] 2008-03-29 11:53 ---
It fixed #10117 but not #10093.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are on the
http://bugzilla.kernel.org/show_bug.cgi?id=10093
--- Comment #15 from [EMAIL PROTECTED] 2008-03-29 11:37 ---
I don't quite understand your comment. I _guess_ the patch didn't help?
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
--- You are receiving t
http://bugzilla.kernel.org/show_bug.cgi?id=10093
--- Comment #14 from [EMAIL PROTECTED] 2008-03-29 11:25 ---
I've applied this patch (using latest git) and rebooted >10 times. I did not
see #10117 to occur and the cpuidle bug (this bug) happened about 3 times.
However after waiting fo
http://bugzilla.kernel.org/show_bug.cgi?id=10093
--- Comment #13 from [EMAIL PROTECTED] 2008-03-28 16:05 ---
Patch : http://marc.info/?l=linux-kernel&m=120674502201007&w=4
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
--- You are receiving this mail b
http://bugzilla.kernel.org/show_bug.cgi?id=10093
--- Comment #12 from [EMAIL PROTECTED] 2008-03-24 14:39 ---
I've applied this patch and rebooted about 10 times and the hang seems gone...
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
--- You are recei
http://bugzilla.kernel.org/show_bug.cgi?id=10093
--- Comment #11 from [EMAIL PROTECTED] 2008-03-22 14:55 ---
Hmm.. There were only few CPUIDLE patches that went in after .24. We should be
able to check them individually. My first suspect is this patch. Can you remove
this change from
http://bugzilla.kernel.org/show_bug.cgi?id=10093
--- Comment #10 from [EMAIL PROTECTED] 2008-03-22 12:16 ---
I tried cstate=1 and it managed to get it to hang too...
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
--- You are receiving this mail because
http://bugzilla.kernel.org/show_bug.cgi?id=10093
--- Comment #9 from [EMAIL PROTECTED] 2008-03-21 15:16 ---
Does
processor.max_cstate=2
or
processor.max_cstate=1
boot option help?
(Note ACPI->PROCESSOR needs to be configured as "in kernel" and not as module
for the above boot options
http://bugzilla.kernel.org/show_bug.cgi?id=10093
--- Comment #8 from [EMAIL PROTECTED] 2008-03-21 15:16 ---
Does
processor.max_cstate=2
or
processor.max_cstate=1
boot option help?
(Note ACPI->PROCESSOR needs to be configured as "in kernel" and not as module
for the above boot options
http://bugzilla.kernel.org/show_bug.cgi?id=10093
--- Comment #7 from [EMAIL PROTECTED] 2008-03-21 08:30 ---
Created an attachment (id=15374)
--> (http://bugzilla.kernel.org/attachment.cgi?id=15374&action=view)
kernel config
--
Configure bugmail: http://bugzilla.kernel.org/userpref
http://bugzilla.kernel.org/show_bug.cgi?id=10093
--- Comment #6 from [EMAIL PROTECTED] 2008-03-21 08:29 ---
always with cpuidle: using governor
(I think ladder) line.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
--- You are receiving this mail becau
http://bugzilla.kernel.org/show_bug.cgi?id=10093
--- Comment #5 from [EMAIL PROTECTED] 2008-03-21 08:08 ---
Does it hang at a specific point during boot? Or at various times?
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
--- You are receiving this mai
http://bugzilla.kernel.org/show_bug.cgi?id=10093
--- Comment #4 from [EMAIL PROTECTED] 2008-03-21 07:55 ---
I cannot attach the config (as bugzilla displays an internal error) so I am
sending it to Venkatesh directly.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?t
http://bugzilla.kernel.org/show_bug.cgi?id=10093
--- Comment #3 from [EMAIL PROTECTED] 2008-03-21 07:50 ---
OK, I am just back from vacation and tried current git
457fb605834504af294916411be128a9b21fc3f6.
The CONFIG_CPU_IDLE=y hang is still there and yes it worked all fine with
2.6.2
http://bugzilla.kernel.org/show_bug.cgi?id=10093
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #2 from [E
http://bugzilla.kernel.org/show_bug.cgi?id=10093
[EMAIL PROTECTED] changed:
What|Removed |Added
Summary|2.6.25-current-git hangs on |2.6.25-current-git hangs on
28 matches
Mail list logo
