2003-06-11 12:58:50

by szazol

Subject: buffer layer error at fs/buffer.c:127

Hi!

I found this message in dmesg:

buffer layer error at fs/buffer.c:127
Pass this trace through ksymoops for reporting
Call Trace: [<c013f145>] [<c0114898>] [<c0114898>] [<c018e69a>] [<c018e730>] [<c018e91d>] [<c018c527>] [<c018c98c>] [<c017bc8e>] [<c0192800>] [<c017ce2d>] [<c02631bc>] [<c013ee28>] [<c013d80c>] [<c013d888>] [<c0108d53>]


Here's the ksymoops output:

ksymoops 2.4.8 on i686 2.5.67. Options used
-V (default)
-K (specified)
-l /proc/modules (default)
-o /lib/modules/2.5.67/ (default)
-m /boot/System.map-2.5.67 (default)

No modules in ksyms, skipping objects
No ksyms, skipping lsmod
Call Trace: [<c013f145>] [<c0114898>] [<c0114898>] [<c018e69a>] [<c018e730>] [<c018e91d>] [<c018c527>] [<c018c98c>] [<c017bc8e>] [<c0192800>] [<c017ce2d>] [<c02631bc>] [<c013ee28>] [<c013d80c>] [<c013d888>] [<c0108d53>]
Warning (Oops_read): Code line not seen, dumping what data is available


Trace; c013f145 <__wait_on_buffer+d0/d2>
Trace; c0114898 <autoremove_wake_function+0/4f>
Trace; c0114898 <autoremove_wake_function+0/4f>
Trace; c018e69a <reiserfs_unmap_buffer+62/9c>
Trace; c018e730 <unmap_buffers+5c/5e>
Trace; c018e91d <indirect2direct+1eb/2e2>
Trace; c018c527 <reiserfs_cut_from_item+3c3/4e6>
Trace; c018c98c <reiserfs_do_truncate+2eb/5a4>
Trace; c017bc8e <reiserfs_truncate_file+df/209>
Trace; c0192800 <journal_end+27/2b>
Trace; c017ce2d <reiserfs_file_release+229/43f>
Trace; c02631bc <ide_do_request+1d4/34f>
Trace; c013ee28 <__fput+9b/9d>
Trace; c013d80c <filp_close+4d/79>
Trace; c013d888 <sys_close+50/5f>
Trace; c0108d53 <syscall_call+7/b>


1 warning issued. Results may not be reliable.

No module support was compiled into the kernel.

Regards,
SZALONTAI Zoltan

2003-06-11 14:39:44

by Oleg Drokin

Subject: Re: buffer layer error at fs/buffer.c:127

Hello!

On Wed, Jun 11, 2003 at 03:12:31PM +0200, [email protected] wrote:

> I found this message in dmesg:
> buffer layer error at fs/buffer.c:127
> Pass this trace through ksymoops for reporting
> Call Trace: [<c013f145>] [<c0114898>] [<c0114898>] [<c018e69a>] [<c018e730>] [<c018e91d>] [<c018c527>] [<c018c98c>] [<c017bc8e>] [<c0192800>] [<c017ce2d>] [<c02631bc>] [<c013ee28>] [<c013d80c>] [<c013d888>] [<c0108d53>]

This incorrect debugging check is already fixed in more recent kernels.

Bye,
Oleg