I generated some logs for debugging .
Among it , there are some like this :
01113671 8941.92285156 [1140] ==> mfn_ProcessHardwareFailure
01113672 8941.92382813 [1140] call found
01113673 8941.92382813 [1140] <== mfn_ProcessHardwareFailure
01113674 8941.95703125 [1140] ==> lineClose()
01113675 8941.95703125 [1140] lineClose(): looking for tspdev
01113676 8941.95703125 [1140] lineClose(): found tspdev
01113712 8941.96093750 [1140] <== lineClose()
I suppose it is generated by system component.
So someone can help me on these questions :
1 ) What does it mean ?
2 ) what is implied when these logs are generated ?
You lost me here - where do these logs come from?
mm
xiedong_sl@126.com wrote:
I generated some logs for debugging .
Among it , there are some like this :
01113671 8941.92285156 [1140] ==> mfn_ProcessHardwareFailure
01113672 8941.92382813 [1140] call found
01113673 8941.92382813 [1140] <== mfn_ProcessHardwareFailure
01113674 8941.95703125 [1140] ==> lineClose()
01113675 8941.95703125 [1140] lineClose(): looking for tspdev
01113676 8941.95703125 [1140] lineClose(): found tspdev
01113712 8941.96093750 [1140] <== lineClose()
I suppose it is generated by system component.
So someone can help me on these questions :
1 ) What does it mean ?
2 ) what is implied when these logs are generated ?
TSP: telephony service provider
( hence - something about lines, calls etc. )
ProcessHardwareFailure: bad things happened
–pa
to MM :
From Windbg .
To Pavel A :
Can you help to specify this bad thing ? .
Also , Can you please take an example of what case can trigger this bad thing ?
xiedong_sl@126.com wrote:
…
To Pavel A :
Can you help to specify this bad thing ? .
Also , Can you please take an example of what case can trigger this bad thing ?
Some hardware failure occured - which may be actually
caused by hardware, or be some driver problem.
Sorry, can not tell more… not feeling psychic today.
–pa
xiedong_sl@126.com wrote:
to MM :
From Windbg .
No, it was from DbgView. Right? The ordinal and time columns give that
away.
To Pavel A :
Can you help to specify this bad thing ? .
Also , Can you please take an example of what case can trigger this bad thing ?
Not really. These message are coming from some driver – probably a
telephony driver of some kind, meaning a modem or smart phone.
Why are you worried about these? Are you seeing a failure of some kind?
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
> No, it was from DbgView. Right? The ordinal and time columns give that
away.
Both in DebugView and in WinDbg you can simply filter these [annoying]
messages out.
Not really. These message are coming from some driver
… and the author [my guess] simply forgot to take out.
----- Original Message -----
From: “Tim Roberts”
To: “Windows System Software Devs Interest List”
Sent: Monday, June 22, 2009 1:30 PM
Subject: Re: [ntdev] Please help to explain log from system compoenent .
> xiedong_sl@126.com wrote:
>> to MM :
>>
>> From Windbg .
>>
>
> No, it was from DbgView. Right? The ordinal and time columns give that
> away.
>
>> To Pavel A :
>>
>> Can you help to specify this bad thing ? .
>>
>> Also , Can you please take an example of what case can trigger this
>> bad thing ?
>>
>
> Not really. These message are coming from some driver – probably a
> telephony driver of some kind, meaning a modem or smart phone.
>
> Why are you worried about these? Are you seeing a failure of some kind?
>
> –
> Tim Roberts, xxxxx@probo.com
> Providenza & Boekelheide, Inc.
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
Thanks to each of you .
Actually , I desire to get to know when these stuff
==> mfn_ProcessHardwareFailure
call found
<== mfn_ProcessHardwareFailure
appears in log , what does it mean ? Implies failure , crash somewhere or nothing , just a just a log output from one driver ?
if this is seen in Dbgview as well, then the number between brackets
“[1140]” in this case tells u which process (service or application) is
sending these. use process explorer to find which process this is.
rtshiva
On Tue, Jun 23, 2009 at 2:16 PM, <xiedong_sl> wrote:
> Thanks to each of you .
>
> Actually , I desire to get to know when these stuff
>
> ==> mfn_ProcessHardwareFailure
> call found
> <== mfn_ProcessHardwareFailure
>
> appears in log , what does it mean ? Implies failure , crash somewhere or
> nothing , just a just a log output from one driver ?
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
></xiedong_sl>
Daniel:
I haven’t any idea of what these mean, but according to Google, mfn_ProcessHardwareFailure is associated with something called the ‘Microsoft Phone Dialer.’
Google is your friend:
http://www.eggheadcafe.com/aspnet_answers/win32programmertapi/Aug2006/post27646006.asp
Good luck,
mm
to???
Thanks .
The provided link seems invalid to me .
“The page you requested is no longer available on eggheadcafe.”
To MM :
I can access this link now . I ever also accessed this link before I posted this topic. But the link is far away from my satisfaction. I hardly get some valuable information from it .
Anyway , thanks for the kind reminder .
xiedong_sl@126.com wrote:
Thanks to each of you .
Actually , I desire to get to know when these stuff
==> mfn_ProcessHardwareFailure
call found
<== mfn_ProcessHardwareFailure
appears in log , what does it mean ? Implies failure , crash somewhere
or nothing , just a just a log output from one driver ?
They are just log output from some piece of software on your system. In
general, if you want to know what they mean you’ll need to somehow find
which bit of software they came from, then find its author and ask them.
There may be some messages which someone here might recognize and be
able to tell you about, but probably not many.