public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Potential BLODA reported for smartctl due to WMI calls
Date: Wed, 11 Jul 2012 09:23:00 -0000	[thread overview]
Message-ID: <20120711092310.GE6026@calimero.vinschen.de> (raw)
In-Reply-To: <4FFD12E6.8030103@t-online.de>

On Jul 11 07:45, Christian Franke wrote:
> If smartctl is run for an USB drive, a potential BLODA is reported:
> 
> # uname -sr
> CYGWIN_NT-6.1-WOW64 1.7.15(0.260/5/3)
> 
> # echo $CYGWIN
> detect_bloda
> 
> # /usr/sbin/smartctl -i /dev/sdb
> smartctl 5.42 2011-10-20 r3458 [i686-pc-cygwin-win7(64)-sp1]
> (cygwin-5.42-1)
> ...
> 
> Potential BLODA detected!  Thread function called outside of Cygwin DLL:
>   C:\Windows\system32\wbem\wbemprox.dll
> 
> Potential BLODA detected!  Thread function called outside of Cygwin DLL:
>   C:\Windows\syswow64\OLE32.dll
> 
> === START OF INFORMATION SECTION ===
> Model Family:     Seagate Barracuda ES.2
> Device Model:     ST31000340NS
> ...
> 
> 
> smartctl uses WMI queries to retrieve USB Id for physical drive.
> This is used to auto-detect ATA pass-through protocol provided by
> USB bridge.
> Could these two DLLs possibly be added to the list of well known DLLs?

Done.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2012-07-11  9:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-11  5:45 Christian Franke
2012-07-11  9:23 ` Corinna Vinschen [this message]
2012-07-16 16:23   ` Christian Franke

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120711092310.GE6026@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).