From nobody Mon Jan 10 12:38:48 2022 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 81DEE1944973 for ; Mon, 10 Jan 2022 12:38:59 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4JXYKZ43Z5z4gV4 for ; Mon, 10 Jan 2022 12:38:58 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 4E59A5C00F7 for ; Mon, 10 Jan 2022 07:38:51 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Mon, 10 Jan 2022 07:38:51 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h= date:from:to:subject:message-id:mime-version:content-type; s= fm1; bh=imG3cdVKaeKMWtuRHJTnixkqsA4GWRvPueGPmfs3hfY=; b=lK5wimvu era3K9NqLI2JLyxBpFsx/RMrEUggmPbo2G/f4zazMEwEOrn/o+6APFH11o1HaLGk KG4bqSlJOJSebQDAGCaAUhuYcAr13IemuKUtcVFtot1sLaLpRtiju1k0oC3qIchf 5uz6rrWJum+ffN9/6ynyarxpMWK9lW40HUSW3E1qdNAUi9cFGDVsrDaquOkCFKUo hiDZMpX4KXZK1J12yFaj8uP1IlAcrBufyagtIZTnrpvo4y5YvcIo13XlPxvGZlCA nd95daqPRpf5z7U3UdWBDvl7owwYO6t/59sEdyD9wxqj1bbHzrggS368U0qtpIIp wr4e+hMhE1JnDw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:message-id :mime-version:subject:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=imG3cdVKaeKMWtuRHJTnixkqsA4GW RvPueGPmfs3hfY=; b=cAHJHfdbsN7i4geoub81rhZwWNVDQoptd8CkdhsVZYL1z DnXQ8msD4hByIx2gUjzlQlBrbkRtRY8yRUoXxdkd/0D6EwjsY+d9fY1Otj2EB6gJ I5mne9cXeBGz2uo1WzXdcAmZY+TRhQAftuZhJ2mKWv1vSoKdHMNWqB0z2g/bmxfK +Ic3Uk15cSLGUckz2f3Y2QxeX2jWHLyf+l9+RT04hBP/jxIVN9KmeHauriUaf9yw dFGVY0NqTKcPP53buzyvYGrCnQTOXa0Epo9DJboVXoErUiOAbGLpsncgu7bj3xbJ jdWr20XwB3CeuJueJqMKOWXWutffjQBaYdPIsDbsg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvuddrudehuddgudekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkgggtugesghdtreertd dtvdenucfhrhhomhepthgvtghhqdhlihhsthhsuceothgvtghhqdhlihhsthhsseiihiig shhtrdhnvghtqeenucggtffrrghtthgvrhhnpeekfeejhfekheegiedvleeltdehgefghf dtkedtvdfgheevhefgvefgueetgeeggeenucffohhmrghinhepfhhrvggvsghsugdrohhr ghdpsghsugdqhhgrrhgufigrrhgvrdhinhhfohenucevlhhushhtvghrufhiiigvpedtne curfgrrhgrmhepmhgrihhlfhhrohhmpehtvggthhdqlhhishhtshesiiihgihsthdrnhgv th X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Mon, 10 Jan 2022 07:38:50 -0500 (EST) Date: Mon, 10 Jan 2022 12:38:48 +0000 From: tech-lists To: freebsd-hackers@freebsd.org Subject: sane-find-scanner on the USB bus causes a crash Message-ID: Mail-Followup-To: freebsd-hackers@freebsd.org List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="PV82uTgAbbBYvHzI" Content-Disposition: inline X-Rspamd-Queue-Id: 4JXYKZ43Z5z4gV4 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=zyxst.net header.s=fm1 header.b=lK5wimvu; dkim=pass header.d=messagingengine.com header.s=fm1 header.b=cAHJHfdb; dmarc=none; spf=pass (mx1.freebsd.org: domain of tech-lists@zyxst.net designates 66.111.4.28 as permitted sender) smtp.mailfrom=tech-lists@zyxst.net X-Spamd-Result: default: False [-6.70 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[zyxst.net:s=fm1,messagingengine.com:s=fm1]; NEURAL_HAM_LONG(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; RWL_MAILSPIKE_GOOD(0.00)[66.111.4.28:from]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:66.111.4.28]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; DWL_DNSWL_LOW(-1.00)[messagingengine.com:dkim]; RCVD_COUNT_THREE(0.00)[4]; MID_RHS_MATCH_FROMTLD(0.00)[]; DKIM_TRACE(0.00)[zyxst.net:+,messagingengine.com:+]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_NA(0.00)[zyxst.net]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; SIGNED_PGP(-2.00)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:19151, ipnet:66.111.4.0/24, country:US]; RCVD_IN_DNSWL_LOW(-0.10)[66.111.4.28:from] X-ThisMailContainsUnwantedMimeParts: N --PV82uTgAbbBYvHzI Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, There is a *very old* PR open here :=20 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D207431 about this issue. It was from 10.2 then someone else confirmed it was happe= ning on stable/11 and i've found it still happening with stable/13. Posting to= =20 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 sta= ble/13. The hw info is at https://bsd-hardware.info/?probe=3D0f0ae001cd The context is stable/13-n248872-2c7441c86ef: Thu Jan 6 02:34:00 UTC 2022= =20 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: 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=20 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, --=20 J. --PV82uTgAbbBYvHzI Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEE8n3tWhxW11Ccvv9/s8o7QhFzNAUFAmHcKMwACgkQs8o7QhFz NAX07Q//VUdR01kmScCjU2A4evSNRcLyORjqFzPwtKcg49bU+kDCdhzgNhdDvl7v kz7T0p2WL2/5G0iC8059BzU5mf/tVWGrFGVfDyP78mhKAMM4y9+kaHxwCtUTnFs3 37+jSADPptSVK40QHbDJ+jHqmpatzSutHar23reP5VgHpSaODOtwwGUtYMf5VfE4 bpZQ5lH7GtEim1odOKVHZTDIIJvxe5EfOcVG/MZmLSylDwWv1/d2nk7jx6Oppuf1 T9MEnaEs2g/RHTf1do3lWHoTB4MAXd9BPrrO3Si0fYwFcBlCP+hhB7M/xlbWCeTk S0aixFD6GFvuA0Z8rvjpuB09ZFFsEAt9Zajga6N2qgtZTakxG/JeA3KTZhkiiaeL e6nixvWQewNISicsiUv4WIqYi4p4oruf930E3TmFp3U04HOCr5IgetTWd60kqqPv Tn201oaEoyueb5txcWsyMMajmQ1oP11HavfhdWiQYGi+XJlcJKbD1v41LHg0AIca UOJLm35x3sFSVEBgeNeXtwqJpk5UFUSLiaReQvx2bjmQL3mky+gaV02yT+kGknBx INW1r3soh/BSenwvQC07GMVCMkAaURSAX6V1GZ0PtdxBnrAyKrnwntGoAyZ8qCU4 GoJhNAcEnGKq/nRRQ6QRhBzoDvWngANRFquwDKfF3BqGIWBOR6k= =Zavh -----END PGP SIGNATURE----- --PV82uTgAbbBYvHzI--