public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Ian Pilcher <i.pilcher-Wuw85uim5zDR7s880joybQ@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: [Fwd: Re: Plea for help]
Date: Fri, 02 Jan 2004 23:27:14 -0600	[thread overview]
Message-ID: <3FF652B2.3080004@comcast.net> (raw)

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

             reply	other threads:[~2004-01-03  5:27 UTC|newest]

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

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3FF652B2.3080004@comcast.net \
    --to=i.pilcher-wuw85uim5zdr7s880joybq@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox