Re: L4Linux with hardware access on amd64 PC ...
Matthias Lange <[email protected]>
| Newsgroups | gmane.comp.micro-kernel.l4.devel |
|---|---|
| Message-ID | <20200831094159.GE298962@triton> |
Hi Andreas,
this is just guessing but I suspect that the compiler you used inserted a
'movqda' instruction into one of the libraries and that L4Linux is running on
a not correctly aligned stack. This is a known issue with newer toolchains (>=
gcc 7). We are currently investigating possible solutions.
Cheers,
Matthias.
On [20-08-2020 21:02], Andreas Steinmetzler wrote:
> Hi Adam,
>
>
> thanks for your reply and providing a new snapshot version. I pulled the tar
> ball and compiled everything without changing the configuration (except the
> L4 build path in L4Linux) and build the L4Linux-mag target as grub2iso.
>
> When booting the target machine it switches to graphics mode and creates one
> black window and on the serial console you could see the L4Linux exception
> (bootlog copied below).
>
> One remark, I couldn't use my original target machine (used in the previous
> post) as it does not have any graphical output (only serial console port) so
> mag server didn't even start. With another machine with graphical output and
> serial port it also stopped when loading L4Linux. As you have tested this
> configuration on your side, I'm wondering if the build environment I'm using
> is causing this problem (Ubuntu 18.04 and GCC 7.5.0). Will try to create a
> Ubuntu 16.04 build machine and try again to check if it's making any
> difference. Will send an update later ...
>
>
> Cheers
>
> Andreas
>
>
>
> L4 Bootstrapper
>
> Build: #1 Thu Aug 20 20:06:22 PDT 2020, x86-64, 7.5.0
>
> RAM: 0000000000000000 - 000000000009ebff: 635kB
>
> RAM: 0000000000100000 - 000000001effffff: 506880kB
>
> RAM: 0000000020200000 - 000000007b083fff: 1489424kB
>
> RAM: 000000007b0fe000 - 000000007b225fff: 1184kB
>
> RAM: 000000007b994000 - 000000007bffffff: 6576kB
>
> RAM: 0000000100000000 - 000000027fffffff: 6291456kB
>
> Total RAM: 8101MB
>
> Scanning fiasco -serial_esc
>
> Scanning sigma0
>
> Scanning moe rom/l4lx-gfx.cfg
>
> need 1272 bytes to copy MBI
>
> reserved 1272 bytes at 0x2000
>
> Moving up to 13 modules behind 1100000
>
> moving module 12 { 248a000-2789fff } -> { 26a7000-29a6fff } [3145728]
>
> moving module 11 { 15d6000-2489c97 } -> { 17f3000-26a6c97 } [15416472]
>
> moving module 08 { 150f000-15d5ddf } -> { 172c000-17f2ddf } [814560]
>
> moving module 06 { 1238000-150eea7 } -> { 1455000-172bea7 } [2977448]
>
> moving module 00 { 1021000-1237d57 } -> { 123e000-1454d57 } [2190680]
>
> moving module 10 { 23e000-23e25e } -> { 123d000-123d25e } [607]
>
> moving module 09 { 23d000-23d337 } -> { 123c000-123c337 } [824]
>
> moving module 07 { 1e9000-23ca7f } -> { 11e8000-123ba7f } [342656]
>
> moving module 05 { 170000-1e89ef } -> { 116f000-11e79ef } [494064]
>
> moving module 04 { 152000-16f72f } -> { 1151000-116e72f } [120624]
>
> moving module 03 { 151000-15151b } -> { 1150000-115051b } [1308]
>
> moving module 02 { 10e000-15075f } -> { 110d000-114f75f } [272224]
>
> moving module 01 { 101000-10d48f } -> { 1100000-110c48f } [50320]
>
> Loading fiasco
>
> Loading sigma0
>
> Loading moe
>
> find kernel info page...
>
> found kernel info page (via ELF) at 400000
>
> Regions of list 'regions'
>
> [0, fff] { 1000} Arch BIOS
>
> [ 1000,1fff] { 1000} Kern fiasco
>
> [ 2000,24f7] {4f8} Root mbi_rt
>
> [9ec00, 9ffff] { 1400} Arch BIOS
>
> [e0000, fffff] {20000} Arch BIOS
>
> [ 100000,11247f] {12480} Sigma0 sigma0
>
> [ 140000,17fa6b] {3fa6c} Root moe
>
> [ 181038,1930e7] {120b0} Root moe
>
> [ 2d0400,2e1257] {10e58} Boot bootstrap
>
> [ 300000,34afff] {4b000} Kern fiasco
>
> [ 400000,61efff] { 21f000} Kern fiasco
>
> [1019000, 101efff] { 6000} Boot bootstrap-ptab64
>
> [1150000, 123dfff] {ee000} Root Module
>
> [1455000, 29a6fff] {1552000} Root Module
>
> [ 1f000000,201fffff] {1200000} Arch BIOS
>
> [ 7b084000,7b0fdfff] {7a000} Arch BIOS
>
> [ 7b226000,7b687fff] { 462000} Arch BIOS
>
> [ 7b688000,7b993fff] { 30c000} Arch BIOS
>
> [ e0000000,efffffff] { 10000000} Arch BIOS
>
> [ fea00000,feafffff] { 100000} Arch BIOS
>
> [ fec00000,fec00fff] { 1000} Arch BIOS
>
> [ fed01000,fed01fff] { 1000} Arch BIOS
>
> [ fed03000,fed03fff] { 1000} Arch BIOS
>
> [ fed06000,fed06fff] { 1000} Arch BIOS
>
> [ fed08000,fed09fff] { 2000} Arch BIOS
>
> [ fed1c000,fed1cfff] { 1000} Arch BIOS
>
> [ fed80000,fedbffff] {40000} Arch BIOS
>
> [ fee00000,fee00fff] { 1000} Arch BIOS
>
> [ ffb00000,ffffffff] { 500000} Arch BIOS
>
> found kernel options (via ELF) at 401000
>
> Sigma0 configip:00000000001004a0 sp:0000000000000000
>
> Roottask configip:00000000001418bd sp:0000000000000000
>
> Starting kernel fiasco at 0000000000300910
>
> Welcome to L4/Fiasco.OC!
>
> L4/Fiasco.OC microkernel on amd64
>
> Rev: unknown compiled with gcc 7.5.0 for x86-64[]
>
> Build: #1 Thu Aug 20 20:08:28 PDT 2020
>
> Performance-critical config option(s) detected:
>
> CONFIG_NDEBUG is off
>
> Superpages: yes
>
> Kmem:: TSS mem at 2619fc000 (4096Bytes)
>
> VMX: enabled
>
> VMX: EPT supported
>
> VMX: initialized
>
> ACPI: RSDP[0xf0580] r02 OEM:ALASKA
>
> FPU0: SSE
>
> ACPI: FACS phys=7b687e80 virt=0x20287e80
>
> ACPI: HW sig=a2e2c242
>
> SERIAL ESC: allocated IRQ 4 for serial uart
>
> Enable MSI support: chained IRQ mgr @ 0xffffffff101f4520
>
> VMX: init page sizes
>
> SERIAL ESC: allocated IRQ 4 for serial uart
>
> Not using serial hack in slow timer handler.
>
> CPU[0]: GenuineIntel (6:4C:4:0)[000406c4] Model: Intel(R) Celeron(R)
> CPUN3060@ 1.60GHz at 1599MHz
>
> 256 Entry D TLB (4K pages)
>
> Freeing init code/data: 36864 bytes (9 pages)
>
> VMX: enabled
>
> VMX: EPT supported
>
> VMX: initialized
>
> Calibrating timer loop... done.
>
> MDB: use page size: 30
>
> MDB: use page size: 21
>
> MDB: use page size: 12
>
> SIGMA0: Hello!
>
> KIP @ 400000
>
> allocated 4KB for maintenance structures
>
> SIGMA0: Dump of all resource maps
>
> RAM:------------------------
>
> [4:RWX:2000;2fff]
>
> [0:RWX:3000;9dfff]
>
> [0:RWX:113000;13ffff]
>
> [4:R-X:140000;17ffff]
>
> [0:RWX:180000;180fff]
>
> [4:RW-:181000;193fff]
>
> [0:RWX:194000;3fffff]
>
> [0:RWX:616000;114ffff]
>
> [4:RWX:1150000;123dfff]
>
> [0:RWX:123e000;1454fff]
>
> [4:RWX:1455000;29a6fff]
>
> [0:RWX:29a7000;1effffff]
>
> [0:RWX:20200000;7b083fff]
>
> [0:RWX:7b0fe000;7b225fff]
>
> [0:RWX:7b994000;7bffffff]
>
> [0:RWX:100000000;2619e4fff]
>
> IOMEM:----------------------
>
> [0:RW-:0;fff]
>
> [0:RW-:9e000;fffff]
>
> [0:RW-:1f000000;201fffff]
>
> [0:RW-:7b084000;7b0fdfff]
>
> [0:RW-:7b226000;7b993fff]
>
> [0:RW-:7c000000;fedfffff]
>
> [0:RWX:fee01000;ffffffff]
>
> [0:RWX:280000000;ffffffffffffffff]
>
> IO PORTS--------------------------
>
> [0:RW-:0;fffffff]
>
> MOE: Hello world
>
> MOE: found 7773044 KByte free memory
>
> MOE: found RAM from 2000 to 2619e5000
>
> MOE: allocated 9753 KByte for the page array @0x616000
>
> MOE: virtual user address space [0-7fffffffffff]
>
> MOE: rom name space cap -> [C:103000]
>
> MOE: rwfs name space cap -> [C:105000]
>
> BOOTFS: [1150000-115051c] [C:107000] l4lx-gfx.cfg
>
> BOOTFS: [1151000-116e730] [C:109000] l4re
>
> BOOTFS: [116f000-11e79f0] [C:10b000] ned
>
> BOOTFS: [1455000-172bea8] [C:10d000] io
>
> BOOTFS: [11e8000-123ba80] [C:10f000] fb-drv
>
> BOOTFS: [172c000-17f2de0] [C:111000] mag
>
> BOOTFS: [123c000-123c338] [C:113000] x86-legacy.devs
>
> BOOTFS: [123d000-123d25f] [C:115000] l4lx-x86.io
>
> BOOTFS: [17f3000-26a6c98] [C:117000] vmlinuz
>
> BOOTFS: [26a7000-29a7000] [C:119000] ramdisk-amd64.rd
>
> No fpage received
>
> MOE: cmdline: moe rom/l4lx-gfx.cfg
>
> MOE: Starting: rom/ned rom/l4lx-gfx.cfg
>
> MOE: loading 'rom/ned'
>
> Ned says: Hi World!
>
> Ned: loading file: 'rom/l4lx-gfx.cfg'
>
> io| Io service
>
> io| Find root Pointer
>
> io| Found root Pointer: f0580
>
> io| ACPI: RSDP 0x00000000000F0580 000024 (v02 ALASKA)
>
> io| ACPI: XSDT 0x000000007B5F3080 00007C (v01 ALASKA A M I01072009
> AMI00010013)
>
> io| ACPI: FACP 0x000000007B5FF750 00010C (v05 ALASKA A M I01072009
> AMI00010013)
>
> io| Firmware Warning (ACPI): 32/64X length mismatch in FADT/Gpe0Block:
> 128/32 (20190816/tbfadt-750)
>
> io| ACPI: DSDT 0x000000007B5F3190 00C5BD (v02 ALASKA A M I01072009 INTL
> 20120913)
>
> io| ACPI: FACS 0x000000007B687E80 000040
>
> io| ACPI: APIC 0x000000007B5FF860 000068 (v03 ALASKA A M I01072009
> AMI00010013)
>
> io| ACPI: FPDT 0x000000007B5FF8C8 000044 (v01 ALASKA A M I01072009
> AMI00010013)
>
> io| ACPI: FIDT 0x000000007B5FF910 00009C (v01 ALASKA A M I01072009
> AMI00010013)
>
> io| ACPI: MCFG 0x000000007B5FF9B0 00003C (v01 ALASKA A M I01072009 MSFT
> 00000097)
>
> io| ACPI: SSDT 0x000000007B5FF9F0 000763 (v01 PmRefCpuPm00003000 INTL
> 20061109)
>
> io| ACPI: SSDT 0x000000007B600158 000290 (v01 PmRefCpu0Tst00003000 INTL
> 20061109)
>
> io| ACPI: SSDT 0x000000007B6003E8 00017A (v01 PmRefApTst00003000 INTL
> 20061109)
>
> io| ACPI: UEFI 0x000000007B600568 000042 (v01 ALASKA A M I0000000000000000)
>
> io| ACPI: LPIT 0x000000007B6005B0 000104 (v01 ALASKA A M I00000005 MSFT
> 0100000D)
>
> io| ACPI: CSRT 0x000000007B6006B8 00014C (v00 INTELLANFORDC 00000005 MSFT
> 0100000D)
>
> io|
>
> io| ACPI table initialization:
>
> io| Table [DSDT: A M I ] (id 01) - 1985 Objects with 142 Devices,64
> Regions,483 Methods (222/261/53 Serial/Non/Cvt)
>
> io| Table [SSDT: CpuPm ] (id 05) - 35 Objects with 0 Devices, 0 Regions, 20
> Methods (12/8/12 Serial/Non/Cvt)
>
> io| Table [SSDT: Cpu0Tst ] (id 06) -8 Objects with 0 Devices, 0 Regions,4
> Methods (1/3/1 Serial/Non/Cvt)
>
> io| Table [SSDT: ApTst ] (id 07) - 12 Objects with 0 Devices, 0 Regions,9
> Methods (0/9/0 Serial/Non/Cvt)
>
> io| ACPI: 4 ACPI AML tables successfully acquired and loaded
>
> io| Final data object initialization: Namespace contains 2049 (0x801)
> objects
>
> io|evxfevnt-0218 Enable: Transition to ACPI mode successful
>
> io| Initializing General Purpose Events (GPEs):
>
> io| Initialized GPE 00 to 3F [_GPE] 8 regs on interrupt 0x9 (SCI)
>
> io| Initializing Device/Processor/Thermal objects and executing _INI/_STA
> methods:
>
> io| Executed 1 _INI methods requiring 0 _STA executions (examined 149
> objects)
>
> io| ERROR: EC: error missing resources
>
> io| error: ACPI LID0: could not evaluate _PRW object (AE_NOT_FOUND), not
> enabled as wake source
>
> io| error: ACPI SLPB: could not evaluate _PRW object (AE_NOT_FOUND), not
> enabled as wake source
>
> io| ACPICA-Version:20190816, System in ACPI MODE, 32bit timer
>
> io| ACPI: Enabled 7 GPEs in block 00 to 3F
>
> io| Ready. Waiting for request.
>
> mag | Hello from MAG
>
> fb-drv| Trying execution of ``set VBE mode'' using x86emu
>
> fb-drv| Found VESA BIOS version 3.0
>
> fb-drv| OEM Intel(R) CHV Mobile/Desktop Graphics Chipset Accelerated VGA
> BIOS
>
> fb-drv| c000:5975 inb 61 -> 0 ignored
>
> fb-drv| c000:597c outb 61 -> 1 ignored
>
> fb-drv| c000:59ad outb 61 -> 0 ignored
>
> fb-drv| c000:5975 inb 61 -> 0 ignored
>
> fb-drv| c000:597c outb 61 -> 1 ignored
>
> fb-drv| c000:59ad outb 61 -> 0 ignored
>
> fb-drv| c000:5975 inb 61 -> 0 ignored
>
> fb-drv| c000:597c outb 61 -> 1 ignored
>
> fb-drv| c000:59ad outb 61 -> 0 ignored
>
> fb-drv| c000:5975 inb 61 -> 0 ignored
>
> fb-drv| c000:597c outb 61 -> 1 ignored
>
> fb-drv| c000:59ad outb 61 -> 0 ignored
>
> fb-drv| c000:5975 inb 61 -> 0 ignored
>
> fb-drv| c000:597c outb 61 -> 1 ignored
>
> fb-drv| c000:59ad outb 61 -> 0 ignored
>
> fb-drv| c000:5975 inb 61 -> 0 ignored
>
> fb-drv| c000:597c outb 61 -> 1 ignored
>
> fb-drv| c000:59ad outb 61 -> 0 ignored
>
> fb-drv| c000:5975 inb 61 -> 0 ignored
>
> fb-drv| c000:597c outb 61 -> 1 ignored
>
> fb-drv| c000:59ad outb 61 -> 0 ignored
>
> fb-drv| c000:5975 inb 61 -> 0 ignored
>
> fb-drv| c000:597c outb 61 -> 1 ignored
>
> fb-drv| c000:59ad outb 61 -> 0 ignored
>
> fb-drv| c000:5975 inb 61 -> 0 ignored
>
> fb-drv| c000:597c outb 61 -> 1 ignored
>
> fb-drv| c000:59ad outb 61 -> 0 ignored
>
> fb-drv| c000:5975 inb 61 -> 0 ignored
>
> fb-drv| c000:597c outb 61 -> 1 ignored
>
> fb-drv| c000:59ad outb 61 -> 0 ignored
>
> fb-drv| c000:5975 inb 61 -> 0 ignored
>
> fb-drv| c000:597c outb 61 -> 1 ignored
>
> fb-drv| c000:59ad outb 61 -> 0 ignored
>
> fb-drv| c000:5975 inb 61 -> 0 ignored
>
> fb-drv| c000:597c outb 61 -> 1 ignored
>
> fb-drv| c000:59ad outb 61 -> 0 ignored
>
> fb-drv| c000:5975 inb 61 -> 0 ignored
>
> fb-drv| c000:597c outb 61 -> 1 ignored
>
> fb-drv| c000:59ad outb 61 -> 0 ignored
>
> fb-drv| c000:5975 inb 61 -> 0 ignored
>
> fb-drv| c000:597c outb 61 -> 1 ignored
>
> fb-drv| c000:59ad outb 61 -> 0 ignored
>
> fb-drv| c000:5975 inb 61 -> 0 ignored
>
> fb-drv| c000:597c outb 61 -> 1 ignored
>
> fb-drv| c000:59ad outb 61 -> 0 ignored
>
> fb-drv| c000:5975 inb 61 -> 0 ignored
>
> fb-drv| c000:597c outb 61 -> 1 ignored
>
> fb-drv| c000:59ad outb 61 -> 0 ignored
>
> fb-drv| c000:5975 inb 61 -> 0 ignored
>
> fb-drv| c000:597c outb 61 -> 1 ignored
>
> fb-drv| c000:59ad outb 61 -> 0 ignored
>
> fb-drv| c000:5975 inb 61 -> 0 ignored
>
> fb-drv| c000:597c outb 61 -> 1 ignored
>
> fb-drv| c000:59ad outb 61 -> 0 ignored
>
> fb-drv| c000:5975 inb 61 -> 0 ignored
>
> fb-drv| c000:597c outb 61 -> 1 ignored
>
> fb-drv| c000:59ad outb 61 -> 0 ignored
>
> fb-drv| c000:5975 inb 61 -> 0 ignored
>
> fb-drv| c000:597c outb 61 -> 1 ignored
>
> fb-drv| c000:59ad outb 61 -> 0 ignored
>
> fb-drv| c000:5975 inb 61 -> 0 ignored
>
> fb-drv| c000:597c outb 61 -> 1 ignored
>
> fb-drv| c000:59ad outb 61 -> 0 ignored
>
> fb-drv| c000:5975 inb 61 -> 0 ignored
>
> fb-drv| c000:597c outb 61 -> 1 ignored
>
> fb-drv| c000:59ad outb 61 -> 0 ignored
>
> fb-drv| c000:5975 inb 61 -> 0 ignored
>
> fb-drv| c000:597c outb 61 -> 1 ignored
>
> fb-drv| c000:59ad outb 61 -> 0 ignored
>
> fb-drv| c000:5975 inb 61 -> 0 ignored
>
> fb-drv| c000:597c outb 61 -> 1 ignored
>
> fb-drv| c000:59ad outb 61 -> 0 ignored
>
> fb-drv| c000:5975 inb 61 -> 0 ignored
>
> fb-drv| c000:597c outb 61 -> 1 ignored
>
> fb-drv| c000:59ad outb 61 -> 0 ignored
>
> fb-drv| c000:5975 inb 61 -> 0 ignored
>
> fb-drv| c000:597c outb 61 -> 1 ignored
>
> fb-drv| c000:59ad outb 61 -> 0 ignored
>
> fb-drv| c000:5975 inb 61 -> 0 ignored
>
> fb-drv| c000:597c outb 61 -> 1 ignored
>
> fb-drv| c000:59ad outb 61 -> 0 ignored
>
> fb-drv| c000:5975 inb 61 -> 0 ignored
>
> fb-drv| c000:597c outb 61 -> 1 ignored
>
> fb-drv| c000:59ad outb 61 -> 0 ignored
>
> fb-drv| c000:5975 inb 61 -> 0 ignored
>
> fb-drv| c000:597c outb 61 -> 1 ignored
>
> fb-drv| c000:59ad outb 61 -> 0 ignored
>
> fb-drv| c000:5975 inb 61 -> 0 ignored
>
> fb-drv| c000:597c outb 61 -> 1 ignored
>
> fb-drv| c000:59ad outb 61 -> 0 ignored
>
> fb-drv| c000:5975 inb 61 -> 0 ignored
>
> fb-drv| c000:597c outb 61 -> 1 ignored
>
> fb-drv| c000:59ad outb 61 -> 0 ignored
>
> fb-drv| c000:5975 inb 61 -> 0 ignored
>
> fb-drv| c000:597c outb 61 -> 1 ignored
>
> fb-drv| c000:59ad outb 61 -> 0 ignored
>
> fb-drv| c000:5975 inb 61 -> 0 ignored
>
> fb-drv| c000:597c outb 61 -> 1 ignored
>
> fb-drv| c000:59ad outb 61 -> 0 ignored
>
> fb-drv| c000:5975 inb 61 -> 0 ignored
>
> fb-drv| c000:597c outb 61 -> 1 ignored
>
> fb-drv| c000:59ad outb 61 -> 0 ignored
>
> fb-drv| c000:5975 inb 61 -> 0 ignored
>
> fb-drv| c000:597c outb 61 -> 1 ignored
>
> fb-drv| c000:59ad outb 61 -> 0 ignored
>
> fb-drv| c000:5975 inb 61 -> 0 ignored
>
> fb-drv| c000:597c outb 61 -> 1 ignored
>
> fb-drv| c000:59ad outb 61 -> 0 ignored
>
> fb-drv| c000:5975 inb 61 -> 0 ignored
>
> fb-drv| c000:597c outb 61 -> 1 ignored
>
> fb-drv| c000:59ad outb 61 -> 0 ignored
>
> fb-drv| c000:5975 inb 61 -> 0 ignored
>
> fb-drv| c000:597c outb 61 -> 1 ignored
>
> fb-drv| c000:59ad outb 61 -> 0 ignored
>
> fb-drv| c000:5975 inb 61 -> 0 ignored
>
> fb-drv| c000:597c outb 61 -> 1 ignored
>
> fb-drv| c000:59ad outb 61 -> 0 ignored
>
> fb-drv| c000:5975 inb 61 -> 0 ignored
>
> fb-drv| c000:597c outb 61 -> 1 ignored
>
> fb-drv| c000:59ad outb 61 -> 0 ignored
>
> fb-drv| c000:5975 inb 61 -> 0 ignored
>
> fb-drv| c000:597c outb 61 -> 1 ignored
>
> fb-drv| c000:59ad outb 61 -> 0 ignored
>
> fb-drv| c000:5975 inb 61 -> 0 ignored
>
> fb-drv| c000:597c outb 61 -> 1 ignored
>
> fb-drv| c000:59ad outb 61 -> 0 ignored
>
> fb-drv| c000:5975 inb 61 -> 0 ignored
>
> fb-drv| c000:597c outb 61 -> 1 ignored
>
> fb-drv| c000:59ad outb 61 -> 0 ignored
>
> fb-drv| c000:5975 inb 61 -> 0 ignored
>
> fb-drv| c000:597c outb 61 -> 1 ignored
>
> fb-drv| c000:59ad outb 61 -> 0 ignored
>
> fb-drv| c000:5975 inb 61 -> 0 ignored
>
> fb-drv| c000:597c outb 61 -> 1 ignored
>
> fb-drv| c000:59ad outb 61 -> 0 ignored
>
> fb-drv| c000:5975 inb 61 -> 0 ignored
>
> fb-drv| c000:597c outb 61 -> 1 ignored
>
> fb-drv| c000:59ad outb 61 -> 0 ignored
>
> fb-drv| c000:5975 inb 61 -> 0 ignored
>
> fb-drv| c000:597c outb 61 -> 1 ignored
>
> fb-drv| c000:59ad outb 61 -> 0 ignored
>
> fb-drv| VBE mode 0x117 successfully set.
>
> fb-drv| Framebuffer memory: phys: 90000000 - 91df0000
>
> fb-drv| virt: 1100000 - 2ef0000
>
> fb-drv| Starting server loop
>
> mag | mapped frame buffer at 0x1200000
>
> mag | View::Info:
>
> mag | flags: 0
>
> mag | size:1024x768
>
> mag | pos: 0x0
>
> mag | bytes_per_line: 2048
>
> mag | buffer_offset:0
>
> mag | RGBA(2):5(11):6(5):5(0):0(0)
>
> mag | memory 0x1200000 - 0x2ff0000
>
> mag | Plugin: Mag_client service started
>
> mag | Plugin: Frame-buffer service started
>
> mag | L4INPUT native mode activated
>
> mag | L4INPUT:!!! W A R N I N G !!!
>
> mag | L4INPUT:Please, do not use Fiasco's "-esc" with L4INPUT.
>
> mag | L4INPUT:!!! W A R N I N G !!!
>
> mag |
> /home/andreas/tud/l4re-snapshot-20.08.0/src/l4/pkg/input/lib/src/init.c:110:
> failed l4input_internal_i8042_init(): -16
>
> PH0 offs=0000000000200000 flags=r-x PH-type=0x1
>
> virt=0000000000200000 evirt=0000000000af0740
>
> phys=0000000000200000 ephys=0000000000af0740
>
> f_sz=00000000008f0740 memsz=00000000008f0740
>
> PH1 offs=0000000000c00000 flags=rw- PH-type=0x1
>
> virt=0000000000c00000 evirt=0000000000db1000
>
> phys=0000000000c00000 ephys=0000000000db1000
>
> f_sz=00000000001b1000 memsz=00000000001b1000
>
> PH2 offs=0000000000db1000 flags=rwx PH-type=0x1
>
> virt=0000000000db1000 evirt=0000000001016000
>
> phys=0000000000db1000 ephys=0000000001016000
>
> f_sz=0000000000077000 memsz=0000000000265000
>
> PH3 offs=0000000000af0704 flags=--- PH-type=0x4
>
> virt=0000000000af0704 evirt=0000000000af0740
>
> phys=0000000000af0704 ephys=0000000000af0740
>
> f_sz=000000000000003c memsz=000000000000003c
>
> Starting binary at 0x200000, argc=6 argv=0xafff5f18 *argv=0x7100fff4
> argv0=rom/vmlinuz
>
> External resolver is at 0x68000d30
>
> ======> L4Linux starting... <========
>
> Linux version 5.7.0-l4 (andreas@deepl) (gcc version 7.5.0 (Ubuntu
> 7.5.0-3ubuntu1~18.04), GNU ld (GNU Binutils for Ubuntu) 2.30) #1 Thu Aug 20
> 20:11:24 PDT 2020
>
> Binary name: rom/vmlinuz
>
> Linux kernel command line (5 args): mem=64M console=tty0
> l4x_rd=rom/ramdisk-amd64.rd root=1:0 ramdisk_size=4000
>
> CPU mapping (l:p)[1]: 0:0
>
> Image: 00200000 - 01016000 [14424 KiB].
>
> Areas: Text: 00200000 - 008006d1 [6145kB]
>
> RO-Data:00a00000 - 00af1000 [964kB]
>
> Data: 00c00000 - 00c54840 [338kB]
>
> Init: 00db1000 - 00e27000 [472kB]
>
> BSS:00e28000 - 01000000 [1888kB]
>
> Device scan:
>
> Device: L4ICU
>
> Device: PCI0
>
> Device: pci_l4x[1]
>
> L4Re: rom/vmlinuz: Unhandled exception: PC=0x68008618 PFA=0x0 LdrFlgs=0x0
>
>
>
> On 8/20/20 4:12 PM, Adam Lackorzynski wrote:
> > Hi,
> >
> > On Mon Aug 17, 2020 at 22:35:11 -0700, Andreas Steinmetzler wrote:
> > > Hi,
> > >
> > > I'm experimenting with the TuD Snapshot release 2020.07.1 and can compile
> > > and run Fiasco, L4re and L4Linux in their basic configurations (amd64
> > > architecture) using the default l4lx.cfg file of the distribution.
> > >
> > > As this is not all that useful, I was looking in getting the system use the
> > > available hardware. Based on snippets I found on the internet and the
> > > example config files, I created the following cfg and devs files, but now
> > > L4Linux immediately runs into an unhandled exception (full boot log at the
> > > end of this eMail).
> > >
> > > Was wondering if someone from the mailing list can share a set of config
> > > files which would allow to get L4Linux up and using at least some of the
> > > basic hardware like network and disks on a typical PC board. In my current
> > > experiments I'm using the following config files (see below).
> > >
> > > Any help or pointers are appreciated!
> > An error like this should not happen, irrespective of any config.
> > I've uploaded 2020.08.0 and checked that the amd64 L4Linux configs in
> > the L4Linux-mag setup works and sees PCI devices.
> > Could you work from that config?
> >
> >
> >
> > Adam
> >
> > _______________________________________________
> > l4-hackers mailing list
> > [email protected]
> > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
> _______________________________________________
> l4-hackers mailing list
> [email protected]
> http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
--
Matthias Lange phone: +49 (0) 351-41 888 614
Senior Operating Systems Engineer
[email protected] Kernkonzept GmbH
https://www.kernkonzept.com Buchenstraße 16b
https://twitter.com/kernkonzept 01097 Dresden
Geschäftsführer: Dr.-Ing. Michael Hohmuth
Registergericht: Amtsgericht Dresden
Handelsregister: HRB 31129