From: Ian Pilcher <i.pilcher-Wuw85uim5zDR7s880joybQ@public.gmane.org>
To: "Yu, Luming" <luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: More info on VP6 panics
Date: Sun, 18 Jan 2004 23:38:35 -0600 [thread overview]
Message-ID: <400B6D5B.4010707@comcast.net> (raw)
In-Reply-To: <3ACA40606221794F80A5670F0AF15F8401720CF5-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
Yu, Luming wrote:
> That experiment can only tell that there is no panic displayed on you
> screen
> before the infinite loop.
The panic isn't occurring in the ACPI code. It's the idle thread on the
other processor that panics.
> Did you file it on bugzilla.kernel.org? It will help us a lot.
I've created bug #1908:
http://bugzilla.kernel.org/show_bug.cgi?id=1908
--
========================================================================
Ian Pilcher i.pilcher-Wuw85uim5zDR7s880joybQ@public.gmane.org
========================================================================
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
next prev parent reply other threads:[~2004-01-19 5:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-18 8:01 More info on VP6 panics Yu, Luming
[not found] ` <3ACA40606221794F80A5670F0AF15F8401720CF5-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-01-19 5:38 ` Ian Pilcher [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-17 6:50 Ian Pilcher
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=400B6D5B.4010707@comcast.net \
--to=i.pilcher-wuw85uim5zdr7s880joybq@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