[Bug 18033] New: Check time-out for kernel boot initialisation

http://bugs.winehq.org/show_bug.cgi?id=18033

Summary: Check time-out for kernel boot initialisation
           Product: Wine
           Version: 1.1.19
          Platform: PC-x86-64
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: P2
         Component: programs
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]

I am surprised by the following result.

elfring@Sonne:~> time wine notepad
err:process:__wine_kernel_init boot event wait timed out

real    0m30.886s
user    0m0.242s
sys     0m0.087s

I find the log message and the timing strange for my system specification.

CPU: 15.43.1 "AMD Athlon(tm) 64 X2 Dual Core Processor 4200+"
Memory: 2 GB

Sonne 2.6.28.7-default #1 SMP PREEMPT Sun Mar 1 18:21:35 CET 2009 x86_64 x86_64
x86_64 GNU/Linux

Can this source code section be improved with different synchronisation
approaches?
http://source.winehq.org/git/wine.git/?a=blob;f=dlls/kernel32/process.c;h=62...

I mentioned this issue also on an other occasion.
http://bugs.winehq.org/show_bug.cgi?id=17728#c2

[Bug 18033] Check time-out for kernel boot initialisation

http://bugs.winehq.org/show_bug.cgi?id=18033

--- Comment #1 from Markus Elfring   2009-04-13 14:54:31 ---
Is my description related to the issue "Wineboot has a race condition"?
http://bugs.winehq.org/show_bug.cgi?id=15492#c10

[Bug 18033] Check time-out for kernel boot initialisation

http://bugs.winehq.org/show_bug.cgi?id=18033

Austin English  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

[Bug 18033] Check time-out for kernel boot initialisation

http://bugs.winehq.org/show_bug.cgi?id=18033

Dmitry Timoshkov  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
          Component|programs                    |-unknown
         Resolution|                            |INVALID

--- Comment #2 from Dmitry Timoshkov   2009-04-13 21:28:42 ---
If all that bothers you is a message on the console this bug is invalid.

[Bug 18033] Check time-out for kernel boot initialisation

http://bugs.winehq.org/show_bug.cgi?id=18033

Dmitry Timoshkov  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED

--- Comment #3 from Dmitry Timoshkov   2009-04-13 21:29:12 ---
Closing.

[Bug 18033] Check time-out for kernel boot initialisation

http://bugs.winehq.org/show_bug.cgi?id=18033

Austin English  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|CLOSED                      |UNCONFIRMED
         Resolution|INVALID                     |

--- Comment #4 from Austin English   2009-04-13 21:31:43 ---
If that error occurs, then wine times out as well. It can also cause an
improperly setup WINEPREFIX.

Markus, do you have any network printers?

[Bug 18033] Check time-out for kernel boot initialisation

http://bugs.winehq.org/show_bug.cgi?id=18033

--- Comment #5 from Markus Elfring   2009-04-14 07:24:24 ---
No - my printer is connected with an USB cable.

Will it be supported that the Notepad application window should appear in less
than 30 seconds?

[Bug 18033] Check time-out for kernel boot initialisation

http://bugs.winehq.org/show_bug.cgi?id=18033

--- Comment #6 from Austin English   2009-04-14 10:50:14 ---
(In reply to comment #5)
> Will it be supported that the Notepad application window should appear in less
> than 30 seconds?

It should only take a couple seconds on a modern CPU. The problem is we don't
know where the delay is.

You might try running with oprofile to see where it's taking so long.

[Bug 18033] Check time-out for kernel boot initialisation

http://bugs.winehq.org/show_bug.cgi?id=18033

--- Comment #7 from Markus Elfring   2009-04-15 01:44:51 ---
Are there better ways to find the reason why the condition for the function
call "WaitForSingleObject(boot_event, 30000)" does not fit on my computer as
expected?
Which other software component should send a corresponding notification
earlier?

[Bug 18033] Check time-out for kernel boot initialisation

http://bugs.winehq.org/show_bug.cgi?id=18033

--- Comment #8 from Vitaliy Margolen   2009-04-15 09:04:11 ---
Markus, have you recreated WINEPREFIX (removed/renamed ~/.wine dir)?

[Bug 18033] Check time-out for kernel boot initialisation

http://bugs.winehq.org/show_bug.cgi?id=18033

--- Comment #9 from Markus Elfring   2009-04-16 14:30:36 ---
I have tried it once again after the updated version 1.1.19-2.1 was installed.

Now I get the following result.
elfring@Sonne:~> WINEPREFIX=~/Projekte/Wine/Test/18033 time wine notepad
0.24user 0.09system 0:02.04elapsed 16%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+14540minor)pagefaults 0swaps

The message "err:process:__wine_kernel_init boot event wait timed out" appears
also on the first activation for a new test configuration.

I guess that my default Wine installation directory contains more data that
results in longer lasting startup than I would expect.

Can an execution trace be limited to the boot process and related function
calls?
http://source.winehq.org/git/wine.git/?a=blob;f=programs/wineboot/wineboot.c...

[Bug 18033] Check time-out for kernel boot initialisation

http://bugs.winehq.org/show_bug.cgi?id=18033

blaise  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #10 from blaise   2009-06-08 23:53:42 ---
I was getting this gnarly problem lately with the
"err:process:__wine_kernel_init boot event wait timed out" showing up and
causing all sorts of havoc. Like   Vitaliy says all you have to do is rename
the ~/.wine directory to wine.old or something. ~/.wine will be recreated and
the problem goes away.

[Bug 18033] Check time-out for kernel boot initialisation

http://bugs.winehq.org/show_bug.cgi?id=18033

--- Comment #11 from Austin English   2010-03-11 17:21:17 ---
This is your friendly reminder that there has been no bug activity for 8
months. Is this still an issue in current (1.1.40 or newer) wine?

[Bug 18033] Check time-out for kernel boot initialisation

http://bugs.winehq.org/show_bug.cgi?id=18033

--- Comment #12 from Markus Elfring   2010-03-13 09:36:49 ---
(In reply to comment #11)

Yes. - I have got the following messages after the first start try.

elfring@Sonne:~> winecfg
Warning: could not find DOS drive for current working directory
'/home/elfring', starting in the Windows directory.
err:alsa:ALSA_CheckSetVolume Could not find 'PCM Playback Volume' element
fixme:mixer:ALSA_MixerInit No master control found on MPU-401 UART, disabling
mixer
fixme:mixer:ALSA_MixerInit No master control found on SAA7134, disabling mixer
err:mshtml:check_version Could not open VERSION file
err:mshtml:install_from_unix_file Could not get dos file name of
"/usr/bin/../share/wine/gecko/wine_gecko-1.0.0-x86.cab"
err:process:__wine_kernel_init boot event wait timed out
err:alsa:ALSA_CheckSetVolume Could not find 'PCM Playback Volume' element
fixme:mixer:ALSA_MixerInit No master control found on MPU-401 UART, disabling
mixer
fixme:mixer:ALSA_MixerInit No master control found on SAA7134, disabling mixer
err:mshtml:check_version Could not open VERSION file
Could not load wine-gecko. HTML rendering will be disabled.
wine: configuration in '/home/elfring/.wine' has been updated.

[Bug 18033] Check time-out for kernel boot initialisation

http://bugs.winehq.org/show_bug.cgi?id=18033

--- Comment #13 from Markus Elfring   2010-03-20 14:28:29 ---
(In reply to comment #11)

Yes. - I have got the following messages after the first start try with the
version 1.1.41-1.1.

elfring@Sonne:~> WINEPREFIX=~/Projekte/Wine/Test/18033 time wine notepad
err:alsa:ALSA_CheckSetVolume Could not find 'PCM Playback Volume' element
fixme:mixer:ALSA_MixerInit No master control found on MPU-401 UART, disabling
mixer
fixme:mixer:ALSA_MixerInit No master control found on SAA7134, disabling mixer
fixme:system:SetProcessDPIAware stub!
fixme:dwmapi:DwmIsCompositionEnabled 0x33cf64
fixme:iphlpapi:NotifyAddrChange (Handle 0xa6de8d8, overlapped 0xa6de8e0): stub
err:process:__wine_kernel_init boot event wait timed out
wine: configuration in '/home/elfring/Projekte/Wine/Test/18033' has been
updated.
0.21user 0.10system 0:36.56elapsed 0%CPU (0avgtext+0avgdata 0maxresident)k
12348inputs+0outputs (8major+15300minor)pagefaults 0swaps

[Bug 18033] Check time-out for kernel boot initialisation

http://bugs.winehq.org/show_bug.cgi?id=18033

--- Comment #14 from Austin English  2011-11-15 23:33:04 CST ---
Likely still present. oprofile/strace info would probably be useful.

[Bug 18033] Check time-out for kernel boot initialisation

http://bugs.winehq.org/show_bug.cgi?id=18033

--- Comment #15 from Austin English  2013-12-05 21:50:50 CST ---
This is your friendly reminder that there has been no bug activity for 2 years.
Is this still an issue in current (1.7.7 or newer) wine? If so, please attach
the terminal output in 1.7.7 (see http://wiki.winehq.org/FAQ#get_log).

[Bug 18033] Check time-out for kernel boot initialisation

http://bugs.winehq.org/show_bug.cgi?id=18033

--- Comment #16 from Markus Elfring  2013-12-06 02:00:53 CST ---
(In reply to comment #15)

I can not reproduce the reported time out with wine 1.7.7 on my openSUSE
13.1/Tumbleweed system.

CPU: 16.5.3 "AMD Phenom(tm) II X4 850 Processor"
Memory: 8 GB

[Bug 18033] Check time-out for kernel boot initialisation

https://bugs.winehq.org/show_bug.cgi?id=18033

Austin English  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |ABANDONED

--- Comment #17 from Austin English  ---
(In reply to Markus Elfring from comment #16)
> (In reply to comment #15)
>
> I can not reproduce the reported time out with wine 1.7.7 on my openSUSE
> 13.1/Tumbleweed system.
>
> CPU: 16.5.3 "AMD Phenom(tm) II X4 850 Processor"
> Memory: 8 GB

Abandoned, thanks.

[Bug 18033] Check time-out for kernel boot initialisation

https://bugs.winehq.org/show_bug.cgi?id=18033

Austin English  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED

--- Comment #18 from Austin English  ---
Closing.