https://bugzilla.kernel.org/show_bug.cgi?id=205657
--- Comment #8 from Zhang Rui (rui.zh...@intel.com) --- (In reply to Pask from comment #0) > > This problem is no longer present by compiling the kernel 3.16.78 (recovered > on https://www.kernel.org). I tested the compilations of several kernel 4.x > and 5.x but this problem comes back. > so this seems like a kernel regression? following is part of the debug trace in your boot dmesg, let's make clear if the trace log is related with the shutdown issue or not first. [ 12.638326] ------------[ cut here ]------------ [ 12.638389] WARNING: CPU: 0 PID: 210 at drivers/ssb/driver_gpio.c:464 ssb_gpio_init.cold+0xa/0x15 [ssb] [ 12.638390] Modules linked in: snd_intel8x0(+) input_leds snd_intel8x0m(+) psmouse b44(+) ssb cfg80211 snd_ac97_codec mmc_core ac97_bus snd_pcm mii yenta_socket libphy rfkill pcmcia_rsrc snd_timer pcmcia pcmcia_core snd sbs(+) soundcore evdev sbshc lpc_ich mac_hid intel_agp intel_gtt rng_core i2c_i801 pcc_cpufreq acpi_cpufreq sg crypto_user ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 sd_mod sr_mod cdrom ata_generic pata_acpi ata_piix firewire_ohci serio_raw atkbd libps2 uhci_hcd libata tifm_7xx1 ehci_pci firewire_core scsi_mod tifm_core crc_itu_t ehci_hcd i8042 serio radeon i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops ttm drm agpgart [ 12.638434] CPU: 0 PID: 210 Comm: systemd-udevd Not tainted 4.19.91-1.0-lts #1 [ 12.638435] Hardware name: Acer Aspire 1680 /Aspire 1680 , BIOS 3A10 10/12/2004 [ 12.638443] EIP: ssb_gpio_init.cold+0xa/0x15 [ssb] [ 12.638446] Code: f7 e8 b1 36 c5 d5 0f 0b 58 e9 b9 ed ff ff 68 64 39 e7 f7 e8 9f 36 c5 d5 0f 0b 5a e9 21 ec ff ff 68 8c 39 e7 f7 e8 8d 36 c5 d5 <0f> 0b 58 83 c8 ff e9 c8 f1 ff ff 68 8c 39 e7 f7 e8 78 36 c5 d5 0f [ 12.638448] EAX: 00000024 EBX: f61d9000 ECX: f6ff0a80 EDX: f6fe9d10 [ 12.638450] ESI: f7e74c68 EDI: f61d9000 EBP: f5b9bc7c ESP: f5b9bc78 [ 12.638452] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 EFLAGS: 00010246 [ 12.638454] CR0: 80050033 CR2: b640d008 CR3: 35b84000 CR4: 000006d0 [ 12.638455] Call Trace: [ 12.638467] ssb_attach_queued_buses+0xe2/0x310 [ssb] [ 12.638473] ssb_bus_register+0x179/0x1d0 [ssb] [ 12.638479] ? ssb_pci_xtal+0x1d0/0x1d0 [ssb] [ 12.638486] ssb_bus_pcibus_register+0x29/0x80 [ssb] [ 12.638492] ssb_pcihost_probe+0xb7/0x110 [ssb] [ 12.638498] pci_device_probe+0xd4/0x160 [ 12.638504] really_probe+0x206/0x360 [ 12.638507] driver_probe_device+0xd9/0x130 [ 12.638510] __driver_attach+0xd9/0x100 [ 12.638513] ? driver_probe_device+0x130/0x130 So can you please confirm if the debug trace always happens in bad kernel, and does not happen in good kernel? Say, back to 3.26.78, which shutdown works, does the log still exists? and does the shutdown problem/trace log still happen in the latest upstream kernel? -- You are receiving this mail because: You are watching the assignee of the bug. _______________________________________________ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
