Re: lowlatency-2.2.14-B1 + 2.2.14aa7 fixes crash, but...

From: Artur Skawina (skawina@geocities.com)
Date: Tue Feb 15 2000 - 17:00:39 EST


William Montgomery wrote:
>
> at making sense of these stack traces and attempted to resolve the
> reasonable looking addresses to symbol names from System.map.
> The output of the decoded stacktrace follows:
>
> ksmod PID=2895 : PID of stuck process "/bin/sync"
> EIP: [<c010f44f>] : c010f2fc T schedule
> ESP: c6e67f34 SavedPC: 00000249
>
> [<c6e67f58>]
> [<fffffc18>]
> [<c022c000>] : c022c000 D init_task_union
> [<c6e67f78>]
> [<c2556420>]
> [<c0242ee8>] : c0242c80 b all_requests
> [<c022c000>] : c022c000 D init_task_union
> [<c0239c00>] : c0239c00 d aligned_data
> [<c6e66000>]
> [<c0124486>] : c01243e8 T __wait_on_buffer
> [<c25563c0>]
> [<c6e66000>]
> [<c6e67f78>]
> [<c6e67f78>]
> [<c6e66000>]
> [<c255644c>]
> [<c012456d>] : c01244c0 t sync_buffers
> [<c2556420>]
> [<c2556420>]
> [<c01247c3>] : c012479c T fsync_dev
> [<c6e66000>]
> [<c01247cf>] : c01247c8 T sys_sync
> [<c0107b7c>] : c0107b48 T system_call
>
> -------------------
> Does this look reasonable?

yes.

> How do I interpret this?

sync()->fsync_dev()->sync_buffers()->wait_on_buffer()

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Tue Feb 15 2000 - 21:00:30 EST