public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Ethan Glasser-Camp <glasse-IL7dBOYR4Vg@public.gmane.org>
To: "Yu, Luming" <luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Re: Oops during startup
Date: Wed, 2 Jun 2004 00:29:17 -0400	[thread overview]
Message-ID: <20040602042917.GA609@paladin> (raw)
In-Reply-To: <3ACA40606221794F80A5670F0AF15F840483B1C4-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1528 bytes --]

On Wed, Jun 02, 2004 at 11:17:57AM +0800, Yu, Luming wrote:
>  Please try kernel option: acpi_sci={ level | edge | high | low }
> 
> --Luming

None of the above resulted in any differences.

Yi Zhu wrote:
> But firstly could you provide whatever be seen to give us a clue?

Here is my reproduction of the oops, as well as I could do it:

   EIP is at acpi_os_read_memory+0x0c/0x60
eax: c0428120  ebx: c13d6b7c  ecx: 00000008  edx: c1233f38
esi: c13d6b94  edi: c1233f38  ebp: 00000008  esp: c1233edc
ds: 007b  es: 0007b  ss: 0068
  Process events/0 (pid:3, threadinfo=c1232000  task=c123cc10)
Stack: 00001a66 c0246116 c0428120 c04280c0 c1233f38 00000008 c13d6b7c c1233f38
       00000282 c1233f3c c13c72bc 00000282 00000002 c03c18d0 c03c1520 c025edc8
       00000008 c1233f38 c13d6b94 c1233f68 c13c72bc c1232000 00000283 00000000

Call trace:
 [<c0246116>] acpi_hw_low_level_read+0x6e/0x124
 [<c025edc8>] acpi_ec_gpe_query+0x128/0x220
 [<c023019d>] acpi_os_execute_deferred+0x5d/0x80
 [<c0230140>] acpi_os_execute_deferred+0x0/0x80
 [<c0130604>] worker_thread+0x298/0x3dc
 [<c013036c>] worker_thread+0x0/0x3dc
 [<c0230140>] acpi_os_execute_deferred+0x0/0x80
 [<c011913c>] default_wake_function+0x0/0x1c
 [<c011913c>] default_wake_function+0x0/0x1c
 [<c013519c>] kthread+0x70/0xa0
 [<c013512c>] kthread+0x0/0xa0
 [<c0103245>] kernel_thread_helper+0x5/0xc

Code: 8a 80 00 00 00 c0 88 02 eb 26 0f b7 80 00 00 00 c0 66 89 02
<6>note: events/0[3] exited with preempt-count 1

Ethan Glasser-Camp

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  parent reply	other threads:[~2004-06-02  4:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-02  3:17 Re: Oops during startup Yu, Luming
     [not found] ` <3ACA40606221794F80A5670F0AF15F840483B1C4-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-06-02  4:29   ` Ethan Glasser-Camp [this message]
2004-06-03  3:43   ` Andrew D. Keyser
  -- strict thread matches above, loose matches on Subject: below --
2004-06-02  5:42 Li, Shaohua
2004-06-09  9:34 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=20040602042917.GA609@paladin \
    --to=glasse-il7dboyr4vg@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=luming.yu-ral2JQCrhuEAvxtiuMwx3w@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