Hide Forgot
Hi! I have some FSC RX300S5 machine that crashed several times in the last weeks and I cannot really find the problem. So I installed crash kernel to get a bit more information before opening a bug report. Note, that I have _many_ RX300 machines running with RHEL5 and I don't see these troubles with the others. However, another note, this is the only machine that has KVM VMs running (3 of them). Here are the last lines of the kernel log - taken from the crash dump: Unable to handle kernel NULL pointer dereference at 00000000000003c8 RIP: [<ffffffff8868f380>] :bridge:__br_deliver+0xcd/0xfc PGD 0 Oops: 0000 [1] SMP last sysfs file: /devices/pci0000:00/0000:00:01.0/0000:01:00.0/vendor CPU 0 Modules linked in: tun ip6table_filter ip6_tables ebtable_nat ebtables nfsd exportfs nfs_acl auth_rpcgss mptctl mptbase autofs4 hidp smbus(U) ipmi_devintf ipmi_si ipmi_msghandler rfcomm l2cap bluetooth lockd sunrpc bonding ipt_REJECT xt_sta te xt_physdev bridge xt_tcpudp iptable_filter ipt_MASQUERADE iptable_nat ip_nat ip_conntrack nfnetlink ip_tables x_table s be2iscsi ib_iser rdma_cm ib_cm iw_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp bnx2i cnic ipv6 xfrm_nalgo crypto_api uio cxgb3i libcxgbi cxgb3 libiscsi_tcp libiscsi2 scsi_transport_iscsi2 scsi_transport_iscsi cpufreq_ondemand acpi_cpufreq fr eq_table mperf dm_multipath scsi_dh video backlight sbs power_meter hwmon i2c_ec dell_wmi wmi button battery asus_acpi a cpi_memhotplug ac parport_pc lp parport ksm(U) kvm_intel(U) kvm(U) sr_mod cdrom sg i2c_i801 i2c_core igb 8021q pcspkr dc a tpm_tis tpm tpm_bios dm_raid45 dm_message dm_region_hash dm_mem_cache dm_snapshot dm_zero dm_mirror dm_log dm_mod ata_ piix libata shpchp megaraid_sas sd_mod scsi_mod ext3 jbd uhci_hcd ohci_hcd ehci_hcd Pid: 3718, comm: syslogd Tainted: G ---- 2.6.18-274.el5 #1 RIP: 0010:[<ffffffff8868f380>] [<ffffffff8868f380>] :bridge:__br_deliver+0xcd/0xfc RSP: 0018:ffff810334641a88 EFLAGS: 00010246 RAX: 0000000000000000 RBX: ffff81063cf22500 RCX: 0000000000000002 RDX: ffff81032b6a4ac0 RSI: ffffffff80064a58 RDI: 0000000000000002 RBP: ffff81063cf22500 R08: ffff810335ad0ba0 R09: ffffffff8868ef95 R10: 0000000000000000 R11: ffffffff888c3720 R12: ffff81032b6a4b18 R13: ffffffff8035eae0 R14: ffff81063cf22000 R15: ffff810335a683c0 FS: 00002b43637446e0(0000) GS:ffffffff8042a000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b CR2: 00000000000003c8 CR3: 000000033448b000 CR4: 00000000000026a0 Process syslogd (pid: 3718, threadinfo ffff810334640000, task ffff81033f7be7a0) Stack: ffff810334641b28 ffff81032b6a4ac0 ffff81032b6a4ac0 ffffffff8868e294 ffff81033b832e60 ffff81032b6a4ac0 ffff81032b6a4ac0 ffffffff80236493 ffff81033b832e60 ffff81063cf22000 ffff81032b6a4ac0 ffffffff8035eae0 Call Trace: [<ffffffff8868e294>] :bridge:br_dev_xmit+0xc7/0xdb [<ffffffff80236493>] dev_hard_start_xmit+0x1b7/0x28a [<ffffffff8002f76f>] dev_queue_xmit+0x1f3/0x2a3 [<ffffffff80031e05>] ip_output+0x29a/0x2dd [<ffffffff80254a48>] ip_push_pending_frames+0x381/0x461 [<ffffffff80264f34>] udp_push_pending_frames+0x21e/0x243 [<ffffffff80052420>] udp_sendmsg+0x4d8/0x5ea [<ffffffff80054e98>] sock_sendmsg+0xf8/0x14a [<ffffffff8000ec2f>] find_get_pages_tag+0x34/0x89 [<ffffffff800a2e5d>] autoremove_wake_function+0x0/0x2e [<ffffffff80049d1d>] wait_on_page_writeback_range+0xdb/0x133 [<ffffffff8004f656>] finish_wait+0x32/0x5d [<ffffffff88036e29>] :jbd:log_wait_commit+0xb8/0xf5 [<ffffffff800a2e5d>] autoremove_wake_function+0x0/0x2e [<ffffffff8000ec2f>] find_get_pages_tag+0x34/0x89 [<ffffffff8022dbae>] sys_sendto+0x131/0x164 [<ffffffff800f64f4>] sync_inode+0x24/0x33 [<ffffffff8005d28d>] tracesys+0xd5/0xe0 Code: 48 8b 80 c8 03 00 00 48 85 c0 74 1f 48 8b 50 38 48 8b 43 18 RIP [<ffffffff8868f380>] :bridge:__br_deliver+0xcd/0xfc RSP <ffff810334641a88> And here is the crash dump backtrace: PID: 3718 TASK: ffff81033f7be7a0 CPU: 0 COMMAND: "syslogd" #0 [ffff8103346417e0] crash_kexec at ffffffff800afef5 #1 [ffff8103346418a0] __die at ffffffff80065127 #2 [ffff8103346418e0] do_page_fault at ffffffff80067474 #3 [ffff8103346419d0] error_exit at ffffffff8005dde9 #4 [ffff810334641a40] _spin_lock at ffffffff80064a58 #5 [ffff810334641ac0] dev_hard_start_xmit at ffffffff80236493 #6 [ffff810334641af0] dev_queue_xmit at ffffffff8002f76f #7 [ffff810334641b20] ip_output at ffffffff80031e05 #8 [ffff810334641b50] ip_push_pending_frames at ffffffff80254a48 #9 [ffff810334641b90] udp_push_pending_frames at ffffffff80264f34 #10 [ffff810334641bd0] udp_sendmsg at ffffffff80052420 #11 [ffff810334641cb0] sock_sendmsg at ffffffff80054e98 #12 [ffff810334641e50] sys_sendto at ffffffff8022dbae #13 [ffff810334641f80] tracesys at ffffffff8005d28d (via system_call) RIP: 00002b43634c1233 RSP: 00007fff614defa8 RFLAGS: 00000246 RAX: ffffffffffffffda RBX: ffffffff8005d28d RCX: ffffffffffffffff RDX: 0000000000000039 RSI: 00007fff614df040 RDI: 0000000000000007 RBP: 0000000000000000 R8: 00002b4379fdd478 R9: 0000000000000010 R10: 0000000000000000 R11: 0000000000000246 R12: 00007fff614df570 R13: 0000000000000000 R14: 00007fff614df040 R15: 00002b4379fdd408 ORIG_RAX: 000000000000002c CS: 0033 SS: 002b Please let me know if I should provide additional information regarding this problem. I'm willing to give you any information that helps to solve this.
This bug/component is not included in scope for RHEL-5.11.0 which is the last RHEL5 minor release. This Bugzilla will soon be CLOSED as WONTFIX (at the end of RHEL5.11 development phase (Apr 22, 2014)). Please contact your account manager or support representative in case you need to escalate this bug.
Thank you for submitting this request for inclusion in Red Hat Enterprise Linux 5. We've carefully evaluated the request, but are unable to include it in RHEL5 stream. If the issue is critical for your business, please provide additional business justification through the appropriate support channels (https://access.redhat.com/site/support).
Why do I still receive notifications for this bug!?