All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@kernel.org>
To: Johannes Berg <johannes.berg@intel.com>,
	Emmanuel Grumbach <emmanuel.grumbach@intel.com>,
	Luca Coelho <luciano.coelho@intel.com>,
	Intel Linux Wireless <linuxwifi@intel.com>,
	linux-wireless@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: iwlwifi: BUG: unable to handle kernel paging request at ffffc90000e1c808
Date: Fri, 12 Apr 2019 11:49:08 +0200	[thread overview]
Message-ID: <20190412094908.GA5223@dhcp22.suse.cz> (raw)
In-Reply-To: <20190411210404.GC4743@dhcp22.suse.cz>

On Thu 11-04-19 23:07:20, Michal Hocko wrote:
> Hi,
> I have just encountered the following splat with 5.1-rc4. Is this a
> known problem? Greping throug older logs show that "Error sending SCAN_CFG_CMD"
> is not new. In older kernels it was followed by "Start IWL Error Log Dump:"
> but it oopsed now. I was running 5.0 previously. Let me know if you need
> more information.

FTR It happened again with 5.1.0-rc2-00001-ga3ac7917b730

-- 
Michal Hocko
SUSE Labs

  reply	other threads:[~2019-04-12  9:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-11 21:07 iwlwifi: BUG: unable to handle kernel paging request at ffffc90000e1c808 Michal Hocko
2019-04-12  9:49 ` Michal Hocko [this message]
2019-04-16 18:36   ` Michal Hocko
2019-04-17  7:33     ` Luca Coelho
2019-04-17  7:35       ` [PATCH] iwlwifi: don't panic in error path on non-msix systems Luca Coelho
2019-04-17 10:11         ` Michal Hocko
2019-04-17 10:17           ` Luca Coelho
2019-04-17 10:53             ` Luca Coelho
2019-04-17 10:59             ` Michal Hocko
2019-04-22 18:07         ` Michal Hocko
2019-04-22 23:56           ` Kirtika Ruchandani
2019-04-23  2:34             ` Kirtika Ruchandani
2019-04-23 13:27               ` Luca Coelho

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=20190412094908.GA5223@dhcp22.suse.cz \
    --to=mhocko@kernel.org \
    --cc=emmanuel.grumbach@intel.com \
    --cc=johannes.berg@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linuxwifi@intel.com \
    --cc=luciano.coelho@intel.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.