bisecting fixing commit since aec3002d07fd2564cd32e56f126fa6db14a168bb building syzkaller on cccc4302d7da39e2fc41f9275442c267935632b7 testing commit aec3002d07fd2564cd32e56f126fa6db14a168bb with gcc (GCC) 8.1.0 kernel signature: 0c26e1f8ca852a3cad1dd93ba38a377f1c211dd4 all runs: crashed: INFO: task hung in blkdev_issue_flush testing current HEAD 174651bdf802a2139065e8e31ce950e2f3fc4a94 testing commit 174651bdf802a2139065e8e31ce950e2f3fc4a94 with gcc (GCC) 8.1.0 kernel signature: 8553a7a06459909e1e4c0e13080356aa19fc021b all runs: OK # git bisect start 174651bdf802a2139065e8e31ce950e2f3fc4a94 aec3002d07fd2564cd32e56f126fa6db14a168bb Bisecting: 1835 revisions left to test after this (roughly 11 steps) [ad58ce6cacd1b7447054f35fa6bb39f6b655a941] nvme-multipath: fix ana log nsid lookup when nsid is not found testing commit ad58ce6cacd1b7447054f35fa6bb39f6b655a941 with gcc (GCC) 8.1.0 kernel signature: c4291eeeb4049da859dcae0547b810163fcf7dfb run #0: crashed: WARNING in mq_flush_data_end_io run #1: OK run #2: OK run #3: OK run #4: OK run #5: OK run #6: OK run #7: OK run #8: OK run #9: OK # git bisect good ad58ce6cacd1b7447054f35fa6bb39f6b655a941 Bisecting: 917 revisions left to test after this (roughly 10 steps) [1a48aaabf1cd75d831b0d9b3005a2b0c9f831123] i2c: acpi: Force bus speed to 400KHz if a Silead touchscreen is present testing commit 1a48aaabf1cd75d831b0d9b3005a2b0c9f831123 with gcc (GCC) 8.1.0 kernel signature: 4ef0f21bce4984b12c62d6a1c85a98ebf5991a25 all runs: OK # git bisect bad 1a48aaabf1cd75d831b0d9b3005a2b0c9f831123 Bisecting: 458 revisions left to test after this (roughly 9 steps) [24ca6289203266875c35d018ab01b872e302a6d6] mac80211: Reject malformed SSID elements testing commit 24ca6289203266875c35d018ab01b872e302a6d6 with gcc (GCC) 8.1.0 kernel signature: 03995fe2d153f39ae552ec655dd9abd6dfd97525 all runs: OK # git bisect bad 24ca6289203266875c35d018ab01b872e302a6d6 Bisecting: 229 revisions left to test after this (roughly 8 steps) [561bf9309209e174035eaee0edfc3247ecfdff76] crypto: caam - fix concurrency issue in givencrypt descriptor testing commit 561bf9309209e174035eaee0edfc3247ecfdff76 with gcc (GCC) 8.1.0 kernel signature: d0eafe49900310061f1e0eb639d644c3f74fdd7b all runs: OK # git bisect bad 561bf9309209e174035eaee0edfc3247ecfdff76 Bisecting: 114 revisions left to test after this (roughly 7 steps) [782a77f2eb39207589ef9175a2ceadd0cca12112] drm/amd/display: reprogram VM config when system resume testing commit 782a77f2eb39207589ef9175a2ceadd0cca12112 with gcc (GCC) 8.1.0 kernel signature: f2893907aa676384612fc1b9c3e9296fdc958984 all runs: OK # git bisect bad 782a77f2eb39207589ef9175a2ceadd0cca12112 Bisecting: 56 revisions left to test after this (roughly 6 steps) [3c54f463402f5469827b245675062576c2502c49] ASoC: Intel: NHLT: Fix debug print format testing commit 3c54f463402f5469827b245675062576c2502c49 with gcc (GCC) 8.1.0 kernel signature: 855ba6b2142f84efa268d17ea31462bb742dbef3 all runs: OK # git bisect bad 3c54f463402f5469827b245675062576c2502c49 Bisecting: 28 revisions left to test after this (roughly 5 steps) [8630a4d13683095fbf14091d59a20e1ac71fdd6b] media: ttusb-dec: Fix info-leak in ttusb_dec_send_command() testing commit 8630a4d13683095fbf14091d59a20e1ac71fdd6b with gcc (GCC) 8.1.0 kernel signature: aa022f805b124b526d7f45fddd77ad46d2359f22 all runs: OK # git bisect bad 8630a4d13683095fbf14091d59a20e1ac71fdd6b Bisecting: 13 revisions left to test after this (roughly 4 steps) [b21919eeced69af1d2562415fc34fbc833c24e21] s390/crypto: xts-aes-s390 fix extra run-time crypto self tests finding testing commit b21919eeced69af1d2562415fc34fbc833c24e21 with gcc (GCC) 8.1.0 kernel signature: e81c997822a72cdca11506d4d1a7f3abedd5e3df all runs: OK # git bisect bad b21919eeced69af1d2562415fc34fbc833c24e21 Bisecting: 6 revisions left to test after this (roughly 3 steps) [e4467fb6ef547aa352dc03397f9474ec84eced5b] ACPI: custom_method: fix memory leaks testing commit e4467fb6ef547aa352dc03397f9474ec84eced5b with gcc (GCC) 8.1.0 kernel signature: ca70ba32f965d7e400cdbb20dcb9f2004026a665 run #0: crashed: WARNING in mq_flush_data_end_io run #1: OK run #2: OK run #3: OK run #4: OK run #5: OK run #6: OK run #7: OK run #8: OK run #9: OK # git bisect good e4467fb6ef547aa352dc03397f9474ec84eced5b Bisecting: 3 revisions left to test after this (roughly 2 steps) [76cf93f04c3dedc29660fed2c26fdbc21f604725] hwmon: (acpi_power_meter) Change log level for 'unsafe software power cap' testing commit 76cf93f04c3dedc29660fed2c26fdbc21f604725 with gcc (GCC) 8.1.0 kernel signature: f052007b9a72fc2661108b7ba09573cb2d35e18e all runs: OK # git bisect bad 76cf93f04c3dedc29660fed2c26fdbc21f604725 Bisecting: 0 revisions left to test after this (roughly 1 step) [f0956418d9975fdc83343c12639edcb55310d27b] closures: fix a race on wakeup from closure_sync testing commit f0956418d9975fdc83343c12639edcb55310d27b with gcc (GCC) 8.1.0 kernel signature: 67255d7cf56328fc7ebc4a8bbde3e93e86834ab9 run #0: crashed: WARNING in mq_flush_data_end_io run #1: OK run #2: OK run #3: OK run #4: OK run #5: OK run #6: OK run #7: OK run #8: OK run #9: OK # git bisect good f0956418d9975fdc83343c12639edcb55310d27b 76cf93f04c3dedc29660fed2c26fdbc21f604725 is the first bad commit commit 76cf93f04c3dedc29660fed2c26fdbc21f604725 Author: Wang Shenran Date: Wed Jul 24 11:01:10 2019 +0300 hwmon: (acpi_power_meter) Change log level for 'unsafe software power cap' [ Upstream commit 6e4d91aa071810deac2cd052161aefb376ecf04e ] At boot time, the acpi_power_meter driver logs the following error level message: "Ignoring unsafe software power cap". Having read about it from a few sources, it seems that the error message can be quite misleading. While the message can imply that Linux is ignoring the fact that the system is operating in potentially dangerous conditions, the truth is the driver found an ACPI_PMC object that supports software power capping. The driver simply decides not to use it, perhaps because it doesn't support the object. The best solution is probably changing the log level from error to warning. All sources I have found, regarding the error, have downplayed its significance. There is not much of a reason for it to be on error level, while causing potential confusions or misinterpretations. Signed-off-by: Wang Shenran Link: https://lore.kernel.org/r/20190724080110.6952-1-shenran268@gmail.com Signed-off-by: Guenter Roeck Signed-off-by: Sasha Levin drivers/hwmon/acpi_power_meter.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) kernel signature: f052007b9a72fc2661108b7ba09573cb2d35e18e previous signature: 67255d7cf56328fc7ebc4a8bbde3e93e86834ab9 revisions tested: 13, total time: 4h0m36.276600901s (build: 1h47m27.069654544s, test: 2h8m17.574621209s) first good commit: 76cf93f04c3dedc29660fed2c26fdbc21f604725 hwmon: (acpi_power_meter) Change log level for 'unsafe software power cap' cc: ["jdelvare@suse.com" "linux-hwmon@vger.kernel.org" "linux-kernel@vger.kernel.org" "linux@roeck-us.net" "sashal@kernel.org" "shenran268@gmail.com"]