-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >>>>> "Stephen" == Stephen C Tweedie <sct@redhat.com> writes: Stephen> However, it would be useful to see the whole call trace, Stephen> because this particular entry looks as if the Stephen> DAC960_ProcessRequest entry is simply the result of a recent Stephen> interrupt, and we're not actually in that call path at the Stephen> moment (the DAC960 address has simply been left behind on the Stephen> stack so is picked up by the trace output.) >> ok. Where would I be able to get that? I do have the complete sysrq >> output of process traces... Stephen> That would be useful, yes. ok. Kinda large to send to the list... it's avail at: http://www.scrye.com/~kevin/ext3-sysrq.txt Hope it helps. I did have to go and clean the minicom control characters out of it. Hopefully I got them all. Let me know if there is any other information I can gather. Its worth noting that the server has been up using ext2 for the last 8 days... so it's sure looking like ext3 might be triggering the problem. Stephen> Cheers, Stephen kevin -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) Comment: Processed by Mailcrypt 3.5.6 and Gnu Privacy Guard <http://www.gnupg.org/> iD8DBQE9TufT3imCezTjY0ERArE+AKCOWa+dbVp+p6b5/e0SJDSRwFJ1PgCffhrN 57YCYP+GZJpJBEvVWmxTUK8= =ztvg -----END PGP SIGNATURE-----
