Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 655058 - >=sys-kernel/gentoo-sources-4.15.16 - "random" crashes on boot
Summary: >=sys-kernel/gentoo-sources-4.15.16 - "random" crashes on boot
Status: UNCONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: AMD64 Linux
: Normal normal (vote)
Assignee: Gentoo Kernel Bug Wranglers and Kernel Maintainers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-05-06 10:58 UTC by Sora Lee
Modified: 2018-06-13 23:41 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
Kernel .config (config,106.09 KB, text/plain)
2018-05-06 11:01 UTC, Sora Lee
Details
emerge --info (system.log,7.96 KB, text/x-log)
2018-05-06 11:02 UTC, Sora Lee
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Sora Lee 2018-05-06 10:58:26 UTC
sys-kernel/gentoo-sources-4.15.15 compiles and boots with no issues at all, but all subsequent versions kernel panic during early boot. I have attached pictures of the debug messages for 5 consecutive boot attempts, as well as the output of `emerge --info` and my kernel .config file.
Comment 1 Sora Lee 2018-05-06 11:01:54 UTC
Created attachment 530172 [details]
Kernel .config
Comment 2 Sora Lee 2018-05-06 11:02:32 UTC
Created attachment 530174 [details]
emerge --info
Comment 4 Jeroen Roovers gentoo-dev 2018-05-07 04:51:29 UTC
Look like "random" problems in the kernel. It seems to get further into the boot process sometimes and other times it crashes really early on at boot.
Comment 5 Sora Lee 2018-05-25 09:59:03 UTC
I'm going to do a bit more digging when I have the time to see whats going on, but for would it be possible to have the 4.15.15 ebuild restored?
Comment 6 Mike Pagano gentoo-dev 2018-05-25 13:42:27 UTC
(In reply to Sora Lee from comment #5)
> I'm going to do a bit more digging when I have the time to see whats going
> on, but for would it be possible to have the 4.15.15 ebuild restored?

No, I don't want our users to think that's it's OK to run any version 4.15.X.
I plan on removing all of 4.15.X in the next day or so.

That said, you can just get it from git and then either create a local overlay or place it in your portage tree directly.

Note that if you do place it in your portage tree directly, it will go away on the next sync.

https://gitweb.gentoo.org/repo/gentoo.git/commit/sys-kernel/gentoo-sources?id=dc4118a1edc78f1a857fd73353b0eb79f895f24f

Can you test the latest 4.16.X kernel ?

If that fails, you can try a bisect
Comment 7 Sora Lee 2018-05-26 05:00:17 UTC
Issue is with the following section of 1015_linux-4.15.16.patch:

diff --git a/drivers/crypto/ccp/ccp-crypto-rsa.c b/drivers/crypto/ccp/ccp-crypto-rsa.c
index e6db8672d89c..05850dfd7940 100644
--- a/drivers/crypto/ccp/ccp-crypto-rsa.c
+++ b/drivers/crypto/ccp/ccp-crypto-rsa.c
@@ -60,10 +60,9 @@ static int ccp_rsa_complete(struct crypto_async_request *async_req, int ret)
 
 static unsigned int ccp_rsa_maxsize(struct crypto_akcipher *tfm)
 {
-	if (ccp_version() > CCP_VERSION(3, 0))
-		return CCP5_RSA_MAXMOD;
-	else
-		return CCP_RSA_MAXMOD;
+	struct ccp_ctx *ctx = akcipher_tfm_ctx(tfm);
+
+	return ctx->u.rsa.n_len;
 }
 
 static int ccp_rsa_crypt(struct akcipher_request *req, bool encrypt)

If I remove this from the patch before applying I have no boot problems at all.

Also, as one of "our users" I'm pretty disappointed with that response - I would have thought fixing serious bugs in new releases before deprecating the currently working old releases would be common sense, but I suppose not.
Comment 8 Sora Lee 2018-05-26 05:02:16 UTC
Yes, I currently have 4.15.15 in my local repo and yes, this issue affects all versions after 4.15.15, including the 4.16.x series.
Comment 9 Mike Pagano gentoo-dev 2018-06-13 23:41:49 UTC
(In reply to Sora Lee from comment #7)
> Issue is with the following section of 1015_linux-4.15.16.patch:
> 
> diff --git a/drivers/crypto/ccp/ccp-crypto-rsa.c
> b/drivers/crypto/ccp/ccp-crypto-rsa.c
> index e6db8672d89c..05850dfd7940 100644
> --- a/drivers/crypto/ccp/ccp-crypto-rsa.c
> +++ b/drivers/crypto/ccp/ccp-crypto-rsa.c
> @@ -60,10 +60,9 @@ static int ccp_rsa_complete(struct crypto_async_request
> *async_req, int ret)
>  
>  static unsigned int ccp_rsa_maxsize(struct crypto_akcipher *tfm)
>  {
> -	if (ccp_version() > CCP_VERSION(3, 0))
> -		return CCP5_RSA_MAXMOD;
> -	else
> -		return CCP_RSA_MAXMOD;
> +	struct ccp_ctx *ctx = akcipher_tfm_ctx(tfm);
> +
> +	return ctx->u.rsa.n_len;
>  }
>  
>  static int ccp_rsa_crypt(struct akcipher_request *req, bool encrypt)
> 
> If I remove this from the patch before applying I have no boot problems at
> all.
> 
> Also, as one of "our users" I'm pretty disappointed with that response - I
> would have thought fixing serious bugs in new releases before deprecating
> the currently working old releases would be common sense, but I suppose not.


I'm pretty disappointed with your above comment. As someone that get's my time for free I would expect you not to scold me.