Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Jesse Brandeburg <jesse.brandeburg@intel.com>,
	anthony.l.nguyen@intel.com
Cc: intel-wired-lan@lists.osuosl.org
Subject: [Intel-wired-lan] Fw: [Bug 205073] igb driver hang
Date: Mon, 12 Dec 2022 13:23:38 -0800	[thread overview]
Message-ID: <20221212132338.26a9f3a0@hermes.local> (raw)



Begin forwarded message:

Date: Mon, 12 Dec 2022 18:58:10 +0000
From: bugzilla-daemon@kernel.org
To: stephen@networkplumber.org
Subject: [Bug 205073] igb driver hang


https://bugzilla.kernel.org/show_bug.cgi?id=205073

Perlover (perlover@perlover.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |perlover@perlover.com

--- Comment #7 from Perlover (perlover@perlover.com) ---
Hello!
Same problem
Ubuntu 20.04 LTE
Kernel: 5.4.0-135-generic

Stack trace:

Dec 12 18:58:05 AH15 kernel: [4699248.577166] igb 0000:01:00.1 internal: PCIe
link lost
Dec 12 18:58:05 AH15 kernel: [4699248.577230] igb 0000:01:00.1 internal:
malformed Tx packet detected and dropped, LVMMC:0xffffffff
Dec 12 18:58:05 AH15 kernel: [4699249.473382] igb 0000:01:00.0 external: PCIe
link lost
Dec 12 18:58:05 AH15 kernel: [4699249.473446] ------------[ cut here
]------------
Dec 12 18:58:05 AH15 kernel: [4699249.473448] igb: Failed to read reg 0xc030!
Dec 12 18:58:05 AH15 kernel: [4699249.473538] WARNING: CPU: 21 PID: 501169 at
drivers/net/ethernet/intel/igb/igb_main.c:756 igb_rd32.cold+0x3a/0x46 [igb]
Dec 12 18:58:05 AH15 kernel: [4699249.473540] Modules linked in: ufs qnx4
hfsplus hfs minix ntfs msdos jfs xfs cpuid binfmt_misc nf_log_ipv6 ip6t_REJECT
nf_reject_ipv6 xt_hl ip6t_rt nf_log_ipv4 nf_log_common ipt_REJECT
nf_reject_ipv4 xt_LOG xt_limit xt_addrtype xt_tcpudp ip6table_filter ip6_tables
xt_recent xt_connt>
Dec 12 18:58:05 AH15 kernel: [4699249.473596]  crypto_simd usbhid cryptd
glue_helper igb ahci libsas drm hid i2c_i801 libahci megaraid_sas lpc_ich
scsi_transport_sas dca i2c_algo_bit
Dec 12 18:58:05 AH15 kernel: [4699249.473613] CPU: 21 PID: 501169 Comm:
kworker/21:1 Not tainted 5.4.0-128-generic #144-Ubuntu
Dec 12 18:58:05 AH15 kernel: [4699249.473615] Hardware name: Supermicro
X9DR3-F/X9DR3-F, BIOS 1.0c 06/29/2012
Dec 12 18:58:05 AH15 kernel: [4699249.473626] Workqueue: events
igb_watchdog_task [igb]
Dec 12 18:58:05 AH15 kernel: [4699249.473638] RIP: 0010:igb_rd32.cold+0x3a/0x46
[igb]
Dec 12 18:58:05 AH15 kernel: [4699249.473643] Code: c7 c6 c2 01 4b c0 e8 da da
23 e2 48 8b bb 30 ff ff ff e8 94 cf cc e1 84 c0 74 16 44 89 ee 48 c7 c7 d0 0e
4b c0 e8 a2 de 1e e2 <0f> 0b e9 12 3c fe ff e9 29 3c fe ff 8b b3 14 18 00 00 49
8d bc 24
Dec 12 18:58:05 AH15 kernel: [4699249.473645] RSP: 0018:ffffb1c9cf1abdb0
EFLAGS: 00010282
Dec 12 18:58:05 AH15 kernel: [4699249.473648] RAX: 0000000000000000 RBX:
ffffa05c6ced0e08 RCX: 0000000000000006
Dec 12 18:58:05 AH15 kernel: [4699249.473650] RDX: 0000000000000007 RSI:
0000000000000092 RDI: ffffa05c7fa5c8c0
Dec 12 18:58:05 AH15 kernel: [4699249.473652] RBP: ffffb1c9cf1abdc8 R08:
0000000000039e75 R09: 0000000000000004
Dec 12 18:58:05 AH15 kernel: [4699249.473654] R10: 0000000000000000 R11:
0000000000000001 R12: 00000000ffffffff
Dec 12 18:58:05 AH15 kernel: [4699249.473655] R13: 000000000000c030 R14:
0000000000000000 R15: ffffa05c78909f00
Dec 12 18:58:05 AH15 kernel: [4699249.473659] FS:  0000000000000000(0000)
GS:ffffa05c7fa40000(0000) knlGS:0000000000000000
Dec 12 18:58:05 AH15 kernel: [4699249.473661] CS:  0010 DS: 0000 ES: 0000 CR0:
0000000080050033
Dec 12 18:58:05 AH15 kernel: [4699249.473662] CR2: 00007f7d7617f000 CR3:
0000000e61c0a006 CR4: 00000000000606e0
Dec 12 18:58:05 AH15 kernel: [4699249.473665] Call Trace:
Dec 12 18:58:05 AH15 kernel: [4699249.473680]  igb_update_stats+0x78/0x820
[igb]
Dec 12 18:58:05 AH15 kernel: [4699249.473689]  igb_watchdog_task+0xa8/0x410
[igb]
Dec 12 18:58:05 AH15 kernel: [4699249.473697]  ? __schedule+0x2eb/0x740
Dec 12 18:58:05 AH15 kernel: [4699249.473705]  process_one_work+0x1eb/0x3b0
Dec 12 18:58:05 AH15 kernel: [4699249.473710]  worker_thread+0x4d/0x400
Dec 12 18:58:05 AH15 kernel: [4699249.473715]  kthread+0x104/0x140
Dec 12 18:58:05 AH15 kernel: [4699249.473719]  ? process_one_work+0x3b0/0x3b0
Dec 12 18:58:05 AH15 kernel: [4699249.473722]  ? kthread_park+0x90/0x90
Dec 12 18:58:05 AH15 kernel: [4699249.473726]  ret_from_fork+0x35/0x40
Dec 12 18:58:05 AH15 kernel: [4699249.473729] ---[ end trace f6253424685efc67
]---
Dec 12 18:58:05 AH15 kernel: [4699249.473740] igb 0000:01:00.0 external:
malformed Tx packet detected and dropped, LVMMC:0xffffffff
Dec 12 18:58:07 AH15 kernel: [4699250.561446] igb 0000:01:00.1 internal:
malformed Tx packet detected and dropped, LVMMC:0xffffffff

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan

                 reply	other threads:[~2022-12-12 21:23 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20221212132338.26a9f3a0@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=anthony.l.nguyen@intel.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jesse.brandeburg@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox