kernel 4.9.6 throws ACPI errors; cannot connect WiFi; core 2 goes near 100%
FedoraForum.org - Fedora Support Forums and Community
Results 1 to 8 of 8
  1. #1
    Join Date
    Feb 2012
    Location
    Lexington
    Posts
    66
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    kernel 4.9.6 throws ACPI errors; cannot connect WiFi; core 2 goes near 100%

    Already posted on bugzilla, but will try here hoping for a quicker answer. As mentioned, this cause WiFi to not work. One of my CPU cores goes near 100% usage, but htop does not report any particular process using anything near that.

    Since kernel upgrade 4.9.6, startup and shutdown throw the following errors, which dmesg confirms. Reverting to prior kernel 4.8.13 works fine.

    [ 1.525840] ACPI Error: No handler for Region [ECRM] (ffff99553a6f85a0) [EmbeddedControl] (20160422/evregion-166)
    [ 1.525844] ACPI Error: Region EmbeddedControl (ID=3) has no handler (20160422/exfldio-299)
    [ 1.525847] ACPI Error: Method parse/execution failed [\_TZ.RDEC] (Node ffff99553b0c5e38), AE_NOT_EXIST (20160422/psparse-542)
    [ 1.525852] ACPI Error: Method parse/execution failed [\_TZ.TZS0._TMP] (Node ffff99553b0c5f00), AE_NOT_EXIST (20160422/psparse-542)
    [ 1.525973] ACPI Error: No handler for Region [ECRM] (ffff99553a6f8ca8) [EmbeddedControl] (20160422/evregion-166)
    [ 1.525975] ACPI Error: Region EmbeddedControl (ID=3) has no handler (20160422/exfldio-299)
    [ 1.525978] ACPI Error: Method parse/execution failed [\_TZ.RDEC] (Node ffff99553b0c5e38), AE_NOT_EXIST (20160422/psparse-542)
    [ 1.525982] ACPI Error: Method parse/execution failed [\_TZ.TZS0._TMP] (Node ffff99553b0c5f00), AE_NOT_EXIST (20160422/psparse-542)

  2. #2
    Join Date
    Mar 2012
    Location
    München, Deutschland
    Posts
    897
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Question Re: kernel 4.9.6 throws ACPI errors; cannot connect WiFi; core 2 goes near 100%

    https://bugzilla.redhat.com/show_bug.cgi?id=1418160

    Possible solutions:
    [1] Please, upgrade you kernel to: 4.9.7-201.fc25.x86_64
    http://forums.fedoraforum.org/showpo...3&postcount=30

    [2] Then, you should read this thread: https://bugs.launchpad.net/ubuntu/+s...x/+bug/1612929
    There are several proposals how to improve situation/get rid of this bug.

    [3] If it does not help, please, do for me the following: dmesg | grep ACPI

    My CLI transcript follows:

    Code:
    [user@localhost ~]$ dmesg | grep ACPI
    [    0.000000] BIOS-e820: [mem 0x00000000bfed0000-0x00000000bfefefff] ACPI data
    [    0.000000] BIOS-e820: [mem 0x00000000bfeff000-0x00000000bfefffff] ACPI NVS
    [    0.000000] ACPI: Early table checksum verification disabled
    [    0.000000] ACPI: RSDP 0x00000000000F6A10 000024 (v02 PTLTD )
    [    0.000000] ACPI: XSDT 0x00000000BFEDD633 00005C (v01 INTEL  440BX    06040000 VMW  01324272)
    [    0.000000] ACPI: FACP 0x00000000BFEFEE73 0000F4 (v04 INTEL  440BX    06040000 PTL  000F4240)
    [    0.000000] ACPI: DSDT 0x00000000BFEDF3DC 01FA97 (v01 PTLTD  Custom   06040000 MSFT 03000001)
    [    0.000000] ACPI: FACS 0x00000000BFEFFFC0 000040
    [    0.000000] ACPI: FACS 0x00000000BFEFFFC0 000040
    [    0.000000] ACPI: BOOT 0x00000000BFEDF3B4 000028 (v01 PTLTD  $SBFTBL$ 06040000  LTP 00000001)
    [    0.000000] ACPI: APIC 0x00000000BFEDE8BD 000742 (v01 PTLTD  ? APIC   06040000  LTP 00000000)
    [    0.000000] ACPI: MCFG 0x00000000BFEDE881 00003C (v01 PTLTD  $PCITBL$ 06040000  LTP 00000001)
    [    0.000000] ACPI: SRAT 0x00000000BFEDD72F 0008D0 (v02 VMWARE MEMPLUG  06040000 VMW  00000001)
    [    0.000000] ACPI: HPET 0x00000000BFEDD6F7 000038 (v01 VMWARE VMW HPET 06040000 VMW  00000001)
    [    0.000000] ACPI: WAET 0x00000000BFEDD6CF 000028 (v01 VMWARE VMW WAET 06040000 VMW  00000001)
    [    0.000000] ACPI: Local APIC address 0xfee00000
    [    0.000000] ACPI: SRAT: Node 0 PXM 0 [mem 0x00000000-0x0009ffff]
    [    0.000000] ACPI: SRAT: Node 0 PXM 0 [mem 0x00100000-0xbfffffff]
    [    0.000000] ACPI: SRAT: Node 0 PXM 0 [mem 0x100000000-0x13fffffff]
    [    0.000000] ACPI: SRAT: Node 0 PXM 0 [mem 0x140000000-0x103fffffff] hotplug
    [    0.000000] ACPI: PM-Timer IO Port: 0x1008
    [    0.000000] ACPI: Local APIC address 0xfee00000
    [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
    [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
    
    ...[snap]...
    
    [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x7d] high edge lint[0x1])
    [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x7e] high edge lint[0x1])
    [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x7f] high edge lint[0x1])
    [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge)
    [    0.000000] ACPI: IRQ0 used by override.
    [    0.000000] ACPI: IRQ9 used by override.
    [    0.000000] Using ACPI (MADT) for SMP configuration information
    [    0.000000] ACPI: HPET id: 0x8086af01 base: 0xfed00000
    [    0.000126] ACPI: Core revision 20160831
    [    0.006841] ACPI: 1 ACPI AML tables successfully acquired and loaded
    [    0.039012] PM: Registering ACPI NVS region [mem 0xbfeff000-0xbfefffff] (4096 bytes)
    [    0.042327] ACPI: bus type PCI registered
    [    0.042332] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
    [    0.049341] ACPI: Added _OSI(Module Device)
    [    0.049343] ACPI: Added _OSI(Processor Device)
    [    0.049344] ACPI: Added _OSI(3.0 _SCP Extensions)
    [    0.049345] ACPI: Added _OSI(Processor Aggregator Device)
    [    0.051106] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
    [    0.061103] ACPI: Interpreter enabled
    [    0.061113] ACPI: (supports S0 S1 S4 S5)
    [    0.061121] ACPI: Using IOAPIC for interrupt routing
    [    0.061129] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
    [    0.124531] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7f])
    [    0.129769] pci 0000:00:07.3: quirk: [io  0x1000-0x103f] claimed by PIIX4 ACPI
    [    0.151759] pci 0000:00:11.0: System wakeup disabled by ACPI
    [    0.152550] pci 0000:00:15.0: System wakeup disabled by ACPI
    [    0.153217] pci 0000:00:15.1: System wakeup disabled by ACPI
    [    0.153925] pci 0000:00:15.2: System wakeup disabled by ACPI
    [    0.154442] pci 0000:00:15.3: System wakeup disabled by ACPI
    [    0.154805] pci 0000:00:15.4: System wakeup disabled by ACPI
    [    0.155961] pci 0000:00:15.5: System wakeup disabled by ACPI
    [    0.156372] pci 0000:00:15.6: System wakeup disabled by ACPI
    [    0.156843] pci 0000:00:15.7: System wakeup disabled by ACPI
    [    0.157994] pci 0000:00:16.0: System wakeup disabled by ACPI
    [    0.158948] pci 0000:00:16.1: System wakeup disabled by ACPI
    [    0.159467] pci 0000:00:16.2: System wakeup disabled by ACPI
    [    0.159892] pci 0000:00:16.3: System wakeup disabled by ACPI
    [    0.160692] pci 0000:00:16.4: System wakeup disabled by ACPI
    [    0.161502] pci 0000:00:16.5: System wakeup disabled by ACPI
    [    0.162078] pci 0000:00:16.6: System wakeup disabled by ACPI
    [    0.162731] pci 0000:00:16.7: System wakeup disabled by ACPI
    [    0.163022] pci 0000:00:17.0: System wakeup disabled by ACPI
    [    0.163466] pci 0000:00:17.1: System wakeup disabled by ACPI
    [    0.164129] pci 0000:00:17.2: System wakeup disabled by ACPI
    [    0.164569] pci 0000:00:17.3: System wakeup disabled by ACPI
    [    0.165493] pci 0000:00:17.4: System wakeup disabled by ACPI
    [    0.166178] pci 0000:00:17.5: System wakeup disabled by ACPI
    [    0.166624] pci 0000:00:17.6: System wakeup disabled by ACPI
    [    0.167188] pci 0000:00:17.7: System wakeup disabled by ACPI
    [    0.167795] pci 0000:00:18.0: System wakeup disabled by ACPI
    [    0.168607] pci 0000:00:18.1: System wakeup disabled by ACPI
    [    0.169253] pci 0000:00:18.2: System wakeup disabled by ACPI
    [    0.169518] pci 0000:00:18.3: System wakeup disabled by ACPI
    [    0.170278] pci 0000:00:18.4: System wakeup disabled by ACPI
    [    0.170879] pci 0000:00:18.5: System wakeup disabled by ACPI
    [    0.171699] pci 0000:00:18.6: System wakeup disabled by ACPI
    [    0.172589] pci 0000:00:18.7: System wakeup disabled by ACPI
    [    0.175674] pci 0000:02:00.0: System wakeup disabled by ACPI
    [    0.180053] pci 0000:02:01.0: System wakeup disabled by ACPI
    [    0.182057] pci 0000:02:02.0: System wakeup disabled by ACPI
    [    0.184838] pci 0000:02:03.0: System wakeup disabled by ACPI
    [    0.187294] pci 0000:03:00.0: System wakeup disabled by ACPI
    [    0.196354] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 *9 10 11 14 15)
    [    0.196355] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 10 *11 14 15)
    [    0.196356] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 9 *10 11 14 15)
    [    0.196356] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 *7 9 10 11 14 15)
    [    0.217737] ACPI: Enabled 2 GPEs in block 00 to 0F
    [    0.232381] ACPI: bus type USB registered
    [    0.233003] PCI: Using ACPI for IRQ routing
    [    0.282772] pnp: PnP ACPI init
    [    0.282977] system 00:00: Plug and Play ACPI device, IDs PNP0c02 (active)
    [    0.283011] pnp 00:01: Plug and Play ACPI device, IDs PNP0b00 (active)
    [    0.283029] pnp 00:02: Plug and Play ACPI device, IDs PNP0303 (active)
    [    0.283045] pnp 00:03: Plug and Play ACPI device, IDs VMW0003 PNP0f13 (active)
    [    0.283243] system 00:04: Plug and Play ACPI device, IDs PNP0103 PNP0c01 (active)
    [    0.284307] pnp 00:05: Plug and Play ACPI device, IDs PNP0501 (active)
    [    0.284454] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
    [    0.310818] pnp: PnP ACPI: found 7 devices
    [    0.621061] ACPI: AC Adapter [ACAD] (on-line)
    [    0.621085] ACPI: Power Button [PWRF]
    [user@localhost ~]$
    Thank you,
    _nobody_

  3. #3
    Join Date
    Feb 2012
    Location
    Lexington
    Posts
    66
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: kernel 4.9.6 throws ACPI errors; cannot connect WiFi; core 2 goes near 100%

    Thanks for reply.

    Per your suggestion, I upgraded kernel to 4.9.7-201.fc25.x86_64 . Error conditions still exactly the same.

    I read thread: https://bugs.launchpad.net/ubuntu/+s...x/+bug/1612929 . Only thing I gleaned from there was to use command apport-collect. However, that discussion was for Ubuntu, and that command seems to be Ubuntu/Debian, not Fedora. That thread also suggested upgrading BIOS, but OP had done that with no success.

    I captured dmesg | grep ACPI while the 4.9.7 was running. Here are the results.

    Code snippet too long, trying to attach it as a file.

    Kindly advise.
    Thanks
    JimR
    Attached Files Attached Files

  4. #4
    Join Date
    Mar 2012
    Location
    München, Deutschland
    Posts
    897
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Arrow Re: kernel 4.9.6 throws ACPI errors; cannot connect WiFi; core 2 goes near 100%

    Hello Jim,

    I read your post, and decided to take my own actions. I also inspected your log... But still, I need to work more on it. Not sure if I understand well all in there (probably not), but it is never late at least to try (once you on this path, you benefit).

    [1] I did bring again the latest kernel on my F25 VM. And I also inspected the GRUB2 boot command line:

    [user@localhost ~]$ uname -r
    4.9.7-201.fc25.x86_64
    [user@localhost ~]$ dmesg | grep BOOT
    [ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-4.9.7-201.fc25.x86_64 root=/dev/mapper/fedora-root ro rd.lvm.lv=fedora/root rd.lvm.lv=fedora/swap rhgb quiet LANG=en_US.UTF-8
    [ 0.000000] ACPI: BOOT 0x00000000BFEDF3B4 000028 (v01 PTLTD $SBFTBL$ 06040000 LTP 00000001)
    [ 0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-4.9.7-201.fc25.x86_64 root=/dev/mapper/fedora-root ro rd.lvm.lv=fedora/root rd.lvm.lv=fedora/swap rhgb quiet LANG=en_US.UTF-8
    [user@localhost ~]$
    Since they, at this pointer: https://bugs.launchpad.net/ubuntu/+s...29/comments/32 they speak about the following: adding to the GRUB2 boot line -> acpi=force command.

    And I did it (stopped in GRUB2, then have chosen latest kernel, executed 'e', and add manually into the kernel command line: acpi=force, exiting GRUB2 with <CTRL> <X>, continuing execution). Then compared my two logs, extracted with the command: $ dmesg |grep ACPI. I found that the logs are the same, but the timing is different (acpi=force has longer timing).

    You might try this, and see if this will help you.
    _______

    [2] In order to use iasl ACPI compiler, you have to have this package installed:

    Code:
    [user@localhost ~]$ iasl
    bash: iasl: command not found...
    Install package 'acpica-tools' to provide command 'iasl'? [N/y] y
    
    
     * Waiting in queue... 
     * Loading list of packages.... 
    The following packages have to be installed:
     acpica-tools-20160831-1.fc25.x86_64	ACPICA tools for the development and debug of ACPI tables
    Proceed with changes? [N/y] y
    
     * Waiting in queue... 
     * Waiting for authentication... 
     * Waiting in queue... 
     * Downloading packages... 
     * Requesting data... 
     * Testing changes... 
     * Installing packages... 
    
    Intel ACPI Component Architecture
    ASL+ Optimizing Compiler version 20160831-64
    Copyright (c) 2000 - 2016 Intel Corporation
    
    Supports ACPI Specification Revision 6.1
    
    Usage: iasl [Options] [Files]
    Options:
    
    General:
      -@ <file>           Specify command file
      -I <dir>            Specify additional include directory
      -p <prefix>         Specify path/filename prefix for all output files
      -v                  Display compiler version
      -vd                 Display compiler build date and time
      -vo                 Enable optimization comments
      -vs                 Disable signon
    
    Help:
      -h                  This message
      -hc                 Display operators allowed in constant expressions
      -hd                 Info for obtaining and disassembling binary ACPI tables
      -hf                 Display help for output filename generation
      -hr                 Display ACPI reserved method names
      -ht                 Display currently supported ACPI table names
    
    Preprocessor:
      -D <symbol>         Define symbol for preprocessor use
      -li                 Create preprocessed output file (*.i)
      -P                  Preprocess only and create preprocessor output file (*.i)
      -Pn                 Disable preprocessor
    
    Errors, Warnings, and Remarks:
      -va                 Disable all errors/warnings/remarks
      -ve                 Report only errors (ignore warnings and remarks)
      -vi                 Less verbose errors and warnings for use with IDEs
      -vr                 Disable remarks
      -vw <messageid>     Disable specific warning or remark
      -w <1|2|3>          Set warning reporting level
      -we                 Report warnings as errors
    
    AML Code Generation (*.aml):
      -oa                 Disable all optimizations (compatibility mode)
      -of                 Disable constant folding
      -oi                 Disable integer optimization to Zero/One/Ones
      -on                 Disable named reference string optimization
      -ot                 Disable typechecking
      -cr                 Disable Resource Descriptor error checking
      -in                 Ignore NoOp operators
      -r <revision>       Override table header Revision (1-255)
    
    Listings:
      -l                  Create mixed listing file (ASL source and AML) (*.lst)
      -lm                 Create hardware summary map file (*.map)
      -ln                 Create namespace file (*.nsp)
      -ls                 Create combined source file (expanded includes) (*.src)
      -lx                 Create cross-reference file (*.xrf)
    
    Firmware Support - C Output:
      -tc                 Create hex AML table in C (*.hex)
      -sc                 Create named hex AML arrays in C (*.c)
      -ic                 Create include file in C for -sc symbols (*.h)
      -so                 Create namespace AML offset table in C (*.offset.h)
    
    Firmware Support - Assembler Output:
      -ta                 Create hex AML table in assembler (*.hex)
      -sa                 Create named hex AML arrays in assembler (*.asm)
      -ia                 Create include file in assembler for -sa symbols (*.inc)
    
    Firmware Support - ASL Output:
      -ts                 Create hex AML table in ASL (Buffer object) (*.hex)
    
    Data Table Compiler:
      -G                  Compile custom table that contains generic operators
      -T <sig list>|ALL   Create ACPI table template/example files
      -T <count>          Emit DSDT and <count> SSDTs to same file
      -vt                 Create verbose template files (full disassembly)
    
    AML Disassembler:
      -d  <f1 f2 ...>     Disassemble or decode binary ACPI tables to file (*.dsl)
                            (Optional, file type is automatically detected)
      -da <f1 f2 ...>     Disassemble multiple tables from single namespace
      -db                 Do not translate Buffers to Resource Templates
      -dc <f1 f2 ...>     Disassemble AML and immediately compile it
                            (Obtain DSDT from current system if no input file)
      -df                 Force disassembler to assume table contains valid AML
      -dl                 Emit legacy ASL code only (no C-style operators)
      -e  <f1 f2 ...>     Include ACPI table(s) for external symbol resolution
      -fe <file>          Specify external symbol declaration file
      -in                 Ignore NoOp opcodes
      -l                  Disassemble to mixed ASL and AML code
      -vt                 Dump binary table data in hex format within output file
    
    Debug Options:
      -bf                 Create debug file (full output) (*.txt)
      -bs                 Create debug file (parse tree only) (*.txt)
      -bp <depth>         Prune ASL parse tree
      -bt <type>          Object type to be pruned from the parse tree
      -f                  Ignore errors, force creation of AML output file(s)
      -m <size>           Set internal line buffer size (in Kbytes)
      -n                  Parse only, no output generation
      -oc                 Display compile times and statistics
      -x <level>          Set debug level for trace output
      -z                  Do not insert new compiler ID for DataTables
    
    [user@localhost ~]$
    By query, the package looks like this:

    [user@localhost ~]$ dnf provides */acpica-tools
    Last metadata expiration check: 0:00:30 ago on Wed Feb 8 11:44:40 2017.
    acpica-tools-20160831-1.fc25.x86_64 : ACPICA tools for the development and debug of ACPI tables
    Repo : @System

    acpica-tools-20160831-1.fc25.x86_64 : ACPICA tools for the development and debug of ACPI tables
    Repo : fedora


    [user@localhost ~]$
    So, after you do these two steps, and start experimenting (using iasl) with this web pointer: https://wiki.archlinux.org/index.php/DSDT we'll stop here, NOT to add more and confuse the issue. OK?

    _nobody_

  5. #5
    Join Date
    Feb 2012
    Location
    Lexington
    Posts
    66
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: kernel 4.9.6 throws ACPI errors; cannot connect WiFi; core 2 goes near 100%

    Hi _nobody_, thanks for your reply. Sorry to take so long to respond, life got in my way.

    Code:
    acpi=force, exiting GRUB2 with <CTRL> <X>, continuing execution)
    Tried that, no good, same results.
    I upgraded kernel to 4.9.7, then later 4.9.9. Both produce the same results. 4.9.10 is waiting in the wings, but I hesitate to try it since it will push one of the last working 4.8 versions off.

    In the link you suggested https://wiki.archlinux.org/index.php/DSDT there were a number of suggestions about giving parameters to GRUB2 at startup I tried some of these, but still the same results.

    Other options on that page seem rather dangerous, especially since they recommend taking a full disk backup before beginning. Also these are for Arch Linux. While related, it give me pause. It seems that a wrong keystroke could brick my computer. Do ou truly think that this is the best approach?

    Thanks
    JimR

  6. #6
    Join Date
    Mar 2012
    Location
    München, Deutschland
    Posts
    897
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Question Re: kernel 4.9.6 throws ACPI errors; cannot connect WiFi; core 2 goes near 100%

    Quote Originally Posted by flaflashr
    Hi _nobody_, thanks for your reply. Sorry to take so long to respond, life got in my way.
    Well, Jim, you can't beat the clock. You can delay it for some time... Even to reverse it for a bit. But it always gets to you. And, the most important, if you do NOT solve any (every) problem properly in your ways, they'll come back to bit you hard!

    Quote Originally Posted by flaflashr
    I upgraded kernel to 4.9.7, then later 4.9.9. Both produce the same results. 4.9.10 is waiting in the wings, but I hesitate to try it since it will push one of the last working 4.8 versions off.
    Since it was a long time back... (2.5 weeks, and for me it looks like millennia), I need to recall... But, in the mean time, let me suggest workaround to the statement in RED, CLI transcript follows:

    [user@localhost ~]$ su -m
    Password:
    [root@localhost ~]# cd /etc/dnf
    [root@localhost dnf]# ls -al
    total 28
    drwxr-xr-x. 4 root root 4096 Jan 25 11:02 .
    drwxr-xr-x. 138 root root 12288 Feb 23 09:44 ..
    -rw-r--r--. 1 root root 72 Aug 18 2016 dnf.conf
    drwxr-xr-x. 2 root root 4096 Jan 17 17:19 plugins
    drwxr-xr-x. 2 root root 4096 Jan 25 11:02 protected.d
    [root@localhost dnf]# cat dnf.conf
    [main]
    gpgcheck=1
    installonly_limit=3
    clean_requirements_on_remove=True
    [root@localhost dnf]#
    Please, make statement in red installonly_limit=6. Save this file /etc/dnf/dnf.conf . So you will have the space for 3 extra more kernels. Then, MANDATORY reboot. After rebooting, you'll do the dnf upgrade: installation -> the acceptance will be that you see just 4.9.10 added, no old 4.8.x deleted.

    If this is correct, you then upgrade, and see if this solves your problem... Until I come back with something. I need to rethink...

    _nobody_

  7. #7
    Join Date
    Feb 2012
    Location
    Lexington
    Posts
    66
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: kernel 4.9.6 throws ACPI errors; cannot connect WiFi; core 2 goes near 100%

    I am cautiously optimistic. I went to do the kernel upgrade, and 4.9.11 was already next in queue, so I installed it. I am still getting the ACPI errors at boot and shutdown, but the htop core usage is normal, and best of all, my WiFi connection seems stable. I have shut down and started 3 times now, and wifi is staying connected.

    As a side note, I upped the dnf.conf installonly_limit=9. When I tried the GUI Yum Extender (DNF), it did not honor the setting. It was going to remove my (stable) prior kernels (screen shot attached) . So instead, I went to the command line DNF update, and it correctly honored the limit and did not attempt to remove any old kernels (screen shots alo attached). But I guess this is an issue for a different bug report.

    Do you want to pursue the ACPI errors on this thread?

    Thanks
    JimR
    Attached Thumbnails Attached Thumbnails Click image for larger version. 

Name:	YumExternder_Removing.png 
Views:	152 
Size:	208.6 KB 
ID:	26986   Click image for larger version. 

Name:	dnf_update01.png 
Views:	78 
Size:	23.1 KB 
ID:	26987   Click image for larger version. 

Name:	dnf_update02.png 
Views:	77 
Size:	17.8 KB 
ID:	26988  

  8. #8
    Join Date
    Mar 2012
    Location
    München, Deutschland
    Posts
    897
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Arrow Re: kernel 4.9.6 throws ACPI errors; cannot connect WiFi; core 2 goes near 100%

    Hello Jim,

    There is the following statement, which I can show to you (CLI transcript follows):

    [root@localhost etc]# cat yum.conf
    [main]
    cachedir=/var/cache/yum/$basearch/$releasever
    keepcache=0
    debuglevel=2
    logfile=/var/log/yum.log
    exactarch=1
    obsoletes=1
    gpgcheck=1
    plugins=1
    installonly_limit=5

    # This is the default, if you make this bigger yum won't see if the metadata
    # is newer on the remote and so you'll "gain" the bandwidth of not having to
    # download the new metadata and "pay" for it by yum not having correct
    # information.
    # It is esp. important, to have correct metadata, for distributions like
    # Fedora which don't keep old packages around. If you don't like this checking
    # interupting your command line usage, it's much better to have something
    # manually check the metadata once an hour (yum-updatesd will do this).
    # metadata_expire=90m

    # PUT YOUR REPOS HERE OR IN separate files named file.repo
    # in /etc/yum.repos.d
    [root@localhost etc]#
    My best guess, your yum deprecated is driven by /etc/yum.conf .

    You can continue to inform us, if you do not mind, what is going on with your kernel upgrades till ACPI works 100% correctly.

    Thank you,
    _nobody_

Similar Threads

  1. Yum check throws errors.
    By yakky58 in forum Using Fedora
    Replies: 3
    Last Post: 12th May 2011, 04:57 PM
  2. ACPI with Kernel Modesetting and Wifi
    By mindthrone in forum Hardware
    Replies: 2
    Last Post: 28th November 2010, 09:38 PM
  3. Replies: 19
    Last Post: 12th May 2009, 12:03 AM

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
  •