mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Kai-Heng Feng <kai.heng.feng@canonical.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Regression caused by commit bc976233a872, ethernet r8169 stops working after system S3
Date: Fri, 30 Mar 2018 21:51:33 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.21.1803302137510.1479@nanos.tec.linutronix.de> (raw)
In-Reply-To: <E3F55561-8733-4056-ABEC-5AF87AC288CB@canonical.com>

On Sat, 31 Mar 2018, Kai-Heng Feng wrote:
> A user reported [1] that the Realtek ethernet r8169 stops working after S3
> since v4.15-rc6. The issue still exists in Linus' tree:
> 
> [ 150.877998] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
> [ 150.944101] do_IRQ: 3.37 No irq handler for vector
> [ 150.944105] r8169 0000:01:00.0 enp1s0: link down
> [ 150.944180] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
> 
> My desktop also has this device, which is also affected by this regression. So
> I did a bisect, and this is the bad commit:
> bc976233a872 genirq/msi x86/vector: Prevent reservation mode for non maskable
> MSI
> 
> After this commit gets reverted, the issue is gone.

Sigh. Can you please apply the debug patch below and provide the output of

# cat /proc/interrupts

and full dmesg after resume.

Thanks,

	tglx

8<------------------
--- a/kernel/irq/cpuhotplug.c
+++ b/kernel/irq/cpuhotplug.c
@@ -134,6 +134,10 @@ static bool migrate_one_irq(struct irq_d
 		brokeaff = false;
 	}
 
+	pr_info("IRQ%u: New affinity: %*pbl effective: %*pbl\n",
+		cpumask_pr_args(affinity),
+		irq_data_get_effective_affinity_mask(d));
+
 	if (maskchip && chip->irq_unmask)
 		chip->irq_unmask(d);
 

  reply	other threads:[~2018-03-30 19:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-30 19:04 Kai-Heng Feng
2018-03-30 19:51 ` Thomas Gleixner [this message]
2018-03-31 15:35   ` Kai-Heng Feng
2018-04-03  8:51     ` Thomas Gleixner
2018-04-11  3:46       ` Kai Heng Feng

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=alpine.DEB.2.21.1803302137510.1479@nanos.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=kai.heng.feng@canonical.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®