Odd Bluetooth Hang this morning on 4.4.79 HUGE First Boot
All --
This is my Work Laptop -- a Slackware64 14.2 + Multilib System ... Not sure what's what, but my system froze when first booting a 'hand-rolled' 4.4.79.kjh HUGE kernel into runlevel 3 when it was starting Bluetooth. Note: being a REALLY old fart, I always boot to runlevel 3 via /etc/inittab ( id:3:initdefault: ) While 4.4.79.kjh was hung, I tried 'typing' on the Laptop Kbd ( :) thinking maybe I could add entropy :) ) No joy Had to Power off after a couple minutes of messing around. I did not think to try <Alt><F2> for another console. I was not able to save the dmesg file. This was the first boot so I had not yet installed my NVidia blob for 4.4.79.kjh After a power off, I tried booting 4.4.79.kjh HUGE again. It booted normally so I installed NVIDIA-Linux-x86_64-384.59.run and rebooted again. Linux 4.4.79.kjh HUGE + NVidia 384.59 booted fine, though I don't see the familiar-and-comforting NVidia Splash Screen when I startx KDE any more. Just for giggles, I rebooted a couple more times but after the first boot, the system did not hang again. Anyhow, I'll keep an eye on things and try to get more info 'the next time' if that ever comes along. Saved a 'little' :) info below ... -- kjh # dmesg |grep -i blue # note: this output is for the currently running session. The last console message I recall for the hung session was 'Bluetooth: Core ver 2.2' Code:
[ 8.243852] Bluetooth: Core ver 2.21 Code:
root 1279 1 0 06:42 ? 00:00:00 /usr/sbin/bluetoothd Code:
linux-vdso.so.1 (0x00007fff289f2000) Code:
-rwxr-xr-x 1 root root 928 Jul 26 19:44 /usr/lib64/libdbus-1.la Code:
-rw-r--r-- 1 root root 2649 May 31 2016 /var/log/packages/bluez-5.40-x86_64-1 Code:
00:00.0 Host bridge: Intel Corporation Sky Lake Host Bridge/DRAM Registers (rev 07) |
do you run the generic kernel 4.4.75 is slack14.2 your is 4.4.79 seems your usb devices causing an issue run generic with and make an intrid. here is my nvidia-intrid script. you must install the kernel per Pat's docs build it and install it the Salckware way not just make and install. edit the slackware/source/k/scripts for your kernel to install.
git clone https://github.com/Drakeo/update-nvidia-mkinitrd.git |
Drakeo --
Thanks for the reply ! I install and test both GENERIC and HUGE Kernels for each new Kernel, but I always 'first boot' HUGE and then I usually run HUGE too. Note: I still get an error 404 when trying to connect to https://github.com/Drakeo/update-nvidia-mkinitrd.git to look at your mkinitrd script. I don't see the USB errors in my dmesg output ? Is there something I should look for in one of the system logs ? As for initrd ... I install both HUGE and GENERIC Kernels each time I build a new Kernel. And even my HUGE Kernels have an initrd line in /etc/lilo.conf to load the intel-ucode firmware for my CPU ( an Intel i7 6700K ). To simplify things for me and my old-and-forgetful mind, I wrote a wrapper script for Alien Bob's /usr/share/mkinitrd/mkinitrd_command_generator.sh called 'do-mkinitrd_command_generator.sh' ( appended in a code-block below ) The do-mkinitrd_command_generator.sh simply writes a script to execute mkinitrd_command_generator.sh -- mostly so I can inspect the `mkinitrd` commandline before I execute it. Thanks again ! -- kjh These are the entries in /etc/lilo.conf for each installed Kernel ( :) I know, I know ! it is time to remove a few :) ) Code:
image = /boot/vmlinuz-huge-4.4.79.kjh Code:
#!/bin/sh The top of the script is output from Alien Bob's /usr/share/mkinitrd/mkinitrd_command_generator.sh The remaining bash code is there to prepend /boot/intel-ucode.cpio with the native initrd.gz file for the 4.4.79.kjh kernel. The output is versioned so I can keep multiple kernels installed until I get around to cleaning them out of lilo and the file system. Code:
# |
All times are GMT -5. The time now is 11:48 AM. |