Re: reiser4 bug
On Sun, Feb 27, 2005 at 07:34:11PM +, Szabolcs Illes wrote: > Hi All, > > I have been using reiser4fs for 4 months without any problem since > today. After tryinig to open a movie with mplayer a have this in my log: no other reiser4 messages in the log for 4 months? like delimiting keys mismatch reports? there was wrong bitmap checksum. actually I haven't seen such reports until now. are you sure your computer's disk/ram work well? > > Feb 27 14:00:22 sunset kernel: reiser4[mc(9192)]: > write_sd_by_inode_common (fs/reiser4/plugin/object.c:480)[nikita-2221]: > Feb 27 14:00:22 sunset kernel: WARNING: Failed to save sd for 1599330: -5 > Feb 27 14:00:22 sunset kernel: reiser4[mc(9192)]: create_child_common > (fs/reiser4/plugin/dir/dir.c:501)[nikita-2219]: > Feb 27 14:00:22 sunset kernel: WARNING: Failed to create sd for 1599330 > Feb 27 14:00:23 sunset kernel: reiser4[cupsd(3296)]: parse_node40 > (fs/reiser4/plugin/node/node40.c:767)[nikita-494]: > Feb 27 14:00:23 sunset kernel: WARNING: Wrong level found in node: 1 != 95 > Feb 27 14:00:23 sunset kernel: reiser4[cupsd(3296)]: parse_node40 > (fs/reiser4/plugin/node/node40.c:767)[nikita-494]: > Feb 27 14:00:23 sunset kernel: WARNING: Wrong level found in node: 1 != 95 > Feb 27 14:00:24 sunset kernel: reiser4[cupsd(3296)]: parse_node40 > (fs/reiser4/plugin/node/node40.c:767)[nikita-494]: > Feb 27 14:00:24 sunset kernel: WARNING: Wrong level found in node: 1 != 95 > .. > 1000x times were there unclear reboots? That shouldn't be a problem unless disk write caching is disabled. > After trying to reboot: > > http://nuk.teteny.elte.hu/~selli/dscf0437.jpg (using 2.6.9-cko3) > http://nuk.teteny.elte.hu/~selli/dscf0438.jpg > http://nuk.teteny.elte.hu/~selli/dscf0439.jpg > > I had to install a new root filesystem, and using that I was able to fix > the filesystem. ( --build-sb, build-fs, and fix ) > I have lost some file but fortunatly I was able to use my system again. > > The affair happend when I was using 2.6.10 with reiser4 patch(from > namesys.com). I tried to reboot with my previos kernel (2.6.9-cko3) but > had the some bug (see screenshots). Sorry but I forgot to save the > outout of the fsck prog :(. > > If U need any information do not hesitate contacting me.( I am not on > the mailing list) > > Some info in advanve: > Hardware: Dell Inpiron 8600c (1600Mhz Centrion processor) > > Kernel config: [...] -- Alex.
Re: reiser4 bug
Alex Zarochentsev wrote: On Sun, Feb 27, 2005 at 07:34:11PM +, Szabolcs Illes wrote: Hi All, I have been using reiser4fs for 4 months without any problem since today. After tryinig to open a movie with mplayer a have this in my log: no other reiser4 messages in the log for 4 months? I have checked my logs. I was not able to find anything from reiserfs. But I have uploaded my syslog since feb 27 (this is when the bug occured): http://nuk.teteny.elte.hu/~selli/syslog.1.bz2 ( 1.8 compressed, 300M uncompresed ) It may has more information about the bug, you should check it. For example the very first message from reiser4 is: Feb 27 12:59:38 sunset kernel: WARNING: Wrong level found in node: 1 != 95 Feb 27 12:59:38 sunset kernel: reiser4[cupsd(3296)]: parse_node40 (fs/reiser4/plugin/node/node40.c:767)[nikita-494]: like delimitingkey mismatch reports? there was wrong bitmap checksum. actually I haven't seen such reports until now. are you sure your computer's disk/ram work well? My machine (seems to be) is fun, I have run some tests. Another info: I was using an extrenal usb2 disk (120Gb/ reiser4) when this affair occurd. After rebooting I had to repair all my reiser4 partitions. ( / hda2, /home hda5/, /mnt/Movies sda1). For the "/" I had to use --build-sb, then --build-fs, then --fix For /home, and the external /mnt/Movies just the --build-sb Feb 27 14:00:22 sunset kernel: reiser4[mc(9192)]: write_sd_by_inode_common (fs/reiser4/plugin/object.c:480)[nikita-2221]: Feb 27 14:00:22 sunset kernel: WARNING: Failed to save sd for 1599330: -5 Feb 27 14:00:22 sunset kernel: reiser4[mc(9192)]: create_child_common (fs/reiser4/plugin/dir/dir.c:501)[nikita-2219]: Feb 27 14:00:22 sunset kernel: WARNING: Failed to create sd for 1599330 Feb 27 14:00:23 sunset kernel: reiser4[cupsd(3296)]: parse_node40 (fs/reiser4/plugin/node/node40.c:767)[nikita-494]: Feb 27 14:00:23 sunset kernel: WARNING: Wrong level found in node: 1 != 95 Feb 27 14:00:23 sunset kernel: reiser4[cupsd(3296)]: parse_node40 (fs/reiser4/plugin/node/node40.c:767)[nikita-494]: Feb 27 14:00:23 sunset kernel: WARNING: Wrong level found in node: 1 != 95 Feb 27 14:00:24 sunset kernel: reiser4[cupsd(3296)]: parse_node40 (fs/reiser4/plugin/node/node40.c:767)[nikita-494]: Feb 27 14:00:24 sunset kernel: WARNING: Wrong level found in node: 1 != 95 .. 1000x times were there unclear reboots? I had some crash ( I think it was because of my bug ethernet driver, I have no crash since I replaced it) That shouldn't be a problem unless disk write caching is disabled. How can I chech this? Szabolcs After trying to reboot: http://nuk.teteny.elte.hu/~selli/dscf0437.jpg (using 2.6.9-cko3) http://nuk.teteny.elte.hu/~selli/dscf0438.jpg http://nuk.teteny.elte.hu/~selli/dscf0439.jpg I had to install a new root filesystem, and using that I was able to fix the filesystem. ( --build-sb, build-fs, and fix ) I have lost some file but fortunatly I was able to use my system again. The affair happend when I was using 2.6.10 with reiser4 patch(from namesys.com). I tried to reboot with my previos kernel (2.6.9-cko3) but had the some bug (see screenshots). Sorry but I forgot to save the outout of the fsck prog :(. If U need any information do not hesitate contacting me.( I am not on the mailing list) Some info in advanve: Hardware: Dell Inpiron 8600c (1600Mhz Centrion processor) Kernel config: [...]
Re: reiser4 bug
Hello, On Sun, Feb 27, 2005 at 07:34:11PM +, Szabolcs Illes wrote: > Hi All, > > I have been using reiser4fs for 4 months without any problem since > today. After tryinig to open a movie with mplayer a have this in my log: how large was the movie file? We have another similar bug report related to writing/reading of a large (20GB) tar file, so file size may be important. > Feb 27 14:00:22 sunset kernel: reiser4[mc(9192)]: > write_sd_by_inode_common (fs/reiser4/plugin/object.c:480)[nikita-2221]: > Feb 27 14:00:22 sunset kernel: WARNING: Failed to save sd for 1599330: -5 > Feb 27 14:00:22 sunset kernel: reiser4[mc(9192)]: create_child_common > (fs/reiser4/plugin/dir/dir.c:501)[nikita-2219]: > Feb 27 14:00:22 sunset kernel: WARNING: Failed to create sd for 1599330 > Feb 27 14:00:23 sunset kernel: reiser4[cupsd(3296)]: parse_node40 > (fs/reiser4/plugin/node/node40.c:767)[nikita-494]: > Feb 27 14:00:23 sunset kernel: WARNING: Wrong level found in node: 1 != 95 > Feb 27 14:00:23 sunset kernel: reiser4[cupsd(3296)]: parse_node40 > (fs/reiser4/plugin/node/node40.c:767)[nikita-494]: > Feb 27 14:00:23 sunset kernel: WARNING: Wrong level found in node: 1 != 95 > Feb 27 14:00:24 sunset kernel: reiser4[cupsd(3296)]: parse_node40 > (fs/reiser4/plugin/node/node40.c:767)[nikita-494]: > Feb 27 14:00:24 sunset kernel: WARNING: Wrong level found in node: 1 != 95 Thanks, -- Alex.
Re: reiser4 bug
Alex Zarochentsev wrote: Hello, On Sun, Feb 27, 2005 at 07:34:11PM +, Szabolcs Illes wrote: Hi All, I have been using reiser4fs for 4 months without any problem since today. After tryinig to open a movie with mplayer a have this in my log: how large was the movie file? It was about 300MB. But previously I have copied a lot of relative big movies (600-700 MB). We have another similar bug report related to writing/reading of a large (20GB) tar file, so file size may be important. I think the larges file I have ever stored using reiser4 was about 3 or 4 GB. ( for example: vmware disk images, dvd isos ...) Feb 27 14:00:22 sunset kernel: reiser4[mc(9192)]: write_sd_by_inode_common (fs/reiser4/plugin/object.c:480)[nikita-2221]: Feb 27 14:00:22 sunset kernel: WARNING: Failed to save sd for 1599330: -5 Feb 27 14:00:22 sunset kernel: reiser4[mc(9192)]: create_child_common (fs/reiser4/plugin/dir/dir.c:501)[nikita-2219]: Feb 27 14:00:22 sunset kernel: WARNING: Failed to create sd for 1599330 Feb 27 14:00:23 sunset kernel: reiser4[cupsd(3296)]: parse_node40 (fs/reiser4/plugin/node/node40.c:767)[nikita-494]: Feb 27 14:00:23 sunset kernel: WARNING: Wrong level found in node: 1 != 95 Feb 27 14:00:23 sunset kernel: reiser4[cupsd(3296)]: parse_node40 (fs/reiser4/plugin/node/node40.c:767)[nikita-494]: Feb 27 14:00:23 sunset kernel: WARNING: Wrong level found in node: 1 != 95 Feb 27 14:00:24 sunset kernel: reiser4[cupsd(3296)]: parse_node40 (fs/reiser4/plugin/node/node40.c:767)[nikita-494]: Feb 27 14:00:24 sunset kernel: WARNING: Wrong level found in node: 1 != 95 Thanks,
Re: reiser4 bug
On Mon, 2006-04-10 at 22:28 -0700, Matt Eaton wrote: > I was running OpenOffice and tried saving a file. > > I'm using 2.6.16.1 + reiser4-for-2.6.16-1.patch.gz > > (Please help! I'm having to run openoffice on a different filesystem as > this crash has occurred twice saving the same file - after a reboot) Did you fsck when you rebooted? > kernel BUG at fs/reiser4/plugin/file/tail_conversion.c:29! > invalid opcode: [#1] > PREEMPT SMP > Modules linked in: eeprom lm85 hwmon_vid i2c_i801 lp vmnet parport_pc > parport vmmon nfs lockd sunrpc snd_seq_midi snd_emu10k1_synth > snd_emux_synth snd_seq_virmidi snd_seq_midi_emul snd_pcm_oss > snd_mixer_oss snd_seq_oss snd_seq_midi_event snd_seq snd_hda_intel > snd_hda_codec snd_emu10k1 snd_rawmidi snd_ac97_codec snd_ac97_bus > snd_pcm snd_seq_device snd_timer snd_page_alloc snd_util_mem snd_hwdep > snd soundcore binfmt_misc ntfs usblp ide_cd cdrom nvidia e100 mii > uhci_hcd ehci_hcdCPU:0 > EIP:0060:[]Tainted: P VLI > EFLAGS: 00210282 (2.6.16.1 #1) > EIP is at get_exclusive_access+0x1c/0x3d > eax: df21b5dc ebx: 0001 ecx: df21b654 edx: c50e17d4 > esi: acb2e000 edi: c50e1780 ebp: esp: e4481f30 > ds: 007b es: 007b ss: 0068 > Process soffice.bin (pid: 21440, threadinfo=e448 task=dc5bfa90) > Stack: <0>c01c56f4 df21b5dc c013ff95 c253a7ac dda673c0 0001 37c2 > >df21b5dc df21b654 5058c680 e32c4680 acb2e000 e4481fa4 37c2 > c014c900 >e32c4680 acb2e000 37c2 e4481fa4 e32c4680 fff7 bf823d43 > e448 > Call Trace: > [] write_unix_file+0x2a6/0x45c > [] vma_link+0xbe/0xc5 > [] vfs_write+0x87/0x11b > [] sys_write+0x3b/0x63 > [] sysenter_past_esp+0x54/0x75 > Code: 8d 43 14 e8 0b 38 13 00 e9 d1 fc ff ff 90 90 ba 00 e0 ff ff 21 e2 > 8b 12 8b 92 c4 04 00 00 8b 44 24 04 8b 52 50 83 7a 10 00 74 08 <0f> 0b > 1d 00 60 b8 31 c0 ba 01 00 ff ff f0 0f c1 10 85 d2 0f 85 > > > -- Jake Maciejewski <[EMAIL PROTECTED]>
Re: reiser4 bug
On Tuesday 11 April 2006 09:28, Matt Eaton wrote:
> I was running OpenOffice and tried saving a file.
>
> I'm using 2.6.16.1 + reiser4-for-2.6.16-1.patch.gz
>
> (Please help! I'm having to run openoffice on a different filesystem
> as this crash has occurred twice saving the same file - after a
> reboot)
>
> kernel BUG at fs/reiser4/plugin/file/tail_conversion.c:29!
> invalid opcode: [#1]
it is known problem. Fixed in 2.6.17-rc1-mm2
(reiser4-have-get_exclusive_access-restart-transaction.patch).
I am afraid the patch from mm would not apply cleanly to 2.6.16.1 +
reiser4-for-2.6.16-1.patch,
you may try to apply only the following hunk:
@@ -20,13 +20,12 @@ void get_exclusive_access(unix_file_info
assert("nikita-3047", LOCK_CNT_NIL(inode_sem_w));
assert("nikita-3048", LOCK_CNT_NIL(inode_sem_r));
/*
-* "deadlock detection": sometimes we commit a transaction under
+* "deadlock avoidance": sometimes we commit a transaction under
* rw-semaphore on a file. Such commit can deadlock with another
* thread that captured some block (hence preventing atom from
being
* committed) and waits on rw-semaphore.
*/
- assert("nikita-3361", get_current_context()->trans->atom ==
NULL);
- BUG_ON(get_current_context()->trans->atom != NULL);
+ txn_restart_current();
LOCK_CNT_INC(inode_sem_w);
down_write(&uf_info->latch);
uf_info->exclusive_use = 1;
_
> PREEMPT SMP
> Modules linked in: eeprom lm85 hwmon_vid i2c_i801 lp vmnet parport_pc
> parport vmmon nfs lockd sunrpc snd_seq_midi snd_emu10k1_synth
> snd_emux_synth snd_seq_virmidi snd_seq_midi_emul snd_pcm_oss
> snd_mixer_oss snd_seq_oss snd_seq_midi_event snd_seq snd_hda_intel
> snd_hda_codec snd_emu10k1 snd_rawmidi snd_ac97_codec snd_ac97_bus
> snd_pcm snd_seq_device snd_timer snd_page_alloc snd_util_mem
> snd_hwdep snd soundcore binfmt_misc ntfs usblp ide_cd cdrom nvidia
> e100 mii uhci_hcd ehci_hcdCPU:0
> EIP:0060:[]Tainted: P VLI
> EFLAGS: 00210282 (2.6.16.1 #1)
> EIP is at get_exclusive_access+0x1c/0x3d
> eax: df21b5dc ebx: 0001 ecx: df21b654 edx: c50e17d4
> esi: acb2e000 edi: c50e1780 ebp: esp: e4481f30
> ds: 007b es: 007b ss: 0068
> Process soffice.bin (pid: 21440, threadinfo=e448 task=dc5bfa90)
> Stack: <0>c01c56f4 df21b5dc c013ff95 c253a7ac dda673c0 0001
> 37c2
>df21b5dc df21b654 5058c680 e32c4680 acb2e000 e4481fa4 37c2
> c014c900
>e32c4680 acb2e000 37c2 e4481fa4 e32c4680 fff7 bf823d43
> e448
> Call Trace:
> [] write_unix_file+0x2a6/0x45c
> [] vma_link+0xbe/0xc5
> [] vfs_write+0x87/0x11b
> [] sys_write+0x3b/0x63
> [] sysenter_past_esp+0x54/0x75
> Code: 8d 43 14 e8 0b 38 13 00 e9 d1 fc ff ff 90 90 ba 00 e0 ff ff 21
> e2 8b 12 8b 92 c4 04 00 00 8b 44 24 04 8b 52 50 83 7a 10 00 74 08
> <0f> 0b 1d 00 60 b8 31 c0 ba 01 00 ff ff f0 0f c1 10 85 d2 0f 85
>
>
>
>
> !DSPAM:443b3e85155598791294130!
--
Alex.
Re: reiser4 bug
Hi, it is known problem. Fixed in 2.6.17-rc1-mm2 (reiser4-have-get_exclusive_access-restart-transaction.patch). as i've been burned by this bug, too i would suggest making a new patch for 2.6.16 including reiser4-have-get_exclusive_access-restart-transaction.patch or at least put a warning there that the version is unstable. i'm sure most people go straight for the vanilla kernel patch and don't bother with mm-kernels. this puts reiser4 in a bad light imo. kind regards, Michael -- /\ | Michael Weissenbacher <[EMAIL PROTECTED]> | | http://www.dermichi.com/ | | Email users are divided into two classes;| | 1) Those who have effective spam-blocking| | 2) Those who wish they did | \/
Re: reiser4 bug
On 4/10/06, Alexander Zarochentsev <[EMAIL PROTECTED]> wrote:
> On Tuesday 11 April 2006 09:28, Matt Eaton wrote:
> > I was running OpenOffice and tried saving a file.
> >
> > I'm using 2.6.16.1 + reiser4-for-2.6.16-1.patch.gz
> >
> > (Please help! I'm having to run openoffice on a different filesystem
> > as this crash has occurred twice saving the same file - after a
> > reboot)
> >
> > kernel BUG at fs/reiser4/plugin/file/tail_conversion.c:29!
> > invalid opcode: [#1]
>
> it is known problem. Fixed in 2.6.17-rc1-mm2
> (reiser4-have-get_exclusive_access-restart-transaction.patch).
>
> I am afraid the patch from mm would not apply cleanly to 2.6.16.1 +
> reiser4-for-2.6.16-1.patch,
> you may try to apply only the following hunk:
>
> @@ -20,13 +20,12 @@ void get_exclusive_access(unix_file_info
> assert("nikita-3047", LOCK_CNT_NIL(inode_sem_w));
> assert("nikita-3048", LOCK_CNT_NIL(inode_sem_r));
> /*
> -* "deadlock detection": sometimes we commit a transaction under
> +* "deadlock avoidance": sometimes we commit a transaction under
> * rw-semaphore on a file. Such commit can deadlock with another
> * thread that captured some block (hence preventing atom from
> being
> * committed) and waits on rw-semaphore.
> */
> - assert("nikita-3361", get_current_context()->trans->atom ==
> NULL);
> - BUG_ON(get_current_context()->trans->atom != NULL);
> + txn_restart_current();
> LOCK_CNT_INC(inode_sem_w);
> down_write(&uf_info->latch);
> uf_info->exclusive_use = 1;
> _
>
>
> > PREEMPT SMP
> > Modules linked in: eeprom lm85 hwmon_vid i2c_i801 lp vmnet parport_pc
> > parport vmmon nfs lockd sunrpc snd_seq_midi snd_emu10k1_synth
> > snd_emux_synth snd_seq_virmidi snd_seq_midi_emul snd_pcm_oss
> > snd_mixer_oss snd_seq_oss snd_seq_midi_event snd_seq snd_hda_intel
> > snd_hda_codec snd_emu10k1 snd_rawmidi snd_ac97_codec snd_ac97_bus
> > snd_pcm snd_seq_device snd_timer snd_page_alloc snd_util_mem
> > snd_hwdep snd soundcore binfmt_misc ntfs usblp ide_cd cdrom nvidia
> > e100 mii uhci_hcd ehci_hcdCPU:0
> > EIP:0060:[]Tainted: P VLI
> > EFLAGS: 00210282 (2.6.16.1 #1)
> > EIP is at get_exclusive_access+0x1c/0x3d
> > eax: df21b5dc ebx: 0001 ecx: df21b654 edx: c50e17d4
> > esi: acb2e000 edi: c50e1780 ebp: esp: e4481f30
> > ds: 007b es: 007b ss: 0068
> > Process soffice.bin (pid: 21440, threadinfo=e448 task=dc5bfa90)
> > Stack: <0>c01c56f4 df21b5dc c013ff95 c253a7ac dda673c0 0001
> > 37c2
> >df21b5dc df21b654 5058c680 e32c4680 acb2e000 e4481fa4 37c2
> > c014c900
> >e32c4680 acb2e000 37c2 e4481fa4 e32c4680 fff7 bf823d43
> > e448
> > Call Trace:
> > [] write_unix_file+0x2a6/0x45c
> > [] vma_link+0xbe/0xc5
> > [] vfs_write+0x87/0x11b
> > [] sys_write+0x3b/0x63
> > [] sysenter_past_esp+0x54/0x75
> > Code: 8d 43 14 e8 0b 38 13 00 e9 d1 fc ff ff 90 90 ba 00 e0 ff ff 21
> > e2 8b 12 8b 92 c4 04 00 00 8b 44 24 04 8b 52 50 83 7a 10 00 74 08
> > <0f> 0b 1d 00 60 b8 31 c0 ba 01 00 ff ff f0 0f c1 10 85 d2 0f 85
> >
> >
> >
> >
> > !DSPAM:443b3e85155598791294130!
>
> --
> Alex.
>
Is this the same bug? And if so can you please provide a patch against
the current 'stable' patch at the ftp?
[ cut here ]
kernel BUG at /usr/src/linux-stable/fs/reiser4/plugin/file/tail_conversion.c:29!
invalid opcode: [#1]
PREEMPT
Modules linked in: ipt_MASQUERADE ipt_LOG ipt_TOS ipt_TCPMSS xt_tcpudp
ipt_tos iptable_mangle ip_nat_ftp xt_tcpmss iptable_nat ip_nat
iptable_filter ipt_multiport xt_state xt_limit xt_conntrack
ip_conntrack_ftp ip_conntrack ip_tables x_tables snd_seq_midi
snd_emu10k1_synth snd_emux_synth snd_seq_virmidi snd_seq_midi_event
snd_seq_midi_emul snd_seq snd_emu10k1 snd_rawmidi snd_ac97_codec
snd_ac97_bus snd_pcm snd_seq_device snd_timer snd_page_alloc
snd_util_mem snd_hwdep snd
CPU:0
EIP:0060:[]Not tainted VLI
EFLAGS: 00010286 (2.6.16.2-reiser4 #5)
EIP is at get_exclusive_access+0x1a/0x3c
eax: c2c9c344 ebx: ecx: d43c9354 edx: b53b7000
esi: c01b46a2 edi: 2000 ebp: 2000 esp: d2f15f34
ds: 007b es: 007b ss: 0068
Process apache2 (pid: 24045, threadinfo=d2f15000 task=c65b30b0)
Stack: <0>c01b4964 b53b7000 ce37b280 d9108340 c2c9c300 d43c93ac
d43c9354
2000 0001 0005 d43c9300 d43c9360 2000 473b7000
ce37b280 c01b46a2 b53b7000 2000 c014712c d2f15fa4 ce37b280 fff7
Call Trace:
[] write_unix_file+0x2c2/0x4cd
[] write_unix_file+0x0/0x4cd
[] vfs_write+0xa1/0x140
[] sys_write+0x3c/0x63
[] sysenter_past_esp+0x54/0x75
Code: ff c7 04 9e 00 00 00 00 43 39 fb 75 e8 5b 5e 5f c3 89 c1 b8 00
f0 ff ff 21 e0 8b 00 8b 80 b4 04 00 00 8b 40 40 83 78 08 00 74 08 <0f>
0b 1d 00 00 f3 32 c0 ba 01 00 ff ff 89 c8 0f c1 10 85 d2 0f
<4><4>reiser4[apache2(24045)]: release_unix_file
(/usr/src/linux-stable/fs/reiser4/plug
RE: reiser4 bug
The patch posted works for me. I would concur with Michael on this one. For some reason openoffice triggered it with my problem. This is a bad area to have data loss and I imagine I wouldn't be the first to lose a document from this bug. It doesn't leave an inconsistent filesystem, but it does lock the current filesystem down (and prevents your document from being saved). Would definitely recommend you guys release a reiser4-for-2.6.16-2 patch and zap -1. Thanks for the quick reply though with the fix -- saved me additional troubles. Regards, Matthew > Original Message ---- > Subject: Re: reiser4 bug > From: Michael Weissenbacher <[EMAIL PROTECTED]> > Date: Tue, April 11, 2006 4:27 am > To: reiserfs-list@namesys.com > Cc: Alexander Zarochentsev <[EMAIL PROTECTED]> > > Hi, > > it is known problem. Fixed in 2.6.17-rc1-mm2 > > (reiser4-have-get_exclusive_access-restart-transaction.patch). > as i've been burned by this bug, too i would suggest making a new patch > for 2.6.16 including > reiser4-have-get_exclusive_access-restart-transaction.patch > or at least put a warning there that the version is unstable. i'm sure > most people go straight for the vanilla kernel patch and don't bother > with mm-kernels. this puts reiser4 in a bad light imo. > > kind regards, > Michael > -- > /\ > | Michael Weissenbacher <[EMAIL PROTECTED]> | > | http://www.dermichi.com/ | > | Email users are divided into two classes;| > | 1) Those who have effective spam-blocking| > | 2) Those who wish they did | > \/
Re: reiser4 bug
On Tuesday 11 April 2006 12:54, Avuton Olrich wrote:
> On 4/10/06, Alexander Zarochentsev <[EMAIL PROTECTED]> wrote:
> > On Tuesday 11 April 2006 09:28, Matt Eaton wrote:
> > > I was running OpenOffice and tried saving a file.
> > >
> > > I'm using 2.6.16.1 + reiser4-for-2.6.16-1.patch.gz
> > >
> > > (Please help! I'm having to run openoffice on a different
> > > filesystem as this crash has occurred twice saving the same file
> > > - after a reboot)
> > >
> > > kernel BUG at fs/reiser4/plugin/file/tail_conversion.c:29!
> > > invalid opcode: [#1]
> >
> > it is known problem. Fixed in 2.6.17-rc1-mm2
> > (reiser4-have-get_exclusive_access-restart-transaction.patch).
> >
> > I am afraid the patch from mm would not apply cleanly to 2.6.16.1 +
> > reiser4-for-2.6.16-1.patch,
> > you may try to apply only the following hunk:
> >
> > @@ -20,13 +20,12 @@ void get_exclusive_access(unix_file_info
> > assert("nikita-3047", LOCK_CNT_NIL(inode_sem_w));
> > assert("nikita-3048", LOCK_CNT_NIL(inode_sem_r));
> > /*
> > -* "deadlock detection": sometimes we commit a transaction
> > under +* "deadlock avoidance": sometimes we commit a
> > transaction under * rw-semaphore on a file. Such commit can
> > deadlock with another * thread that captured some block (hence
> > preventing atom from being
> > * committed) and waits on rw-semaphore.
> > */
> > - assert("nikita-3361", get_current_context()->trans->atom ==
> > NULL);
> > - BUG_ON(get_current_context()->trans->atom != NULL);
> > + txn_restart_current();
> > LOCK_CNT_INC(inode_sem_w);
> > down_write(&uf_info->latch);
> > uf_info->exclusive_use = 1;
> > _
> >
> > > PREEMPT SMP
> > > Modules linked in: eeprom lm85 hwmon_vid i2c_i801 lp vmnet
> > > parport_pc parport vmmon nfs lockd sunrpc snd_seq_midi
> > > snd_emu10k1_synth snd_emux_synth snd_seq_virmidi
> > > snd_seq_midi_emul snd_pcm_oss snd_mixer_oss snd_seq_oss
> > > snd_seq_midi_event snd_seq snd_hda_intel snd_hda_codec
> > > snd_emu10k1 snd_rawmidi snd_ac97_codec snd_ac97_bus snd_pcm
> > > snd_seq_device snd_timer snd_page_alloc snd_util_mem snd_hwdep
> > > snd soundcore binfmt_misc ntfs usblp ide_cd cdrom nvidia e100 mii
> > > uhci_hcd ehci_hcdCPU:0
> > > EIP:0060:[]Tainted: P VLI
> > > EFLAGS: 00210282 (2.6.16.1 #1)
> > > EIP is at get_exclusive_access+0x1c/0x3d
> > > eax: df21b5dc ebx: 0001 ecx: df21b654 edx: c50e17d4
> > > esi: acb2e000 edi: c50e1780 ebp: esp: e4481f30
> > > ds: 007b es: 007b ss: 0068
> > > Process soffice.bin (pid: 21440, threadinfo=e448
> > > task=dc5bfa90) Stack: <0>c01c56f4 df21b5dc c013ff95 c253a7ac
> > > dda673c0 0001 37c2
> > >df21b5dc df21b654 5058c680 e32c4680 acb2e000 e4481fa4
> > > 37c2 c014c900
> > >e32c4680 acb2e000 37c2 e4481fa4 e32c4680 fff7
> > > bf823d43 e448
> > > Call Trace:
> > > [] write_unix_file+0x2a6/0x45c
> > > [] vma_link+0xbe/0xc5
> > > [] vfs_write+0x87/0x11b
> > > [] sys_write+0x3b/0x63
> > > [] sysenter_past_esp+0x54/0x75
> > > Code: 8d 43 14 e8 0b 38 13 00 e9 d1 fc ff ff 90 90 ba 00 e0 ff ff
> > > 21 e2 8b 12 8b 92 c4 04 00 00 8b 44 24 04 8b 52 50 83 7a 10 00 74
> > > 08 <0f> 0b 1d 00 60 b8 31 c0 ba 01 00 ff ff f0 0f c1 10 85 d2 0f
> > > 85
> >
> > --
> > Alex.
>
> Is this the same bug? And if so can you please provide a patch
yes.
> against the current 'stable' patch at the ftp?
ftp://ftp.namesys.com/pub/reiser4-for-2.6/2.6.16/reiser4-for-2.6.16-2.patch.gz
>
> [ cut here ]
> kernel BUG at
> /usr/src/linux-stable/fs/reiser4/plugin/file/tail_conversion.c:29!
> invalid opcode: [#1]
> PREEMPT
> Modules linked in: ipt_MASQUERADE ipt_LOG ipt_TOS ipt_TCPMSS
> xt_tcpudp ipt_tos iptable_mangle ip_nat_ftp xt_tcpmss iptable_nat
> ip_nat iptable_filter ipt_multiport xt_state xt_limit xt_conntrack
> ip_conntrack_ftp ip_conntrack ip_tables x_tables snd_seq_midi
> snd_emu10k1_synth snd_emux_synth snd_seq_virmidi snd_seq_midi_event
> snd_seq_midi_emul snd_seq snd_emu10k1 snd_rawmidi snd_ac97_codec
> snd_ac97_bus snd_pcm snd_seq_device snd_timer snd_page_alloc
> snd_util_mem snd_hwdep snd
> CPU:0
> EIP:0060:[]Not tainted VLI
> EFLAGS: 00010286 (2.6.16.2-reiser4 #5)
> EIP is at get_exclusive_access+0x1a/0x3c
> eax: c2c9c344 ebx: ecx: d43c9354 edx: b53b7000
> esi: c01b46a2 edi: 2000 ebp: 2000 esp: d2f15f34
> ds: 007b es: 007b ss: 0068
> Process apache2 (pid: 24045, threadinfo=d2f15000 task=c65b30b0)
> Stack: <0>c01b4964 b53b7000 ce37b280 d9108340 c2c9c300 d43c93ac
> d43c9354
>2000 0001 0005 d43c9300 d43c9360 2000
> 473b7000 ce37b280 c01b46a2 b53b7000 2000 c014712c d2f15fa4
> ce37b280 fff7 Call Trace:
> [] write_unix_file+0x2c2/0x4cd
> [] write_unix_file+0x0/0x4cd
> [] vfs_write+0xa1/0x140
> [] sys_write+0x3c/0x63
> [] sysenter_past_esp+0x54/0x75
Re: reiser4 bug in 2.6.16-rc2-mm1
On Friday 10 February 2006 09:22, Maarten Deprez wrote:
> Hello,
>
> reiser4 on linux 2.6.16-rc2-mm1 bugs for me in
> plugins/file/tail_conversion.c line 29, locking up a process
> sometimes, when it is reading a file.
>
> Greetings,
> Maarten Deprez
>
>
Still present in 2.6.16-rc3-mm1:
[ cut here ]
kernel BUG at fs/reiser4/plugin/file/tail_conversion.c:81!
invalid opcode: [#1]
PREEMPT
last sysfs file: /devices/pci:00/:00:01.0/:01:00.0/i2c-0/name
CPU:0
EIP:0060:[get_nonexclusive_access+30/49]Not tainted VLI
EFLAGS: 00010286 (2.6.16-rc3-mm1 #2)
EIP is at get_nonexclusive_access+0x1e/0x31
eax: cc2ec288 ebx: ecx: cb87d4e8 edx:
esi: cb87d4e8 edi: ebp: d30ba574 esp: d3934e00
ds: 007b es: 007b ss: 0068
Process kmail (pid: 21299, threadinfo=d3934000 task=d8577570)
Stack: <0>c01ca9ae d94d157c d3934ed8 cb87d540 000f 00320af1
df136ef4 f000 d20b2494 1000 d94d158c
0127 43f543c8 2ac0f373 d94d158c
Call Trace:
write_extent+0x68d/0xbc3item_length_by_coord+0xb/0xf
nr_units_extent+0x5/0xd
init_coord_extension_extent+0x60/0xdf
set_file_state+0x26/0x5bfind_file_item+0xc2/0xd4
write_extent+0x0/0xbc3write_flow+0x248/0x2df
write_unix_file+0x343/0x4cc
lru_cache_add_active+0x47/0x5d
write_unix_file+0x0/0x4ccvfs_write+0x83/0x122
sys_write+0x3c/0x63sysenter_past_esp+0x54/0x75
Code: 81 c4 b0 00 00 00 89 e8 5b 5e 5f 5d c3 85 d2 89 c1 75 20 b8 00 f0 ff ff
21 e0 8b 00 8b 80 c4 04 00 00 8b 40 40 83 78 08 00 74 08 <0f> 0b 51 00 b8 b8 38
c0 89 c8 ff 00 0f 88 e1 06 00 00 c3 55 ba
<4><4>reiser4[kmail(21299)]: release_unix_file
(fs/reiser4/plugin/file/file.c:2674)[vs-44]:
WARNING: out of memory?
<4>reiser4[kmail(21299)]: release_unix_file
(fs/reiser4/plugin/file/file.c:2674)[vs-44]:
WARNING: out of memory?
...
Re: reiser4 bug in 2.6.16-rc2-mm1
Is there a known issue with 2.6.16-xxx-mm1? I too am having severe and very random, but reproducible problems which will completely lock up my machine minutes after mounting an R4 partition if not seconds. I did try disabling 4K stacks in my .config. Also, this is an Athlon 64 X2 I'm running with so maybe there are SMP issues? One of my friends said that Reiser4 became unstable for him also when he upgraded to a dual core Athlon64...but until I test for myself that's just a wild theory that it's an SMP bug. This machine is otherwise stable in Memtest, in Windows playing the latest games, and on Linux compiling huge amounts of software. If there are not known issues with the latest kernels then I will happily try to send detailed configurations and logs of what's happening this evening. I have two shiny new 250GB SATA drives on my machine and I can test freely with one of them until I need the space. I'd love to help squash any bugs that I can :) On 2/16/06, Andrew James Wade <[EMAIL PROTECTED]> wrote: On Friday 10 February 2006 09:22, Maarten Deprez wrote:> Hello,>> reiser4 on linux 2.6.16-rc2-mm1 bugs for me in> plugins/file/tail_conversion.c line 29, locking up a process> sometimes, when it is reading a file. >> Greetings,> Maarten Deprez>>Still present in 2.6.16-rc3-mm1:[ cut here ]kernel BUG at fs/reiser4/plugin/file/tail_conversion.c:81!invalid opcode: [#1] PREEMPTlast sysfs file: /devices/pci:00/:00:01.0/:01:00.0/i2c-0/nameCPU:0EIP:0060:[get_nonexclusive_access+30/49]Not tainted VLIEFLAGS: 00010286 (2.6.16-rc3-mm1 #2)EIP is at get_nonexclusive_access+0x1e/0x31 eax: cc2ec288 ebx: ecx: cb87d4e8 edx: esi: cb87d4e8 edi: ebp: d30ba574 esp: d3934e00ds: 007b es: 007b ss: 0068Process kmail (pid: 21299, threadinfo=d3934000 task=d8577570) Stack: <0>c01ca9ae d94d157c d3934ed8 cb87d540 000f 00320af1 df136ef4 f000 d20b2494 1000 d94d158c 0127 43f543c8 2ac0f373 d94d158c Call Trace: write_extent+0x68d/0xbc3 item_length_by_coord+0xb/0xf nr_units_extent+0x5/0xd init_coord_extension_extent+0x60/0xdf set_file_state+0x26/0x5b find_file_item+0xc2/0xd4 write_extent+0x0/0xbc3 write_flow+0x248/0x2df write_unix_file+0x343/0x4cc lru_cache_add_active+0x47/0x5d write_unix_file+0x0/0x4cc vfs_write+0x83/0x122 sys_write+0x3c/0x63 sysenter_past_esp+0x54/0x75Code: 81 c4 b0 00 00 00 89 e8 5b 5e 5f 5d c3 85 d2 89 c1 75 20 b8 00 f0 ff ff 21 e0 8b 00 8b 80 c4 04 00 00 8b 40 40 83 78 08 00 74 08 <0f> 0b 51 00 b8 b8 38 c0 89 c8 ff 00 0f 88 e1 06 00 00 c3 55 ba <4><4>reiser4[kmail(21299)]: release_unix_file (fs/reiser4/plugin/file/file.c:2674)[vs-44]:WARNING: out of memory?<4>reiser4[kmail(21299)]: release_unix_file (fs/reiser4/plugin/file/file.c:2674)[vs-44]: WARNING: out of memory?...
Re: reiser4 bug in 2.6.16-rc2-mm1
Hello On Fri, 2006-02-17 at 10:43 -0600, John Cohorn wrote: > Is there a known issue with 2.6.16-xxx-mm1? I too am having severe and > very random, but reproducible problems which will completely lock up > my machine minutes after mounting an R4 partition if not seconds. I > did try disabling 4K stacks in my .config. Also, this is an Athlon 64 > X2 I'm running with so maybe there are SMP issues? no, it does not look so. > One of my friends said that Reiser4 became unstable for him also when > he upgraded to a dual core Athlon64...but until I test for myself > that's just a wild theory that it's an SMP bug. This machine is > otherwise stable in Memtest, in Windows playing the latest games, and > on Linux compiling huge amounts of software. > > If there are not known issues with the latest kernels then I will > happily try to send detailed configurations and logs of what's > happening this evening. I have two shiny new 250GB SATA drives on my > machine and I can test freely with one of them until I need the space. > I'd love to help squash any bugs that I can :) > If you described the exact sequence of commands which makes reiser4 to crash - that would help a lot.
Re: reiser4 bug in 2.6.16-rc2-mm1
First off, thank you for taking the time to respond. Basically any heavy activity on the partition seems to trigger it. Here's a short transcript:dually ~ # cat /proc/versionLinux version 2.6.16-rc2-mm1 ([EMAIL PROTECTED]) (gcc version 3.3.6 (Gentoo 3.3.6, ssp-3.3.6-1.0, pie-8.7.8)) #7 SMP PREEMPT Thu Feb 16 21:19:53 Local time zone must be set--dually ~ # mkfs.reiser4 --versionmkfs.reiser4 1.0.5Copyright (C) 2001, 2002, 2003, 2004 by Hans Reiser, licensing governed by reiser4progs/COPYING. dually ~ # mkfs.reiser4 /dev/sdb1 --yesdually ~ # mount /dev/sdb1 /data1 dually ~ # klogd -d -f ~/kernel.logdually ~ # cd /data1dually data1 # cp -ra /usr/src/linux-2.6.16-rc2-mm1/ .dually data1 # tar cf linux.bz2 linux-2.6.16-rc2-mm1/...after about half a minute of activity I receive the message which I've attached as a small JPEG "reiser4 panicked cowardly: reiser4[tar(4078)] commit_current_atom (fs/reiser4/txnmgr.c:1130) [zam-597]:". I can't see whether it was line 1130 or 1138. I'll take a quick look myself, but I'm completely unfamiliar with reiser4 sources and the kernel sources in general. After this my system is completely locked up. When I mount the partition after restarting it no longer contains any files. I have few or no problems when creating, mounting, and working on reiser4 partitions when booted from the System recovery liveCD so it must be something in the latest sources or in my kernel configuration(which is 100% stable for everything else under reiser3, but I haven't bothered to perfect yet). Apologies about the JPEG, I could not figure out how to get the kernel output logged into a file(maybe it freezes before the file can flush to disk, i dunno). If you know of a way, I welcome instruction. On 2/21/06, Vladimir V. Saveliev <[EMAIL PROTECTED]> wrote: HelloOn Fri, 2006-02-17 at 10:43 -0600, John Cohorn wrote:> Is there a known issue with 2.6.16-xxx-mm1? I too am having severe and> very random, but reproducible problems which will completely lock up > my machine minutes after mounting an R4 partition if not seconds. I> did try disabling 4K stacks in my .config. Also, this is an Athlon 64> X2 I'm running with so maybe there are SMP issues? no, it does not look so.> One of my friends said that Reiser4 became unstable for him also when> he upgraded to a dual core Athlon64...but until I test for myself> that's just a wild theory that it's an SMP bug. This machine is > otherwise stable in Memtest, in Windows playing the latest games, and> on Linux compiling huge amounts of software.>> If there are not known issues with the latest kernels then I will> happily try to send detailed configurations and logs of what's > happening this evening. I have two shiny new 250GB SATA drives on my> machine and I can test freely with one of them until I need the space.> I'd love to help squash any bugs that I can :)> If you described the exact sequence of commands which makes reiser4 tocrash - that would help a lot.
Re: reiser4 bug in 2.6.16-rc2-mm1
Hello On Tue, 2006-02-21 at 19:58 -0600, John Cohorn wrote: > First off, thank you for taking the time to respond. > > Basically any heavy activity on the partition seems to trigger it. > Here's a short transcript: > > dually ~ # cat /proc/version > Linux version 2.6.16-rc2-mm1 ([EMAIL PROTECTED]) (gcc version 3.3.6 > (Gentoo 3.3.6, ssp-3.3.6-1.0, pie-8.7.8)) #7 SMP PREEMPT Thu Feb 16 > 21:19:53 Local time zone must be set-- > dually ~ # mkfs.reiser4 --version > mkfs.reiser4 1.0.5 > Copyright (C) 2001, 2002, 2003, 2004 by Hans Reiser, licensing > governed by > reiser4progs/COPYING. > dually ~ # mkfs.reiser4 /dev/sdb1 --yes > dually ~ # mount /dev/sdb1 /data1 > dually ~ # klogd -d -f ~/kernel.log > dually ~ # cd /data1 > dually data1 # cp -ra /usr/src/linux-2.6.16-rc2-mm1/ . > dually data1 # tar cf linux.bz2 linux-2.6.16-rc2-mm1/ > > ...after about half a minute of activity I receive the message which > I've attached as a small JPEG > "reiser4 panicked cowardly: reiser4[tar(4078)] commit_current_atom > (fs/reiser4/txnmgr.c:1130) [zam-597]:". Would you please try your test on ide disk? > I can't see whether it was line 1130 or 1138. I'll take a quick look > myself, but I'm completely unfamiliar with reiser4 sources and the > kernel sources in general. > > After this my system is completely locked up. When I mount the > partition after restarting it no longer contains any files. I have few > or no problems when creating, mounting, and working on reiser4 > partitions when booted from the System recovery liveCD so it must be > something in the latest sources or in my kernel configuration IIRC, there were changes (not in reiser4) which caused kernel to notice i/o errors on SCSI devices where older kernels did not see any problems. > (which is 100% stable for everything else under reiser3, but I haven't > bothered to perfect yet). > > Apologies about the JPEG, I could not figure out how to get the kernel > output logged into a file(maybe it freezes before the file can flush > to disk, i dunno). If you know of a way, I welcome instruction. > reiserfs-list@namesys.com does not accept binary attachments. Please send the image to [EMAIL PROTECTED] and [EMAIL PROTECTED] You should setup either serial or netconsole to catch kernel output. Please look at instructions: linux/Documentation/serial-console.txt linux/Documentation/networking/netconsole.txt
Re: reiser4 bug in 2.6.16-rc2-mm1
Sorry for the delay.On 2/22/06, Vladimir V. Saveliev <[EMAIL PROTECTED]> wrote: HelloOn Tue, 2006-02-21 at 19:58 -0600, John Cohorn wrote:> First off, thank you for taking the time to respond.>> Basically any heavy activity on the partition seems to trigger it.> Here's a short transcript: >> dually ~ # cat /proc/version> Linux version 2.6.16-rc2-mm1 ([EMAIL PROTECTED]) (gcc version 3.3.6> (Gentoo 3.3.6, ssp-3.3.6-1.0, pie-8.7.8)) #7 SMP PREEMPT Thu Feb 16> 21:19:53 Local time zone must be set-- > dually ~ # mkfs.reiser4 --version> mkfs.reiser4 1.0.5> Copyright (C) 2001, 2002, 2003, 2004 by Hans Reiser, licensing> governed by> reiser4progs/COPYING.> dually ~ # mkfs.reiser4 /dev/sdb1 --yes> dually ~ # mount /dev/sdb1 /data1> dually ~ # klogd -d -f ~/kernel.log> dually ~ # cd /data1> dually data1 # cp -ra /usr/src/linux-2.6.16-rc2-mm1/ .> dually data1 # tar cf linux.bz2 linux-2.6.16-rc2-mm1/>> ...after about half a minute of activity I receive the message which> I've attached as a small JPEG> "reiser4 panicked cowardly: reiser4[tar(4078)] commit_current_atom > (fs/reiser4/txnmgr.c:1130) [zam-597]:".Would you please try your test on ide disk?At your suggestion I plugged in a spare PATA IDE disk, formatted it with R4, and was about to copy several copies of the Linux kernel sources to the partition, tar them up, and move them around with no lockups or apparent corruption. > I can't see whether it was line 1130 or 1138. I'll take a quick look > myself, but I'm completely unfamiliar with reiser4 sources and the> kernel sources in general.>> After this my system is completely locked up. When I mount the> partition after restarting it no longer contains any files. I have few > or no problems when creating, mounting, and working on reiser4> partitions when booted from the System recovery liveCD so it must be> something in the latest sources or in my kernel configuration IIRC, there were changes (not in reiser4) which caused kernel to noticei/o errors on SCSI devices where older kernels did not see any problems.Reiser3 is completely stable on my SATA drives...is R4 simply doing more error checking? Why should even a severe I/O error completely freeze my machine? So it seems as though the problem is in the interaction between R4 and the SCSI code...are any workarounds to this apparent? > (which is 100% stable for everything else under reiser3, but I haven't> bothered to perfect yet).>> Apologies about the JPEG, I could not figure out how to get the kernel> output logged into a file(maybe it freezes before the file can flush > to disk, i dunno). If you know of a way, I welcome instruction.>reiserfs-list@namesys.com does not accept binary attachments. Pleasesend the image to [EMAIL PROTECTED] and [EMAIL PROTECTED]done. You should setup either serial or netconsole to catch kernel output.Please look at instructions:linux/Documentation/serial-console.txtlinux/Documentation/networking/netconsole.txt Thanks for the suggestions. I'll see if I can set up logging kernel messages to my laptop.
Re: reiser4 bug [was Re: 2.6.17-rc3-mm1]
Try the patch from here: http://marc.theaimsgroup.com/?l=reiserfs&m=114709188305181&w=2 That helped me get past the bootup phase (currently 8 hours uptime). -Joe Alexander Gran writes: Hi all, 2.6.17-rc3-mm1 doesn't get up running here, it bugs around while init runs: I cannot login afterwards, and syslog did not get the bug too. So here are some poor screenshots from my Treo650 (digicam is broken, sorry..;) EIP is in clear_inode. Trace: reiser4_delete_inode+0x6c/0xd0 d_delete+0xf0/0x10f reiser4_delete_inode+0x0/0xd0 generic_delete_inode+0x6b/0xfb input+0x5c/0x68 do_unlikat+0xd7/0x12c sysenter_past_esp+0x54/0x75 __hidp_send_ctrl_message+0xb4/0xfa details: http://zodiac.dnsalias.org/images/1.jpg http://zodiac.dnsalias.org/images/2.jpg http://zodiac.dnsalias.org/images/3.jpg http://zodiac.dnsalias.org/images/4.jpg Kernel config: http://zodiac.dnsalias.org/images/config System is my T40p, as usual. running an up2date debian unstable. regards Alex
Re: reiser4 bug [was Re: 2.6.17-rc3-mm1]
Nope, did not work... regards Alex Am Dienstag, 9. Mai 2006 01:21 schrieb Joe Feise: > Try the patch from here: > http://marc.theaimsgroup.com/?l=reiserfs&m=114709188305181&w=2 > That helped me get past the bootup phase (currently 8 hours uptime). > > -Joe > > Alexander Gran writes: > > Hi all, > > > > 2.6.17-rc3-mm1 doesn't get up running here, it bugs around while init > > runs: I cannot login afterwards, and syslog did not get the bug too. So > > here are some poor screenshots from my Treo650 (digicam is broken, > > sorry..;) EIP is in clear_inode. > > Trace: > > reiser4_delete_inode+0x6c/0xd0 > > d_delete+0xf0/0x10f > > reiser4_delete_inode+0x0/0xd0 > > generic_delete_inode+0x6b/0xfb > > input+0x5c/0x68 > > do_unlikat+0xd7/0x12c > > sysenter_past_esp+0x54/0x75 > > __hidp_send_ctrl_message+0xb4/0xfa > > details: > > http://zodiac.dnsalias.org/images/1.jpg > > http://zodiac.dnsalias.org/images/2.jpg > > http://zodiac.dnsalias.org/images/3.jpg > > http://zodiac.dnsalias.org/images/4.jpg > > Kernel config: > > http://zodiac.dnsalias.org/images/config > > System is my T40p, as usual. running an up2date debian unstable. > > > > regards > > Alex -- Encrypted Mails welcome. PGP-Key at http://zodiac.dnsalias.org/misc/pgpkey.asc | Key-ID: 0x6D7DD291 pgp043lcmFacP.pgp Description: PGP signature
