Description of problem: First ... as this is an old machine (single p3/600, 440GX board, 512mb ecc ram) it is entirely possible that this is a hardware problem. I'm reporting it just in case it is not ... This machine has 4 scsi disks configured in two md mirrors and lvm2 on top of them. This volume is then split in logical volumes for /, /var and /home (/boot is dedicated small mirror at the beginning of the first two disks). While doing a bonnie++ run on /home, I started a small compile (powerdns) on / and was soon greeted with this oops: Jun 6 13:18:03 klotilda kernel: Assertion failure in __journal_remove_journal_ head() at fs/jbd/journal.c:1772: "buffer_jbd(bh)" Jun 6 13:18:03 klotilda kernel: ------------[ cut here ]------------ Jun 6 13:18:03 klotilda kernel: kernel BUG at fs/jbd/journal.c:1772! Jun 6 13:18:03 klotilda kernel: invalid operand: 0000 [#1] Jun 6 13:18:03 klotilda kernel: Modules linked in: parport_pc lp parport md5 ipv6 autofs4 i2c_dev i2c_core sunrpc uhci_hcd e100 mii floppy sg dm_snapshot dm_zero dm_mirror ext3 jbd raid1 dm_mod aic7xxx sd_mod scsi_mod Jun 6 13:18:03 klotilda kernel: CPU: 0 Jun 6 13:18:03 klotilda kernel: EIP: 0060:[<e08bb7f0>] Not tainted VLI Jun 6 13:18:03 klotilda kernel: EFLAGS: 00010212 (2.6.9-34.0.1.EL) Jun 6 13:18:03 klotilda kernel: EIP is at __journal_remove_journal_head+0x86/0x 120 [jbd] Jun 6 13:18:03 klotilda kernel: eax: 00000063 ebx: d6d307dc ecx: e08bd 080 edx: dfcf8e00 Jun 6 13:18:03 klotilda kernel: esi: caeed48c edi: d6d307dc ebp: caeed48 c esp: dfcf8dfc Jun 6 13:18:03 klotilda kernel: ds: 007b es: 007b ss: 0068 Jun 6 13:18:03 klotilda kernel: Process kswapd0 (pid: 34, threadinfo=dfcf8000 task=dfdcc620) Jun 6 13:18:03 klotilda kernel: Stack: e08bd080 e08bbd97 e08bcfcc 000006ec e08 bd5a8 caeed48c d6d307dc e08bb926 Jun 6 13:18:03 klotilda kernel: caeed48c c101c8a0 e08b3b4b 00000000 c14f 0c00 e08ec9c0 000000d0 dac7da60 Jun 6 13:18:03 klotilda kernel: dfcf8f58 c016bf06 dac7da60 c101c8a0 c 015327d 00000001 00000001 00000002 Jun 6 13:18:03 klotilda kernel: Call Trace: Jun 6 13:18:03 klotilda kernel: [<e08bb926>] journal_put_journal_head+0x64/0x 83 [jbd] Jun 6 13:18:03 klotilda kernel: [<e08b3b4b>] journal_try_to_free_buffers+0x8c/ 0xc3 [jbd] Jun 6 13:18:03 klotilda kernel: [<e08ec9c0>] ext3_releasepage+0x0/0x54 [ext3] Jun 6 13:18:03 klotilda kernel: [<c016bf06>] try_to_release_page+0x34/0x46 Jun 6 13:18:03 klotilda kernel: [<c015327d>] shrink_list+0x294/0x4ea Jun 6 13:18:03 klotilda kernel: [<c01536d2>] shrink_cache+0x1ff/0x454 Jun 6 13:18:03 klotilda kernel: [<c0152d91>] shrink_slab+0x7d/0x14c Jun 6 13:18:03 klotilda kernel: [<c015408c>] shrink_zone+0x8f/0x9e Jun 6 13:18:03 klotilda kernel: [<c015442f>] balance_pgdat+0x197/0x2cb Jun 6 13:18:03 klotilda kernel: [<c015461c>] kswapd+0xb9/0xbb Jun 6 13:18:03 klotilda kernel: [<c011e867>] autoremove_wake_function+0x0/0x2d Jun 6 13:18:04 klotilda kernel: [<c031139a>] ret_from_fork+0x6/0x14 Jun 6 13:18:04 klotilda kernel: [<c011e867>] autoremove_wake_function+0x0/0x2d Jun 6 13:18:04 klotilda kernel: [<c0154563>] kswapd+0x0/0xbb Jun 6 13:18:04 klotilda kernel: [<c01041dd>] kernel_thread_helper+0x5/0xb Jun 6 13:18:04 klotilda kernel: Code: 0f 85 bc 00 00 00 8b 06 f6 c4 20 75 29 68 a8 d5 8b e0 68 ec 06 00 00 68 cc cf 8b e0 68 97 bd 8b e0 68 80 d0 8b e0 e8 21 61 86 df <0f> 0b ec 06 cc cf 8b e0 83 c4 14 39 33 74 29 68 b7 d5 8b e0 68 Version-Release number of selected component (if applicable): kernel 2.6.9-34.0.1.EL on rhel4 with all recent updates How reproducible: Not sure yet if this is reproducible. If it is a hardware problem, I guess I'll see more weird behaviour ... but if it is not, I hope I'll get more of the same. Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: Memtest86 runs on this machie for 24h without any errors.
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. Please See https://access.redhat.com/support/policy/updates/errata/ If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.