All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Felt <steve@circlepix.com>
To: reiserfs-list@namesys.com
Subject: kernel bug
Date: Fri, 18 Feb 2005 12:38:05 -0700	[thread overview]
Message-ID: <1108755484.23313.77.camel@sfelt> (raw)

I'm getting the following "kernel BUG" on SuSE 9.1 Pro (and on 9.2):

[first, the hw/sw details]
  LSI 929x (7202xp)
  Large array of drives (1.4TB)

  cat /proc/meminfo
	MemTotal:      1036148 kB

  cat /proc/cpuinfo
	processor       : 0
	vendor_id       : AuthenticAMD
	cpu family      : 6
	model           : 6
	model name      : AMD Athlon(tm) MP 2000+

  cat /proc/mpt/version
	mptlinux-3.01.14.23
	Fusion MPT base driver
	Fusion MPT SCSI host driver

  cat /etc/SuSE-release
	SuSE Linux 9.1 (i586)
	VERSION = 9.1

  dmesg | grep -i reiser | grep sda
	ReiserFS: sda1: found reiserfs format "3.6" with standard 	journal
	ReiserFS: sda1: using ordered data mode
	ReiserFS: sda1: journal params: device sda1, size 8192, 	journal first
block 18, max trans len 1024, max batch 900, max 	commit age 30, max
trans age 30
	ReiserFS: sda1: checking transaction log (sda1)
	reiserfs: disabling flush barriers on sda1
	ReiserFS: sda1: Using r5 hash to sort names

Symptoms:
   I can do an initial rsync of a large amount of data (~300MB) from
another host, but subsequent rsync attempts fail after about 1hour (when
files are actually being copied over/ replaced etc.) with the following:

 kernel: ------------[ cut here ]------------
 kernel: kernel BUG at fs/reiserfs/namei.c:1291!
 kernel: invalid operand: 0000 [#1]
 kernel: CPU: 0
 kernel: EIP: 0060:[__crc_device_suspend+2680266/3186568] Not tainted
 kernel: EIP: 0060:[] Not tainted
 kernel: EFLAGS: 00010296 (2.6.5-7.111.19-default)
 kernel: EIP is at reiserfs_rename+0x299/0x7d0 [reiserfs]
 kernel: eax: ffffffff ebx: 00008000 ecx: e88a7cf0 edx: e88a7cf0
 kernel: esi: 00000000 edi: e88a7ca0 ebp: e4aa5dcc esp: e88a7be8
 kernel: ds: 007b es: 007b ss: 0068
 kernel: Process rsync (pid: 3062, threadinfo=e88a6000 task=f13de220)
 kernel: Stack: 00000009 00000009 00000001 00008180 f5b49018 00001000
00000000 00000000
 kernel: 00000000 f5b4bb4c e4a84080 f5b4bb4c 00000000 00000000 c1a0e400
00000001
 kernel: 00000000 0000003b 00002b5b 00000000 00000000 e88a7c3c e88a7c3c
e88a7d50
 kernel: Call Trace:
 kernel: [__crc_device_suspend+2716835/3186568]
reiserfs_allocate_blocks_for_region+0xf32/0x1320 [reiserfs]
 kernel: [] reiserfs_allocate_blocks_for_region+0xf32/0x1320 [reiserfs]
 kernel: [__crc_device_suspend+2692640/3186568] inode2sd+0x12f/0x140
[reiserfs]
 kernel: [] inode2sd+0x12f/0x140 [reiserfs]
 kernel: [__crc_device_suspend+2772063/3186568] pathrelse+0x1e/0x30
[reiserfs]
 kernel: [] pathrelse+0x1e/0x30 [reiserfs]
 kernel: [autoremove_wake_function+0/48]
autoremove_wake_function+0x0/0x30
 kernel: [] autoremove_wake_function+0x0/0x30
 kernel: [__crc_device_suspend+2807928/3186568]
do_journal_end+0x1f7/0xc40 [reiserfs]
 kernel: [] do_journal_end+0x1f7/0xc40 [reiserfs]
 kernel: [__crc_device_suspend+2812134/3186568] journal_end+0x65/0xc0
[reiserfs]
 kernel: [] journal_end+0x65/0xc0 [reiserfs]
 kernel: [__crc_device_suspend+2719325/3186568]
reiserfs_file_write+0x5cc/0x639 [reiserfs]
 kernel: [] reiserfs_file_write+0x5cc/0x639 [reiserfs]
 kernel: [vfs_rename_other+149/272] vfs_rename_other+0x95/0x110
 kernel: [] vfs_rename_other+0x95/0x110
 kernel: [vfs_rename+335/896] vfs_rename+0x14f/0x380
 kernel: [] vfs_rename+0x14f/0x380
 kernel: [sys_rename+575/704] sys_rename+0x23f/0x2c0
 kernel: [] sys_rename+0x23f/0x2c0
 kernel: [__pollwait+0/208] __pollwait+0x0/0xd0
 kernel: [] __pollwait+0x0/0xd0
 kernel: [sys_close+112/208] sys_close+0x70/0xd0
 kernel: [] sys_close+0x70/0xd0
 kernel: [sysenter_past_esp+82/121] sysenter_past_esp+0x52/0x79
 kernel: [] sysenter_past_esp+0x52/0x79
 kernel:
 kernel: Code: 0f 0b 0b 05 35 d0 10 f9 8b 84 24 58 02 00 00 8b 8c c4 60
02


--------------------------------------------


I am open to any suggestions and I DO appreciate the hard work that's
gone into ReiserFS. I'm not above paying for the core developers' help,
if it comes to that (yes, I've read 
http://www.namesys.com/support.html
and
http://www.namesys.com/faq.html
). Also, I am open to suggestions, such as "you need to recompile the
kernel with..." or "why don't you read..." or "the hardware has to be
replaced..."

Thanks for reading!
("Blagodaryu za vnimanie!")

-steve



             reply	other threads:[~2005-02-18 19:38 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-18 19:38 Steve Felt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-07-31 17:02 Kernel bug Sergiy Vovk
2011-09-24 19:26 kernel bug Roman Kapusta
2011-09-24 19:45 ` Roman Kapusta
2011-09-26  0:50 ` Li Zefan
2010-12-23 18:12 kernel BUG Dipl.-Ing. Michael Niederle
2010-12-23 19:43 ` Chris Ball
2010-12-23 20:55   ` Michael Niederle
2010-12-24  0:19     ` Chris Ball
2010-12-24  0:32       ` Michael Niederle
2010-12-24  0:51         ` Chris Ball
2010-12-25  9:50           ` Michael Niederle
2010-12-25 11:46             ` Christian Thaeter
     [not found] <200907311139.55095.christoph.thielecke@gmx.de>
2009-07-31 16:01 ` kernel bug Linus Torvalds
2009-07-31 16:26   ` Eric Paris
     [not found] <150c16850812011409hf507ac6m5b168571ee6b453e@mail.gmail.com>
2008-12-02 21:06 ` Kernel BUG Justin Maggard
2008-12-02 23:38   ` Neil Brown
2008-12-11 21:23     ` Dan Williams
2008-09-10 20:35 kernel bug Todor Gyumyushev
2008-09-11  3:21 ` Aaron Straus
2008-04-13 16:06 monte
2008-04-13 18:20 ` Jesper Juhl
2008-04-13 18:33 ` Alan Cox
2008-03-29  9:05 Olver Eduardo Ramos
2008-03-30  1:06 ` Rafael J. Wysocki
2007-09-19 21:43 Kernel bug Branislav Bozgai
2007-09-24 15:33 ` Mel Gorman
2007-08-19 18:33 kernel bug Costas Sismanis
2006-12-22 11:59 Kernel BUG Rudy Zijlstra
2006-12-22 11:59 ` Rudy Zijlstra
2006-12-22 13:42 ` Peter Zijlstra
2006-12-22 13:42   ` Peter Zijlstra
2006-12-22 23:46   ` Rudy Zijlstra
2005-11-26  1:23 Kernel bug Vympel
2005-11-27 12:51 ` Hugh Dickins
2005-11-03 18:10 Kernel BUG Mark Fortescue
2005-11-03 18:59 ` Trond Myklebust
2005-11-03 23:15   ` Mark Fortescue
2005-11-04 10:08   ` Mark Fortescue
2005-09-26  8:59 Haavard Bjerke
2005-04-07 21:26 kernel BUG christophe varoqui
2004-07-06 15:06 Kernel BUG Teuling, Sieme
2004-07-06 20:21 ` Thomas Gleixner
2003-03-26 23:57 Perez-Gonzalez, Inaky
2003-03-27 14:23 ` Hugh Dickins
2003-03-26 13:13 kasper_k_jensen
2003-01-25 22:56 Kernel bug Massimiliano C. - Uf0On|in3
2003-01-19 18:01 Christophe Dupre
2003-01-07  9:17 kernel BUG Sönke Ruempler
2002-12-07 10:09 Kernel BUG Henrik Steffen
2002-12-08  1:47 ` Alan Cox
2002-11-27 11:31 kernel bug sanket rathi
2002-11-27 10:45 sanket rathi
2002-11-27  9:50 sanket rathi
2002-11-27 10:10 ` Arjan van de Ven
2002-06-28 19:54 kernel BUG Eric Weiss
2002-06-28 19:26 ew
2002-06-27 19:23 Chaoyang Deng
2002-06-28  5:58 ` Austin Gonyou
2002-06-28 14:00   ` Mike Black
2002-05-21 14:01 kernel bug Chen Hao
2001-11-25 18:03 Kernel Bug gonzalo.ab
2001-11-25 23:59 ` Adam Schrotenboer
2001-05-13 16:46 Kernel bug Tomas Jura
2001-05-13 17:12 ` Olaf Hering
2001-05-13 17:48   ` Tomas Jura
2001-05-14 15:27     ` Olaf Hering
2001-03-06 19:55 kernel bug ernte23

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=1108755484.23313.77.camel@sfelt \
    --to=steve@circlepix.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.