users

users@lists.genode.org

2330 discussions

Next Step For Sculpt On New ThinkPad
by John J. Karcher 09 Oct '19

09 Oct '19

Hello, As I hoped, by copying the files from the Sculpt USB stick to my NVMe Ext2 partition, I can now boot into Sculpt on the ThinkPad L380 Yoga (using Norman's USB HID-disabling patches). The results are basically the same as booting from from USB, but hopefully this will allow me to load local packages and save log files to the NVMe partition. Does anyone have any ideas on what I can try, in order to generate some useful output? To recap, the most important limitations at the moment are 1) the the Inspect window doesn't open, and 2) I can't connect to a network. Thanks! -- John J. Karcher devuser(a)alternateapproach.com

2 3

CfP: FOSDEM 2020 - Microkernels and Component-based OS devroom
by Julian Stecklina 04 Oct '19

04 Oct '19

[Resent due to wrong Reply-To: header] FOSDEM 2020 - Microkernels and Component-based OS devroom CALL FOR PARTICIPATION The developers of several free and open-source microkernel-based operating systems will meet at FOSDEM 2020 [1] in Brussels, Belgium and will share a developer room. The devroom is currently looking for content in the form of talks and activities related to the area of microkernel-, unikernel-, and component-based operating systems. Possible topics include, but are not limited to: * introduction of a specific OS or framework * design of subsystems and the general architecture of an OS * used languages and tools * enabling support for hardware (architectures, device drivers) * enabling support for programming languages * maintenance and testing * security and robustness * trends and challenges * use cases, experiences, lessons learned and demos The deadline for your proposal is on December 1, 2019. Please use the Pentabarf [2] system to submit your proposals. You do not need to create a new account if you already have one. Make sure to include the following in your proposal: * title of your talk (will be printed in the FOSDEM booklet) * your full name (will be printed in the FOSDEM booklet) * a short abstract (one or two paragraphs) * duration of your talk (at least 25 and no longer than 55 min) The official devroom schedule (along with the accepted talks) will be announced on December 15 on the devroom's mailing list [3] and the speakers will be notified via e-mail. The schedule will also be published on the FOSDEM website. You are invited to send any other suggestions for what you want to see or do at the devroom to the list. We will also use this list to organize the traditional devroom dinner that will happen on the first day of FOSDEM. About the devroom Since the first Microkernel devroom at FOSDEM 2012, this devroom has been part of each following FOSDEM. The focus gradually widened to include component-based operating systems. By now it has become a somewhat institutionalized tradition for the community to meet there; to this date over a dozen projects have participated in one way or another. Each of the projects face similar challenges but come up with partially different solutions. Therefore, the goal of the devroom is to bring the various projects together, let them exchange ideas, cross-pollinate and socialize. Social events It also has become a habit that the microkernel projects dine together somewhere in Brussels. The year 2020 will not be any different, so there is going to be a dinner on Saturday night. We try place a reservation, so we will inform you about the exact location and time later. Consult the FOSDEM web and other projects for additional social events such as the famous FOSDEM-organized Friday Beer Event and the FOSDEM-arranged free sightseeing tours for spouses. About FOSDEM FOSDEM is a two-day event organised by volunteers to promote the widespread use of free and open source software. Taking place in the beautiful city of Brussels (Belgium), FOSDEM is widely recognised as the best such conference in Europe. FOSDEM covers a wide spectrum of free and open source software projects, and offers a platform for people to collaborate. To this end, FOSDEM has set up developer rooms (devrooms) with network/internet connectivity and projectors where teams can meet and showcase their projects. Devrooms are a place for teams to discuss, hack and publicly present latest directions, lightning talks, news and discussions. Besides developer rooms, FOSDEM also offers main tracks, lightning talks, certification exams and project stands. Every year, FOSDEM hosts more than 5000 developers at the ULB Solbosch campus. Participation and attendance is totally free, though the organisers gratefully accept donations and sponsorship. No registration necessary. Important dates recap * 2019-12-01: Deadline for submissions * 2019-12-15: Schedule published and speakers notified of acceptance * 2020-02-01: Devroom Dinner (details to be announced) * 2020-02-01/2020-02-02: The devroom takes places (check the schedule) Links [1] https://fosdem.org/ [2] https://penta.fosdem.org/submission/FOSDEM20 [3] https://lists.fosdem.org/listinfo/microkernel-devroom

1 0

CfP: FOSDEM 2020 - Microkernels and Component-based OS devroom
by Julian Stecklina 04 Oct '19

04 Oct '19

FOSDEM 2020 - Microkernels and Component-based OS devroom CALL FOR PARTICIPATION The developers of several free and open-source microkernel-based operating systems will meet at FOSDEM 2020 [1] in Brussels, Belgium and will share a developer room. The devroom is currently looking for content in the form of talks and activities related to the area of microkernel-, unikernel-, and component-based operating systems. Possible topics include, but are not limited to: * introduction of a specific OS or framework * design of subsystems and the general architecture of an OS * used languages and tools * enabling support for hardware (architectures, device drivers) * enabling support for programming languages * maintenance and testing * security and robustness * trends and challenges * use cases, experiences, lessons learned and demos The deadline for your proposal is on December 1, 2019. Please use the Pentabarf [2] system to submit your proposals. You do not need to create a new account if you already have one. Make sure to include the following in your proposal: * title of your talk (will be printed in the FOSDEM booklet) * your full name (will be printed in the FOSDEM booklet) * a short abstract (one or two paragraphs) * duration of your talk (at least 25 and no longer than 55 min) The official devroom schedule (along with the accepted talks) will be announced on December 15 on the devroom's mailing list [3] and the speakers will be notified via e-mail. The schedule will also be published on the FOSDEM website. You are invited to send any other suggestions for what you want to see or do at the devroom to the list. We will also use this list to organize the traditional devroom dinner that will happen on the first day of FOSDEM. About the devroom Since the first Microkernel devroom at FOSDEM 2012, this devroom has been part of each following FOSDEM. The focus gradually widened to include component-based operating systems. By now it has become a somewhat institutionalized tradition for the community to meet there; to this date over a dozen projects have participated in one way or another. Each of the projects face similar challenges but come up with partially different solutions. Therefore, the goal of the devroom is to bring the various projects together, let them exchange ideas, cross-pollinate and socialize. Social events It also has become a habit that the microkernel projects dine together somewhere in Brussels. The year 2020 will not be any different, so there is going to be a dinner on Saturday night. We try place a reservation, so we will inform you about the exact location and time later. Consult the FOSDEM web and other projects for additional social events such as the famous FOSDEM-organized Friday Beer Event and the FOSDEM-arranged free sightseeing tours for spouses. About FOSDEM FOSDEM is a two-day event organised by volunteers to promote the widespread use of free and open source software. Taking place in the beautiful city of Brussels (Belgium), FOSDEM is widely recognised as the best such conference in Europe. FOSDEM covers a wide spectrum of free and open source software projects, and offers a platform for people to collaborate. To this end, FOSDEM has set up developer rooms (devrooms) with network/internet connectivity and projectors where teams can meet and showcase their projects. Devrooms are a place for teams to discuss, hack and publicly present latest directions, lightning talks, news and discussions. Besides developer rooms, FOSDEM also offers main tracks, lightning talks, certification exams and project stands. Every year, FOSDEM hosts more than 5000 developers at the ULB Solbosch campus. Participation and attendance is totally free, though the organisers gratefully accept donations and sponsorship. No registration necessary. Important dates recap * 2019-12-01: Deadline for submissions * 2019-12-15: Schedule published and speakers notified of acceptance * 2020-02-01: Devroom Dinner (details to be announced) * 2020-02-01/2020-02-02: The devroom takes places (check the schedule) Links [1] https://fosdem.org/ [2] https://penta.fosdem.org/submission/FOSDEM20 [3] https://lists.fosdem.org/listinfo/microkernel-devroom

1 0

depot_autopilot, log/serial, docker and reboots
by Roman Iten 03 Oct '19

03 Oct '19

Hello For continuous testing, I have a docker container in which the depot_autopilot run script is executed. For ARM targets, I include `log/serial` which executes `picocom`. It works like a charm until the point where the run script reboots the target and tries to reconnect to the serial port which is still busy. `ps` reaveals that picocom is still running, although it should have been killed by then. Please note that this only happens when the run script is executed within a docker container... After tinkering around with it, I came up with this patch [1]. It works for me when executing the run script "directly" as well as within the docker container. But to be honest, I don't understand why (...it's only required in a docker environment). I'd feel better if someone can confirm that the patch is reasonable or how else to solve the problem. Thanks, Roman [1] https://github.com/rite/genode/commit/c4c7bf56230d18480d672ba432d6958ff72ec…

1 0

Thread switching in Genode/seL4 and registers and utcb access problem
by Alexander Tormasov 27 Sep '19

27 Sep '19

I am trying to get working getcontext/setcontext/makecontext prototype on seL4/Genode (I can’t use anything except seL4 in this moment due to some reasons). I need both for x86_64 and aarm64 arch. I started from x86. So, question one. May be someone know kind of rough implementation for user-space context switching? I read information that this is not implemented yet in the main genode - but may be some projects does this already? Problem 2. When I start trying to make a fast solution and try to read registers and some info from low level physical seL4 thread using seL4_TCB_ReadRegisters I found that: In returned successfully data rip register is always 0 for current thread, tcb selector myself.native_thread().tcb_sel also 0, and rsp = 0x13! Probably I can’t read myself? Problem 3. I try to take address of IPC buffer bounded to utcb() field of Genode::Thread using code below. It successfully compiled and linked. Anyway, in attempt to run the program I found the following error in log: [init -> test-go] Error: LD: jump slot relocation failed for symbol: 'Genode::Thread::utcb()’ While access for similar fields in the same Thread structure successfully works! Eg Name name() const; can be printed, native_thread() also give results. I even found in the .o file the name of field (function technically) marked as U , and literally the same name mangled in the sym file for ld.lib.so compiled: 000000000003a09a T _ZN6Genode6Thread4utcbEv genode/repos/base/lib/symbols/ld:_ZN6Genode6Thread4utcbEv T How to fix this? // take info about genode thread Thread &myself = *Thread::myself(); log("myself ", &myself, " size ", sizeof(myself)); addr_t const ipc_buffer = reinterpret_cast<addr_t>(myself.utcb()); log(" name ",myself.name(), " sb ", myself.stack_base(), " svb ", myself.stack_area_virtual_base(), " tcb ", (addr_t)myself.native_thread().tcb_sel); seL4_IPCBuffer &ipc_buffer = *reinterpret_cast<seL4_IPCBuffer *>(myself.utcb()); Sincerely, Alexander Tormasov・

4 9

Sculpt Hanging On New ThinkPad
by John J. Karcher 25 Sep '19

25 Sep '19

Hello, I recently got a new mid-range ThinkPad, which I would love to use as a Genode "daily driver". As you can imagine, one of the first things I did was to try to boot up a Sculpt USB stick. (I tried the 19.07 image, and built a fresh image straight from GitHub, both with the same result.) The system boots into Leitzentrale, with the Manager window, log area, and even component graph all displaying. But then it freezes, not accepting keyboard or mouse input. (It may be related to the USB controller, because 1) the USB stick drive either shows a size of 0 bytes or doesn't display at all, and 2) moving the mouse while Genode is starting seems to cause the system to freeze before Leitzentrale is displayed.) Does anyone have any thoughts on this? Is there a diagnostic tool I can run to give more useful info? I will be happy to give more details on the hardware in the appropriate forum. Should I open a GitHub issue? Thanks! -- John J. Karcher devuser(a)alternateapproach.com

2 5

Why application request RAM quota from parent even if it is enough?
by Alexander Tormasov 19 Sep '19

19 Sep '19

I am trying to start Go application in genode/sel4, 19.08. Now it try to alloc 544Mb Ram (standard initialization approach for reservation via mmap - instead it really alloc space using libc malloc inside mmap() ). So, I have 3 gb ram VM, and ram quota for application is 2 gb. I see that it just plain hangs on the response in void resource_request(Resource_args const &args), from expanding_parent_client.h Any suggestions? here it hang in _wait_for_resource_response: /* * Issue resource request */ Parent_client::resource_request(args); /* * Block until we get a response for the outstanding resource * request. */ if (_state == BLOCKING_DEFAULT) _wait_for_resource_response(); } My run script: build { core init timer lib/libc_noux test/go_app } create_boot_directory install_config { <config verbose="yes" ld_verbose="yes"> <parent-provides> <service name="ROM"/> <service name="LOG"/> <service name="RM"/> <service name="CPU"/> <service name="PD"/> <service name="IRQ"/> <service name="IO_MEM"/> <service name="IO_PORT"/> </parent-provides> <default-route> <any-service> <any-child/> <parent/> </any-service> </default-route> <default caps="2200"/> <start name="timer"> <resource name="RAM" quantum="1M"/> <provides><service name="Timer"/></provides> </start> <start name="test-go" caps="1500"> <resource name="RAM" quantum="2G"/> <config verbose="yes" ld_verbose="yes" stdin="/null" stdout="/log" stderr="/log"> </config> </start> </config> } build_boot_image { core init timer ld.lib.so libc.lib.so libm.lib.so posix.lib.so libc_noux.lib.so vfs.lib.so test-go } Log: ... 2747 MiB RAM and 261141 caps assigned to init Warning: void Genode::Rpc_cap_factory::free(Genode::Native_capability) not implemented - resources leaked: 0x1 Warning: void Genode::Rpc_cap_factory::free(Genode::Native_capability) not implemented - resources leaked: 0x2 [init] 0x40000000 .. 0x4fffffff: stack area [init] 0x30000 .. 0x197fff: ld.lib.so [init] parent provides [init] service "ROM" [init] service "LOG" [init] service "RM" [init] service "CPU" [init] service "PD" [init] service "IRQ" [init] service "IO_MEM" [init] service "IO_PORT" [init] child "timer" [init] RAM quota: 776K [init] cap quota: 2168 [init] ELF binary: timer [init] priority: 0 [init] provides service Timer [init] child "test-go" [init] RAM quota: 2096904K [init] cap quota: 1468 [init] ELF binary: test-go [init] priority: 0 Warning: void Genode::Rpc_cap_factory::free(Genode::Native_capability) not implemented - resources leaked: 0x4 Warning: void Genode::Rpc_cap_factory::free(Genode::Native_capability) not implemented - resources leaked: 0x8 [init -> timer] 0x40000000 .. 0x4fffffff: stack area [init -> timer] 0x30000 .. 0x197fff: ld.lib.so [init] child "timer" announces service "Timer" [init -> test-go] 0x40000000 .. 0x4fffffff: stack area [init -> test-go] 0x30000 .. 0x197fff: ld.lib.so [init -> test-go] 0x12f8000 .. 0x1492fff: libc.lib.so [init -> test-go] 0x1493000 .. 0x1503fff: vfs.lib.so [init -> test-go] 0x1504000 .. 0x153bfff: libm.lib.so [init -> test-go] mmap addr=0xc000000000 len =567472562176 prot=0 flags=4098 libc_fd=-1 offset=0 [init -> test-go] [init -> test-go] resource_request: ram_quota=567472578560

5 12

Genode 19.08 demo on seL4/x86 build failing
by Adam T. Wiethuechter 16 Sep '19

16 Sep '19

Hi everyone, It's been a long while since I have messed with Genode and a lot (of really good things) have happened since. I can't wait to get more into the system again (and finally play with Sculpt). To start I'm trying to building the demo for x86 systems (I am targeting a APU2D4 system from PC.Engines) with seL4 as the kernel. Below is what I have run to setup and build the system (on Ubuntu 18.04.1 LTS): ``` sudo apt install make libsdl-dev tclsh expect qemu xorriso e2tools byacc autoconf2.64 autogen bison flex subversion g++ git gperf libxml2-utils xsltproc gdisk texinfo gprbuild gnat cd genode-19.08/ ./tool/tool_chain x86 ./tool/ports/prepare_port sel4 ./tool/depot/create genodelabs/pkg/x86_64/drivers_interactive-linux genodelabs/bin/x86_64/base-sel4-x86 genodelabs/bin/x86_64/demo genodelabs/bin/x86_64/global_keys_handler genodelabs/bin/x86_64/init genodelabs/bin/x86_64/nit_focus genodelabs/bin/x86_64/nitpicker genodelabs/bin/x86_64/report_rom genodelabs/bin/x86_64/rom_filter CROSS_DEV_PREFIX=/usr/local/genode/tool/19.05/bin/genode-x86- ./tool/ports/prepare_port grub2 ./tool/create_builddir x86_64 cd build/x86_64/ vim etc/build.conf make init make clean make run/demo ``` Note that I updated "etc/build.conf" so that 'KERNEL=sel4', 'BOARD=linux', parallel build is enabled and added 'RUN_OPT += --include image/iso' The "make init" command completes without error. The "make run/demo" however spits out this: ``` including /home/adam/genode-19.08/tool/run/boot_dir/sel4 including /home/adam/genode-19.08/tool/run/image/iso including /home/adam/genode-19.08/repos/os/run/demo.run building targets: app/status_bar test/nitpicker spawn make app/status_bar test/nitpicker make[1]: Entering directory '/home/adam/genode-19.08/build/x86_64' checking library dependencies... Library ldso-startup COMPILE startup.o MERGE ldso-startup.lib.a Library ld CONVERT ld.symbols.s ASSEMBLE ld.symbols.o MERGE ld.abi.so Library base MERGE base.lib.a Program test/nitpicker/testnit CONVERT binary_default.tff.o Program app/status_bar/status_bar COMPILE test.o COMPILE main.o LINK testnit LINK status_bar make[1]: Leaving directory '/home/adam/genode-19.08/build/x86_64' genode build completed checking configuration syntax CHECK init building targets: kernel/sel4 spawn make kernel/sel4 make[1]: Entering directory '/home/adam/genode-19.08/build/x86_64' checking library dependencies... Library-description file kernel-sel4-linux.mk is missing var/libdeps:23: *** missing separator. Stop. Makefile:286: recipe for target 'gen_deps_and_build_targets' failed make[1]: *** [gen_deps_and_build_targets] Error 2 make[1]: Leaving directory '/home/adam/genode-19.08/build/x86_64' Error: Genode build failed Makefile:323: recipe for target 'run/demo' failed make: *** [run/demo] Error 252 ``` Just to be sane I also tried using the HW kernel (after grabbing the needed things) getting even weirder but similar results: ``` cd genode-19.08/ ./tool/depot/create genodelabs/bin/x86_64/base-hw-pc CROSS_DEV_PREFIX=/usr/local/genode/tool/19.05/bin/genode-x86- cd build/x86_64 make KERNEL=hw BOARD=linux run/demo including /home/adam/genode-19.08/tool/run/power_on/linux including /home/adam/genode-19.08/tool/run/log/linux including /home/adam/genode-19.08/tool/run/boot_dir/hw including /home/adam/genode-19.08/tool/run/image/iso including /home/adam/genode-19.08/repos/os/run/demo.run building targets: app/status_bar test/nitpicker spawn make app/status_bar test/nitpicker make[1]: Entering directory '/home/adam/genode-19.08/build/x86_64' checking library dependencies... Library ldso-startup COMPILE startup.o MERGE ldso-startup.lib.a Library ld CONVERT ld.symbols.s ASSEMBLE ld.symbols.o MERGE ld.abi.so Library base MERGE base.lib.a COMPILE test.o Program app/status_bar/status_bar CONVERT binary_default.tff.o Program test/nitpicker/testnit COMPILE main.o LINK testnit LINK status_bar make[1]: Leaving directory '/home/adam/genode-19.08/build/x86_64' genode build completed checking configuration syntax CHECK init building targets: bootstrap/hw core/hw spawn make bootstrap/hw core/hw make[1]: Entering directory '/home/adam/genode-19.08/build/x86_64' checking library dependencies... Library-description file bootstrap-hw-linux.mk is missing Library-description file core-hw-linux.mk is missing make[1]: Leaving directory '/home/adam/genode-19.08/build/x86_64' genode build completed error copying "bin/core-hw-linux.o": no such file or directory while executing "file copy -force bin/core-hw-[board].o [run_dir]/genode/core-hw.o " (procedure "run_boot_dir" line 27) invoked from within "run_boot_dir $binaries" (procedure "build_boot_image" line 34) invoked from within "build_boot_image { status_bar testnit launchpad.config }" (file "/home/adam/genode-19.08/repos/os/run/demo.run" line 216) invoked from within "source $include_name" ("foreach" body line 6) invoked from within "foreach include_name [get_cmd_arg --include ""] { # first check if the include name is absolute if {[string first "/" $include_name] == 0} { puts ..." (file "/home/adam/genode-19.08/tool/run/run" line 1006) Makefile:323: recipe for target 'run/demo' failed make: *** [run/demo] Error 1 ``` At this point I think something is up with my environment but I have no idea where to begin. Any pointers? Thanks and happy weekend everyone! -- 73's, Adam Wiethuechter, Jr Software Engineer Critical Technologies Inc. (CTI) Desk: (315)-793-0248 x157 Cell: (315)-552-4298 <adam.wiethuechter(a)critical.com>

3 12

Re: Why application request RAM quota from parent even if it is enough?
by ttcoder＠netcourrier.com 09 Sep '19

09 Sep '19

Hi Norman, yes you did answer, and how extensively so I've added a solid link to your answer in my online notes (chiselapp/genode-book), for me to dig deeper in the future. For now it's a place-holder but maybe it could become a useful (actionable) summary for others to use in the future. Truth be told, libav memory leaks do not seem to present a problem at this stage -- setting a "tight" memory quota and leaving my app running for a while, it does not run into the resource-request case, so the leaks are probably small or non-existant. So between that, and the options you described for handling the problem should it surface, I'd say I'm probably "covered" and won't worry about it. FWIW, my Genode work will probably focus on drivers next, specifically AHCI and (more importantly) HDA. It's not sexy work (actually I kinda hate working on drivers) but not having HDA output on actual stations would be a deal breaker so I'll post more to the concerned ticket on github/genode in the future. The stability situation on Haiku has improved, but I still want to keep working on this and make TTS/CC dual platform regardless (and commit more of my code to the public repo). Cedric > I think all options should be covered by the dynamic init construction > described above. The approach can naturally be extended by letting the > child "report" additional (higher-level) information about its internal > state. The manager may take those reports into account also. E.g., the > Sculpt manager consumes the reports generated by drivers and part_block > instances to find the Genode partition.

1 0

Genode on PC Engines apu2c4 with coreboot
by Sid Hussmann 09 Sep '19

09 Sep '19

Dear Genodians, I'm trying to enable Genode on the apu2c4. I successfully could run the test-pci component using branch [1] based on Genode 17.11: However, using the genodelabs/master branch results in a ACPI parsing error: ´[init -> platform_drv] Error: ACPI report parsing error.´ I set the report_rom to verbose and I noticed following differences: # Working version on apu2c4 [1]: ´´´ Genode 17.11-103-gd0028480b <local changes> 4039 MiB RAM and 63253 caps assigned to init [init -> test-pci] --- Platform test started --- [init -> acpi_drv] Found MADT [init -> acpi_drv] MADT IRQ 0 -> GSI 2 flags: 0 [init -> acpi_drv] MADT IRQ 9 -> GSI 9 flags: 15 [init -> acpi_report_rom] report 'acpi_drv -> acpi' [init -> acpi_report_rom] <acpi> [init -> acpi_report_rom] <fadt features="0x3c5a5" reset_type="0x1000801" reset_addr="0xcf9" reset_value="0x6"/> [init -> acpi_report_rom] <irq_override irq="9" gsi="9" flags="0xf"/> [init -> acpi_report_rom] <irq_override irq="0" gsi="2" flags="0x0"/> [init -> acpi_report_rom] <routing gsi="0x2b" bridge_bdf="0x15" device="0x0" device_pin="0x3"/> [init -> acpi_report_rom] <routing gsi="0x2a" bridge_bdf="0x15" device="0x0" device_pin="0x2"/> [init -> acpi_report_rom] <routing gsi="0x29" bridge_bdf="0x15" device="0x0" device_pin="0x1"/> ... [init -> acpi_report_rom] <routing gsi="0x2c" bridge_bdf="0xc0" device="0x1" device_pin="0x0"/> [init -> acpi_report_rom] </acpi> [init -> test-pci] 0:0.0 class=0x600 vendor=0x1022 (unknown) device=0x1566 [init -> test-pci] 0:2.0 class=0x600 vendor=0x1022 (unknown) device=0x156b ... ´´´ # Broken version on apu2c4 (current master): ´´´ Genode 19.08 <local changes> 4027 MiB RAM and 63253 caps assigned to init [init -> test-pci] --- Platform test started --- [init -> acpi_drv] Found MADT [init -> acpi_drv] MADT IRQ 0 -> GSI 2 flags: 0 [init -> acpi_drv] MADT IRQ 9 -> GSI 9 flags: 15 [init -> acpi_drv] XSDT OEM 'CORE ', table id 'COREBOOT', revision 0, creator 'CORE' (0) [init -> acpi_report_rom] report 'acpi_drv -> acpi' [init -> acpi_report_rom] <acpi> [init -> acpi_report_rom] <root_bridge bdf="0xc0"/> [init -> acpi_report_rom] <irq_override irq="9" gsi="9" flags="0xf"/> [init -> acpi_report_rom] <irq_override irq="0" gsi="2" flags="0x0"/> [init -> acpi_report_rom] <routing gsi="0x2b" bridge_bdf="0x15" device="0x0" device_pin="0x3"/> [init -> acpi_report_rom] <routing gsi="0x2a" bridge_bdf="0x15" device="0x0" device_pin="0x2"/> [init -> acpi_report_rom] <routing gsi="0x29" bridge_bdf="0x15" device="0x0" device_pin="0x1"/> ... [init -> acpi_report_rom] <routing gsi="0x2c" bridge_bdf="0xc0" device="0x1" device_pin="0x0"/> [init -> acpi_report_rom] </acpi> [init -> platform_drv] Error: ACPI report parsing error. [init -> acpi_drv] SMBIOS table (entry point: 0x163ad0 structures: 0xdffd7020) [init -> platform_drv] Error: Uncaught exception of type 'int' [init -> platform_drv] Warning: abort called - thread: ep [init -> acpi_report_rom] report 'acpi_drv -> smbios_table' [init -> acpi_report_rom] _SM_b▒ ´´´ # on QEMU (current master): ´´´ Genode 19.08 <local changes> 471 MiB RAM and 63253 caps assigned to init [init -> test-pci] --- Platform test started --- [init -> acpi_drv] Found MADT [init -> acpi_drv] MADT IRQ 0 -> GSI 2 flags: 0 [init -> acpi_drv] MADT IRQ 5 -> GSI 5 flags: 13 [init -> acpi_drv] MADT IRQ 9 -> GSI 9 flags: 13 [init -> acpi_drv] MADT IRQ 10 -> GSI 10 flags: 13 [init -> acpi_drv] MADT IRQ 11 -> GSI 11 flags: 13 [init -> acpi_drv] Found MCFG [init -> acpi_drv] MCFG BASE 0xb0000000 seg 0x0 bus 0x0-0xff [init -> acpi_drv] RSDT OEM 'BOCHS ', table id 'BXPCRSDT', revision 1, creator 'BXPC' (1) [init -> acpi_report_rom] report 'acpi_drv -> acpi' [init -> acpi_report_rom] <acpi> [init -> acpi_report_rom] <root_bridge bdf="0x0"/> [init -> acpi_report_rom] <bdf start="0" count="65536" base="0xb0000000"/> [init -> acpi_report_rom] <irq_override irq="11" gsi="11" flags="0xd"/> [init -> acpi_report_rom] <irq_override irq="10" gsi="10" flags="0xd"/> [init -> acpi_report_rom] <irq_override irq="9" gsi="9" flags="0xd"/> [init -> acpi_report_rom] <irq_override irq="5" gsi="5" flags="0xd"/> [init -> acpi_report_rom] <irq_override irq="0" gsi="2" flags="0x0"/> [init -> acpi_report_rom] </acpi> [init -> platform_drv] ECAM/MMCONF range 00:00.0-ff:1f.7 - addr [00000000b0000000,00000000c0000000) [init -> acpi_drv] SMBIOS table (entry point: 0x165710 structures: 0xf5730) [init -> platform_drv] Root bridge: 00:00.0 [init -> acpi_report_rom] report 'acpi_drv -> smbios_table' [init -> acpi_report_rom] _SM_W [init -> test-pci] 0:0.0 class=0x600 vendor=0x8086 (Intel) device=0x29c0 [init -> test-pci] 0:1.0 class=0x300 vendor=0x1234 (unknown) device=0x1111 ... ´´´ Cherry-picking from [1] to the master branch didn't help. On QEMU I noticed a ´bdf´ node in the acpi_report. ´platform_drv´ is expecting this node. The ´bdf´ node is written in ´Acpi::generate_report()´ but only if there is an entry in the ´Pci_config_space´ list. The only function that inserts something to that list is ´Table_wrapper::parse_mcfg()´, which is called from ´Acpi_table::_parse_tables()´ in case one of the tables has the "MCFG" signature. However, none of the tables seem to have that signature. And now I'm lost. How do I move on? Cheers, Sid [1] https://github.com/chelmuth/genode/commits/cobalt

3 6

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users