Logs filled with psargs/psparse kernel message

hazza · 03-24-2005, 06:09 AM

I'm running SUSE Linux 9.2 on an Acer Aspire 1690 series notebook and have noticed my logs being filled with psargs and psparse kernel mesages continuously:

Code:

Mar 24 18:31:42 knuckles kernel:   psargs-0352: *** Error: Looking up [Z00B] in namespace, AE_NOT_FOUND
Mar 24 18:31:42 knuckles kernel: search_node cdeb2a28 start_node cdeb2a28 return_node 00000000
Mar 24 18:31:42 knuckles kernel:  psparse-1133: *** Error: [NULL NAME], AE_NOT_FOUND
Mar 24 18:31:42 knuckles kernel:  psparse-1133: *** Error: Method execution failed [\_SB_.BAT1._BST] (Node cdeb24a8), AE_NOT_FOUND

The kernel source generating these messages appears to be under /usr/src/linux/drivers/acpi/parser/. So that would make it an ACPI parser problem. Has anyone else encountered this problem and managed to at least suppress the logging of it? I'd rather not disable ACPI.

sm1else · 03-30-2005, 03:45 PM

I have a Acer Travelmate 2200, and while I havent noticed the errors you mention in any logs, I have a problem with ACPI and have come across a similar message while trying to fix it.

My problem is that my battery is not detected (the ac adapter is detected, but not the battery). According to some of the ACPI documents (http://acpi.sourceforge.net/dsdt/index.php), many manufacturers do not write a correct DSDT (Differentiated System Description Table) to describe the various components. I have followed the instructions in the documentation to disassemble the DSDT and then recompile it. One of the errors during recompilation (there were quite a few but I have resolved the others) was:
dsdt.dsl 1798: Z00B,
Error 1022 - Object does not exist ^ (Z00B)

Note that dsdt.dsl is my disassembled source for the DSDT.
This occurs during the section describing the battery (well, presumably its the battery, it contains the string "Li-Ion" in the same block). The other compile issues included an implicit return (it needs to be explicit), and two instances of accessing memory in the wrong access mode (not sure ive got this quite right) where AnyAcc was used when it should have been ByteAcc.

Ive had a glance through the submitted DSDT's at http://acpi.sourceforge.net/dsdt/vie...ufacturer=ACER and there seems to be a DSDT that may match your laptop, if it doesnt match then you may have to try what im attempting now, http://www.cpqlinux.com/acpi-howto.html#basic_steps contains lots of information on how to fix a DSDT including common compile errors and solutions (sadly the Z00B error isnt listed)

Btw in case you are also having problems with the hotkeys (including the mail led on some acer laptops) have a look for the acerhk kernel module.

hazza · 03-31-2005, 12:25 AM

Thanks for the reply. I had noticed that on my notebook I wasn't getting a reading from the battery level sensors. I hadn't thought about that being related to the error message until you mentioned. Originally I did come across the acpi.sourceforge.net website but at the time didn't find anything specific for my notebook model. They now seem to have an entry for my precise model of ACER Aspire 1691WLMi. I'll look trying to use it to fix the probem.

On the topic of the hotkeys I used an existing method of mine to sort them out. I didn't find many keys that weren't reporting a scancode so I was able to use setkeycodes and XKB. I'll post what I've done here later so anyone else can use them for reference.

EDIT: I've posted my multimedia and Fn key configuration in the Mapping Multimedia Keyboard thread.

hazza · 04-01-2005, 02:33 AM

I tried to compile pacpidump.tar.gz as mentioned in the Linux ACPI Howto and found that gcc doesn't agree with it. It appears as though C++ style comments (//) have been used in the middle of the first string argument that was split over several lines. That's not the only thing that gcc doesn't like but I'm trying to fix it.

sm1else · 04-03-2005, 05:53 AM

Have you tried the -ansi option with gcc, it uses strict ANSI C rather than C99 with GNU extensions. Among other things it will not consider // to be a comment in ANSI mode.

when dissasembling the dsdt, i just used 'iasl -d' on /proc/acpi/dsdt and it worked fine, though its probably best to use pacpidump anyway.

I managed to get the dsdt corrected, and its fixed my battery problem, i havent checked my logs because im not sure which one the messages should be in.

Some information I found for creating the new initrd (it is possible to overide the bios DSDT using this rather than building it into the kernel) at the end turned out to be incorrect. You need to modify one of the sysconfig files (if i remember rightly it was /etc/sysconfig/kernel), in that file there is a line regarding extra files for building the initrd. Add the compiled DSDT filename (should be a .dsl) to this list and run:
mkinitrd
lilo

thanks for the pointer on the hotkeys

hazza · 04-03-2005, 07:22 AM

Quote:

Originally posted by sm1else
Have you tried the -ansi option with gcc, it uses strict ANSI C rather than C99 with GNU extensions. Among other things it will not consider // to be a comment in ANSI mode.

Another person I asked mentioned using an option like that as well. The only thing was I had already modified the code to make it compile without using ANSI C.

Quote:

when dissasembling the dsdt, i just used 'iasl -d' on /proc/acpi/dsdt and it worked fine, though its probably best to use pacpidump anyway.

Considering I just ran acpidump as a normal user and noticed it fail on trying to read /dev/mem I think the way you've disassembled the DSDT might be better.

Quote:

I managed to get the dsdt corrected, and its fixed my battery problem, i havent checked my logs because im not sure which one the messages should be in.

The kernel messages would probably look similar to the ones I posted.

aristodemos · 05-07-2005, 10:49 AM

so hazza have you been able to solve your issue with the ASPIRE 1690?

I am thinking about buying one of these laptops and I want to know how well it runs on linux, and in particular on SuSe... I have read some people complaining about the video and X... no problems for you?

hazza · 05-07-2005, 11:37 AM

Quote:

Originally posted by aristodemos
so hazza have you been able to solve your issue with the ASPIRE 1690?

The ACPI issue is still a work in progress. I have it down to just one compile error and one warning:

Code:

$ iasl -sa ACER-Aspire_1691WLMi-S3C11-custom.asl

Intel ACPI Component Architecture
ASL Optimizing Compiler / AML Disassembler version 20040220 [Oct  2 2004]
Copyright (C) 2000 - 2004 Intel Corporation
Supports ACPI Specification Revision 2.0c

ACER-Aspire_1691WLMi-S3C11-custom.asl   571:             If (LEqual (And (PDC0,0x0A), 0x0A))
Error    1022 -                                        Object does not exist ^(PDC0)

ACER-Aspire_1691WLMi-S3C11-custom.asl  2542:                 Scope (\_SB.PCI0)
Warning  2031 -                                     Internal compiler error ^  (Not using optimized name - did not find node)

ASL Input:  ACER-Aspire_1691WLMi-S3C11-custom.asl - 6915 lines, 241189 bytes, 3175 keywords
Compilation complete. 1 Errors, 1 Warnings, 0 Remarks, 1110 Optimizations

I need more information to fix it and the ACPI specification doesn't seem to cover this sort of thing.

Quote:

I am thinking about buying one of these laptops and I want to know how well it runs on linux, and in particular on SuSe... I have read some people complaining about the video and X... no problems for you?

SUSE 9.2 works okay on my Aspire 1691 after some tweaking. It's the only distribution so far that I have been able to get to use the correct video resolution. Can you provide a link where you read about the X problems?

I've found that regardless of the distribution starting PCMCIA hangs it. To actually install SUSE I told it to do a manual install to stop it from loading PCMCIA. After installing SUSE I had to boot into runlevel 1 to disable it with "chkconfig pcmcia off". At the time I couldn't figure out what kernel argument to use to disable PCMCIA. I've since found that SUSE checks for a non-empty variable named NOPCMCIA to disable PCMCIA rather than the more common pcmcia=off.

There also appears to be some sort of boot loader/kernel loading issue that results in a hang when the kernel is loaded. I had initially thought it was a problem with isolinux as I was able to work around it by using GRUB. I've now learnt how to replace the boot loader on bootable CDs with GRUB. However more recently I've found that I'm unable to a kernel built under Gentoo with the same GRUB boot loader that can load SUSE.

The answer to the question off whether you should get an Aspire 1690 is to ask yourself do you like a challenge? Of course that might be redundant if you've already been scared off by the problems I've mentioned. Although my guess is more people having this laptop will probably means that there'd be a better chance of Linux support improving.

aristodemos · 05-07-2005, 12:18 PM

Quote:

Originally posted by hazza
SUSE 9.2 works okay on my Aspire 1691 after some tweaking. It's the only distribution so far that I have been able to get to use the correct video resolution. Can you provide a link where you read about the X problems?

I've found that regardless of the distribution starting PCMCIA hangs it. To actually install SUSE I told it to do a manual install to stop it from loading PCMCIA. After installing SUSE I had to boot into runlevel 1 to disable it with "chkconfig pcmcia off". At the time I couldn't figure out what kernel argument to use to disable PCMCIA. I've since found that SUSE checks for a non-empty variable named NOPCMCIA to disable PCMCIA rather than the more common pcmcia=off.

There also appears to be some sort of boot loader/kernel loading issue that results in a hang when the kernel is loaded. I had initially thought it was a problem with isolinux as I was able to work around it by using GRUB. I've now learnt how to replace the boot loader on bootable CDs with GRUB. However more recently I've found that I'm unable to a kernel built under Gentoo with the same GRUB boot loader that can load SUSE.

The answer to the question off whether you should get an Aspire 1690 is to ask yourself do you like a challenge? Of course that might be redundant if you've already been scared off by the problems I've mentioned. Although my guess is more people having this laptop will probably means that there'd be a better chance of Linux support improving. [/B]

thanks very much hazza for alll the info you gave me, that helps a lot and it seems you have had some issues with this laptop and linux. I will have to really think about this... ;-)

The video is the thing that concerns me most. The Aspire 1691 that I am considering seems to have an
ATI MOBILITY™ RADEON® X600 PCI Express video card which presumably it is not supported by the ATI drivers (check http://www2.ati.com/drivers/linux/li...10.html#176601 )
Interestingly, the X700 seems to be supported, but that is the video card that comes with the Aspire 1680 though.

I have read some people having a black screen on the laptop. (e.g.., http://www.linuxquestions.org/questions/history/316292).

I guess you know this page already: http://odin.prohosting.com/wedge01/g...l#1_whichcards

There it says the following about laptops using ATI cards:

--------------------------------------------------------------------------------------------------
Question 4.40: X appears to be starting up, but I can only see a black screen
There are various possible causes for this. The first thing to try should always be toggling the value of the "UseInternalAGPGART" setting in your /etc/X11/xorg.conf.

Other possible solutions:

* Some systems may require you to change the "MonitorLayout" setting from the default of "AUTO, AUTO" (which tries to autodetect your monitor config). If you have a laptop with a Mobility card and are seeing black screens, try changing "AUTO, AUTO" to "LVDS, AUTO". This problem particularly seems to be affecting laptops with X-series Mobilty chipsets (X300, X600 etc).
* It may also be worth trying different values for the "MonitorLayout" setting for various other monitor layouts. The possible values for the two settings (the first is the primary monitor, the second is the secondary) appear to be:
o NONE
o TVDAC/ExtDAC
o AUTO
o TMDS
o LVDS

--------------------------------------------------------------------------------------------------

Did you try that solution?

In any case, I am a bit confused about the video card on the 1691 as there may be variations in different models. Do you know exactly which video card your 1691 uses? (X600, X700 ???)

I would probably like to have more info about your 1691 + linux. Do you have some messanger or email we can communicate more easily than this post? Please write me to ssardina at datafull dot com if you can. Thanks and good luck!

hazza · 05-07-2005, 12:51 PM

Quote:

Originally posted by aristodemos
thanks very much hazza for alll the info you gave me, that helps a lot and it seems you have had some issues with this laptop and linux. I will have to really think about this... ;-)

The video is the thing that concerns me most. The Aspire 1691 that I am considering seems to have an
ATI MOBILITYï¿½ RADEONï¿½ X600 PCI Express video card which presumably it is not supported by the ATI drivers (check http://www2.ati.com/drivers/linux/li...10.html#176601 )
Interestingly, the X700 seems to be supported, but that is the video card that comes with the Aspire 1680 though.

The specific model of my laptop is the Aspire 1691WLMi. The graphics chip in it is indeed an ATI MOBILITY RADEON X600. I had less success (well none really) with the ATI driver that SUSE bundles (fglrx) than the radeon driver that's included in Xorg. After going to the ATI site and eventually I wasn't too impressed by the fact that when I looked up a driver for the Mobility X600 and was redirected to a page telling me to use Windows.

Quote:

I have read some people having a black screen on the laptop. (e.g.., http://www.linuxquestions.org/questions/history/316292).

I guess you know this page already: http://odin.prohosting.com/wedge01/g...l#1_whichcards

I didn't come across that page but I had already come to the conclusion that the ATI fglrx driver doesn't support the Mobility X600 chip.

Quote:

There it says the following about laptops using ATI cards:

--------------------------------------------------------------------------------------------------
Question 4.40: X appears to be starting up, but I can only see a black screen
There are various possible causes for this. The first thing to try should always be toggling the value of the "UseInternalAGPGART" setting in your /etc/X11/xorg.conf.

Other possible solutions:

* Some systems may require you to change the "MonitorLayout" setting from the default of "AUTO, AUTO" (which tries to autodetect your monitor config). If you have a laptop with a Mobility card and are seeing black screens, try changing "AUTO, AUTO" to "LVDS, AUTO". This problem particularly seems to be affecting laptops with X-series Mobilty chipsets (X300, X600 etc).
* It may also be worth trying different values for the "MonitorLayout" setting for various other monitor layouts. The possible values for the two settings (the first is the primary monitor, the second is the secondary) appear to be:
o NONE
o TVDAC/ExtDAC
o AUTO
o TMDS
o LVDS

--------------------------------------------------------------------------------------------------

Did you try that solution?

Would the blanking problem be using the ATI fglrx driver? When I tried it with the version that comes with SUSE it just crashed. I managed to get Yast to configure the display at it's native resolution of 1280x800 using the radeon driver. After I tweaked /etc/xorg/xorg.conf I made it immuteable to keep it that way.

Quote:

In any case, I am a bit confused about the video card on the 1691 as there may be variations in different models. Do you know exactly which video card your 1691 uses? (X600, X700 ???)

Well, as far as I know my particular version of this model is a Aspire 1691WLMi that has the ATI Mobility Radeon X600 chip. I made a point of only buying a laptop I could see in person. You might find Kanotix handy to help you make a decision. After telling it to boot with pcmcia=off it booted and started X albeit not at the native resolution at 1024x768. After getting this laptop Kanotix has become my favourite live CD.

sm1else · 05-08-2005, 04:30 AM

For the PDC0 error, have you tried replacing PDC0 with

Code:

External(PDC0)

?

hazza · 05-08-2005, 04:48 AM

Quote:

Originally posted by sm1else
For the PDC0 error, have you tried replacing PDC0 with

Code:

External(PDC0)

?

I replaced PDC0 with External(PDC0) in

Code:

    Method (PNOT, 0, Serialized)
    {
        If (HTTE)
        {
            If (LEqual (And (PDC0, 0x0A), 0x0A))
            {
                Notify (\_PR.CPU0, 0x80)
            }

            If (LEqual (And (\_SB.PCI0.RP01.PDC1, 0x0A), 0x0A))
            {
                Notify (\_PR.CPU1, 0x80)
            }
        }
        Else
        {
            Notify (\_PR.CPU0, 0x80)
            Sleep (0x64)
            Notify (\_PR.CPU0, 0x81)
        }
    }

That just changed the error to:

Code:

$ iasl ACER-Aspire_1691WLMi-S3C11-custom.asl

Intel ACPI Component Architecture
ASL Optimizing Compiler / AML Disassembler version 20040220 [Oct  2 2004]
Copyright (C) 2000 - 2004 Intel Corporation
Supports ACPI Specification Revision 2.0c

ACER-Aspire_1691WLMi-S3C11-custom.asl   571:             If (LEqual (And (External (PDC0), 0x0A), 0x0A))
Error    1037 -                        syntax error, unexpected PARSEOP_EXTERNAL ^

ACER-Aspire_1691WLMi-S3C11-custom.asl   571:             If (LEqual (And (External (PDC0), 0x0A), 0x0A))
Error    1037 -                                     syntax error, unexpected ',', expecting ')' ^

ACER-Aspire_1691WLMi-S3C11-custom.asl   581:         Else
Error    1037 -   syntax error, unexpected PARSEOP_ELSE ^

ASL Input:  ACER-Aspire_1691WLMi-S3C11-custom.asl - 6790 lines, 238469 bytes, 247 keywords
Compilation complete. 3 Errors, 0 Warnings, 0 Remarks, 0 Optimizations

It looks like substituting PDC0 with External (PDC0) in that context results in incorrect syntax.

Djax · 05-09-2005, 06:29 AM

On a Gentoo Forum , Swisscheese who has an Acer Travelmate 8103, did the following to fix the PDC0 error:

Quote:

Around line #1939 Change:

Code:

 
Field (P1CS, AnyAcc, NoLock, WriteAsZeros)
                {
                    Offset (0x1A),
                    ABP1,   1,
                        ,   2,
                    PDC1,   1,
                    PDC2,   2,
                    PDS1,   1,
                    Offset (0x20),

To:

Code:

 
Field (P1CS, AnyAcc, NoLock, WriteAsZeros)
                {
                    Offset (0x1A),
                    ABP1,   1,
                    PDC0,   2,
                    PDC1,   1,
                    PDC2,   2,
                    PDS1,   1,
                    Offset (0x20),

Around line #515 Change:

Code:

If (HTTE)
        {
            If (LEqual (And (PDC0, 0x0A), 0x0A))
            {
                Notify (\_PR.CPU0, 0x80)
            }

            If (LEqual (And (PDC1, 0x0A), 0x0A))
            {
                Notify (\_PR.CPU1, 0x80)
            }
        }

To:

Code:

If (HTTE)
        {
            If (LEqual (And (\_SB.PCI0.RP01.PDC0, 0x0A), 0x0A))
            {
                Notify (\_PR.CPU0, 0x80)
            }

            If (LEqual (And (\_SB.PCI0.RP01.PDC1, 0x0A), 0x0A))
            {
                Notify (\_PR.CPU1, 0x80)
            }
        }

The compilation error is gone, but i don't know if it sloves a problem and which one.

I have a Acer Aspire 1694WLMi Bios 3c25 and I get the following errors when I try to compile my DSDT:

Code:

Intel ACPI Component Architecture
ASL Optimizing Compiler / AML Disassembler version 20050309 [May  6 2005]
Copyright (C) 2000 - 2005 Intel Corporation
Supports ACPI Specification Revision 3.0

dsdt.20050509.dsl   450:                     Or (CFGD, 0xC0, CFGD)
Error    1022 -               Object does not exist ^  (CFGD)

dsdt.20050509.dsl   450:                     Or (CFGD, 0xC0, CFGD)
Error    1022 -                           Object does not exist ^  (CFGD)

dsdt.20050509.dsl   470:                     And (CFGD, 0x3F, CFGD)
Error    1022 -                Object does not exist ^  (CFGD)

dsdt.20050509.dsl   470:                     And (CFGD, 0x3F, CFGD)
Error    1022 -                            Object does not exist ^  (CFGD)

dsdt.20050509.dsl  2625:                             And (CFGD, 0x3F, CFGD)
Error    1022 -                        Object does not exist ^  (CFGD)

dsdt.20050509.dsl  2625:                             And (CFGD, 0x3F, CFGD)
Error    1022 -                                    Object does not exist ^  (CFGD)

dsdt.20050509.dsl  2634:                             Or (CFGD, 0xC0, CFGD)
Error    1022 -                       Object does not exist ^  (CFGD)

dsdt.20050509.dsl  2634:                             Or (CFGD, 0xC0, CFGD)
Error    1022 -                                   Object does not exist ^  (CFGD)

ASL Input:  dsdt.20050509.dsl - 6944 lines, 244149 bytes, 3203 keywords
Compilation complete. 8 Errors, 0 Warnings, 0 Remarks, 1120 Optimizations

I have no idea what CFGD represents and how to find it. Any help appreciated.

hazza · 05-09-2005, 07:04 AM

Quote:

Originally posted by Djax
On a Gentoo Forum , Swisscheese who has an Acer Travelmate 8103, did the following to fix the PDC0 error

That seems to narrow the problem down to the fact it wasn't defined in a Device declaration. It looks like it's part of a field. I'll have a look into that link to see if any justification the location of the PDC0 declaration. I've already made a couple of random decisions on return codes which I'm not really comfortable with.

Quote:

I have no idea what CFGD represents and how to find it. Any help appreciated.

It would appear as though you have a similar problem with a variable that's in use not being defined anywhere. When I did a search for documents I came up with the ACPI specification but that doesn't have any useful informations for specific implementations like we're dealing with. The short answer is you'll need to find a Device section to define CFGD. At a glance it's not possible to know where. I think we need ot find some specific documentation.