Date: Tue, 1 Jun 1999 09:20:04 -0700 (PDT) From: "Kenneth D. Merry" <ken@plutotech.com> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/11969: VM_fault with mmap'd CDROM data. Message-ID: <199906011620.JAA64557@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/11969; it has been noted by GNATS. From: "Kenneth D. Merry" <ken@plutotech.com> To: rivers@dignus.com (Thomas David Rivers) Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: kern/11969: VM_fault with mmap'd CDROM data. Date: Tue, 1 Jun 1999 10:17:21 -0600 (MDT) Thomas David Rivers wrote... > > 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? That's possible, but your drive should handle the 1-block read that the ISO9660 code tried to do. I believe there are other portions of the ISO9660 code and the CD driver that will try to read 1 block at a time. It could be some sort of firmware bug that happens in certain situations. It would help if we could get hold of the SCSI specs for that drive. They might shed light on what that error code means. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199906011620.JAA64557>