Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 249262 - sys-kernel/gentoo-sources-2.6.27-r4 - ACPI errors on Intel Core 2 Duo
Summary: sys-kernel/gentoo-sources-2.6.27-r4 - ACPI errors on Intel Core 2 Duo
Status: RESOLVED CANTFIX
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: All Linux
: High minor (vote)
Assignee: Gentoo Kernel Bug Wranglers and Kernel Maintainers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-29 14:10 UTC by André Terpstra
Modified: 2009-04-02 00:14 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
dmesg output (dmesg.txt,39.64 KB, text/plain)
2008-11-29 14:11 UTC, André Terpstra
Details
dmesg output from temporary git-sources (dmesg.txt,42.64 KB, text/plain)
2008-11-29 23:28 UTC, André Terpstra
Details
kernel conf for gentoo-sources (conf-2.6.27-gentoo-r4,47.40 KB, text/plain)
2008-11-30 18:02 UTC, André Terpstra
Details
kernel conf for git sources (conf-2.6.28-rc5-git4,49.67 KB, text/plain)
2008-11-30 18:03 UTC, André Terpstra
Details
dmesg output (updated) (dmesg.txt,42.62 KB, text/plain)
2008-11-30 18:04 UTC, André Terpstra
Details
acpidump output (acpi.txt,119.34 KB, text/plain)
2008-11-30 20:22 UTC, André Terpstra
Details

Note You need to log in before you can comment on or make changes to this bug.
Description André Terpstra 2008-11-29 14:10:28 UTC
On my new Sony Vaio laptop I have successfully ported Gentoo from a Core 2 Duo desktop. Everything seems to work quite well, however I receive errors from the kernel ACPI (sub)system. the major error message that troubles me is "ACPI Error (psargs-0358): [SMS_] Namespace lookup failure, AE_NOT_FOUND".

This may be just an informational message but looks like a bug. Before reporting it to kernel bugzilla, since I use gentoo-sources, I have to post it here.

Again, the system works, but I wonder how to proceed. The dmesg output will be attached.
Comment 1 André Terpstra 2008-11-29 14:11:39 UTC
Created attachment 173754 [details]
dmesg output
Comment 2 Mike Pagano gentoo-dev 2008-11-29 19:15:06 UTC
Can you test with the latest git-sources.

Comment 3 André Terpstra 2008-11-29 21:55:06 UTC
(In reply to comment #2)
> Can you test with the latest git-sources.

ok how?
Comment 4 Andreas Aronsson 2008-11-29 22:07:47 UTC
I believe Mike refers to the git-sources in portage. In that case first step would be to keyword and then emerge git-sources.
Comment 5 André Terpstra 2008-11-29 23:27:57 UTC
This did not help in any way. See the new dmesg output.

It even caused some extra problems, since I could not get my nvidia card working I had to revert to the gentoo-sources.
Comment 6 André Terpstra 2008-11-29 23:28:37 UTC
Created attachment 173827 [details]
dmesg output from temporary git-sources
Comment 7 André Terpstra 2008-11-29 23:29:56 UTC
(In reply to comment #4)
> I believe Mike refers to the git-sources in portage. In that case first step
> would be to keyword and then emerge git-sources.
> 

BTW keywording was not necessary; I already use the unstable tree.
Comment 9 Mike Pagano gentoo-dev 2008-11-30 16:34:42 UTC
(In reply to comment #8)
> Harmless known bug (with the BIOS?):
> 
> http://markmail.org/message/kbpgytwd7fmsq4e7
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=20edd74fcf9ad02c19efba0c13670a7b6b045099
> 

Looks like it might be the case.  Can you post .config from both the git-sources kernel you used and the 2.6.27-r4 kernel.
Comment 10 André Terpstra 2008-11-30 18:02:36 UTC
Created attachment 173882 [details]
kernel conf for gentoo-sources

Note: this is slightly different from the one I used earlier, so I'll post an updated dmesg log.
Comment 11 André Terpstra 2008-11-30 18:03:29 UTC
Created attachment 173883 [details]
kernel conf for git sources
Comment 12 André Terpstra 2008-11-30 18:04:19 UTC
Created attachment 173884 [details]
dmesg output (updated)
Comment 13 Mike Pagano gentoo-dev 2008-11-30 19:31:16 UTC
Can you post the BIOS version and exact laptop model?
Can you attach the output of acpidump (located in pmtools)
Comment 14 André Terpstra 2008-11-30 20:09:23 UTC
The laptop model is Sony Vaio VGN-AR71M
The BIOS version is R2090J8

I must add that there is something strange about this BIOS. I've never seen a BIOS that allows you so few changes. In fact no single setting on this machine can be changed except for trivial things such as date/time and boot order. Weird, like someone locked the BIOS in the shop?!
Comment 15 André Terpstra 2008-11-30 20:14:29 UTC
cannot emerge pmtools. some bug prevents this.
Comment 16 André Terpstra 2008-11-30 20:22:09 UTC
Ok bugzilla provided the solution. aftwer downgrading to bison-2.3 I could continue.
Comment 17 André Terpstra 2008-11-30 20:22:50 UTC
Created attachment 173893 [details]
acpidump output
Comment 18 André Terpstra 2008-11-30 21:26:39 UTC
(In reply to comment #14)
> The laptop model is Sony Vaio VGN-AR71M
> The BIOS version is R2090J8
> 
> I must add that there is something strange about this BIOS. I've never seen a
> BIOS that allows you so few changes. In fact no single setting on this machine
> can be changed except for trivial things such as date/time and boot order.
> Weird, like someone locked the BIOS in the shop?!
> 
I've looked a little closer and based on the title "Phoenix TrustedCore" this BIOS actually looks like my first EFI... Have no idea about the consequence, not even sure whether I enabled it in the kernel...
Comment 19 Mike Pagano gentoo-dev 2008-12-02 00:30:02 UTC
I think this is a BIOS bug.

I believe a non-existent variable is trying to be accessed and therefore the error message is thrown. 

Is there an update for your BIOS?
Comment 20 André Terpstra 2008-12-03 07:26:23 UTC
No I cannot find any BIOS update.
Comment 21 Daniel Drake (RETIRED) gentoo-dev 2008-12-03 12:02:31 UTC
This is indeed a bios bug, the first SSDT implements the SATA extensions wrongly.. it refers to an external namespace which is not defined by any other table.

This error is otherwise harmless though. You could avoid it by disabling CONFIG_ATA_ACPI. The consequences of this error message is that the features enabled by CONFIG_ATA_ACPI are not available.

I assume that everything is working fine even in the presence of this "error" message.


Eray: Thanks for investigating; the reports you found are similar but not the same. In the case you found, the problem is with the _EC object which is right at the heart of ACPI. In this case, it is the _SDD method being called on a SATA device that causes the problem. You can see that it is related to the ata (libata) subsystem because of the message that appears right after:
[    8.951872] ata1.00: ACPI _SDD failed (AE 0x5)
Comment 22 David Carlos Manuelda 2009-04-02 00:14:46 UTC
for more info, I have same issues on a sony vaio vgz-aw21z on kernel 2.6.29