Perfect - thanks so much Nick and Tony for helping me get to the bottom of this. And I may try the 7.6 kernel - we'll see.

Eric

The file names are not critical. Just use something you can remember, and I think they have to end in .conf but I am not sure. You should only need one of the two files as I think modprobe loads from both locations.

If you really wanted to try the 7.6 kernel, you can do it with:

yum update kernel --enablerepo=clearos-updates-testing,centos-unverified

But as you have 7.5 working, it is probably not worth the effort.

Hi Tony and Nick,

So this is what did it:

nano /etc/modprobe.d/snd.conf

# disable soundcard drivers to keep ClearOS 7.5 kernel from crashing
blacklist snd-hdmi-lpe-audio

7.5 came up working fine.

Makes sense since this is the name of the driver with the (+) designation next to it in the original boot error screen capture.

Thanks for your help!

OK so looking at the list there are 4 drivers with no calling programs related to sound. So this is what I did:

nano /etc/modprobe.d/sound.blacklist.conf

# disable soundcard drivers for uninstalled hardware to keep ClearOS 7.5 kernel from crashing
blacklist snd_soc_rt5645
blacklist snd_intel_sst_acpi
blacklist snd_soc_rt5640
blacklist snd_seq

nano /etc/modprobe.d/snd.conf

# disable soundcard drivers for uninstalled hardware to keep ClearOS 7.5 kernel from crashing
blacklist snd_soc_rt5645
blacklist snd_intel_sst_acpi
blacklist snd_soc_rt5640
blacklist snd_seq

I have to wait until I get home in a few hours to try this.

Neither of these files either existed, or if they did they were empty, before I started this. So hopefully one of these does it. Let me know if you think I should do something else.

For the 7.6 kernel, I'm happy to load and try it if you think it might help the developers. But if there are questions as to how effective the 7.6 exercise would be in it's current state, I'm fine waiting until the next update of ClearOS.

I'm not totally sure what to do for blacklisting. I think you only need to blacklist the lines with only one module named. Ones with modules on the right are dependencies of the modules named on the right. This is based on observation and not knowledge. As an example, I don't think you need to blacklist snd_soc_sst_match as it is only loaded because of snd_intel_sst_acpi. As snd_intel_sst_acpi is also an entry on its own, it should be blacklisted.

Re the 7.6 kernel. It is there but I have not been able to make out what it is. The problem is that it is suffixed el7, but ClearOS kernels should be suffixed v7. This means it is either a ClearOS kernel wrongly named (it has been known), or it is a pure Centos kernel. A pure Centos kernel has not been patched for IMQ drivers so will not work with the ClearOS QoS (actually it might but that is another story). It will also not work with any of my kmod drivers which I suspect you don't use with your Intel NICs. I'll have to post how to update it tomorrow as I'll need to find the matching linux-firmware and selinux-policy-targeted packages are, but it is bed time now.

Eric - thanks "lspci" without any parameters was all that was required... The Intel Atom® Processor E3845 SoC includes Intel HD Audio Technology - so as suspected it's there in the chipset (in this case the SoC), but the extra hardware required to support it wasn't installed and the BIOS support lacking... the "lspci" report confirms this...

Wonder if this is part of the problem as sound is expected from a system with this SoC? Anyway - you now have a nice list for blacklisting - but only those beginning with snd... or sound....

For Nick:

[root@gateway ~]# lsmod | grep snd
snd_soc_rt5645 141612 0
snd_intel_sst_acpi 13355 0
snd_intel_sst_core 76444 1 snd_intel_sst_acpi
snd_soc_rt5640 118324 0
snd_soc_sst_mfld_platform 94528 1 snd_intel_sst_core
snd_soc_rl6231 13321 2 snd_soc_rt5640,snd_soc_rt5645
snd_soc_sst_match 13186 1 snd_intel_sst_acpi
snd_soc_core 229807 3 snd_soc_rt5640,snd_soc_rt5645,snd_soc_sst_mfld_platform
snd_compress 19637 1 snd_soc_core
snd_seq 62699 0
snd_seq_device 14356 1 snd_seq
snd_pcm 106416 4 snd_soc_rt5640,snd_soc_rt5645,snd_soc_core,snd_soc_sst_mfld_platform
snd_timer 29822 2 snd_pcm,snd_seq
snd 83383 7 snd_soc_core,snd_timer,snd_pcm,snd_seq,snd_soc_sst_mfld_platform,snd_seq_device,snd_compress
regmap_i2c 12915 2 snd_soc_rt5640,snd_soc_rt5645
soundcore 15047 1 snd
iosf_mbi 13523 3 sdhci_acpi,snd_intel_sst_acpi,intel_rapl
i2c_core 40756 11 drm,i915,i2c_i801,snd_soc_rt5640,snd_soc_rt5645,i2c_hid,i2c_designware_core,i2c_designware_platform,regmap_i2c,drm_kms_helper,i2c_algo_bit
[root@gateway ~]#

For Toni ...

lspci -vxx was pretty verbose , so just lspci to start:

[root@gateway ~]# lspci
00:00.0 Host bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register (rev 11)
00:02.0 VGA compatible controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display (rev 11)
00:03.0 Multimedia controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Camera ISP (rev 11)
00:13.0 SATA controller: Intel Corporation Atom Processor E3800 Series SATA AHCI Controller (rev 11)
00:14.0 USB controller: Intel Corporation Atom Processor Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI (rev 11)
00:1a.0 Encryption controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine (rev 11)
00:1c.0 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 1 (rev 11)
00:1c.1 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 2 (rev 11)
00:1c.2 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 3 (rev 11)
00:1c.3 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 4 (rev 11)
00:1f.0 ISA bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Power Control Unit (rev 11)
00:1f.3 SMBus: Intel Corporation Atom Processor E3800 Series SMBus Controller (rev 11)
01:00.0 Ethernet controller: Intel Corporation 82583V Gigabit Network Connection
02:00.0 Ethernet controller: Intel Corporation 82583V Gigabit Network Connection
03:00.0 Ethernet controller: Intel Corporation 82583V Gigabit Network Connection
04:00.0 Ethernet controller: Intel Corporation 82583V Gigabit Network Connection

Tony Ellis wrote:

Eric - Nick might have more information on 7.6 - I imagine it is in a developer repo...

Would be more inclined to blacklist the following sound drivers as listed in your screen-shot and try again...
snd_hdmi_lpe_audio
snd_pcm
snd_timer
snd
sound_core Your system is listed as "YL-E3845L4-V2" - What exactly is it? Just because it has no sound jacks doesn't necessarily indicate the chipset doesn't have sound capability within it - just the board manufacturer didn't install the necessary hardware to make use of it and removed that BIOS section... notice the driver above loading support for sound via the hdmi port..

Agree on all. This is a Yanling single-board computer in a fanless heatsink/case, E3845 Atom AES-NI CPU: Ibox-501 N12 is pretty close in description.


[/quote]Can you please provide the output from "lspci"[/quote]

so

lspci -vvx

correct?

Nick Howitt wrote:
It probably is not a good idea at this point going through how to download manually and then do a localinstall. I'd expect there may be a dependency issue, perhaps to linux-firmware or to microcode which we'd have to work through.[quote]

Wise counsel - agreed!

[quote]As a thought, with 7.4 try:

lsmod | grep snd

This should show up the primary sound driver (among other bits). You could then try blacklisting it. There is a thread here for blacklisting in Ubuntu. I guess you can add your own /etc/modprobe.d/blacklist.conf file there, or you can add a file /usr/lib/modprobe.d/{anything}.conf and blacklist there.[quote]

I'll work on that

[quote]From this post I suspect the driver to blacklist is snd_hda_intel

Thanks to both of you for the references. I will focus my efforts on blacklisting the drivers

The 7.6 kernel is in updates-testing but yum does not see it so I've asked if the index/filelist is broken. It probably is not a good idea at this point going through how to download manually and then do a localinstall. I'd expect there may be a dependency issue, perhaps to linux-firmware or to microcode which we'd have to work through.

As a thought, with 7.4 try:

lsmod | grep snd

This should show up the primary sound driver (among other bits). You could then try blacklisting it. There is a thread here for blacklisting in Ubuntu. I guess you can add your own /etc/modprobe.d/blacklist.conf file there, or you can add a file /usr/lib/modprobe.d/{anything}.conf and blacklist there.

From this post I suspect the driver to blacklist is snd_hda_intel

Eric - Nick might have more information on 7.6 - I imagine it is in a developer repo...

Would be more inclined to blacklist the following sound drivers as listed in your screen-shot and try again...
snd_hdmi_lpe_audio
snd_pcm
snd_timer
snd
sound_core

Your system is listed as "YL-E3845L4-V2" - What exactly is it? Just because it has no sound jacks doesn't necessarily indicate the chipset doesn't have sound capability within it - just the board manufacturer didn't install the necessary hardware to make use of it and removed that BIOS section... notice the driver above loading support for sound via the hdmi port..

Can you please provide the output from "lspci"

Just to put the record straight, you don't need desktop software to support sound - though of course it is easier - there are command-line sound tools. Here's something put together many moons ago Command Line Sound

Edit: Corrected typo - got lspci command scrambled

Thanks for chasing this down Toni. I read through the link you sent and I'm thinking it is the same bug I am seeing there.

Unfortunately there are no sound settings in the BIOS for this box - there aren't any audio in/out jacks, apparently no audio hardware on the board. So I have nothing to turn off.

I checked my software update log and it looks like after I deleted kernel-3.10.0-862.11.6.v7 a couple days ago that the system reloaded it on 2/5. I'll look into moving it's priority.


Any Ideas on how I would go about getting the 7.6 kernel loaded ... other than waiting for it to roll out as an update?

Eric - helps in that it excludes some potential problem areas...
Using "Attached scsi generic sg0 type 0" as a key - had a look at what happens on my system while booting during that time-frame... as Nick surmised - sound seems to be the focus...
See Kernel Oops - Sound for something similar... maybe try to blacklist some audio drivers or as Nick suggested and somewhat easier - disable sound...

... snipped

[    1.836857] mei_me 0000:00:16.0: irq 40 for MSI/MSI-X

[    1.853937] input: PC Speaker as /devices/platform/pcspkr/input/input3

[    1.860164] sd 0:0:0:0: Attached scsi generic sg0 type 0

[    1.860204] sd 2:0:0:0: Attached scsi generic sg1 type 0

[    1.860238] sd 3:0:0:0: Attached scsi generic sg2 type 0

[    1.860272] sd 4:0:0:0: Attached scsi generic sg3 type 0

[    1.867127] iTCO_vendor_support: vendor-support=0

[    1.868982] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11

[    1.869022] iTCO_wdt: unable to reset NO_REBOOT flag, device disabled by hardware/BIOS

[    1.876998] cryptd: max_cpu_qlen set to 100

[    1.882225] random: crng init done

[    1.896517] AVX version of gcm_enc/dec engaged.

[    1.896517] AES CTR mode by8 optimization enabled

[    1.901609] async_tx: api initialized (async)

[    1.903910] snd_hda_intel 0000:00:1b.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])

[    1.904021] alg: No test for __gcm-aes-aesni (__driver-gcm-aes-aesni)

[    1.904053] alg: No test for __generic-gcm-aes-aesni (__driver-generic-gcm-aes-aesni)

[    1.905417] xor: automatically using best checksumming function:

[    1.908635] Adding 6291452k swap on /dev/sda6.  Priority:-1 extents:1 across:6291452k SSFS

[    1.914572] snd_hda_intel 0000:00:1b.0: irq 41 for MSI/MSI-X

[    1.914883]    avx       : 23828.000 MB/sec

[    1.933799] snd_hda_codec_via hdaudioC0D2: autoconfig for VT2020: line_outs=3 (0x24/0x25/0x26/0x0/0x0) type:line

[    1.933809] snd_hda_codec_via hdaudioC0D2:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)

[    1.933817] snd_hda_codec_via hdaudioC0D2:    hp_outs=1 (0x28/0x0/0x0/0x0/0x0)

[    1.933824] snd_hda_codec_via hdaudioC0D2:    mono: mono_out=0x0

[    1.933828] snd_hda_codec_via hdaudioC0D2:    dig-out=0x2d/0x2e

[    1.933833] snd_hda_codec_via hdaudioC0D2:    inputs:

[    1.933838] snd_hda_codec_via hdaudioC0D2:      Front Mic=0x29

[    1.933843] snd_hda_codec_via hdaudioC0D2:      Rear Mic=0x2b

[    1.933848] snd_hda_codec_via hdaudioC0D2:      Line=0x2a

[    1.940884] raid6: sse2x1   gen()  6285 MB/s

... snipped

Hey Nick, thanks for the link - wish I'd seen that earlier.

If we're getting close to a 7.6 release maybe I should try it, if for no other reason than to report any issues like this. I don't mind helping, especially if I can move my boot order if there is an issue.


Hey Tony, my installation is all ClearOS 7.4, and all drivers are whatever was supplied "out-of-the-box". Nothing else is running on the machine. Does that help?

Eric - using any kmod drivers?

I would not like to say if it is OK to stay on the 7.4 kernel. Things have moved quite fast over the last year because of the Spectre and Meltdown issues. I was going to suggest the 7.6 kernel in updates-testing but I can't get to it with yum. I'll need to ask the devs.

I have no idea if the issue will reappear if you stay with the 7.4 kernel. I don't even know if my diagnosis is correct. I just looked at the output. Really it would be an idea to google the error.

Next time you want to change the boot order, have a look at something like this.

Sorry for the Newbie mistakes. I didn't realize the images weren't posting because there is a 2MB limit.

Are the chances high that if I continue to use the 7.4 kernel that I will have issues?

The problem you have been having posting is because the first couple of your posts get moderated. I keep having to delete your duplicates.
You may have to reinstall the kernel to get the menu back. There should be other ways as well but I am not sure of them.

I can go into the BIOS and do that.

If I do a software update again will it bring this kernel back so I can test?

To my untrained eye it looks like it is something to do with sound. As it is a server, you don't need it (read: can't use it unless you install some extra bits like a desktop). Have you tried disabling sound in the BIOS to see if it helps?

attachment (again)

Attachment, please.