From: Ed Tomlinson <tomlins@cam.org>
To: reiserfs-list@namesys.com
Cc: Chris Mason <mason@suse.com>
Subject: [BUG] tons of logging patches
Date: Fri, 7 Jun 2002 23:32:29 -0400 [thread overview]
Message-ID: <200206072332.29892.tomlins@cam.org> (raw)
Hi,
On pre10-ac2 with your:
01-relocation-3.diff
02-commit_super-8-relocation.diff
03-beta-data-logging-7.diff
Adpated for the O(1) scheduler which required replacing code in two places
in journal.c with yield() and with by slab_in_lru patch, I found this in my log:
Jun 7 07:21:33 oscar kernel: printing eip:
Jun 7 07:21:33 oscar kernel: c016d2ff
Jun 7 07:21:33 oscar kernel: Oops: 0000
Jun 7 07:21:33 oscar kernel: CPU: 0
Jun 7 07:21:33 oscar kernel: EIP: 0010:[flush_commit_list+31/812] Tainted: P
Jun 7 07:21:33 oscar kernel: EFLAGS: 00010286
Jun 7 07:21:33 oscar kernel: eax: 00000000 ebx: 00000000 ecx: db71a124 edx: e2a910d8
Jun 7 07:21:33 oscar kernel: esi: df2ea000 edi: df2ea000 ebp: c99d99c0 esp: dceb3f20
Jun 7 07:21:33 oscar kernel: ds: 0018 es: 0018 ss: 0018
Jun 7 07:21:33 oscar kernel: Process newsplex (pid: 4524, stackpage=dceb3000)
Jun 7 07:21:33 oscar kernel: Stack: 00000580 df2ea000 000e7995 c99d99c0 000e7995 c66ae000 d1ff24a0 dceb2000
Jun 7 07:21:33 oscar kernel: 00000000 00000000 c017102d df2ea000 00000000 00000001 00000000 c99d99c0
Jun 7 07:21:33 oscar kernel: 00000000 c99d9a2c 00000000 00000000 00000000 000149b0 00000000 00001000
Jun 7 07:21:33 oscar kernel: Call Trace: [reiserfs_commit_for_inode+217/228] [reiserfs_sync_file+66/84] [sys_fsync+98/164] [s
ystem_call+51/64]
Jun 7 07:21:33 oscar kernel:
Jun 7 07:21:33 oscar kernel: Code: 8b 6b 2c 68 1f c7 20 c0 e8 4c fc ff ff 8b 43 14 83 c4 04 85
Ed Tomlinson
next reply other threads:[~2002-06-08 3:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-08 3:32 Ed Tomlinson [this message]
2002-06-16 20:54 ` [BUG] tons of logging patches Chris Mason
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200206072332.29892.tomlins@cam.org \
--to=tomlins@cam.org \
--cc=mason@suse.com \
--cc=reiserfs-list@namesys.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.