Bug 205799 - kernel panic always in skb_get_hash_perturb entering runlevel 2
Summary: kernel panic always in skb_get_hash_perturb entering runlevel 2
Status: NEW
Alias: None
Product: Backports project
Classification: Unclassified
Component: Backports (show other bugs)
Hardware: x86-64 Linux
: P1 high
Assignee: Backports Project Mailing List
Depends on:
Reported: 2019-12-08 15:02 UTC by James Richardson
Modified: 2019-12-17 01:54 UTC (History)
2 users (show)

See Also:
Kernel Version: 5.3.0-24
Tree: Mainline
Regression: No

screenshot of panic stacktrace (3.20 MB, image/jpeg)
2019-12-08 15:02 UTC, James Richardson
proposed patch (3.96 KB, patch)
2019-12-10 15:41 UTC, You-Sheng Yang
Details | Diff

Description James Richardson 2019-12-08 15:02:53 UTC
Created attachment 286225 [details]
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.
Comment 1 You-Sheng Yang 2019-12-10 15:41:56 UTC
Created attachment 286243 [details]
proposed patch

PPA: https://launchpad.net/~vicamo/+archive/ubuntu/ppa-gitlab-backport-iwlwifi-dkms-7/+packages (still building)
Comment 2 You-Sheng Yang 2019-12-12 03:15:19 UTC
Re-filed as https://bugzilla.kernel.org/show_bug.cgi?id=205839
Comment 3 Hauke Mehrtens 2019-12-17 00:13:29 UTC
This is already fixed here:

and also backported to the 4.19 branch.
I am missing the Ubuntu extras, would be nice if you could send them as a patch. Are you using some other version than 4.19 or 5.4-rcX?
Comment 4 You-Sheng Yang 2019-12-17 01:54:38 UTC
@Hauke, this was intended for backport-iwlwifi[1], so I re-filed as bug 205839 under wireless component.

[1]: https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/backport-iwlwifi.git/

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