Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#49171 - [linux] Powering off failing with kernel 4.5

Attached to Project: Arch Linux
Opened by Colin Pitrat (LiFo2) - Sunday, 01 May 2016, 22:53 GMT
Last edited by Tobias Powalowski (tpowa) - Sunday, 26 June 2016, 05:47 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas Bächler (brain0)
Architecture i686
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Since upgrade to linux-4.5-1, my Asus EEE PC will not poweroff anymore.
Upgrading further to linux-4.5.1-1 didn't solve the issue.
Downgrading to linux-4.4.5 fixes the issue.

The only odd thing I could find by comparing dmesg of both versions with the 4.5 kernels is this:
mai 01 23:15:46 pitrat4 kernel: asus_wmi: ASUS WMI generic driver loaded
mai 01 23:15:46 pitrat4 kernel: BUG: unable to handle kernel NULL pointer dereference at 00000094
(...)
mai 01 23:15:48 pitrat4 kernel: IP: [<f8bfb241>] sch_gpio_probe+0x161/0x280 [gpio_sch]
mai 01 23:15:48 pitrat4 kernel: *pde = 00000000
mai 01 23:15:48 pitrat4 kernel: Oops: 0000 [#1] PREEMPT SMP
mai 01 23:15:48 pitrat4 kernel: Modules linked in: eeepc_wmi(+) gpio_sch(+) libps2 asus_wmi irqbypass snd_hda_codec cfg80211 snd_hda_core pcspkr at
mai 01 23:15:48 pitrat4 kernel: CPU: 1 PID: 235 Comm: systemd-udevd Not tainted 4.5.1-1-ARCH #1
mai 01 23:15:48 pitrat4 kernel: Hardware name: ASUSTeK Computer INC. 1201HA/1201HA, BIOS 0302 02/05/2010
mai 01 23:15:49 pitrat4 kernel: task: f5402d00 ti: f4e50000 task.ti: f4e50000
mai 01 23:15:49 pitrat4 kernel: EIP: 0060:[<f8bfb241>] EFLAGS: 00010246 CPU: 1
mai 01 23:15:49 pitrat4 kernel: EIP is at sch_gpio_probe+0x161/0x280 [gpio_sch]
mai 01 23:15:49 pitrat4 kernel: EAX: 0000000a EBX: f5656e4c ECX: 00000000 EDX: 0000000e
mai 01 23:15:49 pitrat4 kernel: ESI: f8bfc0cc EDI: 00000000 EBP: f4e51cb4 ESP: f4e51c98
mai 01 23:15:49 pitrat4 kernel: DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
mai 01 23:15:49 pitrat4 kernel: CR0: 80050033 CR2: 00000094 CR3: 34e25000 CR4: 000006d0
mai 01 23:15:49 pitrat4 kernel: Stack:
mai 01 23:15:50 pitrat4 kernel: 00000040 f4e211b0 f4e2100c f4e21000 f4e2100c f8bfd014 f4e2100c f4e51cd0
mai 01 23:15:51 pitrat4 kernel: c1387b13 f4e51cd0 c13850e2 f4e2100c 00000000 f8bfd014 f4e51d04 c1385b49
mai 01 23:15:53 pitrat4 kernel: 00000000 f4e51cf0 c130a6ac f4e2100c f8bfd014 00000000 f4e51d04 00000025
mai 01 23:15:53 pitrat4 kernel: Call Trace:
mai 01 23:15:54 pitrat4 kernel: [<c1387b13>] platform_drv_probe+0x43/0xb0
mai 01 23:15:55 pitrat4 kernel: [<c13850e2>] ? driver_sysfs_add+0x62/0x80
mai 01 23:15:56 pitrat4 kernel: [<c1385b49>] driver_probe_device+0x1f9/0x450
mai 01 23:15:57 pitrat4 kernel: [<c130a6ac>] ? acpi_driver_match_device+0x31/0x4b
mai 01 23:15:58 pitrat4 kernel: [<c1385e19>] __driver_attach+0x79/0x80
mai 01 23:15:58 pitrat4 kernel: [<c1385da0>] ? driver_probe_device+0x450/0x450
mai 01 23:15:58 pitrat4 kernel: [<c13839a7>] bus_for_each_dev+0x57/0xa0
mai 01 23:15:59 pitrat4 kernel: [<c13852be>] driver_attach+0x1e/0x20
mai 01 23:15:59 pitrat4 kernel: [<c1385da0>] ? driver_probe_device+0x450/0x450
mai 01 23:15:59 pitrat4 kernel: [<c1384dcf>] bus_add_driver+0x1ef/0x290
mai 01 23:15:59 pitrat4 kernel: [<f815c000>] ? 0xf815c000
mai 01 23:15:59 pitrat4 kernel: [<f815c000>] ? 0xf815c000
mai 01 23:16:00 pitrat4 kernel: [<c138670d>] driver_register+0x5d/0xf0
mai 01 23:16:00 pitrat4 kernel: [<c1387a7f>] __platform_driver_register+0x2f/0x40
mai 01 23:16:00 pitrat4 kernel: [<f815c012>] sch_gpio_driver_init+0x12/0x1000 [gpio_sch]
mai 01 23:16:01 pitrat4 kernel: [<c100047a>] do_one_initcall+0xaa/0x200
mai 01 23:16:01 pitrat4 kernel: [<f815c000>] ? 0xf815c000
mai 01 23:16:01 pitrat4 kernel: [<c115f525>] ? kvfree+0x45/0x50
mai 01 23:16:01 pitrat4 kernel: [<c11938be>] ? kmem_cache_alloc_trace+0x7e/0x1f0
mai 01 23:16:01 pitrat4 kernel: [<c1140fe9>] ? do_init_module+0x21/0x1a8
mai 01 23:16:01 pitrat4 kernel: [<c1140fe9>] ? do_init_module+0x21/0x1a8
mai 01 23:16:01 pitrat4 kernel: [<c1141018>] do_init_module+0x50/0x1a8
mai 01 23:16:02 pitrat4 kernel: [<c10e1cfc>] load_module+0x204c/0x25b0
mai 01 23:16:02 pitrat4 kernel: [<c10e2387>] SyS_init_module+0x127/0x180
mai 01 23:16:02 pitrat4 kernel: [<c1001b3d>] do_fast_syscall_32+0x8d/0x150
mai 01 23:16:02 pitrat4 kernel: [<c150b187>] sysenter_past_esp+0x40/0x61
mai 01 23:16:02 pitrat4 kernel: Code: ff ff 5b 5e 5f 5d c3 8d 76 00 8b 7b 10 31 c0 ba 0e 00 00 00 66 89 83 92 00 00 00 b8 0a 00 00 00 66 89 53 4c 6
mai 01 23:16:03 pitrat4 kernel: EIP: [<f8bfb241>] sch_gpio_probe+0x161/0x280 [gpio_sch] SS:ESP 0068:f4e51c98
mai 01 23:16:03 pitrat4 kernel: CR2: 0000000000000094
mai 01 23:16:03 pitrat4 kernel: ---[ end trace 159ce0d925c94927 ]---


This task depends upon

Closed by  Tobias Powalowski (tpowa)
Sunday, 26 June 2016, 05:47 GMT
Reason for closing:  Upstream
Comment by Colin Pitrat (LiFo2) - Sunday, 01 May 2016, 22:55 GMT
Could very well be linked to this commit:
https://github.com/torvalds/linux/commit/f5b3f66548b72f8ab77fea5867bd45ad91ed2143#diff-a746f90c9503689310ee8f3bdc77bc4e

The commit itself seems correct (the macro removed is defined in another header) but:
- the releases matches (included in 4.5)
- the change is in the module where I get the BUG
- the Oops stack is about platform_drv_probe which is where the macro is called

So I don't understand how this would cause the issue but this seems like a good candidate.
Comment by Doug Newgard (Scimmia) - Monday, 02 May 2016, 13:44 GMT
Have you taken this upstream? Little/nothing will happen here until upstream fixes it.
Comment by Colin Pitrat (LiFo2) - Monday, 02 May 2016, 21:14 GMT
Reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=117531

Loading...