| To: | Andrew Klaassen <ak@xxxxxxx> |
|---|---|
| Subject: | Re: Oops - 2.4.2-SGI_XFS_1.0.1_PR1 |
| From: | Keith Owens <kaos@xxxxxxxxxxxxxxxxx> |
| Date: | Tue, 26 Jun 2001 11:46:12 +1000 |
| Cc: | linux-xfs@xxxxxxxxxxx |
| In-reply-to: | Your message of "Mon, 25 Jun 2001 19:47:43 -0400." <20010625194743.A5726@xxxxxxxxxxx> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
On Mon, 25 Jun 2001 19:47:43 -0400, Andrew Klaassen <ak@xxxxxxx> wrote: >Okay - I've got an oops, and this time I've got a serial console >attached. There's a pretty little kdb prompt sitting there >waiting for me. > >What do I do for maximum debugging pleasure? Capture the serial console output. 'bt' to trace the failing task is probably all you need at this stage. For an oops it is usually only the current task that is interesting. For loops and hangs, 'ps' and 'bta' are useful to get backtrace for all processes. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: unkillable process, Keith Owens |
|---|---|
| Next by Date: | Re: unkillable process, Alan Eldridge |
| Previous by Thread: | Oops - 2.4.2-SGI_XFS_1.0.1_PR1, Andrew Klaassen |
| Next by Thread: | Re: Oops - 2.4.2-SGI_XFS_1.0.1_PR1, Andrew Klaassen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |