On Tue, Dec 26, 2017 at 07:00:43PM -0800, h...@zytor.com wrote:
> On December 26, 2017 6:54:55 PM PST, Linus Torvalds
> wrote:
> >On Tue, Dec 26, 2017 at 6:25 PM, wrote:
> >>
> >> This is why I personally prefer to see these kinds of terminal
On Tue, Dec 26, 2017 at 07:00:43PM -0800, h...@zytor.com wrote:
> On December 26, 2017 6:54:55 PM PST, Linus Torvalds
> wrote:
> >On Tue, Dec 26, 2017 at 6:25 PM, wrote:
> >>
> >> This is why I personally prefer to see these kinds of terminal stubs
> >written in assembly explicitly: the C
Sounds like it's been pinned down then. Just confirming this:
On Tue, Dec 26, 2017 at 06:16:37PM -0800, Linus Torvalds wrote:
> On Tue, Dec 26, 2017 at 3:19 PM, Alexandru Chirvasitu
> wrote:
> >
> > I went back to the initial problematic commit e802a51 and modified it as
>
Sounds like it's been pinned down then. Just confirming this:
On Tue, Dec 26, 2017 at 06:16:37PM -0800, Linus Torvalds wrote:
> On Tue, Dec 26, 2017 at 3:19 PM, Alexandru Chirvasitu
> wrote:
> >
> > I went back to the initial problematic commit e802a51 and modified it as
> > you suggest:
>
>
On December 26, 2017 6:54:55 PM PST, Linus Torvalds
wrote:
>On Tue, Dec 26, 2017 at 6:25 PM, wrote:
>>
>> This is why I personally prefer to see these kinds of terminal stubs
>written in assembly explicitly: the C compiler simply doesn't have all
On December 26, 2017 6:54:55 PM PST, Linus Torvalds
wrote:
>On Tue, Dec 26, 2017 at 6:25 PM, wrote:
>>
>> This is why I personally prefer to see these kinds of terminal stubs
>written in assembly explicitly: the C compiler simply doesn't have all
>the information needed to do the right thing.
On Tue, Dec 26, 2017 at 6:25 PM, wrote:
>
> This is why I personally prefer to see these kinds of terminal stubs written
> in assembly explicitly: the C compiler simply doesn't have all the
> information needed to do the right thing.
>
> I'm personally very sceptical to nuking
On Tue, Dec 26, 2017 at 6:25 PM, wrote:
>
> This is why I personally prefer to see these kinds of terminal stubs written
> in assembly explicitly: the C compiler simply doesn't have all the
> information needed to do the right thing.
>
> I'm personally very sceptical to nuking the GDT unless
On December 26, 2017 6:16:37 PM PST, Linus Torvalds
wrote:
>On Tue, Dec 26, 2017 at 3:19 PM, Alexandru Chirvasitu
> wrote:
>>
>> I went back to the initial problematic commit e802a51 and modified it
>as you suggest:
>
>Thank you.
>
>> This did
On December 26, 2017 6:16:37 PM PST, Linus Torvalds
wrote:
>On Tue, Dec 26, 2017 at 3:19 PM, Alexandru Chirvasitu
> wrote:
>>
>> I went back to the initial problematic commit e802a51 and modified it
>as you suggest:
>
>Thank you.
>
>> This did not work out for me, but now it fails differently.
On Tue, Dec 26, 2017 at 3:19 PM, Alexandru Chirvasitu
wrote:
>
> I went back to the initial problematic commit e802a51 and modified it as you
> suggest:
Thank you.
> This did not work out for me, but now it fails differently. Both
> (kexec -l + kexec -e) and (kexec -p +
On Tue, Dec 26, 2017 at 3:19 PM, Alexandru Chirvasitu
wrote:
>
> I went back to the initial problematic commit e802a51 and modified it as you
> suggest:
Thank you.
> This did not work out for me, but now it fails differently. Both
> (kexec -l + kexec -e) and (kexec -p + echo c >
On December 26, 2017 3:19:00 PM PST, Alexandru Chirvasitu
wrote:
>On Tue, Dec 26, 2017 at 10:51:12AM -0800, Linus Torvalds wrote:
>> [ Sorry, I was off-line on Christmas Eve due to festivities, and then
>> yesterday because I've apparently caught a cold.
>>
>> Still not
On December 26, 2017 3:19:00 PM PST, Alexandru Chirvasitu
wrote:
>On Tue, Dec 26, 2017 at 10:51:12AM -0800, Linus Torvalds wrote:
>> [ Sorry, I was off-line on Christmas Eve due to festivities, and then
>> yesterday because I've apparently caught a cold.
>>
>> Still not back to normal, but at
On December 26, 2017 3:19:00 PM PST, Alexandru Chirvasitu
wrote:
>On Tue, Dec 26, 2017 at 10:51:12AM -0800, Linus Torvalds wrote:
>> [ Sorry, I was off-line on Christmas Eve due to festivities, and then
>> yesterday because I've apparently caught a cold.
>>
>> Still not
On December 26, 2017 3:19:00 PM PST, Alexandru Chirvasitu
wrote:
>On Tue, Dec 26, 2017 at 10:51:12AM -0800, Linus Torvalds wrote:
>> [ Sorry, I was off-line on Christmas Eve due to festivities, and then
>> yesterday because I've apparently caught a cold.
>>
>> Still not back to normal, but at
On December 26, 2017 3:19:00 PM PST, Alexandru Chirvasitu
wrote:
>On Tue, Dec 26, 2017 at 10:51:12AM -0800, Linus Torvalds wrote:
>> [ Sorry, I was off-line on Christmas Eve due to festivities, and then
>> yesterday because I've apparently caught a cold.
>>
>> Still not
On December 26, 2017 3:19:00 PM PST, Alexandru Chirvasitu
wrote:
>On Tue, Dec 26, 2017 at 10:51:12AM -0800, Linus Torvalds wrote:
>> [ Sorry, I was off-line on Christmas Eve due to festivities, and then
>> yesterday because I've apparently caught a cold.
>>
>> Still not back to normal, but at
On Tue, Dec 26, 2017 at 10:51:12AM -0800, Linus Torvalds wrote:
> [ Sorry, I was off-line on Christmas Eve due to festivities, and then
> yesterday because I've apparently caught a cold.
>
> Still not back to normal, but at least I can sit in front of the
> computer again ]
>
> On Mon, Dec 25,
On Tue, Dec 26, 2017 at 10:51:12AM -0800, Linus Torvalds wrote:
> [ Sorry, I was off-line on Christmas Eve due to festivities, and then
> yesterday because I've apparently caught a cold.
>
> Still not back to normal, but at least I can sit in front of the
> computer again ]
>
> On Mon, Dec 25,
On December 26, 2017 10:51:12 AM PST, Linus Torvalds
wrote:
>[ Sorry, I was off-line on Christmas Eve due to festivities, and then
>yesterday because I've apparently caught a cold.
>
> Still not back to normal, but at least I can sit in front of the
>computer
On December 26, 2017 10:51:12 AM PST, Linus Torvalds
wrote:
>[ Sorry, I was off-line on Christmas Eve due to festivities, and then
>yesterday because I've apparently caught a cold.
>
> Still not back to normal, but at least I can sit in front of the
>computer again ]
>
>On Mon, Dec 25, 2017 at
[ Sorry, I was off-line on Christmas Eve due to festivities, and then
yesterday because I've apparently caught a cold.
Still not back to normal, but at least I can sit in front of the
computer again ]
On Mon, Dec 25, 2017 at 1:29 PM, Alexandru Chirvasitu
wrote:
>
> On
[ Sorry, I was off-line on Christmas Eve due to festivities, and then
yesterday because I've apparently caught a cold.
Still not back to normal, but at least I can sit in front of the
computer again ]
On Mon, Dec 25, 2017 at 1:29 PM, Alexandru Chirvasitu
wrote:
>
> On Mon, Dec 25, 2017 at
Thanks for that!
On Mon, Dec 25, 2017 at 06:40:14AM -0800, Andy Lutomirski wrote:
> On Sat, Dec 23, 2017 at 7:30 PM, Linus Torvalds
> wrote:
> > On Sat, Dec 23, 2017 at 5:44 PM, Alexandru Chirvasitu
> > wrote:
> >>
> >> For testing purposes,
Thanks for that!
On Mon, Dec 25, 2017 at 06:40:14AM -0800, Andy Lutomirski wrote:
> On Sat, Dec 23, 2017 at 7:30 PM, Linus Torvalds
> wrote:
> > On Sat, Dec 23, 2017 at 5:44 PM, Alexandru Chirvasitu
> > wrote:
> >>
> >> For testing purposes, I've altered machine_kexec_32.c making the
> >>
On Sat, Dec 23, 2017 at 7:30 PM, Linus Torvalds
wrote:
> On Sat, Dec 23, 2017 at 5:44 PM, Alexandru Chirvasitu
> wrote:
>>
>> For testing purposes, I've altered machine_kexec_32.c making the
>> following toy commit. It naively undoes part of
On Sat, Dec 23, 2017 at 7:30 PM, Linus Torvalds
wrote:
> On Sat, Dec 23, 2017 at 5:44 PM, Alexandru Chirvasitu
> wrote:
>>
>> For testing purposes, I've altered machine_kexec_32.c making the
>> following toy commit. It naively undoes part of e802a51, solely to
>> confirm that's where it goes
* Alexandru Chirvasitu wrote:
> The first attachment is the config I initially used last night after
> that second patch (removing 'local' etc.).
>
> As you guessed, all four options are set, hence the name of the file
> (ending in '-y'). The other config I'm attaching
* Alexandru Chirvasitu wrote:
> The first attachment is the config I initially used last night after
> that second patch (removing 'local' etc.).
>
> As you guessed, all four options are set, hence the name of the file
> (ending in '-y'). The other config I'm attaching was treated as you
> lay
* Alexandru Chirvasitu wrote:
> Thank you for the swift reply!
>
> On Sat, Dec 23, 2017 at 07:30:21PM -0800, Linus Torvalds wrote:
> > On Sat, Dec 23, 2017 at 5:44 PM, Alexandru Chirvasitu
> > wrote:
> > >
> > > For testing purposes, I've altered
* Alexandru Chirvasitu wrote:
> Thank you for the swift reply!
>
> On Sat, Dec 23, 2017 at 07:30:21PM -0800, Linus Torvalds wrote:
> > On Sat, Dec 23, 2017 at 5:44 PM, Alexandru Chirvasitu
> > wrote:
> > >
> > > For testing purposes, I've altered machine_kexec_32.c making the
> > > following
Thank you for the swift reply!
On Sat, Dec 23, 2017 at 07:30:21PM -0800, Linus Torvalds wrote:
> On Sat, Dec 23, 2017 at 5:44 PM, Alexandru Chirvasitu
> wrote:
> >
> > For testing purposes, I've altered machine_kexec_32.c making the
> > following toy commit. It naively
Thank you for the swift reply!
On Sat, Dec 23, 2017 at 07:30:21PM -0800, Linus Torvalds wrote:
> On Sat, Dec 23, 2017 at 5:44 PM, Alexandru Chirvasitu
> wrote:
> >
> > For testing purposes, I've altered machine_kexec_32.c making the
> > following toy commit. It naively undoes part of e802a51,
On Sat, Dec 23, 2017 at 5:44 PM, Alexandru Chirvasitu
wrote:
>
> For testing purposes, I've altered machine_kexec_32.c making the
> following toy commit. It naively undoes part of e802a51, solely to
> confirm that's where it goes awry in my setup.
That's really funky.
The
On Sat, Dec 23, 2017 at 5:44 PM, Alexandru Chirvasitu
wrote:
>
> For testing purposes, I've altered machine_kexec_32.c making the
> following toy commit. It naively undoes part of e802a51, solely to
> confirm that's where it goes awry in my setup.
That's really funky.
The idt_invalidate() seems
Short description: loading a crash kernel with (a) kexec -l [..] or
(b) kexec -p [..] and then testing it with (a) kexec -e or (b) echo c
> /proc/sysrq-trigger results in a regular reboot (going through BIOS,
etc.).
The commit that starts exhibiting this behaviour for me is
e802a51: x86/idt:
Short description: loading a crash kernel with (a) kexec -l [..] or
(b) kexec -p [..] and then testing it with (a) kexec -e or (b) echo c
> /proc/sysrq-trigger results in a regular reboot (going through BIOS,
etc.).
The commit that starts exhibiting this behaviour for me is
e802a51: x86/idt:
38 matches
Mail list logo