Nemotron 3.5 Bolt on GB10: intermittent "prepared model reported device error 6" mid-stream at concurrency 1

オープン
  • 何か問題がありますか？
#52 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
48/100
issue の種類
バグ
明瞭さ
おおむね明確
活発さ
活発
技術スタック
python
領域
backend, performance

調査の方向性

Start by tracing where streaming decode reports prepared model reported device error 6, then compare that path with the intermittent KV page reuse issue in #14. Reproduce with the supplied GB10 setup and sequential streaming requests at --max-concurrency 1, using the offered debug build or request bodies to capture more detail. Done when the cause is identified and the supplied workload no longer produces mid-stream errors.

索引モデルが issue の本文から書いたものです。

説明

bug model:nemotron-3.5-bolt priority:P2 triage:investigate

Summary

Streaming chat completions intermittently fail mid-stream with prepared model reported device error 6 on a single DGX Spark (GB10) serving Nemotron 3.5 Bolt at --max-concurrency 1. The first token is streamed, then the stream ends with a server_error. 4 of the first 11 requests to this server process failed, all from one agent session.

Environment

  • NVIDIA DGX Spark, GB10 (SM121), driver 580.178.04, CUDA 13.0, kernel 7.0.0-1019-nvidia
  • Flare 47581cc (2026-10-20), release build
  • Package: nvidia/NVIDIA-Nemotron-3.5-Bolt-74B-A9B-24GB, exported for concurrency 4
  • Command: flare run bolt-lilicorr-c4.safetensors --gpus 0 --host 0.0.0.0 --port 8000 --served-model-name nemotron-3.5-bolt --kv-cache-limit concurrency --max-concurrency 1
  • Startup: Prepare execution. concurrency 1, Plan cache. per GPU: 27.73 GiB loaded · 69.30 GiB cache budget · reserve 4GiB · KV capped at 1 contexts

Workload

One OpenCode agent session (OpenAI-compatible /v1/chat/completions, stream: true, tools defined, chat_template_kwargs.enable_thinking: false). Requests are sequential; there is never more than one in flight. Prompt sizes at the failures were about 28K–53K tokens, mostly a reused prefix.

Server log

[Fri, 23 Oct 2026 10:16:08 GMT] request_id=chatcmpl-1307976-6 stage=stream code=server_error message="prepared model reported device error 6"
[Fri, 23 Oct 2026 10:16:46 GMT] request_id=chatcmpl-1307976-7 stage=stream code=server_error message="prepared model reported device error 6"
[Fri, 23 Oct 2026 10:16:50 GMT] request_id=chatcmpl-1307976-8 stage=stream code=server_error message="prepared model reported device error 6"
[Fri, 23 Oct 2026 10:22:57 GMT] request_id=chatcmpl-1307976-11 stage=stream code=server_error message="prepared model reported device error 6"

Client-side error

{"type":"server_error","message":"prepared model reported device error 6","param":null,"code":"server_error"}

The HTTP status is 200; the error arrives in the stream after the first content token.

Notes

  • The server stays up after each error, and the next request succeeds.
  • The same error appeared on 2026-10-21 with the same package under concurrent requests.
  • Possibly related: #14 (intermittent mid-decode errors from reused KV pages on SM120). The error code here is 6, not 1.

I can provide the full request bodies or run a debug build if that helps.

主要言語
Rust
スター
800
フォーク
106
平均マージ
1日 3時間
マージ済み PR（30日）
100

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

NVIDIA/hyperflare-inference のほかの issue

NVIDIA/hyperflare-inference の issue をすべて見る

似ている issue

Rust の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。