All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: James Hogan <jhogan@kernel.org>,
	<intel-wired-lan@lists.osuosl.org>,
	Sasha Neftin <sasha.neftin@intel.com>,
	"Gomes, Vinicius" <vinicius.gomes@intel.com>
Cc: Jesse Brandeburg <jesse.brandeburg@intel.com>
Subject: Re: [Intel-wired-lan] I225-V (igc driver) hangs after resume in igc_resume/igc_tsn_reset
Date: Fri, 15 Jul 2022 10:25:34 -0700	[thread overview]
Message-ID: <2fd6595a-ce3b-46d9-0d63-e034c9a85958@intel.com> (raw)
In-Reply-To: <4752347.31r3eYUQgx@saruman>

Adding a couple people who work on igc.

On 7/14/2022 1:14 AM, James Hogan wrote:
> Hi,
> 
> I'm getting regular hangs after resume from suspend with the igc driver, for
> an I225-V (rev 3) on an MSI Pro Z690-A, with version 5.18.11 on archlinux. A few
> stable versions ago it was possible to get the network back up by removing and
> reloading the igc driver, however now I get the following, and only a reboot
> works (which itself hangs before actually restarting the machine, and requires
> a hard reset).
> 
> Any ideas?
> 
> INFO: task NetworkManager:1139 blocked for more than 124 seconds.
>        Not tainted 5.18.11-arch1-1 #1
> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> task:NetworkManager  state:D stack:    0 pid: 1139 ppid:     1 flags:0x00004002
> Call Trace:
>   <TASK>
>   __schedule+0x37c/0x11f0
>   schedule+0x4f/0xb0
>   schedule_preempt_disabled+0x15/0x20
>   __mutex_lock.constprop.0+0x2d0/0x480
>   ? igc_tsn_reset+0x64/0x100 [igc c7b6f7549edcf5dd76637367233bb9aa57fc35fd]
>   igc_resume+0xf6/0x1d0 [igc c7b6f7549edcf5dd76637367233bb9aa57fc35fd]
>   pci_pm_runtime_resume+0xab/0xd0
>   ? pci_pm_freeze_noirq+0xe0/0xe0
>   __rpm_callback+0x41/0x160
>   rpm_callback+0x35/0x70
>   ? pci_pm_freeze_noirq+0xe0/0xe0
>   rpm_resume+0x5e6/0x820
>   __pm_runtime_resume+0x4b/0x80
>   dev_ethtool+0x128/0x3060
>   ? inet_ioctl+0xdc/0x1e0
>   dev_ioctl+0x157/0x520
>   sock_do_ioctl+0xd7/0x120
>   sock_ioctl+0xee/0x330
>   ? syscall_exit_to_user_mode+0x26/0x50
>   ? do_syscall_64+0x6b/0x90
>   ? syscall_exit_to_user_mode+0x26/0x50
>   __x64_sys_ioctl+0x8e/0xc0
>   do_syscall_64+0x5c/0x90
>   ? do_syscall_64+0x6b/0x90
>   ? do_syscall_64+0x6b/0x90
>   ? do_syscall_64+0x6b/0x90
>   ? syscall_exit_to_user_mode+0x26/0x50
>   ? do_syscall_64+0x6b/0x90
>   entry_SYSCALL_64_after_hwframe+0x44/0xae
> RIP: 0033:0x7f5d37b077af
> RSP: 002b:00007ffd791600f0 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
> RAX: ffffffffffffffda RBX: 00007ffd791603e0 RCX: 00007f5d37b077af
> RDX: 00007ffd79160210 RSI: 0000000000008946 RDI: 0000000000000013
> RBP: 00007ffd79160390 R08: 0000000000000000 R09: 00007ffd791603e8
> R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
> R13: 00007ffd79160210 R14: 00007ffd791601f0 R15: 00007ffd791601f0
>   </TASK>
> 
> Thanks
> James
> 
> 
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan

  reply	other threads:[~2022-07-15 17:26 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-14  8:14 [Intel-wired-lan] I225-V (igc driver) hangs after resume in igc_resume/igc_tsn_reset James Hogan
2022-07-15 17:25 ` Tony Nguyen [this message]
2022-07-17 19:59 ` Vinicius Costa Gomes
     [not found]   ` <4773114.31r3eYUQgx@saruman>
2022-07-23 15:52     ` James Hogan
2022-07-27 14:37       ` Vinicius Costa Gomes
2022-07-28 17:36         ` James Hogan
2022-08-04 13:03           ` James Hogan
2022-08-04 13:27             ` Paul Menzel
2022-08-04 21:41               ` James Hogan
2022-08-04 22:07                 ` James Hogan
2022-08-05 11:25                   ` James Hogan
2022-08-11 15:13                     ` [Intel-wired-lan] [PATCH] igc: fix deadlock caused by taking RTNL in RPM resume path Vinicius Costa Gomes
2022-08-11 18:58                       ` kernel test robot
2022-08-11 18:58                         ` kernel test robot
2022-08-11 19:59                       ` kernel test robot
2022-08-11 20:25                       ` [Intel-wired-lan] [WIP v2] " Vinicius Costa Gomes
2022-08-11 21:41                         ` James Hogan
2022-08-13  0:05                           ` Vinicius Costa Gomes
2022-08-13 17:18                             ` James Hogan
2022-08-29  8:16                               ` James Hogan
2022-10-02 10:56                                 ` James Hogan
2023-08-14 11:04                                   ` James Hogan
2023-08-29  1:58                                     ` Vinicius Costa Gomes
2023-09-03 17:57                                       ` James Hogan

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=2fd6595a-ce3b-46d9-0d63-e034c9a85958@intel.com \
    --to=anthony.l.nguyen@intel.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jesse.brandeburg@intel.com \
    --cc=jhogan@kernel.org \
    --cc=sasha.neftin@intel.com \
    --cc=vinicius.gomes@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.