| To: | linux-xfs@xxxxxxxxxxx |
|---|---|
| Subject: | Re: xfs BUG at page_buf_io.c:1061 |
| From: | Keith Owens <kaos@xxxxxxxxxxxxxxxxx> |
| Date: | Thu, 05 Oct 2000 07:41:54 +1100 |
| In-reply-to: | Your message of "Wed, 04 Oct 2000 10:19:09 CDT." <39DB4A6C.69668AA2@xxxxxxxxxxx> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
On Wed, 04 Oct 2000 10:19:09 -0500, Russell Cattelan <cattelan@xxxxxxxxxxx> wrote: >Yes I hit this one yesterday... unfortunately it was on a laptop >machine without a serial console connected. kdb supports logging of its output via syslog, set LOGGING=1 and all new output goes via syslog. The data is written to disk when you exit kdb via 'go'. Since the log buffers have limited size, only the last 8K or so iof output is saved. And obviously your kernel needs to be capable of writing to disk after the oops. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Lilo hanging in XFS development tree, Steve Lord |
|---|---|
| Next by Date: | BUG 803884 - double-fault with HIGHMEM, dxm@xxxxxxxxxxxx |
| Previous by Thread: | Re: xfs BUG at page_buf_io.c:1061, Russell Cattelan |
| Next by Thread: | BUG 803884 - double-fault with HIGHMEM, dxm@xxxxxxxxxxxx |
| Indexes: | [Date] [Thread] [Top] [All Lists] |