Hi! > I gave the user a debugging patch, but they reported that they > can no longer trigger the issue with 2.6.31.1 > > See: > > http://marc.info/?l=linux-ide&m=125469615425454&w=4 > > Maybe that's enough to close this, I dunno. I'm the user with the debugging patch, I'd say no, don't close it. Even though on my first tests I had the computer to crash the two weekends I had tested, it seems that crashing on weekend was only luck and seems that having the bug appear is more difficult than I had thought. So... my comments saying that 2.6.31.1 seemed ok are probably wrong (I have read the .1 changelog and there is an ata patch, but probably unrelated). It is true that I had 2.6.31.1 running for a whole week without it crashing, but seems that crashing it may need more time. I'm now back to the 2.6.31 with the patch to debug it (3 days uptime) in order to gather more info and after I get the info from 2.6.31 I'd test 3.6.31.latest or even 2.6.32whatever in case you find that better. Regards... -- Manty/BestiaTester -> http://manty.net -- To unsubscribe from this list: send the line "unsubscribe kernel-testers" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
