From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
Cc: Srinivasan Shanmugam <srinivasan.shanmugam@amd.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
amd-gfx@lists.freedesktop.org,
Alex Deucher <alexander.deucher@amd.com>,
David Airlie <airlied@gmail.com>
Subject: Re: next-20230726 and later - crash in radeon module during init
Date: Thu, 10 Aug 2023 05:44:24 -0400 [thread overview]
Message-ID: <130185.1691660664@turing-police> (raw)
In-Reply-To: <129403.1691660102@turing-police>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 431 bytes --]
On Thu, 10 Aug 2023 05:35:02 -0400, "Valdis Klētnieks" said:
> I am seeing the following consistent crash at boot:
> Some quick digging indicates the most likely culprit is:
>
> commit cbd0606e6a776bf2ba10d4a6957bb7628c0da947
> Author: Srinivasan Shanmugam <srinivasan.shanmugam@amd.com>
> Date: Thu Jul 20 15:39:24 2023 +0530
>
> drm/radeon: Prefer dev_* variant over printk
Nevermind - I see it was already reverted...
[-- Attachment #2: Type: application/pgp-signature, Size: 494 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
Cc: Srinivasan Shanmugam <srinivasan.shanmugam@amd.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
amd-gfx@lists.freedesktop.org,
Alex Deucher <alexander.deucher@amd.com>
Subject: Re: next-20230726 and later - crash in radeon module during init
Date: Thu, 10 Aug 2023 05:44:24 -0400 [thread overview]
Message-ID: <130185.1691660664@turing-police> (raw)
In-Reply-To: <129403.1691660102@turing-police>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 431 bytes --]
On Thu, 10 Aug 2023 05:35:02 -0400, "Valdis Klētnieks" said:
> I am seeing the following consistent crash at boot:
> Some quick digging indicates the most likely culprit is:
>
> commit cbd0606e6a776bf2ba10d4a6957bb7628c0da947
> Author: Srinivasan Shanmugam <srinivasan.shanmugam@amd.com>
> Date: Thu Jul 20 15:39:24 2023 +0530
>
> drm/radeon: Prefer dev_* variant over printk
Nevermind - I see it was already reverted...
[-- Attachment #2: Type: application/pgp-signature, Size: 494 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: unlisted-recipients:; (no To-header on input)
Cc: Srinivasan Shanmugam <srinivasan.shanmugam@amd.com>,
Alex Deucher <alexander.deucher@amd.com>,
David Airlie <airlied@gmail.com>,
amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: next-20230726 and later - crash in radeon module during init
Date: Thu, 10 Aug 2023 05:44:24 -0400 [thread overview]
Message-ID: <130185.1691660664@turing-police> (raw)
In-Reply-To: <129403.1691660102@turing-police>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 431 bytes --]
On Thu, 10 Aug 2023 05:35:02 -0400, "Valdis Klētnieks" said:
> I am seeing the following consistent crash at boot:
> Some quick digging indicates the most likely culprit is:
>
> commit cbd0606e6a776bf2ba10d4a6957bb7628c0da947
> Author: Srinivasan Shanmugam <srinivasan.shanmugam@amd.com>
> Date: Thu Jul 20 15:39:24 2023 +0530
>
> drm/radeon: Prefer dev_* variant over printk
Nevermind - I see it was already reverted...
[-- Attachment #2: Type: application/pgp-signature, Size: 494 bytes --]
next prev parent reply other threads:[~2023-08-10 12:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 9:35 next-20230726 and later - crash in radeon module during init Valdis Klētnieks
2023-08-10 9:35 ` Valdis Klētnieks
2023-08-10 9:35 ` Valdis Klētnieks
2023-08-10 9:44 ` Valdis Klētnieks [this message]
2023-08-10 9:44 ` Valdis Klētnieks
2023-08-10 9:44 ` Valdis Klētnieks
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=130185.1691660664@turing-police \
--to=valdis.kletnieks@vt.edu \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=srinivasan.shanmugam@amd.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.