Dell PowerEdge R640

Server · 1U Rack

命

Lifecycle

Released
2017-07-11
General Availability
2017-07-11
End of Sale
2022-06-01
End of Support
2027-06-01
End of Service Life
2029-06-01

EOL

When a vendor has not published an exact date, we render an estimated range with an explicit confidence score — never an empty cell. See how to read TPM library records honestly.

Failure Outlook

Age: 9.0 years

Failure likelihood: 65%

Likely to fail (most → least)

  • PSUs (hot-plug wear)
  • Backplane capacitors
  • iDRAC CMOS battery
  • Fan modules (single-rotor design)
  • SAS expander board
禅

Indicative TPM Pricing

Indicative — not a quote.

SLA tierAnnualMonthly
9×5 NBD $700 – $1,050 $58 – $88
24×7 NBD $910 – $1,365 $76 – $114
24×7×4 onsite + parts $1,260 – $2,100 $105 – $175
24×7×4 remote only $630 – $1,470 $52 – $122

Pricing confidence: ●●○○○

Monthly = annual ÷ 12. Real TPM monthly billing is typically ~5–10% higher than this — use annual for accurate budgeting.

Get a real quote:

Coming soon Coming soon Coming soon

Bushido is an information service. We do not sell maintenance contracts — partners listed above do.

Affiliate disclosure: Bushido may earn a referral fee from successful introductions to listed partners. Partners pay nothing to be vetted or listed; revenue accrues only on completed business. Vetting standards are published at /partners/apply.

守

Security Advisories (8)

  • CVE-2021-21554 ↗ MEDIUM — Dell PowerEdge R640, R740, R740XD, R840, R940, R940xa, MX740c, MX840c, and, Dell Precision 7920 Rack Workstation BIOS contain a stack-based buffer overflow vulnerability in systems with Intel Optane DC Persistent Memory installed. A local malicious user with high privileges may potentially exploit this vulnerability, leading to a denial of Service, arbitrary code execution, or information disclosure in UEFI or BIOS Preboot Environment.
  • CVE-2021-21555 ↗ MEDIUM — Dell PowerEdge R640, R740, R740XD, R840, R940, R940xa, MX740c, MX840c, and T640 Server BIOS contain a heap-based buffer overflow vulnerability in systems with NVDIMM-N installed. A local malicious user with high privileges may potentially exploit this vulnerability, leading to a denial of Service, arbitrary code execution, or information disclosure in UEFI or BIOS Preboot Environment.
  • CVE-2021-21556 ↗ MEDIUM — Dell PowerEdge R640, R740, R740XD, R840, R940, R940xa, MX740c, MX840c, and T640 Server BIOS contain a stack-based buffer overflow vulnerability in systems with NVDIMM-N installed. A local malicious user with high privileges may potentially exploit this vulnerability, leading to a denial of Service, arbitrary code execution, or information disclosure in UEFI or BIOS Preboot Environment.
  • CVE-2021-47041 ↗ MEDIUM — In the Linux kernel, the following vulnerability has been resolved: nvmet-tcp: fix incorrect locking in state_change sk callback We are not changing anything in the TCP connection state so we should not take a write_lock but rather a read lock. This caused a deadlock when running nvmet-tcp and nvme-tcp on the same system, where state_change callbacks on the host and on the controller side have causal relationship and made lockdep report on this with blktests: ================================ WARNING: inconsistent lock state 5.12.0-rc3 #1 Tainted: G I -------------------------------- inconsistent {IN-SOFTIRQ-W} -> {SOFTIRQ-ON-R} usage. nvme/1324 [HC0[0]:SC0[0]:HE1:SE1] takes: ffff888363151000 (clock-AF_INET){++-?}-{2:2}, at: nvme_tcp_state_change+0x21/0x150 [nvme_tcp] {IN-SOFTIRQ-W} state was registered at: __lock_acquire+0x79b/0x18d0 lock_acquire+0x1ca/0x480 _raw_write_lock_bh+0x39/0x80 nvmet_tcp_state_change+0x21/0x170 [nvmet_tcp] tcp_fin+0x2a8/0x780 tcp_data_queue+0xf94/0x1f20 tcp_rcv_established+0x6ba/0x1f00 tcp_v4_do_rcv+0x502/0x760 tcp_v4_rcv+0x257e/0x3430 ip_protocol_deliver_rcu+0x69/0x6a0 ip_local_deliver_finish+0x1e2/0x2f0 ip_local_deliver+0x1a2/0x420 ip_rcv+0x4fb/0x6b0 __netif_receive_skb_one_core+0x162/0x1b0 process_backlog+0x1ff/0x770 __napi_poll.constprop.0+0xa9/0x5c0 net_rx_action+0x7b3/0xb30 __do_softirq+0x1f0/0x940 do_softirq+0xa1/0xd0 __local_bh_enable_ip+0xd8/0x100 ip_finish_output2+0x6b7/0x18a0 __ip_queue_xmit+0x706/0x1aa0 __tcp_transmit_skb+0x2068/0x2e20 tcp_write_xmit+0xc9e/0x2bb0 __tcp_push_pending_frames+0x92/0x310 inet_shutdown+0x158/0x300 __nvme_tcp_stop_queue+0x36/0x270 [nvme_tcp] nvme_tcp_stop_queue+0x87/0xb0 [nvme_tcp] nvme_tcp_teardown_admin_queue+0x69/0xe0 [nvme_tcp] nvme_do_delete_ctrl+0x100/0x10c [nvme_core] nvme_sysfs_delete.cold+0x8/0xd [nvme_core] kernfs_fop_write_iter+0x2c7/0x460 new_sync_write+0x36c/0x610 vfs_write+0x5c0/0x870 ksys_write+0xf9/0x1d0 do_syscall_64+0x33/0x40 entry_SYSCALL_64_after_hwframe+0x44/0xae irq event stamp: 10687 hardirqs last enabled at (10687): [<ffffffff9ec376bd>] _raw_spin_unlock_irqrestore+0x2d/0x40 hardirqs last disabled at (10686): [<ffffffff9ec374d8>] _raw_spin_lock_irqsave+0x68/0x90 softirqs last enabled at (10684): [<ffffffff9f000608>] __do_softirq+0x608/0x940 softirqs last disabled at (10649): [<ffffffff9cdedd31>] do_softirq+0xa1/0xd0 other info that might help us debug this: Possible unsafe locking scenario: CPU0 ---- lock(clock-AF_INET); <Interrupt> lock(clock-AF_INET); *** DEADLOCK *** 5 locks held by nvme/1324: #0: ffff8884a01fe470 (sb_writers#4){.+.+}-{0:0}, at: ksys_write+0xf9/0x1d0 #1: ffff8886e435c090 (&of->mutex){+.+.}-{3:3}, at: kernfs_fop_write_iter+0x216/0x460 #2: ffff888104d90c38 (kn->active#255){++++}-{0:0}, at: kernfs_remove_self+0x22d/0x330 #3: ffff8884634538d0 (&queue->queue_lock){+.+.}-{3:3}, at: nvme_tcp_stop_queue+0x52/0xb0 [nvme_tcp] #4: ffff888363150d30 (sk_lock-AF_INET){+.+.}-{0:0}, at: inet_shutdown+0x59/0x300 stack backtrace: CPU: 26 PID: 1324 Comm: nvme Tainted: G I 5.12.0-rc3 #1 Hardware name: Dell Inc. PowerEdge R640/06NR82, BIOS 2.10.0 11/12/2020 Call Trace: dump_stack+0x93/0xc2 mark_lock_irq.cold+0x2c/0xb3 ? verify_lock_unused+0x390/0x390 ? stack_trace_consume_entry+0x160/0x160 ? lock_downgrade+0x100/0x100 ? save_trace+0x88/0x5e0 ? _raw_spin_unlock_irqrestore+0x2d/0x40 mark_lock+0x530/0x1470 ? mark_lock_irq+0x1d10/0x1d10 ? enqueue_timer+0x660/0x660 mark_usage+0x215/0x2a0 __lock_acquire+0x79b/0x18d0 ? tcp_schedule_loss_probe.part.0+0x38c/0x520 lock_acquire+0x1ca/0x480 ? nvme_tcp_state_change+0x21/0x150 [nvme_tcp] ? rcu_read_unlock+0x40/0x40 ? tcp_mtu_probe+0x1ae0/0x1ae0 ? kmalloc_reserve+0xa0/0xa0 ? sysfs_file_ops+0x170/0x170 _raw_read_lock+0x3d/0xa0 ? nvme_tcp_state_change+0x21/0x150 [nvme_tcp] nvme_tcp_state_change+0x21/0x150 [nvme_tcp] ? sysfs_file_ops ---truncated---
  • CVE-2025-38684 ↗ MEDIUM — In the Linux kernel, the following vulnerability has been resolved: net/sched: ets: use old 'nbands' while purging unused classes Shuang reported sch_ets test-case [1] crashing in ets_class_qlen_notify() after recent changes from Lion [2]. The problem is: in ets_qdisc_change() we purge unused DWRR queues; the value of 'q->nbands' is the new one, and the cleanup should be done with the old one. The problem is here since my first attempts to fix ets_qdisc_change(), but it surfaced again after the recent qdisc len accounting fixes. Fix it purging idle DWRR queues before assigning a new value of 'q->nbands', so that all purge operations find a consistent configuration: - old 'q->nbands' because it's needed by ets_class_find() - old 'q->nstrict' because it's needed by ets_class_is_strict() BUG: kernel NULL pointer dereference, address: 0000000000000000 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 0 P4D 0 Oops: Oops: 0000 [#1] SMP NOPTI CPU: 62 UID: 0 PID: 39457 Comm: tc Kdump: loaded Not tainted 6.12.0-116.el10.x86_64 #1 PREEMPT(voluntary) Hardware name: Dell Inc. PowerEdge R640/06DKY5, BIOS 2.12.2 07/09/2021 RIP: 0010:__list_del_entry_valid_or_report+0x4/0x80 Code: ff 4c 39 c7 0f 84 39 19 8e ff b8 01 00 00 00 c3 cc cc cc cc 66 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3 0f 1e fa <48> 8b 17 48 8b 4f 08 48 85 d2 0f 84 56 19 8e ff 48 85 c9 0f 84 ab RSP: 0018:ffffba186009f400 EFLAGS: 00010202 RAX: 00000000000000d6 RBX: 0000000000000000 RCX: 0000000000000004 RDX: ffff9f0fa29b69c0 RSI: 0000000000000000 RDI: 0000000000000000 RBP: ffffffffc12c2400 R08: 0000000000000008 R09: 0000000000000004 R10: ffffffffffffffff R11: 0000000000000004 R12: 0000000000000000 R13: ffff9f0f8cfe0000 R14: 0000000000100005 R15: 0000000000000000 FS: 00007f2154f37480(0000) GS:ffff9f269c1c0000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000000 CR3: 00000001530be001 CR4: 00000000007726f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 PKRU: 55555554 Call Trace: <TASK> ets_class_qlen_notify+0x65/0x90 [sch_ets] qdisc_tree_reduce_backlog+0x74/0x110 ets_qdisc_change+0x630/0xa40 [sch_ets] __tc_modify_qdisc.constprop.0+0x216/0x7f0 tc_modify_qdisc+0x7c/0x120 rtnetlink_rcv_msg+0x145/0x3f0 netlink_rcv_skb+0x53/0x100 netlink_unicast+0x245/0x390 netlink_sendmsg+0x21b/0x470 ____sys_sendmsg+0x39d/0x3d0 ___sys_sendmsg+0x9a/0xe0 __sys_sendmsg+0x7a/0xd0 do_syscall_64+0x7d/0x160 entry_SYSCALL_64_after_hwframe+0x76/0x7e RIP: 0033:0x7f2155114084 Code: 89 02 b8 ff ff ff ff eb bb 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 f3 0f 1e fa 80 3d 25 f0 0c 00 00 74 13 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 54 c3 0f 1f 00 48 83 ec 28 89 54 24 1c 48 89 RSP: 002b:00007fff1fd7a988 EFLAGS: 00000202 ORIG_RAX: 000000000000002e RAX: ffffffffffffffda RBX: 0000560ec063e5e0 RCX: 00007f2155114084 RDX: 0000000000000000 RSI: 00007fff1fd7a9f0 RDI: 0000000000000003 RBP: 00007fff1fd7aa60 R08: 0000000000000010 R09: 000000000000003f R10: 0000560ee9b3a010 R11: 0000000000000202 R12: 00007fff1fd7aae0 R13: 000000006891ccde R14: 0000560ec063e5e0 R15: 00007fff1fd7aad0 </TASK> [1] https://lore.kernel.org/netdev/e08c7f4a6882f260011909a868311c6e9b54f3e4.1639153474.git.dcaratti@redhat.com/ [2] https://lore.kernel.org/netdev/[email protected]/

CVE data from NVD (National Vulnerability Database). KEV flag from CISA Known Exploited Vulnerabilities catalog. Always verify against the vendor's own security advisory portal.

Parts Market

Whole unit: $300 – $1100

Common parts

  • Fan Module — $30
  • PERC H730P Mini — $60
  • PSU 750W Platinum — $75
  • DIMM 32GB DDR4 2933 — $25
探

Find parts for this unit

Bushido publishes the standard bill of materials above. For substitute part chains, current pricing, and serial- or service-tag-specific configurations, go straight to the manufacturer's own portal — the authoritative source. We don't scrape or resell parts data, and we earn nothing from these links.

Dell — official sources

Independent cross-reference — not affiliated with Bushido

Dell does not publish a public substitute cross-reference — alternate-part chains live in Dell's internal service systems. Use the Service Tag lookup for the original BOM, then the third-party cross-reference below for substitutes.

No single manufacturer publishes a cross-vendor "alternative parts" list, and no one official aggregates across all vendors. Lenovo and HPE expose substitute chains publicly; Dell and Sun/Oracle keep them internal or gated. These links are the honest map of where each vendor's data actually lives. If a link is dead or a portal has moved, tell us and we'll fix it.

Modern Replacements

Direct successor: Dell PowerEdge R650 (2021) — 15th Gen, 3rd Gen Intel Xeon Scalable (Ice Lake), 32 DIMM slots, OCP 3.0 NIC, integrated BOSS-S2; same 1U rack footprint

Current generation: Dell PowerEdge R660 (2023) — 16th Gen, 4th/5th Gen Intel Xeon Scalable, PCIe Gen5, DDR5, higher core density in 1U

Power / Rack

Idle: 150W · Typical: 500W · Max PSU: 1100W

1U

部

Standard Bill of Materials (at GA)

The Dell EMC PowerEdge R640 shipped at GA (July 2017) as a 1U dual-socket rack server built on the Intel C620 (Lewisburg) chipset. The base configuration included one Intel Xeon Silver 4110 processor (8-core, 2.1 GHz, 85W TDP), two 16 GB DDR4 RDIMM DIMMs at 2666 MT/s (of 24 available slots), a PERC H730P Mini RAID controller with 2 GB NV cache, two 495 W Platinum hot-plug redundant PSUs, an Intel i350 quad-port 1 GbE NDC (Network Daughter Card), iDRAC9 Express with a dedicated 1 GbE management port, and ReadyRails II sliding rail kit. The chassis offered a choice of 4×3.5-inch LFF, 8×2.5-inch SFF, or 10×2.5-inch SFF drive bays; the 8-bay SFF chassis was the most common base SKU. No drives were included in the base system-only configuration.

ComponentDescriptionPart #QtyNotes
CPU Intel Xeon Silver 4110 (8C/16T, 2.1 GHz, 85W TDP) 338-BLTU 1 Base 1-CPU SKU; second socket populated optionally; supported up to Platinum 8180 (28C)
RAM 16 GB DDR4 RDIMM 2666 MT/s single rank 370-ADND 2 24 DIMM slots total (12 per CPU); max 3 TB with LRDIMMs or 7.68 TB with Optane PMem
RAID Controller PERC H730P Mini Mono 2 GB NV cache 405-AAOG 1 Supports RAID 0/1/5/6/10/50/60; HBA330 and H740P also orderable
PSU 495 W Platinum hot-plug redundant AC 450-ADWS 2 750 W, 1100 W, and 1600 W options available; 1600 W requires 200–240 V high-line
NIC Intel i350 4×1 GbE NDC (Network Daughter Card) 540-BBHB 1 NDC slot; optional 2×10 GbE, 4×10 GbE, or 2×25 GbE NDC cards available
Management iDRAC9 Express with dedicated 1 GbE port 385-BBKT 1 iDRAC9 Enterprise and Datacenter licenses available; QuickSync 2 optional
Rails ReadyRails II sliding rails with optional CMA 770-BBBQ 1 Static rails also available; CMA kit sold separately

BOM reflects the standard base configuration at GA (July 2017) for the 8×2.5-inch SFF chassis SKU. Non-standard CPU quantities, larger memory configurations, NVMe-only chassis variants, BOSS boot-accelerator cards, GPU options, and factory-installed OS are not enumerated. Part numbers shown are Dell order codes valid at launch and may have been superseded; always cross-reference with Dell's current spare-parts portal before ordering.

BOM is AI-synthesized from public datasheets. Cross-reference with the vendor's spare-parts portal before ordering.

Firmware

  • BIOS: 2.23.0
  • iDRAC: 6.10.30

Download pointer ↗

道

Next Steps

  • Want a real maintenance quote? → See the partner list in the pricing block above
  • Want to replace it? → See the modern replacements section
  • Want to repair it yourself? → Check secondhand pricing in the parts market block
  • Want the latest firmware? → Vendor download page ↗
  • Want to verify security advisories? → See the advisories block — each CVE links to NVD detail
  • Want to verify our data? → Cross-reference with the vendor's own EOL bulletin and authoritative aggregators. Every field carries a confidence score above.

Bushido is an information service. We do not sell maintenance, parts, or support — partners listed above do.