Description of problem: This error pops up in the automatic error report tool several times a day. The machine is Thinkpad R61, Nvidia graphics, using noveau. Freschly installed a week ago, updated, only fedora packages. I do not know if it is related, but *sometimes* the system reboots while waking from sleep (in RAM). I have now installed kdump to try to catch something. The system was recently running mageia 4, diffrence is that on mageia only X crashed and restarted sometimes after sleep, and occasionally it hung then, while fc20 reboots. I also have a T61 that show same problem on mageia, so probably not broken hardware. Both here and in mageia bugzilla there are bug reports with different issues waking from reboot on a few different systems. On mageia I tried both noveau and nvidia proprietary drivers, same problem. Additional info: reporter: libreport-2.2.2 WARNING: CPU: 0 PID: 1 at drivers/pnp/pnpacpi/core.c:97 pnpacpi_set_resources+0x13d/0x150() Modules linked in: CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.14.2-200.fc20.x86_64 #1 Hardware name: LENOVO 8918DFG/8918DFG, BIOS 7KETA9WW (2.09 ) 12/27/2007 0000000000000000 0000000004e64ef1 ffff88007c7bfc30 ffffffff816eec92 0000000000000000 ffff88007c7bfc68 ffffffff8108a1bd ffff88007c334400 ffff88007d03cd20 ffffffff81ca9e20 0000000000000000 0000000000000000 Call Trace: [<ffffffff816eec92>] dump_stack+0x45/0x56 [<ffffffff8108a1bd>] warn_slowpath_common+0x7d/0xa0 [<ffffffff8108a2ea>] warn_slowpath_null+0x1a/0x20 [<ffffffff8140acfd>] pnpacpi_set_resources+0x13d/0x150 [<ffffffff814084d2>] pnp_start_dev+0x42/0x80 [<ffffffff81408c78>] pnp_activate_dev+0x38/0x50 [<ffffffff814071a0>] pnp_device_probe+0x90/0xd0 [<ffffffff81464e25>] driver_probe_device+0x125/0x3a0 [<ffffffff81465173>] __driver_attach+0x93/0xa0 [<ffffffff814650e0>] ? __device_attach+0x40/0x40 [<ffffffff81462c53>] bus_for_each_dev+0x73/0xc0 [<ffffffff814647de>] driver_attach+0x1e/0x20 [<ffffffff81464390>] bus_add_driver+0x180/0x250 [<ffffffff81d6f0ad>] ? serial8250_console_init+0x19/0x19 [<ffffffff814657f4>] driver_register+0x64/0xf0 [<ffffffff81d6f0ad>] ? serial8250_console_init+0x19/0x19 [<ffffffff81406fa0>] pnp_register_driver+0x20/0x30 [<ffffffff81446c65>] serial8250_pnp_init+0x15/0x20 [<ffffffff81d6f10a>] serial8250_init+0x5d/0x1a4 [<ffffffff81d6f0ad>] ? serial8250_console_init+0x19/0x19 [<ffffffff8100216a>] do_one_initcall+0xfa/0x1b0 [<ffffffff810ac165>] ? parse_args+0x225/0x3f0 [<ffffffff81d261a3>] kernel_init_freeable+0x1ab/0x247 [<ffffffff81d25926>] ? do_early_param+0x88/0x88 [<ffffffff816dfe20>] ? rest_init+0x80/0x80 [<ffffffff816dfe2e>] kernel_init+0xe/0xf0 [<ffffffff816fef7c>] ret_from_fork+0x7c/0xb0 [<ffffffff816dfe20>] ? rest_init+0x80/0x80
Created attachment 892192 [details] File: dmesg
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs. Fedora 20 has now been rebased to 3.14.4-200.fc20. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those.
Still valid. The crash on resume problem: Bug 1096989
what info can i provide?
Today, from journalctl -k: jul 01 12:48:16 bamse kernel: ------------[ cut here ]------------ jul 01 12:48:16 bamse kernel: WARNING: CPU: 1 PID: 1 at drivers/pnp/pnpacpi/core.c:96 pnpacpi_set_resources+0x16a/0x180() jul 01 12:48:16 bamse kernel: Modules linked in: jul 01 12:48:16 bamse kernel: CPU: 1 PID: 1 Comm: swapper/0 Not tainted 3.14.9-200.fc20.x86_64 #1 jul 01 12:48:16 bamse kernel: Hardware name: LENOVO 8918DFG/8918DFG, BIOS 7KETC9WW (2.29 ) 04/07/2010 jul 01 12:48:16 bamse kernel: 0000000000000000 00000000ac5fb366 ffff88007c7bfc20 ffffffff816ef90e jul 01 12:48:16 bamse kernel: 0000000000000000 ffff88007c7bfc58 ffffffff8108a0fd 0000000000000000 jul 01 12:48:16 bamse kernel: ffff88007d03cd98 ffff88007c350000 0000000000000000 0000000000000000 jul 01 12:48:16 bamse kernel: Call Trace: jul 01 12:48:16 bamse kernel: [<ffffffff816ef90e>] dump_stack+0x45/0x56 jul 01 12:48:16 bamse kernel: [<ffffffff8108a0fd>] warn_slowpath_common+0x7d/0xa0 jul 01 12:48:16 bamse kernel: [<ffffffff8108a22a>] warn_slowpath_null+0x1a/0x20 jul 01 12:48:16 bamse kernel: [<ffffffff8140ae6a>] pnpacpi_set_resources+0x16a/0x180 jul 01 12:48:16 bamse kernel: [<ffffffff81408622>] pnp_start_dev+0x42/0x80 jul 01 12:48:16 bamse kernel: [<ffffffff81408dc8>] pnp_activate_dev+0x38/0x50 jul 01 12:48:16 bamse kernel: [<ffffffff814072f0>] pnp_device_probe+0x90/0xd0 jul 01 12:48:16 bamse kernel: [<ffffffff81464fed>] driver_probe_device+0x12d/0x3d0 jul 01 12:48:16 bamse kernel: [<ffffffff81465363>] __driver_attach+0x93/0xa0 jul 01 12:48:16 bamse kernel: [<ffffffff814652d0>] ? __device_attach+0x40/0x40 jul 01 12:48:16 bamse kernel: [<ffffffff81462e13>] bus_for_each_dev+0x73/0xc0 jul 01 12:48:16 bamse kernel: [<ffffffff8146499e>] driver_attach+0x1e/0x20 jul 01 12:48:16 bamse kernel: [<ffffffff81464550>] bus_add_driver+0x180/0x250 jul 01 12:48:16 bamse kernel: [<ffffffff81d6f035>] ? serial8250_console_init+0x19/0x19 jul 01 12:48:16 bamse kernel: [<ffffffff814659e4>] driver_register+0x64/0xf0 jul 01 12:48:16 bamse kernel: [<ffffffff81d6f035>] ? serial8250_console_init+0x19/0x19 jul 01 12:48:16 bamse kernel: [<ffffffff814070f0>] pnp_register_driver+0x20/0x30 jul 01 12:48:16 bamse kernel: [<ffffffff81446ec5>] serial8250_pnp_init+0x15/0x20 jul 01 12:48:16 bamse kernel: [<ffffffff81d6f092>] serial8250_init+0x5d/0x1a4 jul 01 12:48:16 bamse kernel: [<ffffffff81d6f035>] ? serial8250_console_init+0x19/0x19 jul 01 12:48:16 bamse kernel: [<ffffffff8100216a>] do_one_initcall+0xfa/0x1b0 jul 01 12:48:16 bamse kernel: [<ffffffff810ac105>] ? parse_args+0x225/0x3f0 jul 01 12:48:16 bamse kernel: [<ffffffff81d26188>] kernel_init_freeable+0x190/0x22c jul 01 12:48:16 bamse kernel: [<ffffffff81d25926>] ? do_early_param+0x88/0x88 jul 01 12:48:16 bamse kernel: [<ffffffff816e0a60>] ? rest_init+0x80/0x80 jul 01 12:48:16 bamse kernel: [<ffffffff816e0a6e>] kernel_init+0xe/0xf0 jul 01 12:48:16 bamse kernel: [<ffffffff816ffb7c>] ret_from_fork+0x7c/0xb0 jul 01 12:48:16 bamse kernel: [<ffffffff816e0a60>] ? rest_init+0x80/0x80 jul 01 12:48:16 bamse kernel: ---[ end trace 179bd11e4698b52d ]---
Sometimes the "97" in the message is "96" instead, i.e drivers/pnp/pnpacpi/core.c:96 pnpacpi_set_resources+0x13d/0x150()
This should be fixed by "ACPI / PNP: Fix acpi_pnp_match()" in 3.16.0, 3.15.9, and 3.14.16. commit b6328a07bd6b3d31b64f85864fe74f3b08c010ca Author: Rafael J. Wysocki <rafael.j.wysocki> Date: Wed Jul 30 00:23:09 2014 +0200 ACPI / PNP: Fix acpi_pnp_match() The acpi_pnp_match() function is used for finding the ACPI device object that should be associated with the given PNP device. Unfortunately, the check used by that function is not strict enough and may cause success to be returned for a wrong ACPI device object. To fix that, use the observation that the pointer to the ACPI device object in question is already stored in the data field in struct pnp_dev, so acpi_pnp_match() can simply use that field to do its job. This problem was uncovered in 3.14 by commit 202317a573b2 (ACPI / scan: Add acpi_device objects for all device nodes in the namespace). Fixes: 202317a573b2 (ACPI / scan: Add acpi_device objects for all device nodes in the namespace) Reported-and-tested-by: Vinson Lee <vlee> Cc: 3.14+ <stable.org> # 3.14+ Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki>
Thanks for the pointer Vinson. All Fedora releases should have an update that contains the fix in the according stable kernel version, so it would be great if someone could verify that.