From: "Anthony R." <russo.lutions@verizon.net>
To: linux-kernel@vger.kernel.org
Subject: kernel BUG at fs/reiserfs/prints.c:339! kernel 2.6.5
Date: Fri, 16 Apr 2004 11:12:10 -0400 [thread overview]
Message-ID: <407FF7CA.3050002@verizon.net> (raw)
Hi,
Using kernel version 2.6.5, Pentium 4 PC,
ReiserFS. While running slocate cron job, the
following errors showed up and the harddrive's
LED remained lit until a hard power cycle. I've been running
2.6.x kernels on this same hardware for months and never
saw this problem before until kernel 2.6.5. I realize it could be a
hardware problem but I want to report it here first.
Thank you.
-- tony
Syslog messages follow:
Apr 16 04:07:14 manic kernel: hdb: dma_timer_expiry: dma status == 0x61
Apr 16 04:07:24 manic kernel: hdb: DMA timeout error
Apr 16 04:07:24 manic kernel: hdb: dma timeout error: status=0xd0 { Busy }
Apr 16 04:07:24 manic kernel:
Apr 16 04:07:24 manic kernel: hda: DMA disabled
Apr 16 04:07:24 manic kernel: hdb: DMA disabled
Apr 16 04:07:55 manic kernel: ide0: reset timed-out, status=0xd0
Apr 16 04:07:55 manic kernel: hdb: status error: status=0x00 { }
Apr 16 04:07:55 manic kernel:
Apr 16 04:07:55 manic kernel: hdb: drive not ready for command
Apr 16 04:07:55 manic kernel: hdb: status error: status=0x00 { }
Apr 16 04:07:55 manic kernel:
Apr 16 04:07:55 manic kernel: hdb: drive not ready for command
Apr 16 04:07:56 manic kernel: hdb: status error: status=0x00 { }
Apr 16 04:07:56 manic kernel:
Apr 16 04:07:56 manic kernel: hdb: drive not ready for command
Apr 16 04:07:56 manic kernel: hdb: status error: status=0x00 { }
Apr 16 04:07:56 manic kernel:
Apr 16 04:07:56 manic kernel: hdb: drive not ready for command
Apr 16 04:08:27 manic kernel: ide0: reset timed-out, status=0xd0
Apr 16 04:08:27 manic kernel: end_request: I/O error, dev hdb, sector 499007
Apr 16 04:08:27 manic kernel: end_request: I/O error, dev hdb, sector 499007
Apr 16 04:08:28 manic kernel: vs-13050: reiserfs_update_sd: i/o failure
occurred trying to update [1 2 0x0 SD] stat dataend_request: I/O error,
dev hdb, sector 36743
Apr 16 04:08:28 manic kernel: Buffer I/O error on device hdb1, logical
block 4585
Apr 16 04:08:28 manic kernel: lost page write due to I/O error on hdb1
Apr 16 04:08:28 manic kernel: journal-601, buffer write failed
Apr 16 04:08:28 manic kernel: ------------[ cut here ]------------
Apr 16 04:08:28 manic kernel: kernel BUG at fs/reiserfs/prints.c:339!
Apr 16 04:08:28 manic kernel: invalid operand: 0000 [#1]
Apr 16 04:08:28 manic kernel: PREEMPT
Apr 16 04:08:28 manic kernel: CPU: 0
Apr 16 04:08:28 manic kernel: EIP: 0060:[<c019ad43>] Tainted: P
Apr 16 04:08:28 manic kernel: EFLAGS: 00010286 (2.6.5)
Apr 16 04:08:28 manic kernel: EIP is at reiserfs_panic+0x37/0x67
Apr 16 04:08:28 manic kernel: eax: 00000024 ebx: c2692e00 ecx:
c04b46c4 edx: c03f1838
Apr 16 04:08:28 manic kernel: esi: f8bd4ddc edi: 00000000 ebp:
f6477d08 esp: f6477cf8
Apr 16 04:08:28 manic kernel: ds: 007b es: 007b ss: 0068
Apr 16 04:08:28 manic kernel: Process pdflush (pid: 6243,
threadinfo=f6476000 task=cd081800)
Apr 16 04:08:28 manic kernel: Stack: c0397014 c04c32a0 f8bd4ddc c2692e00
f6477d4c c01a5c7e c2692e00 c03a2240
Apr 16 04:08:28 manic kernel: 00000000 00001000 f6fd1000 f6fe7a00
000011ea 00000005 00000003 00000000
Apr 16 04:08:28 manic kernel: 00000002 f462d2ec 00000031 f6fe7a00
c2692e00 f6477dc0 c01aa04c c2692e00
Apr 16 04:08:28 manic kernel: Call Trace:
Apr 16 04:08:28 manic kernel: [<c01a5c7e>] flush_commit_list+0x2cc/0x459
Apr 16 04:08:28 manic kernel: [<c01aa04c>] do_journal_end+0x598/0xbbe
Apr 16 04:08:28 manic kernel: [<c01a8b62>] do_journal_begin_r+0x256/0x28a
Apr 16 04:08:28 manic kernel: [<c01a93e3>] flush_old_commits+0x12f/0x1c2
Apr 16 04:08:28 manic kernel: [<c0197cc6>] reiserfs_write_super+0x84/0x86
Apr 16 04:08:28 manic kernel: [<c01535f4>] sync_supers+0xb2/0xbb
Apr 16 04:08:28 manic kernel: [<c01356b6>] wb_kupdate+0x43/0x134
Apr 16 04:08:28 manic kernel: [<c011463f>] schedule+0x344/0x5a0
Apr 16 04:08:28 manic kernel: [<c0135cf4>] __pdflush+0xdc/0x1de
Apr 16 04:08:28 manic kernel: [<c0135e20>] pdflush+0x2a/0x2e
Apr 16 04:08:28 manic kernel: [<c0135673>] wb_kupdate+0x0/0x134
Apr 16 04:08:28 manic kernel: [<c0129a10>] kthread+0xa5/0xaa
Apr 16 04:08:28 manic kernel: [<c0135df6>] pdflush+0x0/0x2e
Apr 16 04:08:28 manic kernel: [<c012996b>] kthread+0x0/0xaa
Apr 16 04:08:28 manic kernel: [<c0104fcd>] kernel_thread_helper+0x5/0xb
Apr 16 04:08:28 manic kernel:
Apr 16 04:08:28 manic kernel: Code: 0f 0b 53 01 53 aa 39 c0 b8 68 a6 39
c0 8d 93 10 01 00 00 85
Apr 16 04:08:28 manic kernel: end_request: I/O error, dev hdb, sector 36751
Apr 16 04:08:28 manic kernel: Buffer I/O error on device hdb1, logical
block 4586
Apr 16 04:08:28 manic kernel: lost page write due to I/O error on hdb1
Apr 16 04:08:29 manic kernel: end_request: I/O error, dev hdb, sector
43544419
Apr 16 04:08:29 manic kernel: end_request: I/O error, dev hdb, sector
43544419
Apr 16 04:08:46 manic kernel: vs-13050: reiserfs_update_sd: i/o failure
occurred trying to update [1 2 0x0 SD] stat data<4>
--
next reply other threads:[~2004-04-16 15:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-16 15:12 Anthony R. [this message]
2004-04-16 21:59 ` [PATCH] ReiserFS I/O error Handling [was Re: kernel BUG at fs/reiserfs/prints.c:339! kernel 2.6.5] Jeff Mahoney
2004-04-18 20:47 ` Anthony R.
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=407FF7CA.3050002@verizon.net \
--to=russo.lutions@verizon.net \
--cc=linux-kernel@vger.kernel.org \
/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.