The bug report mentions both AMD and Intel CPUs. I suspect it is a coding problem that is only triggered by certain Motherboard Chipset/BIOS combinations.

By the way, just for my personal geek culture : do you guess to what hardware the issue is linked to ?
clocksource ... this could be the MB ? or the CPU ? or the RAM ?

Your thank-you is more than sufficient. Just to make one point clear. I selected an existing machine close to your specs, I did not rebuild one. That machine normally runs Microsoft Home Server Version 2, and was rebooted with the ClearOS install disk just for the test... It is back running Microsoft Home Server.

Tony Ellis wrote:

Thanks Michael for providing the hardware details - that may have solved your problem. I selected a machine as close as possible to yours (it is actually a Microsoft Home Server v 2) and stuck the install disk in and booted. Boom!!!! Just after the grey screen with the cursor in the top left-hand corner I got a panic almost identical to yours. The important difference was a few lines at the top talking about tick and clock. A search on the web revealed this hit... https://bugs.centos.org/view.php?id=9860

So I rebooted again and hit <TAB> on the options screen and added according to the report "initcall_blacklist=clocksource_done_booting" so my line at the bottom of the screen looked like
(... snipped) quiet initcall_blacklist=clocksource_done_booting

hit <ENTER> - a little anxious time then HOORAY!!! up comes the normal boot messages, no panic :-) I didn't proceed further as I'm not installing on the machine...

Give it a try Michael - make sure you use underscores between the words.

Dave - you might want to review https://bugs.centos.org/view.php?id=9860 and replace the kernel in the iso with a newer one?

EDIT: forget to add this from the bug report

- for installed system : 

  - boot with the initcall_blacklist=clocksource_done_booting kernel parameter added (or reboot on previous kernel)

  - once booted, add the same parameter at the end of the GRUB_CMDLINE_LINUX=" .." line , in the file /etc/default/grub

  - as root, run "grub2-mkconfig -o /etc/grub2.conf"



- for a system you want to install

  - start the kernel/boot media with the initcall_blacklist=clocksource_done_booting kernel parameter added

  - when you reboot, add the solution above (for installed system) if not already applied to the default grub config

Don't forget to check the installed system has the added parameter - when you upgrade to the latest kernel I don't think this is required any more

Wow

WOW !

It worked perfectly !

Despite the fact that you brought the correct fix, the most impressive is that you found this tip on a webpage lost in the internet and, from what I could read, is not directly linked to my issue.
When you add the fact that you previously took the time and energy to rebuild a machine similar to mine, my non-native english is not rich enough to find the words to thank you.

@Tony - Wow...Not sure what else to say...The community is really lucky to have you on this forum.

@Michael - Can you confirm this worked for you and mark this as resolved...and maybe make your subject more detailed so others might gain from the help you received.

Thanks all.

B.

Thanks Michael for providing the hardware details - that may have solved your problem. I selected a machine as close as possible to yours (it is actually a Microsoft Home Server v 2) and stuck the install disk in and booted. Boom!!!! Just after the grey screen with the cursor in the top left-hand corner I got a panic almost identical to yours. The important difference was a few lines at the top talking about tick and clock. A search on the web revealed this hit... https://bugs.centos.org/view.php?id=9860

So I rebooted again and hit <TAB> on the options screen and added according to the report "initcall_blacklist=clocksource_done_booting" so my line at the bottom of the screen looked like
(... snipped) quiet initcall_blacklist=clocksource_done_booting

hit <ENTER> - a little anxious time then HOORAY!!! up comes the normal boot messages, no panic :-) I didn't proceed further as I'm not installing on the machine...

Give it a try Michael - make sure you use underscores between the words.

Dave - you might want to review https://bugs.centos.org/view.php?id=9860 and replace the kernel in the iso with a newer one?

EDIT: forget to add this from the bug report

- for installed system : 

  - boot with the initcall_blacklist=clocksource_done_booting kernel parameter added (or reboot on previous kernel)

  - once booted, add the same parameter at the end of the GRUB_CMDLINE_LINUX=" .." line , in the file /etc/default/grub

  - as root, run "grub2-mkconfig -o /etc/grub2.conf"



- for a system you want to install

  - start the kernel/boot media with the initcall_blacklist=clocksource_done_booting kernel parameter added

  - when you reboot, add the solution above (for installed system) if not already applied to the default grub config

Don't forget to check the installed system has the added parameter - when you upgrade to the latest kernel I don't think this is required any more

I can't help you with the panic. It is not really my area of knowledge. All I'd do is use google. Tony has far better knowledge or research abilities in that area.

I promise I'll use the dedicated driver
But for the moment, I can't even install 7.2 as I'm stucked at the same stage

What's happening ?
I keep only the vital hardware when installing and I'm stucked with this panic screen

Michael wrote:
For Nick's answer :
You"re right with the RTL8169, this is one of my NIC.
I've just tried to boot with the less hardware possible as I told so only MB, CPU, RAM and 1 DD (one time with the SSD, one time with the HDD) and it always ends with the same panic screen.
So this looks like a NIC problem.
I'll re-try to install without any NIC available (ethernet and wifi). I hope it is possible to disable the internal NIC because the BIOS is not very recent.

The built-in r8169 driver is fine for r8169 cards. It is just that RHEL and its derivatives use the same driver for the r8168 where it is not very good. It would be safe to try the installation with just the r8169 card for starters, but, as you say, it does not necessarily look like a NIC issue. The reason for installing the r8169 driver I linked to is that it will stop the r8169 driver loading for the r8168 card, which it otherwise tends to do by preference even after you load the correct r8168 driver.

So this doesn't look like a NIC issue.
I disabled the internal NIC in the BIOS and tried a fresh installation without any other NIC plugged, but I'm still facing the same panic screen.
So I tried to load defaults in the BIOS, and enable or disable various parameters, but without success. (eg Sata was configured as IDE, I tried AHCI ; I tried to disable ACPI, or disable internal LAN/audio/USB3, or disable multiple cores of CPU, etc...)

For Dave : I can access the 'Troubleshooting' menus when I boot on the USB key, but the non graphical option lands on the same issue, and I began a mempass test but ... this is useless as I run 6.7 without any problem so I finally interrupted the test.

Thanks for the quick answer.

A few more infos related to my previous posts :
- I have two NICs, 1 in the motherboard and 1 as a PCI card. These are 2 realtek
* RTL8111/8168/8411 Gigabit
* RTL 8169 Gigabit (running @ 100Mb, I never could fix that)
- there is no scroll, these are the only panic messages available

For Nick's answer :
You"re right with the RTL8169, this is one of my NIC.
I've just tried to boot with the less hardware possible as I told so only MB, CPU, RAM and 1 DD (one time with the SSD, one time with the HDD) and it always ends with the same panic screen.
So this looks like a NIC problem.
I'll re-try to install without any NIC available (ethernet and wifi). I hope it is possible to disable the internal NIC because the BIOS is not very recent.


EDIT : by the way, something weird : Since I've been trying to install the 7.2, the 6.7 still runs flawlessly ... but the web interface is not available anymore (w.x.y.z:81)

CentOS 7 is based on RHEL 7.

This may not help with your current issue, but you have a problem NIC. The drivers supplied sometimes work and sometimes just appear to work but give a load of background problems. If you manage to get 7.2 installed, please can you install this driver which is optimal, and this driver which removes the compatibility of the r8169 driver with your NIC. It may also help if you install with some other NIC, if you have one, and disable the on-board one for installation. You can re-enable it afterwards, preferably when you've installed the linked drivers.

Can I suggest you also remove your wireless NIC while installing?

No need to reboot into BIOS, dmidecode is my friend
MB : ASUS M4A88T-M/USB3
Processor : AMD Athlon II X2 4450e 2.8Ghz
RAM : 4Go of DDR3 1333Mhz

Oops, sorry for the screenshot, I didn't notice it was upside down.
When I verified the upload http://www.orvis.fr/ClearOS/install-fails.jpg it was printed correctly.

So a few direct answer to your questions :

- I think this is all the panic messages, I didn't notice any scroll. But I'll test the installation again to confirm.
- the hardware : this is mostly some (not so) old hardware combined to build a firewall : I'll check the BIOS to have the correct description but iit should be something like AMD 64 processor with 2 cores, a 6 or 7 years old MB, 3 or 4 Go of DDR3 RAM, 1 SSD sata and 1 HDD sata (?), an asus wifi card to use it as an access point (I had a hard time to make this work)
- I was running a 64-bit version of ClearOS 6.7

By the way, you gave me the answer to the question for which I spent 1 hour to find an answer : ClearOS is based on CentOS 7 and not RHEL 7

For the other questions, I'll I have a look right now (and I'll try to boot with the minimum hardware plugged)

Are you able to run the rescue utilities or does it panic for those as well?

Hi Michael, While I applaud the quality of the screen-shot, why upside-down? and least that is how it displays here... Is this all of the panic, or did some of it scroll by before stopping, and thus we are missing the most important part which is the beginning?

How about providing us an idea of the hardware you are using such as CPU type and model, same for motherboard. Disks SATA or IDE, if SATA mode? ahci or ide emulation. If this is a commercial system make and model so we can lookup specs. What memory installed - type and size etc. NICs?

Have you done a google search? ClearOS is based on CentOS, so you can use that as part of your search argument while searching for panics or crashes while installing CentOS 7.

Incidentally were you running the 32-bit or 64-bit version of ClearOS 6.7?

EDIT:
downloaded your image and opened it with GIMP... Immediately got this....

According to the EXIF data, this image is rotated.
Would you like GIMP to rotate it into the standard orientation?
(boxes) Keep Orientation (and) Rotate

Hitting 'rotate' box turned it the correct way up...