diff options
author | Jesper Juhl <jesper.juhl@gmail.com> | 2005-11-07 01:01:03 -0800 |
---|---|---|
committer | Linus Torvalds <torvalds@g5.osdl.org> | 2005-11-07 07:53:54 -0800 |
commit | 62a07e6e9e93eda88a6eeb5009fc46d44ca60281 (patch) | |
tree | 6e5a0891a46b1d9864d5591a5961c63e1b818bea /Documentation/video4linux | |
parent | 55032eacdb3acf54f5ba2e4dd9205db2c5c0bce2 (diff) |
[PATCH] ksymoops related docs update
Update ksymoops related documentation to reflect current 2.6 reality.
Signed-off-by: Jesper Juhl <jesper.juhl@gmail.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'Documentation/video4linux')
-rw-r--r-- | Documentation/video4linux/bttv/README.freeze | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/Documentation/video4linux/bttv/README.freeze b/Documentation/video4linux/bttv/README.freeze index 51f8d4379a94..4259dccc8287 100644 --- a/Documentation/video4linux/bttv/README.freeze +++ b/Documentation/video4linux/bttv/README.freeze @@ -27,9 +27,9 @@ information out of a register+stack dump printed by the kernel on protection faults (so-called "kernel oops"). If you run into some kind of deadlock, you can try to dump a call trace -for each process using sysrq-t (see Documentation/sysrq.txt). ksymoops -will translate these dumps into kernel symbols too. This way it is -possible to figure where *exactly* some process in "D" state is stuck. +for each process using sysrq-t (see Documentation/sysrq.txt). +This way it is possible to figure where *exactly* some process in "D" +state is stuck. I've seen reports that bttv 0.7.x crashes whereas 0.8.x works rock solid for some people. Thus probably a small buglet left somewhere in bttv |