From mboxrd@z Thu Jan 1 00:00:00 1970 From: Linus Walleij Subject: Re: NULL pointer dereference when 'rmmod gpio_lynxpoint' Date: Wed, 11 May 2016 11:22:02 +0200 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from mail-oi0-f43.google.com ([209.85.218.43]:32864 "EHLO mail-oi0-f43.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932109AbcEKJWE (ORCPT ); Wed, 11 May 2016 05:22:04 -0400 Received: by mail-oi0-f43.google.com with SMTP id v145so57864849oie.0 for ; Wed, 11 May 2016 02:22:02 -0700 (PDT) In-Reply-To: Sender: linux-gpio-owner@vger.kernel.org List-Id: linux-gpio@vger.kernel.org To: Anatol Pomozov Cc: Mathias Nyman , "linux-gpio@vger.kernel.org" , Mika Westerberg , Matt DeVillier On Tue, May 3, 2016 at 5:23 AM, Anatol Pomozov wrote: > On Sun, May 1, 2016 at 11:30 AM, Linus Walleij wrote: >> On Sun, May 1, 2016 at 4:36 PM, Anatol Pomozov wrote: >>> On Sun, May 1, 2016 at 1:38 AM, Linus Walleij wrote: >>>> On Sun, May 1, 2016 at 2:33 AM, Anatol Pomozov wrote: >> >>> Starting from 4.2/4.3 kernel release I see numerous problems with this >>> driver. For example there are regular crashes at the boot time when >>> tries to load this driver https://goo.gl/photos/fGk2U6PgUFtxUk9w5 I >>> have to stick with Arch 4.1 kernel that does not have this problem. >> >> Hm atleast it is not due to my recent refactorings of GPIO then. >> >> Any chance you can run a bisect and nail the commit? > > I compiled lynx gpio into kernel instead of compiling it as a module. > And the system got more stable - I rebooted my devices ~50 times > already and I do not see the boot problem I had before. 'CONFIG_..=y' > definitely makes the situation better. > > As of bisecting - it will require time do find the commit. I might do > it if I find some spare time. If nothing else works I'm happy to accept a patch turning the driver into a bool and removing all module handling code. Yours, Linus Walleij