Odd Bluetooth Hang this morning on 4.4.79 HUGE First Boot

kjhambrick · 07-28-2017, 07:47 AM

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
[    8.243858] Bluetooth: HCI device and connection manager initialized
[    8.243860] Bluetooth: HCI socket layer initialized
[    8.243861] Bluetooth: L2CAP socket layer initialized
[    8.243863] Bluetooth: SCO socket layer initialized
[    8.245107] Bluetooth: HCI UART driver ver 2.3
[    8.245108] Bluetooth: HCI UART protocol H4 registered
[    8.245108] Bluetooth: HCI UART protocol BCSP registered
[    8.245108] Bluetooth: HCI UART protocol LL registered
[    8.245108] Bluetooth: HCI UART protocol ATH3K registered
[    8.245109] Bluetooth: HCI UART protocol Three-wire (H5) registered
[    8.245127] Bluetooth: HCI UART protocol Intel registered
[    8.245139] Bluetooth: HCI UART protocol BCM registered
[    8.245139] Bluetooth: HCI UART protocol QCA registered
[   10.924280] Bluetooth: hci0: using rampatch file: qca/rampatch_usb_00000302.bin
[   10.924280] Bluetooth: hci0: QCA: patch rome 0x302 build 0x138, firmware rome 0x302 build 0x111
[   10.952272] Bluetooth: hci0: using NVM file: qca/nvm_usb_00000302.bin
[   17.676060] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   17.676062] Bluetooth: BNEP filters: protocol multicast
[   17.676064] Bluetooth: BNEP socket layer initialized
[   68.535504] Bluetooth: RFCOMM TTY layer initialized
[   68.535508] Bluetooth: RFCOMM socket layer initialized
[   68.535511] Bluetooth: RFCOMM ver 1.11

# ps -ef |grep -i blue |grep -v 'grep -i blue' # from a KDE 4 Konsole root session

Code:

root      1279     1  0 06:42 ?        00:00:00 /usr/sbin/bluetoothd
konrad    4086     1  0 06:43 ?        00:00:00 /usr/libexec/bluetooth/obexd
konrad    4101     1  0 06:43 ?        00:00:00 /usr/bin/bluedevil-monolithic
konrad    5052  4078  0 06:43 ?        00:00:00 /usr/bin/python2.7 /usr/bin/blueman-applet

# ldd /usr/sbin/bluetoothd

Code:

        linux-vdso.so.1 (0x00007fff289f2000)
        libglib-2.0.so.0 => /usr/lib64/libglib-2.0.so.0 (0x00007f3d5a75e000)
        libdbus-1.so.3 => /usr/lib64/libdbus-1.so.3 (0x00007f3d5a50f000)
        libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f3d5a2f2000)
        libdl.so.2 => /lib64/libdl.so.2 (0x00007f3d5a0ee000)
        librt.so.1 => /lib64/librt.so.1 (0x00007f3d59ee6000)
        libc.so.6 => /lib64/libc.so.6 (0x00007f3d59b1d000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f3d5aa95000)

# ls -la /usr/lib64/libdbus*

Code:

-rwxr-xr-x 1 root root    928 Jul 26 19:44 /usr/lib64/libdbus-1.la
lrwxrwxrwx 1 root root     19 Jul 27 03:31 /usr/lib64/libdbus-1.so -> libdbus-1.so.3.14.6
lrwxrwxrwx 1 root root     19 Jul 27 03:31 /usr/lib64/libdbus-1.so.3 -> libdbus-1.so.3.14.6
-rwxr-xr-x 1 root root 321128 Jul 26 19:44 /usr/lib64/libdbus-1.so.3.14.6
-rwxr-xr-x 1 root root   1168 Mar  3  2016 /usr/lib64/libdbus-glib-1.la
lrwxrwxrwx 1 root root     23 Mar  6  2016 /usr/lib64/libdbus-glib-1.so -> libdbus-glib-1.so.2.3.3
lrwxrwxrwx 1 root root     23 Mar  6  2016 /usr/lib64/libdbus-glib-1.so.2 -> libdbus-glib-1.so.2.3.3
-rwxr-xr-x 1 root root 160672 Mar  3  2016 /usr/lib64/libdbus-glib-1.so.2.3.3
lrwxrwxrwx 1 root root     19 Feb  8  2016 /usr/lib64/libdbusmenu-qt.so -> libdbusmenu-qt.so.2
lrwxrwxrwx 1 root root     23 Feb  8  2016 /usr/lib64/libdbusmenu-qt.so.2 -> libdbusmenu-qt.so.2.6.0
-rwxr-xr-x 1 root root 207952 Jul 30  2012 /usr/lib64/libdbusmenu-qt.so.2.6.0

# ver bluez dbus # note: `ver` is a local script that did in this case: ls -la /var/log/packages/*[Bb][Ll][Uu][Ee][Zz]* /var/log/packages/*[Dd][Bb][Uu][Ss]*

Code:

-rw-r--r-- 1 root root 2649 May 31  2016 /var/log/packages/bluez-5.40-x86_64-1
-rw-r--r-- 1 root root 1119 Feb  8  2016 /var/log/packages/bluez-firmware-1.2-x86_64-1
-rw-r--r-- 1 root root 4083 Jul 27 03:31 /var/log/packages/dbus-1.10.8-x86_64-2_slack14.2
-rw-r--r-- 1 root root 1587 Jul 27 03:38 /var/log/packages/dbus-compat32-1.10.8-x86_64-2_slack14.2compat32
-rw-r--r-- 1 root root 2784 Mar  6  2016 /var/log/packages/dbus-glib-0.106-x86_64-1
-rw-r--r-- 1 root root  961 Mar 12  2016 /var/log/packages/dbus-glib-compat32-0.106-x86_64-1compat32
-rw-r--r-- 1 root root 4284 Apr  2  2016 /var/log/packages/dbus-python-1.2.4-x86_64-1
-rw-r--r-- 1 root root 5793 Feb  8  2016 /var/log/packages/libdbusmenu-qt-0.9.2-x86_64-2

# lspci

Code:

00:00.0 Host bridge: Intel Corporation Sky Lake Host Bridge/DRAM Registers (rev 07)
00:01.0 PCI bridge: Intel Corporation Sky Lake PCIe Controller (x16) (rev 07)
00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller (rev 31)
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H Thermal subsystem (rev 31)
00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI #1 (rev 31)
00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA controller [AHCI mode] (rev 31)
00:1b.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Root Port #17 (rev f1)
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #1 (rev f1)
00:1c.6 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #7 (rev f1)
00:1c.7 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #8 (rev f1)
00:1d.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #9 (rev f1)
00:1d.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #13 (rev f1)
00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31)
00:1f.3 Audio device: Intel Corporation Sunrise Point-H HD Audio (rev 31)
00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31)
01:00.0 VGA compatible controller: NVIDIA Corporation GM204M [GeForce GTX 970M] (rev a1)
01:00.1 Audio device: NVIDIA Corporation GM204 High Definition Audio Controller (rev a1)
02:00.0 SATA controller: Samsung Electronics Co Ltd Device a801 (rev 01)
3c:00.0 Ethernet controller: Qualcomm Atheros Killer E2400 Gigabit Ethernet Controller (rev 10)
3d:00.0 SD Host controller: Realtek Semiconductor Co., Ltd. RTS5250 PCI Express Card Reader (rev 01)
3e:00.0 SATA controller: Samsung Electronics Co Ltd Device a801 (rev 01)
3f:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32)

Drakeo · 07-29-2017, 12:34 AM

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

kjhambrick · 07-29-2017, 06:08 AM

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
  root   = /dev/sda3
  initrd = /boot/intel-ucode.cpio
  label  = Linux4479H.kjh
  read-only
image    = /boot/vmlinuz-generic-4.4.79.kjh
  root   = /dev/sda3
  initrd = /boot/initrd-generic-4.4.79.kjh-ucode.gz
  label  = Linux4479G.kjh
  read-only
image    = /boot/vmlinuz-huge-4.4.78.kjh
  root   = /dev/sda3
  initrd = /boot/intel-ucode.cpio
  label  = Linux4478H.kjh
  read-only
image    = /boot/vmlinuz-generic-4.4.78.kjh
  root   = /dev/sda3
  initrd = /boot/initrd-generic-4.4.78.kjh-ucode.gz
  label  = Linux4478G.kjh
  read-only
image    = /boot/vmlinuz-huge-4.4.77.kjh
  root   = /dev/sda3
  initrd = /boot/intel-ucode.cpio
  label  = Linux4477H.kjh
  read-only
image    = /boot/vmlinuz-generic-4.4.77.kjh
  root   = /dev/sda3
  initrd = /boot/initrd-generic-4.4.77.kjh-ucode.gz
  label  = Linux4477G.kjh
  read-only
image    = /boot/vmlinuz-huge-4.4.76.kjh
  root   = /dev/sda3
  initrd = /boot/intel-ucode.cpio
  label  = Linux4476H.kjh
  read-only
image    = /boot/vmlinuz-generic-4.4.76.kjh
  root   = /dev/sda3
  initrd = /boot/initrd-generic-4.4.76.kjh-ucode.gz
  label  = Linux4476G.kjh
  read-only
image    = /boot/vmlinuz-huge-4.4.75
  root   = /dev/sda3
  initrd = /boot/intel-ucode.cpio
  label  = Slack4475H
  read-only
image    = /boot/vmlinuz-generic-4.4.75
  root   = /dev/sda3
  initrd = /boot/initrd-generic-4.4.75-ucode.gz
  label  = Slack4475G
  read-only

This is the do-mkinitrd_command_generator.sh script

Code:

#!/bin/sh
#
WriteIt=0
DoUCode=1
UCodeFile="/boot/intel-ucode.cpio"

OutDir="/root/tmp/update-logs/initrd"        # edit me !  This is where stuff is written

[ "$1" = "-w" ] && WriteIt=1 && shift 

[ $# -lt 1 ] && echo "usage:  `basename $0` [ -w ] KernelVersion" >&2 && exit 1

[ "$DoUCode" = "1" -a ! -f "$UCodeFile" ] && echo "cannot find $UCodeFile ... ABORT" && exit 2

Version="$1"

UCodeInit="initrd-generic-$Version-ucode.gz"

[ ! -f "/boot/vmlinuz-generic-$Version" ] && echo "cannot find a generic kernel version $Version" >&2 && exit 2

/usr/share/mkinitrd/mkinitrd_command_generator.sh \
   -k $Version \
   -a          \
   "-o $OutDir/initrd-generic-$Version.gz"    |
   if [ "$WriteIt" != "1" ]
   then
      cat
   else
      cat > "do-mkinitrd-$Version.sh"
   fi

   if [ "$DoUCode" = "1" ]
   then
      echo "#"
      echo "# prepending the latest intel microcode as $UCodeInit"
      echo "#"
      echo "cat $UCodeFile $OutDir/initrd-generic-$Version.gz > $OutDir/$UCodeInit"
      echo "#"
      echo "echo \"# all done.\""
      echo "ls -la $OutDir/initrd-generic-$Version.gz /root/tmp/$UCodeInit"
      echo "echo \"# \""
      echo "echo \"# check around ... if all went well, invoke the following cp command.\""
      echo "echo \"# \""
      echo "echo \"# cp -p $OutDir/initrd-generic-$Version.gz $OutDir/$UCodeInit /boot/\""
   fi |
   if [ "$WriteIt" != "1" ]
   then
      cat
   else
      cat >> "do-mkinitrd-$Version.sh"
      chmod 700 "do-mkinitrd-$Version.sh"

      echo "#"
      echo "# do-mkinitrd-$Version.sh is ready to run"
   fi

This is the script generated by `do-mkinitrd-generator.sh -w 4.4.79.kjh` ( the output script is named: do-mkinitrd-4.4.79.kjh.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:

#
# mkinitrd_command_generator.sh revision 1.45
#
# This script will now make a recommendation about the command to use
# in case you require an initrd image to boot a kernel that does not
# have support for your storage or root filesystem built in
# (such as the Slackware 'generic' kernels').
# A suitable 'mkinitrd' command will be:

mkinitrd -c -k 4.4.79.kjh -f ext4 -r /dev/sda3 -m xhci-pci:ohci-pci:ehci-pci:xhci-hcd:uhci-hcd:ehci-hcd:hid:usbhid:i2c-hid:hid_generic:hid-cherry:hid-logitech:hid-logitech-dj:hid-logitech-hidpp:hid-lenovo:hid-microsoft:hid_multitouch:jbd2:mbcache:ext4 -u -o /root/tmp/update-logs/initrd/initrd-generic-4.4.79.kjh.gz
#
# prepending the latest intel microcode as initrd-generic-4.4.79.kjh-ucode.gz
#
cat /boot/intel-ucode.cpio /root/tmp/update-logs/initrd/initrd-generic-4.4.79.kjh.gz > /root/tmp/update-logs/initrd/initrd-generic-4.4.79.kjh-ucode.gz
#
echo "# all done."
ls -la /root/tmp/update-logs/initrd/initrd-generic-4.4.79.kjh.gz /root/tmp/initrd-generic-4.4.79.kjh-ucode.gz
echo "# "
echo "# check around ... if all went well, invoke the following cp command."
echo "# "
echo "# cp -p /root/tmp/update-logs/initrd/initrd-generic-4.4.79.kjh.gz /root/tmp/update-logs/initrd/initrd-generic-4.4.79.kjh-ucode.gz /boot/"