17.10 boot failure on Lenovo ThinkStation S30

[Alvin Cao]

This a boot failure(100%) so I cannot provide most information.

1. I tried upgrading from 17.04, the new kernel 4.13 kernel failed to boot but the 4.10 kernel still did. 17.10 could run on kernel 4.10.

2. Then I tried doing a fresh installation of 17.10. The same result.

I cannot get the log in text since it's early stage. I attached a screen shot of kernel log.

I think the kernel version is linux-image-4.13.0-16-generic_4.13.0-16.19_amd64.deb

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1730305/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1730305

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc8

[Alvin Cao (kneep)]

Hi Joseph.
I don't have any bootable kernel on the machine since it's fresh installation. Can I install another kernel? If yes, could provide some instructions? Thanks.

[Alvin Cao (kneep)]

Update:

I tried the following:

1. Fresh installed 17.04 with kernel 4.10, everything was OK.
2. Installed http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13.11/linux-image-4.13.11-041311-generic_4.13.11-041311.201711020532_amd64.deb, boot failure and the same error log.
3. Installed http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc8/linux-image-4.14.0-041400rc8-generic_4.14.0-041400rc8.201711052313_amd64.deb, boot failure and the same error log.

So apparently it's only about the kernel, nothing to do with Ubuntu version. If there is anything else I can help, let me know.

[Alvin Cao (kneep)]

Any update?

[Kai-Heng Feng (kaihengfeng)]

Try v4.11 and v4.12.

[Alvin Cao (kneep)]

Hi.

linux-image-4.11.12-041112-generic_4.11.12-041112.201707210350_amd64.deb worked while linux-image-4.12.14-041214-generic_4.12.14-041214.201709200843_amd64.deb failed. Both kernels are the latest build in their major series. So this bug was introduced in v4.12.

[Alvin Cao (kneep)]

Any idea?

[Kai-Heng Feng (kaihengfeng)]

Can you confirm that v4.11 works while v4.12 does not?

Use the exactly version, v4.11, not v4.11.X.