http://bugzilla.kernel.org/show_bug.cgi?id=8757


[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[EMAIL PROTECTED]




------- Comment #18 from [EMAIL PROTECTED]  2007-08-12 18:50 -------
I decided to comment on this bug, even though I can't say for sure that what
I'm experiencing is the same thing, or related to the problem discussed here,
but I think it is...  First of all, my hardware is Toshiba Satellite A30-213,
an oldish P4 laptop with Phoenix (not Toshiba) bios.  I'm not using
toshiba_acpi module (it is incompatible with my bios) - only standard ACPI
modules.  The kernel is pretty much the default Arch Linux kernel but with
Suspend2 patch added and with some minor configuration changes - the problem
also occurs with the default arch linux 2.6.22.1 and 2.6.22.2 kernels.

My problem is certainly ACPI related and it also only occurs in 2.6.22 kernels
(both 2.6.22.1 and 2.6.22.2) - 2.6.21 works without problems, and I don't
remember experiencing anything like this with any previous kernel.  The
symptoms are similar - ACPI fails hanging all ACPI related software (conky,
suspend, etc.), when I try running "acpi -b" or "acpi -V", for example, the
terminal will hang and has to be killed manually (ctrl-c doesn't work).  Doing
something like "cat /proc/acpi/battery/BAT1/state" results in the same kind of
lockup.  Reloading ACPI modules manually doesn't help.

[Another problem I've been experiencing with this 2.6.22 kernel has to do with
clocksource - I have to run the kernel with "clocksource=pit" option, otherwise
I get temporary soft lockups every now and then.  At first I thought that the
problems were related, but now I don't think so - the ACPI problem appears even
when using pit clock and in spite of the fact that the soft lockups don't
happen anymore.  I thought I'd mention this for the sake of completeness
though.]

I am able to reproduce the bug fairly easily, basically all I have to do is
restart the computer instead of shutting it down completely and then powering
it back on. The bug generally occurs within the first couple of minutes from
reboot  - pretty much whenever the computer is not shutdown completely
(although not always).  If it doesn't occur then it doesn't seem to occur at
all until another reboot.

When the problem does occur, the following can be found in
/var/log/messages.log:

----
Aug 13 03:21:00 toshiba ACPI Error (dswload-0774): [PBST] Namespace lookup
failure, AE_ALREADY_EXISTS
Aug 13 03:21:00 toshiba ACPI Exception (psloop-0225): AE_ALREADY_EXISTS, During
name lookup/catalog [20070126]
Aug 13 03:21:00 toshiba ACPI Error (psparse-0537): Method parse/execution
failed [\_SB_.PCI0.LPCB.BAT1._BST] (Node c18a3b80), AE_ALREADY_EXISTS
Aug 13 03:21:00 toshiba ACPI: Marking method _BST as Serialized
Aug 13 03:21:00 toshiba ACPI Exception (battery-0206): AE_ALREADY_EXISTS,
Evaluating _BST [20070126]
Aug 13 03:21:00 toshiba ACPI Error (psargs-0355): [PBST] Namespace lookup
failure, AE_NOT_FOUND
Aug 13 03:21:00 toshiba ACPI Error (psparse-0537): Method parse/execution
failed [\_SB_.PCI0.LPCB.BAT1._BST] (Node c18a3b80), AE_NOT_FOUND
Aug 13 03:21:00 toshiba ACPI Exception (battery-0206): AE_NOT_FOUND, Evaluating
_BST [20070126]
----

Interestingly, adding "ec_intr=0" *seems* to fix the problem for me.  I added
it to my kernel command line and I rebooted three times without the problem
appearing.  I removed it from the kernel command line and, sure enough, the
problem appeared on the second try.  I added it back and right now, after two
more reboots, everything is working perfectly.  It's a bit late right now, but
I will do more testing tomorrow and I'll report if I discover something
interesting.

This is my first comment on the kernel bugzilla so please bear with my relative
lack of experience.  I'd be happy to help out any way I can, although you might
have to be a bit explicit at first when telling me what you need from me.


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla

Reply via email to