Just to add some more notes, I've had the crash happen a few more times and investigated more closely what's going on. I enabled the wireless LED a few days ago and I've noticed that when the machine hangs, the LED is on and stays on, so I am tempted to guess that it's hanging inside a wireless send/receive type function.
In terms of SysRq commands, there's not much that seems to work - I tried to kill X, dump some stats and do a "safe" sync,unmount,reboot, but the only one that works is the reboot one. I would hazard a guess that this is because the kernel is busy waiting for the wireless driver to finish doign whatever its doing. However, all of this makes it extraordinarily difficult to track down what's really going on, especially with no serial port. Can anyone think of some other way(s) we can collect information about what failed? -- [madwifi] Semi-random system lockups in Dapper https://launchpad.net/bugs/37773 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
