mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <regressions@leemhuis.info>
To: "regressions@lists.linux.dev" <regressions@lists.linux.dev>
Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] arm64 updates for 6.1-rc1 #forregzbot
Date: Wed, 7 Dec 2022 06:36:28 +0100	[thread overview]
Message-ID: <45f96562-e6d9-f586-0fcb-4e4f560f98ea@leemhuis.info> (raw)
In-Reply-To: <49ab0931-0d45-7884-e7b6-5c7d4de82ee2@leemhuis.info>

On 14.11.22 19:59, Thorsten Leemhuis wrote:
> [Note: this mail is primarily send for documentation purposes and/or for
> regzbot, my Linux kernel regression tracking bot. That's why I removed
> most or all folks from the list of recipients, but left any that looked
> like a mailing lists. These mails usually contain '#forregzbot' in the
> subject, to make them easy to spot and filter out.]
> 
> On 08.11.22 18:28, Amit Pundir wrote:
>> On Tue, 25 Oct 2022 at 18:08, Amit Pundir <amit.pundir@linaro.org> wrote:
>>> On Wed, 12 Oct 2022 at 17:24, Catalin Marinas <catalin.marinas@arm.com> wrote:
>>>> On Sat, Oct 08, 2022 at 08:28:26PM +0530, Amit Pundir wrote:
>>>>> On Wed, 5 Oct 2022 at 20:11, Catalin Marinas <catalin.marinas@arm.com> wrote:
>>>>>> Will Deacon (2):
>>>>>>       arm64: dma: Drop cache invalidation from arch_dma_prep_coherent()
>>>>>
>>>>> Hi Will,
>>>>>
>>>>> This patch broke AOSP on Dragonboard 845c (SDM845). I don't see any
>>>>> relevant crash in the attached log and device silently reboots into
>>>>> USB crash dump mode. The crash is fairly reproducible on db845c. I
>>>>> could trigger it twice in 5 reboots and it always crash at the same
>>>>> point during the boot process. Reverting this patch fixes the crash.
> [...]
> #regzbot ^introduced c44094eee32f
> #regzbot title arm64: crash on the Qualcomm SM8250
> #regzbot monitor
> https://lore.kernel.org/all/20221114110329.68413-1-manivannan.sadhasivam@linaro.org/

#regzbot fixed-by: b7d9aae404841d9999b7476170867ae441e948d2

      reply	other threads:[~2022-12-07  5:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-05 14:41 [GIT PULL] arm64 updates for 6.1-rc1 Catalin Marinas
2022-10-06 19:00 ` pr-tracker-bot
2022-10-08 14:58 ` Amit Pundir
2022-10-12 11:54   ` Catalin Marinas
2022-10-18 16:05     ` Amit Pundir
2022-10-25 12:38     ` Amit Pundir
2022-11-08 17:28       ` Amit Pundir
2022-11-11 11:15         ` Catalin Marinas
2022-11-11 11:54           ` Robin Murphy
2022-11-11 17:39           ` Manivannan Sadhasivam
2022-11-11 19:18             ` Manivannan Sadhasivam
2022-11-14 14:09               ` Will Deacon
2022-11-14 14:54                 ` Catalin Marinas
2022-11-14 18:59         ` [GIT PULL] arm64 updates for 6.1-rc1 #forregzbot Thorsten Leemhuis
2022-12-07  5:36           ` Thorsten Leemhuis [this message]

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=45f96562-e6d9-f586-0fcb-4e4f560f98ea@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    /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

all inboxes | Powered by JetHome®