> > The 2.6.38.2 kernel still exhibits the same lockups that we see with the > > 2.6.26 kernel. > > Okay. Just to help narrow it down a bit, how does 2.6.32 behave ? > > Thanks. Hi Mark, I have reproduced the issue with the 2.6.32 kernel. In case it is of use, the silicon is rev 09 (i.e. C0 stepping) and I am using gcc 4.4.2 to build the kernel and modules. I am currently inserting tracing into 2.6.38.2 to try to work out what is going on. From mv_write_main_irq_mask I can see that the IRQ for each port is still enabled, even when ports stop responding. I see interrupts generated when I hotplug or unplug disks on ports that are not locked up, but no interrupt is generated at all for the ports that are locked (this is from tracing in asm_do_IRQ in arch/arm/kernel/irq.c) One thing I noticed was that there is no spinlock around the mv_save_cached_regs/mv_edma_cfg in mv_hardreset (unlike mv_port_start and mv_port_stop); why is this? Kind Regards, Bruce Stenning, IndigoVision, b <dot> stenning <at> indigovision <dot> com Latest News at: http://www.indigovision.com/index.php/en/news.html ÿô.nlj·Ÿ®‰†+%ŠË±é¥Šwÿº{.nlj·¥Š{±þ'^þ)íè jg¬±¨ ¶‰šŽŠÝjÿ¾«þG«é¸ ¢·¦j:+v‰¨Šwèm¶Ÿÿþø®w¥þŠà£¢·hšâÿ†Ù
