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 07:59:49 +0000 [thread overview]
Message-ID: <bug-209981-201763-vsGU4bMoHh@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-209981-201763@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=209981
Aaron Dominick (aaron.zakhrov@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |OBSOLETE
--- Comment #6 from Aaron Dominick (aaron.zakhrov@gmail.com) ---
(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
--
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2020-11-02 7:59 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
2020-11-02 5:12 ` Dave Chinner
2020-11-02 5:31 ` bugzilla-daemon
2020-11-02 7:59 ` bugzilla-daemon [this message]
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-vsGU4bMoHh@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.