[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <562F84AE.1030500@list.ru>
Date: Tue, 27 Oct 2015 17:05:34 +0300
From: Stas Sergeev <stsp@...t.ru>
To: Andy Lutomirski <luto@...capital.net>
Cc: Andy Lutomirski <luto@...nel.org>, X86 ML <x86@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Brian Gerst <brgerst@...il.com>,
Denys Vlasenko <dvlasenk@...hat.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Borislav Petkov <bp@...en8.de>,
Stas Sergeev <stsp@...rs.sourceforge.net>
Subject: Re: [PATCH v2 0/4] x86: sigcontext fixes, again
27.10.2015 03:52, Andy Lutomirski пишет:
> On Mon, Oct 26, 2015 at 4:45 AM, Stas Sergeev <stsp@...t.ru> wrote:
>> 26.10.2015 04:25, Andy Lutomirski пишет:
>>> This is take 2 at fixing x86 64-bit signals wrt SS. After a lot of
>>> thought, this is not controlled by any flags -- I would much prefer
>>> to avoid opt-in behavior. Instead, it just tries hard to avoid
>>> triggering the cases that break DOSEMU.
>>>
>>> Stas, this now seems to pass the test you sent me. It works with
>>> stock dosemu2 (I haven't tested classic dosemu because I can't get it
>>> to work regardless).
>> I'll test it myself then.
>> But this will have to wait till a week-end I am afraid.
>> In a mean time you can test vm86() - last time I tried,
>> I got oops and hard lockup.
>
> Can you tell me exactly what kernel version (release by Linus or
> commit hash) oopses and, if it's easy, post a screenshot or log?
I archived my config and git hash.
I can't easily post an Oops: under X it doesn't even appear -
machine freezes immediately, and under non-KMS console it is
possible to get one, but difficult to screen-shot (using bare
metal, not VM). Also the Oops was seemingly unrelated.
And if you run "dosemu -s" under non-KMS console, you'll also
reproduce this one:
https://bugzilla.kernel.org/show_bug.cgi?id=97321
Download attachment "cfg.tar.gz" of type "application/x-gzip" (32362 bytes)
Powered by blists - more mailing lists