Feedback on the Dell Latitude 7400

Hi Martin,

Thank you for bringing this to our attention, this absolutely should not be happening and I'm truly sorry you're having this issue. Our engineers are looking into it now and will be with your shortly. To help expedite this, may I please ask for a few things:

1) Do you recall which kernel the system was updating to?
2) Which exact SKU of the 7400 do you have? We've certified a SKU with Intel wireless and one with Qualcomm wireless

Thank you for bearing with us on this, we'll do what we can to get this solved. We appreciate your help.

Thanks
Chris

 > 1) Do you recall which kernel the system was updating to?
The first kernel is:
4.15.0-1030-oem

then the next is:
4.15.0-1080-oem

Thats from the advanced Linux boot screen.
 > 2) Which exact SKU of the 7400 do you have? We've certified a SKU
with Intel wireless and one with Qualcomm wireless
"$ dmidecode -t system" gives:
SKU Number: 08E1

I guess you can find the details.

Thanks for getting into this.

Cheers,
Martin

On 25.05.20 21:01, Chris Wayne wrote:
> Your question #690926 on Ubuntu-Certification changed:
> https://answers.launchpad.net/ubuntu-certification/+question/690926
>
> Status: Open => Needs information
>
> Chris Wayne requested more information:
> Hi Martin,
>
> Thank you for bringing this to our attention, this absolutely should not
> be happening and I'm truly sorry you're having this issue. Our
> engineers are looking into it now and will be with your shortly. To
> help expedite this, may I please ask for a few things:
>
> 1) Do you recall which kernel the system was updating to?
> 2) Which exact SKU of the 7400 do you have? We've certified a SKU with Intel wireless and one with Qualcomm wireless
>
> Thank you for bearing with us on this, we'll do what we can to get this
> solved. We appreciate your help.
>
> Thanks
> Chris
>

--
+----------------------------------------------------------------------+
| Martin Kuemmel E-mail: <email address hidden> |
| LMU Faculty of Physics Skype: martin.kuemmel |
| Scheinerstr. 1 Google: <email address hidden> |
| D-81679 Muenchen Room: 133 (I04) |
| Germany Phone: +49 89 2180-5993 |
| __o |
| _ \<._ |
+_(_)/_(_)_____________________________________________________________+

Martin,

We appreciate you getting back to us with information so quickly. We're currently looking into this issue and we believe it may actually be a GRUB issue rather than a kernel issue (which could explain why you're seeing problems on several distros). We'll let you know the path forward once we finalize it.

Thanks for your patience
Chris

> We appreciate you getting back to us with information so quickly. We're
> currently looking into this issue and we believe it may actually be a
> GRUB issue rather than a kernel issue (which could explain why you're
> seeing problems on several distros). We'll let you know the path
> forward once we finalize it.
That is possible, since I noted that also grub is updated with the kernel.

For your information, the updated grub is:
grub2 2.02-2ubuntu 8.15

In ubuntu 20.04 (which has no boot problems) the grub version is:
grub2 2.04-1ubuntu26

Hope this helps,
Martin

--
+----------------------------------------------------------------------+
| Martin Kuemmel E-mail: <email address hidden> |
| LMU Faculty of Physics Skype: martin.kuemmel |
| Scheinerstr. 1 Google: <email address hidden> |
| D-81679 Muenchen Room: 133 (I04) |
| Germany Phone: +49 89 2180-5993 |
| __o |
| _ \<._ |
+_(_)/_(_)_____________________________________________________________+

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Honestly, I don't think it helps to close that issue only if no solution is not found within 15 days.

If this issue isn't being solved, Dell is still selling high value laptops with a *certified* OS that just does not work.

I would *at least* expect a final comment from the people responsible and consequences for the certificate!

Martin,

You're absolutely right, this should not have been marked as closed, I apologize for this. The team is looking into whether this is indeed a grub issue, though it appears that it may possibly be an issue with an updated intel-microcode package. May I please ask which version of intel-microcode you have loaded on the system? To be clear, we are still investigating the possibility of a grub regression as well.

I truly am sorry for the lack of communication on this issue, I take full responsibility for this. That said, I can assure you we are digging into the problem and will do everything we can to fix it.

I just connected to that system. It *was*:
mkuemmel@bruceII:~$ grep -E 'family|model|stepping|microcode'
/proc/cpuinfo | head -5
cpu family : 6
model : 142
model name : Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz
stepping : 12
microcode : 0xca

Note that I run a regular system update.

*After* that update it is:
mkuemmel@bruceII:~$ grep -E 'family|model|stepping|microcode'
/proc/cpuinfo | head -5
cpu family : 6
model : 142
model name : Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz
stepping : 12
microcode : 0xd6

Hope this helps.

The problem seems to be solved, likely due to the many updates on the ubuntu side that had happened over time.

Closing the issue.