From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mats Petersson Subject: Re: txftrans.c:4498 -- TXF_HARD_ERROR Date: Fri, 11 Jan 2013 13:15:45 +0000 Message-ID: <50F01081.2030609@citrix.com> References: <1357812259.7989.317.camel@zakaz.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On 10/01/13 21:37, Rushikesh Jadhav wrote: > > > On Thu, Jan 10, 2013 at 3:34 PM, Ian Campbell > wrote: > > On Tue, 2013-01-08 at 21:53 +0000, Rushikesh Jadhav wrote: > > > > > > Please help me in diagnosing below error in > /var/log/messages > > > > HVM1[16586]: txftrans.c:4498 -- TXF_HARD_ERROR (0xC01A002B) > > for RM: fffff8800d099000 > The error code, according to this random site google found: http://repo.meh.or.id/Windows/ntstatus.txt means "STATUS_LOG_STATE_INVALID", which doesn't really give us much more leads as to what it actually does/means. It almost sounds like the code in that file is doing something the rest of the system is not expecting. C01Axxxx are all "STATUS_LOG_XXXX" error messages. However, there are also a bunch of {4,8,C}019xxxx error messages which mentions transactions and similar things - it may be that at some point, these have been renumbered to be C01Axxxx range? No 2B in the ones I could find tho'. -- Mats > > This message was printed by your dom1 kernel, via the PV drivers. > > Google suggests to me that txftrans.c is a Windows Vista source file, > but I don't especially want to follow that trail to far for fear of > seeing something I shouldn't. > > I've no idea what the message might mean though. > > Ian. > > Thanks Ian, > > I have also stopped perusing the file and error. Its just bugging me > every hour :( > I'm surprised that this error and file is never reported anywhere and > I don't think my Windows DomU is any special to generate such error. > > - Rushikesh