Bug 209981 - Unable to boot with kernel 5.10-r1
Summary: Unable to boot with kernel 5.10-r1
Status: RESOLVED OBSOLETE
Alias: None
Product: File System
Classification: Unclassified
Component: XFS (show other bugs)
Hardware: All Linux
: P1 high
Assignee: FileSystem/XFS Default Virtual Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-10-31 10:12 UTC by Aaron Dominick
Modified: 2020-11-02 07:59 UTC (History)
2 users (show)

See Also:
Kernel Version: 5.10-rc1
Subsystem:
Regression: No
Bisected commit-id:


Attachments
journalctl captured till lock up (153.66 KB, text/plain)
2020-10-31 10:12 UTC, Aaron Dominick
Details
lsblk tree (1.45 KB, text/plain)
2020-10-31 10:12 UTC, Aaron Dominick
Details

Description Aaron Dominick 2020-10-31 10:12:22 UTC
Created attachment 293333 [details]
journalctl captured till lock up

I have a Dell G5 15 SE with a Samsung PM99 NVME SSD. When I try to compile and boot with Linux kernel 5.10-rc1 or 5.10 git my computer locks up after entering the password to decrypt my encrypted root partition. 
Kernels before 5.10-rc1 work just fine. There is no kernel panic but xfs keeps stalling
Comment 1 Aaron Dominick 2020-10-31 10:12:57 UTC
Created attachment 293335 [details]
lsblk tree
Comment 2 Eric Sandeen 2020-11-02 00:09:27 UTC
Why do you feel this is an xfs bug?  I don't see any indication of xfs problems in your logs.
Comment 3 Eric Sandeen 2020-11-02 00:12:10 UTC
The journal log indicates you had a failure in the iwlwifi code.
Comment 4 Aaron Dominick 2020-11-02 05:02:06 UTC
(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
Comment 5 Dave Chinner 2020-11-02 05:31:24 UTC
On Mon, Nov 02, 2020 at 05:02:06AM +0000, bugzilla-daemon@bugzilla.kernel.org wrote:
> 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

Your kernel oopsed trying to load firmware for the iwl driver.
Everything after that is colateral damage. Sort out the firmware
loading problem first because once that problem goes away all the
others should, too.

Cheers,

Dave.
Comment 6 Aaron Dominick 2020-11-02 07:59:49 UTC
(In reply to Dave Chinner from comment #5)
> On Mon, Nov 02, 2020 at 05:02:06AM +0000,
> bugzilla-daemon@bugzilla.kernel.org wrote:
> > 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
> 
> Your kernel oopsed trying to load firmware for the iwl driver.
> Everything after that is colateral damage. Sort out the firmware
> loading problem first because once that problem goes away all the
> others should, too.
> 
> Cheers,
> 
> Dave.

OK my bad. 5.10-rc2 seems to work fine

Note You need to log in before you can comment on or make changes to this bug.