Linux kernel

Sebastian Roth

@Maorui2k What exactly did you try?? There are several different options you can set with reboot=.... Which one did you try? As well you can look into playing with kernel parameter acpi=.... Possible a combination of both might work.

Don’t get me wrong. You are more than welcome to build you very own kernel and hopefully make things work. But it’s definitely quicker to try out different kernel parameters first and see if things work that way. As I said, latest kernel in FOG is 4.11.0 so if you are trying to build 4.4.0 (which is working in Ubuntu) from plain vanilla source I highly doubt that reboot is working for you out of the box.

Please keep us posted on this.

Maorui2k

@Sebastian-Roth I tried all reboot options, none of them works…

I understand your concern. Actually I don’t care which version to use, 4.4 or 4.11 are both fine for me. I wonder if something was missed or disabled in the kernel configuration, which caused this reboot issue. Now 3.17.3 is not able to work with fog 1.4.0, so that’s why I wanted to compile my own kernel.

Any way I will try acpi and combination first.

Sebastian Roth

@Maorui2k Sorry for not getting back on to this. Did you get to build your own kernel and find/fix the issue? Or did any off the kernel parameters help.

Maorui2k

@Sebastian-Roth I tried CentOS 6 & 7, both have the issue. So Ubuntu is the only survivor. I’m still finghting with the Ubuntu kernel compile process. It’s not same as general process, and I always got error in the middle. Not sure the reason yet…

Quazz

Can you try to boot one of the machines in debug mode and try to reboot there?

It’s unlikely, but perhaps it will give some useful information.

I’m guessing these are custom built PCs? (given that no DMI info is supplied)

It’s interesting that under certain circumstances they wouldn’t reboot.

What about shutdown? Does that work?

Maorui2k

@Quazz I tried and got same result.

Quazz

@Maorui2k “same result” being nothing happening at all?

Maorui2k

@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.

Quazz

@Maorui2k If you have an operating system installed on them, can they shut down/reboot?

Are there any BIOS updates available for this motherboard?

Sebastian Roth

@Maorui2k said in Linux kernel:

I tried CentOS 6 & 7, both have the issue. So Ubuntu is the only survivor. I’m still finghting with the Ubuntu kernel compile process. It’s not same as general process, and I always got error in the middle. Not sure the reason yet…

Please post the error so I might be able to help. Without I don’t have a chance to give you a hint. Let me know which steps/command you do/run and which error you get.

I am wondering if it’s Ubuntu’s kernel config or if they have a special patch that does help shutting down your machines. The problem is that building a normal Ubuntu kernel won’t help you because FOG has all the important drivers included in the kernel (bzImage) while Ubuntu has most in the initrd. Ubuntu kernel is smaller but would not work with FOG (initrd). I’ll think about it a little more and try some stuff.

Sebastian Roth

@Maorui2k Ok, to see if the Ubuntu patches do the trick I downloaded those, applied to a vanilla 4.4.0 kernel, used our FOG kernel config and build a kernel from that. Please download bzImage and init.xz here. If this kernel properly shuts down your machine then we can start looking through the patchset. On the other hand, if this kernel does not shutdown/turn off your machine, then the Ubuntu patches are irrelevant and you can start comparing the kernel configs and/or parameters.

Maorui2k

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

Maorui2k

@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.

Sebastian Roth

@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!

Maorui2k

@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

@Maorui2k Sorry for the USB issue. Didn’t think that USB keyboard would be build as a module by default. I added it to the kernel and uploaded a new version. Could you please try again?

Have you ever installed Ubuntu 16.04 on that hardware and tried to reboot? I am just wondering if we are on the wrong track with this. Maybe booting a live CD is just a little different.

Bay the way: Are you working on the exact same PC all the time? Just to rule out that BIOS settings might be causing the issue on one of the PCs?

Maorui2k

@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.

Wayne Workman

Moved to Hardware Compatibility.

Sebastian Roth

@Maorui2k I found this in the kernel config:

 config X86_REBOOTFIXUPS
        bool "Enable X86 board specific fixups for reboot"
        depends on X86_32
        ---help---
          This enables chipset and/or board specific fixups to be done
          in order to get reboot to work correctly. This is only needed on
          some combinations of hardware and BIOS. The symptom, for which
          this config is intended, is when reboot ends with a stalled/hung
          system.

          Currently, the only fixup is for the Geode machines using
          CS5530A and CS5536 chipsets and the RDC R-321x SoC.

Although it sounds promising at first I don’t think this is what we are after. Those chipsets don’t seem to match yours. And this option is only available on 32 bit kernel builds!! So I highly doubt this would fix the reboot for you.

But this made me think about CPU architecture. Are you sure the 64 bit kernel is loaded by iPXE?? Pay attention to the screen when it says:

bzImage... ok
init.xz... ok

Nothing about 32 there, right???

I updated that kernel once again as I still was missing the USB HID settings, too bad. Hope that your keyboard is working now but probably won’t help the reboot anyway.
As well I’ve used the 3.17.3 kernel config from our repo and updated it to build a 4.4 kernel from that. So if anything was in that config it should be still in there. Please try both kernels.

I’ve been reading through this and searched the web over and over again. I just don’t understand why none of the kernels I build is doing any better. Just scratching my head… Why do 3.17.3 and the ubuntu kernels reboot properly? Boot up a live system again (or from disk if you have still installed ubuntu) and get a full listing of the kernel messages buffer. I feel this could be quite important in finding the issue. Get a FAT32 formated USB key and run:

sudo -i
mkdir /usbkey
mount -t vfat /dev/sdb1 /usbkey
dmesg > /usbkey/ubuntu_working.txt
umount /usbkey

Do the same in a FOG debug task just no sudo and choosing a different filename to store the dmesg output in. Please upload both full outputs and post download links here.

Maorui2k

@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

Linux kernel

195

12.0k

17.3k

155.2k