Posts made by Maorui2k

@sebastian-roth I have no idea too… Changing hardware is not an option, too many PCs… Currently I would keep using fog 1.3.x and kernel 3.17.3, so far it could meet my requirement. Maybe I would try to merge the initrd later. Anyway thank you so much for your support!!!

@sebastian-roth still failed at the same position…

@sebastian-roth The one extracted from ISO

@sebastian-roth I tried the 1st option, but the PC hung after the language selection screen showed up, both keyboard & power button were frozen. Didn’t see any error message, so I don’t know if it is realted to HID driver or not, but anyway I cannot do the testing, should be driver missed or conflicted.

@sebastian-roth Oops, I missed the result. I tested the kernel & initrd from ISO in two booting ways - PXE and USB. The results were quiet similar, 36 passed + 14 failed & 34 passed + 16 failed.

@sebastian-roth Yes, 3.17.3 is not perfect. I did a quick testing and found starting from 4.0 kernel (fog kernel + fog initrd + PXE) the chance of this issue raised to around 50%. I tested the installed Ubuntu 16.04 system 60 times, no any failure. I also retested the latest CentOS 7 which used 3.10 kernal and systemd, but the failure rate was around 50% too.

As you said, we already did many compiling and testing, it’s fainful :-D, and got no significant changes. This should not be the right way. The recent testing result strengthened my gut feeling that this is a system level issue. Ubuntu team found and resolved this issue somehow, but CentOS didn’t. Kernel, driver, systemd and some other unknown parts involved in this issue. So I think the best solution should be converting the installed Ubuntu 16 into PXE boot in some way. What’s your suggestion?

@sebastian-roth Sorry, I was out again, the whole week. I retested 3.17.3+PXE 60 times, 2 failed and 58 passed.

@sebastian-roth It seems here is a misunderstanding, the official Ubuntu 16.04 kernel I tested was not from installation DVD, but from an installed system.

I tested the kernel+initrd of installation DVD, it’s similar to kernels built by you, say about 50% failed.

The installed kernel is not same as installation DVD. The installed kernel + initrd-ubuntu.xz has about 75% successful rate in 20 times reboot.

I tried to PXE boot the installed kernel (/boot/vmlinuz-4.4.0-62-generic) and initrd (/boot/initrd.img-4.4.0-62-generic), but the rootfs failed to mount. I uploaded screen capture screen-capture-rootfs-failed.jpg https://drive.google.com/open?id=0Bx_soHaLoSYETXhEeUVBRVllNVE

It seems the handler of reboot/shutdown is different in your initrd and Ubuntu initrd. The Ubuntu reboot/shutdown is handled by systemctl. Now I wonder if my reboot/shutdown issue is a kind of system-level issue, both kernel/drivers/utilities have their roles.

How can I use the initrd of the installed Ubuntu in PXE? I think this may have a good chance to resolve my issue.

@sebastian-roth log uploaded https://drive.google.com/open?id=0Bx_soHaLoSYETXhEeUVBRVllNVE dmesg-bzImage-4.4.0-62-generic-with-new-initrd.log

I did 50 times reboot/shutdown each. Here is the result.

3.17.3 kernel - PXE boot    46 passed, 4 failed.
bzImage-4.4.0-62-generic and latest initrd - PXE boot          27 passed, 23 failed.
Ubuntu-16.04 - CD boot      50 passed, 0 failed.

Seems 3.17.3 also has a very little chance of failure, but acceptable for me.

Is it possible to use Ubuntu 16.04 kernel and generate an initrd from it? It’s the best one.

@sebastian-roth The new initrd had a little improvement, I did 20 times reboot/shutdown, 70% passed. I’m not sure if it is just a result of probability.

The irqpoll has no any effect, and caused a hung during the boot process before network initializing messages. The passed ratio was still around 70% in 10 times reboot/shutdown.

@sebastian-roth the new kernel is bzImage-4.4.0-62-generic, and other 4.4.0 based kernels had similar results. Fog-* means fog official kernels. The last line is official Ubuntu 16.04 kernel. I guess APIC or ACPI or some related module have a stability/compatibility issue, and Ubuntu fixed it.

@sebastian-roth I might forget to save the FOG_KERNEL_RAMDISK_SIZE parameter… The boot is fine now. And the new kernel has around 50% chance to reboot/shutdown!

It seems the attempts of reboot/shutdown I tried were too few. The fog official 4.4.0 kernel also has similar chance. So I went through the testing again with more attempts. Here is the result table.

Kernel                     Attempts      Passed      Failed
3.17.3                     10            10          0
bzImage-4.4.0-62-generic   22            12          10
Fog-4.4.0                  10            4           6
Other 4.4 you compiled     28            14          14
Fog-4.8.11                 10            0           10
Ubuntu-16.04               12            12          0

It seems the kernel got some changes between 4.4 & 4.8 which made things much worser, and Ubuntu 16.04 indeed got something fixed here. And the reboot/shutdown of Ubuntu 16.04 looked more smooth. The kernels you provided would delay 1~2s before really taking effects.

I uploaded two dmesg logs https://drive.google.com/open?id=0Bx_soHaLoSYETXhEeUVBRVllNVE
dmesg-bzImage-fog-4.4.0.log & dmesg-bzImage-4.4.0-62-generic.log

@sebastian-roth I got an kernel panic this time. The last line of error message was “VFS: unable to mount root fs on unknown-block(1,0)” I wonder if the initrd.xz was broken.

Thanks for detailed instruction about compiling the kernel! I found some Wiki pages in Ubuntu website, but failed to finish it in Ubuntu 16.04. I will try your way this time.

@sebastian-roth I was away for days again… I uploaded the new logs here. https://drive.google.com/open?id=0Bx_soHaLoSYETXhEeUVBRVllNVE The reboot/shutdown was still failed.

I would be happy to help in this investigation So don’t hesitate to ask for more testing and logs. I’ve dedicated the same PC for this testing.

@sebastian-roth I checked kernel version, it’s x64. The USB works this time, thx!

I uploaded three logs, pls take a look. https://drive.google.com/open?id=0Bx_soHaLoSYETXhEeUVBRVllNVE

dmesg-Ubuntu-16.04.2.log: original Ubuntu 16.04.2 kernel which has no reboot/shutdown issue
dmesg-44-Ubuntu-config.log: bzImage4.4-pretty-close-to-the-ubuntu-build
dmesg-44-config-3.17.3.log: bzImage4.4-with-config-uped-from-3.17.3

@Sebastian-Roth The reboot/shutdown and USB still didn’t work with the new kernel…

I installed Ubuntu 16.04 desktop and server edition, and both could reboot successfully. Live CD was also fine.

I tried everything in same PC. I checked all BIOS options, didn’t see anything related to this issue.

@Sebastian-Roth said in Linux kernel:

@Maorui2k Sorry for the long delay, I have been away. So it looks like the ubuntu kernel patches don’t make a difference. So next we can try to use the ubuntu kernel config to see if that helps. Find a newly compiled bzImage here. Please try this and let me know!

It didn’t work… And the USB keyboard didn’t work with this version, so I couldn’t test the reboot in debug mode manually. I tried two different keyboards and all USB2/3 ports. The keyboard stopped response after the new kernel was loaded.

@Sebastian-Roth Thanks for the kernel, but it doesn’t work too. There is no error message, just stopped at the last step of regular reboot/shutdown process. The last step should be a signal to hardware. I uploaded a picture of the screen here. https://drive.google.com/open?id=0Bx_soHaLoSYETllpSUVmVEotX28 So the kernel config may do the trick.

@Quazz Windows & Ubuntu 16 could reboot/shutdown. And there is no BIOS update.

@Quazz I tried debug mode, both reboot & shutdown had same result. I could see the message of killall process, but the PC just hung there after message ‘Requesting system reboot/halt’, and the keyboard was freezed too, CTRL-ALT-DEL won’t work.