Comment 11 for bug 295091

@gbon -- thanks for testing that.

From the two sets of photos you have attached the behaviour looks the same. Its pretty clear something occurs when trying to register a link in sysfs, the initial panics in both case are EIP sysfs_create_link. We later get other softlockups trying take a lock in the same routine, so we clearly failed in sysfs_create_link with some lock held and it is now lost. We can ignore the later panics as they are mearly victims, their call chains are not particularly interesting.

Sadly in both cases we do not have the initial lines of the first dump (I am assuming it zooms past rather fast). It is this part of the output which is most important (of course). If you do get a chance to try and reproduce this could you add the "pause_on_oops=120" (to get a two minute pause when the first panic occurs) and then you could attempt to scroll up with Shift-PgUp and see if you can get a picture of the start of the panic.

Even if you are not able to test again, It would be useful to have dmesg output, lsmod output, and lspci -nnvv output from the system when working ok on Intrepid so we can see what this machine has in it.