From: Bodo Stroesser <bstroesser@fujitsu-siemens.com>
To: user-mode-linux devel <user-mode-linux-devel@lists.sourceforge.net>
Cc: Peter <peter.spamcatcher@rimuhosting.com>
Subject: [Fwd: Re: [uml-devel] Memory corruption/errors?]
Date: Thu, 23 Dec 2004 14:24:55 +0100 [thread overview]
Message-ID: <41CAC727.9030102@fujitsu-siemens.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 39 bytes --]
I'm forwarding this to the list.
Bodo
[-- Attachment #2: Re: [uml-devel] Memory corruption/errors? --]
[-- Type: message/rfc822, Size: 3926 bytes --]
From: Peter <peter.spamcatcher@rimuhosting.com>
To: Bodo Stroesser <bstroesser@fujitsu-siemens.com>
Cc: Jeff Dike <jdike@addtoit.com>
Subject: Re: [uml-devel] Memory corruption/errors?
Date: Thu, 23 Dec 2004 23:04:02 +1300
Message-ID: <41CA9812.2060505@rimuhosting.com>
I really don't know what fxsr is. But I think I have it. My servers
are dual proc xeons. 2.6.8.1 with skas3 v7 (mostly).
# cat /proc/cpuinfo | grep fxsr
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe cid
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe cid
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe cid
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe cid
So you can only reproduce the problem when your use the sighandler? But
when you use your patch the problem is not triggered (even with the
sighandler)?
I'd be happy to try a patch. I only have production machines at the
moment, so I may not be able to restart one for a week or two until some
new ones arrive.
Regards, Peter
Bodo Stroesser wrote:
> Peter wrote:
>
>> I don't run TT mode UMLs. So, no I haven't tried that.
>>
>> I don't know about the sighandler. The program runs as it was listed.
>> It is running on a 'regular' server (Debian, and/or WBL3) with other
>> processes running. And the host servers happen to be running other
>> UMLs. I don't know if that information helps. (i.e. can a sighandler
>> in another process on the UML or on the host cause this problem?)
>>
>> I'd be happy to try out a skas patch - preferably if it just applied
>> to the guest ;) To see if it fixes things or not.
>>
>> Regards, Peter
>>
> I could try to create a patch, just for testing.
> What machine is your host? It probably has fxsr?
>
> Bodo
next reply other threads:[~2004-12-23 13:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-23 13:24 Bodo Stroesser [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-23 13:26 [Fwd: Re: [uml-devel] Memory corruption/errors?] Bodo Stroesser
2004-12-24 2:32 ` Peter
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=41CAC727.9030102@fujitsu-siemens.com \
--to=bstroesser@fujitsu-siemens.com \
--cc=peter.spamcatcher@rimuhosting.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.