https://bugzilla.kernel.org/show_bug.cgi?id=14831 --- Comment #42 from starlight@xxxxxxxxxxx 2010-08-30 16:42:08 --- Kashyap, Thank you for looking at this problem in depth. Since it is different, I certainly can create a new bugzilla for it. I'll do that in the next day or so. Do you have any ideas about what might be the cause? One thing that crosses my mind is that the drives here are not enterprise Seagate Constellation drives, but are Seagate Momentus drives that have more aggressive power saving features intended for laptops. We chose them because at the time they were much less expensive and the sequential read/write performance was the same. Now the price differential is much smaller and we would have gone with Constellations. Is there any chance that the Momentus drives require the 10 second command time-out in the LSI BIOS config to be extended? This is just a random idea. The drives were all active at the time of the event and so would not have been in power saving mode or been responding slowly to commands. Another theory I have is that there might be a memory leak in the firmware and that when all free memory is exhausted, the controller "goes insane". Is such a memory leak something that would be apparent in the tracing? Finally should mention that I believe the configuration is unusual. A large, identical partition on the eight drives is configured as a software RAID0 volume. I doubt that many people configure systems this way. It might be stressing the firmware/software in a unique fashion. Thanks, David At 03:18 PM 8/30/2010 +0000, bugzilla-daemon@xxxxxxxxxxxxxxxxxxx wrote: >https://bugzilla.kernel.org/show_bug.cgi?id=14831 > >I have taken a deep look of all the available logs for below >configuration. > >In summary, this can be a completely different issue. Can we move this issue to >new bugzilla, so that I can have a fresh look on it ? > >Thanks, Kashyap -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
