All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Anatol Pomozov <anatol.pomozov@gmail.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	Mathias Nyman <mathias.nyman@linux.intel.com>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	Matt DeVillier <matt.devillier@gmail.com>
Subject: Re: NULL pointer dereference when 'rmmod gpio_lynxpoint'
Date: Thu, 12 May 2016 17:11:24 +0300	[thread overview]
Message-ID: <20160512141124.GU1713@lahna.fi.intel.com> (raw)
In-Reply-To: <CAOMFOmX59DVU4U37jjHpNHLVfhqydNx3SHsMduHWud_rUoHWXw@mail.gmail.com>

On Thu, May 12, 2016 at 06:35:20AM -0700, Anatol Pomozov wrote:
> I use Chromebox with Matt's coreboot firmware and Arch Linux that
> currently compiles LYNX gpio as a module.
>
> There are 2 crashes:
> 1) ~25% chance of crash at boot time. Just boot the device and the
> system crashes when tries to probe the driver
> 2) system crashes when try to 'rmmod'. See stack trace in the first
> message of this thread.

I tried pretty much the same on a Broadwell based machine (uses the same
GPIO driver) and I did not see any crashes. I don't have Haswell based
machines around anymore.

Since you seem to be able get it crashing pretty easily, I wonder if you
can try following to debug the first crash:

 1. Blacklist gpio-lynxpoint
 2. Boot the system
 3. Send me contents of /proc/interrupts and /sys/kernel/debug/gpio
 4. Run 'insmod gpio-lynxpoint.ko'
 5. Send me full dmesg of the crash (if you can get it).

And the second crash:

 1. Remoge gpio-lynxpoint from blacklist
 2. Boot the system
 3. Run 'rmmod gpio-lynxpoint'
 4. Send me full dmesg of the crash (if you can get it).

Hopefully with that information we can find root cause of both crashes
(which may be the same).

  reply	other threads:[~2016-05-12 14:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-01  0:33 NULL pointer dereference when 'rmmod gpio_lynxpoint' Anatol Pomozov
2016-05-01  8:38 ` Linus Walleij
2016-05-01 14:36   ` Anatol Pomozov
2016-05-01 18:30     ` Linus Walleij
2016-05-03  3:23       ` Anatol Pomozov
2016-05-11  9:22         ` Linus Walleij
     [not found]           ` <CAOMFOmWTvH0ObHjnBAbKkew79oFN4OMrjou5x6V1HRc=CnP91w@mail.gmail.com>
2016-05-11 14:02             ` Mika Westerberg
2016-05-12 13:35               ` Anatol Pomozov
2016-05-12 14:11                 ` Mika Westerberg [this message]
2016-05-12 10:34             ` Mathias Nyman
2016-05-24 11:03               ` Linus Walleij
2016-05-11 14:26           ` Anatol Pomozov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160512141124.GU1713@lahna.fi.intel.com \
    --to=mika.westerberg@linux.intel.com \
    --cc=anatol.pomozov@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=mathias.nyman@linux.intel.com \
    --cc=matt.devillier@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.