Created attachment 276835 [details] ACPI dump Asus K501UB (This bug is reported as Red Hat Bugzilla #1594572) Description of problem: The current kernel 4.17.2 does not recognise the internal keyboard and trackpad of the Asus K501UB laptop, rendering the machine useless on the go. Input works from an external keyboard and mouse. Machine works fine with kernel 4.16. Version-Release number of selected component (if applicable): Any Fedora kernel newer than (including) kernel-4.17.0-0.rc0.git4.1.fc29, - Linux v4.16-9576-g38c23685b273. This commit identifier is the result of installing various pre-release kernel RPMs, not of a proper git bisect. How reproducible: Type. Steps to Reproduce: 1. Start machine 2. Type (In my case: hard drive decryption key) Actual results: None Expected results: Many Additional information: - Allocating an IDR fails with [ 8.886249] couldn't get idr A likely condition for this to happen is to be called with a "start" integer smaller than 0. For I2C devices this is set to adap->nr, unless adap->nr is -1, in which case it's assigned to __i2c_first_dynamic_bus_num. - __i2c_first_dynamic_bus_num does not have a default value and is only initialised in i2c_register_board_info(). If due to ACPI problems this function is never called, it could default to anything including a negative number, causing the allocation to fail. Does it make sense to assign a default value to __i2c_first_dynamic_bus_num regardless of whether ACPI needs fixing? - Semi-related: I've also lost a lot of suspend modes. 4.16 reports "ACPI: (supports S0 S3 S4 S5)", 4.17 reports ACPI: (supports S0). There many warnings in the logs leading up to that.
Created attachment 276837 [details] GOOD dmesg for kernel 4.16.16
Created attachment 276839 [details] BAD dmesg for kernel 4.17.2
Created attachment 276927 [details] GOOD dmesg for kernel 4.17.3 Symptoms have vanished with kernel 4.17.3, thanks! There's still a few warnings left in the dmesg logs (attached), but those are of much lower urgency now that the system works correctly again.
so I guess the bug can be closed?