Date: Thu, 22 Feb 2007 15:33:08 -0500 From: Ken Smith <kensmith@cse.Buffalo.EDU> To: Ken Smith <kensmith@FreeBSD.org> Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/usr.sbin/sysinstall cdrom.c Message-ID: <1172176388.91228.19.camel@opus.cse.buffalo.edu> In-Reply-To: <200702222029.l1MKTrOX079236@repoman.freebsd.org> References: <200702222029.l1MKTrOX079236@repoman.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-Ez8ThlAeqyTF02f4INs8
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable
On Thu, 2007-02-22 at 20:29 +0000, Ken Smith wrote:
> kensmith 2007-02-22 20:29:53 UTC
>=20
> FreeBSD src repository
>=20
> Modified files:
> usr.sbin/sysinstall cdrom.c=20
> Log:
> If floppies are used to boot the machine, the user lets the machine
> complete the boot and enter into sysinstall, and only then inserts
> a CD into the CDROM drive and tries to select that as the install
> media the first call to mount(2) generates EIO but the second call
> to mount(2) will succeed. This was 100% reproducible on 6.2-RELEASE,
> RELENG_6, and HEAD. If the user inserts the disc into the CDROM
> while the machine is booting off the floppies the first call to mount(2=
)
> succeeds with no problems. The problem was originally reported in
> PR #56952 against 5.1-CURRENT so it's been there for a while now.
> =20
> PR: bin/56952
> MFC after: 2 weeks
> =20
> Revision Changes Path
> 1.55 +6 -1 src/usr.sbin/sysinstall/cdrom.c
This is clearly a symptom of a deeper problem but I can't reproduce =20
this behavior under any other scenario I've tried (e.g. if you boot
a machine to single-user mode the first attempt at mounting a CD
doesn't fail...). It's only in this "floppy booted sysinstall"
environment I'm able to see the problem. The test machine has an
IDE CDROM drive, I don't know if this can be reproduced on a machine
that has a SCSI CDROM drive.
It would be nice to fix the deeper problem instead of masking the symptom
but since this is such an obscure edge case and I can't seem to reproduce
the problem in any other environment I'm not sure what else to do. If
someone else can figure out what the deeper problem is I'll happily
back this out...
--=20
Ken Smith
- From there to here, from here to | kensmith@cse.buffalo.edu
there, funny things are everywhere. |
- Theodore Geisel |
--=-Ez8ThlAeqyTF02f4INs8
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (FreeBSD)
iD8DBQBF3f4E/G14VSmup/YRAp4oAJ0aXfUyJVGDdXE7vS+mPVMw2MAQ+wCfWCUo
VwqFHjUeK3na3927he01Q94=
=Q7/+
-----END PGP SIGNATURE-----
--=-Ez8ThlAeqyTF02f4INs8--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1172176388.91228.19.camel>