Months ago, I had issues with the AHCI driver not working with part_blk. I tested a simple scenario with AHCI and a non-writing version of test-blk-cli. It didn't work (test-blk-cli-nowrite didn't give any output), but the AHCI driver gave its normal output. I tested a slightly modified config using rom_blk instead of ahci, and it worked just fine. Any ideas about what might be wrong?
After further investigation, I found that the AHCI driver is stalling on _irq_rec.wait_for_signal(); (ahci_device_base.h). This suggests that the interrupt mechanism may be at fault. Where should I go from here?
On Wed, Apr 29, 2015 at 3:33 PM, Nobody III <hungryninja101@...9...> wrote:
Months ago, I had issues with the AHCI driver not working with part_blk. I tested a simple scenario with AHCI and a non-writing version of test-blk-cli. It didn't work (test-blk-cli-nowrite didn't give any output), but the AHCI driver gave its normal output. I tested a slightly modified config using rom_blk instead of ahci, and it worked just fine. Any ideas about what might be wrong?
By the way, I'm using acpi, and the driver says it supports my acpi table format.
On Wed, Apr 29, 2015 at 10:51 PM, Nobody III <hungryninja101@...9...> wrote:
After further investigation, I found that the AHCI driver is stalling on _irq_rec.wait_for_signal(); (ahci_device_base.h). This suggests that the interrupt mechanism may be at fault. Where should I go from here?
On Wed, Apr 29, 2015 at 3:33 PM, Nobody III <hungryninja101@...9...> wrote:
Months ago, I had issues with the AHCI driver not working with part_blk. I tested a simple scenario with AHCI and a non-writing version of test-blk-cli. It didn't work (test-blk-cli-nowrite didn't give any output), but the AHCI driver gave its normal output. I tested a slightly modified config using rom_blk instead of ahci, and it worked just fine. Any ideas about what might be wrong?
Hello,
On April 30, 2015 12:55:56 AM CEST, Nobody III <hungryninja101@...9...> wrote:
By the way, I'm using acpi, and the driver says it supports my acpi table format.
[...]
On Wed, Apr 29, 2015 at 10:51 PM, Nobody III <hungryninja101@...9...> wrote:
After further investigation, I found that the AHCI driver is stalling
on
_irq_rec.wait_for_signal(); (ahci_device_base.h). This suggests that
the
interrupt mechanism may be at fault. Where should I go from here?
That may be an issue we have from time to time, where the ACPI tables contain just plain wrong interrupt routing information. We investigated the issue and Linux too (when forced into non-MSI mode) stops working on our test hardware.
With Genode 15.05, we plan to release a reimplementation of AHCI driver by Sebastian Sumpf and also introduce a vast amount of changes in our I/O management infrastructure, which will also bring transparent use of MSI for capable devices on base-foc and base-nova. So please stay tuned until end of May.
Regards
-
Christian Helmuth -
Nobody III