Jeff,
you should not run queries on the table that you are CHECKing. Those queries cause the timeout.
Or upgrade to MySQL-4.1.xx where the timeout is 2 hours.
MySQL/InnoDB data format on disk is the same on Solaris/Sparc and Linux/AMD64. Thus, when you have the Solaris database ok, it is simple to move it to the Opteron.
Interesting that the Opteron box was badly corrupt while the Solaris box was ok. That suggests that fsync is badly broken in the Linux-2.4.21-27.ELsmp/Opteron box while Solaris/Sparc is ok. That strengthens my guess that commercial Unix computers are more carefully designed than Linux computers.
"
InnoDB: Page lsn 12 4083660083, low 4 bytes of lsn at page end 4180158248
InnoDB: Also the page in the doublewrite buffer is corrupt.
"
The corruption is probably that the start of the page is from an earlier time than the tail of the page.
Have you tried to use hdparm or a proprietary program of the disk vendor to switch off write caching?
Best regards,
Heikki
Oracle Corp./Innobase Oy
InnoDB - transactions, row level locking, and foreign keys for MySQL
InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up MyISAM tables
http://www.innodb.com/order.php