Experiencing intermittent boot issue...

Netrunner Rolling Rolling 2016.01
1

Sometimes when I boot, the process appears to start normally, but then it suddenly becomes corrupted filling the screen with a list. This moves so quickly that I don’t see any initial error message. See the attached pic.

This happens maybe about 20% of the time. The other 80% are normal boots. Is there a log file that should capture all of the output? If so, I could post some of that here.

The question is: what is likely to cause this, and how could I fix it? My hope is that its not a hardware problem… Thanks.

2

That looks to me like a kernel panic, these are harder to diagnose as they are usually related to a hardware failure.
You can use this command to see if you can find the culprit:

sudo journalctl --dmesg

If you catch it on the next boot you can use this instread:

journalctl --since=today
3

Yes, I was afraid of this probably being a hardware issue. In them meantime I realized that I think this problem arose since I added an Adaptec 8405 RAID controller.

Checking the Adaptec site, I find Linux drivers are provided for Debian, Fedora, Red Hat, SuSE, and Ubuntu. Arch, etc. is not officially supported, but they do provide a link to Linux driver source code.

And I’m not having any issues like BSOD on my Windows side using the official drivers.

Is it likely this could be related to the new RAID card? And if so, any chance I can get this supported?

Thanks

4

The aacraid driver module is provided by the kernel out of the box.
What does the following command give you:

inxi -R

This could also be an IRQ conflict issue, have you tried moving the card to a different slot?

5

Yes, I thought the driver would be included in the kernel. But then I wondered why Adaptec seems to provide links to variouis Linux drivers.

I received the following output for that command.

[code]$ inxi -R

RAID: No RAID data: /proc/mdstat missing-is md_mod kernel module loaded?[/code]

Not sure if I can move the RAID card to a different slot. My PCIe slots are highly populated: 2 x video card, and 1 sound card.

Also, what should I look for in the journalctl --dmesg that would be suspicious? Only red text error messages or could there be other indications?

Thanks again.

6

Strange, there must be some reason the module isn’t loading.
Can you please give me the output of inxi -F and lspci?

7

Yes, see the following.

Any thoughts on why I sometimes get a kernel panic at boot? Thanks.

$ inxi -F System: Host: mike-pc Kernel: 4.4.11-1-MANJARO x86_64 (64 bit) Desktop: KDE Plasma 5.6.4 Distro: Netrunner Rolling Edition Machine: Mobo: ASUSTeK model: RAMPAGE IV EXTREME v: Rev 1.xx Bios: American Megatrends v: 4901 date: 05/14/2014 CPU: Hexa core Intel Core i7-3930K (-MCP-) cache: 12288 KB clock speeds: max: 5700 MHz 1: 3299 MHz 2: 3298 MHz 3: 3200 MHz 4: 3298 MHz 5: 3199 MHz 6: 3200 MHz Graphics: Card-1: NVIDIA GK110B [GeForce GTX TITAN Black] Card-2: NVIDIA GK110B [GeForce GTX TITAN Black] Display Server: X.Org 1.17.4 driver: nvidia Resolution: 2560x1600@59.97hz GLX Renderer: GeForce GTX TITAN Black/PCIe/SSE2 GLX Version: 4.5.0 NVIDIA 364.19 Audio: Card-1 2x NVIDIA GK110 HDMI Audio driver: snd_hda_intelsnd_hda_intel Sound: ALSA v: k4.4.11-1-MANJARO Card-2 Creative Labs EMU20k2 [X-Fi Titanium Series] driver: snd_ctxfi Network: Card: Intel 82579V Gigabit Network Connection driver: e1000e IF: eno1 state: up speed: 100 Mbps duplex: full mac: d8:50:e6:d1:28:f2 Drives: HDD Total Size: 1720.1GB (2.4% used) ID-1: /dev/sda model: INTEL_SSDSC2BW24 size: 240.1GB ID-2: /dev/sdb model: WDC_WD1000DHTZ size: 1000.2GB ID-3: /dev/sdc model: LogicalDrv_0 size: 479.8GB Partition: ID-1: / size: 66G used: 34G (54%) fs: ext4 dev: /dev/sda4 ID-2: swap-1 size: 2.15GB used: 0.00GB (0%) fs: swap dev: /dev/sda5 ID-3: swap-2 size: 0.56GB used: 0.00GB (0%) fs: swap dev: /dev/zram0 ID-4: swap-3 size: 0.56GB used: 0.00GB (0%) fs: swap dev: /dev/zram1 ID-5: swap-4 size: 0.56GB used: 0.00GB (0%) fs: swap dev: /dev/zram2 ID-6: swap-5 size: 0.56GB used: 0.00GB (0%) fs: swap dev: /dev/zram3 ID-7: swap-6 size: 0.56GB used: 0.00GB (0%) fs: swap dev: /dev/zram4 ID-8: swap-7 size: 0.56GB used: 0.00GB (0%) fs: swap dev: /dev/zram5 Sensors: System Temperatures: cpu: 36.0C mobo: N/A gpu: 25C Fan Speeds (in rpm): cpu: N/A Info: Processes: 209 Uptime: 1 min Memory: 1136.6/15991.8MB Client: Shell (bash) inxi: 2.3.0

$ lspci 00:00.0 Host bridge: Intel Corporation Xeon E5/Core i7 DMI2 (rev 07) 00:01.0 PCI bridge: Intel Corporation Xeon E5/Core i7 IIO PCI Express Root Port 1a (rev 07) 00:02.0 PCI bridge: Intel Corporation Xeon E5/Core i7 IIO PCI Express Root Port 2a (rev 07) 00:03.0 PCI bridge: Intel Corporation Xeon E5/Core i7 IIO PCI Express Root Port 3a in PCI Express Mode (rev 07) 00:03.2 PCI bridge: Intel Corporation Xeon E5/Core i7 IIO PCI Express Root Port 3c (rev 07) 00:05.0 System peripheral: Intel Corporation Xeon E5/Core i7 Address Map, VTd_Misc, System Management (rev 07) 00:05.2 System peripheral: Intel Corporation Xeon E5/Core i7 Control Status and Global Errors (rev 07) 00:05.4 PIC: Intel Corporation Xeon E5/Core i7 I/O APIC (rev 07) 00:11.0 PCI bridge: Intel Corporation C600/X79 series chipset PCI Express Virtual Root Port (rev 06) 00:16.0 Communication controller: Intel Corporation C600/X79 series chipset MEI Controller #1 (rev 05) 00:19.0 Ethernet controller: Intel Corporation 82579V Gigabit Network Connection (rev 06) 00:1a.0 USB controller: Intel Corporation C600/X79 series chipset USB2 Enhanced Host Controller #2 (rev 06) 00:1c.0 PCI bridge: Intel Corporation C600/X79 series chipset PCI Express Root Port 1 (rev b6) 00:1c.1 PCI bridge: Intel Corporation C600/X79 series chipset PCI Express Root Port 2 (rev b6) 00:1c.2 PCI bridge: Intel Corporation C600/X79 series chipset PCI Express Root Port 3 (rev b6) 00:1c.3 PCI bridge: Intel Corporation C600/X79 series chipset PCI Express Root Port 4 (rev b6) 00:1c.4 PCI bridge: Intel Corporation C600/X79 series chipset PCI Express Root Port 5 (rev b6) 00:1c.5 PCI bridge: Intel Corporation C600/X79 series chipset PCI Express Root Port 6 (rev b6) 00:1c.7 PCI bridge: Intel Corporation C600/X79 series chipset PCI Express Root Port 8 (rev b6) 00:1d.0 USB controller: Intel Corporation C600/X79 series chipset USB2 Enhanced Host Controller #1 (rev 06) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a6) 00:1f.0 ISA bridge: Intel Corporation C600/X79 series chipset LPC Controller (rev 06) 00:1f.2 SATA controller: Intel Corporation C600/X79 series chipset 6-Port SATA AHCI Controller (rev 06) 00:1f.3 SMBus: Intel Corporation C600/X79 series chipset SMBus Host Controller (rev 06) 01:00.0 VGA compatible controller: NVIDIA Corporation GK110B [GeForce GTX TITAN Black] (rev a1) 01:00.1 Audio device: NVIDIA Corporation GK110 HDMI Audio (rev a1) 02:00.0 Audio device: Creative Labs EMU20k2 [X-Fi Titanium Series] (rev 03) 03:00.0 VGA compatible controller: NVIDIA Corporation GK110B [GeForce GTX TITAN Black] (rev a1) 03:00.1 Audio device: NVIDIA Corporation GK110 HDMI Audio (rev a1) 04:00.0 RAID bus controller: Adaptec Series 8 12G SAS/PCIe 3 (rev 01) 07:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller 08:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller 09:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller 0a:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller 0b:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 01) 0c:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 01)

8

Unfortunately, other than the raid controller, I have no idea what could be causing your issue at this point.
The last error that I can see in your initial screen shot is ata4.00 related.

9

I have not experienced one of the kernel panics in the last few days. I did look through the journalctl output. The only thing that looked somewhat suspicious in there was the following.

Not sure how to fix this, and not sure if it could be related to the kernel panics…

Jun 02 16:26:52 mike-pc kernel: NVRM: Your system is not currently configured to drive a VGA console Jun 02 16:26:52 mike-pc kernel: NVRM: on the primary VGA device. The NVIDIA Linux graphics driver Jun 02 16:26:52 mike-pc kernel: NVRM: requires the use of a text-mode VGA console. Use of other console Jun 02 16:26:52 mike-pc kernel: NVRM: drivers including, but not limited to, vesafb, may result in Jun 02 16:26:52 mike-pc kernel: NVRM: corruption and stability problems, and is not supported.

Also, is there anything I should do about the md_mod kernel module not being loaded?

Thanks :shy:

10

Could be, the nvrm error has to do with the nvidia driver and the framebuffer for the console. this is a common issue on UEFI systems. There maybe some grub options, etc. you can use to fix the issue with the framebuffer and your nvidia cards, a search online may be helpful for that error.

I’m not 100% sure on how raid works, but your controller card would use the aacraid module. I believe the md_mod driver is used for software raid solutions.

11

I was advised to check the systemd journal, which I did as follows.

Any action I should take based on this output?

Thanks again!

[code]$ journalctl -p 3 -xb

– Logs begin at Wed 2016-03-02 15:35:05 CST, end at Sat 2016-06-04 04:28:02 CDT. –
Jun 04 04:25:07 mike-pc systemd[1]: dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device: Dev dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device appeared twice with different sysfs paths /sys/devices/p
Jun 04 04:25:07 mike-pc nmbd[1801]: [2016/06/04 04:25:07.857032, 0] …/lib/util/become_daemon.c:135(daemon_status)
Jun 04 04:25:07 mike-pc nmbd[1801]: STATUS=daemon ‘nmbd’ : No local IPv4 non-loopback interfaces available, waiting for interface …NOTE: NetBIOS name resolution is not supported for Internet Protocol Version 6 (IPv6).
Jun 04 04:25:08 mike-pc smbd[1818]: [2016/06/04 04:25:08.014124, 0] …/lib/util/become_daemon.c:124(daemon_ready)
Jun 04 04:25:08 mike-pc smbd[1818]: STATUS=daemon ‘smbd’ finished starting up and ready to serve connections
Jun 04 04:25:10 mike-pc ntpd[1986]: bind(21) AF_INET6 fe80::eb40:ac46:2515:f638%2#123 flags 0x11 failed: Cannot assign requested address
Jun 04 04:25:10 mike-pc ntpd[1986]: unable to create socket on eno1 (5) for fe80::eb40:ac46:2515:f638%2#123
Jun 04 04:25:11 mike-pc ntpd[1986]: bind(24) AF_INET6 fe80::eb40:ac46:2515:f638%2#123 flags 0x11 failed: Cannot assign requested address
Jun 04 04:25:11 mike-pc ntpd[1986]: unable to create socket on eno1 (6) for fe80::eb40:ac46:2515:f638%2#123
Jun 04 04:25:11 mike-pc nmbd[1801]: [2016/06/04 04:25:11.795277, 0] …/lib/util/become_daemon.c:124(daemon_ready)
Jun 04 04:25:11 mike-pc nmbd[1801]: STATUS=daemon ‘nmbd’ finished starting up and ready to serve connections
Jun 04 04:25:44 mike-pc nmbd[1801]: [2016/06/04 04:25:44.875026, 0] …/source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
Jun 04 04:25:44 mike-pc nmbd[1801]: *****
Jun 04 04:25:44 mike-pc nmbd[1801]:
Jun 04 04:25:44 mike-pc nmbd[1801]: Samba name server MIKE-PC is now a local master browser for workgroup WORKGROUP on subnet 192.168.0.6
Jun 04 04:25:44 mike-pc nmbd[1801]:
Jun 04 04:25:44 mike-pc nmbd[1801]: *****
Jun 04 04:26:01 mike-pc systemd-coredump[2109]: Process 2105 (ksplashqml) of user 1000 dumped core.

                                            Stack trace of thread 2105:
                                            #0  0x00007f1aa41d89b7 _ZN7QObject11setPropertyEPKcRK8QVariant (libQt5Core.so.5)                                                                                                   
                                            #1  0x00000000004062ce n/a (ksplashqml)                                                                                                                                            
                                            #2  0x0000000000404f7c n/a (ksplashqml)                                                                                                                                            
                                            #3  0x00000000004055bb n/a (ksplashqml)                                                                                                                                            
                                            #4  0x000000000040450e n/a (ksplashqml)                                                                                                                                            
                                            #5  0x00007f1aa381a741 __libc_start_main (libc.so.6)                                                                                                                               
                                            #6  0x0000000000404569 _start (ksplashqml)                                                                                                                                         
                                                                                                                                                                                                                               
                                            Stack trace of thread 2107:                                                                                                                                                        
                                            #0  0x00007f1aa38d868d poll (libc.so.6)                                                                                                                                            
                                            #1  0x00007f1aa079afd6 n/a (libglib-2.0.so.0)                                                                                                                                      
                                            #2  0x00007f1aa079b0ec g_main_context_iteration (libglib-2.0.so.0)                                                                                                                 
                                            #3  0x00007f1aa41f972f _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5)                                                       
                                            #4  0x00007f1aa41a14ca _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5)                                                                                     
                                            #5  0x00007f1aa3fc82f3 _ZN7QThread4execEv (libQt5Core.so.5)                                                                                                                        
                                            #6  0x00007f1aa32be915 n/a (libQt5Qml.so.5)                                                                                                                                        
                                            #7  0x00007f1aa3fcd1d8 n/a (libQt5Core.so.5)                                                                                                                                       
                                            #8  0x00007f1aa204d474 start_thread (libpthread.so.0)                                                                                                                              
                                            #9  0x00007f1aa38e169d __clone (libc.so.6)                                                                                                                                         
                                                                                                                                                                                                                               
                                            Stack trace of thread 2106:                                                                                                                                                        
                                            #0  0x00007f1aa38d868d poll (libc.so.6)
                                            #1  0x000000382080aae2 n/a (libxcb.so.1)
                                            #2  0x000000382080c757 xcb_wait_for_event (libxcb.so.1)
                                            #3  0x00007f1a992fea79 n/a (libQt5XcbQpa.so.5)
                                            #4  0x00007f1aa3fcd1d8 n/a (libQt5Core.so.5)
                                            #5  0x00007f1aa204d474 start_thread (libpthread.so.0)
                                            #6  0x00007f1aa38e169d __clone (libc.so.6)

– Subject: Process 2105 (ksplashqml) dumped core
– Defined-By: systemd
– Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
– Documentation: man:core(5)

– Process 2105 (ksplashqml) crashed and dumped core.

– This usually indicates a programming error in the crashing program and
– should be reported to its vendor as a bug.[/code]

12

All that is telling me is that you have a drive that is being seen twice at duiferent pathsm, and that ksplash has crashed.
This is very likely the nvidia driver that is causing the crash.

13

So far the kernel panics have not returned since the most recent update. It would be nice if that resolved my problem.

Is there a way to correct the drive being seen twice in different paths, or is that something I needn’t be concerned about?

Thanks

14

Are you having issues with the drives not mounting, etc.?
If not, then I wouldn’t worry about it.

15

No, haven’t had any problems with drives not mounting, so I won’t worry about it.

Thanks :slight_smile: