From: bugzilla-daemon@bugzilla.kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 209981] Unable to boot with kernel 5.10-r1
Date: Mon, 02 Nov 2020 05:02:06 +0000 [thread overview]
Message-ID: <bug-209981-201763-tzBjyBEau6@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-209981-201763@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=209981
--- Comment #4 from Aaron Dominick (aaron.zakhrov@gmail.com) ---
(In reply to Eric Sandeen from comment #2)
> Why do you feel this is an xfs bug? I don't see any indication of xfs
> problems in your logs.
I dont think the logs are being captured. Basically after I boot and enter my
lvm password, the system locks up with a bunch of pending in flight requests.
Among them are the xfs_buf_ioend_work
480.364103) pug : cpus nodee flags=8x0 nice act live-2/256 refont-3 pend Ing:
dbs_Mork_handler, URstat shepherd
180.3641031
480.3641031
480.3641031
workqueue events_unbound: flags-x2 puq 32: cpus=0-15 flags-ex4 nice 6 active
1/512 refcnt-6
480.3641031 in-flight: 84:fsnotify connector destroy world
funotify_connector_destroy_um 480.3611031 workqueue events_freezable: flags=0x1
I 488.364103) puj 6: cpus 3 node-0 flags-Ox0 nice-e active=1/256 refcnt-2
180.3641031
pending: pci_pme_1ist_scan
I 180.3641031 workqueue rcu gp: flags ex8
pug 6: cpu node-0 flags-ex0 nice-e active=1/256 refent-2 488.3641031 pend ing:
process_srcu 480.3641031 workqueue percpu vg: flags-ex8
480.3641031
480.364103) puj 6: cpus-3 mode flags-exe nice act lue=2/256 refont-4
480.3641031 pending: umstat_update. Iru_add_drain_per_cpu BARC102) puq 0: cpus=
node0 flags Ox0 nice-0 active 1/256 refent-2 E 480.3641031 pending:
unstat_update E 180.3641031 workqueue ur iteback: flags-xta 480.3641031 pug 32:
cpus=0-15 flags-0x1 nice o active 1/256 refcnt-3
180.3641631
E180.364103) in-flight: 1582 :ub workin
480.364103) workqueue kdnf lush: flags-x8 pg 6: cpus 3 node-0 Flags x0 nice to
actlue-1/256 refcnt-2 [ 480.364163) pend ing: dn_ Mork And nod) 400.3641031
workqueue xfs-buf/dn1: flags Oxc
480.3641031
480.3641031
480.3641031
100.364183)
pag 6: cpus 3 node o flags Ox0 nice e act lue-1/1 regent 3 pending: xfs
buf_loend_Mork Exfs) delayed: xfs_buf_loend uork Exfs)
180.3641031 workqueue xfs-conan 1: flags-Oxc I 480.36A103) puq 14: cpus-7
node=0 flags-ex0 nice-e active=1/256 refent-2
I 180.3641031 in-flight: 1331 Exis_end_lo xfs 180.3641031 porqueue
xfs-cilddr-4: Flags Oxe
pug 32: cpus-0-15 flags-Ox1 nice- active=1/256 refent-1 in-Flight: B6:xlog
cil_push_vork Exfs) BARC 1593) I 180.3641031 workqueue xfs-eofblocks/dn-4:
flags-Oxe
180.3641e3)
I 100.364103)
400.364103) 180.3641031 pug 6: cpus=3 node-o flags Ox0 nice-e active 1/256
refent-2
pend ing: xfs_cofblocks_Morker Exfs) 180.S55570) worqueue xs- cdn-1: flagsx1
100.5666701
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2020-11-02 5:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-31 10:12 [Bug 209981] New: Unable to boot with kernel 5.10-r1 bugzilla-daemon
2020-10-31 10:12 ` [Bug 209981] " bugzilla-daemon
2020-11-02 0:09 ` bugzilla-daemon
2020-11-02 0:12 ` bugzilla-daemon
2020-11-02 5:02 ` bugzilla-daemon [this message]
2020-11-02 5:12 ` Dave Chinner
2020-11-02 5:31 ` bugzilla-daemon
2020-11-02 7:59 ` bugzilla-daemon
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=bug-209981-201763-tzBjyBEau6@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-xfs@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 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.