[SOLVED] Pi 3, upgrade kernel to version 6.1.32. Local console spewing error messages.

camorri · 06-19-2023, 01:35 PM

I downloaded from the sarpi site the latest kernel for my raspberry pi 3.

I md5sum checked all 5 files and all were good.

Recently, I aquired a TV and attached it to the HDMI port, added a usb keyboard and mouse. All worked as expected on the previous kernel.

Today I devided to upgrade the 5 packages and booted. Booting looks normal up to and including 'starting samba'. After that I get a continuous stream of messages on the console. I did grab a picture of the message stream. Here is what I see.

Quote:

Can't open serial port: No such file or directory
Can't initialize device: No such file or directory
Unable to attach the device! We try again...

This repeats endlessly.

I can ssh into the pi. I looked in inittab to see if a s0 was uncommented, no it is not.

I can boot into run level 1, and the console is then stable and useable. It is unuseable in run level 3 or 4.

I looked in dmesg for a clew, nothing I saw looked like an error.

The pi 3 in a print server, ntp server, and I use it to store the current slackware tree. I have two other systems running current. I can mount the externat disk on the pi, and access files on the HD.

So, the console spew is the issue.

I don't know the boot process well enough to have any idea waht is trying to start a serial post.

Is any one else running 6.1.32 on a pi 3? If yes, is the console functional?

Thoughts on how to track this down?

Any work arounds?

camorri · 06-19-2023, 04:06 PM

I had a look at the system with htop. I saw rc.M burning a lot of cpu cycles. I browsed rc.d, but don't see any reason why after a boot it should still be running. I killed it, and the console spew stopped.

I also rc.local was still running burning cycles. I killed it also. Now the system seems normal.

I started the x server with startx. It all works.

I will boot it tomorrow and see what happens. I don't think I have fixed anything, so I expect the console spew will run again. I will post after another boot.

glorsplitz · 06-19-2023, 06:37 PM

Quote:

# rc.M This file is executed by init(8) when the system is being
# initialized for one of the "multi user" run levels (i.e.
# levels 1 through 6). It usually does mounting of file
# systems et al.

there are many things in rc.M, what did you kill?
you need to be specific

Quote:

I browsed rc.d, but don't see any reason why after a boot it should still be running. I killed it

you need to be specific, what did you kill?

Quote:

rc.local was still running burning cycles. I killed it also.

Quote:

# /etc/rc.d/rc.local: Local system initialization script.
#
# Put any local startup commands in here.

what things do you have in rc.local?
you need to be specific

I have rpi3 running lastest kernel without any issues

Quote:

Linux rpi3.example.net 6.1.32-v7-sarpi3 #1 SMP Wed Jun 14 11:23:03 BST 2023 armv7l BCM2835 GNU/Linux
load average: 0.25, 0.22, 0.19

camorri · 06-19-2023, 06:45 PM

Quote:

you need to be specific, what did you kill?

rc.M was showing 25 percent cpu usage many minutes after booting. I killed rc.M.

Quote:

what things do you have in rc.local?

Here is what is in rc.local on the pi.

Code:

cat rc.local
#!/bin/bash
#
# /etc/rc.d/rc.local:  Local system initialization script.
#
# Put any local startup commands in here.  Also, if you have
# anything that needs to be run at shutdown time you can
# make an /etc/rc.d/rc.local_shutdown script and put those
# commands in there.

# set system date/time at boot from ntp server \ [sarpi3-hacks-3.0]
/usr/sbin/sntp -sS 0.pool.ntp.org > /dev/null 2>&1
echo ondemand | sudo tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor
if ps axc | grep -q bluetoothd; then
        killall bluetoothd
fi
if ps axc | grep -q hciattach; then
        killall hciattach
fi
if lsmod | grep -q hci_uart; then
        rmmod hci_uart
fi
if lsmod | grep -q btbcm; then
        rmmod btbcm
fi
modprobe btbcm
bluetoothd &
while ! hciattach /dev/ttyAMA0 bcm43xx; do
        echo "Unable to attach the device! We try again..."
done

hciconfig hci0 up

if [ -x /etc/rc.d/rc.webmin ]; then
       /etc/rc.d/rc.webmin start
fi

I did not add the bluetooth stuff in rc.local. I am assuming it needs to be there, and the people that got 15.0 going on a pie added those lines.

glorsplitz · 06-19-2023, 07:00 PM

I would cp rc.M, add echo lines before each piece indicating what part of the script it's at as it's running, it's has to be stuck somewhere

same with rc.local

mralk3 · 06-19-2023, 08:55 PM

Please post the contents of your /etc/inittab.

camorri · 06-20-2023, 05:32 AM

Here is inittab.

Code:

cat /etc/inittab
#
# inittab       This file describes how the INIT process should set up
#               the system in a certain run-level.
#
# Version:      @(#)inittab             2.04    17/05/93        MvS
#                                       2.10    02/10/95        PV
#                                       3.00    02/06/1999      PV
#                                       4.00    04/10/2002      PV
#                                      13.37    2011-03-25      PJV
#
# Author:       Miquel van Smoorenburg, <miquels@drinkel.nl.mugnet.org>
# Modified by:  Patrick J. Volkerding, <volkerdi@slackware.com>
#

# These are the default runlevels in Slackware:
#   0 = halt
#   1 = single user mode
#   2 = unused (but configured the same as runlevel 3)
#   3 = multiuser mode (default Slackware runlevel)
#   4 = X11/Wayland with SDDM/KDM/GDM/XDM (session managers)
#   5 = unused (but configured the same as runlevel 3)
#   6 = reboot

# Default runlevel. (Do not set to 0 or 6)
id:3:initdefault:

# System initialization (runs when system boots).
si:S:sysinit:/etc/rc.d/rc.S

# Script to run when going single user (runlevel 1).
su:1S:wait:/etc/rc.d/rc.K

# Script to run when going multi user.
rc:2345:wait:/etc/rc.d/rc.M

# What to do at the "Three Finger Salute".
ca::ctrlaltdel:/sbin/shutdown -t5 -r now

# Runlevel 0 halts the system.
l0:0:wait:/etc/rc.d/rc.0

# Runlevel 6 reboots the system.
l6:6:wait:/etc/rc.d/rc.6

# What to do when power fails.
pf::powerfail:/sbin/genpowerfail start

# If power is back, cancel the running shutdown.
pg::powerokwait:/sbin/genpowerfail stop

# These are the standard console login getties in multiuser mode:
c1:12345:respawn:/sbin/agetty --noclear 38400 tty1 linux
c2:12345:respawn:/sbin/agetty 38400 tty2 linux
#c3:12345:respawn:/sbin/agetty 38400 tty3 linux
#c4:12345:respawn:/sbin/agetty 38400 tty4 linux
#c5:12345:respawn:/sbin/agetty 38400 tty5 linux
#c6:12345:respawn:/sbin/agetty 38400 tty6 linux

# Local serial lines:
#s0:12345:respawn:/sbin/agetty --keep-baud 115200,38400,9600 ttyS1 vt100
#s1:12345:respawn:/sbin/agetty -L ttyS0 9600 vt100
#s2:12345:respawn:/sbin/agetty -L ttyS1 9600 vt100

# Dialup lines:
#d1:12345:respawn:/sbin/agetty -mt60 38400,19200,9600,2400,1200 ttyS0 vt100
#d2:12345:respawn:/sbin/agetty -mt60 38400,19200,9600,2400,1200 ttyS1 vt100

# Runlevel 4 also starts /etc/rc.d/rc.4 to run a display manager for X.
# Display managers are preferred in this order:  gdm, kdm, xdm
x1:4:respawn:/etc/rc.d/rc.4

# End of /etc/inittab

camorri · 06-20-2023, 05:43 AM

I boot the pi3 this morning, and the same results as yesterday.
Htop showed rc.M running constantly, i killed it, and rc.local popped to the top of the htop display, and the spew to the console stopped as soon as I killed rc.local.

Here is the contents of rc.local.

Code:

cat /etc/rc.d/rc.local
#!/bin/bash
#
# /etc/rc.d/rc.local:  Local system initialization script.
#
# Put any local startup commands in here.  Also, if you have
# anything that needs to be run at shutdown time you can
# make an /etc/rc.d/rc.local_shutdown script and put those
# commands in there.

# set system date/time at boot from ntp server \ [sarpi3-hacks-3.0]
/usr/sbin/sntp -sS 0.pool.ntp.org > /dev/null 2>&1
echo ondemand | sudo tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor
if ps axc | grep -q bluetoothd; then
        killall bluetoothd
fi
if ps axc | grep -q hciattach; then
        killall hciattach
fi
if lsmod | grep -q hci_uart; then
        rmmod hci_uart
fi
if lsmod | grep -q btbcm; then
        rmmod btbcm
fi
modprobe btbcm
bluetoothd &
while ! hciattach /dev/ttyAMA0 bcm43xx; do
        echo "Unable to attach the device! We try again..."
done

hciconfig hci0 up

if [ -x /etc/rc.d/rc.webmin ]; then
       /etc/rc.d/rc.webmin start
fi

camorri · 06-20-2023, 08:48 AM

I have confirmed btbcm is loaded, and bluetoothd is running. ( see the end of rc.local ).
I have also confirmed /dev/ttyAMA0 does not exist.

I believe this is the cause of the spew to the console. Killing rc.M and rc.local stops the console spew.

I will investigate bluetooth and try and find out why there is no device in /dev.

camorri · 06-20-2023, 04:23 PM

I have stopped the kernel spew to the console by commenting out all the lines dealing with bluetooth in rc.local.

The system boots without issues, however bluetooth does not work on this system. That is a topic for another thread, so I'm marking this thread solved.

drmozes · 06-25-2023, 03:14 AM

Quote:

Originally Posted by camorri

I downloaded from the sarpi site the latest kernel for my raspberry pi 3.

Have you tried installing Slackware on it?
I don't know if the RPi3 support still works (nothing changed recently apart from the Kernel) as nobody on the team has a working RPi3 now, but you can download the Installer image, write it to a spare SD card if you have one and boot it.
The RPi4 instructions can be followed exactly for the RPi3.

camorri · 06-25-2023, 05:21 AM

Quote:

Have you tried installing Slackware on it?

No, I have not tried installing with these instructions. I have thought about it, though.

Now, I do have the Pi3 behaving itself. The only problem is the bluetooth stack. I do use the without a gui for the most part. When I have some more time, I will give your suggestion a go. Thank-you for the thought.

mralk3 · 06-25-2023, 05:56 PM

You could edit the config.txt in your boot partition that contains all the other pi goodies.
(/boot/config.txt)

Code:

enable_uart=0

On Slackware, that should allow you to have bluetooth and disables the serial connection. It is listed in the [all] section of config.txt on SA64.

drmozes · 06-26-2023, 03:00 AM

Quote:

Originally Posted by mralk3

You could edit the config.txt in your boot partition that contains all the other pi goodies.
(/boot/config.txt)

Code:

enable_uart=0

On Slackware, that should allow you to have bluetooth and disables the serial connection. It is listed in the [all] section of config.txt on SA64.

Thanks, I've added this to the RPi installation guide.

camorri · 06-26-2023, 06:13 AM

Here is what I had in /boot/confi.txt for bluetooth. It was working somewhere in the distant past.

Quote:

# Uncomment to enable Bluetooth LE
dtoverlay=pi3-miniuart-bt
enable_uart=1

and this is what is running.

Quote:

ps aux | grep bluetooth
root 814 0.0 0.3 6040 3348 ? S Jun20 0:00 /usr/sbin/bluetoothd