From owner-freebsd-bugs Tue Jun 1 9:20: 4 1999 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 6C77E15084 for ; Tue, 1 Jun 1999 09:20:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id JAA64548; Tue, 1 Jun 1999 09:20:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Tue, 1 Jun 1999 09:20:02 -0700 (PDT) Message-Id: <199906011620.JAA64548@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Thomas David Rivers Subject: Re: kern/11969: VM_fault with mmap'd CDROM data. Reply-To: Thomas David Rivers Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/11969; it has been noted by GNATS. From: Thomas David Rivers To: ken@plutotech.com, rivers@dignus.com Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: kern/11969: VM_fault with mmap'd CDROM data. Date: Tue, 1 Jun 1999 12:10:26 -0400 (EDT) > The problem here may be two-fold. First, your CDROM drive is barfing on > the read command above. I don't know why that's happening, especially > since there's a vendor-specific ASC and ASCQ. If you can get the SCSI > specs for that drive, you may be able to figure out what's going on. > True - But - it's something specific to the read - somehow... because, cat of that file works correctly, gets the right data and doesn't cause the SCSI drive/driver to "barf". So - what's different when the read is a result of an mmap()? The size of the read maybe? - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message