I am not entirely sure if it's the kernel itself, or this particular machine, because this is the only computer I keep constantly on. It's been crashing annoyingly frequently, tends to crash once a week or so. I found this in the logs, in case it helps log-2005-02-26-19:22:42:Feb 23 12:47:24 [kernel] ReiserFS: warning: is_leaf: item location seems wrong (second one): *3.6*[54957 54959 0x1 DIRECT], item_len 176, item_location 2340, free_space(entry_count) 65535 I ran reiserfsck on all partitions, just in case, no errors found. When it happened my ssh connection hung, but I could log in successfully from the console. I copied the oops by hand, then tried to redirect dmesg to a file. Then I ran sync, which also hung. However, the data seems to have been saved. Reproducible: Sometimes Steps to Reproduce: Unknown Unable to handle kernel paging request at virtual address 0009b909 printing eip: 0009b909 *pde = 00000000 Oops: 0000 [#1] PREEMPT Modules linked in: CPU: 0 EIP: 0060:[<0009b909>] Not tainted VLI EFLAGS: 00010286 (2.6.10-rc3no) EIP is at 0x9b909 eax: 00000000 ebx: 0009b909 ecx: c1777060 edx: c17776e0 esi: c1777060 edi: de8ea0d4 ebp: 00000000 esp: ddeacdfc ds: 007b es: 007b ss: 0068 Process pdflush (pid: 224, threadinfo=ddeac000 task=dde92060) Stack: ddc7f600 c01b9e68 ddc7f600 c1777060 00000286 ddeace38 00000286 de8ea068 00000000 00000001 de8ea000 00000000 ddc7f600 00000001 0009b909 00000000 c01bef27 ddc7f600 c1777060 00000001 00001000 ddc7f600 00002000 de8ea0d4 Call Trace: [<c01b9e68>] flush_commit_list+0x78/0x4e0 [<c01bef27>] do_journal_end+0x707/0xa90 [<c01bde45>] journal_end_sync+0x55/0xa0 [<c01a9877>] reiserfs_sync_fs+0x67/0x80 [<c015b851>] sync_supers+0xd1/0xe0 [<c013bb18>] wb_kupdate+0x28/0x110 [<c013c5da>] __pdflush+0xca/0x1d0 [<c013c6e0>] pdflush+0x0/0x30 [<c013c706>] pdflush+0x26/0x30 [<c013baf0>] wb_kupdate+0x0/0x110 [<c013c6e0>] pdflush+0x0/0x30 [<c012bd3a>] kthread+0xaa/0xb0 [<c012bc90>] kthread+0x0/0xb0 [<c01012cd>] kernel_thread_helper+0x5/0x18 Code: Bad EIP value.
Created attachment 52422 [details] kernel config
Vadim: That's not a supported kernel and bugs.g.o is not a help line. Please check your system with a stable kernel, and take your problem to lkml.org if necessary.
Ahh, my apologies. This kernel version was installed on request from Daniel Drake though, when he replied to another oops I reported on 2.6.9-gentoo-r4, in bug #73967. Must have forgotten to upgrade to a later version after that... I am also not entirely sure of the correct procedures here. I searched the list a bit, and there appear to be a number of oopses reported, so I assumed it was the right thing to do. Shall I report all kernel problems to LKML, even if they are the Gentoo ones, then? I wasn't entirely sure if I should report all kernel problems to LKML, or only ones that happen with the vanilla version. BTW, just to clarify things. Of course I expect to get no tech support here. I was merely providing all the information I could think of, meaning this is the only computer that runs for long, so I'm not entirely sure if this problem ever happens on other machines, or is specific to this one.
If you report a kernel bug here that I don't have any immediate idea at what may be causing it, I will simply ask you to test the latest release candidate, which is exactly what happened on bug #73967. If the latest -rc fixes it, I will try and locate the fix and backport it into our stable kernels. This is not always possible. If the latest -rc still contains the problem then I would just redirect you to post a bug at http://bugzilla.kernel.org If you wish to report kernel bugs here, then thats fine, just make sure you follow this: http://dev.gentoo.org/~dsd/gentoo-dev-sources/bugs.htm
