donbrew
Posts: 78
Joined: Sun Sep 04, 2016 2:32 pm

Can't auto mount NFS shares, manually works

Wed Jun 24, 2020 3:29 am

This thread covers the problem in Raspberry Pi OS Buster and Ubuntu 20.04. https://www.raspberrypi.org/forums/vie ... #p1684506
I can mount a NFS share using

Code: Select all

mount -a
if the line is in fstab it will not mount on boot.
I can mount a NFS share using

Code: Select all

systemctl start mnt-tv3.mount
it will not mount on boot.

The error seems to trace back to RPC files not working. I think nfs-utils is now part of the kernel, it appears to be faulty.
My kernel is 4.19.118-v71+


I finally got it working by adding some option to fstab

Code: Select all

defaults,rw,user,exec,noauto,x-systemd.automount

itsmedoofer
Posts: 404
Joined: Wed Sep 25, 2013 8:43 am

Re: STICKY: Buster bug report thread

Thu Jun 25, 2020 2:30 pm

Hi,

I'm not sure if this is the definition of a Buster bug but I have found some packages that are available in Debian Buster ARMHF but not in the PiOS32 repo.

This following thread has the details..

viewtopic.php?f=66&t=277658#p1685428

bobg
Posts: 11
Joined: Mon Dec 26, 2011 8:56 am
Location: London, UK

Cloned SDcard boot: first of many FAILED errors "Failed to start Remount Root and Kernel File Systems"

Wed Jul 01, 2020 8:53 pm

Originally reported 6 posts earlier - i have now better defined my issue.

Starting with "2020-05-27-raspios-buster-lite-armhf.img" I built an image with all my required options. This master SD card worked nicely, however cloned SD cards have many FAILED messages on boot. The first error was "Failed to start Remount Root and Kernel File Systems".

I use a Debian system via command line to make and clone my SD cards. I use the dd command for copying.

The master SD card needs to be at least slightly bigger than the cloned SD card eg 16G and 15.9G to fail - I was just unlucky!

The Remount failed because partition 2 did not have a PARTUUID.

The PARTUUID is not stored on the SD card but is determined on boot. It checks the partition is valid and then uses the label-id from the MBR to generates the PARTUUID as seen by BLKID etc. If partition 2 is not valid then no PARTUUID is generated - I suspect this is a relative new check or updated check.

On the cloned SD card:
sudo sfdisk -V /dev/mmcblk0
reports
"Total allocated sectors 31334400 greater than the maximum 30703616"

When building my master I modify /etc/init.d/resize2fs_once to add a parameter of +3600M to the resize2fs command.
However It would appear that the rpi always expands partition 2 to fill the SD card.

Thus smaller SD cards always fail to boot.

I can resolve this by setting partition 2 to +3600M, and the cloned SD card now boots successfully (on cards down to 4G)

I believe there is an issue with the rpi always expanding partition 2 to fill the SD card.
It would be nice if this could be controlled via the /etc/init.d/resize2fs_once file.

fik
Posts: 37
Joined: Thu Jan 17, 2013 1:34 pm

zstd causes Bus error

Fri Jul 03, 2020 8:15 am

There is a problem with zstd package in recent Raspberry Pi OS (armhf). When trying to compress anything with zstd and default or low compression, it generates a Bus error and stops. The version is zstd-1.3.8+dfsg-3+rpi1. I think it used to work in the past. I'm using RPi4.

Code: Select all

zstd file 
Bus error
Debian 10.4 zstd-1.3.8+dfsg-3 works fine both for armhf and aarch64. Experimental Raspberry Pi OS aarch64 works as well, here the version is zstd-1.3.8+dfsg-3 (probably from Debian).

The Bus error occurs when compression level is between 1 and 4 (default compression level without specifying anything is 3). From 5 up, there is no error. Decompression is also fine.

zstd -3 file.... crash
zstd -5 file.... OK

beta-tester
Posts: 1384
Joined: Fri Jan 04, 2013 1:57 pm
Location: de_DE

ifconfig & gnome-system-monitor: RX bytes overflow at 4 GByte

Sat Jul 04, 2020 1:30 pm

hi, is it normal, that ipconfig (and gnome-system-monitor) can not show RX bytes higher that 4GBytes (4294967295 bytes )?
it overflows and then it is starting from 0 bytes again over and over.

is it an issue only for the 32bit Raspberry Pi OS version
{ I only give negative feedback }
RPi B (256MB), B (512MB), B+, ZeroW; 2B; 3B, 3B+; 4B (4GB)

User avatar
DougieLawson
Posts: 39192
Joined: Sun Jun 16, 2013 11:19 pm
Location: A small cave in deepest darkest Basingstoke, UK
Contact: Website Twitter

Re: ifconfig & gnome-system-monitor: RX bytes overflow at 4 GByte

Sat Jul 04, 2020 2:23 pm

beta-tester wrote:
Sat Jul 04, 2020 1:30 pm
hi, is it normal, that ipconfig [sic] (and gnome-system-monitor) can not show RX bytes higher that 4GBytes (4294967295 bytes )?
Looks like it's probably a bug with ifconfig using a 32-bit unsigned integer. It may be a kernel bug.

Do you get the same with ip -s link?

This is from a machine with uptime of 146 days.

Code: Select all

2: enxb827eb5fffed: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
    link/ether b8:27:eb:5f:ff:ed brd ff:ff:ff:ff:ff:ff
    RX: bytes  packets  errors  dropped overrun mcast
    17993561521 207650749 0       0       0       0
    TX: bytes  packets  errors  dropped carrier collsns
    2758251376 28835863 0       0       0       0
This is from my other machine that's been up for the same number of days

Code: Select all

3: wlxd47bb07a1fa2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DORMANT group default qlen 1000
    link/ether d4:7b:b0:7a:1f:a2 brd ff:ff:ff:ff:ff:ff
    RX: bytes  packets  errors  dropped overrun mcast
    123841701  194758072 0       11608   0       185915387
    TX: bytes  packets  errors  dropped carrier collsns
    1507610074 16434668 0       0       0       0


So I can't tell whether it's a kernel bug.
Note: Any requirement to use a crystal ball or mind reading will result in me ignoring your question.

Criticising any questions is banned on this forum.

Any DMs sent on Twitter will be answered next month.
All non-medical doctors are on my foes list.

beta-tester
Posts: 1384
Joined: Fri Jan 04, 2013 1:57 pm
Location: de_DE

Re: ifconfig & gnome-system-monitor: RX bytes overflow at 4 GByte

Sat Jul 04, 2020 4:40 pm

DougieLawson wrote:
Sat Jul 04, 2020 2:23 pm
beta-tester wrote:
Sat Jul 04, 2020 1:30 pm
hi, is it normal, that ipconfig [sic] (and gnome-system-monitor) can not show RX bytes higher that 4GBytes (4294967295 bytes )?
Looks like it's probably a bug with ifconfig using a 32-bit unsigned integer. It may be a kernel bug.

Do you get the same with ip -s link?
yes, i get the exact same wrong values with ip -s link
{ I only give negative feedback }
RPi B (256MB), B (512MB), B+, ZeroW; 2B; 3B, 3B+; 4B (4GB)

User avatar
DougieLawson
Posts: 39192
Joined: Sun Jun 16, 2013 11:19 pm
Location: A small cave in deepest darkest Basingstoke, UK
Contact: Website Twitter

Re: STICKY: Buster bug report thread

Sat Jul 04, 2020 4:59 pm

OK. That means it's a kernel bug (or limitation) and you'll have to ask Linus Torvalds to fix it for you.
Note: Any requirement to use a crystal ball or mind reading will result in me ignoring your question.

Criticising any questions is banned on this forum.

Any DMs sent on Twitter will be answered next month.
All non-medical doctors are on my foes list.

trejan
Posts: 2204
Joined: Tue Jul 02, 2019 2:28 pm

Re: ifconfig & gnome-system-monitor: RX bytes overflow at 4 GByte

Sat Jul 04, 2020 6:34 pm

beta-tester wrote:
Sat Jul 04, 2020 1:30 pm
hi, is it normal, that ipconfig (and gnome-system-monitor) can not show RX bytes higher that 4GBytes (4294967295 bytes )?
it overflows and then it is starting from 0 bytes again over and over.

is it an issue only for the 32bit Raspberry Pi OS version
It is normal and it is fixed with a 64-bit kernel. The net_device_ops counters are 32-bit on a 32-bit OS unless the network interface driver implements the optional ndo_get_stats64 for 64-bit counters. Only the old LAN9512/LAN9514 driver implemented that. The LAN7514 in the 3B+ and BCM GENET in the 4B don't have ndo_get_stats64 but does have the ethtool interface instead. You can look at the counters on that by using "ethtool -S eth0"

beta-tester
Posts: 1384
Joined: Fri Jan 04, 2013 1:57 pm
Location: de_DE

Re: ifconfig & gnome-system-monitor: RX bytes overflow at 4 GByte

Sat Jul 04, 2020 8:02 pm

DougieLawson wrote:
Sat Jul 04, 2020 4:59 pm
OK. That means it's a kernel bug (or limitation) and you'll have to ask Linus Torvalds to fix it for you.
Linus Torvalds will kick me when a nobody will ask him for fixing it... :lol:
(and even then, it will not find its way to RaspiOS in time)
trejan wrote:
Sat Jul 04, 2020 6:34 pm
You can look at the counters on that by using "ethtool -S eth0"
thank you for spotting this command... will see if it serves my need.
EDIT: no, it also flips from 4G over to 0 or do i misunderstand the values?
is there something like a counter that counts the overflows?
{ I only give negative feedback }
RPi B (256MB), B (512MB), B+, ZeroW; 2B; 3B, 3B+; 4B (4GB)

trejan
Posts: 2204
Joined: Tue Jul 02, 2019 2:28 pm

Re: ifconfig & gnome-system-monitor: RX bytes overflow at 4 GByte

Sat Jul 04, 2020 11:33 pm

beta-tester wrote:
Sat Jul 04, 2020 8:02 pm
trejan wrote:
Sat Jul 04, 2020 6:34 pm
You can look at the counters on that by using "ethtool -S eth0"
thank you for spotting this command... will see if it serves my need.
EDIT: no, it also flips from 4G over to 0 or do i misunderstand the values?
is there something like a counter that counts the overflows?
Hmm. Which Pi are you using? Looking at the code more closely, it looks like the LAN78xx driver for the 3B+ does try to handle counter overflow. The BCM GENET driver for the Pi 4 does have ethtool_get_stats callback but it it just using an unsigned 32-bit int for the counter so it overflows.

You'll have to use the 64-bit kernel if you want to count > 4GB.

beta-tester
Posts: 1384
Joined: Fri Jan 04, 2013 1:57 pm
Location: de_DE

Re: ifconfig & gnome-system-monitor: RX bytes overflow at 4 GByte

Sun Jul 05, 2020 4:26 am

i am using RPi4B (4GByte), but with the 32bit kernel
Linux pxe-server 4.19.118-v7l+ #1311 SMP Mon Apr 27 14:26:42 BST 2020 armv7l GNU/Linux
{ I only give negative feedback }
RPi B (256MB), B (512MB), B+, ZeroW; 2B; 3B, 3B+; 4B (4GB)

AdamMiltonBarker
Posts: 11
Joined: Sun May 15, 2016 2:48 am
Location: Spain
Contact: Website Facebook

Re: STICKY: Buster bug report thread

Fri Jul 10, 2020 7:31 pm

Hi on RPI3 I have installed Raspberry OS, on the RPI4 it works fine but I cannot access WiFi nor Bluetooth on RPI3 anymore (I have used this device many times and both have worked fine, today I did a fresh install).

At startup I get the error;

"failed to start configure bluetooth modems connected by uart"

When I try raspi-config it says no Wifi adapter found, I have gone through nearly every post with the same issue, none of the solutions have solved this. Any advice guys ?

Right now at startup it is stuck at Started Daily apt upgrade and clean activities.
Adam Milton-Barker
President & Lead Developer Asociacion De Investigacion En Inteligencia Artificial Para La Leucemia Peter Moss

mike.308
Posts: 1
Joined: Sat Jul 11, 2020 1:17 am

Re: STICKY: Buster bug report thread

Sat Jul 11, 2020 1:29 am

Howdy.
A day ago I have collected my PI 4 B 8GB.
I have started downloading the minimal version of Pi OS, then I've installed gnome by apt. For some reasons I couldn't make it cooperate with a wireless AP. Despite iwlist was able to find the ESSID, the gnome manager was always popping out "No network available". Ive tried with several different APs. Since the iwlist throws out the network info, I assume this is different than wifi jamming by own HDMI port.

Then, I have downloaded the PiOS which includes the desktop and the wifi access was perfect.

Being sure I have all the packets and user group privileges, I've installed the gnome over again. And again the same problem replicated. "No network available" on gnome.

beta-tester
Posts: 1384
Joined: Fri Jan 04, 2013 1:57 pm
Location: de_DE

Re: STICKY: Buster bug report thread

Sat Jul 11, 2020 5:59 am

AdamMiltonBarker wrote:
Fri Jul 10, 2020 7:31 pm
Hi on RPI3 I have installed Raspberry OS, on the RPI4 it works fine but I cannot access WiFi nor Bluetooth on RPI3 anymore
last month i had a similar issue to run WiFi on an SD-card prepared on an RPi4B and using it on an RPi3B.
by using the same SD-card, WiFi was working on the RPi4B but not on the RPi3B.
in my case i had to "unblock" WiFi on the RPi3B with the command

Code: Select all

sudo rfkill unblock wlan
sudo rfkill unblock bluetooth
after running this command on the RPi3B, i was able to use WiFi on both RPi's.
maybe it will help you too.
{ I only give negative feedback }
RPi B (256MB), B (512MB), B+, ZeroW; 2B; 3B, 3B+; 4B (4GB)

AdamMiltonBarker
Posts: 11
Joined: Sun May 15, 2016 2:48 am
Location: Spain
Contact: Website Facebook

Re: STICKY: Buster bug report thread

Sat Jul 11, 2020 10:01 pm

beta-tester wrote:
Sat Jul 11, 2020 5:59 am
AdamMiltonBarker wrote:
Fri Jul 10, 2020 7:31 pm
Hi on RPI3 I have installed Raspberry OS, on the RPI4 it works fine but I cannot access WiFi nor Bluetooth on RPI3 anymore
last month i had a similar issue to run WiFi on an SD-card prepared on an RPi4B and using it on an RPi3B.
by using the same SD-card, WiFi was working on the RPi4B but not on the RPi3B.
in my case i had to "unblock" WiFi on the RPi3B with the command

Code: Select all

sudo rfkill unblock wlan
sudo rfkill unblock bluetooth
after running this command on the RPi3B, i was able to use WiFi on both RPi's.
maybe it will help you too.
Thanks I have already tried that I have two additional RPI3's I am going to load Buster on them and see if I get the issue again on another device.
Adam Milton-Barker
President & Lead Developer Asociacion De Investigacion En Inteligencia Artificial Para La Leucemia Peter Moss

AdamMiltonBarker
Posts: 11
Joined: Sun May 15, 2016 2:48 am
Location: Spain
Contact: Website Facebook

Re: STICKY: Buster bug report thread

Sun Jul 12, 2020 12:01 am

So I have a weird situation which I am putting down to damaged boards I guess. Using official power source, valid sd cards/images, this is what I have, all with Buster lite, in the results below all use the same functioning psu and sd:

- 1 Raspberry Pi 2 Model B V1: Boots fine, act led flashes normally and screen works.
- 1 Raspberry Pi 2 Model B V1: Doesn't boot, solid act led, screen does not work.
- 1 Raspberry Pi 3 Model B V1.2 : Boots fine, no act led activity at all, bluetooth and wifi do not work (interfaces not found), screen works, can login.
- 1 Rasberry Pi 3 Model B+ (Donated to us today was working before Buster I assume): Does not boot, no act led, screen does not work.
- 1 Rasberry Pi 3 Model B+ (Donated to us today was working before Buster I assume): Boots fine, act led fine, screen works, wifi / bluetooth work.
- 1 Rasberry Pi 4 Model B: All fine.

If anyone notices a pattern let me know but I am guessing I have some damaged boards :D

Update, trying a different psu on the non working RPI 2, it works lol, I was able to get 1 flash on the act led of the non working 3B+ by applying some pressure, but haven't been able to repeat that or get it booted.
Adam Milton-Barker
President & Lead Developer Asociacion De Investigacion En Inteligencia Artificial Para La Leucemia Peter Moss

User avatar
led-bloon
Posts: 14
Joined: Mon Dec 03, 2012 4:48 am
Location: Oz

FreeCAD 0.18 crashes

Mon Jul 13, 2020 5:35 am

FreeCAD 0.18 crashes on a Pi 4B 4G - Buster - 32 or 64 bit kernel. Same result on a Pi 3B+
From the opening screen...
Selecting 'File - New' or 'File - Open' results in a complete crash of the program (back to desktop).
FreeCAD 0.16 on Stretch OS runs ok on a Pi 3B+.
led

user1
Posts: 14
Joined: Thu Apr 23, 2015 4:06 pm
Location: India

RPi 4 as wireless access point using hostapd doesn't work correctly. Works using Network manager.

Mon Jul 13, 2020 3:19 pm

I followed https://www.raspberrypi.org/documentati ... -routed.md to set up Pi 4 as wireless access point. Pi shows up as hotspot and devices can connect sometimes. The hotspot sometimes disappears. Devices try to connect but doesn't accept connections. I installed network manager in raspberry pi OS 32 bit using https://gist.github.com/jjsanderson/ab2 ... 81b14a537a and the wireless access point works perfectly. Also tried wireless access point on ubuntu server 20.04 on pi 4 using network manger (nm-connection-editor) and it works.

NimbUx
Posts: 174
Joined: Fri Jan 03, 2020 10:33 am

loadkeys --console bug ?

Thu Jul 16, 2020 9:19 am

The loadkeys command appears to always affect ALL virtual consoles,
even when including "-C device" or "--console=device" (although it accepts it
without reporting an error).

I suspect, but haven't verified, this bug coming from "upstream" (Debian) or maybe
even "more up-stream" Linux...

LTolledo
Posts: 3500
Joined: Sat Mar 17, 2018 7:29 am
Location: Anime Heartland

Re: STICKY: Buster bug report thread

Mon Jul 20, 2020 2:43 pm

Logitech USB receiver not working on RPi3B+ after upgrade to "5.4"
full dmesg below:

Code: Select all

pi@RPi3BP1:~ $ dmesg
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 5.4.51-v7+ (dom@buildbot) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611)) #1326 SMP Fri Jul 17 10:45:25 BST 2020
[    0.000000] CPU: ARMv7 Processor [410fd034] revision 4 (ARMv7), cr=10c5383d
[    0.000000] CPU: div instructions available: patching division code
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] OF: fdt: Machine model: Raspberry Pi 3 Model B Plus Rev 1.3
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] Reserved memory: created CMA memory pool at 0x2fc00000, size 64 MiB
[    0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool
[    0.000000] On node 0 totalpages: 211968
[    0.000000]   Normal zone: 1656 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 211968 pages, LIFO batch:63
[    0.000000] percpu: Embedded 20 pages/cpu s49792 r8192 d23936 u81920
[    0.000000] pcpu-alloc: s49792 r8192 d23936 u81920 alloc=20*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 210312
[    0.000000] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_headphones=1 bcm2708_fb.fbwidth=720 bcm2708_fb.fbheight=576 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000  console=ttyS0,115200 console=tty1 root=PARTUUID=ecbd3bda-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes, linear)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes, linear)
[    0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
[    0.000000] Memory: 760548K/847872K available (8192K kernel code, 681K rwdata, 2532K rodata, 1024K init, 824K bss, 21788K reserved, 65536K cma-reserved)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] ftrace: allocating 27966 entries in 55 pages
[    0.000000] rcu: Hierarchical RCU implementation.
[    0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
[    0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[    0.000000] random: get_random_bytes called from start_kernel+0x328/0x4e8 with crng_init=0
[    0.000000] arch_timer: cp15 timer(s) running at 19.20MHz (phys).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns
[    0.000007] sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every 4398046511078ns
[    0.000022] Switching to timer-based delay loop, resolution 52ns
[    0.000286] Console: colour dummy device 80x30
[    0.000868] printk: console [tty1] enabled
[    0.000932] Calibrating delay loop (skipped), value calculated using timer frequency.. 38.40 BogoMIPS (lpj=192000)
[    0.000981] pid_max: default: 32768 minimum: 301
[    0.001325] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes, linear)
[    0.001371] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes, linear)
[    0.002563] CPU: Testing write buffer coherency: ok
[    0.003132] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.004090] Setting up static identity map for 0x100000 - 0x10003c
[    0.004311] rcu: Hierarchical SRCU implementation.
[    0.005007] smp: Bringing up secondary CPUs ...
[    0.006146] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.007402] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
[    0.008554] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
[    0.008706] smp: Brought up 1 node, 4 CPUs
[    0.008795] SMP: Total of 4 processors activated (153.60 BogoMIPS).
[    0.008824] CPU: All CPU(s) started in HYP mode.
[    0.008848] CPU: Virtualization extensions available.
[    0.009776] devtmpfs: initialized
[    0.026148] VFP support v0.3: implementor 41 architecture 3 part 40 variant 3 rev 4
[    0.026451] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.026508] futex hash table entries: 1024 (order: 4, 65536 bytes, linear)
[    0.029546] pinctrl core: initialized pinctrl subsystem
[    0.030760] NET: Registered protocol family 16
[    0.034936] DMA: preallocated 1024 KiB pool for atomic coherent allocations
[    0.041174] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
[    0.041216] hw-breakpoint: maximum watchpoint size is 8 bytes.
[    0.041452] Serial: AMBA PL011 UART driver
[    0.043387] bcm2835-mbox 3f00b880.mailbox: mailbox enabled
[    0.060083] raspberrypi-firmware soc:firmware: Attached to firmware from 2020-07-17 11:04, variant start
[    0.070096] raspberrypi-firmware soc:firmware: Firmware hash is 21a15cb094f41c7506ad65d2cb9b29c550693057
[    0.121105] bcm2835-dma 3f007000.dma: DMA legacy API manager, dmachans=0x1
[    0.123279] SCSI subsystem initialized
[    0.123550] usbcore: registered new interface driver usbfs
[    0.123631] usbcore: registered new interface driver hub
[    0.123782] usbcore: registered new device driver usb
[    0.125778] clocksource: Switched to clocksource arch_sys_counter
[    1.284068] VFS: Disk quotas dquot_6.6.0
[    1.284223] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    1.284426] FS-Cache: Loaded
[    1.284668] CacheFiles: Loaded
[    1.294226] thermal_sys: Registered thermal governor 'step_wise'
[    1.294618] NET: Registered protocol family 2
[    1.295569] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes, linear)
[    1.295636] TCP established hash table entries: 8192 (order: 3, 32768 bytes, linear)
[    1.295824] TCP bind hash table entries: 8192 (order: 4, 65536 bytes, linear)
[    1.296035] TCP: Hash tables configured (established 8192 bind 8192)
[    1.296218] UDP hash table entries: 512 (order: 2, 16384 bytes, linear)
[    1.296292] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes, linear)
[    1.296602] NET: Registered protocol family 1
[    1.297480] RPC: Registered named UNIX socket transport module.
[    1.297511] RPC: Registered udp transport module.
[    1.297537] RPC: Registered tcp transport module.
[    1.297563] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    1.299290] hw perfevents: enabled with armv7_cortex_a7 PMU driver, 7 counters available
[    1.302585] Initialise system trusted keyrings
[    1.302846] workingset: timestamp_bits=30 max_order=18 bucket_order=0
[    1.313224] FS-Cache: Netfs 'nfs' registered for caching
[    1.313982] NFS: Registering the id_resolver key type
[    1.314062] Key type id_resolver registered
[    1.314089] Key type id_legacy registered
[    1.314126] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    1.315421] Key type asymmetric registered
[    1.315450] Asymmetric key parser 'x509' registered
[    1.315528] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249)
[    1.315566] io scheduler mq-deadline registered
[    1.315593] io scheduler kyber registered
[    1.319170] bcm2708_fb soc:fb: FB found 1 display(s)
[    1.336135] Console: switching to colour frame buffer device 90x36
[    1.343013] bcm2708_fb soc:fb: Registered framebuffer for display 0, size 720x576
[    1.351984] bcm2835-rng 3f104000.rng: hwrng registered
[    1.356286] vc-mem: phys_addr:0x00000000 mem_base=0x3ec00000 mem_size:0x40000000(1024 MiB)
[    1.364449] vc-sm: Videocore shared memory driver
[    1.368683] gpiomem-bcm2835 3f200000.gpiomem: Initialised: Registers at 0x3f200000
[    1.384112] brd: module loaded
[    1.399678] loop: module loaded
[    1.404686] Loading iSCSI transport class v2.0-870.
[    1.409320] libphy: Fixed MDIO Bus: probed
[    1.413070] usbcore: registered new interface driver lan78xx
[    1.416884] usbcore: registered new interface driver smsc95xx
[    1.420614] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
[    2.152596] Core Release: 2.80a
[    2.156299] Setting default values for core params
[    2.159941] Finished setting default values for core params
[    2.363935] Using Buffer DMA mode
[    2.367528] Periodic Transfer Interrupt Enhancement - disabled
[    2.371144] Multiprocessor Interrupt Enhancement - disabled
[    2.374774] OTG VER PARAM: 0, OTG VER FLAG: 0
[    2.378405] Dedicated Tx FIFOs mode
[    2.382664] WARN::dwc_otg_hcd_init:1074: FIQ DMA bounce buffers: virt = afd14000 dma = 0xefd14000 len=9024
[    2.390122] FIQ FSM acceleration enabled for :
               Non-periodic Split Transactions
               Periodic Split Transactions
               High-Speed Isochronous Endpoints
               Interrupt/Control Split Transaction hack enabled
[    2.408203] dwc_otg: Microframe scheduler enabled
[    2.408271] WARN::hcd_init_fiq:457: FIQ on core 1
[    2.411893] WARN::hcd_init_fiq:458: FIQ ASM at 806bdc88 length 36
[    2.415492] WARN::hcd_init_fiq:497: MPHI regs_base at b4010000
[    2.419056] dwc_otg 3f980000.usb: DWC OTG Controller
[    2.422563] dwc_otg 3f980000.usb: new USB bus registered, assigned bus number 1
[    2.426117] dwc_otg 3f980000.usb: irq 56, io mem 0x00000000
[    2.429514] Init: Port Power? op_state=1
[    2.432827] Init: Power Port (0)
[    2.436414] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.04
[    2.442987] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.446513] usb usb1: Product: DWC OTG Controller
[    2.449990] usb usb1: Manufacturer: Linux 5.4.51-v7+ dwc_otg_hcd
[    2.453484] usb usb1: SerialNumber: 3f980000.usb
[    2.457734] hub 1-0:1.0: USB hub found
[    2.461281] hub 1-0:1.0: 1 port detected
[    2.465463] dwc_otg: FIQ enabled
[    2.465473] dwc_otg: NAK holdoff enabled
[    2.465483] dwc_otg: FIQ split-transaction FSM enabled
[    2.465497] Module dwc_common_port init
[    2.465905] usbcore: registered new interface driver usb-storage
[    2.469598] mousedev: PS/2 mouse device common for all mice
[    2.474449] bcm2835-wdt bcm2835-wdt: Broadcom BCM2835 watchdog timer
[    2.479394] cpufreq: cpufreq_online: CPU0: Running at unlisted freq: 600000 KHz
[    2.485646] cpufreq: cpufreq_online: CPU0: Unlisted initial frequency changed to: 700000 KHz
[    2.492323] sdhci: Secure Digital Host Controller Interface driver
[    2.495476] sdhci: Copyright(c) Pierre Ossman
[    2.499067] mmc-bcm2835 3f300000.mmcnr: could not get clk, deferring probe
[    2.502669] sdhost-bcm2835 3f202000.mmc: could not get clk, deferring probe
[    2.506000] sdhci-pltfm: SDHCI platform and OF driver helper
[    2.510833] ledtrig-cpu: registered to indicate activity on CPUs
[    2.514371] hidraw: raw HID events driver (C) Jiri Kosina
[    2.517793] usbcore: registered new interface driver usbhid
[    2.521033] usbhid: USB HID core driver
[    2.525066] vchiq: vchiq_init_state: slot_zero = (ptrval)
[    2.529948] [vc_sm_connected_init]: start
[    2.539841] [vc_sm_connected_init]: end - returning 0
[    2.544566] Initializing XFRM netlink socket
[    2.547823] NET: Registered protocol family 17
[    2.551111] Key type dns_resolver registered
[    2.554832] Registering SWP/SWPB emulation handler
[    2.558317] registered taskstats version 1
[    2.561440] Loading compiled-in X.509 certificates
[    2.564891] Key type ._fscrypt registered
[    2.568041] Key type .fscrypt registered
[    2.579991] uart-pl011 3f201000.serial: cts_event_workaround enabled
[    2.583080] 3f201000.serial: ttyAMA0 at MMIO 0x3f201000 (irq = 81, base_baud = 0) is a PL011 rev2
[    2.590805] bcm2835-power bcm2835-power: Broadcom BCM2835 power domains driver
[    2.595345] mmc-bcm2835 3f300000.mmcnr: mmc_debug:0 mmc_debug2:0
[    2.598626] mmc-bcm2835 3f300000.mmcnr: DMA channel allocated
[    2.628173] sdhost: log_buf @ (ptrval) (efd13000)
[    2.668326] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
[    2.673068] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[    2.676316] Indeed it is in host mode hprt0 = 00021501
[    2.739395] mmc0: sdhost-bcm2835 loaded - DMA enabled (>1)
[    2.744601] of_cfs_init
[    2.747771] of_cfs_init: OK
[    2.751436] Waiting for root device PARTUUID=ecbd3bda-02...
[    2.758489] random: fast init done
[    2.763299] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[    2.769075] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
[    2.834265] mmc0: host does not support reading read-only switch, assuming write-enable
[    2.841469] mmc0: new high speed SDHC card at address aaaa
[    2.845177] mmcblk0: mmc0:aaaa SC16G 14.8 GiB
[    2.848611] mmc1: new high speed SDIO card at address 0001
[    2.857914]  mmcblk0: p1 p2
[    2.885827] usb 1-1: new high-speed USB device number 2 using dwc_otg
[    2.888925] Indeed it is in host mode hprt0 = 00001101
[    2.891437] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[    2.897923] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
[    2.912394] devtmpfs: mounted
[    2.953688] Freeing unused kernel memory: 1024K
[    2.976141] Run /sbin/init as init process
[    3.126152] usb 1-1: New USB device found, idVendor=0424, idProduct=2514, bcdDevice= b.b3
[    3.132625] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    3.136598] hub 1-1:1.0: USB hub found
[    3.139887] hub 1-1:1.0: 4 ports detected
[    3.455831] usb 1-1.1: new high-speed USB device number 3 using dwc_otg
[    3.586121] usb 1-1.1: New USB device found, idVendor=0424, idProduct=2514, bcdDevice= b.b3
[    3.592521] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    3.596612] hub 1-1.1:1.0: USB hub found
[    3.600085] hub 1-1.1:1.0: 3 ports detected
[    3.646821] systemd[1]: System time before build time, advancing clock.
[    3.695828] usb 1-1.2: new full-speed USB device number 4 using dwc_otg
[    3.796297] NET: Registered protocol family 10
[    3.800932] Segment Routing with IPv6
[    3.827818] usb 1-1.2: New USB device found, idVendor=1a86, idProduct=8074, bcdDevice=a2.41
[    3.834994] usb 1-1.2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    3.839318] systemd[1]: systemd 241 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid)
[    3.839588] hub 1-1.2:1.0: USB hub found
[    3.859954] systemd[1]: Detected architecture arm.
[    3.864181] hub 1-1.2:1.0: 4 ports detected
[    3.946585] systemd[1]: Set hostname to <RPi3BP1>.
[    4.185852] usb 1-1.2.1: new full-speed USB device number 5 using dwc_otg
[    4.323200] usb 1-1.2.1: New USB device found, idVendor=046d, idProduct=c534, bcdDevice=29.00
[    4.330550] usb 1-1.2.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    4.342829] input: HID 046d:c534 as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2/1-1.2.1/1-1.2.1:1.0/0003:046D:C534.0001/input/input0
[    4.415838] usb 1-1.1.1: new high-speed USB device number 6 using dwc_otg
[    4.416609] hid-generic 0003:046D:C534.0001: input,hidraw0: USB HID v1.11 Keyboard [HID 046d:c534] on usb-3f980000.usb-1.2.1/input0
[    4.437625] input: HID 046d:c534 Mouse as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2/1-1.2.1/1-1.2.1:1.1/0003:046D:C534.0002/input/input1
[    4.446059] input: HID 046d:c534 Consumer Control as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2/1-1.2.1/1-1.2.1:1.1/0003:046D:C534.0002/input/input2
[    4.526095] input: HID 046d:c534 System Control as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2/1-1.2.1/1-1.2.1:1.1/0003:046D:C534.0002/input/input3
[    4.534934] hid-generic 0003:046D:C534.0002: input,hiddev96,hidraw1: USB HID v1.11 Mouse [HID 046d:c534] on usb-3f980000.usb-1.2.1/input1
[    4.546262] usb 1-1.1.1: New USB device found, idVendor=0424, idProduct=7800, bcdDevice= 3.00
[    4.554859] usb 1-1.1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    4.588968] systemd[1]: /lib/systemd/system/smbd.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/samba/smbd.pid → /run/samba/smbd.pid; please update the unit file accordingly.
[    4.678556] systemd[1]: /lib/systemd/system/nmbd.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/samba/nmbd.pid → /run/samba/nmbd.pid; please update the unit file accordingly.
[    4.828393] lan78xx 1-1.1.1:1.0 (unnamed net_device) (uninitialized): No External EEPROM. Setting MAC Speed
[    4.838836] libphy: lan78xx-mdiobus: probed
[    4.861183] random: systemd: uninitialized urandom read (16 bytes read)
[    4.872595] lan78xx 1-1.1.1:1.0 (unnamed net_device) (uninitialized): int urb period 64
[    4.901429] systemd[1]: Condition check resulted in Journal Audit Socket being skipped.
[    4.906504] random: systemd: uninitialized urandom read (16 bytes read)
[    4.913759] systemd[1]: Created slice system-getty.slice.
[    4.924188] random: systemd: uninitialized urandom read (16 bytes read)
[    4.929956] systemd[1]: Listening on Journal Socket.
[    4.940526] systemd[1]: Listening on udev Kernel Socket.
[    4.954266] systemd[1]: Mounting RPC Pipe File System...
[    5.089710] i2c /dev entries driver
[    5.235857] usb 1-1.1.2: new full-speed USB device number 7 using dwc_otg
[    5.375711] usb 1-1.1.2: New USB device found, idVendor=0d8c, idProduct=0014, bcdDevice= 1.00
[    5.375729] usb 1-1.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    5.375740] usb 1-1.1.2: Product: USB Audio Device
[    5.375801] usb 1-1.1.2: Manufacturer: C-Media Electronics Inc.
[    5.381456] input: C-Media Electronics Inc. USB Audio Device as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.3/0003:0D8C:0014.0003/input/input6
[    5.446273] hid-generic 0003:0D8C:0014.0003: input,hidraw2: USB HID v1.00 Device [C-Media Electronics Inc. USB Audio Device] on usb-3f980000.usb-1.1.2/input3
[    5.719751] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[    5.821371] systemd-journald[110]: Received request to flush runtime journal from PID 1
[    6.707601] mc: Linux media interface: v0.10
[    6.809308] usbcore: registered new interface driver snd-usb-audio
[    7.077056] vc_sm_cma: module is from the staging directory, the quality is unknown, you have been warned.
[    7.079251] bcm2835_vc_sm_cma_probe: Videocore shared memory driver
[    7.079274] [vc_sm_connected_init]: start
[    7.082437] [vc_sm_connected_init]: installed successfully
[    7.125528] videodev: Linux video capture interface: v2.00
[    7.136262] snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned.
[    7.161971] bcm2835_audio bcm2835_audio: card created with 4 channels
[    7.163061] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
[    7.163065] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
[    7.174866] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
[    7.177594] bcm2835_isp: module is from the staging directory, the quality is unknown, you have been warned.
[    7.181417] bcm2835_v4l2: module is from the staging directory, the quality is unknown, you have been warned.
[    7.183947] bcm2835_audio bcm2835_audio: card created with 4 channels
[    7.196365] bcm2835-isp bcm2835-isp: Device node output[0] registered as /dev/video13
[    7.202600] bcm2835-isp bcm2835-isp: Device node capture[0] registered as /dev/video14
[    7.206694] bcm2835-isp bcm2835-isp: Device node capture[1] registered as /dev/video15
[    7.207844] bcm2835-isp bcm2835-isp: Device node stats[2] registered as /dev/video16
[    7.207880] bcm2835-isp bcm2835-isp: Register output node 0 with media controller
[    7.207917] bcm2835-isp bcm2835-isp: Register capture node 1 with media controller
[    7.207933] bcm2835-isp bcm2835-isp: Register capture node 2 with media controller
[    7.207948] bcm2835-isp bcm2835-isp: Register capture node 3 with media controller
[    7.208647] bcm2835-isp bcm2835-isp: Loaded V4L2 bcm2835-isp
[    7.218637] bcm2835_codec: module is from the staging directory, the quality is unknown, you have been warned.
[    7.243797] bcm2835-codec bcm2835-codec: Device registered as /dev/video10
[    7.243852] bcm2835-codec bcm2835-codec: Loaded V4L2 decode
[    7.247514] bcm2835-codec bcm2835-codec: Device registered as /dev/video11
[    7.247574] bcm2835-codec bcm2835-codec: Loaded V4L2 encode
[    7.305003] bcm2835-codec bcm2835-codec: Device registered as /dev/video12
[    7.305068] bcm2835-codec bcm2835-codec: Loaded V4L2 isp
[    7.593478] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[    7.769198] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[    7.856050] brcmfmac: F1 signature read @0x18000000=0x15264345
[    7.863777] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[    7.864698] usbcore: registered new interface driver brcmfmac
[    7.929222] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt failed with error -2
[    7.947279] logitech-djreceiver 0003:046D:C534.0001: hidraw0: USB HID v1.11 Keyboard [HID 046d:c534] on usb-3f980000.usb-1.2.1/input0
[    8.000588] random: crng init done
[    8.000601] random: 7 urandom warning(s) missed due to ratelimiting
[    8.145885] usb 1-1.1.3: new high-speed USB device number 8 using dwc_otg
[    8.155088] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[    8.206037] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Mar  2 2020 23:30:41 version 7.45.202 (r724630 CY) FWID 01-72f6ece2
[    8.278032] usb 1-1.1.3: New USB device found, idVendor=174c, idProduct=55aa, bcdDevice= 1.00
[    8.278052] usb 1-1.1.3: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[    8.278064] usb 1-1.1.3: Product: Best USB Device
[    8.278076] usb 1-1.1.3: Manufacturer: ULT-Best
[    8.278104] usb 1-1.1.3: SerialNumber: 041911145862
[    8.279517] usb 1-1.1.3: The driver for the USB controller dwc_otg_hcd does not support scatter-gather which is
[    8.279535] usb 1-1.1.3: required by the UAS driver. Please try an other USB controller if you wish to use UAS.
[    8.279549] usb-storage 1-1.1.3:1.0: USB Mass Storage device detected
[    8.281194] usb-storage 1-1.1.3:1.0: Quirks match for vid 174c pid 55aa: 400000
[    8.281412] scsi host0: usb-storage 1-1.1.3:1.0
[    8.389554] logitech-djreceiver 0003:046D:C534.0002: hiddev96,hidraw1: USB HID v1.11 Mouse [HID 046d:c534] on usb-3f980000.usb-1.2.1/input1
[    8.451571] usbcore: registered new interface driver uas
[    8.463760] logitech-djreceiver 0003:046D:C534.0002: logi_dj_probe: logi_dj_recv_query_paired_devices error:-32
[    9.359466] scsi 0:0:0:0: Direct-Access     MARSHAL  MAL22000SA-T54   0    PQ: 0 ANSI: 6
[    9.362661] sd 0:0:0:0: [sda] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
[    9.362680] sd 0:0:0:0: [sda] 4096-byte physical blocks
[    9.364426] sd 0:0:0:0: [sda] Write Protect is off
[    9.364447] sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
[    9.365244] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    9.440122] sd 0:0:0:0: Attached scsi generic sg0 type 0
[    9.694027]  sda: sda1
[    9.707477] sd 0:0:0:0: [sda] Attached SCSI disk
[    9.724356] uart-pl011 3f201000.serial: no DMA platform data
[    9.733147] 8021q: 802.1Q VLAN Support v1.8
[   10.471702] Adding 102396k swap on /var/swap.  Priority:-2 extents:6 across:151548k SSFS
[   10.866149] 8021q: adding VLAN 0 to HW filter on device eth0
[   10.871808] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   16.914175] Bluetooth: Core ver 2.22
[   16.914252] NET: Registered protocol family 31
[   16.914259] Bluetooth: HCI device and connection manager initialized
[   16.914282] Bluetooth: HCI socket layer initialized
[   16.914294] Bluetooth: L2CAP socket layer initialized
[   16.914317] Bluetooth: SCO socket layer initialized
[   16.926361] Bluetooth: HCI UART driver ver 2.3
[   16.926377] Bluetooth: HCI UART protocol H4 registered
[   16.926437] Bluetooth: HCI UART protocol Three-wire (H5) registered
[   16.926631] Bluetooth: HCI UART protocol Broadcom registered
[   17.239257] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   17.239271] Bluetooth: BNEP filters: protocol multicast
[   17.239287] Bluetooth: BNEP socket layer initialized
[   17.347874] Bluetooth: RFCOMM TTY layer initialized
[   17.347900] Bluetooth: RFCOMM socket layer initialized
[   17.347923] Bluetooth: RFCOMM ver 1.11
[   22.592766] fuse: init (API version 7.31)
[   24.800273] FS-Cache: Netfs 'cifs' registered for caching
[   24.815631] Key type cifs.spnego registered
[   24.815649] Key type cifs.idmap registered
[   24.816714] CIFS: Attempting to mount //192.168.11.51/HDD4TB
[   25.077473] CIFS: Attempting to mount //192.168.11.161/NAS4TB
[   25.256497] CIFS: Attempting to mount //192.168.11.1/disk1_pt1
[   25.979817] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
[   27.994077] logitech-djreceiver 0003:046D:C534.0002: delayedwork_callback: logi_dj_recv_query_paired_devices error: -32
[   28.490042] logitech-djreceiver 0003:046D:C534.0002: delayedwork_callback: logi_dj_recv_query_paired_devices error: -32
[   29.001916] logitech-djreceiver 0003:046D:C534.0002: delayedwork_callback: logi_dj_recv_query_paired_devices error: -32
[   42.024693] usb 1-1.2-port1: cannot reset (err = -32)
[   42.024804] usb 1-1.2-port1: cannot reset (err = -32)
[   42.024928] usb 1-1.2-port1: cannot reset (err = -32)
[   42.025052] usb 1-1.2-port1: cannot reset (err = -32)
[   42.025175] usb 1-1.2-port1: cannot reset (err = -32)
[   42.025185] usb 1-1.2-port1: Cannot enable. Maybe the USB cable is bad?
[   42.025306] usb 1-1.2-port1: cannot disable (err = -32)
[   42.025427] usb 1-1.2-port1: cannot reset (err = -32)
[   42.025552] usb 1-1.2-port1: cannot reset (err = -32)
[   42.025677] usb 1-1.2-port1: cannot reset (err = -32)
[   42.025843] usb 1-1.2-port1: cannot reset (err = -32)
[   42.026057] usb 1-1.2-port1: cannot reset (err = -32)
[   42.026066] usb 1-1.2-port1: Cannot enable. Maybe the USB cable is bad?
[   42.026186] usb 1-1.2-port1: cannot disable (err = -32)
[   42.026308] usb 1-1.2-port1: cannot reset (err = -32)
[   42.026429] usb 1-1.2-port1: cannot reset (err = -32)
[   42.026553] usb 1-1.2-port1: cannot reset (err = -32)
[   42.026678] usb 1-1.2-port1: cannot reset (err = -32)
[   42.026809] usb 1-1.2-port1: cannot reset (err = -32)
[   42.026818] usb 1-1.2-port1: Cannot enable. Maybe the USB cable is bad?
[   42.026928] usb 1-1.2-port1: cannot disable (err = -32)
[   42.027053] usb 1-1.2-port1: cannot reset (err = -32)
[   42.027176] usb 1-1.2-port1: cannot reset (err = -32)
[   42.027307] usb 1-1.2-port1: cannot reset (err = -32)
[   42.027427] usb 1-1.2-port1: cannot reset (err = -32)
[   42.027552] usb 1-1.2-port1: cannot reset (err = -32)
[   42.027561] usb 1-1.2-port1: Cannot enable. Maybe the USB cable is bad?
[   42.027677] usb 1-1.2-port1: cannot disable (err = -32)
[   42.027803] usb 1-1.2-port1: cannot disable (err = -32)
[   42.028557] hub 1-1.2:1.0: hub_ext_port_status failed (err = -32)
[   42.269586] usb 1-1.2: USB disconnect, device number 4
[   42.269607] usb 1-1.2.1: USB disconnect, device number 5
[   44.355819] usb 1-1.3: new full-speed USB device number 9 using dwc_otg
[   44.487710] usb 1-1.3: New USB device found, idVendor=1a86, idProduct=8074, bcdDevice=a2.41
[   44.487728] usb 1-1.3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[   44.488725] hub 1-1.3:1.0: USB hub found
[   44.489310] hub 1-1.3:1.0: 4 ports detected
[   44.805819] usb 1-1.3.1: new full-speed USB device number 10 using dwc_otg
[   44.942090] usb 1-1.3.1: New USB device found, idVendor=046d, idProduct=c534, bcdDevice=29.00
[   44.942108] usb 1-1.3.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[   44.950817] logitech-djreceiver 0003:046D:C534.0004: hidraw0: USB HID v1.11 Keyboard [HID 046d:c534] on usb-3f980000.usb-1.3.1/input0
[   45.026408] logitech-djreceiver 0003:046D:C534.0005: hiddev96,hidraw1: USB HID v1.11 Mouse [HID 046d:c534] on usb-3f980000.usb-1.3.1/input1
[   45.097423] logitech-djreceiver 0003:046D:C534.0005: logi_dj_probe: logi_dj_recv_query_paired_devices error:-32
[   46.280079] logitech-djreceiver 0003:046D:C534.0005: delayedwork_callback: logi_dj_recv_query_paired_devices error: -32
[   46.792072] logitech-djreceiver 0003:046D:C534.0005: delayedwork_callback: logi_dj_recv_query_paired_devices error: -32
[   47.288078] logitech-djreceiver 0003:046D:C534.0005: delayedwork_callback: logi_dj_recv_query_paired_devices error: -32
[   47.800078] logitech-djreceiver 0003:046D:C534.0005: delayedwork_callback: logi_dj_recv_query_paired_devices error: -32
[   48.312079] logitech-djreceiver 0003:046D:C534.0005: delayedwork_callback: logi_dj_recv_query_paired_devices error: -32
[   48.888213] logitech-djreceiver 0003:046D:C534.0005: delayedwork_callback: logi_dj_recv_query_paired_devices error: -32
[   50.248079] logitech-djreceiver 0003:046D:C534.0005: delayedwork_callback: logi_dj_recv_query_paired_devices error: -32
[   53.304080] logitech-djreceiver 0003:046D:C534.0005: delayedwork_callback: logi_dj_recv_query_paired_devices error: -32
[   55.234084] logitech-djreceiver 0003:046D:C534.0005: delayedwork_callback: logi_dj_recv_query_paired_devices error: -32
[   57.034079] logitech-djreceiver 0003:046D:C534.0005: delayedwork_callback: logi_dj_recv_query_paired_devices error: -32
[  108.296081] logitech-djreceiver 0003:046D:C534.0005: delayedwork_callback: logi_dj_recv_query_paired_devices error: -32
[  108.808082] logitech-djreceiver 0003:046D:C534.0005: delayedwork_callback: logi_dj_recv_query_paired_devices error: -32
[  109.304083] logitech-djreceiver 0003:046D:C534.0005: delayedwork_callback: logi_dj_recv_query_paired_devices error: -32
[  109.816086] logitech-djreceiver 0003:046D:C534.0005: delayedwork_callback: logi_dj_recv_query_paired_devices error: -32
[  110.328080] logitech-djreceiver 0003:046D:C534.0005: delayedwork_callback: logi_dj_recv_query_paired_devices error: -32
[  110.824085] logitech-djreceiver 0003:046D:C534.0005: delayedwork_callback: logi_dj_recv_query_paired_devices error: -32
[  111.336081] logitech-djreceiver 0003:046D:C534.0005: delayedwork_callback: logi_dj_recv_query_paired_devices error: -32
[  111.846830] logitech-djreceiver 0003:046D:C534.0005: delayedwork_callback: logi_dj_recv_query_paired_devices error: -32
[  115.304082] logitech-djreceiver 0003:046D:C534.0005: delayedwork_callback: logi_dj_recv_query_paired_devices error: -32
[  115.816080] logitech-djreceiver 0003:046D:C534.0005: delayedwork_callback: logi_dj_recv_query_paired_devices error: -32
[  116.328080] logitech-djreceiver 0003:046D:C534.0005: delayedwork_callback: logi_dj_recv_query_paired_devices error: -32
[  116.824084] logitech-djreceiver 0003:046D:C534.0005: delayedwork_callback: logi_dj_recv_query_paired_devices error: -32
[  117.538081] logitech-djreceiver 0003:046D:C534.0005: delayedwork_callback: logi_dj_recv_query_paired_devices error: -32
[  119.714084] logitech-djreceiver 0003:046D:C534.0005: delayedwork_callback: logi_dj_recv_query_paired_devices error: -32
[  120.216080] logitech-djreceiver 0003:046D:C534.0005: delayedwork_callback: logi_dj_recv_query_paired_devices error: -32
[  120.728078] logitech-djreceiver 0003:046D:C534.0005: delayedwork_callback: logi_dj_recv_query_paired_devices error: -32
[  121.234084] logitech-djreceiver 0003:046D:C534.0005: delayedwork_callback: logi_dj_recv_query_paired_devices error: -32
[  121.992117] logitech-djreceiver 0003:046D:C534.0005: delayedwork_callback: logi_dj_recv_query_paired_devices error: -32
[  122.488083] logitech-djreceiver 0003:046D:C534.0005: delayedwork_callback: logi_dj_recv_query_paired_devices error: -32
[  122.984082] logitech-djreceiver 0003:046D:C534.0005: delayedwork_callback: logi_dj_recv_query_paired_devices error: -32
[  123.496082] logitech-djreceiver 0003:046D:C534.0005: delayedwork_callback: logi_dj_recv_query_paired_devices error: -32
[  124.008082] logitech-djreceiver 0003:046D:C534.0005: delayedwork_callback: logi_dj_recv_query_paired_devices error: -32
[  124.538080] logitech-djreceiver 0003:046D:C534.0005: delayedwork_callback: logi_dj_recv_query_paired_devices error: -32
[  125.050078] logitech-djreceiver 0003:046D:C534.0005: delayedwork_callback: logi_dj_recv_query_paired_devices error: -32
pi@RPi3BP1:~ $ 

USB attached HDD is functional
USB sound dongle is functional

result of lsusb:

Code: Select all

pi@RPi3BP1:~ $ lsusb
Bus 001 Device 010: ID 046d:c534 Logitech, Inc. Unifying Receiver
Bus 001 Device 009: ID 1a86:8074 QinHeng Electronics 
Bus 001 Device 008: ID 174c:55aa ASMedia Technology Inc. Name: ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge, ASM1153E SATA 6Gb/s bridge
Bus 001 Device 007: ID 0d8c:0014 C-Media Electronics, Inc. Audio Adapter (Unitek Y-247A)
Bus 001 Device 006: ID 0424:7800 Standard Microsystems Corp. 
Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 002: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

waiting for fix.....or.... how can I revert back to previous kernel?

did an update on this RPi4B-4G, but did not preform the full-upgrade so its still "safe"
"Don't come to me with 'issues' for I don't know how to deal with those
Come to me with 'problems' and I'll help you find solutions"

Some people be like:
"Help me! Am drowning! But dont you dare touch me nor come near me!"

LTolledo
Posts: 3500
Joined: Sat Mar 17, 2018 7:29 am
Location: Anime Heartland

Re: STICKY: Buster bug report thread

Tue Jul 21, 2020 8:55 am

a bit of an update on the problem above...

the RPi3B+ desktop setup is connected to the wireless keyboard and mouse via KVM (Bus 001 Device 009: ID 1a86:8074 QinHeng Electronics )
in this setup, the keyboard and mouse is unresponsive.

however if the wireless dongle (of the keyboard and mouse) is connected directly to RPi3B+, the keyboard and mouse is responsive.

so with the upgrade to kernel 5.4, it has killed the functionality of the KVM where the keyboard and wireless dongle is connected
"Don't come to me with 'issues' for I don't know how to deal with those
Come to me with 'problems' and I'll help you find solutions"

Some people be like:
"Help me! Am drowning! But dont you dare touch me nor come near me!"

tombsar
Posts: 46
Joined: Wed May 13, 2020 12:40 am

Re: STICKY: Buster bug report thread

Sun Jul 26, 2020 1:41 am

I updated my Raspberry Pi 4B today with apt full-upgrade, and something (most likely the new kernel) has broken fullscreen. Some modes seem to work, but others give a garbled mess of pixels, as though it's reading the framebuffer with the wrong orientation and/or stride. Enabling/disabling vsync, for example, can make the difference between normal and garbled output.

uname -a reports "Linux arthur-rpi4 5.4.51-v7l+ #1327 SMP Thu Jul 23 11:04:39 BST 2020 armv7l GNU/Linux". I'm using the vc4-fkms-v3d driver.

Is there a way for me to downgrade to whatever kernel version we had last week (4.18 or something) to verify that the new kernel is the problem?

ejolson
Posts: 5431
Joined: Tue Mar 18, 2014 11:47 am

Re: STICKY: Buster bug report thread

Sun Jul 26, 2020 3:23 am

tombsar wrote:
Sun Jul 26, 2020 1:41 am
Is there a way for me to downgrade to whatever kernel version we had last week (4.18 or something) to verify that the new kernel is the problem?
Is suggest writing a new SD card with the version of Raspberry Pi OS that you started with which still available for download. Don't do any upgrades, but check whether the original image works the way you remember. Keep both cards so whenever you have a question about how it used to work versus how it does not, checking is just swapping cards.

beta-tester
Posts: 1384
Joined: Fri Jan 04, 2013 1:57 pm
Location: de_DE

Re: STICKY: Buster bug report thread

Sun Jul 26, 2020 6:30 am

tombsar wrote:
Sun Jul 26, 2020 1:41 am
Is there a way for me to downgrade to whatever kernel version we had last week (4.18 or something) to verify that the new kernel is the problem?
to up- or downgrade to a specific kernel, use ifs commit hash value:

Code: Select all

sudo rpi-update  e1050e94821a70b2e4c72b318d6c6c968552e9a2  # hash of commit  "kernel: Bump to 4.19.118"
sudo reboot
see here for commits and its hash values
https://github.com/Hexxeh/rpi-firmware/commits/master

a 4.18 kernel i could not find there...

be warned, you may get more problems than solving them with a kernel that does not fit to the rest of the environment.
from 5.4 back to 4.19 is a huge step back.
{ I only give negative feedback }
RPi B (256MB), B (512MB), B+, ZeroW; 2B; 3B, 3B+; 4B (4GB)

Return to “Raspberry Pi OS”