From: Alessandro Suardi <alessandro.suardi-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
To: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: linux-kernel
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
ACPI Developers
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: 2.6.3-rc3 (and possibly earlier 2.6): weird hang and oopses
Date: Tue, 17 Feb 2004 21:10:22 +0100 [thread overview]
Message-ID: <4032752E.9070201@oracle.com> (raw)
In-Reply-To: <1076999173.2508.30.camel-D2Zvc0uNKG8@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1873 bytes --]
Len Brown wrote:
> Alessandro,
> Sure looks like a failure in the ACPI processor driver.
>
> Please confirm your system is otherwise happy when you disable the
> processor driver. eg. CONFIG_ACPI_PROCESSOR=n
>
> Also, it would be helpful to know if this failure started recently or
> you saw it in previous releases, b/c we've made some changes to the
> processor driver recently.
Will run from now for a couple of weeks with CONFIG_ACPI_PROCESSOR=n;
I checked my logs and noticed my first hang happened with 2.6.2, but
so far I only experienced the problem twice since Feb 6.
I just now noticed that in /var/log I have the full Oops traces
(until I Alt-SysRq'd out of it), so I'm attaching them; would you
please take a further look and confirm this is _only_ an ACPI-related
issue ?
messages.gz is 2.6.3-rc3, messages.2.gz is 2.6.2 vanilla.
> thanks,
> -Len
>
> ps. acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org is the preferred alias to send
> Linux ACPI issues -- it includes linux-acpi-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org which is a small
> sub-set.
OK, thanks for the info, will do next time.
> On Mon, 2004-02-16 at 17:47, Alessandro Suardi wrote:
>
>>[CC:ing linux-acpi since some acpi stuff appears in backtraces]
>>
>>While apparently doing nothing special (possibly a 'rm' on a
>> regular ext3 filesystem) my laptop hung. Not completely, as
>> I could
>>
>> * switch virtual desktops within Ximian Desktop 2
>> * click on the kill window top right button, see the "app is
>> not responding, kill it anyway ?" dialog, say ok, see the
>> gnome-terminal vanish
>> * Alt-Fn to virtual consoles, type a login name (but getting
>> no prompt for the password - this hung)
>> * Alt-SysRq
Many thanks,
--alessandro
"Two rivers run too deep
The seasons change and so do I"
(U2, "Indian Summer Sky")
[-- Attachment #2: messages.gz --]
[-- Type: application/x-gzip, Size: 5232 bytes --]
[-- Attachment #3: messages.2.gz --]
[-- Type: application/x-gzip, Size: 8850 bytes --]
next prev parent reply other threads:[~2004-02-17 20:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A6974D8E5F98D511BB910002A50A6647615F214C@hdsmsx402.hd.intel.com>
[not found] ` <A6974D8E5F98D511BB910002A50A6647615F214C-N2PTB0HCzHJF3Yvz3xaN/VDQ4js95KgL@public.gmane.org>
2004-02-17 6:26 ` 2.6.3-rc3 (and possibly earlier 2.6): weird hang and oopses Len Brown
[not found] ` <1076999173.2508.30.camel-D2Zvc0uNKG8@public.gmane.org>
2004-02-17 20:10 ` Alessandro Suardi [this message]
[not found] ` <4032752E.9070201-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2004-02-18 9:00 ` Dominik Brodowski
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=4032752E.9070201@oracle.com \
--to=alessandro.suardi-qhclzuegtsvqt0dzr+alfa@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@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