All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Stapelberg <michael@stapelberg.ch>
To: dri-devel@lists.freedesktop.org, torvalds@linux-foundation.org,
	felix.kuehling@amd.com, Dave Airlie <airlied@gmail.com>
Subject: Re: [git pull] drm for 5.14-rc1
Date: Sat, 18 Sep 2021 11:18:33 +0200	[thread overview]
Message-ID: <871r5mp7h2.fsf@midna.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <CAHk-=whgcN6MEyZBgK3UZRw=vwd1CAAK9+rafmZ2vsOiGpsMSA@mail.gmail.com>

Hi,

torvalds at linux-foundation.org (Linus Torvalds) writes:
> Did I fix it up correctly? Who knows. The code makes more sense to me
> now and seems valid. But I really *really* want to stress how locking
> is important.

As far as I can tell, this merge conflict resolution made my Raspberry
Pi 3 hang on boot. You can find the full serial console output at:

https://t.zekjur.net/linux-5.14-raspberry-pi-3-hang-vc4.txt

The last few messages are from vc4, then the boot hangs.

Using git-bisect, I tracked this down to
https://github.com/torvalds/linux/commit/e058a84bfddc42ba356a2316f2cf1141974625c9,
which is the merge you’re talking about here, AFAICT.

I also tried the git://anongit.freedesktop.org/drm/drm, and that tree
boots as expected, suggesting that the problem really is with the
additional changes.

The code seems to work on my Raspberry Pi 4, just not on the Raspberry
Pi 3. Any ideas why that might be, and how to fix it?

Thanks!

-- 
Best regards,
Michael

  parent reply	other threads:[~2021-09-18 10:06 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-01  4:34 [git pull] drm for 5.14-rc1 Dave Airlie
2021-07-01  4:34 ` Dave Airlie
2021-07-01 20:15 ` Linus Torvalds
2021-07-01 20:15   ` Linus Torvalds
2021-07-01 21:31   ` Felix Kuehling
2021-07-01 21:31     ` Felix Kuehling
2021-09-18  9:18   ` Michael Stapelberg [this message]
2021-09-18 10:09     ` Simon Ser
2021-09-18 19:24     ` Linus Torvalds
2021-09-18 20:13       ` Michael Stapelberg
2021-09-18 22:12         ` Linus Torvalds
2021-09-19  7:26           ` Michael Stapelberg
2021-09-18 22:00       ` Sudip Mukherjee
2021-09-18 22:15         ` Linus Torvalds
2021-09-18 22:47           ` Sudip Mukherjee
2021-09-18 23:06             ` Linus Torvalds
2021-09-19 11:05               ` Sudip Mukherjee
2021-09-19 17:19                 ` Linus Torvalds
2021-09-20 12:17                   ` Maxime Ripard
2021-09-20 12:50                     ` Sudip Mukherjee
2021-09-20 17:10                     ` Linus Torvalds
2021-09-20 17:32                       ` Maxime Ripard
2021-09-20 17:47                         ` Linus Torvalds
2021-09-22 11:54                           ` Maxime Ripard
2021-09-20  8:55     ` Maxime Ripard
2021-09-20 12:18       ` Maxime Ripard
2021-07-01 20:24 ` pr-tracker-bot
2021-07-01 20:24   ` pr-tracker-bot

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=871r5mp7h2.fsf@midna.i-did-not-set--mail-host-address--so-tickle-me \
    --to=michael@stapelberg.ch \
    --cc=airlied@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=felix.kuehling@amd.com \
    --cc=torvalds@linux-foundation.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 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.