[prev in list] [next in list] [prev in thread] [next in thread]
List: freebsd-hackers
Subject: sane-find-scanner on the USB bus causes a crash
From: tech-lists <tech-lists () zyxst ! net>
Date: 2022-01-10 12:38:48
Message-ID: Ydwo2Ppjf/mfdZ1d () ceres ! zyxst ! net
[Download RAW message or body]
Hi,
There is a *very old* PR open here :
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207431
about this issue. It was from 10.2 then someone else confirmed it was happening
on stable/11 and i've found it still happening with stable/13. Posting to
hackers@ hoping someone knowledgeable will look at this. How is it that
the usb subsystem can cause a crash to console?
I have an old desktop c.2010 vintage im trying to get working well with stable/13.
The hw info is at https://bsd-hardware.info/?probe=0f0ae001cd
The context is stable/13-n248872-2c7441c86ef: Thu Jan 6 02:34:00 UTC 2022
root@releng3.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64
8GB RAM, zfs raidz1 (3*1TB disks)
packages were installed from pkg.freebsd.org
if I run sane-find-scanner -q
this happens:
Jan 10 00:41:29 kernel: ugen4.2: <EPSON EPSON Perfection V37/V370> at usbus4
as expected, but a few seconds later, this happens:
Jan 10 00:50:33 kernel: ata2: FAILURE - odd-sized DMA transfer attempt 5 % 2
Jan 10 00:50:33 kernel: ata2: setting up DMA failed
Jan 10 00:53:36 syslogd: kernel boot file is /boot/kernel/kernel
Jan 10 00:53:36 kernel: ata3: already running!
Jan 10 00:53:36 kernel: ata2: already running!
Jan 10 00:53:36 kernel: spin lock 0xffffffff81cac3c0 (callout) held by
0xfffffe000f91f3a0 (tid 100003) too long
resulting in a lockup at next write then drops to console, press any key to reboot.
What info would I need to capture to try to resolve this?
The system is fine in every way apart from this.
thanks,
--
J.
["signature.asc" (application/pgp-signature)]
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic