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 <hungryninja...@gmail.com>
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?
>
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
genode-main mailing list
genode-main@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/genode-main
