Bug 204761 - Regression MEGARAID_SAS since 5.2 kernel
Summary: Regression MEGARAID_SAS since 5.2 kernel
Status: NEW
Alias: None
Product: IO/Storage
Classification: Unclassified
Component: Serial ATA (show other bugs)
Hardware: x86-64 Linux
: P1 blocking
Assignee: Tejun Heo
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-09-03 14:50 UTC by Darko Luketic
Modified: 2019-09-10 10:59 UTC (History)
0 users

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


Attachments
dmesg output (51.54 KB, text/plain)
2019-09-10 10:59 UTC, Darko Luketic
Details

Description Darko Luketic 2019-09-03 14:50:20 UTC
My distribution is Gentoo Linux.
This is a production system.

When I upgraded from 5.1.16 to 5.2.1 and following kernels (untested with 5.2.11)
the result was an unbootable system.
In particular, I asked the datacenter support to connect a KVM console to the server and I watched what happened in the boot process.
The result was "the GUID xyz could not be found".
I have then checked /dev and nothing disk related was there.
The driver is embedded <*> and the 5.1.16 config was taken with --oldconfig.

If you need any more info I'll try to provide.

See also:
https://forums.gentoo.org/viewtopic-t-1099598.html
Comment 1 Darko Luketic 2019-09-10 10:59:13 UTC
The issue was related to naming of devices.
I'm not sure what really was the issue.
Fact is the devices were not there. No /dev/disk/by-uuid/ or similar not even /dev/sda were present.
Now I've compiled 5.2.13 and plugged a remote kvm console into the server.
Which showed me that the network interface that was named `enp5s0` is now named `p5p1`.
So it has to be some combination of kernel 5.2 and systemd 242 or 243rc1 243rc2
Comment 2 Darko Luketic 2019-09-10 10:59:57 UTC
Created attachment 284905 [details]
dmesg output

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