I have a 2.4.0-test9/reiserfs-3.6.17 (as well as various other patches
which I can enumerate if you think it matters) system which is oopsing
reproducably. The sequence to reproduce is:
o make a reiserfs filesystem
o mount it
o run "find /usr -mount -depth | cpio -pvudm /mnt/reiserfs" to bulk copy
data to it
During the cpio I get:
kernel BUG at highmem.c:221!
invalid operand: 0000
CPU: 0
EIP: 0010:[kunmap_high+28/120]
EFLAGS: 00210286
eax: 0000001d ebx: 00000000 ecx: c284e000 edx: c618f7a0
esi: c284fbec edi: c284fe90 ebp: c284fc04 esp: c284fba0
ds: 0018 es: 0018 ss: 0018
Process cpio (pid: 8366, stackpage=c284f000)
Stack: c02085af c0208791 000000dd c3029000 c016e0d4 00000000 00001000 00000000
c25a0c00 00003000 00000000 00000050 00001000 00000005 00000033 00004000
20000000 00000001 00000004 00000005 00000033 00003001 20000000 0050ffff
Call Trace: [tvecs+13279/49404] [tvecs+13761/49404] [indirect2direct+620/696]
[maybe_indirect_to_direct+497/508] [reiserfs_cut_from_item+204/1072]
[reiserfs_do_truncate+756/1028] [reiserfs_truncate_file+178/500]
[devfsd_buf_size+9208/40928] [devfsd_buf_size+28810/40928]
[reiserfs_file_release+818/852] [devfsd_buf_size+9570/40928]
[devfsd_buf_size+28810/40928] [fput+56/208] [filp_close+92/100] [sys_close+67/84]
[system_call+51/64] [startup_32+43/314]
Code: 0f 0b 83 c4 0c 8d 76 00 8d 83 00 00 00 02 ba 00 cf 2a c0 c1
The "BUG" message and the oops happen at the same time.
Is there anything more I can do to help track this down?
b.
--
Brian J. Murrell
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
