From: bugzilla-daemon@bugzilla.kernel.org
To: backports@vger.kernel.org
Subject: [Bug 205799] New: kernel panic always in skb_get_hash_perturb entering runlevel 2
Date: Sun, 08 Dec 2019 15:02:53 +0000 [thread overview]
Message-ID: <bug-205799-58281@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=205799
Bug ID: 205799
Summary: kernel panic always in skb_get_hash_perturb entering
runlevel 2
Product: Backports project
Version: unspecified
Kernel Version: 5.3.0-24
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: Backports
Assignee: backports@vger.kernel.org
Reporter: james@time4tea.net
Regression: No
Created attachment 286225
--> https://bugzilla.kernel.org/attachment.cgi?id=286225&action=edit
screenshot of panic stacktrace
Apologies if this is this wrong place to raise this bug.
I upgraded my ubuntu system to 5.3.0-24, and now get always-reproducible panic
on boot entering runlevel 2 in skb_get_hash_perturb.
this using version 8042-0ubuntu1 of backport-iwlwifi-dkms.
the same bug does not appear on 5.3.0-23.
I was unable to get a text version of the stacktrace, but i took a picture -
hopefully this is useful.
--
You are receiving this mail because:
You are the assignee for the bug.--
To unsubscribe from this list: send the line "unsubscribe backports" in
next reply other threads:[~2019-12-08 15:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-08 15:02 bugzilla-daemon [this message]
2019-12-10 15:41 ` [Bug 205799] kernel panic always in skb_get_hash_perturb entering runlevel 2 bugzilla-daemon
2019-12-12 3:15 ` bugzilla-daemon
2019-12-17 0:13 ` bugzilla-daemon
2019-12-17 1:54 ` 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-205799-58281@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=backports@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).