------- Comment From <email address hidden> 2018-07-23 07:30 EDT-------
Indira, I think Cascardo is looking for /tmp/initrd.img-`uname -r` file
whne MODULES=dep is used. Also, sosreport?
(In reply to comment #26)
> Created attachment 128855 [details]
> woo_kdump_nvmedisk_console logs
btw, looks like PHB initialization is failing. So, whether nvme driver
is present or not in the initrd is secondary here, the device initialization
itself could be at fault. What is the f/w level. Is it latest?
Thanks
Hari
------- Comment From <email address hidden> 2018-07-23 07:35 EDT-------
(In reply to comment #28)
> Indira, I think Cascardo is looking for /tmp/initrd.img-`uname -r` file
> whne MODULES=dep is used. Also, sosreport?
>
> (In reply to comment #26)
> > Created attachment 128855 [details]
> > woo_kdump_nvmedisk_console logs
>
> btw, looks like PHB initialization is failing. So, whether nvme driver
> is present or not in the initrd is secondary here, the device initialization
> itself could be at fault. What is the f/w level. Is it latest?
also, the initial console log is different from this.. Was the f/w on the system
updated as well..
------- Comment From <email address hidden> 2018-07-23 07:30 EDT------- img-`uname -r` file
Indira, I think Cascardo is looking for /tmp/initrd.
whne MODULES=dep is used. Also, sosreport?
(In reply to comment #26) nvmedisk_ console logs
> Created attachment 128855 [details]
> woo_kdump_
btw, looks like PHB initialization is failing. So, whether nvme driver
is present or not in the initrd is secondary here, the device initialization
itself could be at fault. What is the f/w level. Is it latest?
Thanks
Hari
------- Comment From <email address hidden> 2018-07-23 07:35 EDT------- img-`uname -r` file nvmedisk_ console logs
(In reply to comment #28)
> Indira, I think Cascardo is looking for /tmp/initrd.
> whne MODULES=dep is used. Also, sosreport?
>
> (In reply to comment #26)
> > Created attachment 128855 [details]
> > woo_kdump_
>
> btw, looks like PHB initialization is failing. So, whether nvme driver
> is present or not in the initrd is secondary here, the device initialization
> itself could be at fault. What is the f/w level. Is it latest?
also, the initial console log is different from this.. Was the f/w on the system
updated as well..
Thanks
Hari