Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp2886748ybi; Sun, 9 Jun 2019 23:54:28 -0700 (PDT) X-Google-Smtp-Source: APXvYqwHTvICIy3KrU1VP2jVt14QMfcGjg9Y9mdAvaPpHrzHPeDW3hccCs3sc+r4YyLs+YQNuc9s X-Received: by 2002:a17:902:9885:: with SMTP id s5mr68873699plp.102.1560149668267; Sun, 09 Jun 2019 23:54:28 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1560149668; cv=none; d=google.com; s=arc-20160816; b=nggVvKjrCQdVOU29xrkcbZsgMfBmPQto0wnnDxV8vCobRJ3EQJoUhQ9rOeIjka8PS/ QfMlWQr4JI17Vy1zLz/zt3McIWOKNUImh55kPUAXQzOlfmeWtCjAbZ0G9/Mm+L65Dae8 8QE0XNm61yrohbx76FCl5EVPS3szePbU1LNEelFrLCE3qXmu+1dvYVLvhEWvkhrOxrMs 5Eg3oOGg7NBRLIAo5BtnV+kT0emML/mWyNfApOTz4i8Py6jsqIXm8kL2rOaD6Qi4LQZg X6VQhmsoJvkBNURl0WFTS5XDABLKCqmK0W9VldmxeURyBzJZq93X8VbCfQyKrVHrAuIS YEhA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=hpJ8laeRMo44o7Xfh9K1uH3yYvR4RdIiGg456hvouTw=; b=gzOs5wu1PDJVLnf9vMDx23yTlmhYpyUmNnhHjBsmlpXu2MYmQJLx5IQ/tkBcRtwCvI rST1zdFFV2jBhxKY+5KYPEv+PmPkhMJSEi9G1me5//yPhrD1qbwLg6TMvmxLJl1JB2hw xPXJIjI1UtTxnKbOfZX96Fejr2Un0GHtvZ8+HSnF2ItOOGxcGg2ngbIgGPD9bs3JG3ed 0+w5+rnzasX/C8s1O6a0NuWcw4hZfCjGUnf4a7o2vaK4bO4HS8IIWuPKFiHqqpVdHlgq o5h05w5N8uNA1Og5oztlWGxC4vvRbfXHhI0gcMCDhSugoRmuovQPPWGtEzIp6ZrBVQbF 7MjA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=XSe6WvK7; spf=pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id k7si8646759pll.145.2019.06.09.23.54.13; Sun, 09 Jun 2019 23:54:28 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=XSe6WvK7; spf=pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2387839AbfFJGu2 (ORCPT + 99 others); Mon, 10 Jun 2019 02:50:28 -0400 Received: from mail-vs1-f45.google.com ([209.85.217.45]:34255 "EHLO mail-vs1-f45.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2387718AbfFJGu2 (ORCPT ); Mon, 10 Jun 2019 02:50:28 -0400 Received: by mail-vs1-f45.google.com with SMTP id q64so4683539vsd.1 for ; Sun, 09 Jun 2019 23:50:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=hpJ8laeRMo44o7Xfh9K1uH3yYvR4RdIiGg456hvouTw=; b=XSe6WvK7p0WEAabV7k68XmK5ElwQhbgn18t6ZIoun5MUwvbXM1KLtcbCry/XUTLyS5 1nu7cwxho+cyFXfnd2F7p3wNDrGJrxL9GVGJgplE7syMtWCAzNHw3lof3oy7JoudwtV3 q4cUSEcNBghGYM7bu4ZCN7m0ERKWMU+qaNn+A7urbGzuxZrtc5RKLotKWHcag4ddEU+W XCkt8Z0E/xILRtGl8GN9Xt6gkIBEYsS1ntYslmjFCjTUV+kgIKC5p+fPZ75U2cQjHgpE Nt3ZFBQOy+KT5DcWuMPa/0wm+6JukPyVQ7rEiE9H5aglki/c87PMbt6ZvU4Pp1MH4PhN rwqg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=hpJ8laeRMo44o7Xfh9K1uH3yYvR4RdIiGg456hvouTw=; b=ps3T2A9srhDaNJWNF3EqURf4vCKVzFyalPa9kswbdcC1ZkLTjt9jAjP1+E9h36YTCk ZlOjhfrXCGa7JxTyCuxD22iTPe+05FGZmTwq0u3nfYwM899ey1B9OtzMDtYR0xn9oz5q ybONUUKEZCx/GcJ8LG94rPhG5YYPRqH/o+SuB5hHMPTNQDd4nS76/bgdhK0cyC1x5Coj XaiF04h+kTIVC9Zhp9SX/RmQPcm0vfROZGQ0Gzu2MKY7B1CFSDjaQnwOASZEP3X+sxKj iSfO3V71oMVoDi4wANHmi4MjXH/yrSwCjKQHP+KD+jpunChtuHZxF95XMMvXt9ukSWmh caEg== X-Gm-Message-State: APjAAAVYXAq6pr/+r0aLcp8pKpCfOsO10NzCvqqWZ0SyaNtc4EP99+fV ZphvdWFWNmMMbDBSsR6xH41QB4mll9/bjf7iEids+0IxJ7Dckg== X-Received: by 2002:a67:e244:: with SMTP id w4mr8965940vse.176.1560149427063; Sun, 09 Jun 2019 23:50:27 -0700 (PDT) MIME-Version: 1.0 References: <2455026.F8Aexx8IWb@zadesk> <2696773.yqXG4m880n@zadesk> In-Reply-To: <2696773.yqXG4m880n@zadesk> From: Emmanuel Grumbach Date: Mon, 10 Jun 2019 09:50:13 +0300 Message-ID: Subject: Re: iwlwifi module crash To: Balakrishnan Balasubramanian Cc: linux-wireless Content-Type: text/plain; charset="UTF-8" Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org On Fri, Jun 7, 2019 at 2:41 PM Balakrishnan Balasubramanian wrote: > > > This is because the device is removed from the PCI bus. Nothing from > > iwlwifi side can be done. > > I am sure the device is not physically disturbed. If that was the case, should it not stay down when restarting the system? Not necessarily. The disturbance may impact ASPM or something alike. > > > If that happens upon suspend / resume, I know there are been fixes in > > PCI bus driver. > > To my knowledge I have disabled all power/suspend features and I don't see releated logs in journal except the below. Not sure if relevant. > > Jun 03 21:33:14 zadesk kernel: wlan0: Limiting TX power to 14 (17 - 3) dBm as advertised by d4:5d:df:25:ee:90 > > Is there a way to restart the module safely without restarting the system? echo 1 > /sys/module/iwlwifi/devices/0000\:02\:00.0/remove echo 1 > /sys/bus/pci/rescan > > Regards, > Bala > > > On Friday, June 7, 2019 5:25:41 AM EDT Emmanuel Grumbach wrote: > > On Fri, Jun 7, 2019 at 5:22 AM Balakrishnan Balasubramanian > > > > wrote: > > > I am using iwd demon for wifi. Once a while I loose connectivity. > > > Restarting the demon does not help. But once I restart the system, it > > > starts working fine. Attaching stack trace from journal. > > > > This is because the device is removed from the PCI bus. Nothing from > > iwlwifi side can be done. > > If that happens upon suspend / resume, I know there are been fixes in > > PCI bus driver. If not, check that the device sits correctly in its > > socket. > > > > > Regards, > > > Bala > > > > > > > > > ---------- Forwarded message ---------- > > > From: Denis Kenzior > > > To: Balakrishnan Balasubramanian , iwd@lists.01.org > > > Cc: > > > Bcc: > > > Date: Thu, 06 Jun 2019 18:07:40 -0500 > > > Subject: Re: iwd crashes randomly > > > Hi Bala, > > > > > > On 06/06/2019 06:00 PM, Balakrishnan Balasubramanian wrote: > > > > Sometimes after a week and sometimes after two days. Once crashed, > > > > restarting the service does not help. Had to restart the computer. > > > > Attaching stack trace from journal. > > > > > > That implies that your kernel is crashing, not iwd. The attached log > > > shows a kernel stack trace somewhere inside iwlwifi module. I would > > > post this trace to linux-wireless@vger.kernel.org. > > > > > > If you have an associated iwd backtrace, then certainly post this here, > > > but if the kernel module is crashing, there isn't much we can do. > > > > > > Regards, > > > -Denis > > > >