1.6.0 just crashed

Matthew Dillon dillon at apollo.backplane.com
Mon Dec 18 21:34:13 PST 2006


    No, it probably isn't anything you did.  1.6.0 had some bugs.  You
    can try upgrading it to the latest on the release branch or you can
    just try compiling and installing from HEAD, to see if that clears things
    up.

    Since you were running X, the panic would not have been visible.  One
    way to figure out why it is panicing when running X is to attach a 
    null modem cable from the serial port to another computer and 'boot -h'.
    Then if a panic occurs the console will be on the serial port. 

    Another way would be to try to have it automatically dump on panic by
    compiling up a kernel with options DDB_UNATTENDED (and setting up a
    dump device), then seeing if the machine dumps when it panics instead
    of simply resetting.

    DragonFly should be able to access FreeBSD-style partitions but it
    won't be happy about it.

    The DFLTPHYS messages are just warnings and have nothing to do with
    anything (just means the SCSI driver hasn't supplied a maximum
    transfer size to the kernel, which is ok as the kernel's default will
    cover it).

						-Matt





More information about the Users mailing list