IRC channel logs

<jack-sparrow>happy new year from france

<damo22>im definitely in protected mode:

<damo22> 0x0001103c <+60>: b8 aa aa aa aa mov $0xaaaaaaaa,%eax

<damo22> 0x00011041 <+65>: f4 hlt

<damo22>=> 0x00011042 <+66>: 90 nop

<damo22>CPU#5

<damo22>EAX=aaaaaaaa EBX=00000000 ECX=00000000 EDX=00001100

<damo22>ESI=00000000 EDI=00000000 EBP=00000000 ESP=00000000

<damo22>EIP=00011042 EFL=00000006 [-----P-] CPL=0 II=0 A20=1 SMM=0 HLT=1

<damo22> 0x0001103c <+60>: 0f 01 15 72 5c 09 01 lgdtl 0x1095c72

<damo22> 0x00011043 <+67>: ea 4a 10 01 00 08 00 ljmp $0x8,$0x1104a

<damo22> 0x0001104a <+74>: This is never reached

<damo22>maybe it needs to be 0xc001104a so the segmentation applies and corrects the offset

<damo22>got it!!

<damo22>Thread 2 (Thread 1.2 (CPU#1 [halted ])):

<damo22>#0 0xc001105e in ?? ()

<damo22>somehow the segmentation is not right anymore in the bootstrap C code in call_ap_main()

<damo22>youpi: what is the reasoning behind needing to set up gnumach with 40000000 segmentation in early boot? can we remove it?

<damo22>why cant we just use a flat address space?

<azert>damo22: in regards to swaps, we should pay attention that user space may be able to use the fsgsbase instruction. If that is allowed, the paranoid check cannot be used if I recall correctly and only the stack based check works.

<azert>swapgs

<youpi1>damo22: I don't see what you are referring to

<yang>Happy GNU year!

<nexussfan>:D

<user_oreloznog>Happy new year Hurd!

IRC channel logs

2026-01-01.log