http://bugzilla.kernel.org/show_bug.cgi?id=9994 ------- Comment #6 from jan.fikar@xxxxxx 2008-04-11 02:40 ------- The latest results are not very good... Bisecting and waiting for at least 24 hours leads to a different wrong result: f435a91e66e7776f0c73fca5af3cb87c61130ed6 is first bad commit commit f435a91e66e7776f0c73fca5af3cb87c61130ed6 Author: Ralf Baechle <ralf@xxxxxxxxxxxxxx> Date: Thu Dec 6 17:15:57 2007 +0000 [MIPS] BCM1480: Fix interrupt routing, take 2. Signed-off-by: Ralf Baechle <ralf@xxxxxxxxxxxxxx> :040000 040000 73dbf425d802ab4d4a1c6fd4776df2b9d0086043 0fa229550fa638511ff9f9edde20f0329d650174 M arch Then I tried kernel 2.6.25-rc6 and unfortunately I still see the error, although it seems to be triggered even less often. One time I saw a single DMA timeout in 4 days without disabling DMA. Second time after three days and last time I saw the real problem, so a lot of timeouts, resets and disabling DMA on hda during two days. Is there a possibility to try only atiixp related patches instead of the bisecting? If I need to wait let's say 5 days, bisecting would take in the worst case two months :( -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. -- To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
