public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
* [Fwd: Re: Plea for help]
@ 2004-01-03  5:27 Ian Pilcher
  0 siblings, 0 replies; 4+ messages in thread
From: Ian Pilcher @ 2004-01-03  5:27 UTC (permalink / raw)
  Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f

Yu, Luming wrote:
> 
> Since I cannot reporduce it on my side. Would you please dig into 
> function acpi_ev_create_gpe_block.
> 

Before I sent the first message in this thread, I added a bunch of
printks to this function.  They ended up mixed in with the panic, just
like the ACPI debugging messages.

I'm not sure what else I can do to "dig into" it.

> 
>>And just for grins and giggles, I tried booting with 'idle=poll'.  Sure
>>enough, no panic.
> 
> 
> I'm confused! 
> 

My guess, and that's all it can be, is that the transition to ACPI mode
does something that causes the idle thread on the other processor to
crash.  Perhaps a spurious interrupt is being thrown, or an interrupt is
routed to the wrong processor.  (Is the behavior of a HLTed processor
that gets a misrouted interrupt different than that of a processor that
is polling?)

There certainly seems to be a timing sensitivity too.  Is there a kernel
mode sleep-like function that I could play with?

Thanks!

-- 
========================================================================
Ian Pilcher                                        i.pilcher-Wuw85uim5zDR7s880joybQ@public.gmane.org
========================================================================



-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click

^ permalink raw reply	[flat|nested] 4+ messages in thread

* RE: [Fwd: Re: Plea for help]
@ 2004-01-06  3:27 Yu, Luming
       [not found] ` <3ACA40606221794F80A5670F0AF15F8401720C7F-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
  0 siblings, 1 reply; 4+ messages in thread
From: Yu, Luming @ 2004-01-06  3:27 UTC (permalink / raw)
  To: Ian Pilcher; +Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f

>> 
>> Since I cannot reporduce it on my side. Would you please dig into 
>> function acpi_ev_create_gpe_block.
>> 
>Before I sent the first message in this thread, I added a bunch of
>printks to this function.  They ended up mixed in with the panic, just
>like the ACPI debugging messages.
>
>I'm not sure what else I can do to "dig into" it.

Maybe you need to file a tracker on bugzilla.kernel.org.
You can put anything you found to let us enjoy.
It's an effective  way.

> Perhaps a spurious interrupt is being thrown, or an interrupt is
>routed to the wrong processor.  (Is the behavior of a HLTed processor
>that gets a misrouted interrupt different than that of a processor that
>is polling?)

It's a hint.

>There certainly seems to be a timing sensitivity too.  Is there a
kernel
>mode sleep-like function that I could play with?

wait_event?


-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id\x1278&alloc_id371&op=click

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [Fwd: Re: Plea for help]
       [not found] ` <3ACA40606221794F80A5670F0AF15F8401720C7F-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
@ 2004-01-12  2:55   ` Ian Pilcher
  0 siblings, 0 replies; 4+ messages in thread
From: Ian Pilcher @ 2004-01-12  2:55 UTC (permalink / raw)
  To: Yu, Luming; +Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f

Yu, Luming wrote:
> 
> 
>>There certainly seems to be a timing sensitivity too.  Is there a
> 
> kernel
> 
>>mode sleep-like function that I could play with?
> 
> 
> wait_event?
> 

Can you point me to an example of using wait_event to "sleep" for a set
period of time?

Thanks!

-- 
========================================================================
Ian Pilcher                                        i.pilcher-Wuw85uim5zDR7s880joybQ@public.gmane.org
========================================================================



-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html

^ permalink raw reply	[flat|nested] 4+ messages in thread

* RE: [Fwd: Re: Plea for help]
@ 2004-01-12  6:11 Yu, Luming
  0 siblings, 0 replies; 4+ messages in thread
From: Yu, Luming @ 2004-01-12  6:11 UTC (permalink / raw)
  To: Ian Pilcher; +Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f

> 
> Can you point me to an example of using wait_event to "sleep" 
> for a set
> period of time?
> 

You need to init a timer for timing. Wait_event just let you sleep.
When timeout, function wake_up could be used to complete sleeping.


-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2004-01-12  6:11 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-01-03  5:27 [Fwd: Re: Plea for help] Ian Pilcher
  -- strict thread matches above, loose matches on Subject: below --
2004-01-06  3:27 Yu, Luming
     [not found] ` <3ACA40606221794F80A5670F0AF15F8401720C7F-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-01-12  2:55   ` Ian Pilcher
2004-01-12  6:11 Yu, Luming

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox