Unimplemented function KERNEL32.dll.FindFirstVolumeW

devzero at web.de devzero at web.de
Tue Nov 20 02:13:43 CST 2007


mhhh - since it cost me more then one hour to find out why my machine reboots and triggering a reboot by just _reading_ a file on my system, device node or not is at least very weird behaviour from a user`s perspective.

>waiting for an user-space daemon to start handling of /dev/watchdog file  (opening it and manipulating it from time to time to show that it's still alive.
>When you cat the file, kernel recognizes it as that such an app is taking over control of the watchdog and starts it. 
it`s looks a little bit too simple for me. triggering a reboot just by some simple open() and read() and close() ?
let`s wait what the maintainer has to tell.

regards
roland

> Hi!
>   I think it's not a bug, it's a normal behaviour.
>   The kernel watchdog is normally not active when the machine is booted,
> waiting for an user-space daemon to start handling of /dev/watchdog file
> (opening it and manipulating it from time to time to show that it's still
> alive). When you cat the file, kernel recognizes it as that such an app
> is taking over control of the watchdog and starts it. However, because
> cat closes the file immediately, it is not handled anymore and kernel
> recognizes it as a userspace problem, thus rebooting the machine after
> the timeout expires.
>   With regards, Pavel Troller
> 


> -----Ursprüngliche Nachricht-----
> Von: Pavel Troller <patrol at sinus.cz>
> Gesendet: 20.11.07 08:49:53
> An: devzero at web.de
> CC: Hans Leidekker <hans at it.vu.nl>, wine-devel at winehq.org
> Betreff: Re: Unimplemented function KERNEL32.dll.FindFirstVolumeW


> 
> > i`ve tracked this down to a watchdog issue.
> > 
> > whenever i do "cat /dev/watchdog" - my system reboots after ~1 minute.
> > 
> > i`ve contacted the maintainer of the watchdog subsystem.
> > 
> > looks like a bug to me.
> > 
> > thanks
> > roland
> > 
> Hi!
>   I think it's not a bug, it's a normal behaviour.
>   The kernel watchdog is normally not active when the machine is booted,
> waiting for an user-space daemon to start handling of /dev/watchdog file
> (opening it and manipulating it from time to time to show that it's still
> alive). When you cat the file, kernel recognizes it as that such an app
> is taking over control of the watchdog and starts it. However, because
> cat closes the file immediately, it is not handled anymore and kernel
> recognizes it as a userspace problem, thus rebooting the machine after
> the timeout expires.
>   With regards, Pavel Troller
> 


______________________________________________________________________________
Jetzt neu! Im riesigen WEB.DE Club SmartDrive Dateien freigeben und mit 
Freunden teilen! http://www.freemail.web.de/club/smartdrive_ttc.htm/?mc=021134




More information about the wine-devel mailing list