Ok, I think we are homing in on it but there is too much confusion
between stable and current... use ONLY CURRENT kernels. It doesn't
matter if it's a debug kernel or not, but it should be a CURRENT
kernel, not a STABLE kernel.
-Matt
Matthew Dillon
<dillon@backplane.com>
: I had just about enough time before running out the door to work this
:morning to try a couple of things. Here is what I've done so far.
:
:I had the dfly-stable-20041009.iso.gz file on hand so I went ahead and
:installed it instead of the dfly-20041107-stable.iso.gz. Unable to repeat
:the keyboard loss (non-debug kernel).
:
:I had downloaded the two following kernels:
:
: 2CSNAP-20041001-2330-GCC2-GENERIC-kernel.debug.gz
: 2CSNAP-20041020-2330-GCC2-GENERIC-kernel.debug.gz
:
:When I boot from either of these, the problem is easily reproduced.
:
:20041001:
:DragonFly workstation.zip 1.1-CURRENT DragonFly 1.1-CURRENT #0: Sat Oct 2
:00:19:37 GMT 2004
:root@chlamydia.fs.ei.tum.de:/usr/obj/usr/src/sys/GENERIC i386
:
:20041009 (non-debug):
:DragonFly workstation.zip 1.1-CURRENT DragonFly 1.1-CURRENT #0: Sat Oct 9
:01:47:25 PDT 2004
:dillon@office1.backplane.com:/usr/obj/usr/src/sys/GENERIC i386
:
:20041020:
:DragonFly workstation.zip 1.1-CURRENT DragonFly 1.1-CURRENT #0: Thu Oct 21
:00:17:13 GMT 2004
:root@chlamydia.fs.ei.tum.de:/usr/obj/usr/src/sys/GENERIC i386
:
:The two 2CSNAP kernels are debug kernels and the 20041009 is not. Maybe the
:problem manifests with a debug kernel only. At this stage I can either put
:the 20041107 iso build back on, cvsup and try building a non-debug kernel
:or look for a repository of non-debug kernels. This morning my time was
:limited so I only looked at:
:
:ftp://ftp.theshell.com/pub/DragonFly/snapshots/i386/kernels/
:
:If there is a non-debug kernel repository where I could get a non-debug
:version of the 20041107 kernel it would be quicker than downloading all the
:source from cvs, as at present I currently have no source code and I'd have
:to do so by controlling the box from remote (telnet/ssh).
:
:If I am unable to reproduce with a newer non-debug it might focus attention
:on what is different in the debug kernels that is causing the problem.
:
:-Mike
: