From: Diederik de Haas <didi.debian@cknow.org>
To: Karol Herbst <kherbst@redhat.com>,
Thorsten Leemhuis <regressions@leemhuis.info>,
Olaf Skibbe <news@kravcenko.com>
Cc: dri-devel@lists.freedesktop.org, nouveau@lists.freedesktop.org,
1042753@bugs.debian.org, Ben Skeggs <bskeggs@redhat.com>,
Lyude Paul <lyude@redhat.com>,
Linux kernel regressions list <regressions@lists.linux.dev>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: Bug#1042753: nouveau bug in linux/6.1.38-2
Date: Fri, 04 Aug 2023 15:38:03 +0200 [thread overview]
Message-ID: <1861943.tdWV9SEqCh@bagend> (raw)
In-Reply-To: <b12e2b00-de18-df9c-eb4a-c6704aad2c97@kravcenko.com>
[-- Attachment #1: Type: text/plain, Size: 402 bytes --]
On Friday, 4 August 2023 15:11:46 CEST Olaf Skibbe wrote:
> (On the occasion a maybe silly question: am I right assuming that the
> kernel has to be build on the machine we want to reproduce the bug on?
> Otherwise it could use much faster hardware (running also bookworm).)
If that is also an amd64 machine running Debian kernel 6.1.38-2, it should be
fine to build the kernel on the faster machine.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-08-04 13:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20be6650-5db3-b72a-a7a8-5e817113cff5@kravcenko.com>
2023-08-04 12:02 ` nouveau bug in linux/6.1.38-2 Thorsten Leemhuis
2023-08-04 12:15 ` Karol Herbst
2023-08-04 12:46 ` Olaf Skibbe
2023-08-04 12:51 ` Karol Herbst
2023-08-04 13:11 ` Olaf Skibbe
2023-08-04 13:38 ` Diederik de Haas [this message]
2023-08-04 18:08 ` Olaf Skibbe
2023-08-04 23:09 ` Karol Herbst
2023-08-05 9:44 ` Olaf Skibbe
2023-08-31 9:40 ` Linux regression tracking #update (Thorsten Leemhuis)
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=1861943.tdWV9SEqCh@bagend \
--to=didi.debian@cknow.org \
--cc=1042753@bugs.debian.org \
--cc=bskeggs@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kherbst@redhat.com \
--cc=lyude@redhat.com \
--cc=news@kravcenko.com \
--cc=nouveau@lists.freedesktop.org \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.org \
/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