Netdev List
 help / color / mirror / Atom feed
From: Skyler Hawthorne <skyler@dead10ck.com>
To: Marc Haber <mh+netdev@zugschlus.de>,
	linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
	netdev@vger.kernel.org
Subject: Re: iwl_mvm_add_new_dqa_stream_wk BUG in lib/list_debug.c:56
Date: Mon, 01 Jul 2019 07:34:11 -0700	[thread overview]
Message-ID: <7cc8efb985c2e770a328919e1b99d93f30d7295a.camel@dead10ck.com> (raw)
In-Reply-To: <20190625130317.GB31363@torres.zugschlus.de>

Hello, I'm also still experiencing this issue on 5.1.15. It's making it
very difficult to use my work laptop in my office, since it has many
access points and frequently has to reauthenticate. I hit this bug 1-3
times per day, and the only way to fix it is a hard shutdown. Has there
been any effort to identify and/or fix the cause?

-- 
Skyler

On Tue, 2019-06-25 at 15:03 +0200, Marc Haber wrote:
> On Sun, Jun 02, 2019 at 03:48:42PM +0200, Marc Haber wrote:
> > On Thu, May 30, 2019 at 10:12:57AM +0200, Marc Haber wrote:
> > > on my primary notebook, a Lenovo X260, with an Intel Wireless
> > > 8260
> > > (8086:24f3), running Debian unstable, I have started to see
> > > network
> > > hangs since upgrading to kernel 5.1. In this situation, I cannot
> > > restart Network-Manager (the call just hangs), I can log out of
> > > X, but
> > > the system does not cleanly shut down and I need to Magic SysRq
> > > myself
> > > out of the running system. This happens about once every two
> > > days.
> > 
> > The issue is also present in 5.1.5 and 5.1.6.
> 
> Almost a month later, 5.1.15 still crashes about twice a day on my
> Notebook. The error message seems pretty clear to me, how can I go on
> from there and may be identify a line number outside of a library?
> 
> Greetings
> Marc
> 
> 


      reply	other threads:[~2019-07-01 14:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-30  8:12 iwl_mvm_add_new_dqa_stream_wk BUG in lib/list_debug.c:56 Marc Haber
2019-06-02 13:48 ` Marc Haber
2019-06-07 20:20   ` Yussuf Khalil
2019-06-07 20:44     ` Marc Haber
2019-07-12  9:57       ` Luciano Coelho
2019-06-25 13:03   ` Marc Haber
2019-07-01 14:34     ` Skyler Hawthorne [this message]

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=7cc8efb985c2e770a328919e1b99d93f30d7295a.camel@dead10ck.com \
    --to=skyler@dead10ck.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mh+netdev@zugschlus.de \
    --cc=netdev@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox