On 1 Jun 2009, at 15:08, Chris Ridd wrote: > > On 1 Jun 2009, at 15:02, Chris Ridd wrote: > >> >> On 7 May 2009, at 17:55, John Martin wrote: >> >>> Chris Ridd wrote: >>>> >>>> I can give that a try, but maybe it is worth getting some >>>> diagnostic info first. >>>> >>>>> Does this system have a serial port (ttya)? >>>> >>>> Yes it does. >>>> >>> The original post says the box no longer responds to pings and USB >>> mouse/keyboard >>> activity ceases. Setting the console to the serial port allows >>> debugging of a box >>> stuck at a high priority. >> >> It wedged a couple of times this morning, so I figured I'd set up a >> serial console :-) >> >> The console (minicom running on Linux) seems to be output-only - is >> there any magic required to have an interactive serial console >> *and* an interactive X server? > > It just wedged again with some slight display corruption in a gnome- > terminal running a big "gmake clean". The only thing in the console > is when I logged in: > > --- > canopus console login: Jun 1 14:57:16 canopus gnome-keyring- > daemon[1389]: coulk > --- > > I'm imagine the last char's been overwritten. But the line doesn't > look terribly relevant.
I'm still unsure how to extract extra diagnostics from a wedged system via a serial console. However I have since forced the box to boot this BE (111b) with a 32- bit kernel - it only has 3GB of RAM anyway - and so far things have been fine... Cheers, Chris
