From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760265AbcIZFiL convert rfc822-to-8bit (ORCPT ); Mon, 26 Sep 2016 01:38:11 -0400 Received: from ni.piap.pl ([195.187.100.4]:58708 "EHLO ni.piap.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752313AbcIZFiK (ORCPT ); Mon, 26 Sep 2016 01:38:10 -0400 From: khalasa@piap.pl (Krzysztof =?utf-8?Q?Ha=C5=82asa?=) To: Andrey Utkin Cc: Hans Verkuil , Andrey Utkin , linux-kernel@vger.kernel.org, linux-media@vger.kernel.org, Mauro Carvalho Chehab , Hans Verkuil , Ismael Luceno , Bluecherry Maintainers Subject: Re: solo6010 modprobe lockup since e1ceb25a (v4.3 regression) References: <20160915130441.ji3f3jiiebsnsbct@acer> <9cbb2079-f705-5312-d295-34bc3c8dadb9@xs4all.nl> <20160921134554.s3tdolyej6r2w5wh@zver> <20160922152356.nhgacxprxtvutb67@zver> Date: Mon, 26 Sep 2016 07:38:05 +0200 In-Reply-To: <20160922152356.nhgacxprxtvutb67@zver> (Andrey Utkin's message of "Thu, 22 Sep 2016 18:23:56 +0300") Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8BIT X-KLMS-Rule-ID: 1 X-KLMS-Message-Action: clean X-KLMS-AntiSpam-Lua-Profiles: 103351 [Sep 26 2016] X-KLMS-AntiSpam-Version: 5.6.0.28 X-KLMS-AntiSpam-Envelope-From: khalasa@piap.pl X-KLMS-AntiSpam-Rate: 0 X-KLMS-AntiSpam-Status: not_detected X-KLMS-AntiSpam-Method: none X-KLMS-AntiSpam-Info: LuaCore: 114 114 9222339828e48414c7ed910e427388be64f1ccbe, Auth:dkim=none X-KLMS-AntiSpam-Interceptor-Info: scan successful X-KLMS-AntiPhishing: Clean, 2016/09/23 07:28:51 X-KLMS-AntiVirus: Kaspersky Security 8.0 for Linux Mail Server, version 8.0.1.721, bases: 2016/09/26 01:07:00 #7876322 X-KLMS-AntiVirus-Status: Clean, skipped Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Andrey Utkin writes: > On Thu, Sep 22, 2016 at 10:51:37AM +0200, Krzysztof HaƂasa wrote: >> I wonder if the following fixes the problem (completely untested). > > I have given this a run, and it still hangs. Does (only) adding the pci_read_config_word(solo_dev->pdev, PCI_STATUS, &val); in solo_reg_write() help? -- Krzysztof Halasa Industrial Research Institute for Automation and Measurements PIAP Al. Jerozolimskie 202, 02-486 Warsaw, Poland