Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 18 Oct 2002 16:14:44 +0100
From:      Josef Karthauser <joe@FreeBSD.org>
To:        Brian Fundakowski Feldman <green@FreeBSD.org>
Cc:        current@FreeBSD.org
Subject:   Re: kernel panic trying to utilize a da(4)/umass(4) device with ohci(4)
Message-ID:  <20021018151444.GC1328@genius.tao.org.uk>
In-Reply-To: <200210062342.g96NgIoA001063@green.bikeshed.org>
References:  <200210062342.g96NgIoA001063@green.bikeshed.org>

next in thread | previous in thread | raw e-mail | index | archive | help

--uh9ZiVrAOUUm9fzH
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Does this happen on a current with this patch applied too?

Index: usb_port.h
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
RCS file: /home/ncvs/src/sys/dev/usb/usb_port.h,v
retrieving revision 1.58
diff -u -r1.58 usb_port.h
--- usb_port.h	2 Oct 2002 07:44:20 -0000	1.58
+++ usb_port.h	18 Oct 2002 15:14:23 -0000
@@ -339,10 +339,7 @@
=20
 #define USBVERBOSE
=20
-/* We don't use the soft interrupt code in FreeBSD. */
-#if 0
 #define USB_USE_SOFTINTR
-#endif
=20
 #define Static static


Joe
=20
On Sun, Oct 06, 2002 at 07:42:18PM -0400, Brian Fundakowski Feldman wrote:
> I can't get more info because crash dumps don't work when this happens, b=
ut=20
> for what it's worth, here's a traceback which shows what happens when I=
=20
> attempt to use my da0: <SanDisk ImageMate II 1.30> Removable Direct Access
> SCSI-2 device on an OHCI-based controller.  This was working just a few d=
ays=20
> ago with a UHCI controller, so ...
>=20
> The crash is from an invalid read at 0xbff3e000, which is PTmap plus some
> offset. The trace as far as I can get it, from a kernel with USB but no
> "options"=20
> enabled, would be:
>=20
> ohci_alloc_std_chain+0xf5 (calling a DMAADDR() function, I believe)
> ohci_device_bulk_start+0x0d
> ohci_device_bulk_transfer+0x27
> usbd_transfer+0xc0
> umass_setup_transfer+0x4f
> umass_bbb_state
> usb_transfer_complete
> ohci_softintr
>=20
> Can anyone confirm if this is normal or I have an exceptional system?  I=
=20
> have two completely unrelated OHCI-based controllers in my system and=20
> neither works.
>=20
> --=20
> Brian Fundakowski Feldman                           \'[ FreeBSD ]''''''''=
''\
>   <> green@FreeBSD.org  <> bfeldman@tislabs.com      \  The Power to Serv=
e! \
>  Opinions expressed are my own.                       \,,,,,,,,,,,,,,,,,,=
,,,,\
>=20
>=20
>=20
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message

--=20
"As far as the laws of mathematics refer to reality, they are not certain;
and as far as they are certain, they do not refer to reality." - Albert
Einstein, 1921

--uh9ZiVrAOUUm9fzH
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (FreeBSD)

iEYEARECAAYFAj2wJWQACgkQXVIcjOaxUBZ1HwCgxTb3vuoS6vyoCYYZ0z7UCOty
X9sAmwchZKykUv9qskiH/u1UVxccEtbC
=RnsV
-----END PGP SIGNATURE-----

--uh9ZiVrAOUUm9fzH--

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021018151444.GC1328>