linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Tytus Rogalewski <tytanick@gmail.com>
To: "David Hildenbrand (Arm)" <david@kernel.org>
Cc: linux-mm@kvack.org, muchun.song@linux.dev, osalvador@suse.de
Subject: Re: walk_pgd_range BUG: unable to handle page fault
Date: Thu, 5 Mar 2026 09:11:43 +0100	[thread overview]
Message-ID: <CANfXJzthDnrQJoCQWrfZwK1Mrw4QZv92ZEzsOy6WGqq3zCYzHw@mail.gmail.com> (raw)
In-Reply-To: <CANfXJzt7yGZZcuBjmazU9n7V8vupMSLNm+qCiZxcrmtUZicR1g@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1496 bytes --]

Hi David,

This is strange but the issue stopped when i changed io_uring to threads.
Would that make any sense ?
We did also few other smaller things but honestly issues stopped.
Was it fixed or maybe Async IO could cause it ? (The qcow2 image is on fuse
mounting).

I am not certain but if that makes any sense, should i report this to
someone working on io_uring or it should have nothing to do with that bug ?

[image: CleanShot 2026-03-05 at 09.08.15@2x.png]

On all those kernels i seen no such bug for few weeks after changing async
io.

[image: CleanShot 2026-03-05 at 09.09.03@2x.png]

--

tel. 790 202 300

*Tytus Rogalewski*

Dolina Krzemowa 6A

83-010 Jagatowo

NIP: 9570976234


czw., 5 lut 2026 o 14:20 Tytus Rogalewski <tytanick@gmail.com> napisał(a):

> All my clients are renting GPUs so i can passthrough but i have no idea
> what they are doing there and it is not instant crash. it can work for few
> days under heavy load and then it happens. So even if i would di cpu only,
> i dont think it would give us anything.
>
> --
>
> tel. 790 202 300
>
> *Tytus Rogalewski*
>
> Dolina Krzemowa 6A
>
> 83-010 Jagatowo
>
> NIP: 9570976234
>
>
> czw., 5 lut 2026 o 13:57 David Hildenbrand (Arm) <david@kernel.org>
> napisał(a):
>
>> On 2/5/26 13:46, Tytus Rogalewski wrote:
>> > Hehe, i cant. I dont have any CPU only servers :)
>>
>> But you can just not passthrough a GPU to the VM?
>> --
>> Cheers,
>>
>> David
>>
>

[-- Attachment #1.2: Type: text/html, Size: 4425 bytes --]

[-- Attachment #2: CleanShot 2026-03-05 at 09.08.15@2x.png --]
[-- Type: image/png, Size: 26541 bytes --]

[-- Attachment #3: CleanShot 2026-03-05 at 09.09.03@2x.png --]
[-- Type: image/png, Size: 74642 bytes --]

  reply	other threads:[~2026-03-05  8:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CANfXJzt4P+FCkdL_=FfmG80_bY8FkzSocJSPeksSQ_vXObRNOQ@mail.gmail.com>
2026-02-04 21:52 ` David Hildenbrand (arm)
2026-02-04 22:24   ` Tytus Rogalewski
2026-02-04 22:50     ` Tytus Rogalewski
2026-02-05 12:44       ` David Hildenbrand (Arm)
2026-02-05 12:46         ` Tytus Rogalewski
2026-02-05 12:57           ` David Hildenbrand (Arm)
2026-02-05 13:20             ` Tytus Rogalewski
2026-03-05  8:11               ` Tytus Rogalewski [this message]
2026-03-05 11:17                 ` David Hildenbrand (Arm)
2026-03-05 11:29                   ` Tytus Rogalewski
2026-03-05 11:33                     ` David Hildenbrand (Arm)
2026-03-05 11:34                       ` Tytus Rogalewski
2026-03-05 11:38                         ` David Hildenbrand (Arm)
2026-03-05 11:39                           ` Tytus Rogalewski
2026-03-05 11:40                             ` David Hildenbrand (Arm)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CANfXJzthDnrQJoCQWrfZwK1Mrw4QZv92ZEzsOy6WGqq3zCYzHw@mail.gmail.com \
    --to=tytanick@gmail.com \
    --cc=david@kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=muchun.song@linux.dev \
    --cc=osalvador@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox