I just got another oops while trying to cp from my md/raid5 array (2 of 3 sata drives) to another sata drive on the same controller. This time, though, it said there's a bug in timer.c, line 405, and that the stack's garbage. I'm thinking it has nothing to do with timer.c, and something in md or libata is chomping all over the kernel.
It's odd that no one else is experiencing problems. I read a post where someone was sucessfully using a mandrake 2.6.8.1 kernel, with the same controller (promise tx4) and raid5. I suppose my controller card could be faulty, but it's odd that drives on the controller w/o raid seem to be doing alright.
I'm going to try a 2.4 kernel so I might be able to back up my array before things get really hairy. I should probably also ping Neil Brown or whoever the current md maintainer is. I'll continue to post findings.
Will - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
