DragonFly BSD
DragonFly bugs List (threaded) for 2004-08
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

Re: mysqld startup problem

From: Matthew Dillon <dillon@xxxxxxxxxxxxxxxxxxxx>
Date: Fri, 6 Aug 2004 20:40:00 -0700 (PDT)

    Yes, it definitely is.  These vesa modes are probably making a video
    bios call for each character and/or line that is output.

    I think I am going to have to back-out the timer_restore code in the vesa
    bios path for now, it's creating more problems then it is solving.  I'll
    have to figure out a better way to detect when the BIOS messes with the

					Matthew Dillon 

:I finally tracked down the problem with mysqld not starting at boot
:time. It looks like switching the display mode on syscon causes the
:trouble. The following line's from my /etc/rc.conf:
:allscreens_flags="-g 100x37 -c destructive -f 8x16 iso15-thin-8x16
:VESA_800x600 green black"
:When I delete this line from rc.conf and reboot, everything starts up
:normally. Once I enable mode switching again, mysqld does not start at
:all. Additionally, "ntpdate", which also gets executed at boot time,
:fails, and does not set the time correctly.
:Again, after the system's up, I can start all this stuff manually
:without problems.
:I also experience strange timer behaviour in higher display modes,
:e.g. executing "ls -al" in "/" causes the system time to jump at least
:80 minutes or so ahead of real time.
:With the MySQL subsystem running, a video made change via vidcontrol
:causes mysqld to crash and again leads to funny time outputs.
:I don't know how to fix this (except disabling the corresponding line
:in rc.conf), but I guess it's somehow related to the VESA.mo problems
:that were reported here.
:cd /pub
:more beer

[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]