upgraded gentoo vanilla-sources 2.6.12-rc3 on jfs partition to -rc4 using previous .config and rebooted. as soon as the boot process reaches reiser devices it prints numerous lines to dmesg and continues to KDE login. Able to login to KDE but none of the reiser partitions are mountable.. It was then not possible to reboot, i.e. it hangs. However, after 'fsck -t jfs' of the partition from another gentoo copy, it was possible to reboot the 2.6.12-rc3 version ok Reproducible: Always Steps to Reproduce: 1.Upgrade to vanilla-sources-2.6.12-rc4 on a jfs partition 2.make sure CONFIG_REISERFS_CHECK=y 3.reboot Actual Results: Able to login to KDE but none of the reiser partitions are mountable.. Expected Results: mountable reiser partitions will get back with 'emerge info' when jfs partition rebooted ok from dmesg: ReiserFS: hda7: found reiserfs format "3.6" with standard journal ReiserFS: hda7: warning: CONFIG_REISERFS_CHECK is set ON ReiserFS: hda7: warning: - it is slow mode for debugging. ReiserFS: hda7: using ordered data mode ReiserFS: hda7: journal params: device hda7, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 ReiserFS: hda7: checking transaction log (hda7) ReiserFS: hda7: journal-1153: found in header: first_unflushed_offset 7763, last_flushed_trans_id 409784 ReiserFS: hda7: journal-1206: Starting replay from offset 1760013173399123, trans_id 0 ReiserFS: hda7: journal-1299: Setting newest_mount_id to 358 ReiserFS: hda7: Using r5 hash to sort names REISERFS: panic (device Null superblock): reiserfs[4540]: assertion !( comp_keys( &MAX_KEY, p_s_key ) && ! key_in_buffer(p_s_search_path, p_s_key, p_s_sb) ) failed at fs/reiserfs/stree.c:685:search_by_key: PAP-5130: key is not in the buffer ------------[ cut here ]------------ kernel BUG at fs/reiserfs/prints.c:362! invalid operand: 0000 [#1] PREEMPT Modules linked in: eeprom i2c_dev asb100 i2c_sensor i2c_core unix CPU: 0 EIP: 0060:[<c01b05fe>] Not tainted VLI EFLAGS: 00010282 (2.6.12-rc4) EIP is at reiserfs_panic+0x51/0x76 eax: 000000fb ebx: c0405473 ecx: 000029f2 edx: c04b6701 esi: 00000000 edi: 00000140 ebp: ef2ebd78 esp: ef2ebbcc ds: 007b es: 007b ss: 0068 Process mount (pid: 4540, threadinfo=ef2ea000 task=ef2540a0) Stack: c04108b4 c0405473 c054ffa0 ffffffff ffffffff c03f008d c01b9daa 00000000 c0415454 000011bc 000002ad c03f010c 00000000 00000001 ef2ebd7c c01b8933 eeba0000 ffffffff 00000000 ef2ea000 ef2ea000 ef2ea000 ef2ea000 ef2ea000 Call Trace: [<c01b9daa>] search_by_key+0x13cd/0x1bc4 [<c01b8933>] is_tree_node+0x6c/0x71 [<c013ecf8>] __alloc_pages+0x173/0x3d8 [<c011a0a6>] call_console_drivers+0x67/0x13b [<c01ad069>] finish_unfinished+0x9f/0x3a2 [<c012e1a5>] autoremove_wake_function+0x0/0x57 [<c01c4e80>] do_journal_end+0x7f3/0x966 [<c025d3c3>] vsprintf+0x27/0x2b [<c01af7cc>] reiserfs_fill_super+0x6c6/0x77e [<c01a14c9>] reiserfs_init_locked_inode+0x0/0x16 [<c015f82e>] sb_set_blocksize+0x2e/0x5e [<c015f1f8>] get_sb_bdev+0xe0/0x145 [<c01742dc>] alloc_vfsmnt+0x9c/0xd1 [<c01af8f0>] get_super_block+0x2f/0x33 [<c01af106>] reiserfs_fill_super+0x0/0x77e [<c015f46c>] do_kern_mount+0x63/0xe9 [<c0175437>] do_new_mount+0x9e/0xf7 [<c0175b27>] do_mount+0x19d/0x1bb [<c0175933>] copy_mount_options+0x60/0xb7 [<c0175ef4>] sys_mount+0x9f/0xd7 [<c0102a27>] sysenter_past_esp+0x54/0x75 Code: 24 8d be 40 01 00 00 e8 e2 fc ff ff 85 f6 89 d8 c7 44 24 08 a0 ff 54 c0 c7 04 24 b4 08 41 c0 0f 45 c7 89 44 24 04 e8 42 9c f6 ff <0f> 0b 6a 01 36 5a 40 c0 85 f6 c7 44 24 08 a0 ff 54 c0 c7 04 24
emerge info Linux p4pe 2.6.12-rc4 #2 Sun May 8 21:23:11 UTC 2005 i686 Intel(R) Pentium(R) 4 CPU 2.40GHz GenuineIntel GNU/Linux p4pe linux-2.6.12-rc4 # emerge info Portage 2.0.51.19 (default-linux/x86/2005.0, gcc-3.4.3-20050110, glibc-2.3.4.20050125-r1, 2.6.12-rc4 i686) ================================================================= System uname: 2.6.12-rc4 i686 Intel(R) Pentium(R) 4 CPU 2.40GHz Gentoo Base System version 1.6.11 Python: dev-lang/python-2.3.5 [2.3.5 (#1, Apr 30 2005, 20:28:33)] ccache version 2.4 [enabled] dev-lang/python: 2.3.5 sys-apps/sandbox: 1.2 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.5 sys-devel/binutils: 2.15.92.0.2-r7 sys-devel/libtool: 1.5.16 virtual/os-headers: 2.6.8.1-r4 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O2 -march=pentium4 -fomit-frame-pointer -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=pentium4 -fomit-frame-pointer -pipe" DISTDIR="/mnt/hdb9/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://mirror.gentoo.no/ ftp://ftp.snt.utwente.nl/pub/os/linux/gentoo ftp://ftp.du.se/pub/os/gentoo http://gentoo.osuosl.org http://www.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/mnt/hdb9/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/mnt/hdb9/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 X a52 aac aalib alsa apm arts audiofile avi berkdb bitmap-fonts cddb cdparanoia cdr crypt cups curl directfb dts dvd dvdr emboss encode esd faad fam flac foomaticdb gdbm gif gpm gtk2 imagemagick imlib ipv6 java javascript jpeg kde ldap libg++ libwww live lm_sensors mad mikmod mmx motif mp3 mpeg nas ncurses network nls nptl ogg oggvorbis opengl oss pam pdflib perl png ppds python qt quicktime readline real rtc sdl slang spell sse sse2 ssl svga tcltk tcpd theora tiff truetype truetype-fonts type1-fonts usb vorbis xine xml2 xmms xv xvid zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS
Please use "New -> Gentoo Linux -> Component: Ebuilds" in future. Infrastructure is not the correct addressee.
on the same system I have also detected that when CONFIG_SND_USB_AUDIO=y my voip handset no longer works, however, using CONFIG_SND_USB_AUDIO=m and all is well. NB! 2.6.12-rc3 works OK with =y Proc Asound ----------------------------------------------- Advanced Linux Sound Architecture Driver Version 1.0.9rc2 (Thu Mar 24 10:33:39 2005 UTC). 0 [I82801DBICH4 ]: ICH4 - Intel 82801DB-ICH4 Intel 82801DB-ICH4 with AD1980 at 0xec000000, irq 3 1 [Phone ]: USB-Audio - VoIPvoice USB Phone PDT VoIPvoice USB Phone at usb-0000:00:1d.2-2, full speed
Ref comment 3's CONFIG_SND_USB_AUDIO=y problem, I said the problem was on the same system, where I should have said "on a system with the same version" (i.e. 2.6.12-rc4). This problem was seen on two other Gentoo copies when upgraded from -rc3 to -rc4, but oddly enough NOT on the original bug's system, which had CONFIG_SND_USB_AUDIO=m, and where voipphone worked. I have now found that once I recompile with CONFIG_SND_USB_AUDIO=m each of the failing systems will work OK, but if I then put them back to CONFIG_SND_USB_AUDIO=y, they still work, as will the bug's system if I change that to CONFIG_SND_USB_AUDIO=y from its original =m. So the solution seems be related to the fact that I still have RC_DEVICE_TARBALL="yes" in /etc/conf.d/rc on each of these systems (this saves me setting up pktcdvd after each boot..)
Please use one bug for one issue. Looking at the reiserfs oops issue, is this reproducable?
I can confirm this bug, which affects vanilla-sources-2.6.12_rc4 as well as Linus' current 2.6 tree which I just pulled from git. I have a ReiserFS 3 root partition and during boot I saw: Mounting root... Segmentation fault Could not mount specified ROOT, try again The root block device is unspecified or not detected If I drop into the (genkernel) initrd shell and try to mount ReiserFS, the shell hangs. Trying to mount FAT, I just get an error. However as soon as I unset ReiserFS debugging, mounting works again. Also 2.6.12_rc3 worked perfectly either way.
Yes its reproducible. Just did it again to be sure.. There is also another report be Dr Z on my original thread http://forums.gentoo.org/viewtopic-t-334521-highlight-.html and a further probable in this thread http://forums.gentoo.org/viewtopic-p-2398054.html#2398054 mvh
Ok, thats quite worrying. Please write a plain-text mail to linux-kernel@vger.kernel.org about this, with linux-fsdevel@vger.kernel.org and reiserfs-list@namesys.com and me on CC. Make sure you state that it happens on an unpatched 2.6.12-rc4, occurs even when reiserfs partitions are not present, and caused some form of data corruption. Include the oops message too.
I added this information to a bug report from another user for the same issue on linux-kernel. http://lkml.org/lkml/2005/5/17/243
Thanks. I've made Andrew Morton aware of the issue. He'd like to know when the bug was introduced. The original report says it was introduced in 2.6.12-rc4 and was not present in 2.6.12-rc3. Can anyone else confirm this?
Just spotted comment #6. I guess we can say this was introduced between rc3 and rc4 for definate.
Right, looking at the diff between -rc3 and -rc4 there was a change from a reiserfs_key type to an in_core_key type across several files, and a new constant MAX_IN_CORE_KEY introduced alongside MAX_KEY. Looking at the oops it seems logical this might be the source of the new bug, but this is only an uneducated guess. REISERFS: panic (device Null superblock): reiserfs[4540]: assertion !( comp_keys( &MAX_KEY, p_s_key ) && ! key_in_buffer(p_s_search_path, p_s_key, p_s_sb) ) failed at fs/reiserfs/stree.c:685:search_by_key: PAP-5130: key is not in the buffer
Can someone please confirm that 2.6.12-rc5 fixes the problem.
Happy to report the original problem has been fixed in 2.6.12-rc5 I am running OK again with CONFIG_REISERFS_CHECK=y Thanks!
