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.
Created attachment 173754 [details]
Can you test with the latest git-sources.
(In reply to comment #2)
> Can you test with the latest git-sources.
I believe Mike refers to the git-sources in portage. In that case first step would be to keyword and then emerge git-sources.
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.
Created attachment 173827 [details]
dmesg output from temporary git-sources
(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.
Harmless known bug (with the BIOS?):
(In reply to comment #8)
> Harmless known bug (with the BIOS?):
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.
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.
Created attachment 173883 [details]
kernel conf for git sources
Created attachment 173884 [details]
dmesg output (updated)
Can you post the BIOS version and exact laptop model?
Can you attach the output of acpidump (located in pmtools)
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?!
cannot emerge pmtools. some bug prevents this.
Ok bugzilla provided the solution. aftwer downgrading to bison-2.3 I could continue.
Created attachment 173893 [details]
(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...
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?
No I cannot find any BIOS update.
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)
for more info, I have same issues on a sony vaio vgz-aw21z on kernel 2.6.29