On Monday 02 August 2004 12:06, micah nerren wrote: > Hi, > > On Mon, 2004-08-02 at 08:46, Adam Manthei wrote: > > On Mon, Aug 02, 2004 at 07:48:02AM -0700, micah nerren wrote: > > > The system crashes. At the console, there are tons of system > > > calls being listed, and at the bottom of the screen: > > > > > > Code: 39 d0 75 f8 85 c9 74 10 8b 44 24 14 39 d0 74 08 8b 44 24 14 > > > Console Shuts up: > > > pid: 3547, lock_gulmd Not tainted > > > RIP: 0010 > > > > > > > > > So... Any ideas on what may be causing this? > > > > Those "tons of system calls being listed" are really quite useful > > if not necessary to tell you what the problem is. My gut feeling > > is that there is a stack overrun that is happening. > > I could try to post them if anybody would find that useful. I will > write all that down and attempt to post it coherently. Is there any > way to capture that kind of info to a file? The traditional way is to connect a serial cable and direct console output to the serial port. You can then cut and paste the console messages from a nice graphical buffer. Other ways are proposed, such as crash dump to disk and network crash dump, but I don't think any have made it to mainline yet, though patches are available. (More voices asking for it on lkml would help.) Regards, Daniel
