All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alvaro Lopes <alvieboy@alvie.com>
To: "Grover, Andrew" <andrew.grover@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [ACPI] 2.5.58 hangs at boot
Date: Thu, 23 Jan 2003 15:35:42 +0000	[thread overview]
Message-ID: <3E300BCE.9080909@alvie.com> (raw)
In-Reply-To: <F760B14C9561B941B89469F59BA3A847137F76@orsmsx401.jf.intel.com>

Hi Andrew, all.

I have the same problem here with 2.5.57/8/9 with a Toshiba 2410 Laptop. 
Very funny also. The exact system lockup varies according to printk's 
inserted in the code.

>Can you stick a printk in ev_sci_handler and see if that's being called
>repeatedly?
>
Yes it is.

do_IRQ() is called for irq line 9, calls handle_IRQ_event() which then 
calls acpi_irq and finally ev_sci_handler().

This repeats 'ad infinitum'. Didn't wait for more than a few minutes, 
but it looks like it will.

The interrupts are handled at acpi_ev_gpe_detect (), which returns 1. At 
this point in_irq() returns 0x00010000 (or 0x00001000, don't have a 
serial console :/)

Any ideas ??? Need some more debugging ?

Funny enough, without the printk's it usually hangs at 
create_workqueue(), while doing wait_for_completion() - seems the kernel 
thread simply fails to get run.

-- 

Álvaro Lopes 
---------------------
A .sig is just a .sig



  parent reply	other threads:[~2003-01-23 15:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-16 21:38 [ACPI] 2.5.58 hangs at boot Grover, Andrew
2003-01-16 21:38 ` Grover, Andrew
     [not found] ` <F760B14C9561B941B89469F59BA3A847137F76-sBd4vmA9Se4Lll3ZsUKC9FDQ4js95KgL@public.gmane.org>
2003-01-16 22:26   ` Michael Dreher
2003-01-23 15:35 ` Alvaro Lopes [this message]
     [not found]   ` <3E300BCE.9080909-JkNoWtNHh5AAvxtiuMwx3w@public.gmane.org>
2003-01-26 13:59     ` [ACPI] " Alvaro Lopes
2003-01-26 13:59       ` Alvaro Lopes
  -- strict thread matches above, loose matches on Subject: below --
2003-01-16 21:15 Michael Dreher

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=3E300BCE.9080909@alvie.com \
    --to=alvieboy@alvie.com \
    --cc=andrew.grover@intel.com \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.