Of course, the dmesg is attached.
Let me know if I can provide more info.
Am 25.03.20 um 22:50 schrieb Sudip Mukherjee:
Thanks for testing and debugging it.
Can you please send me your dmesg which shows the trace.
--
Regards
Sudip
[0.00] Booting Linux on physical CPU 0x0
[
Thanks for testing and debugging it.
Can you please send me your dmesg which shows the trace.
--
Regards
Sudip
Investigating the error by building the packages of scanbd and libsane
from source and adding some debugging output turned out that it is not
an issue of scanbd. Thus, this bug can be closed.
This kernel Oops is triggered by the canon_pp backend of libsane.
Disabling it in
Thanks for testing, I appreciate it very much!
I am interested which exact commands you were using for qemu?
I haven't used it for emulating the raspi yet and had some trouble finding
useful/working settings.
The qemu model versatiblepb ('-M versatilepb') works for emulating the initial
raspi1
I tried it on a qemu image for aarch64 and could not reproduce the probem,
and there was no error in dmesg.
root@debian-arm64:/home/sudip# lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:Debian GNU/Linux 10 (buster)
Release:10
Codename: buster
Package: scanbd
Version: 1.5.1-5
Severity: important
Dear Maintainer,
I installed the package *scanbd* on the current Raspbian buster on a
Raspberry Pi 4 (4GB).
The behaviour is identical regardless of version '1.5.1-5' or '1.5.1-4'.
The latter version works fine with a Raspberry Pi 2B and
6 matches
Mail list logo
