Andrew Daugherity wrote:
I completely missed that you're running amd64 (I saw Intel Xeon, and
thought i386). You might try an i386 kernel (maybe the bsd.rd
installer, as you don't want to mix libs between i386 and amd64) to
see if the CD-ROM works there. If it works under i386, then it looks
like a bug somewhere in the amd64 kernel, and might be worth filing a
bug over (or perhaps adding comments to PR4570).
I wasn't using the i386 kernel as it hangs when probing PCI devices. I
managed to get past this by disabling pcibios, but it has the same
problem as the amd64 kernel when it comes to reading the CDROM, so
nothing gained other than showing that the problem is not amd64 specific.
More data is good. If you can swap the drive, that would be a good
test. Also, testing other BSDs can't hurt -- NetBSD, OpenBSD, and
FreeBSD share some code, Net and Open more so than Free; although
they've diverged quite a bit, sometimes drivers (and bugfixes) are
ported between them. Note that saying "but it works in NetBSD, fix
it!" isn't likely to get you much help here, but "it's also broken in
NetBSD" might help track down the bug. I'm not an OpenBSD developer,
so if someone who is one chimes in, take their word over mine. :-)
I have two machines, both with the same problem, so it's not the drive.
I've tried using NetBSD, and the amd64 2.1 kernel works fine. How can I
bring this to the attention of a developer? I'm guessing that with the
release tomorrow developers are a little busy, but once 3.8 is out what
should I do to get this fixed? I have some experience with c, but not
enough to fix the problem myself. I would be able to apply patchs etc to
help deduce the problem though.
Thanks for your help,
Stephen
