Results 1 to 4 of 4

Thread: Invalid _PCT data error

  1. #1

    Question Invalid _PCT data error

    Hello again! I recently (10/17/2017) reinstalled openSUSE Tumbleweed on my old system (dual Intel Pentium 4 processors, 2+ GiB of Ram, Western Digital hard disk drive, integrated VGA adapter). I did the reinstall because I was having trouble with the new BTRFS. I went back to EXT4 for the file system, and my system is behaving much better now. But I do have one little problem -- it's more of an annoyance than anything else.

    Whenever I reboot my system I have to boot up twice. The first attempt always hangs up with an error message (usually two of them, but sometimes as many as six). This morning I got these two errors.
    Code:
    21.647883 ACPI Invalid _PCT data
    21.647667 ACPI Invalid _PCT data
    The second boot attempt always succeeds (so far). But I do get the same error message on the second boot. (This morning, again.)
    Code:
    [   19.712410] ACPI Warning: \_PR.CPU1._PCT: Return Package is too small - found 1 elements, expected 2 (20170531/nsprepkg-398)
    [   19.712432] ACPI: Invalid _PCT data
    [   19.712980] ACPI Warning: \_PR.CPU2._PCT: Return Package is too small - found 1 elements, expected 2 (20170531/nsprepkg-398)
    [   19.712998] ACPI: Invalid _PCT data
    [   19.826604] ACPI: Invalid _PCT data
    [   19.827228] ACPI: Invalid _PCT data
    [   19.861515] ACPI: Invalid _PCT data
    [   19.862163] ACPI: Invalid _PCT data
    Any ideas how I can fix this? Thank you!

  2. #2
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    32,355
    Blog Entries
    15

    Default Re: Invalid _PCT data error

    Hi
    Related to frequency scaling... Line 234;
    http://elixir.free-electrons.com/lin...ssor_perflib.c

    I'm guessing nothing can be done for an old processor... running 32bit is it?
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  3. #3

    Question Re: Invalid _PCT data error

    Quote Originally Posted by malcolmlewis View Post
    Hi
    Related to frequency scaling... Line 234;
    http://elixir.free-electrons.com/lin...ssor_perflib.c

    I'm guessing nothing can be done for an old processor... running 32bit is it?
    Well, I found that bit of code ... it looks like it's been part of Linux for a long time. I've been running an openSUSE version of Linux for about 15 or 16 years now. About 10 years on this box. And yes, it's a 32-bit processor (2 of them, actually).

    The odd thing is, I've never gotten this error message before. I ran Tumbleweed for about a month before my latest install, and the only thing I changed was to use the EXT4 file system instead of BTRFS.

    As I stated previously, this is more of an annoyance than anything else. I'm just curious why it started happening recently, when it didn't happen just a few weeks ago.

  4. #4
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    32,355
    Blog Entries
    15

    Default Re: Invalid _PCT data error

    On Sat 04 Nov 2017 07:36:01 PM CDT, davidcbryant1951 wrote:

    malcolmlewis;2843928 Wrote:
    > Hi
    > Related to frequency scaling... Line 234;
    > http://tinyurl.com/yaywgjfa
    >
    > I'm guessing nothing can be done for an old processor... running 32bit
    > is it?


    Well, I found that bit of code ... it looks like it's been part of Linux
    for a long time. I've been running an openSUSE version of Linux for
    about 15 or 16 years now. About 10 years on this box. And yes, it's a
    32-bit processor (2 of them, actually).

    The odd thing is, I've never gotten this error message before. I ran
    Tumbleweed for about a month before my latest install, and the only
    thing I changed was to use the EXT4 file system instead of BTRFS.

    As I stated previously, this is more of an annoyance than anything else.
    I'm just curious why it started happening recently, when it didn't
    happen just a few weeks ago.


    Hi
    Changes in the kernel, 32bit flags are being dropped, so maybe one of
    those has affected it...

    --
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    openSUSE Leap 42.2|GNOME 3.20.2|4.4.90-18.32-default
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!


Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •